# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
+# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
+#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-06-26 16:13+0000\n"
+"POT-Creation-Date: 2010-01-04 00:17+0100\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"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: ENCODING"
-# type: Content of: <chapter><title>
-#: beyond-pkging.dbk:5
+#. type: Content of: <chapter><title>
+#: beyond-pkging.dbk:7
msgid "Beyond Packaging"
msgstr ""
-# type: Content of: <chapter><para>
-#: beyond-pkging.dbk:7
+#
. type: Content of: <chapter><para>
+#: beyond-pkging.dbk:9
msgid ""
"Debian is about a lot more than just packaging software and maintaining "
"those packages. This chapter contains information about ways, often really "
"maintaining packages."
msgstr ""
-# type: Content of: <chapter><para>
-#: beyond-pkging.dbk:12
+#
. type: Content of: <chapter><para>
+#: beyond-pkging.dbk:14
msgid ""
"As a volunteer organization, Debian relies on the discretion of its members "
"in choosing what they want to work on and in choosing the most critical "
"thing to spend their time on."
msgstr ""
-# type: Content of: <chapter><section><title>
-#: beyond-pkging.dbk:17
+#. type: Content of: <chapter><section><title>
+#: beyond-pkging.dbk:19
msgid "Bug reporting"
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:19
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:21
msgid ""
"We encourage you to file bugs as you find them in Debian packages. In fact, "
"Debian developers are often the first line testers. Finding and reporting "
"bugs in other developers' packages improves the quality of Debian."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:24
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:26
msgid ""
-"Read the <ulink url=\"http://www.debian.org/Bugs/Reporting\">instructions "
-"for reporting bugs</ulink> in the Debian <ulink "
-"url=\"http://www.debian.org/Bugs/\">bug tracking system</ulink>."
+"Read the <ulink url=\"&url-bts-report;\">instructions for reporting "
+"bugs</ulink> in the Debian <ulink url=\"&url-bts;\">bug tracking "
+"system</ulink>."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:29
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:31
msgid ""
"Try to submit the bug from a normal user account at which you are likely to "
"receive mail, so that people can reach you if they need further information "
"about the bug. Do not submit bugs as root."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:34
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:36
msgid ""
"You can use a tool like <citerefentry> "
"<refentrytitle>reportbug</refentrytitle> <manvolnum>1</manvolnum> "
"process."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:39
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:41
msgid ""
"Make sure the bug is not already filed against a package. Each package has "
"a bug list easily reachable at "
-"<literal>http://bugs.debian.org/<replaceable>packagename</replaceable></literal> "
+"<literal>http://&bugs-host;/<replaceable>packagename</replaceable></literal> "
"Utilities like <citerefentry> <refentrytitle>querybts</refentrytitle> "
"<manvolnum>1</manvolnum> </citerefentry> can also provide you with this "
"information (and <command>reportbug</command> will usually invoke "
"<command>querybts</command> before sending, too)."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:48
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:50
msgid ""
"Try to direct your bugs to the proper location. When for example your bug "
"is about a package which overwrites files from another package, check the "
"filing duplicate bug reports."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:54
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:56
msgid ""
"For extra credit, you can go through other packages, merging bugs which are "
"reported more than once, or tagging bugs `fixed' when they have already been "
"permission from the maintainer)."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:61
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:63
msgid ""
"From time to time you may want to check what has been going on with the bug "
"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.debian.org/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:68
+#. type: Content of: <chapter><section><section><title>
+#: beyond-pkging.dbk:70
msgid "Reporting lots of bugs at once (mass bug filing)"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:70
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:72
msgid ""
"Reporting a great number of bugs for the same problem on a great number of "
"different packages — i.e., more than 10 — is a deprecated practice. Take "
"emitted."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:77
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:79
msgid ""
"If you report more than 10 bugs on the same topic at once, it is recommended "
-"that you send a message to <email>debian-devel@lists.debian.org</email> "
-"describing your intention before submitting the report, and mentioning the "
-"fact in the subject of your mail. This will allow other developers to "
-"verify that the bug is a real problem. In addition, it will help prevent a "
-"situation in which several maintainers start filing the same bug report "
-"simultaneously."
+"that you send a message to &email-debian-devel; describing your intention "
+"before submitting the report, and mentioning the fact in the subject of your "
+"mail. This will allow other developers to verify that the bug is a real "
+"problem. In addition, it will help prevent a situation in which several "
+"maintainers start filing the same bug report simultaneously."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:85
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:87
msgid ""
-"Please use the programms <command>dd-list</command> and if appropriate "
+"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@lists.debian.org</email>."
+"&email-debian-devel;."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:91
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:93
msgid ""
"Note that when sending lots of bugs on the same subject, you should send the "
-"bug report to <email>maintonly@bugs.debian.org</email> so that the bug "
-"report is not forwarded to the bug distribution mailing list."
+"bug report to <email>maintonly@&bugs-host;</email> so that the bug report is "
+"not forwarded to the bug distribution mailing list."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><title>
+#: beyond-pkging.dbk:98
+msgid "Usertags"
msgstr ""
-# type: Content of: <chapter><section><title>
+#. type: Content of: <chapter><section><section><section><para>
#: beyond-pkging.dbk:100
+msgid ""
+"You may wish to use BTS usertags when submitting bugs across a number of "
+"packages. Usertags are similar to normal tags such as 'patch' and 'wishlist' "
+"but differ in that they are user-defined and occupy a namespace that is "
+"unique to a particular user. This allows multiple sets of developers to "
+"'usertag' the same bug in different ways without conflicting."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:107
+msgid ""
+"To add usertags when filing bugs, specify the <literal>User</literal> and "
+"<literal>Usertags</literal> pseudo-headers:"
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><screen>
+#: beyond-pkging.dbk:111
+#, no-wrap
+msgid ""
+"To: submit@bugs.debian.org\n"
+"Subject: <replaceable><title-of-bug></replaceable>\n"
+"\n"
+"Package: <replaceable><pkgname></replaceable>\n"
+"<replaceable>[ ... ]</replaceable>\n"
+"User: <replaceable><email-addr></replaceable>\n"
+"Usertags: <replaceable><tag-name> [ <tag-name> "
+"... ]</replaceable>\n"
+"\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."
+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>."
+msgstr ""
+
+#. type: Content of: <chapter><section><title>
+#: beyond-pkging.dbk:137
msgid "Quality Assurance effort"
msgstr ""
-# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:102
+#. type: Content of: <chapter><section><section><title>
+#: beyond-pkging.dbk:139
msgid "Daily work"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:104
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:141
msgid ""
"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 "
"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@lists.debian.org</email> or "
-"<email>debian-devel@lists.debian.org</email>). At the same time, you can "
-"look for co-maintainers (see <xref linkend=\"collaborative-maint\"/> )."
+"(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>
-#: beyond-pkging.dbk:118
+#. type: Content of: <chapter><section><section><title>
+#: beyond-pkging.dbk:155
msgid "Bug squashing parties"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:120
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:157
msgid ""
"From time to time the QA group organizes bug squashing parties to get rid of "
"as many problems as possible. They are announced on "
-"<email>debian-devel-announce@lists.debian.org</email> 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)."
+"&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 "
+"<command>perl</command> version which requires recompilation of all the "
+"binary modules)."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:129
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:166
msgid ""
"The rules for non-maintainer uploads differ during the parties because the "
"announcement of the party is considered prior notice for NMU. If you have "
"BTS."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:138
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:175
msgid ""
"People participating in the party have special rules for NMU, they can NMU "
"without prior notice if they upload their NMU to DELAYED/3-day at least. "
"maintainer."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:145
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:182
msgid ""
"If you don't feel confident about doing an NMU, just send a patch to the "
"BTS. It's far better than a broken NMU."
msgstr ""
-# type: Content of: <chapter><section><title>
-#: beyond-pkging.dbk:153
+#. type: Content of: <chapter><section><title>
+#: beyond-pkging.dbk:190
msgid "Contacting other maintainers"
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:155
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:192
msgid ""
"During your lifetime within Debian, you will have to contact other "
"maintainers for various reasons. You may want to discuss a new way of "
"someone that a new upstream version is available and that you need it."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:161
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:198
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.debian.org</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><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."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:169
+#
. 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>@packages.qa.debian.org</literal> "
-"email address."
+"do so by using the <literal><package>@&pts-host;</literal> email "
+"address."
msgstr ""
-# type: Content of: <chapter><section><title>
-#: beyond-pkging.dbk:177
+#. type: Content of: <chapter><section><title>
+#: beyond-pkging.dbk:215
msgid "Dealing with inactive and/or unreachable maintainers"
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:179
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:217
msgid ""
"If you notice that a package is lacking maintenance, you should make sure "
"that the maintainer is active and will continue to work on their packages. "
"they just need a reminder."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:186
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:224
msgid ""
"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"
-msgstr ""
-
-# type: Content of: <chapter><section><screen>
-#: beyond-pkging.dbk:194
-#, no-wrap
-msgid "-query --help"
-msgstr ""
-
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:197
-msgid ""
+"<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>
-#: beyond-pkging.dbk:202
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:235
msgid ""
"The first step is to politely contact the maintainer, and wait a reasonable "
"time for a response. It is quite hard to define reasonable time, but it is "
"way to handle this would be to send a reminder after two weeks."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:208
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:241
msgid ""
"If the maintainer doesn't reply within four weeks (a month), one can assume "
"that a response will probably not happen. If that happens, you should "
"maintainer in question as possible. This includes:"
msgstr ""
-# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: beyond-pkging.dbk:216
+#
. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: beyond-pkging.dbk:249
msgid ""
-"The echelon information available through the <ulink "
-"url=\"https://db.debian.org/\">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:225
+#
. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: beyond-pkging.dbk:259
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 "
"whom."
msgstr ""
-# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: beyond-pkging.dbk:234
+#
. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: beyond-pkging.dbk:268
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 "
"groups."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:241
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:275
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:249
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:283
msgid ""
-"It is also allowed to post a query to "
-"<email>debian-devel@lists.debian.org</email>, asking if anyone is aware of "
-"the whereabouts of the missing maintainer. Please Cc: the person in "
-"question."
+"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 "
+"person in question."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:254
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:288
msgid ""
-"Once you have gathered all of this, you can contact "
-"<email>mia@qa.debian.org</email>. People on this alias will use the "
-"information you provide in order to decide how to proceed. For example, "
-"they might orphan one or all of the packages of the maintainer. If a "
-"package has been NMUed, they might prefer to contact the NMUer before "
-"orphaning the package — perhaps the person who has done the NMU is "
-"interested in the package."
+"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 "
+"proceed. For example, they might orphan one or all of the packages of the "
+"maintainer. If a package has been NMUed, they might prefer to contact the "
+"NMUer before orphaning the package — perhaps the person who has done the NMU "
+"is interested in the package."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:262
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:296
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 "
"the deceased and find a very impolite, angry and accusing message!"
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:270
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:304
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 "
"package to someone with more time."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:276
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:310
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@qa.debian.org</email>."
+"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:284
+#. type: Content of: <chapter><section><title>
+#: beyond-pkging.dbk:318
msgid "Interacting with prospective Debian developers"
msgstr ""
-# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:286
+#
. type: Content of: <chapter><section><para>
+#: beyond-pkging.dbk:320
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 "
"section describes how to help new prospective developers."
msgstr ""
-# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:292
+#. type: Content of: <chapter><section><section><title>
+#: beyond-pkging.dbk:326
msgid "Sponsoring packages"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:294
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:328
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 "
"package also means accepting responsibility for it."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:299
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:339
msgid ""
"New maintainers usually have certain difficulties creating Debian packages — "
"this is quite understandable. That is why the sponsor is there, to check "
"inspect it before letting it in.)"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:306
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:346
msgid ""
"Sponsoring merely by signing the upload or just recompiling is <emphasis "
"role=\"strong\">definitely not recommended</emphasis>. You need to build "
"traced to you."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:313
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:353
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 "
"handling the 'Tasks and Skills' part of their application."
msgstr ""
-# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:320
+#. type: Content of: <chapter><section><section><title>
+#: beyond-pkging.dbk:360
msgid "Managing sponsored packages"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:322
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:362
msgid ""
"By uploading a sponsored package to Debian, you are certifying that the "
"package meets minimum Debian standards. That implies that you must build "
"and test the package on your own system before uploading."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:327
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:367
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 "
"<filename>.orig.tar.gz</filename> file that they're providing."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:336
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:376
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 "
"the package is in acceptable shape. Being a sponsor means being a mentor."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:341
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:381
msgid "Once the package meets Debian standards, build and sign it with"
msgstr ""
-# type: Content of: <chapter><section><section><screen>
-#: beyond-pkging.dbk:344
+#. type: Content of: <chapter><section><section><screen>
+#: beyond-pkging.dbk:384
#, no-wrap
-msgid "-buildpackage -k<replaceable>KEY-ID</replaceable>"
+msgid "dpkg-buildpackage -k<replaceable>KEY-ID</replaceable>\n"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:347
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:387
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 "
"in your secret keyring."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:352
+#
. 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, "
"about the package."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:358
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:398
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:362
+#
. 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\"/> ."
msgstr ""
-# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:368
+#. type: Content of: <chapter><section><section><title>
+#: beyond-pkging.dbk:408
msgid "Advocating new developers"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:370
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:410
msgid ""
-"See the page about <ulink "
-"url=\"http://www.debian.org/devel/join/nm-advocate\">advocating a "
+"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:377
+#. type: Content of: <chapter><section><section><title>
+#: beyond-pkging.dbk:417
msgid "Handling new maintainer applications"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:379
+#
. type: Content of: <chapter><section><section><para>
+#: beyond-pkging.dbk:419
msgid ""
-"Please see <ulink "
-"url=\"http://www.debian.org/devel/join/nm-amchecklist\">Checklist for "
+"Please see <ulink url=\"&url-newmaint-amchecklist;\">Checklist for "
"Application Managers</ulink> at the Debian web site."
msgstr ""
~ianmdlvl / developers-reference.git / blobdiff