Package: reportbug Version: 3.37 Severity: wishlist When reporting a serious bug, reportbug prompts for the relevant Policy section. For convenience, how about listing some of the most common sections relevant to bug reports as part of the prompt? Obviously most sections of Policy can lead to bug reports, but listing the top five or so causes of serious bugs along with the corresponding Policy section numbers seems reasonable. The resulting prompt could look like this:
""" You are reporting a serious bug; which section of the Debian Policy Manual contains the "must" or "required" directive that it violates? (E.g., "1.2.3") Some common sections for serious bug reports: 2.2.1: Not DFSG-free, or package requires software outside of main 3.5: Missing Depends or Pre-Depends 4.5: Package has no /usr/share/doc/$pkg/copyright 7.3: Conflicts 7.5: Replaces 9.1: Filesystem Hierarchy Standard Just type "unknown" if you are not sure. > In the above, reportbug could substitute the actual package name for $pkg, and could show 2.2.1 only if reporting a bug on a package in main. - Josh Triplett -- Package-specific info: ** Environment settings: EDITOR="emacs" DEBEMAIL="[EMAIL PROTECTED]" EMAIL="[EMAIL PROTECTED]" INTERFACE="text" ** /home/josh/.reportbugrc: reportbug_version "3.21.2" mode advanced ui text no-cc header "X-Debbugs-CC: [EMAIL PROTECTED]" smtphost bugs.debian.org -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.18-josh (PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages reportbug depends on: ii apt 0.6.46.4-0.1 Advanced front-end for dpkg ii python 2.4.4-3 An interactive high-level object-o ii python-central 0.5.13-0.1 register and build utility for Pyt reportbug recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
