#. type: Content of: <chapter><section><para>
#: beyond-pkging.dbk:26
msgid ""
-"Read the <ulink url=\"&url-bts-report;\">instructions for reporting "
-"bugs</ulink> in the Debian <ulink url=\"&url-bts;\">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>
#. type: Content of: <chapter><section><para>
#: beyond-pkging.dbk:36
msgid ""
-"You can use a tool like <citerefentry> "
-"<refentrytitle>reportbug</refentrytitle> <manvolnum>1</manvolnum> "
-"</citerefentry> to submit bugs. It can automate and generally ease the "
-"process."
+"You can use a tool like <citerefentry> <refentrytitle>reportbug</"
+"refentrytitle> <manvolnum>1</manvolnum> </citerefentry> to submit bugs. It "
+"can automate and generally ease the process."
msgstr ""
#. 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-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)."
+"a bug list easily reachable at <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>
"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-host;/from:<replaceable>your-email-addr</replaceable></literal>."
+"have to visit <literal>http://&bugs-host;/from:<replaceable>your-email-addr</"
+"replaceable></literal>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
"different packages — i.e., more than 10 — is a deprecated practice. Take "
"all possible steps to avoid submitting bulk bugs at all. For instance, if "
"checking for the problem can be automated, add a new check to <systemitem "
-"role=\"package\">lintian</systemitem> so that an error or warning is "
-"emitted."
+"role=\"package\">lintian</systemitem> so that an error or warning is emitted."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: beyond-pkging.dbk:87
msgid ""
"Please use the programs <command>dd-list</command> and if appropriate "
-"<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;."
+"<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>
#. 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>."
+"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>
"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\"/>)."
+"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>
#: 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; 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)."
+"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 <command>perl</"
+"command> version which requires recompilation of all the binary modules)."
msgstr ""
#. type: Content of: <chapter><section><section><para>
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><replaceable>package</replaceable>@&pts-host;</literal> email "
-"address."
+"do so by using the <literal><replaceable>package</replaceable>@&pts-host;</"
+"literal> email address."
msgstr ""
#. type: Content of: <chapter><section><title>
"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 "
-"<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."
+"<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:249
msgid ""
-"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."
+"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:310
msgid ""
"If you are interested in working in the MIA team, please have a look at the "
-"<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;."
+"<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>
#: beyond-pkging.dbk:340
msgid ""
"The maintainer prepares a source package (<filename>.dsc</filename>) and "
-"puts it online somewhere (like on <ulink "
-"url=\"http://mentors.debian.net/cgi-bin/welcome\">mentors.debian.net</ulink>) "
-"or even better, provides a link to a public VCS repository (see <xref "
-"linkend=\"servers-vcs\"/>) where the package is maintained."
+"puts it online somewhere (like on <ulink url=\"http://mentors.debian.net/cgi-"
+"bin/welcome\">mentors.debian.net</ulink>) or even better, provides a link to "
+"a public VCS repository (see <xref linkend=\"servers-vcs\"/>) where the "
+"package is maintained."
msgstr ""
#. type: Content of: <chapter><section><section><para><orderedlist><listitem><para>
#. type: Content of: <chapter><section><section><para>
#: beyond-pkging.dbk:337
msgid ""
-"The process of sponsoring a package is: <placeholder type=\"orderedlist\" "
-"id=\"0\"/>"
+"The process of sponsoring a package is: <placeholder type=\"orderedlist\" id="
+"\"0\"/>"
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: beyond-pkging.dbk:396
msgid ""
"Don't ever sponsor a new package without reviewing it. The review of new "
-"packages done by ftpmasters mainly ensures that the software is really "
-"free. Of course, it happens that they stumble on packaging problems but they "
+"packages done by ftpmasters mainly ensures that the software is really free. "
+"Of course, it happens that they stumble on packaging problems but they "
"really should not. It's your task to ensure that the uploaded package "
"complies with the Debian Free Software Guidelines and is of good quality."
msgstr ""
msgid ""
"Building the package and testing the software is part of the review, but "
"it's also not enough. The rest of this section contains a non-exhaustive "
-"list of points to check in your review. <placeholder type=\"footnote\" "
-"id=\"0\"/>"
+"list of points to check in your review. <placeholder type=\"footnote\" id="
+"\"0\"/>"
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
#: beyond-pkging.dbk:421
msgid ""
"Run <command>lintian</command> (see <xref linkend=\"lintian\"/>). It will "
-"catch many common problems. Be sure to verify that any "
-"<command>lintian</command> overrides setup by the maintainer is fully "
-"justified."
+"catch many common problems. Be sure to verify that any <command>lintian</"
+"command> overrides setup by the maintainer is fully justified."
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
#: beyond-pkging.dbk:448
msgid ""
"Proofread the maintainer scripts (<filename>preinst</filename>, "
-"<filename>postinst</filename>, <filename>prerm</filename>, "
-"<filename>postrm</filename>, <filename>config</filename>): will the "
-"<filename>preinst</filename>/<filename>postrm</filename> work when the "
-"dependencies are not installed? Are all the scripts idempotent (i.e. can you "
-"run them multiple times without consequences)?"
+"<filename>postinst</filename>, <filename>prerm</filename>, <filename>postrm</"
+"filename>, <filename>config</filename>): will the <filename>preinst</"
+"filename>/<filename>postrm</filename> work when the dependencies are not "
+"installed? Are all the scripts idempotent (i.e. can you run them multiple "
+"times without consequences)?"
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
#: beyond-pkging.dbk:456
msgid ""
-"Review any change to upstream files (either in "
-"<filename>.diff.gz</filename>, or in <filename>debian/patches/</filename> or "
-"directly embedded in the <filename>debian</filename> tarball for binary "
-"files). Are they justified? Are they properly documented (with <ulink "
-"url=\"&url-dep3;\">DEP-3</ulink> for patches)?"
+"Review any change to upstream files (either in <filename>.diff.gz</"
+"filename>, or in <filename>debian/patches/</filename> or directly embedded "
+"in the <filename>debian</filename> tarball for binary files). Are they "
+"justified? Are they properly documented (with <ulink url=\"&url-dep3;"
+"\">DEP-3</ulink> for patches)?"
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
"If the audit did not reveal any problem, you can build the package and "
"upload it to Debian. Remember that even if you're not the maintainer, the "
"sponsor is still responsible of what he uploaded to Debian. That's why "
-"you're encouraged to keep up with the package through the <xref "
-"linkend=\"pkg-tracking-system\"/>."
+"you're encouraged to keep up with the package through the <xref linkend="
+"\"pkg-tracking-system\"/>."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
msgid ""
"Note that you should not need to modify the source package to put your name "
"in the <filename>changelog</filename> or in the <filename>control</filename> "
-"file. 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. That way "
-"she will get all the BTS mail."
+"file. 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. That way she will get all the BTS "
+"mail."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
#: beyond-pkging.dbk:510
msgid ""
"To be able to analyze the difference you need both versions. Download the "
-"current version of the source package (with <command>apt-get "
-"source</command>) and rebuild it (or download the current binary packages "
-"with <command>aptitude download</command>). Download the source package to "
+"current version of the source package (with <command>apt-get source</"
+"command>) and rebuild it (or download the current binary packages with "
+"<command>aptitude download</command>). Download the source package to "
"sponsor (usually with <command>dget</command>)."
msgstr ""
"the <systemitem role=\"package\">devscripts</systemitem> package), you can "
"run it with two source packages (<filename>.dsc</filename> files), or two "
"binary packages, or two <filename>.changes</filename> files (it will then "
-"compare all the binary packages listed in the "
-"<filename>.changes</filename>)."
+"compare all the binary packages listed in the <filename>.changes</filename>)."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
msgid ""
"If you compare the source packages (excluding upstream files in the case of "
"a new upstream version, for example by filtering the output of "
-"<command>debdiff</command> with <command>filterdiff -i "
-"'*/debian/*'</command>), you must understand all the changes you see and "
-"they should be properly documented in the Debian changelog."
+"<command>debdiff</command> with <command>filterdiff -i '*/debian/*'</"
+"command>), you must understand all the changes you see and they should be "
+"properly documented in the Debian changelog."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
#. type: Content of: <chapter><section><section><section><para>
#: beyond-pkging.dbk:537
msgid ""
-"You might want to check out the Package Tracking System (see <xref "
-"linkend=\"pkg-tracking-system\"/>) to verify if the maintainer has not "
-"missed something important. Maybe there are translations updates sitting in "
-"the BTS that could have been integrated. Maybe the package has been NMUed "
-"and the maintainer forgot to integrate the changes from the NMU in his "
-"package. Maybe there's a release critical bug that he has left unhandled and "
-"that's blocking migration to <literal>testing</literal>. Whatever. If you "
-"find something that she could have done (better), it's time to tell her so "
-"that she can improve for next time, and so that she has a better "
-"understanding of her responsibilities."
+"You might want to check out the Package Tracking System (see <xref linkend="
+"\"pkg-tracking-system\"/>) to verify if the maintainer has not missed "
+"something important. Maybe there are translations updates sitting in the BTS "
+"that could have been integrated. Maybe the package has been NMUed and the "
+"maintainer forgot to integrate the changes from the NMU in his package. "
+"Maybe there's a release critical bug that he has left unhandled and that's "
+"blocking migration to <literal>testing</literal>. Whatever. If you find "
+"something that she could have done (better), it's time to tell her so that "
+"she can improve for next time, and so that she has a better understanding of "
+"her responsibilities."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
~ianmdlvl / developers-reference.git / blobdiff