Bundler vs. yanked Gems

Hi everyone!

There was a mistake with gem dependencies, resulting in net-scp 1.0.6
being
yanked: https://github.com/net-ssh/net-ssh/issues/80

Unfortunately, my Bundler had seen 1.0.6 and put that in my
Gemfile.lock.
Bundler did not understand - “bundle update net-scp” just kept local
version 1.0.6.

After some fighting, I had to “gem search -rda net-scp” and pick another
version, then peg to that version in Gemfile, then “bundle update
net-scp”.
Even though net-scp was originally just a dependency, pulled in by fog.

There’s an issue for this:
https://github.com/carlhuda/bundler/issues/2277

But in the meantime, is there a better way to get bundler to forget it’s
seen a version?

Does not removing the Gemfile.lock resolve that issue? Recently I
installed mistakenly some newer gem and the bundler complaints
disappeared after I deleted Gemfile.lock.
v.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs