I just looked into this and it looks like the issue is being caused by a change from https://launchpadlibrarian.net/230675272/rubygems- integration_1.9_1.10.diff.gz. The issue is the change to `lib/rubygems/defaults/operating_system.rb` which aliases `default_specifications_dir` to `upstream_default_specifications_dir`. I'm not sure why the change was made but the `upstream_specifications_dir` is what is causing rubygems to look for the gem executables in `/usr/`. If you look at https://github.com/rubygems/rubygems/blob/2ed01b87152cb5ebec3ae934dca50a1609ea2ebd/lib/rubygems/specification.rb#L889, you can see that it uses `default_specifications_dir` to figure out where to load the gems from with `Gem::Specification.load` in `Gem::Specification.each_spec`.
As I said before I don't know the backstory for this change but changing that, or the default that's being set for `upstream_specifications_dir` seem to be the potential fixes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749226 Title: rubygems 2.7.5 fails to execute "bundle" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rubygems-integration/+bug/1749226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
