is a tool used to submit
(PRs) to a central support site. In most cases the correct
will be the default. This argument indicates the support site which
is responsible for the category of problem involved. Some sites may
use a local address as a default.
values are defined by using the
invokes an editor on a problem report template (after trying to fill
in some fields with reasonable default values). When you exit the
sends the completed form to the
Problem Report Management System
(GNATS) at a central support site. At the support site, the PR
is assigned a unique number and is stored in the GNATS database
according to its category and submitter-id. GNATS automatically
replies with an acknowledgement, citing the category and the PR
To ensure that a PR is handled promptly, it should contain
one of the available categories to identify the
problem area. (Use
to see a list of categories.)
The more precise your problem description and the more complete your
information, the faster your support team can solve your problems.
depends on a correctly configured mail submission system to work correctly.
If, for any reason, sending mail is not working, problem reports can be
submitted over the web, through:
specify a file (problem-report) which already contains a
complete problem report.
sends the contents of the file without invoking the editor. If
the value for
reads from standard input.
Give the problem report the severity
Change mail address at the support site for problem reports. The
is the address used for the default
argument rather than this option in nearly all cases.
header of the message.
Copy the specified
Binary files are uuencoded.
print the form specified by the environment variable
on standard output. If
is not set, print the standard blank PR template. No mail is sent.
print the list of available categories. No mail is sent.
This may also be specified as
to submit problem reports rather than mailing them directly. Using
both the template and
itself will help ensure all necessary information will reach the
This used to be for the advocacy WWW pages.
Now deprecated in favour of the
category, relevant alternative use of this category is encouraged.
Alpha processor specific problems.
AMD64 processor specific problems.
ARM processor specific problems.
Corrections or enhancements to system executables.
Corrections or enhancements to the system configuration files.
Corrections or enhancements to the manpages or other documentation.
Corrections or enhancements to the GNU contributed software.
Intel x86 processor specific problems.
Intel ia64 processor specific problems.
Problems related to Java.
Changes or enhancements to the architecture independent kernel sources.
Problems that do not fit into any of the other categories.
Corrections or enhancements (including new ports) to the ports collection.
PowerPC processor specific problems.
SPARC processor specific problems.
Standards conformance issues.
Problems specific to the SPARC sun4v architecture and processors.
Problems related to threading on FreeBSD.
Problems related to the USB subsystem.
Changes or enhancements to the FreeBSD website.
The environment variable
specifies the editor to invoke on the template.
If the environment variable
is set, its value is used as the path + command line arguments of the
executable to be invoked for sending the problem report (which will be
provided via standard input).
This can be useful if you either use a MTA other than sendmail or need
to provide additional parameters, such as the envelope sender on
machines without a valid FQDN.
/usr/sbin/sendmail -oi -t
If the environment variable
is set, then its value is used as the file name of the template for
your problem-report editing session. You can use this to start with a
partially completed form (for example, a form with the identification
fields already completed).
HOW TO FILL OUT A PROBLEM REPORT
Problem reports have to be in a particular form so that a program can
easily manage them. Please remember the following guidelines:
with each problem report.
For follow-up mail, use the same subject line as the one in the automatic
acknowledgement. It consists of category, PR number and the original synopsis
line. This allows the support site to relate several mail messages to a
particular PR and to record them automatically.
Please try to be as accurate as possible in the subject and/or synopsis line.
The subject and the synopsis line are not confidential. This is
because open-bugs lists are compiled from them. Avoid confidential
See the GNU
or the document Reporting Problems With send-pr for detailed
information on reporting problems
HOW TO SUBMIT TEST CASES, CODE, ETC.
Submit small code samples with the PR. Contact the support site for
instructions on submitting larger test cases and problematic source
/tmp/pf.XXXXXXXXcopy of PR used in editing session
/tmp/pf.XXXXXXXXcopy of empty PR form, for testing purposes
/tmp/pr.XXXXXXXXcopy of filled PR form, created on interrupt
/tmp/pbad.XXXXXXXXfile for rejected PRs
EMACS USER INTERFACE
An Emacs user interface for
with completion of field values is part of the
distribution (invoked with
See the file
or the ASCII file
in the top level directory of the distribution for configuration and
installation information. The Emacs LISP template file is
and is installed as
INSTALLATION AND CONFIGURATION
for installation instructions.
Reporting Problems Using send-pr
(also installed as the GNU Info file
Jeffrey Osier, Brendan Kehoe, Jason Merrill, Heinz G. Seidl (Cygnus
Copyright (c) 1992, 1993 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
are preserved on all copies.
Permission is granted to copy and distribute modified versions of this
manual under the conditions for verbatim copying, provided that the
entire resulting derived work is distributed under the terms of a
permission notice identical to this one.
Permission is granted to copy and distribute translations of this
manual into another language, under the above conditions for modified
versions, except that this permission notice may be included in
translations approved by the Free Software Foundation instead of in
the original English.