Control: tags -1 + moreinfo
On Wed, 30 Nov 2016 21:31:41 +0100 Martin Steigerwald wrote:
[...]
> Dear Maintainer,
Hello Martin,
thanks for your bug report.
>
> I manually added:
>
> merkaba:/etc/apt> cat preferences.d/apt-listbugs
> Explaination: Pinned manually
> Explaination: #845785: chromium crashes on certain websites
This is a typo (it should be "Explanation")...
> Package: chromium
> Pin: version *
> Pin-Priority: -30000
This would prevent the *installation* of chromium, if your system did
not have it already installed.
On the other hand, if you have version x.y-z installed on your system
and you want to prevent the upgrade to newer versions, you should write:
Package: chromium
Pin: version x.y-z
Pin-Priority: 30000
>
> cause Michael downgraded the severity of that bug to "normal" and thus from
> what I understand apt-listbug would not protect my system from upgrading to
> the newer broken chromium version in unstable.
Well, what will happen is that apt-listbugs will remove the pin, since
the bug that you fear was downgraded to a severity ("normal") that
apt-listbugs ignores.
To avoid the automatic pin removal, you have two possible strategies
(that I can think of):
(a) you may include "normal" in the list of severities to be considered
by apt-listbugs (see option AptListbugs::Severities
in /etc/apt/apt.conf.d/10apt-listbugs ; this option may for instance be
set to "critical,grave,serious,important,normal")
(b) you may create a manual pin outside of apt-listbugs jurisdiction
(without Explanation fields and in files other
than /etc/apt/preferences.d/apt-listbugs ; for instance in
/etc/apt/preferences.d/chromium-pin )
If you follow strategy (a), apt-listbugs will warn you about all normal
bugs, and there will probably be several of them for each package to be
installed/upgraded. Maybe a bit inconvenient...
If instead you follow strategy (b), apt-listbugs will never touch your
pin and you will have to manage it by hand (that is to say, you'll have
to keep an eye on the bug and decide when the pin should be manually
removed).
>
> I do hope that apt-listbugs will automatically remove it once the bug is
> fixed,
I am afraid apt-listbugs will remove the pin on the next run of its
cron daily job...
> but I also would like a way to manually pin a bug from command line
> in order to avoid having to make up an entry like above myself.
I think this would be of very little usefulness, because of the above
explained facts.
If you configure apt-listbugs to also care about bugs of "normal"
severity, everything will work as usual, with the only downside that
you will see lots of bugs at each installation/upgrade attempt.
If you instead decide to manage the pin by hand, you may as well create
it by hand... After all, it's not that hard, once you understand the
meaning of the fields!
>
> I didn´t see a way to do it after looking at the manpage of apt-listbugs
> tough.
Indeed, apt-listbugs is not intended to be an on-demand package pin
generator. It will generate pins for packages that would introduce
bugs (of one of the configured severities) into your system.
I hope this clarifies.
Please let me know.
--
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
pgp1y_Y_1G524.pgp
Description: PGP signature
