On Sat, 11 Jul 2009 20:09:18 +0200 max wrote: [...] > Hi
Hi! > > the command > > # apt-listbugs list apt-listbug > > lists > > Reading package fields... Done > Reading package status... Done > Retrieving bug reports... Done > Parsing Found/Fixed information... Done > > and the return value is 0, ie. Success You are right, I can confirm that apt-listbugs behaves like this (I've just checked with version 0.1.0, currently in unstable and testing). > > but there is no apt-listbug package and so the listing should be > something like: > > ... > ... > WARNING: There is no maintainer for apt-listbug > WARNING: There is no record of the apt-listbug package > > > and the return value should not be 0. Well, I am not sure that this proposed new behavior (i.e.: exit with non-zero status when a package does not exist) is a good idea. For instance, when you pin a package because of some bug, the pinning is written to /etc/apt/preferences; a cron.daily job checks the package to see if it still has the bug (see /etc/cron.daily/apt-listbugs, which uses /usr/share/apt-listbugs/aptcleanup) and drops the pinning when the package no longer has the bug. Suppose you're running Debian unstable (or Debian testing) and you pin a buggy package; then you shut the system down for some time; when you boot it up again, the package could have been removed from unstable (and testing); if the package never made it into a stable release, the BTS web interface says that there is no maintainer and no record for the package. Now, what would happen if apt-listbugs exited with non-zero status? The cron.daily job would try to run /usr/share/apt-listbugs/aptcleanup, which would exit with error, and hence the pinnings in /etc/apt/preferences would not be properly cleaned up... As a consequence, I am under the impression that the behavior of apt-listbugs on non-existent packages is *intended*, rather than a *bug*. Ryan (maintainer of apt-listbugs), do you agree with my analysis? -- New location for my website! Update your bookmarks! http://www.inventati.org/frx ..................................................... Francesco Poli . GnuPG key fpr == C979 F34B 27CE 5CD8 DC12 31B5 78F4 279B DD6D FCF4
pgpeFyoLUsafD.pgp
Description: PGP signature
