On Thu, 7 May 2009 19:06:11 +0200 Michele Cascella wrote: > Hi,
Hi! > I had a similar issue but I did not look into it in details, I hope > the patch will solve it. I am pretty confident that my patch will significantly improve aptcleanup behavior. I hope your issue will be fixed as well. > > I have a question: > > Why does apt-listbugs use "Pin-Priority: 1000" to force the package > to remain to a particular version instead of just forbidding apt to > upgrade to a bugged version by using "Pin-Priority: 0" > > maybe the answer is very simple, but the "Pin-Priority: 0" behaviour > would seem a lot simpler to me and would not require a cron job to > clean the preferencies file. My answer is: because we want to unpin the package when the bug is fixed for the candidate version, not just when a new candidate version is available. Those two cases are distinct, since a new version may be uploaded to unstable (and possibly migrate to testing) without fixing the bug that you fear, or, on the flip side, the bug that you fear may be downgraded or reassigned to another package without any new upload. Hence, we *need* to periodically query the BTS, in order to decide whether to unpin a pinned package. Bye and many thanks for your interest in apt-listbugs. -- 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
pgpyMZG81VfLz.pgp
Description: PGP signature
