Hi, Thanks for your response.
But: how does pinning help? I don't want it to become permanently pinned. Only for the current action (dist-upgrade for instance) I want the package pinned... Suppose I do a dist-upgrade again a few days later, and the bug is fixed, then I want to include that package in the upgrade automatically, without worrying about pins. So I still think for the scenario where you indeed have critical bugs listed which make you decide to skip the upgrade of the package, the usability could be greatly improved. 2016-03-11 0:20 GMT+01:00 Francesco Poli <invernom...@paranoici.org>: > On Thu, 10 Mar 2016 19:22:36 +0100 Manuel Bilderbeek wrote: > > > Package: apt-listbugs > > Version: 0.1.17 > > Severity: normal > > > > Dear Maintainer, > > Hello Manuel, > thanks for using apt-listbugs! > > > > > I thought the purpose of this package was to warn you that there is a > critical > > bug in a package you're upgrading, so you can skip upgrading that > package. > > Indeed, it is. > > > But > > when you say "No" to the question "Do you want to continue" (or whatever > it > > is), the whole upgrade is aborted. > > Please take a look at the documentation (man page, README.Debian), but, > above all, use the on-line help: if you answer "n" to the "Are you sure > you want to install/upgrade the above packages?", you are saying that > you want to abort the installation/upgrade. > > If you answer "?", you will see the on-line help. > Among other possible answers, there are: > > p <pkg..> - pin pkgs (restart APT session to enable). > p - pin all the above pkgs (restart APT session to enable). > > These commands will pin the packages that you fear would introduce > troublesome bugs into your system (or all the buggy packages that > apt-listbugs has just listed). > > > I would expected the package with the bug to > > remain at the current version and the rest of the upgrade is just > performed as > > it should (as far as that's possible). > > The purpose of the package pinning is exactly to force the pinned > packages to remain at their current state (at their currently installed > version or at their current not-installed state). > > Unfortunately, after pins have been placed by apt-listbugs, your > package manager of choice (apt, or aptitude, or ...) won't re-read its > configuration files. As a consequence, after pinning some packages, you > have to answer "n" in order to abort the installation/upgrade and then > issue the package management command again (for instance "aptitude > safe-upgrade"). At that point the pins will be effective. > > > > > This makes the package a lot less usable as it could have been. > > I agree that it would great, if apt or aptitude could dynamically > re-read their configuration and change behavior on the fly, but this is > not the case, as far as I know. > > However, I am convinced that apt-listbugs is usable anyway. > I am therefore closing your bug report. > > Thanks for getting in touch, though. > 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 > -- Grtjs, Manuel PS: http://manuel.msxnet.org/
