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
Gem install minitest on NFS fails #1161
Comments
IMO the bug comes from this hoe crap, that is what the seattlerb gems have in common. |
I guess it is. Is there any ways to skip the minitest part in ruby installation? |
@jirutka crap? "humble" opinion? interesting... |
@drbrain, I believe this to be a bug in rubygems' tar support. I've verified that it is NOT an issue with NFS by manually untarring a minitest gem on one of the affected hosts w/ NFS and then used
I tried futzing with the mkdir_p to not use OK. I tried this and it works (rubygems/package.rb:369) : open destination, 'wb' do |out|
out.write entry.read
File.chmod entry.header.mode, destination
end if entry.file? |
Fix incoming... |
Well, if it’s a bug in RubyGems, then why the problem occurs only with seattlerb gems (that uses hoe) and not any normal gems that uses RubyGems’ GemSpec? |
@drbrain, this is fixed and tested live against NFS. I can't realistically write a test against this, but all tests pass fwiw. This bug blocks installing newer versions of ruby, because they blow up installing minitest. I highly doubt that ruby's install is flexible enough to grab newer versions of rubygems, so this is still stuck until this gets released AND ruby gets updated to point to it. |
@jirutka because of hoe crap, according to you. |
@zenspider This is only my guess. You’ve told that the bug is in RubyGems, not hoe, so a logical question arises — why it affects only seattlerb gems? |
This is also breaking rbenv installations of 2.2.0 on an NFS mounted /home directory on Ubuntu server 14.04 |
@excalq this fix shipped in 2.4.6 / 2015-02-05. |
@drbrain can we get this backported/updated in ruby 2.2.x? |
Rubygems may fail when installing on NFS filesystems as reported in Issue #1161: rubygems/rubygems#1161 Apply patch supplied for that issue into ruby's version of rubygems.
This is still affecting me today. Ubuntu 16.04, Ruby 2.2.1, home directory mounted on NFS. |
@mathuin what version of rubygems? Can you upgrade and try again? |
I ran Still doesn't work on 2.2.1:
For what it's worth, I'm hitting the same bug in Ruby itself for version 2.3.1:
|
Is it possible that building Ruby 2.2.1 with rbenv most likely uses a version of rubygems that's before the fix you added? |
I've confirmed that this fix is in ruby 2.2.0 and 2.3.1. (tho my installs might be tainted. I didn't look at the tarballs) |
OK. No, not the case for 2.2: https://github.com/ruby/ruby/blob/ruby_2_2/lib/rubygems/package.rb but it is fixed for 2.3: https://github.com/ruby/ruby/blob/ruby_2_3/lib/rubygems/package.rb Not sure why this wasn't backported for 2.2. Someone on rubygems core will have to comment on that. @indirect ? |
@zenspider it's up to the ruby core team what version of rubygems they bundle |
The right solution would be to fix whatever is broken in the underlying call to File.open() in Ruby, but I can't make a simple working example of the problem which makes it hard to report as a bug to the Ruby folks. |
@segiddins yes and no. Last I checked there were ruby core members on rubygems core. If that is not the case, there still needs to be a request from rubygems to ruby core to backport/update and I doubt that happened. |
@zenspider hsbt does all the backporting |
@zenspider We will not backport all rubygems update. Only regression, security issue, critical defects are backported. I try to backport this fix with 0a76e13 to next stable release aka 2.2.6 |
I addressed https://bugs.ruby-lang.org/issues/12579 |
Hi,
installing
minitest
,hoe
or whatever gems from seattlerb on a nfs partition fails, e.g.:This seems independent to rbenv (the example above does not use it).
You can see at minitest/minitest#435 all the tests and why I am opening this issue here.
I honestly do not know if the bug comes from minitest or rubygems.
Anyways, thank you very much.
The text was updated successfully, but these errors were encountered: