[Reportbug-maint] Bug#613427: Independency of bug severity
sergey
sergey_ifeo at rambler.ru
Tue Feb 15 18:06:06 UTC 2011
Additional: it was wrong, reportbug crashes without dependency of bug severity.
Here the next dialog with reportbug:
sergey at fc3:~$ reportbug
Please enter the name of the package in which you have found a problem, or
type 'other' to report a more general problem.
> xfe
*** Welcome to reportbug. Use ? for help at prompts. ***
Detected character set: UTF-8
Please change your locale if this is incorrect.
Using 'sergey <sergey_ifeo at rambler.ru>' as your from address.
Getting status for xfe...
Checking for newer versions at packages.debian.org...
Will use http protocol talking to sourceforge.net/projects/xfe.
Maintainer for xfe is 'Joachim Wiedorn <ad_debian at joonet.de>'.
Looking up dependencies of xfe...
Getting changed configuration files...
Please briefly describe your problem (max. 100 characters allowed; you can
elaborate in a moment). This will be the bug email subject, so write a concise
summary of what is wrong with the package, for example, "fails to send email"
or "does not start with -q option specified" (type Ctrl+c to exit).
> xfe requires libtiff.so.3 that is not in dependencies
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.)
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]
Traceback (most recent call last):
File "/usr/bin/reportbug", line 2098, in <module>
main()
File "/usr/bin/reportbug", line 1045, in main
return iface.user_interface()
File "/usr/bin/reportbug", line 1990, in user_interface
issource=self.options.source)
File "/usr/lib/pymodules/python2.6/reportbug/utils.py", line 745, in generate_blank_report
debsumsoutput=debsumsoutput, issource=issource)
File "/usr/lib/pymodules/python2.6/reportbug/bugreport.py", line 43, in __init__
self.type = type
File "/usr/lib/pymodules/python2.6/reportbug/bugreport.py", line 59, in tset
raise AttributeError, 'invalid report type'
AttributeError: invalid report type
sergey at fc3:~$
More information about the Reportbug-maint
mailing list