On Fri, 9 May 2014 11:39:05 +0200 Christian Hofstaedtler wrote: > Package: apt-listbugs > Version: 0.1.13 > Severity: important > > Dear Francesco,
Hello Christian, thanks for your bug report, it's nice to read you. > > please add a failure catcher to apt-listbugs, so that in common > configurations apt doesn't break during an upgrade of ruby and > related packages. Could you elaborate a bit, please? Do you think that apt-listbugs should realize that it's failing to load the debian_version (binary) module and just exit with zero status without doing anything? The fact is that, if the user wants apt-listbugs to run before each installation or upgrade by APT in order to check whether the installation/upgrade is safe, apt-listbugs should stop APT whenever it is *not* able to perform its normal checks (running and querying the BTS, and so forth...). I think this is a feature, not a bug. At least as far as I am personally concerned, if I am about to upgrade, say, some 60 or 70 packages and apt-listbugs cannot run, I want to stop the upgrade immediately, examine the situation, fix the minimum needed to let apt-listbugs run correctly, and *only after that* proceed with the upgrade! I am of course open to any suggestion to improve apt-listbugs, as long as it takes this need into account. > As you know, the ruby wheezy->jessie upgrade path is already a > little bit fragile, so it'd be nice if apt-listbugs could catch > a missing ruby-debian extension. I think that the ruby upgrade path should be made less fragile. I don't think that compensating for a fragile language interpreter upgrade path should be the responsibility of each single application... > See #747406 for an example where apt-listbugs and ruby are already > upgraded, but ruby-debian is still the old version (due to missing > Breaks on ruby), and the user is left with a broken apt. As I have previously said in the past, I think that some Breaks would be highly useful to make the upgrade path more robust... Please consider addressing the issue from this side. I hope this line of reasoning makes sense to you. Thanks for the great work on Ruby packaging! -- 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
pgpRwHavG1umZ.pgp
Description: PGP signature
