Your message dated Mon, 21 Jul 2008 10:58:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#422085: bugscripts are executed, but content not put
in email
has caused the Debian Bug report #422085,
regarding reportbug-ng: should use /usr/share/bug/$package/*
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.)
--
422085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422085
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: reportbug-ng
Version: 0.2007.04.27
Severity: normal
Hi,
reportbug provides a way to control how bugs are reported on a
particular package, by adding files in /usr/share/bug/$package. However
reportbug-ng doesn't seem to use that information, which means that bugs
reported with it lack very important information. In particular,
without the output of /usr/share/bug/$package/script, many reports are
useless.
Thanks,
Julien
-- System Information:
Debian Release: lenny/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500,
'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-4-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages reportbug-ng depends on:
ii python 2.4.4-2 An interactive high-level object-o
ii python-central 0.5.13-0.1 register and build utility for Pyt
ii python-qt3 3.16-1.2 Qt3 bindings for Python
reportbug-ng recommends no packages.
-- no debconf information
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
This is not a bug of rng and not related to 422085:
* calling /usr/share/bug/texlive-doc-base 3>&1 aborts with an error
(getkey: command not found) when called in the console.
If you feel this is a bug of rng, please open a new report specific to
this problem and not to rng not using the scripts at all.
* xserver-xorg: the output of the script is too long to handle so rng
added the following text to the mail (you should have seen that, Sune):
-8<---8<---8<---8<---8<---8<---8<---8<---8<--
Please attach the file:
/tmp/reportbug-ng-xserver-xorg-oob9Xu.txt
to the mail. I'd do it myself if the output wasn't too long to handle.
Thank you!
->8--->8--->8--->8--->8--->8--->8--->8--->8--"
as you can see rng already gathered the info and even put in in a file,
all the user has to do is to attach this file to the mail.
* mdadm: not tested, since not installed, but I assume its one of the
above problems.
Try udev, it also comes with a script whose output isn't > 80kb big and
it works fine, rng attaches the output automatically and the user has
nothing to do.
The "file too long" problem isn't rng's fault but a limitation of the
shell which can't execute commands of unlimited length. Rng detects such
cases where calling the MUA failed and puts the output in a file and
asks the user kindly to attach it.
Sune Vuorela wrote:
reopen 422085
thanks
Hi!
I just tried using reportbug-ng to report bugs against packages like texlive-
doc-base, xserver-xorg and mdadm. (what's common for these 3 packages is that
thay have bug scripts)
And the result is:
I see a terminal pop up briefly with a lot of text scrolling over and a line
added to the email with the following:
--- Output from package bug script ---
but no actual output from bug script.
I use kmail as the email client - and running reportbug-ng with -l info
doesn't reveal any info about why it isn't adding the bug script output.
/Sune
--
Bastian Venthur http://venthur.de
Debian Developer venthur at debian org
--- End Message ---
