Your message dated Fri, 11 Mar 2016 00:20:03 +0100
with message-id <[email protected]>
and subject line Re: Bug#817832: apt-listbugs: Aborts complete upgrade instead
of skipping package with bug
has caused the Debian Bug report #817832,
regarding apt-listbugs: Aborts complete upgrade instead of skipping package
with bug
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
817832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817832
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: apt-listbugs
Version: 0.1.17
Severity: normal
Dear Maintainer,
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. But
when you say "No" to the question "Do you want to continue" (or whatever it
is), the whole upgrade is aborted. 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).
This makes the package a lot less usable as it could have been.
-- System Information:
Debian Release: stretch/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages apt-listbugs depends on:
ii apt 1.2.6
ii ruby 1:2.3.0+1
ii ruby-debian 0.3.9+b5
ii ruby-gettext 3.1.7-1
ii ruby-soap4r 2.0.5-3
ii ruby-unicode 0.4.4-2+b6
ii ruby-xmlparser 0.7.3-1+b3
ii ruby2.1 [ruby-interpreter] 2.1.5-4
ii ruby2.2 [ruby-interpreter] 2.2.4-1
ii ruby2.3 [ruby-interpreter] 2.3.0-4
Versions of packages apt-listbugs recommends:
ii ruby-httpclient 2.7.1-1
Versions of packages apt-listbugs suggests:
ii chromium [www-browser] 49.0.2623.75-2
ii debianutils 4.7
ii iceweasel [www-browser] 44.0.2-1
ii reportbug 6.6.6
ii w3m [www-browser] 0.5.3-27
-- no debconf information
--- End Message ---
--- Begin Message ---
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
pgpDEo0vjLTKt.pgp
Description: PGP signature
--- End Message ---
