Bug#991015: Acknowledgement (cannot execute due to incorrect shebang line)
On Fri, Jul 16, 2021 at 11:11:44AM -0300, Antonio Terceiro wrote: > On Tue, Jul 13, 2021 at 12:48:49PM +0300, Adrian Bunk wrote: > > On Mon, Jul 12, 2021 at 09:10:15PM -0400, Ryan Kavanagh wrote: > > > This bug seems to be, in part, due to a potentially (?) broken ruby > > > upgrade behaviour. I've been running unstable on this laptop for ~6 > > > years, but still had > > > > > > ii ruby2.1 [ruby-interpreter] 2.1.5-4 > > > ii ruby2.2 [ruby-interpreter] 2.2.4-1 > > > > > > installed as my only ruby interpreters. These are no longer available in > > > unstable, and ruby2.1 was last available in: > > > > > > ruby2.1| 2.1.5-2+deb8u3 | oldoldstable | source, amd64, armel, armhf, > > > i386 > > > > > > Will users upgrading from buster to bullseye will encounter a similar > > > issue if they've dist-upgraded from jessie to stretch to buster? > > > > The problem is the following in the dependencies: > > Depends: ruby | ruby-interpreter, ... > > > > The /usr/bin/ruby symlink is in the ruby package, > > the alternative dependency ruby-interpreter is > > therefore wrong. > > We noticed that a while ago, and ruby2.2 was the last of the rubyX.Y > packages to actually provide `ruby-interpreter`. Thanks for this information. > At this point, there are 900+ packages that still depend on `ruby | > ruby-interpreter`, so this isn't something we can easily fix. I will > submit a lintian check for this to get eventually fixed, but it will > take a while. >... ~ 90% of these seem to be Ruby modules, it is not obvious to me that "ruby | ruby-interpreter" is even a bug for these. A bookworm MBF for the small part that are non-interpreter packages might be an option? cu Adrian
Bug#991015: Acknowledgement (cannot execute due to incorrect shebang line)
On Fri, Jul 16, 2021 at 06:37:52PM +0530, Pirate Praveen wrote: > See https://lists.debian.org/debian-ruby/2021/07/msg2.html > Since it affects only very old releases, reducing severity. I think that Antonio's claim that this should only be a problem on older systems, I would even say only in already non-supported Debian releases. is wrong, at least regarding the second clause. This bug affects me on Debian unstable, and will likely affect anybody who has been upgrading between stable releases and who has not installed a more recent version of ruby. It's too late to fix this for bullseye, so I think it would be worthwhile to add a release note so that users are aware of the potential issue when upgrading to the next stable release. Ryan -- |)|/ Ryan Kavanagh | 4E46 9519 ED67 7734 268F |\|\ https://rak.ac | BD95 8F7B F8FC 4A11 C97A signature.asc Description: PGP signature
Bug#991015: Acknowledgement (cannot execute due to incorrect shebang line)
Control: severity -1 important On Mon, 12 Jul 2021 21:10:15 -0400 Ryan Kavanagh wrote: > This bug seems to be, in part, due to a potentially (?) broken ruby > upgrade behaviour. I've been running unstable on this laptop for ~6 > years, but still had > > ii ruby2.1 [ruby-interpreter] 2.1.5-4 > ii ruby2.2 [ruby-interpreter] 2.2.4-1 > > installed as my only ruby interpreters. These are no longer available in > unstable, and ruby2.1 was last available in: > > ruby2.1| 2.1.5-2+deb8u3 | oldoldstable | source, amd64, armel, armhf, i386 > > Will users upgrading from buster to bullseye will encounter a similar > issue if they've dist-upgraded from jessie to stretch to buster? rubyX.Y no longer provides ruby-interpreter from ruby2.3 See https://lists.debian.org/debian-ruby/2021/07/msg2.html Since it affects only very old releases, reducing severity. -- Sent from my p≡p for Android.
Bug#991015: Acknowledgement (cannot execute due to incorrect shebang line)
On Tue, Jul 13, 2021 at 12:48:49PM +0300, Adrian Bunk wrote: > On Mon, Jul 12, 2021 at 09:10:15PM -0400, Ryan Kavanagh wrote: > > This bug seems to be, in part, due to a potentially (?) broken ruby > > upgrade behaviour. I've been running unstable on this laptop for ~6 > > years, but still had > > > > ii ruby2.1 [ruby-interpreter] 2.1.5-4 > > ii ruby2.2 [ruby-interpreter] 2.2.4-1 > > > > installed as my only ruby interpreters. These are no longer available in > > unstable, and ruby2.1 was last available in: > > > > ruby2.1| 2.1.5-2+deb8u3 | oldoldstable | source, amd64, armel, armhf, > > i386 > > > > Will users upgrading from buster to bullseye will encounter a similar > > issue if they've dist-upgraded from jessie to stretch to buster? > > The problem is the following in the dependencies: > Depends: ruby | ruby-interpreter, ... > > The /usr/bin/ruby symlink is in the ruby package, > the alternative dependency ruby-interpreter is > therefore wrong. We noticed that a while ago, and ruby2.2 was the last of the rubyX.Y packages to actually provide `ruby-interpreter`. At this point, there are 900+ packages that still depend on `ruby | ruby-interpreter`, so this isn't something we can easily fix. I will submit a lintian check for this to get eventually fixed, but it will take a while. To workaround this, please install `ruby` and remove `ruby2.1`. and `ruby2.2`. signature.asc Description: PGP signature
Bug#991015: Acknowledgement (cannot execute due to incorrect shebang line)
On Mon, Jul 12, 2021 at 09:10:15PM -0400, Ryan Kavanagh wrote: > This bug seems to be, in part, due to a potentially (?) broken ruby > upgrade behaviour. I've been running unstable on this laptop for ~6 > years, but still had > > ii ruby2.1 [ruby-interpreter] 2.1.5-4 > ii ruby2.2 [ruby-interpreter] 2.2.4-1 > > installed as my only ruby interpreters. These are no longer available in > unstable, and ruby2.1 was last available in: > > ruby2.1| 2.1.5-2+deb8u3 | oldoldstable | source, amd64, armel, armhf, i386 > > Will users upgrading from buster to bullseye will encounter a similar > issue if they've dist-upgraded from jessie to stretch to buster? The problem is the following in the dependencies: Depends: ruby | ruby-interpreter, ... The /usr/bin/ruby symlink is in the ruby package, the alternative dependency ruby-interpreter is therefore wrong. cu Adrian
Bug#991015: Acknowledgement (cannot execute due to incorrect shebang line)
This bug seems to be, in part, due to a potentially (?) broken ruby upgrade behaviour. I've been running unstable on this laptop for ~6 years, but still had ii ruby2.1 [ruby-interpreter] 2.1.5-4 ii ruby2.2 [ruby-interpreter] 2.2.4-1 installed as my only ruby interpreters. These are no longer available in unstable, and ruby2.1 was last available in: ruby2.1| 2.1.5-2+deb8u3 | oldoldstable | source, amd64, armel, armhf, i386 Will users upgrading from buster to bullseye will encounter a similar issue if they've dist-upgraded from jessie to stretch to buster? -- |)|/ Ryan Kavanagh | 4E46 9519 ED67 7734 268F |\|\ https://rak.ac | BD95 8F7B F8FC 4A11 C97A signature.asc Description: PGP signature
