-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
railsexpress patches won't apply on p448 and latest stable RVM (1.21.20) #20
Comments
Also, for what it's worth, I tried this on another, similar machine, with similar results |
Is it possible that you applied additional patches? Can you paste the full rvm command you used and all output? Otherwise I don't see how to make progress on this issue. |
Certainly. Here it is: $ rvmsudo rvm install 1.9.3 --patch railsexpress -n railsexpress
to avoid the warning, put it in shell initialization file to make it persistent. In case there is no
to avoid the warning, put it in shell initialization file to make it persistent. |
In pasting this, I noticed: Patch 'https://raw.github.com/skaes/rvm-patchsets/master/patches/ruby/1.9.3/p448/railsexpress/01-fix-make-clean.patch' not found. Not sure if that is relevant. |
$ patch -v This program comes with NO WARRANTY, to the extent permitted by law. written by Larry Wall and Paul Eggert |
@srobertjames did you found a solution or workaround? I'm also experiencing this issue when using rvm 1.22.14. |
I have no clue yet. I'll try to investigate a bit more this week. Sorry for the delay. |
I just encountered this when trying to install Ruby 1.9.3-p448 with the railsexpress patch on a CentOS 5.9 box via Chef. When I tried installing it using the This might not be the cause of the issue that @srobertjames was experiencing, but I feel like there's at least a non-zero chance that looking at how many rvm-related processes are running might be illuminating, and a reasonable chance that this might be related to issues outside of this repo. |
I just found out that my issue happens when i'm using zsh. I'm using Mountain Lion with oh-my-zsh. I simply switched to bash and used the same command that I was trying with zsh. It worked perfectly. All patches were properly applied. Maybe this is related to what @justinlocsei reported. |
FWIW, I just ran into "patch not found" errors while running After attempting this several times, it seems that rvm will fail to download railsexpress's subpatches in a non-deterministic manner--sometimes it successfully gets a few of them, sometimes only one or two. I'm able to install the ruby version after attempting the install several times (allowing the local patch cache to populate), which implies a race condition or network-related issue. I'm hoping it's just network-related, which means it's temporary, but I'll post a follow-up if the problem continues. Relevant details:
|
Interesting - I'm using zsh as well On 11/17/13, Jeff Lee notifications@github.com wrote:
|
@srobertjames Just to clarify, we're not using zsh. Previous commentators mentioned that moving from zsh to bash fixes it, but we're still encountering this problem intermittently using bash. |
Confirm the same (patch not found) problem on debian |
I head the same issue and could fix it. I run "rvm get stable" and still got the error. I run "rvm get head" and .rvm/patchsets/ruby/ includes 2.2.3 as latest ruby. |
"rvm get head" also made it work for me with "rvm install 2.5.0 --patch railsexpress -n railsexpress". |
Applying patch https://raw.github.com/skaes/rvm-patchsets/master/patches/ruby/1.9.3/p448/railsexpress/13-railsbench-gc-fixes.patch...................
Error running 'patch -F 25 -p1 -N -f -i /tmp/tmp.KS6QFKzsmCghFhvZHQ',
please read /usr/local/rvm/log/ruby-1.9.3-p448-railsexpress/1376062746_patch.apply.13-railsbench-gc-fixes.patch.log
$ cat /usr/local/rvm/log/ruby-1.9.3-p448-railsexpress/1376062746_patch.apply.13-railsbench-gc-fixes.patch.log
patching file gc.c
Hunk #1 FAILED at 108.
Hunk #2 succeeded at 312 (offset -9 lines).
Hunk #3 FAILED at 557.
Hunk #4 succeeded at 572 with fuzz 3 (offset -9 lines).
Hunk #5 FAILED at 604.
Hunk #6 FAILED at 643.
Hunk #7 succeeded at 593 (offset -111 lines).
Hunk #8 FAILED at 1536.
Hunk #9 FAILED at 1794.
Hunk #10 succeeded at 1299 with fuzz 3 (offset -620 lines).
Hunk #11 FAILED at 2547.
Hunk #12 FAILED at 2563.
Hunk #13 FAILED at 3048.
Hunk #14 succeeded at 2373 with fuzz 2 (offset -714 lines).
Hunk #15 succeeded at 2386 with fuzz 3 (offset -714 lines).
Hunk #16 FAILED at 3150.
Hunk #17 FAILED at 3437.
11 out of 17 hunks FAILED -- saving rejects to file gc.c.rej
$ cat /etc/redhat-release
CentOS release 6.3 (Final)
$ rvm -v
rvm 1.21.20 (stable) by Wayne E. Seguin wayneeseguin@gmail.com, Michal Papis mpapis@gmail.com [https://rvm.io/]
The text was updated successfully, but these errors were encountered: