-
-
Notifications
You must be signed in to change notification settings - Fork 11.3k
ruby: postinstall fail #29982
Comments
I hate do do this, but "me, too."
|
I'm not sure what's causing that undefined method error, I wasn't getting it a few days ago (installed from bottle and source). However as of 2.1.2_1, the newly installed gems directory is non-empty, so I guess we can just wipe it for now. |
Same issue on OS X 10.10 FWIW. I just ended up removing the Homebrew ruby and going back to Yosemite's system version. For some reason the Homebrew formula for Ruby has always given me issues on both 10.9-10.9.3 and now 10.10. |
Is it really safe to delete the gems that come bundled with Ruby? |
Doing so has never caused me any issues. For some reason Ruby seems to habitually get bunged up and struggles to update gems, so I occasionally end up wandering into the folder and blitzing everything in sight and then going back to the terminal and doing 'gem install xxxxx' and updating that way, which works flawlessly from then for a pretty decent amount of time. |
Got the same problem... |
Same issue this morning while doing an upgrade (10.9.3):
|
Same issue OSX 10.9.3
|
We don't need any more "I also have this issue" reports at this time, thanks. |
Yup. Please run |
|
At this point we don't need any more debugging information - thanks. Will have a solution soon. |
@mistydemeo Sorry! Thank you! |
I guess there's no workaround for the time being? |
(workaround) |
@hlian Your workaround doesn't work for me:
|
Try making the directory empty :) |
@hlian I don't know the semantic result of that—clearly I had rake, test-unit, and rdoc before; do I still need them? These aren't symlinks so if I just blow away those libs and executables, they're gone. I've managed distros of Perl and Python before, so I'd know what to do in this sort of situation, but I'm a neophyte when it comes to Ruby installs. |
Conjecture: those are the default gems, and the recipe wants to delete them, but it's using Qualifier: not a Ruby expert. Just an ordinary dude who wanted to update a CocoaPod. |
@hlian That's what pull request #29986 does in 5dcf6c1, so I'm hoping it's safe? (OTOH, that pull request hasn't been accepted and others earlier in the thread say this is "being worked on", so not sure if this is the right answer or just a "make-it-work-for-now" hack.) I use rake and rdoc myself. I suppose I can always backup those dirs and back out to a previous ruby if it's not the case. |
I'm testing a fix for this that should be ready later today. |
This configures rubygems to install all gems into a public, non-versioned directory by default - both gems and their binaries. (This means that users no longer need /usr/local/opt/ruby/bin in their PATH.) This means that we no longer have to monkey with gem directories at all in postinstall. Bundled gems will be symlinked into this location. Fixes Homebrew#29982. Closes Homebrew#29986.
PR in #30129 for the bots to test/build bottles |
This configures rubygems to install all gems into a public, non-versioned directory by default - both gems and their binaries. (This means that users no longer need /usr/local/opt/ruby/bin in their PATH.) This means that we no longer have to monkey with gem directories at all in postinstall. Bundled gems will be symlinked into this location. Fixes Homebrew#29982. Closes Homebrew#29986.
Pushed the fix. |
This configures rubygems to install all gems into a public, non-versioned directory by default - both gems and their binaries. (This means that users no longer need /usr/local/opt/ruby/bin in their PATH.) This means that we no longer have to monkey with gem directories at all in postinstall. Bundled gems will be symlinked into this location. Fixes Homebrew#29982. Closes Homebrew#29986.
The text was updated successfully, but these errors were encountered: