On Fri, 31 Jan 2014 13:09:36 +1300 Brendon Green wrote: > On 31 January 2014 12:04, Francesco Poli <invernom...@paranoici.org> wrote: [...] > > Anyway, please read > > http://bugs.debian.org/735116#10 > > for the suggested procedure to fix the issue. > > > Thank you. I found it sufficient to install ruby1.9.1/1.9.3.194-8.1+deb7u2 > from stable. I could not remove ruby1.8, as it is pulled in as a > dependency of apt-listbugs/0.1.8+deb7u1.
Well, I thought you wanted to upgrade to apt-listbugs/0.1.12 ... At least, that's what you stated in the original bug report. But anyway... > > Since apt-listbugs/0.1.8+deb7u1 does not appear to work with the > interpreter that was provided by ruby1.8/1.8.7.358-7.1+deb7u1, this is > perhaps a packaging bug that requires fixing? I tested apt-listbugs/0.1.8+deb7u1 in a stable chroot environment and it definitely seemed to work for me. If you are experiencing any difficulty with apt-listbugs/0.1.8+deb7u1 in an up-to-date *purely* stable system, please do not hesitate to report bugs. Otherwise, on a mixed testing/stable system, I suspect that the issue may be caused by the fact that ruby1.8/1.8.7.358-7.1+deb7u1 still Provides "ruby-interpreter" and may be selected as system-wide default Ruby interpreter, but ruby-debian/0.3.8+b2 (installed from testing) no longer supports ruby1.8 ... Antonio, any thoughts about this partial-upgrade scenario? Is there a way to avoid this? Maybe architecture-dependent Ruby libraries (such as ruby-debian) should really conflict with libruby1.8, as soon as they drop support for the obsolete ruby1.8 (as I initially suggested)? Any simpler solution? -- http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt New GnuPG key, see the transition document! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpsOY9pbumcg.pgp
Description: PGP signature
