Thank you for the update. I'll mark this bug as Invalid for action in
Ubuntu itself then.
** Changed in: rubygems-integration (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
This is good to close and no changes are needed in Ubuntu. It wasn't
backported, but that's no reason to address this in Ubuntu. Current
version works as expected and the fix is as simple as running "gem
update --system".
--
You received this bug notification because you are a member of Ubuntu
Bu
Are there still changes needed in Ubuntu to close this bug? Sorry for
asking, I'm not at all familiar with rubygems and bundler, and the
rubygems-integration package versions available in Ubuntu do not seem to
match what was mentioned in this bug so far:
$ rmadison rubygems-integration
rubygems-i
This has been resolved in rubygems & bundler.
Using Bundler 1.16.2 (that's the current release as of today, released
in May'18) I don't see the error anymore. The original issue in rubygems
has been closed too & I think it's safe to close this bug report.
Jacob thanks for your time looking into t
I suspect this one: https://github.com/rubygems/rubygems/pull/2169/files
#diff-3d2f1e4ce4bf8e4f701d1706efb9f9a1L385
I have included more details on Github issue:
https://github.com/rubygems/rubygems/issues/2180
** Bug watch added: github.com/rubygems/rubygems/issues #2180
https://github.com/ru
I would also love to know what commit you think is causing the issue.
I've been trying to dig through a bit and haven't had any luck tracking
down the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I just realized I misspoke slightly in the above. All places that I said
`upstream_default_specifications_dir` should actually be
`upstream_default_dir`.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Hi Rob,
Sorry for that duplicate comment. If you need any help with anything
just let me know. I'd be happy to help put together something for a
rubygems PR if need be.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
I think I just managed to narrow down the problem to a specific commit
in rubygems that introduced the regression. I don't know how to exactly
fix it, but I will keep you updated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Thanks very much Jacob,
I will try to look deeper into rubygems codebase and will let you know
how it goes.
--
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 exec
I just realized I misspoke slightly in the above. All places that I said
`upstream_default_specifications_dir` should actually be
`upstream_default_dir`.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rubygems-integration (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749226
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_defaul
13 matches
Mail list logo
