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; 27 Aug 2002 06:48:46 +0000
>From [EMAIL PROTECTED] Tue Aug 27 01:48:46 2002
Return-path: <[EMAIL PROTECTED]>
Received: from mr.tuwien.ac.at [128.130.2.10]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 17ja9d-0007XU-00; Tue, 27 Aug 2002 01:48:45 -0500
Received: from asgard.pte.at (lt132.ben.tuwien.ac.at [193.170.74.132])
by mr.tuwien.ac.at (8.12.0/8.12.0) with ESMTP id g7R6mhqe022097
for <[EMAIL PROTECTED]>; Tue, 27 Aug 2002 08:48:43 +0200 (MEST)
Received: from alfie by asgard.pte.at with local (Exim 3.35 #1 (Debian))
id 17ja9Q-0000LF-00
for <[EMAIL PROTECTED]>; Tue, 27 Aug 2002 08:48:32 +0200
Date: Tue, 27 Aug 2002 08:48:31 +0200
From: Gerfried Fuchs <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: bugs.debian.org: ChangeLog closes handling should be changed
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-Debbugs-CC: [EMAIL PROTECTED]
X-Reportbug-Version: 1.99.50
Mail-Copies-To: nobody
X-Editor: Vi Improved <http://www.vim.org/>
X-Signature-Color: cyan
X-Signature-Prg: sigd/0.9.1 (Perl) <http://alfie.ist.org/projects/sigd/>
X-Face: "`Q5\Ix+YG'{KDq<>5mcZL8Sp7$[L|%#^MSk'{Qpp"J8.<RP*P9<{{6$8%_~*:6c{)<;e:s
!:C2%IH-5:GT<,Sf3Xx}di,JDbDRH/;-eb{n`VSi*}-R2,[EMAIL PROTECTED]
{3w}E7d}+GN<|v=gDc;.c(xiy{Og_=2cy)T1J"Lu}y6Onsr
Sender: Gerfried Fuchs <[EMAIL PROTECTED]>
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)
Delivered-To: [EMAIL PROTECTED]
Package: bugs.debian.org
Severity: wishlist
Hi there!
With the addition of the testing distribution we have new problems:
Bugs are closed in unstable but flow more or less slowly (due to
dependency problems) into testing, but are due to the uploads into
unstable long closed.
What we need is a change here: Bugs should just be closed in unstable.
How to do this? They should be rather be tagged <sarge> than be closed
by an upload to unstable. Not unconditionally, of course. The version
of the bugreport should be compared with the version currently in
testing. Some sort of algorithm not too complex but able to handle most
of the cases shouldn't be too hard to do (yes, I volunteer to help
there).
Secondly, the testing scripts should be tweaked, too. They should
check the differences between the current changelog.Debian and the one
of the version that is going to flow in from unstable and close the
bugreports tagged <sarge>. Why only those? To avoid messages tagged
sid that where retagged sid because of problebugreports tagged <sarge>.
Why only those? To avoid messages that were retagged sid because of
problems that are still in effect in unstable.
Of course these sugguestions are not foolproof -- but the current
situation is neither. I sugguest these changes to make the BTS a better
place to track bugs. Current situation is far from optimal. We
currently state that there isn't a bug anymore just by closing it with
an upload to unstable. The fact is that is still is active in testing
and the BTS should live up to that fact.
I hope that these sugguestion will hit some open ears. I'm not really
sure if this is the best sugguestion, but it's the one idea I currently
came up with. Feel free to comment on it, I guess discussion on
debian-devel (*without* the copy to the BTS directly) would be a good
idea, I am thinking of scanning the responses and mail summaries into
the BTS to keep the bugreport current. If you like, Cc: me offlist if
really needed, I am not subcribed to debian-devel, but I'll watch the
discussion through both the webarchives and news:linux.debian.devel (and
answer from there -- need to finish my setup wrt/ that anyway ,).
Thanks, and I hope some of the inner circle like the idea.
Alfie
--
php ist an sich ne recht nutzlose sprache wenn da nicht soviele dinge so
einfach drin moeglich waeren
-- Getty in #debian.de
---------------------------------------
Received: (at 158434-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: 2
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]
