Your message dated Fri, 2 Dec 2016 00:06:22 +0100
with message-id <>
and subject line Re: Bug#846384: apt-listbugs: allow to pin bugs manually
has caused the Debian Bug report #846384,
regarding apt-listbugs: allow to pin bugs manually
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

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Package: apt-listbugs
Version: 0.1.20
Severity: wishlist

Dear Maintainer,

I manually added:

merkaba:/etc/apt> cat preferences.d/apt-listbugs 
Explaination: Pinned manually
Explaination:   #845785: chromium crashes on certain websites
Package: chromium
Pin: version *
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.

I do hope that apt-listbugs will automatically remove it once the bug is
fixed, 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 didn´t see a way to do it after looking at the manpage of apt-listbugs


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-rc7-tp520-btrfstrim+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages apt-listbugs depends on:
ii  apt             1.4~beta1
ii  ruby            1:2.3.0+4
ii  ruby-debian     0.3.9+b6
ii  ruby-gettext    3.2.2-1
ii  ruby-soap4r     2.0.5-3
ii  ruby-unicode    0.4.4-2+b7
ii  ruby-xmlparser  0.7.3-3

Versions of packages apt-listbugs recommends:
ii  ruby-httpclient  2.7.1-1

Versions of packages apt-listbugs suggests:
ii  chromium [www-browser]     53.0.2785.143-1
ii  debianutils                4.8.1
ii  firefox [www-browser]      50.0-3
ii  firefox-esr [www-browser]  45.5.0esr-1
ii  konqueror [www-browser]    4:16.08.3-1
ii  lynx [www-browser]         2.8.9dev11-1
ii  qupzilla [www-browser]     1.8.9~dfsg1-3
ii  reportbug                  6.6.6
ii  w3m [www-browser]          0.5.3-33

-- no debconf information

--- End Message ---
--- Begin Message ---
Control: tags -1 - moreinfo

On Thu, 01 Dec 2016 00:13:03 +0100 Martin Steigerwald wrote:

> Am Mittwoch, 30. November 2016, 23:39:40 CET schrieb Francesco Poli:
> > 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.
> Hmmm, I understand. So for apt-listbugs I need to rely on the judgement of 
> the 
> Debian developer or maintainer or confront myself with lots of uncritical bug 
> reports.

Well, you have to rely on the package maintainer's judgment anyway.
You must rely on the assumption that the package maintainer will not:

 • incorrectly close the bug report, while the bug is still present
 • incorrectly set the version tracking info on the BTS
 • incorrectly reassign the bug report to a different package which is
   not responsible for the bug
 • ...

There is no way for apt-listbugs to distinguish between the cases where
the above actions are performed and the cases where the bug report is
handled reasonably by the package maintainer.

The same holds for the severity of a bug report.

Whenever you really think that a bug report is being handled
incorrectly, you may get in touch with the package maintainer and try
to persuade him/her that he/she should change his/her mind...

I am closing this bug report.
Thanks anyway for taking the time to write this feature request.


 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

Attachment: pgpuqrtDsKOhd.pgp
Description: PGP signature

--- End Message ---

Reply via email to