msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2010-05-06 17:34-0400\n"
+"POT-Creation-Date: 2010-06-03 21:58-0400\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"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>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
#: beyond-pkging.dbk:87
msgid ""
"Please use the programs <command>dd-list</command> and if appropriate "
-"<command>whodepends</command> (from the package devscripts) to generate a "
-"list of all affected packages, and include the output in your mail to "
-"&email-debian-devel;."
+"<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;."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#, no-wrap
msgid ""
"To: submit@bugs.debian.org\n"
-"Subject: <replaceable><title-of-bug></replaceable>\n"
+"Subject: <replaceable>title-of-bug</replaceable>\n"
"\n"
-"Package: <replaceable><pkgname></replaceable>\n"
+"Package: <replaceable>pkgname</replaceable>\n"
"<replaceable>[ ... ]</replaceable>\n"
-"User: <replaceable><email-addr></replaceable>\n"
-"Usertags: <replaceable><tag-name> [ <tag-name> "
-"... ]</replaceable>\n"
+"User: <replaceable>email-addr</replaceable>\n"
+"Usertags: <replaceable>tag-name [ tag-name ... ]</replaceable>\n"
"\n"
-"<replaceable><description-of-bug ...></replaceable>\n"
+"<replaceable>description-of-bug ...</replaceable>\n"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
#: beyond-pkging.dbk:122
msgid ""
"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 set the <literal>User</literal> to an appropriate mailing list "
-"after describing your intention there."
+"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."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
#: beyond-pkging.dbk:128
msgid ""
"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>."
msgstr ""
#. type: Content of: <chapter><section><title>
"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 should consider orphaning some of your packages (see "
-"<xref 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\"/> )."
+"<xref 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 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\"/>)."
msgstr ""
#. type: Content of: <chapter><section><section><title>
msgid ""
"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 "
-"email the maintainer, whatever their individual email address (or addresses) "
-"may be. Replace <literal><package></literal> with the name of a "
-"source or a binary package."
+"<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 <replaceable>package</replaceable> "
+"with the name of a source or a binary package."
msgstr ""
#. type: Content of: <chapter><section><para>
#: beyond-pkging.dbk:206
msgid ""
"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."
msgstr ""
"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 "
+"<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 "
#: beyond-pkging.dbk:310
msgid ""
"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 documented and contact &email-mia;."
+"<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;."
msgstr ""
#. type: Content of: <chapter><section><title>
"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 providing."
+"<filename>.orig.tar.{gz,bz2,lzma}</filename> file that they're providing."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
#: beyond-pkging.dbk:392
msgid ""
-"The Maintainer 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."
+"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."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: beyond-pkging.dbk:402
msgid ""
"You are encouraged to keep tabs on the package you sponsor using <xref "
-"linkend=\"pkg-tracking-system\"/> ."
+"linkend=\"pkg-tracking-system\"/>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
~ianmdlvl / developers-reference.git / blobdiff