[Reportbug-maint] Bug#619138: Bug#619138: reportbug failure

[Lx]

Hi Sandro

Here we go:
user at host:~$ reportbug 
Please enter the name of the package in which you have found a problem, or type 'other' to report a more general problem.
> libapache2-mod-gnutls
*** Welcome to reportbug.  Use ? for help at prompts. ***
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'Lx <lix at lix.cc>' as your from address.
Getting status for libapache2-mod-gnutls...
No matching source or binary packages.
Please enter the version of the package this report applies to (blank OK)
> 0.5.6-1
Will send report to Debian (per lsb_release).
Querying Debian BTS for reports on libapache2-mod-gnutls (source)...
No bug reports found.

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).
> Segmentation fault error with apache2 & mod_dav (webdav). Same error as described here: http://www.outoforder.cc/projects/apache/mod_gnutls In mod_gnutls v. 0.5.8 the problem has been fixed, but the package is not available as dpkg yet. The maintainer Jack Bates <ms419 at freezone.co.uk> could not be contacted, because his mailbox is full (over quota). See also: https://bugs.launchpad.net/ubuntu/+source/mod-gnutls/+bug/719973
Your description is a bit long; please enter a shorter subject. (An empty response will retain the existing subject.)
> Segmentation fault with libapache2-mod-gnutls
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

Best, Lx

Am 21.03.2011 um 16:43 schrieb Sandro Tosi:

> Hi Lx,
> can you please cut and paste all the command line output (along with
> the exact command you launched)?
> 
> On Mon, Mar 21, 2011 at 16:04, Lx <lix at lix.cc> wrote:
>> Package: reportbug
>> Version: 4.12.6
>> 
>> Reporting a bug in the command line using reportbug causes the following error:
>> 
>> "[...]
>> 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"
>> 
>> Best, Lx
> 
> 
> -- 
> Sandro Tosi (aka morph, morpheus, matrixhasu)
> My website: http://matrixhasu.altervista.org/
> Me at Debian: http://wiki.debian.org/SandroTosi