reports that you submitted. Take this opportunity to close those that you
can't reproduce anymore. To find out all the bugs you submitted, you just have
to visit
-<literal>http://&bugs-host;/from:<replaceable><your-email-addr></replaceable></literal>.
+<literal>http://&bugs-host;/from:<replaceable>your-email-addr</replaceable></literal>.
</para>
<section id="submit-many-bugs">
<title>Reporting lots of bugs at once (mass bug filing)</title>
several maintainers start filing the same bug report simultaneously.
</para>
<para>
-Please use the programms <command>dd-list</command> and if appropriate
-<command>whodepends</command> (from the package devscripts) to generate a list
+Please use the programs <command>dd-list</command> and if appropriate
+<command>whodepends</command> (from the package <systemitem role="package">devscripts</systemitem>) to generate a list
of all affected packages, and include the output in your mail to
&email-debian-devel;.
</para>
</para>
<screen>
To: submit@bugs.debian.org
-Subject: <replaceable><title-of-bug></replaceable>
+Subject: <replaceable>title-of-bug</replaceable>
-Package: <replaceable><pkgname></replaceable>
+Package: <replaceable>pkgname</replaceable>
<replaceable>[ ... ]</replaceable>
-User: <replaceable><email-addr></replaceable>
-Usertags: <replaceable><tag-name> [ <tag-name> ... ]</replaceable>
+User: <replaceable>email-addr</replaceable>
+Usertags: <replaceable>tag-name [ tag-name ... ]</replaceable>
-<replaceable><description-of-bug ...></replaceable>
+<replaceable>description-of-bug ...</replaceable>
</screen>
<para>
Note that tags are seperated by spaces and cannot contain underscores. If you
-are filing bugs for for a particular group or team it is recommended that you
+are filing bugs for a particular group or team it is recommended that you
set the <literal>User</literal> to an appropriate mailing list after describing
your intention there.
</para>
<para>
To view bugs tagged with a specific usertag, visit
-<literal>http://&bugs-host;/cgi-bin/pkgreport.cgi?users=<replaceable><email-addr></replaceable>&tag=<replaceable><tag-name></replaceable></literal>.
+<literal>http://&bugs-host;/cgi-bin/pkgreport.cgi?users=<replaceable>email-addr</replaceable>&tag=<replaceable>tag-name</replaceable></literal>.
</para>
</section>
</section>
Even though there is a dedicated group of people for Quality Assurance, QA
duties are not reserved solely for them. You can participate in this effort by
keeping your packages as bug-free as possible, and as lintian-clean (see <xref
-linkend="lintian"/> ) as possible. If you do not find that possible, then you
+linkend="lintian"/>) as possible. If you do not find that possible, then you
should consider orphaning some of your packages (see <xref
-linkend="orphaning"/> ). Alternatively, you may ask the help of other people
+linkend="orphaning"/>). Alternatively, you may ask the help of other people
in order to catch up with the backlog of bugs that you have (you can ask for
help on &email-debian-qa; or
&email-debian-devel;). At the same time, you can look for
-co-maintainers (see <xref linkend="collaborative-maint"/> ).
+co-maintainers (see <xref linkend="collaborative-maint"/>).
</para>
</section>
<para>
Looking up the email address of the maintainer for the package can be
distracting. Fortunately, there is a simple email alias,
-<literal><package>@&packages-host;</literal>, which provides a way to
+<literal><replaceable>package</replaceable>@&packages-host;</literal>, which provides a way to
email the maintainer, whatever their individual email address (or addresses)
-may be. Replace <literal><package></literal> with the name of a source
+may be. Replace <replaceable>package</replaceable> with the name of a source
or a binary package.
</para>
<para>
You may also be interested in contacting the persons who are subscribed to a
-given source package via <xref linkend="pkg-tracking-system"/> . You can do so
-by using the <literal><package>@&pts-host;</literal> email
+given source package via <xref linkend="pkg-tracking-system"/>. You can do so
+by using the <literal><replaceable>package</replaceable>@&pts-host;</literal> email
address.
</para>
<!-- FIXME: moo@packages.d.o is easily confused with moo@packages.qa.d.o -->
maintainers who are deemed Missing In Action is recorded. When a member of the
QA group contacts an inactive maintainer or finds more information about one,
this is recorded in the MIA database. This system is available in
-<filename>/org/qa.debian.org/mia</filename> on the host <literal>qa.debian.org
-</literal>, and can be queried with the <command>mia-query</command> tool.
+<filename>/org/qa.debian.org/mia</filename> on the host <literal>qa.debian.org</literal>,
+and can be queried with the <command>mia-query</command> tool.
Use <command>mia-query --help</command> to see how to query the database.
If you find that no information has been recorded about an inactive maintainer yet,
or that you can add more information, you should generally proceed as follows.
</para>
<para>
If you are interested in working in the MIA team, please have a look at the
-README file in <filename>/org/qa.debian.org/mia</filename> on <literal>
-qa.debian.org</literal> where the technical details and the MIA procedures are
+<filename>README</filename> file in <filename>/org/qa.debian.org/mia</filename> on
+<literal>qa.debian.org</literal> where the technical details and the MIA procedures are
documented and contact &email-mia;.
</para>
</section>
original source tarball, and then you should download the source and apply the
diff yourself. In practice, you may want to use the source package built by
your sponsoree. In that case, you have to check that they haven't altered the
-upstream files in the <filename>.orig.tar.gz</filename> file that they're
+upstream files in the <filename>.orig.tar.{gz,bz2,lzma}</filename> file that they're
providing.
</para>
<para>
secret keyring.
</para>
<para>
-The Maintainer field of the <filename>control</filename> file and the
+The <literal>Maintainer</literal> field of the <filename>control</filename> file and the
<filename>changelog</filename> should list the person who did the packaging,
i.e., the sponsoree. The sponsoree will therefore get all the BTS mail about
the package.
</para>
<para>
You are encouraged to keep tabs on the package you sponsor using <xref
-linkend="pkg-tracking-system"/> .
+linkend="pkg-tracking-system"/>.
</para>
</section>
~ianmdlvl / developers-reference.git / blobdiff