Your message dated Sat, 24 Oct 2009 12:17:12 +0000
with message-id <[email protected]>
and subject line Bug#439203: fixed in reportbug-ng 1.10
has caused the Debian Bug report #439203,
regarding Doesn't give any explanations of the severities and what they mean
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.)
--
439203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=439203
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug-ng
Version: 0.2007.08.20
Severity: serious
--- Please enter the report below this line. ---
Too many users files bugs with a wrong severity because there is no
explanation when choosing severity in reportbug-ng.
Another bug reporting tool does this quite nicely like this:
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.)
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.
That other tool do also require a detailed justification for choosing a
justification for the report.
For example, if I choose 2 grave, I need to answer one more question:
You are reporting a grave bug; which of the following criteria does it meet?
1 renders package unusable renders the package unusable, or mostly so, on
all or nearly all possible systems on which it could be installed (i.e., not
a hardware-specific bug); or renders
package uninstallable or unremovable without
special effort
2 causes non-serious data loss causes the loss of data on the system that is
unimportant, or restorable without resorting to backup media
3 user security hole introduces a security hole allowing access to
user accounts or data not normally accessible
4 unknown not sure, or none of the above
- and if unknown is chosen, the severity is automatically downgraded to
normal.
Reportbug-ng makes it too easy to file bug reprots with a escalated - or
wrong - severity.
I might have filed this bug reprot with a wrong severity, but I forgot what
the severities meant.
/Sune
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.20-1-vserver-k7
Debian Release: lenny/sid
500 unstable www.debian-multimedia.org
500 unstable ssh.pusling.com
500 unstable ftp.debian.org
500 unstable ftp.de.debian.org
500 testing ssh.pusling.com
500 stable ssh.pusling.com
200 experimental ssh.pusling.com
200 experimental ftp.de.debian.org
--- Package information. ---
Depends (Version) | Installed
=============================-+-===========
python | 2.4.4-6
python-central (>= 0.5.8) | 0.5.14
python-qt3 | 3.17.3-2
python-soappy | 0.11.3-1.8
xdg-utils | 1.0.1-2
--
Do you know how may I ping a 3X mailer?
You neither can ever upload the device to the space bar, nor must forward to a
Fast DLL file on the system.
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: reportbug-ng
Source-Version: 1.10
We believe that the bug you reported is fixed in the latest version of
reportbug-ng, which is due to be installed in the Debian FTP archive:
reportbug-ng_1.10.dsc
to pool/main/r/reportbug-ng/reportbug-ng_1.10.dsc
reportbug-ng_1.10.tar.gz
to pool/main/r/reportbug-ng/reportbug-ng_1.10.tar.gz
reportbug-ng_1.10_all.deb
to pool/main/r/reportbug-ng/reportbug-ng_1.10_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bastian Venthur <[email protected]> (supplier of updated reportbug-ng package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Sat, 24 Oct 2009 12:17:25 +0200
Source: reportbug-ng
Binary: reportbug-ng
Architecture: source all
Version: 1.10
Distribution: unstable
Urgency: low
Maintainer: Bastian Venthur <[email protected]>
Changed-By: Bastian Venthur <[email protected]>
Description:
reportbug-ng - An easy to use alternative to Debian's classic reportbug
Closes: 439203
Changes:
reportbug-ng (1.10) unstable; urgency=low
.
* Fix "Doesn't give any explanations of the severities and what they
mean" (Closes: #439203)
- Moved the explanations from what-is-this-help to to a always visible
lable
- Also Moved the help for the tags from what-is-this to tooltips
Checksums-Sha1:
6a688f0f230695625cf5009b4dfce59b2eb25c8c 1509 reportbug-ng_1.10.dsc
4846c616bc41e928ca1d119cd929771d7b21d3af 84484 reportbug-ng_1.10.tar.gz
3a86ab6cac482d185438eb0118e1fb2f1c051ace 81416 reportbug-ng_1.10_all.deb
Checksums-Sha256:
fb1c152b07c26d573304a14e4cc9962b0ff25ccd0a81b0f8acc02b0837aca10f 1509
reportbug-ng_1.10.dsc
8454629d4bcf13598a3b86347c63999552c63dc9144c6b49be08d63d7581baa9 84484
reportbug-ng_1.10.tar.gz
4a4da1ed805d07df39f2f66e0b55f65e5abc5d6bd9cab52037a2ee33149d428b 81416
reportbug-ng_1.10_all.deb
Files:
4648b31dc32fbad741703fab34d6f089 1509 utils optional reportbug-ng_1.10.dsc
63947e49a60750320a6659dadc328c44 84484 utils optional reportbug-ng_1.10.tar.gz
83a72621444920c1cc917bd4c9d8a399 81416 utils optional reportbug-ng_1.10_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBAgAGBQJK4uyDAAoJEI6IlUTZhQANQMcQAIA9c0inzY8HxGJrSvJiJ+QX
jD/m0I8DKVGLHf3o5YKG5+7wW6hNWpGX9K9gV2NR6NPSbnhRk7LAC2o2Zp2p/6ha
n64/PU5OBB2PNNIwHKGsvMmCv2GK5FX5LNQS+DSeQp/bMuzMK8+00MJ4LKt5FTfO
ZcvrjJvQpo/7ZdmaF203RQwge7zZwmdcMqbhKP18+/J0m9qFwpk8fu2kYpYsD4d6
UVFiOekBotzCZFQLF7nMQuuTMBBy515CqSMkfoIAHZgLmdfPOKsBrJhHg6zalJZs
I0paz+DB7QiMkYr3UeU94zU1opWjm6CI77h0baR+UY3qxQPfdt0ots9K8ZJLCvbi
H2ScB3QuCjk7EvYWcbIV0TMGDtc70m2Kyf4YG48ECvvLhDVPDCtbP5aCTEHG39zI
q7REzwv5djSj74NZxAcXSTP0Zbitdplp3GHib0yucGpIS/wmJXUAE4W0mbW4/L1S
zGNTwXVA6Caw7o9eWObc6lbAQM7IxQ7hvzdPaE/aP5rOcpGJ5IlJFeLdmgmGk+0N
CMWArj5/UJ9jnDt5CD98WQXGQf16y56qGs8thWE5eS0wsLBFo5JVaIK9szjyO3/K
Q+QmCggHbL1Hq5aF6FAotxJ9M25fQ+BRh0YU4hfeHG4S4hYkORZpEqQqeeWXGbxf
7STuGAKwMqkPyL2MH/y9
=xbwh
-----END PGP SIGNATURE-----
--- End Message ---
