Your message dated Mon, 28 Mar 2005 14:24:06 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#301739: All e-mails to <[EMAIL PROTECTED]> should be
forwarded to the upstream -devel list or maintainer
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; 28 Mar 2005 01:12:43 +0000
>From [EMAIL PROTECTED] Sun Mar 27 17:12:43 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp-send.myrealbox.com [192.108.102.143]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DFio7-0004KB-00; Sun, 27 Mar 2005 17:12:43 -0800
Received: from jspi [69.158.179.116] by myrealbox.com
with NetMail ModWeb Module; Sun, 27 Mar 2005 18:12:43 -0700
Subject: All e-mails to <[EMAIL PROTECTED]> should be forwarded to the upstream
-devel list or maintainer
From: "Jason Spiro" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: Sun, 27 Mar 2005 18:12:43 -0700
X-Mailer: NetMail ModWeb Module
X-Sender: jspi
MIME-Version: 1.0
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: debbugs
Severity: normal
(This cannot be implemented before bug 34071 is dealt with, but this is a s=
eparate issue.)
AFAIK, when a bug is submitted to [EMAIL PROTECTED], the debbugs serve=
r sends the package maintainer a copy of the bug report, and the package =
maintainer soon sends a copy to the upstream -devel mailing list, e.g. ba=
sh-devel or xemacs-devel, or the upstream maintainer.
However, when someone sends in extra information on an existing bug, I doub=
t this info always makes its way upstream.
Once a "bug subscription" feature (bug #34071) is added to debbugs, it woul=
d help get bugs fixed faster if the upstream -devel list or maintainer we=
re automatically subscribed to get any additional info on the bug that pe=
ople come up with. This would require that the package tracking system ke=
ep track of the e-mail address of the upstream -devel list for all packag=
es that have such a list.
(It would also be useful if the BTS recognized a special set of aliases, sa=
y upstream-gw-<pkg_name>@bugs.debian.org, and if package maintainers were=
able to subscribe the upstream-gw alias for their packages to the releva=
nt -devel lists. This way, the BTS could forward info even to lists that =
only allow list subscribers to post messages. Perhaps it could even store=
replies from -devel lists back into the relevant bug page at bugs.debian=
.org by looking at the X-Debian-PR-Message header field.)
Once upstream -devel lists or maintainers automatically get copies of addit=
ionalinfo on upstream bugs, communication will be improved and some upstr=
eam bugs will get fixed sooner.
---------------------------------------
Received: (at 301739-done) by bugs.debian.org; 28 Mar 2005 13:24:12 +0000
>From [EMAIL PROTECTED] Mon Mar 28 05:24:12 2005
Return-path: <[EMAIL PROTECTED]>
Received: from chiark.greenend.org.uk [193.201.200.170] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DFuE0-00055z-00; Mon, 28 Mar 2005 05:24:12 -0800
Received: from [192.168.124.112] (helo=riva.lab.dotat.at)
by chiark.greenend.org.uk (Debian Exim 3.35 #1) with esmtp
(return-path [EMAIL PROTECTED])
id 1DFuDx-0000d7-00
for [EMAIL PROTECTED]; Mon, 28 Mar 2005 14:24:10 +0100
Received: from cjwatson by riva.lab.dotat.at with local (Exim 3.35 #1 (Debian))
for [EMAIL PROTECTED]
id 1DFuDu-0007NJ-00; Mon, 28 Mar 2005 14:24:06 +0100
Date: Mon, 28 Mar 2005 14:24:06 +0100
From: Colin Watson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#301739: All e-mails to <[EMAIL PROTECTED]> should be forwarded
to the upstream -devel list or maintainer
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.3.28i
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-Status: No, hits=-5.8 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER,
OPT_IN autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
On Sun, Mar 27, 2005 at 06:12:43PM -0700, Jason Spiro wrote:
> Package: debbugs
> Severity: normal
>
> (This cannot be implemented before bug 34071 is dealt with, but this
> is a separate issue.)
>
> AFAIK, when a bug is submitted to [EMAIL PROTECTED], the debbugs
> server sends the package maintainer a copy of the bug report, and the
> package maintainer soon sends a copy to the upstream -devel mailing
> list, e.g. bash-devel or xemacs-devel, or the upstream maintainer.
>
> However, when someone sends in extra information on an existing bug, I
> doubt this info always makes its way upstream.
>
> Once a "bug subscription" feature (bug #34071) is added to debbugs, it
> would help get bugs fixed faster if the upstream -devel list or
> maintainer were automatically subscribed to get any additional info on
> the bug that people come up with.
Absolutely not. This would cause many upstreams to simply ignore Debian
bugs; it's not uncommon for bugs to be unique to the Debian package, and
to have nothing to do with upstream.
The package tracking system (http://packages.qa.debian.org/) already
provides the facility to subscribe to all bugs on a package. You are
requesting this to be opt-out rather than opt-in, which I do not think
is appropriate.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
