Your message dated Wed, 15 Jan 2014 16:31:46 +0100
with message-id <[email protected]>
and subject line Re: Bug#734525: apt-listbugs: breaks when /usr/bin/ruby is
ruby1.8
has caused the Debian Bug report #734525,
regarding apt-listbugs: breaks when /usr/bin/ruby is ruby1.8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
734525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734525
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: apt-listbugs
Version: 0.1.12
Severity: normal
Dear Maintainer,
I was updating from stable to testing to unstable when apt-listchanges
broke. It depends on ruby (any version) and I only had 1.8
installed). But ruby-debian (on which it depends) now only depends on
(and works with) libruby(1.9.1|2.0). Which results in apt-listbugs
crashing when it tries to `require 'debian'`. And thus aptitude no
longer works.
This fixed it:
$ dpkg --remove apt-listbugs
$ aptitude install ruby1.9.1
$ aptitude install apt-listbugs
- Felix
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages apt-listbugs depends on:
ii apt 0.9.14.2
ii ruby 1:1.9.3
ii ruby-debian 0.3.8+b2
ii ruby-gettext 3.0.3-1
ii ruby-httpclient 2.3.3-2
ii ruby-soap4r 2.0.5-2
ii ruby-xmlparser 0.7.2-2
ii ruby1.8 [ruby-interpreter] 1.8.7.358-9
ii ruby1.9.1 [ruby-interpreter] 1.9.3.484-1
ii ruby2.0 [ruby-interpreter] 2.0.0.353-1
apt-listbugs recommends no packages.
Versions of packages apt-listbugs suggests:
ii chromium [www-browser] 31.0.1650.63-1
ii debianutils 4.4
ii iceweasel [www-browser] 24.2.0esr-1
ii reportbug 6.4.4
ii w3m [www-browser] 0.5.3-15
-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, Jan 09, 2014 at 12:11:43AM +0100, Francesco Poli wrote:
> Control: reassign -1 ruby1.8 1.8.7.358-10
>
> On Wed, 08 Jan 2014 03:51:26 +0100 Felix C. Stegerman wrote:
>
> [...]
> > > On 2014-01-08 00:06, Francesco Poli wrote:
> [...]
> > >> This seems to be exactly the same issue that has already been
> > >> reported as bug #734233: http://bugs.debian.org/734233
> > >
> > >> I am therefore merging the two reports.
> [...]
> > It seems to be fixed in ruby1.8 now (http://bugs.debian.org/734319).
>
> Thanks for the heads up, Felix.
> Yes, it seems the upgrade of ruby1.8 fixes the issue.
>
> Mmmh, no wait, ruby1.8 no longer provides ruby-interpreter (and this is
> good, since now packages depending on "ruby | ruby-interpreter" will
> pull in ruby1.9.1), but /usr/bin/ruby1.8 still seems to be a
> possible alternative for /usr/bin/ruby ...
>
> I am under the impression that this means it's still possible to find
> oneself with a broken ruby-debian: if root manually installed ruby1.8
> and ruby1.9.1 and manually set /usr/bin/ruby1.8 as the alternative
> for /usr/bin/ruby, I think the upgrade
> ruby1.8 1.8.7.358-9 → 1.8.7.358-10
> won't alter the alternatives and apt-listbugs will fail to run.
>
> Antonio, please correct me if I am wrong.
> Is there a way to declare that /usr/bin/ruby1.8 is no longer a valid
> alternative for /usr/bin/ruby ?
> Should the ruby1.8.postinst run
> update-alternatives --remove ruby /usr/bin/ruby1.8
> or something like that?
The problem is that this sollution will not help with upgrades from
wheezy, sinde there will be no ruby1.8 to upgrade to.
My current idea on this is to make `ruby` conflict with `ruby1.8`.
> I am reassigning this bug report to ruby1.8, but I am not yet closing or
> merging it, since there is this last doubt to be clarified.
>
> Antonio, please let me know.
I don't think the fix for this issue belongs to ruby1.8 source package,
so maybe there is no point in keeping this bug open (I'm closing it).
--
Antonio Terceiro <[email protected]>
signature.asc
Description: Digital signature
--- End Message ---
