-
-
Notifications
You must be signed in to change notification settings - Fork 2k
No such file or directory @ rb_file_s_stat - MIT-LICENSE #3686
Comments
I guess this is probably a no, but could you share your Gemfile? I strongly suspect this has to do with a bad gem spec. |
As intended I can't upload the Gemfile but we found the issue (thanks @andremedeiros for your suggestion). The problem was one of our project (last update 11 months ago) which specifies, in its gemspec, some inexistant files: MIT-LICENSE, Rakefile,.. So I removed these useless informations and it works again. So it's maybe a regression from the previous version of bundler but it can be fixed easily. We also had some errors because of duplication in our gemspec. So we have just cleaned the gemspec and everything looks OK \o/. But, definitively, all these things were working yesterday and I don't see anything about this kind of change in the CHANGELOG. Any clue of why it happens now? |
I ran into this problem as well. In our case it was because of this gem: https://github.com/intercity/knife-solo which was declared as follow in our gemfile:
The file that could not be found was:
Which is in a submodule for that gem. I checked the repo for the submodule, and the file is still present there. I solves this problem by downgrading to |
We also add an error because name and email were set to It definitively looks like the gems used as a git dependency are now validated when we bundle. |
We definitely should add file existence checking to RubyGems, and in the meantime rescuing errno and explaining where it's coming from might make sense? |
@segiddins Yeah that sounds like a good fix! In that case you know what is causing the error :D It has taken me about 3 hours to figure out haha |
@segiddins yup could be awesome @jvanbaarsen I debugged it the ugly way: opening |
This should be fixed by #3708, which will be released shortly. |
@segiddins Thanks for the quick response/fix 👍 |
@segiddins: thank you 💯 |
@segiddins thank you 💯 |
What did you do?
I ran the command
/home/ubuntu/.rvm/gems/ruby-2.1.6@global/bin/bundle install --path=../vendor/bundle
We use Circle-CI and we update bundler each time we run the tests. The tests had no gem updates, just some view related code.
Tests were green yesterday and now they are all failing (a rebuild of master leads to a fail also).
What did you expect to happen?
I expected Bundler to install my gems as usual
What happened instead?
Instead, what actually happened was...
Error details
Environment
Bundler settings
The text was updated successfully, but these errors were encountered: