On Fri, 11 Mar 2016 23:02:15 +0100 Manuel Bilderbeek wrote: [...] > On 11-03-16 19:33, Francesco Poli wrote: > >> But: how does pinning help? I don't want it to become permanently pinned. > > > > Each pin is automatically removed by a daily cron job, as soon as the > > bug is fixed in the package version available for installation/upgrade. > > Hmm, I used to pin something, but then it always was permanent. How does > the automatic unpinning work?
It checks whether the bug is fixed (or downgraded below the configured severity threshold) in the version of the package that would get installed without the pin itself. If this is the case, the pin is actually removed and the installation/upgrade of the package becomes possible again. Please make sure that the cron daily job is run (if the system is up and running almost 24/7, then cron should suffice, otherwise, the installation of anacron is recommended). Please also make sure that the Internet link is working while the cron job is run. Finally, you have to remember to keep the package indexes up-to-date (with "apt update" or "aptitude update" or ...), in order for the unpinning to work correctly. [...] > Just one suggestion: add 'p' to the hints at possible answers to the > question "Are you sure you want to install/upgrade the above packages?". > Or simply behave as if 'p' was responded when people answer 'no', > because I would expect that to be the most likely answer that a > knowledgeable user would give. "p" would pin all the listed buggy packages, which is not necessarily what a user would always want to do (maybe one bug does not affect your architecture or your use case, and you prefer to upgrade the package despite the bug). > Or change the question to something like: "What would you like to do > now? a) abort the upgrade b) pin these packages to their current > versions until the bugs are solved c) just continue the upgrade. This is too long and detailed! It would be annoying for the users who already know how to use the program. On the other hand, the users who need to read explanations may always use the on-line help (by answering '?'). [...] > > Thanks for maintaining this useful package :) You're welcome! ;-) Bye. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpJ4nRH3YKBt.pgp
Description: PGP signature
