# Copyright (C) 2007 Free Software Foundation, Inc.
# <>, 2007.
# , fuzzy
-#
-#
+#
+#
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2007-07-01 21:16+0000\n"
+"POT-Creation-Date: 2008-08-08 11:36-0300\n"
"PO-Revision-Date: 2007-07-01 23:09+0000\n"
"Last-Translator: <>\n"
"Language-Team: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: "
+"Content-Transfer-Encoding: \n"
# type: Content of: <chapter><title>
#: beyond-pkging.dbk:7
"as many problems as possible. They are announced on &email-debian-devel-"
"announce; and the announcement explains which area will be the focus of the "
"party: usually they focus on release critical bugs but it may happen that "
-"they decide to help finish a major upgrade (like a new perl version which "
-"requires recompilation of all the binary modules)."
+"they decide to help finish a major upgrade (like a new <command>perl</"
+"command> version which requires recompilation of all the binary modules)."
msgstr ""
# type: Content of: <chapter><section><section><para>
"There is a simple system (the MIA database) in which information about "
"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 /org/"
-"qa.debian.org/mia on the host qa.debian.org, and can be queried with a tool "
-"known as <command>mia-query</command>. 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."
+"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. 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."
msgstr ""
# type: Content of: <chapter><section><para>
# type: Content of: <chapter><section><itemizedlist><listitem><para>
#: beyond-pkging.dbk:214
msgid ""
-"The echelon information available through the <ulink url=\"&url-debian-db;"
-"\">developers' LDAP database</ulink>, which indicates when the developer "
-"last posted to a Debian mailing list. (This includes uploads via debian-*-"
-"changes lists.) Also, remember to check whether the maintainer is marked as "
-"on vacation in the database."
+"The <literal>echelon</literal> information available through the <ulink url="
+"\"&url-debian-db;\">developers' LDAP database</ulink>, which indicates when "
+"the developer last posted to a Debian mailing list. (This includes mails "
+"about uploads distributed via the &email-debian-devel-changes; list.) Also, "
+"remember to check whether the maintainer is marked as on vacation in the "
+"database."
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: beyond-pkging.dbk:223
+#: beyond-pkging.dbk:224
msgid ""
"The number of packages this maintainer is responsible for, and the condition "
"of those packages. In particular, are there any RC bugs that have been open "
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: beyond-pkging.dbk:232
+#: beyond-pkging.dbk:233
msgid ""
"Is there any activity of the maintainer outside of Debian? For example, they "
"might have posted something recently to non-Debian mailing lists or news "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:239
+#: beyond-pkging.dbk:240
msgid ""
"A bit of a problem are packages which were sponsored — the maintainer is not "
-"an official Debian developer. The echelon information is not available for "
-"sponsored people, for example, so you need to find and contact the Debian "
-"developer who has actually uploaded the package. Given that they signed the "
-"package, they're responsible for the upload anyhow, and are likely to know "
-"what happened to the person they sponsored."
+"an official Debian developer. The <literal>echelon</literal> information is "
+"not available for sponsored people, for example, so you need to find and "
+"contact the Debian developer who has actually uploaded the package. Given "
+"that they signed the package, they're responsible for the upload anyhow, and "
+"are likely to know what happened to the person they sponsored."
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:247
+#: beyond-pkging.dbk:248
msgid ""
"It is also allowed to post a query to &email-debian-devel;, asking if anyone "
"is aware of the whereabouts of the missing maintainer. Please Cc: the "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:252
+#: beyond-pkging.dbk:253
msgid ""
"Once you have gathered all of this, you can contact &email-mia;. People on "
"this alias will use the information you provide in order to decide how to "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:260
+#: beyond-pkging.dbk:261
msgid ""
"One last word: please remember to be polite. We are all volunteers and "
"cannot dedicate all of our time to Debian. Also, you are not aware of the "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:268
+#: beyond-pkging.dbk:269
msgid ""
"On the other hand, although we are volunteers, we do have a responsibility. "
"So you can stress the importance of the greater good — if a maintainer does "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:274
+#: beyond-pkging.dbk:275
msgid ""
"If you are interested in working in the MIA team, please have a look at the "
-"README file in /org/qa.debian.org/mia on qa.debian.org where the technical "
-"details and the MIA procedures are documented and contact &email-mia;."
+"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;."
msgstr ""
# type: Content of: <chapter><section><title>
-#: beyond-pkging.dbk:282
+#: beyond-pkging.dbk:283
msgid "Interacting with prospective Debian developers"
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:284
+#: beyond-pkging.dbk:285
msgid ""
"Debian's success depends on its ability to attract and retain new and "
"talented volunteers. If you are an experienced developer, we recommend that "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:290
+#: beyond-pkging.dbk:291
msgid "Sponsoring packages"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:292
+#: beyond-pkging.dbk:293
msgid ""
"Sponsoring a package means uploading a package for a maintainer who is not "
"able to do it on their own, a new maintainer applicant. Sponsoring a "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:303
+#: beyond-pkging.dbk:304
msgid ""
"New maintainers usually have certain difficulties creating Debian packages — "
"this is quite understandable. That is why the sponsor is there, to check "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:310
+#: beyond-pkging.dbk:311
msgid ""
"Sponsoring merely by signing the upload or just recompiling is <emphasis "
"role=\"strong\">definitely not recommended</emphasis>. You need to build "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:317
+#: beyond-pkging.dbk:318
msgid ""
"If you are an application manager for a prospective developer, you can also "
"be their sponsor. That way you can also verify how the applicant is "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:324
+#: beyond-pkging.dbk:325
msgid "Managing sponsored packages"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:326
+#: beyond-pkging.dbk:327
msgid ""
"By uploading a sponsored package to Debian, you are certifying that the "
"package meets minimum Debian standards. That implies that you must build "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:331
+#: beyond-pkging.dbk:332
msgid ""
"You cannot simply upload a binary <filename>.deb</filename> from the "
"sponsoree. In theory, you should only ask for the diff file and the "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:340
+#: beyond-pkging.dbk:341
msgid ""
"Do not be afraid to write the sponsoree back and point out changes that need "
"to be made. It often takes several rounds of back-and-forth email before "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:345
+#: beyond-pkging.dbk:346
msgid "Once the package meets Debian standards, build and sign it with"
msgstr ""
# type: Content of: <chapter><section><section><screen>
#: beyond-pkging.dbk:348
#, no-wrap
-msgid "dpkg-buildpackage -k<replaceable>KEY-ID</replaceable>"
+msgid ""
+"\n"
+"dpkg-buildpackage -k<replaceable>KEY-ID</replaceable>\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:351
+#: beyond-pkging.dbk:352
msgid ""
"before uploading it to the incoming directory. Of course, you can also use "
"any part of your <replaceable>KEY-ID</replaceable>, as long as it's unique "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:356
+#: beyond-pkging.dbk:357
msgid ""
"The Maintainer field of the <filename>control</filename> file and the "
"<filename>changelog</filename> should list the person who did the packaging, "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:362
+#: beyond-pkging.dbk:363
msgid ""
"If you prefer to leave a more evident trace of your sponsorship job, you can "
"add a line stating it in the most recent changelog entry."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:366
+#: beyond-pkging.dbk:367
msgid ""
"You are encouraged to keep tabs on the package you sponsor using <xref "
"linkend=\"pkg-tracking-system\"/> ."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:372
+#: beyond-pkging.dbk:373
msgid "Advocating new developers"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:374
+#: beyond-pkging.dbk:375
msgid ""
"See the page about <ulink url=\"&url-newmaint-advocate;\">advocating a "
"prospective developer</ulink> at the Debian web site."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:381
+#: beyond-pkging.dbk:382
msgid "Handling new maintainer applications"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:383
+#: beyond-pkging.dbk:384
msgid ""
"Please see <ulink url=\"&url-newmaint-amchecklist;\">Checklist for "
"Application Managers</ulink> at the Debian web site."
msgstr ""
-