packaged gem binaries cannot be located
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rubygems-integration (Debian) |
New
|
Unknown
|
|||
rubygems-integration (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
As noted in https:/
Note that in 2015 bundler stated placing gem binaries in a directory named "exe", but although the error may differ slightly the cause is the same. https:/
This is a particular problem for gems that attempt to execute rake via this method. Since the ruby packages depend on the rake package, gems end up with a version of rake that they cannot run via .bin_dir/.bin_file.
And also, because of bug 1405108, installing a newer version of rake via "gem install" doesn't solve the problem.
description: | updated |
description: | updated |
Changed in rubygems-integration (Debian): | |
status: | Unknown → New |
Thank you for taking the time to report this bug and helping to make Ubuntu better.
Am I right in understanding that users will only bump into this when mixing ruby modules packaged in the archive and using "gem install"? If so, would Importance: Low be appropriate, since this shouldn't affect production and a workaround is available?