msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2010-05-06 17:34-0400\n"
+"POT-Creation-Date: 2012-01-10 17:56-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"
+"Language: \n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=utf-8\n"
-"Content-Transfer-Encoding: ENCODING"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
#. type: Content of: <chapter><title>
#: new-maintainer.dbk:7
"word <literal>subscribe</literal> in the <literal>Subject</literal> of an "
"email to &email-debian-devel-req;. In case of problems, contact the list "
"administrator at &email-listmaster;. More information on available mailing "
-"lists can be found in <xref linkend=\"mailing-lists\"/> . "
+"lists can be found in <xref linkend=\"mailing-lists\"/>. "
"&email-debian-devel-announce; is another list which is mandatory for anyone "
"who wishes to follow Debian's development."
msgstr ""
"Another good list to subscribe to is &email-debian-mentors;. See <xref "
"linkend=\"mentors\"/> for details. The IRC channel "
"<literal>#debian</literal> can also be helpful; see <xref "
-"linkend=\"irc-channels\"/> ."
+"linkend=\"irc-channels\"/>."
msgstr ""
#. type: Content of: <chapter><section><para>
"to that list and an experienced developer will volunteer to help."
msgstr ""
-#. FIXME - out of order
-#. Those who are seeking a
-#. sponsor can request one at <ulink url="http://www.internatif.org/bortzmeyer/debian/sponsor/">
-#. </ulink>.
-#
#. type: Content of: <chapter><section><para>
#: new-maintainer.dbk:76
msgid ""
"are waiting for your new maintainer application to go through, you might be "
"able find a sponsor to upload your package for you. Sponsors are people who "
"are official Debian Developers, and who are willing to criticize and upload "
-"your packages for you. Please read the unofficial debian-mentors FAQ at "
-"<ulink url=\"&url-mentors;\"></ulink> first."
+"your packages for you. Please read the debian-mentors FAQ at <ulink "
+"url=\"&url-mentors;\"></ulink> first."
msgstr ""
#. type: Content of: <chapter><section><para>
-#: new-maintainer.dbk:89
+#: new-maintainer.dbk:84
msgid ""
"If you wish to be a mentor and/or sponsor, more information is available in "
-"<xref linkend=\"newmaint\"/> ."
+"<xref linkend=\"newmaint\"/>."
msgstr ""
#. type: Content of: <chapter><section><title>
-#: new-maintainer.dbk:95
+#: new-maintainer.dbk:90
msgid "Registering as a Debian developer"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: new-maintainer.dbk:97
+#: new-maintainer.dbk:92
msgid ""
"Before you decide to register with &debian-formal;, you will need to read "
"all the information available at the <ulink url=\"&url-newmaint;\">New "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: new-maintainer.dbk:111
+#: new-maintainer.dbk:106
msgid ""
"The process of registering as a developer is a process of verifying your "
"identity and intentions, and checking your technical skills. As the number "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: new-maintainer.dbk:120
+#: new-maintainer.dbk:115
msgid ""
"Before you actually register you should have shown that you can do competent "
"work and will be a good contributor. You show this by submitting patches "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: new-maintainer.dbk:129
+#: new-maintainer.dbk:124
msgid ""
"Registration requires that you are familiar with Debian's philosophy and "
"technical documentation. Furthermore, you need a GnuPG key which has been "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: new-maintainer.dbk:142
+#: new-maintainer.dbk:137
msgid ""
"If you do not have an OpenPGP key yet, generate one. Every developer needs "
"an OpenPGP key in order to sign and verify package uploads. You should read "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: new-maintainer.dbk:150
+#: new-maintainer.dbk:145
msgid ""
-"Debian uses the <command>GNU Privacy Guard</command> (package <systemitem "
+"Debian uses the <literal>GNU Privacy Guard</literal> (package <systemitem "
"role=\"package\">gnupg</systemitem> version 1 or better) as its baseline "
"standard. You can use some other implementation of OpenPGP as well. Note "
"that OpenPGP is an open standard based on <ulink url=\"&url-rfc2440;\">RFC "
msgstr ""
#. type: Content of: <chapter><section><para><footnote><para>
-#: new-maintainer.dbk:159
+#: new-maintainer.dbk:155
msgid ""
"Version 4 keys are keys conforming to the OpenPGP standard as defined in RFC "
"2440. Version 4 is the key type that has always been created when using "
"GnuPG. PGP versions since 5.x also could create v4 keys, the other choice "
-"having beein pgp 2.6.x compatible v3 keys (also called legacy RSA by PGP)."
+"having been pgp 2.6.x compatible v3 keys (also called legacy RSA by PGP)."
msgstr ""
#. type: Content of: <chapter><section><para><footnote><para>
-#: new-maintainer.dbk:163
+#: new-maintainer.dbk:159
msgid ""
"Version 4 (primary) keys can either use the RSA or the DSA algorithms, so "
"this has nothing to do with GnuPG's question about which kind of key do you "
msgstr ""
#. type: Content of: <chapter><section><para><footnote><para>
-#: new-maintainer.dbk:167
+#: new-maintainer.dbk:163
msgid ""
"The easiest way to tell whether an existing key is a v4 key or a v3 (or v2) "
"key is to look at the fingerprint: Fingerprints of version 4 keys are the "
msgstr ""
#. type: Content of: <chapter><section><para><footnote><para>
-#: new-maintainer.dbk:174
+#: new-maintainer.dbk:170
msgid ""
"Another possibility is to pipe the key into <command>pgpdump</command>, "
"which will say something like Public Key Packet - Ver 4."
msgstr ""
#. type: Content of: <chapter><section><para><footnote><para>
-#: new-maintainer.dbk:176
+#: new-maintainer.dbk:172
msgid ""
"Also note that your key must be self-signed (i.e. it has to sign all its "
"own user IDs; this prevents user ID tampering). All modern OpenPGP software "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: new-maintainer.dbk:157
+#: new-maintainer.dbk:152
msgid ""
-"You need a version 4 key for use in Debian Development. Your key length "
-"must be at least 1024 bits; there is no reason to use a smaller key, and "
-"doing so would be much less secure. <placeholder type=\"footnote\" "
-"id=\"0\"/>"
+"You need a version 4 key for use in Debian Development. <ulink "
+"url=\"http://lists.debian.org/20090520092534.GG22906@earth.li\">Your key "
+"length must be greater than 1024 bits</ulink>; there is no reason to use a "
+"smaller key, and doing so would be much less secure.<placeholder "
+"type=\"footnote\" id=\"0\"/>"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: new-maintainer.dbk:182
+#: new-maintainer.dbk:178
msgid ""
"If your public key isn't on a public key server such as &pgp-keyserv;, "
"please read the documentation available at <ulink "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: new-maintainer.dbk:190
+#: new-maintainer.dbk:186
msgid ""
"Some countries restrict the use of cryptographic software by their "
"citizens. This need not impede one's activities as a Debian package "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: new-maintainer.dbk:198
+#: new-maintainer.dbk:194
msgid ""
"To apply as a new maintainer, you need an existing Debian Developer to "
"support your application (an <literal>advocate</literal>). After you have "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: new-maintainer.dbk:205
+#: new-maintainer.dbk:201
msgid ""
"When you have found an advocate, have your GnuPG key signed and have already "
"contributed to Debian for a while, you're ready to apply. You can simply "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: new-maintainer.dbk:215
+#: new-maintainer.dbk:211
msgid ""
"For more details, please consult <ulink url=\"&url-newmaint;\">New "
"Maintainer's Corner</ulink> at the Debian web site. Make sure that you are "
~ianmdlvl / developers-reference.git / blobdiff