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"
msgid ""
"Be very careful with your private keys. Do not place them on any public "
"servers or multiuser machines, such as the Debian servers (see <xref "
-"linkend=\"server-machines\"/> ). Back your keys up; keep a copy offline. "
+"linkend=\"server-machines\"/>). Back your keys up; keep a copy offline. "
"Read the documentation that comes with your software; read the <ulink "
"url=\"&url-pgp-faq;\">PGP FAQ</ulink>."
msgstr ""
#: developer-duties.dbk:102
msgid ""
"Usually this means that other developers are allowed to NMU (see <xref "
-"linkend=\"nmu\"/> ) your package if a big problem (release critical bug, "
+"linkend=\"nmu\"/>) your package if a big problem (release critical bug, "
"security update, etc.) occurs while you're on vacation. Sometimes it's "
"nothing as critical as that, but it's still appropriate to let others know "
"that you're unavailable."
#. type: Content of: <chapter><section><para>
#: developer-duties.dbk:124
msgid ""
-"Ideally, you should sign up at the <ulink "
-"url=\"&url-newmaint-db;gpg.php\">GPG coordination site</ulink> when booking "
-"a holiday and check if anyone there is looking for signing. This is "
-"especially important when people go to exotic places where we don't have any "
-"developers yet but where there are people who are interested in applying."
+"Ideally, you should sign up at the <ulink url=\"&url-gpg-coord;\">GPG "
+"coordination pages</ulink> when booking a holiday and check if anyone there "
+"is looking for signing. This is especially important when people go to "
+"exotic places where we don't have any developers yet but where there are "
+"people who are interested in applying."
msgstr ""
#. type: Content of: <chapter><section><title>
#: developer-duties.dbk:166
msgid ""
"Generally you should deal with bug reports on your packages as described in "
-"<xref linkend=\"bug-handling\"/> . However, there's a special category of "
+"<xref linkend=\"bug-handling\"/>. However, there's a special category of "
"bugs that you need to take care of — the so-called release-critical bugs (RC "
"bugs). All bug reports that have severity <literal>critical</literal>, "
"<literal>grave</literal> or <literal>serious</literal> are considered to "
"<email>debian-qa@&lists-host;</email>, or explain your difficulties and "
"present a plan to fix them by sending a mail to the bug report. Otherwise, "
"people from the QA group may want to do a Non-Maintainer Upload (see <xref "
-"linkend=\"nmu\"/> ) after trying to contact you (they might not wait as long "
+"linkend=\"nmu\"/>) after trying to contact you (they might not wait as long "
"as usual before they do their NMU if they have seen no recent activity from "
"you in the BTS)."
msgstr ""
#. type: Content of: <chapter><section><orderedlist><listitem><para>
#: developer-duties.dbk:200
-msgid "Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ."
+msgid "Orphan all your packages, as described in <xref linkend=\"orphaning\"/>."
msgstr ""
#. type: Content of: <chapter><section><orderedlist><listitem><para>
#: developer-duties.dbk:211
msgid ""
"Notify the Debian key ring maintainers that you are leaving by opening a "
-"ticket in Debian RT by sending a mail to keyring@rt.debian.org with the "
-"words 'Debian RT' somewhere in the subject line (case doesn't matter)."
+"ticket in Debian RT by sending a mail to &email-keyring; with the words "
+"'Debian RT' somewhere in the subject line (case doesn't matter)."
msgstr ""
~ianmdlvl / developers-reference.git / blobdiff