Your message dated Mon, 18 Jul 2005 12:44:58 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Version tracking implemented
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 2 Oct 1999 01:24:39 +0000
Received: (qmail 22672 invoked from network); 2 Oct 1999 01:24:32 -0000
Received: from snoopy.apana.org.au ([EMAIL PROTECTED])
by master.debian.org with SMTP; 2 Oct 1999 01:24:32 -0000
Received: by snoopy.apana.org.au (Postfix, from userid 1003)
id 121CC1774; Sat, 2 Oct 1999 11:25:23 +1000 (EST)
From: <[EMAIL PROTECTED]>
Subject: bugs.debian.org: closing bugs with version number
To: [EMAIL PROTECTED]
X-Mailer: bug 3.1.7
Reply-To: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]>
Date: Sat, 2 Oct 1999 11:25:23 +1000 (EST)
Package: bugs.debian.org
Version: N/A
severity: wishlist
I think is should be possible (if not mandatory) to supply a version
number when closing a bug report. Either this, or a special value to
indicate there was no bug in the first place (ie a mistake). The bug
would automatically apply to all versions between the version the
submitter used to the version when it was closed.
Perhaps some mechanism could be done to automate this when a package
is uploaded that closes the bugs off.
Why?
As that would allow part 2 of my wishlist:
I think that is should be possible to submit a request to the bug system
"are there any bugs in package X version Y? What version has my problem
been fixed in?". You could automate this, eg with a program "getbug"
that automatically loads the webbrowser of the users choice, and supplies
the version number of the currently installed package.
Currently, there can be big problems with not doing this.
1. if I submit a bug report for package X in stable, the maintainer
can't fix the version in stable, but rather has to fix the version in
unstable. However, if he/she closes the bug, other people will report
the same thing. If he/she doesn't close the bug, it looks like it hasn't
been fixed. Although you can mark a bug as being "fixed", I think this
is for NMUs. Even then, it is not possible to tell if the stable version
has been fixed or the unstable version. Even if there is some message
within the bug tracking system, it doesn't make the statistics look any
better.
2. if I want to investigate if a bug in package X, stable version, I
have to wade through all the bugs that are specific for the unstable
version and do not apply to stable.
3. other advantages I haven't yet thought of.
The only possible problem I see with this, is the stable version of the
package is released *after* several nonstable versions. The version
numbers of the packages which have been fixed will not be sequential.
I think this should be easy to solve.
I believe that this is very important now that bugs are archived, to
be able to get some idea for exactly what versions a specific bug
applies to.
-- System Information
Debian Release: 2.1
Kernel Version: Linux snoopy 2.2.12 #1 Thu Sep 2 10:09:15 EST 1999 i486 unknown
---------------------------------------
Received: (at 46434-done) by bugs.debian.org; 18 Jul 2005 11:45:00 +0000
>From [EMAIL PROTECTED] Mon Jul 18 04:45:00 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.metronet.co.uk [213.162.97.75]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1DuU3Q-0004f8-00; Mon, 18 Jul 2005 04:45:00 -0700
Received: from riva.pelham.vpn.ucam.org
(83-216-156-196.colinw664.adsl.metronet.co.uk [83.216.156.196])
by smtp.metronet.co.uk (MetroNet Mail) with ESMTP
id 578F2412E06; Mon, 18 Jul 2005 12:44:50 +0100 (BST)
Received: from cjwatson by riva.pelham.vpn.ucam.org with local (Exim 3.36 #1
(Debian))
id 1DuU3O-0000i8-00; Mon, 18 Jul 2005 12:44:58 +0100
Date: Mon, 18 Jul 2005 12:44:58 +0100
From: Colin Watson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: Version tracking implemented
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 3
Version tracking has been implemented on bugs.debian.org (see
debian-devel-announce). No doubt there will be some teething problems,
but it essentially finally closes these bugs. :-)
As far as #105776 goes, version-tracking-aware expiry isn't done yet,
but we won't be turning bug expiry back on again until it is.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
