Your message dated Mon, 4 Jan 2010 22:39:18 +0100
with message-id <[email protected]>
and subject line Re: Bug#310514: reportbug: bts vs. upstream issues
has caused the Debian Bug report #310514,
regarding reportbug: bts vs. upstream issues
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.)
--
310514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=310514
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 3.8
Severity: normal
1. novice mode should clarify
novices are confused about whether bts reports are meant to be only
for debian issues or to partly replace (i.e. lightly filter
irrelevance) the upstream reporting systems. maintainers seem to
behave inconsistently on this point.
it's worth having novice mode explain this.
2. the bts should make it easy to cc: upstream
it would be great to have reportbug ask if the bug should be sent to
the bug reporting system for upstream. might be hard to implement for
some, but others are simply a lookup by package name and a cc: header.
i find it annoying to look up the upstream bug list (what address?
what's the etiquette? can non-subscribers post? how to get a cc:
automatically even for replies?) when it can be done automatically in
principle via a single interface: reportbug.
please cc: me on any replies.
thanks.
-- Package-specific info:
** /home/rasa/.reportbugrc:
reportbug_version "3.2"
mode standard
ui text
realname ""
email "[email protected]"
no-cc
header "X-Debbugs-CC: [email protected]"
smtphost master.debian.org
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.11--from-2.6.9-proc-config-and-menuconfig
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages reportbug depends on:
ii python2.3 2.3.5-3 An interactive high-level object-o
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,
thanks for your report.
On Mon, May 23, 2005 at 07:01:53PM -0700, [email protected] wrote:
> 1. novice mode should clarify
>
> novices are confused about whether bts reports are meant to be only
> for debian issues or to partly replace (i.e. lightly filter
> irrelevance) the upstream reporting systems. maintainers seem to
> behave inconsistently on this point.
>
> it's worth having novice mode explain this.
>From apt-cache show reportbug:
Description: reports bugs in the Debian distribution
reportbug is a tool designed to make the reporting of bugs in Debian
and derived distributions relatively painless.
from man reportbug:
reportbug is primarily designed to report bugs in the Debian
distribution; by default, it creates an email to the Debian bug
tracking system at [email protected] with information about the
bug you've found, and makes a carbon copy of the report for you as
well.
So I think there are plenty of description of what the tool is about
to do: report a bug to the Debian bug tracking system.
> 2. the bts should make it easy to cc: upstream
>
> it would be great to have reportbug ask if the bug should be sent to
> the bug reporting system for upstream. might be hard to implement for
> some, but others are simply a lookup by package name and a cc: header.
> i find it annoying to look up the upstream bug list (what address?
> what's the etiquette? can non-subscribers post? how to get a cc:
> automatically even for replies?) when it can be done automatically in
> principle via a single interface: reportbug.
No, this is a task for the maintainer: only he/she knows if a bug
applies to the debian package (because of patches introduced in it) or
applies upstream, and so it's his/her responsibility to let the
upstream know about that bug, forwarding accordingly (either via email
or on the upstream BTS) and then tag the bug as forwarded with the
link to look that up.
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
_______________________________________________
Reportbug-maint mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint
