On 26/08/11 00:27, Sandro Tosi wrote:
On Thu, May 6, 2010 at 10:16, Torquil Macdonald Sørensen
<torq...@gmail.com> wrote:
Package: reportbug
Version: 4.12.1
Severity: normal
I'm not sure how I would make a transcript, but believe that I do not do
just run reportbug --ui=text in a terminal and cut&paste the complete output.
Ok thanks. I guess I don't need the --ui=text since I get the text frontend by
default. I have included the output below.
anything out of the ordinary. SInce you mention MTA, I always make a
point about removing any mail server packages, e.g. exim-packages and so
on, since I don't need those types of software since e.g. Icedove
communicates with SMTP servers without the help any such software.
I don't know how reportbug does this, but it does manage to send bugreports.
Another check: are those files old? I.e: if you report a bug now, does
reportbug leave an empty .bug file behind on /var/tmp ?
Yup, reportbug still produces those empty files. I just reported a minor bug on
the guitarix package, resulting in a new empty file /var/tmp/guitarix.bug.
I "monitored" /var/tmp while writing the bug report. After having written the
bug report and chosen to save the text (I use EDITOR=nano), the empty file in
/var/tmp/ had not yet been created. Thus it is created at the last moment when I
select to send the report (by selecting Y from the list of choices).
Here is the transcript of the reportbug session:
tmac@asus:~$ reportbug guitarix
*** Welcome to reportbug. Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of the
submitter).
Detected character set: UTF-8
Please change your locale if this is incorrect.
Using '"Torquil Macdonald Sørensen" <torq...@gmail.com>' as your from address.
Getting status for guitarix...
Checking for newer versions at packages.debian.org, incoming.debian.org and
http://ftp-master.debian.org/new.html
Will send report to Debian (per lsb_release).
Querying Debian BTS for reports on guitarix (source)...
No bug reports found.
Maintainer for guitarix is 'Roland Stigge <sti...@antcom.de>'.
Looking up dependencies of guitarix...
Briefly describe the problem (max. 100 characters allowed). This will be the bug
email subject, so keep the summary as concise as possible, for example: "fails
to send email" or "does not
start with -q option specified" (enter Ctrl+c to exit).
> Invisible scroll bar
Rewriting subject to 'guitarix: Invisible scroll bar'
Enter any additional addresses this report should be sent to; press ENTER after
each address. Press ENTER on a blank line to continue.
>
How would you rate the severity of this problem or report?
1 critical makes unrelated software on the system (or the whole system)
break, or causes serious data loss, or introduces a security hole on systems
where you install the package.
2 grave makes the package in question unusable by most or all users,
or causes data loss, or introduces a security hole allowing access to the
accounts of users who use the package.
3 serious is a severe violation of Debian policy (that is, the problem
is a violation of a 'must' or 'required' directive); may or may not affect the
usability of the package. Note
that non-severe policy violations may be 'normal,' 'minor,'
or 'wishlist' bugs. (Package maintainers may also designate other bugs as
'serious' and thus release-critical;
however, end users should not do so.). For the canonical list
of issues worthing a serious severity you can refer to this webpage:
http://release.debian.org/wheezy/rc_policy.txt .
4 important a bug which has a major effect on the usability of a package,
without rendering it completely unusable to everyone.
5 does-not-build a bug that stops the package from being built from source.
(This is a 'virtual severity'.)
6 normal a bug that does not undermine the usability of the whole
package; for example, a problem with a particular option or menu item.
7 minor things like spelling mistakes and other minor cosmetic errors
that do not affect the core functionality of the package.
8 wishlist suggestions and requests for new features.
Please select a severity level: [normal] 7
Do any of the following apply to this report?
1 d-i This bug is relevant to the development of debian-installer.
2 experimental This bug only applies to the experimental branch of Debian.
3 ipv6 This bug affects support for Internet Protocol version 6.
4 l10n This bug reports a localization/internationalization issue.
5 lenny This bug only applies to the lenny release (Debian 5.0).
6 lfs This bug affects support for large files (over 2 gigabytes).
7 patch You are including a patch to fix this problem.
8 security This problem is a security vulnerability in Debian.
9 sid This bug only applies to the unstable branch of Debian.
10 squeeze This bug only applies to the squeeze release (Debian 6.0).
11 upstream This bug applies to the upstream part of the package.
12 wheezy This bug only applies to the wheezy release
13 none
Please select tags: (one at a time) [none]
Spawning nano...
Report will be sent to "Debian Bug Tracking System" <sub...@bugs.debian.org>
Submit this report on guitarix (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|s|?]?
Connecting to smtp.uio.no via SMTP...
Enter SMTP password for t...@smtp.uio.no:
Bug report submitted to: "Debian Bug Tracking System" <sub...@bugs.debian.org>
Copies sent to:
Debian Bug Tracking System <sub...@bugs.debian.org>
=?utf-8?q?Torquil_Macdonald_S=C3=B8rensen?= <torq...@gmail.com>
If you want to provide additional information, please wait to receive the bug
tracking number via email; you may then send any extra information to
n...@bugs.debian.org (e.g.
999...@bugs.debian.org), where n is the bug number. Normally you will receive an
acknowledgement via email including the bug report number within an hour; if you
haven't received a
confirmation, then the bug reporting process failed at some point (reportbug or
MTA failure, BTS maintenance, etc.).
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
