[komar@pavilion ~/src/pcre-ocaml-release-6.0.1/doc/pcre]$ reportbug
/usr/lib/python2.5/site-packages/zope/__init__.py:3: UserWarning: Module urwid was already imported from /usr/lib/pymodules/python2.5/urwid/__init__.py, but /usr/lib/pymodules/python2.5 is being added to sys.path
import pkg_resources
Xlib: extension "RANDR" missing on display ":0.0".
Please enter the name of the package in which you have found a problem, or type 'other' to report a more general problem.
> libpcre-ocaml-dev
*** Welcome to reportbug. Use ? for help at prompts. ***
Detected character set: UTF-8
Please change your locale if this is incorrect.
Using 'Alexander Markov <apsheronets@gmail.com>' as your from address.
Getting status for libpcre-ocaml-dev...
Checking for newer versions at packages.debian.org...
Will send report to Debian (per lsb_release).
Querying Debian BTS for reports on pcre-ocaml (source)...
No bug reports found.
Maintainer for libpcre-ocaml-dev is 'Debian OCaml Maintainers <debian-ocaml-maint@lists.debian.org>'.
Looking up dependencies of libpcre-ocaml-dev...
Please briefly describe your problem (max. 100 characters allowed; you can elaborate in a moment; an empty response will stop reportbug). 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"
(enter Ctrl+c to exit).
> No API docs in /usr/share/doc/libpcre-ocaml-dev/
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] 6
Traceback (most recent call last):
File "/usr/bin/reportbug", line 2035, in <module>
main()
File "/usr/bin/reportbug", line 997, in main
return iface.user_interface()
File "/usr/bin/reportbug", line 1930, in user_interface
klass, subject, tags, body, mode, pseudos, debsumsoutput)
File "/usr/lib/pymodules/python2.5/reportbug/utils.py", line 718, in generate_blank_report
debsumsoutput=debsumsoutput)
File "/usr/lib/pymodules/python2.5/reportbug/bugreport.py", line 43, in __init__
self.type = type
File "/usr/lib/pymodules/python2.5/reportbug/bugreport.py", line 58, in tset
raise AttributeError, 'invalid report type'
[komar@pavilion ~/src/pcre-ocaml-release-6.0.1/doc/pcre]$