Your message dated Fri, 24 Oct 2008 00:33:22 -0400
with message-id <[EMAIL PROTECTED]>
and subject line close
has caused the Debian Bug report #430183,
regarding bugs.debian.org: some bugs don't get marked as resolved even after
fix enters unstable
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.)
--
430183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=430183
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: bugs.debian.org
Severity: normal
some bugs end up being listed as "outstanding" even after the version of
the package with the fix enters unstable. it should be expected that
the bug would be listed as "resolved" once the fixed version is
uploaded.
i think the problem is with the "Version:" tag. i think that what
happens is that for example if the [EMAIL PROTECTED] message
contains "Version: 0.6.0", but the next version to enter unstable is
0.6.1, the bug will not get relisted as "resolved" because
0.6.0 != 0.6.1, "fixed version != uploaded version". the resolved
test should check for "uploaded version >= fixed version".
mike
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.21-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
i haven't run into this issue in a while now, so i am going to
consider it solved. thanks!
--- End Message ---
