Package: apt-listbugs
Version: 0.0.82
Severity: minor

I am currently in the middle of a sid-to-sid upgrade which will upgrade ntp
from 1:4.2.4p4+dfsg-1 to 1:4.2.4p4+dfsg-2.  Apt-listbugs says #446891 is
"done in the latest versions" but when I look at the bug log, I see that
the latest version (1:4.2.4p4+dfsg-2) is red in the version graph (ie.
that version does *not* fix the bug, according to the BTS).

Note that the following are all true of that bug report:
  - the report has been -done'd
  - the version 4.2.4p4+dfsg-1 is marked as "fixed"
  - the same version (1:4.2.4p4+dfsg-1) is also marked as "found"
(This list is in the chronological order of events.)
Presumably either apt-listbugs or whatever BTS interface it uses
misreads this rather odd collection of facts.

(The bug probably should have been closed with the -2 upload, but it
hasn't been, so it doesn't matter for my purpose here.)

For the record, the last event in that bug report's logs that I can
currently see is the mail

  From: Wladimir Mutel <[EMAIL PROTECTED]>
  Date: Sun, 21 Oct 2007 09:09:59 +0300

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.23.1-ibid (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages apt-listbugs depends on:
ii  apt                          0.7.6       Advanced front-end for dpkg
ii  libdpkg-ruby1.8              0.3.2       modules/classes for dpkg on ruby 1
ii  libhttp-access2-ruby1.8      2.0.6-3     HTTP accessing library for ruby
ii  libintl-gettext-ruby1.8      0.11-10     Gettext wrapper for Ruby 1.8
ii  libruby1.8 [libzlib-ruby1.8] 1.8.6.111-1 Libraries necessary to run Ruby 1.
ii  libxml-parser-ruby1.8        0.6.8-2     Interface of expat for the scripti
ii  ruby                         1.8.2-1     An interpreter of object-oriented 

apt-listbugs recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to