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-3An interactive high-level object-o
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
