msgstr ""
"Project-Id-Version: best-pkging-practices\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2008-08-08 11:43-0300\n"
+"POT-Creation-Date: 2009-01-23 09:48+0100\n"
"PO-Revision-Date: 2009-01-20 19:42+0100\n"
"Last-Translator: Christian Perrier <bubulle@debian.org>\n"
"Language-Team: French <debian-l10n-french@lists.debian.org>\n"
# type: Content of: <chapter><section><title>
#: best-pkging-practices.dbk:24
msgid "Best practices for <filename>debian/rules</filename>"
-msgstr "Les meilleures pratiques pour le fichier <filename>debian/rules</filename>"
+msgstr ""
+"Les meilleures pratiques pour le fichier <filename>debian/rules</filename>"
# type: Content of: <chapter><section><para>
#: best-pkging-practices.dbk:26
# type: Content of: <chapter><section><section><section><para>
#: best-pkging-practices.dbk:757
+#, fuzzy
msgid ""
"Avoid changing templates too often. Changing templates text induces more "
-"work to translators which will get their translation fuzzied. If you plan "
-"changes to your original templates, please contact translators. Most active "
-"translators are very responsive and getting their work included along with "
-"your modified templates will save you additional uploads. If you use "
-"gettext-based templates, the translator's name and e-mail addresses are "
-"mentioned in the po files headers."
+"work to translators which will get their translation fuzzied. A fuzzy "
+"translation is a string for which the original changed since it was "
+"translated, therefore requiring some update by a translator to be usable. "
+"When changes are small enough, the original translation is kept in PO files "
+"but marked as <literal>fuzzy</literal>."
msgstr ""
"Évitez de changer les écrans trop souvent. La modification des textes des "
"écrans impacte les traducteurs dont les traductions vont devenir "
"fichiers PO."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:766
+#: best-pkging-practices.dbk:765
+#, fuzzy
+msgid ""
+"If you plan to do changes to your original templates, please use the "
+"notification system provided with the <systemitem role=\"package\">po-"
+"debconf</systemitem> package, namely the <command> podebconf-report-po</"
+"command>, to contact translators. Most active translators are very "
+"responsive and getting their work included along with your modified "
+"templates will save you additional uploads. If you use gettext-based "
+"templates, the translator's name and e-mail addresses are mentioned in the "
+"PO files headers and will be used by <command> podebconf-report-po</command>."
+msgstr ""
+"Évitez de changer les écrans trop souvent. La modification des textes des "
+"écrans impacte les traducteurs dont les traductions vont devenir "
+"« floues » (« fuzzy »). Si vous prévoyez des modifications aux écrans "
+"d'origine, veuillez contacter les traducteurs. La plupart d'entre eux sont "
+"réactifs et inclure des mises à jour en même temps que les modifications aux "
+"écrans d'origine vous évitera des envois ultérieurs pour la mise à jour des "
+"traductions. Si vous utilisez des écrans se servant de gettext, le nom et "
+"l'adresse électronique des traducteurs sont mentionnés dans les en-têtes des "
+"fichiers PO."
+
+# type: Content of: <chapter><section><section><section><para>
+#: best-pkging-practices.dbk:777
+msgid "A recommended use of that utility is:"
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><programlisting>
+#: best-pkging-practices.dbk:779
+#, no-wrap
+msgid "cd debian/po && podebconf-report-po --languageteam --withtranslators --call --deadline=\"+10 days\""
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><para>
+#: best-pkging-practices.dbk:781
msgid ""
-"The use of the <command>podebconf-report-po</command> from the <systemitem "
-"role=\"package\">po-debconf</systemitem> package is highly recommended to "
-"warn translators which have incomplete translations and request them for "
-"updates."
+"This command will first synchronize the PO and POT files in debian/po with "
+"the templates files listed in <filename>debian/po/POTFILES.in</filename>. "
+"Then, it will send a call for translation updates to the language team "
+"(mentioned in the <literal>Language-Team</literal> field of each PO file) "
+"as well as the last translator (mentioned in <literal>Last-translator</"
+"literal>). Finally, it will also send a call for new translations, in the "
+"&email-debian-i18n; mailing list."
msgstr ""
-"L'utilisation de la commande <command>podebconf-report-po</command> fournie "
-"par le paquet <systemitem role=\"package\">po-debconf</systemitem> est "
-"fortement recommandée pour avertir les traducteurs dont les traductions sont "
-"incomplètes et leur demander de les mettre à jour."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:771
+#: best-pkging-practices.dbk:790
+msgid ""
+"Giving a deadline to translators is always appreciated, so that they can "
+"organize their work. Please remember that some translation teams have a "
+"formalized translate/review process and a delay lower than 10 days is "
+"considered as unreasonable. A shorter delay puts too much pressure on "
+"translation teams and should be kept for very minor changes."
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><para>
+#: best-pkging-practices.dbk:797
msgid ""
"If in doubt, you may also contact the translation team for a given language "
"(debian-l10n-xxxxx@&lists-host;), or the &email-debian-i18n; mailing list."
"langue donnée (debian-l10n-xxxxx@&lists-host;) ou la liste de diffusion "
"&email-debian-i18n;."
-# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:776
-msgid ""
-"Calls for translations posted to &email-debian-i18n; with the "
-"<filename>debian/po/templates.pot</filename> file attached or referenced in "
-"a URL are encouraged. Be sure to mentions in these calls for new "
-"translations which languages you have existing translations for, in order to "
-"avoid duplicate work."
-msgstr ""
-"Des appels à traductions envoyés dans &email-debian-i18n;, avec le fichier "
-"<filename>debian/po/templates.pot</filename> attaché sont encouragés. "
-"Veuillez vous assurer de bien mentionner dans ces appels à traductions les "
-"langues pour lesquelles des traductions existent déjà, afin d'éviter du "
-"travail en double."
-
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:785
+#: best-pkging-practices.dbk:804
msgid "Unfuzzy complete translations when correcting typos and spelling"
msgstr ""
"Correction (« unfuzzy ») des traductions complètes lors des corrections de "
"fautes de frappe ou d'orthographe"
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:787
+#: best-pkging-practices.dbk:806
+#, fuzzy
msgid ""
"When the text of a debconf template is corrected and you are <emphasis role="
"\"strong\">sure</emphasis> that the change does <emphasis role=\"strong"
"\">not</emphasis> affect translations, please be kind to translators and "
-"unfuzzy their translations."
+"<emphasis>unfuzzy</emphasis> their translations."
msgstr ""
"Lorsque le texte d'un écran de debconf est corrigé et que vous avec la "
"<emphasis role=\"strong\">certitude</emphasis> que la modification n'affecte "
"traducteurs et rendez leur translations à nouveau complètes (« unfuzzy »)."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:793
+#: best-pkging-practices.dbk:812
msgid ""
"If you don't do so, the whole template will not be translated as long as a "
"translator will send you an update."
"tant qu'un traducteur n'aura pas réenvoyé un fichier corrigé."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:797
+#: best-pkging-practices.dbk:816
msgid ""
-"To <literal>unfuzzy</literal> translations, you can proceed the following "
-"way:"
-msgstr "Pour corriger les traductions, vous pouvez procéder de la manière suivante :"
+"To <emphasis>unfuzzy</emphasis> translations, you can use two methods. The "
+"first method does <emphasis>preventive</emphasis> search and replace actions "
+"in the PO files. The latter uses <command>gettext</command> utilities to "
+"<emphasis>unfuzzy</emphasis> strings."
+msgstr ""
-# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:803
+# type: Content of: <chapter><section><section><section><para>
+#: best-pkging-practices.dbk:822
+msgid "<emphasis>Preventive unfuzzy</emphasis> method:"
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><para>
+#: best-pkging-practices.dbk:827
+#, fuzzy
msgid ""
-"Put all incomplete PO files out of the way. You can check the completeness "
-"by using (needs the <systemitem role=\"package\">gettext</systemitem> "
-"package installed):"
+"Try finding a complete translation file <emphasis role=\"strong\"> before</"
+"emphasis> the change:"
msgstr ""
-"Déplacez les fichiers PO incomplets à un endroit temporaire. Les fichiers "
-"peuvent être contrôlés avec la commande suivante (qui nécessite "
-"l'installation du paquet <systemitem role=\"package\">gettext</systemitem>) :"
+"La partie longue de la description ne devrait <emphasis role=\"strong"
+"\">jamais</emphasis> comporter de question."
# type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting>
-#: best-pkging-practices.dbk:807
+#: best-pkging-practices.dbk:830 best-pkging-practices.dbk:900
#, no-wrap
msgid ""
"for i in debian/po/*po; do echo -n $i: ; msgfmt -o /dev/null\n"
"--statistics $i; done"
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:812
+#: best-pkging-practices.dbk:833
+msgid ""
+"The file only showing <emphasis>translated</emphasis> items will be used as "
+"the reference file. If there is none (which should not happen if you take "
+"care to properly interact with translators), you should use the file with "
+"the most translated strings."
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
+#: best-pkging-practices.dbk:841
+msgid ""
+"Identify the needed change. In this example, let's assume the change is "
+"about fixing a typo in the word <literal>typo</literal> which was "
+"inadvertently written as <literal>tpyo</literal>. Therefore, the change is "
+"<command>s/tpyo/typo</command>."
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
+#: best-pkging-practices.dbk:849
+msgid ""
+"Check that this change is only applied to the place where you really intend "
+"to make it and <emphasis role=\"strong\">not</emphasis> in any other place "
+"where the original string is appropriate. This specifically applies to "
+"change in punctuation, for instance."
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
+#: best-pkging-practices.dbk:857
+msgid ""
+"Modify all PO files by using <command>sed</command>. The use of that command "
+"is recommended over any text editor to guarantee that the files encoding "
+"will not be broken by the edit action."
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting>
+#: best-pkging-practices.dbk:861
+#, no-wrap
+msgid ""
+"\n"
+"cd debian/po\n"
+"for i in *.po; do sed -i 's/tpyo/typo/g' $i; done\n"
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
+#: best-pkging-practices.dbk:868
+msgid "Change the debconf template file to fix the typo."
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
+#: best-pkging-practices.dbk:873
+#, fuzzy
+msgid "Run <command>debconf-updatepo</command>"
+msgstr "exécutez la commande <command>debconf-updatepo</command> à nouveau"
+
+# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
+#: best-pkging-practices.dbk:878
+msgid ""
+"Check the <filename>foo.po</filename> reference file. Its statistics should "
+"not be changed:"
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting>
+#: best-pkging-practices.dbk:881
+#, no-wrap
+msgid ""
+"\n"
+"msgfmt -o /dev/null --statistics debian/po/foo.po\n"
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><para>
+#: best-pkging-practices.dbk:891
+msgid "Gettext utilities method:"
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
+#: best-pkging-practices.dbk:896
+msgid ""
+"Put all incomplete PO files out of the way. You can check the completeness "
+"by using (needs the <systemitem role=\"package\">gettext</systemitem> "
+"package installed):"
+msgstr ""
+"Déplacez les fichiers PO incomplets à un endroit temporaire. Les fichiers "
+"peuvent être contrôlés avec la commande suivante (qui nécessite "
+"l'installation du paquet <systemitem role=\"package\">gettext</systemitem>) :"
+
+# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
+#: best-pkging-practices.dbk:905
msgid ""
"move all files which report either fuzzy strings to a temporary place. "
"Files which report no fuzzy strings (only translated and untranslated) will "
"être laissés en place."
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:819
+#: best-pkging-practices.dbk:912
msgid ""
"now <emphasis role=\"strong\">and now only</emphasis>, modify the template "
"for the typos and check again that translation are not impacted (typos, "
"général pas de problèmes)."
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:826
+#: best-pkging-practices.dbk:919
msgid ""
"run <command>debconf-updatepo</command>. This will fuzzy all strings you "
"modified in translations. You can see this by running the above again"
"être contrôlé avec la commande ci-dessus à nouveau."
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:832
+#: best-pkging-practices.dbk:925
msgid "use the following command:"
msgstr "utilisez la commande suivante :"
# type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting>
-#: best-pkging-practices.dbk:834
+#: best-pkging-practices.dbk:927
#, no-wrap
msgid "for i in debian/po/*po; do msgattrib --output-file=$i --clear-fuzzy $i; done"
msgstr "for i in debian/po/*po; do msgattrib --output-file=$i --clear-fuzzy $i; done"
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:838
-msgid "move back to debian/po the files which showed fuzzy strings in the first step"
+#: best-pkging-practices.dbk:931
+msgid ""
+"move back to debian/po the files which showed fuzzy strings in the first step"
msgstr ""
"replacez à nouveau dans <filename>debian/po</filename> les fichiers "
"précédemment déplacés."
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:843
+#: best-pkging-practices.dbk:936
msgid "run <command>debconf-updatepo</command> again"
msgstr "exécutez la commande <command>debconf-updatepo</command> à nouveau"
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:850
+#: best-pkging-practices.dbk:943
msgid "Do not make assumptions about interfaces"
msgstr "Ne faites pas de suppositions sur les interfaces utilisateurs"
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:852
+#: best-pkging-practices.dbk:945
+#, fuzzy
msgid ""
"Templates text should not make reference to widgets belonging to some "
-"debconf interfaces. Sentences like If you answer Yes... have no meaning "
-"for users of graphical interfaces which use checkboxes for boolean questions."
+"debconf interfaces. Sentences like <emphasis>If you answer Yes...</"
+"emphasis> have no meaning for users of graphical interfaces which use "
+"checkboxes for boolean questions."
msgstr ""
"Les textes des écrans ne devraiernt pas faire référence aux éléments "
"disponibles sur certaines interfaces de debconf. Des phrases telles que « If "
"boutons radio sont utilisés pour les questions booléennes."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:857
+#: best-pkging-practices.dbk:950
msgid ""
"String templates should also avoid mentioning the default values in their "
"description. First, because this is redundant with the values seen by the "
"exemple, lorsque la base de données de debconf a été pré-renseignée)."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:863
+#: best-pkging-practices.dbk:956
msgid ""
"More generally speaking, try to avoid referring to user actions. Just give "
"facts."
"particulières des utilisateurs et donnez simplement des faits."
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:869
+#: best-pkging-practices.dbk:962
msgid "Do not use first person"
msgstr "N'utilisez pas la première personne"
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:871
-msgid ""
-"You should avoid the use of first person (I will do this... or We "
-"recommend...). The computer is not a person and the Debconf templates do "
-"not speak for the Debian developers. You should use neutral construction. "
-"Those of you who already wrote scientific publications, just write your "
-"templates like you would write a scientific paper. However, try using "
-"action voice if still possible, like Enable this if ... instead of This can "
-"be enabled if ...."
+#: best-pkging-practices.dbk:964
+#, fuzzy
+msgid ""
+"You should avoid the use of first person (<emphasis>I will do this...</"
+"emphasis> or <emphasis>We recommend...</emphasis>). The computer is not a "
+"person and the Debconf templates do not speak for the Debian developers. "
+"You should use neutral construction. Those of you who already wrote "
+"scientific publications, just write your templates like you would write a "
+"scientific paper. However, try using active voice if still possible, like "
+"<emphasis>Enable this if ...</emphasis> instead of <emphasis>This can be "
+"enabled if...</emphasis>."
msgstr ""
"Vous devriez éviter l'utilisation de la première personne (« Je vais faire "
"ceci » ou « Nous recommandons que... »). L'ordinateur n'est pas une personne "
"be enabled if... »."
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:881
+#: best-pkging-practices.dbk:974
msgid "Be gender neutral"
msgstr "Restez neutre en genre"
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:883
+#: best-pkging-practices.dbk:976
msgid ""
"The world is made of men and women. Please use gender-neutral constructions "
"in your writing."
-msgstr "Le monde est fait d'hommes et de femmes. Veuillez utiliser des constructions neutres en genre dans vos écrits."
+msgstr ""
+"Le monde est fait d'hommes et de femmes. Veuillez utiliser des constructions "
+"neutres en genre dans vos écrits."
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:891
+#: best-pkging-practices.dbk:984
msgid "Templates fields definition"
msgstr "Définition de champs des modèles (« templates »)"
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:893
+#: best-pkging-practices.dbk:986
msgid ""
"This part gives some information which is mostly taken from the "
"<citerefentry> <refentrytitle>debconf-devel</refentrytitle> <manvolnum>7</"
"manvolnum> </citerefentry> manual page."
msgstr ""
-"Les informations présentées dans cette partie proviennent pour l'essentiel de la page de manuel <citerefentry> <refentrytitle>debconf-devel</refentrytitle> <manvolnum>7</"
-"manvolnum> </citerefentry>"
+"Les informations présentées dans cette partie proviennent pour l'essentiel "
+"de la page de manuel <citerefentry> <refentrytitle>debconf-devel</"
+"refentrytitle> <manvolnum>7</manvolnum> </citerefentry>"
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:898
+#: best-pkging-practices.dbk:991
msgid "Type"
msgstr "Type"
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:900
+#: best-pkging-practices.dbk:993
msgid "string:"
msgstr "string:"
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:902
-msgid "Results in a free-form input field that the user can type any string into."
-msgstr "offre un champ de saisie où l'utilisateur peut entrer n'importe quelle chaîne de caractère."
+#: best-pkging-practices.dbk:995
+msgid ""
+"Results in a free-form input field that the user can type any string into."
+msgstr ""
+"offre un champ de saisie où l'utilisateur peut entrer n'importe quelle "
+"chaîne de caractère."
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:907
+#: best-pkging-practices.dbk:1000
msgid "password:"
msgstr "password:"
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:909
+#: best-pkging-practices.dbk:1002
msgid ""
"Prompts the user for a password. Use this with caution; be aware that the "
"password the user enters will be written to debconf's database. You should "
"probably clean that value out of the database as soon as is possible."
-msgstr "demande un mot de passe. Ce champ est à utiliser avec précaution car le mot de passe saisi sera conservé dans la base de données de debconf. Il est conseillé d'effacer cette valeur de la base de donnes dès que possible."
+msgstr ""
+"demande un mot de passe. Ce champ est à utiliser avec précaution car le mot "
+"de passe saisi sera conservé dans la base de données de debconf. Il est "
+"conseillé d'effacer cette valeur de la base de donnes dès que possible."
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:916
+#: best-pkging-practices.dbk:1009
msgid "boolean:"
msgstr "boolean:"
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:918
+#: best-pkging-practices.dbk:1011
msgid ""
"A true/false choice. Remember: true/false, <emphasis role=\"strong\">not "
"yes/no</emphasis>..."
-msgstr "offre un choix vrai/faux. Veuillez noter que c'est bien d'un choix vrai/faux, <emphasis role=\"strong\">pas oui/non</emphasis>..."
+msgstr ""
+"offre un choix vrai/faux. Veuillez noter que c'est bien d'un choix vrai/"
+"faux, <emphasis role=\"strong\">pas oui/non</emphasis>..."
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:924
+#: best-pkging-practices.dbk:1017
msgid "select:"
msgstr "select:"
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:926
+#: best-pkging-practices.dbk:1019
+#, fuzzy
msgid ""
"A choice between one of a number of values. The choices must be specified "
"in a field named 'Choices'. Separate the possible values with commas and "
-"spaces, like this: Choices: yes, no, maybe"
-msgstr "offre le choix entre différentes valeurs. Les choix doivent être indiqués dans un champ appelé « Choices ». Les différentes valeurs doivent être séparées par des virgules et des espace. Ainsi : yes, no, maybe"
+"spaces, like this: <literal>Choices: yes, no, maybe</literal>."
+msgstr ""
+"offre le choix entre différentes valeurs. Les choix doivent être indiqués "
+"dans un champ appelé « Choices ». Les différentes valeurs doivent être "
+"séparées par des virgules et des espace. Ainsi : yes, no, maybe"
+
+# type: Content of: <chapter><section><section><section><section><para>
+#: best-pkging-practices.dbk:1024
+msgid ""
+"If choices are translatable strings, the 'Choices' field may be marked as "
+"translatable by using <literal>__Choices</literal>. The double underscore "
+"will split out each choice in a separate string."
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><section><para>
+#: best-pkging-practices.dbk:1029
+msgid ""
+"The <command>po-debconf</command> system also offers interesting "
+"possibilities to only mark <emphasis role=\"strong\">some</emphasis> choices "
+"as translatable. Example:"
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><section><programlisting>
+#: best-pkging-practices.dbk:1033
+#, no-wrap
+msgid ""
+"\n"
+"Template: foo/bar\n"
+"Type: Select\n"
+"#flag:translate:3\n"
+"__Choices: PAL, SECAM, Other\n"
+"_Description: TV standard:\n"
+" Please choose the TV standard used in your country.\n"
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><section><para>
+#: best-pkging-practices.dbk:1042
+msgid ""
+"In that example, only the 'Other' string is translatable while others are "
+"acronyms that should not be translated. The above allows only 'Other' to be "
+"included in PO and POT files."
+msgstr ""
+
+# type: Content of: <chapter><section><section><para>
+#: best-pkging-practices.dbk:1047
+#, fuzzy
+msgid ""
+"The debconf templates flag system offers many such possibilities. The "
+"<citerefentry> <refentrytitle>po-debconf</refentrytitle> <manvolnum>7</"
+"manvolnum> </citerefentry> manual page lists all these possibilities."
+msgstr ""
+"Les informations présentées dans cette partie proviennent pour l'essentiel "
+"de la page de manuel <citerefentry> <refentrytitle>debconf-devel</"
+"refentrytitle> <manvolnum>7</manvolnum> </citerefentry>"
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:933
+#: best-pkging-practices.dbk:1055
msgid "multiselect:"
msgstr "multiselect:"
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:935
+#: best-pkging-practices.dbk:1057
msgid ""
"Like the select data type, except the user can choose any number of items "
"from the choices list (or chose none of them)."
-msgstr "similaire au type « select », mais permet de choisir plusieurs (ou aucune) valeurs parmi la liste de choix."
+msgstr ""
+"similaire au type « select », mais permet de choisir plusieurs (ou aucune) "
+"valeurs parmi la liste de choix."
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:941
+#: best-pkging-practices.dbk:1063
msgid "note:"
msgstr "note:"
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:943
+#: best-pkging-practices.dbk:1065
msgid ""
"Rather than being a question per se, this datatype indicates a note that can "
"be displayed to the user. It should be used only for important notes that "
"the user really should see, since debconf will go to great pains to make "
"sure the user sees it; halting the install for them to press a key, and even "
"mailing the note to them in some cases."
-msgstr "plus qu'une vraie question, ce type indique une note affichée aux utilisateurs. Elle doit être réservée à des informations importantes que l'utilisateur doit absolument voir, car debconf fera tout pour s'assurer qu'elle est visible et notamment interrompra l'installation en attente qu'une touche soit appuyée, voire envoyer la note par courrier électronique dans certains cas."
+msgstr ""
+"plus qu'une vraie question, ce type indique une note affichée aux "
+"utilisateurs. Elle doit être réservée à des informations importantes que "
+"l'utilisateur doit absolument voir, car debconf fera tout pour s'assurer "
+"qu'elle est visible et notamment interrompra l'installation en attente "
+"qu'une touche soit appuyée, voire envoyer la note par courrier électronique "
+"dans certains cas."
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:952
+#: best-pkging-practices.dbk:1074
msgid "text:"
msgstr "text:"
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:954
+#: best-pkging-practices.dbk:1076
msgid "This type is now considered obsolete: don't use it."
msgstr "ce type de données est obsolète. Il ne faut pas l'utiliser."
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:959
+#: best-pkging-practices.dbk:1081
msgid "error:"
msgstr "error:"
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:961
+#: best-pkging-practices.dbk:1083
msgid ""
"This type is designed to handle error messages. It is mostly similar to the "
"note type. Frontends may present it differently (for instance, the dialog "
"frontend of cdebconf draws a red screen instead of the usual blue one)."
-msgstr "ce type permet de gérer des messages d'erreur. Il est analogue au type « note ». Les interfaces utilisateur peuvent le présenter différemment (ainsi l'interface « dialog » dessine un écran à fond rouge au lieu de l'écran bleu habituel)."
+msgstr ""
+"ce type permet de gérer des messages d'erreur. Il est analogue au type "
+"« note ». Les interfaces utilisateur peuvent le présenter différemment (ainsi "
+"l'interface « dialog » dessine un écran à fond rouge au lieu de l'écran bleu "
+"habituel)."
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:966
+#: best-pkging-practices.dbk:1088
msgid ""
"It is recommended to use this type for any message that needs user attention "
"for a correction of any kind."
-msgstr "Il est recommandé d'utiliser ce type pour tout message qui requiert l'attention de l'utilisateur pour procéder à une correction, quelle qu'elle soit."
+msgstr ""
+"Il est recommandé d'utiliser ce type pour tout message qui requiert "
+"l'attention de l'utilisateur pour procéder à une correction, quelle qu'elle "
+"soit."
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:974
+#: best-pkging-practices.dbk:1096
msgid "Description: short and extended description"
msgstr "Description: description courte et étendue"
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:976
+#: best-pkging-practices.dbk:1098
msgid ""
"Template descriptions have two parts: short and extended. The short "
"description is in the Description: line of the template."
-msgstr "Les descriptions de modèles comportent deux parties : la partie courte et la partie étendue. La partie courte est celle qui est placée sur la ligne «Description: » du modèle."
+msgstr ""
+"Les descriptions de modèles comportent deux parties : la partie courte et la "
+"partie étendue. La partie courte est celle qui est placée sur la ligne "
+" «Description: » du modèle."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:980
+#: best-pkging-practices.dbk:1102
msgid ""
"The short description should be kept short (50 characters or so) so that it "
"may be accomodated by most debconf interfaces. Keeping it short also helps "
"translators, as usually translations tend to end up being longer than the "
"original."
-msgstr "La partie courte doit rester courte (environ 50 caractères) afin de pouvoir être gérée par la majorité des interfaces de debconf. La garder courte facilite également le travail des traducteurs car les traductions sont en général plus longues que les textes originaux."
+msgstr ""
+"La partie courte doit rester courte (environ 50 caractères) afin de pouvoir "
+"être gérée par la majorité des interfaces de debconf. La garder courte "
+"facilite également le travail des traducteurs car les traductions sont en "
+"général plus longues que les textes originaux."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:986
+#: best-pkging-practices.dbk:1108
msgid ""
"The short description should be able to stand on its own. Some interfaces "
"do not show the long description by default, or only if the user explicitely "
"asks for it or even do not show it at all. Avoid things like What do you "
"want to do?"
-msgstr "La description courte doit être autonome. Certaines interfaces ne montrent pas la description longue par défaut ou ne la montrent que si l'utilisateur le demande explicitement. Il est ainsi déconseillé d'utiliser des phrases comme « Que voulez-vous faire maintenant ? »"
+msgstr ""
+"La description courte doit être autonome. Certaines interfaces ne montrent "
+"pas la description longue par défaut ou ne la montrent que si l'utilisateur "
+"le demande explicitement. Il est ainsi déconseillé d'utiliser des phrases "
+"comme « Que voulez-vous faire maintenant ? »"
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:992
+#: best-pkging-practices.dbk:1114
msgid ""
"The short description does not necessarily have to be a full sentence. This "
"is part of the keep it short and efficient recommendation."
-msgstr "La description courte ne doit pas nécessairement être une phrase entière. Cela est une façon de la garder courte et efficace."
+msgstr ""
+"La description courte ne doit pas nécessairement être une phrase entière. "
+"Cela est une façon de la garder courte et efficace."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:996
+#: best-pkging-practices.dbk:1118
msgid ""
"The extended description should not repeat the short description word for "
"word. If you can't think up a long description, then first, think some "
"more. Post to debian-devel. Ask for help. Take a writing class! That "
"extended description is important. If after all that you still can't come "
"up with anything, leave it blank."
-msgstr "La partie longue ne doit pas répéter la partie courte. Si vous ne trouvez pas de partie longue appropriée, réfléchissez un peu plus. Demandez dans debian-devel. Demandez de l'aide. Prenez un cours d'écriture ! La description longue est importante..et si, malgré tout cela, vous ne trouvez rien d'intéressant à ajouter, laissez-la vide."
+msgstr ""
+"La partie longue ne doit pas répéter la partie courte. Si vous ne trouvez "
+"pas de partie longue appropriée, réfléchissez un peu plus. Demandez dans "
+"debian-devel. Demandez de l'aide. Prenez un cours d'écriture ! La "
+"description longue est importante..et si, malgré tout cela, vous ne trouvez "
+"rien d'intéressant à ajouter, laissez-la vide."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1003
+#: best-pkging-practices.dbk:1125
msgid ""
"The extended description should use complete sentences. Paragraphs should "
"be kept short for improved readability. Do not mix two ideas in the same "
"paragraph but rather use another paragraph."
-msgstr "La partie longue doit utiliser des phrases complètes. Les paragraphes doivent rester courts pour améliorer la lisibilité. Ne placez pas deux idées différentes dans le même paragraphe mais séparez-les en deux paragraphes."
+msgstr ""
+"La partie longue doit utiliser des phrases complètes. Les paragraphes "
+"doivent rester courts pour améliorer la lisibilité. Ne placez pas deux idées "
+"différentes dans le même paragraphe mais séparez-les en deux paragraphes."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1008
+#: best-pkging-practices.dbk:1130
msgid ""
"Don't be too verbose. User tend to ignore too long screens. 20 lines are "
"by experience a border you shouldn't cross, because that means that in the "
"classical dialog interface, people will need to scroll, and lot of people "
"just don't do that."
-msgstr "Ne soyez pas trop verbeux. Les utilisateurs ont tendance à ne pas lire les écrans trop longs. Un maximum de 20 lignes est une limite que vous ne devriez pas dépasser car, avec l'interface standard « dialog », les utilisateurs devront monter et descendre avec des ascenseurs, ce qui sera omis par la plupart des utilisateurs."
+msgstr ""
+"Ne soyez pas trop verbeux. Les utilisateurs ont tendance à ne pas lire les "
+"écrans trop longs. Un maximum de 20 lignes est une limite que vous ne "
+"devriez pas dépasser car, avec l'interface standard « dialog », les "
+"utilisateurs devront monter et descendre avec des ascenseurs, ce qui sera "
+"omis par la plupart des utilisateurs."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1014
+#: best-pkging-practices.dbk:1136
msgid ""
"The extended description should <emphasis role=\"strong\">never</emphasis> "
"include a question."
msgstr ""
-"La partie longue de la description ne devrait <emphasis role=\"strong\">jamais</emphasis> "
-"comporter de question."
+"La partie longue de la description ne devrait <emphasis role=\"strong"
+"\">jamais</emphasis> comporter de question."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1018
+#: best-pkging-practices.dbk:1140
msgid ""
"For specific rules depending on templates type (string, boolean, etc.), "
"please read below."
-msgstr "Les parties qui suivent donnent des recommandations spécifiques pour certains types de modèles (string, boolean, etc.)."
+msgstr ""
+"Les parties qui suivent donnent des recommandations spécifiques pour "
+"certains types de modèles (string, boolean, etc.)."
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1024
+#: best-pkging-practices.dbk:1146
msgid "Choices"
msgstr "Choices"
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1026
+#: best-pkging-practices.dbk:1148
msgid ""
"This field should be used for Select and Multiselect types. It contains the "
"possible choices which will be presented to users. These choices should be "
"separated by commas."
-msgstr "Ce champ doit être utilisé pour les types Select et Multiselect. Il contient les choix proposés aux utilisateurs. Ces choix doivent être séparés par des virgules."
+msgstr ""
+"Ce champ doit être utilisé pour les types Select et Multiselect. Il contient "
+"les choix proposés aux utilisateurs. Ces choix doivent être séparés par des "
+"virgules."
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1033
+#: best-pkging-practices.dbk:1155
msgid "Default"
msgstr "Default"
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1035
+#: best-pkging-practices.dbk:1157
msgid ""
"This field is optional. It contains the default answer for string, select "
"and multiselect templates. For multiselect templates, it may contain a "
"comma-separated list of choices."
-msgstr "Ce champ optionnel contient la réponse par défaut pour les modèles string, select et multiselect. Dans ce dernier cas, il peut comporter une liste de choix multiples, séparés par des virgules."
+msgstr ""
+"Ce champ optionnel contient la réponse par défaut pour les modèles string, "
+"select et multiselect. Dans ce dernier cas, il peut comporter une liste de "
+"choix multiples, séparés par des virgules."
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1044
+#: best-pkging-practices.dbk:1166
msgid "Templates fields specific style guide"
msgstr "Guide de style spécifique à certains modèles"
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1046
+#: best-pkging-practices.dbk:1168
msgid "Type field"
msgstr "Champ type"
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1048
+#: best-pkging-practices.dbk:1170
msgid ""
"No specific indication except: use the appropriate type by referring to the "
"previous section."
-msgstr "Pas d'indication particulière si ce n'est choisir le type adapté en se référant à la section précédente."
+msgstr ""
+"Pas d'indication particulière si ce n'est choisir le type adapté en se "
+"référant à la section précédente."
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1054
+#: best-pkging-practices.dbk:1176
msgid "Description field"
msgstr "Champ Description"
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1056
+#: best-pkging-practices.dbk:1178
msgid ""
"Below are specific instructions for properly writing the Description (short "
"and extended) depending on the template type."
-msgstr "Vous trouverez ici des instruction particulières pour l'écriture du champ Description (parties courtes et longue) selon le type de modèle."
+msgstr ""
+"Vous trouverez ici des instruction particulières pour l'écriture du champ "
+"Description (parties courtes et longue) selon le type de modèle."
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:1060
+#: best-pkging-practices.dbk:1182
msgid "String/password templates"
msgstr "Modèles string et password"
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1064
+#: best-pkging-practices.dbk:1186
msgid ""
"The short description is a prompt and <emphasis role=\"strong\">not</"
"emphasis> a title. Avoid question style prompts (IP Address?) in favour of "
"opened prompts (IP address:). The use of colons is recommended."
msgstr ""
"La description courte est une invite et <emphasis role=\"strong\">pas</"
-"emphasis> un titre. Il faut éviter la forme interrogative (« Adresse IP ? ») et préférer une invite ouverte (« Adresse IP : »). L'utilisation d'un « deux-points » final est recommandée."
+"emphasis> un titre. Il faut éviter la forme interrogative (« Adresse IP ? ») "
+"et préférer une invite ouverte (« Adresse IP : »). L'utilisation d'un « deux-"
+"points » final est recommandée."
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1071
+#: best-pkging-practices.dbk:1193
msgid ""
"The extended description is a complement to the short description. In the "
"extended part, explain what is being asked, rather than ask the same "
"question again using longer words. Use complete sentences. Terse writing "
"style is strongly discouraged."
-msgstr "La partie longue complète la partie courte. Il est conseillé d'y expliquer ce qui est demandé, plutôt que répéter la même demande. Utilisez des phrases complètes. Un style d'écriture abrégé est déconseillé."
+msgstr ""
+"La partie longue complète la partie courte. Il est conseillé d'y expliquer "
+"ce qui est demandé, plutôt que répéter la même demande. Utilisez des phrases "
+"complètes. Un style d'écriture abrégé est déconseillé."
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:1081
+#: best-pkging-practices.dbk:1203
msgid "Boolean templates"
msgstr "Modèles « boolean »"
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1085
+#: best-pkging-practices.dbk:1207
msgid ""
"The short description should be phrased in the form of a question which "
"should be kept short and should generally end with a question mark. Terse "
"writing style is permitted and even encouraged if the question is rather "
"long (remember that translations are often longer than original versions)"
-msgstr "La partie courte doit utiliser la forme interrogative et se terminer par un point d'interrogation. Un style abrégé est toléré et même encouragé si la question est complexe (les traductions vont être plus longues que la version originale)."
+msgstr ""
+"La partie courte doit utiliser la forme interrogative et se terminer par un "
+"point d'interrogation. Un style abrégé est toléré et même encouragé si la "
+"question est complexe (les traductions vont être plus longues que la version "
+"originale)."
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1093
+#: best-pkging-practices.dbk:1215
msgid ""
"Again, please avoid referring to specific interface widgets. A common "
"mistake for such templates is if you answer Yes-type constructions."
-msgstr "Il est important d'éviter de faire référence aux objets de certains interfaces spécifiques. Une erreur classique est d'utiliser une construction comme « If you answer Yes... » (« Si vous répondez Oui... »)."
+msgstr ""
+"Il est important d'éviter de faire référence aux objets de certains "
+"interfaces spécifiques. Une erreur classique est d'utiliser une construction "
+"comme « If you answer Yes... » (« Si vous répondez Oui... »)."
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:1101
+#: best-pkging-practices.dbk:1223
msgid "Select/Multiselect"
msgstr "Select/Multiselect"
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1105
+#: best-pkging-practices.dbk:1227
msgid ""
"The short description is a prompt and <emphasis role=\"strong\">not</"
"emphasis> a title. Do <emphasis role=\"strong\">not</emphasis> use useless "
"have to choose something...:)"
msgstr ""
"La description courte est une invite et <emphasis role=\"strong\">pas</"
-"emphasis> un titre. N'utilisez <emphasis role=\"strong\">pas</emphasis> de constructions comme « Please choose... » (« Veuillez choisir... »). Les utilisateurs sont suffisamment intelligents pour comprendre qu'il est nécessaire de choisir quelque chose."
+"emphasis> un titre. N'utilisez <emphasis role=\"strong\">pas</emphasis> de "
+"constructions comme « Please choose... » (« Veuillez choisir... »). Les "
+"utilisateurs sont suffisamment intelligents pour comprendre qu'il est "
+"nécessaire de choisir quelque chose."
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1113
+#: best-pkging-practices.dbk:1235
msgid ""
"The extended description will complete the short description. It may refer "
"to the available choices. It may also mention that the user may choose more "
"than one of the available choices, if the template is a multiselect one "
"(although the interface often makes this clear)."
-msgstr "La description longue complète la partie courte. Elle peut faire référence aux choix disponibles. Elle peut également indiquer que l'utilisateur peut choisir plus d'un parmi les choix disponibles, dans le cas de modèles « multiselect » (bien que l'interface rende en général cela tout à fait clair)."
+msgstr ""
+"La description longue complète la partie courte. Elle peut faire référence "
+"aux choix disponibles. Elle peut également indiquer que l'utilisateur peut "
+"choisir plus d'un parmi les choix disponibles, dans le cas de modèles "
+"« multiselect » (bien que l'interface rende en général cela tout à fait "
+"clair)."
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:1123
+#: best-pkging-practices.dbk:1245
msgid "Notes"
msgstr "Notes"
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1127
+#: best-pkging-practices.dbk:1249
msgid "The short description should be considered to be a *title*."
msgstr "La description courte doit être considérée comme un *titre*."
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1132
+#: best-pkging-practices.dbk:1254
msgid ""
"The extended description is what will be displayed as a more detailed "
"explanation of the note. Phrases, no terse writing style."
-msgstr "La partie longue est ce qui sera affiché comme description plus détaillée de la note. Il est conseillé d'éviter d'y utiliser un style abrégé."
+msgstr ""
+"La partie longue est ce qui sera affiché comme description plus détaillée de "
+"la note. Il est conseillé d'éviter d'y utiliser un style abrégé."
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1138
+#: best-pkging-practices.dbk:1260
msgid ""
"<emphasis role=\"strong\">Do not abuse debconf.</emphasis> Notes are the "
"most common way to abuse debconf. As written in debconf-devel manual page: "
"notes. If, by reading this, you consider converting your Note type "
"templates to entries in NEWS/Debian or README.Debian, plus consider keeping "
"existing translations for the future."
-msgstr "<emphasis role=\"strong\">N'abusez pas de debconf.</emphasis>. Les notes sont un des abus les plus fréquents de debconf. Comm eindiqué dans la page de manuel de debconf, elle devraient être réservée pour avertir les utilisateurs de problème très importants. Les fichiers NEWS.Debian ou README.Debian sont les endroits appropriés pour l'information qu'affichent la majorité des notes. Si, à la lecture de ces conseils, vous envisagez de convertir vos modèles de type note en entrée dans NEWS.Debian ou README.Debian, pensez à conserver d'éventuelles traductions existantes."
+msgstr ""
+"<emphasis role=\"strong\">N'abusez pas de debconf.</emphasis>. Les notes "
+"sont un des abus les plus fréquents de debconf. Comm eindiqué dans la page "
+"de manuel de debconf, elle devraient être réservée pour avertir les "
+"utilisateurs de problème très importants. Les fichiers NEWS.Debian ou README."
+"Debian sont les endroits appropriés pour l'information qu'affichent la "
+"majorité des notes. Si, à la lecture de ces conseils, vous envisagez de "
+"convertir vos modèles de type note en entrée dans NEWS.Debian ou README."
+"Debian, pensez à conserver d'éventuelles traductions existantes."
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1153
+#: best-pkging-practices.dbk:1275
msgid "Choices field"
msgstr "Champ Choices"
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1155
+#: best-pkging-practices.dbk:1277
msgid ""
"If the Choices are likely to change often, please consider using the "
"__Choices trick. This will split each individual choice into a single "
"string, which will considerably help translators for doing their work."
-msgstr "Si les choix changent souvent, il est suggéré d'utiliser l'astuce « __Choices ». Avec ce format, chaque choix sera une chaîne différente proposée à la traduction, ce qui facilite grandement le travail des traducteurs."
+msgstr ""
+"Si les choix changent souvent, il est suggéré d'utiliser l'astuce "
+"« __Choices ». Avec ce format, chaque choix sera une chaîne différente "
+"proposée à la traduction, ce qui facilite grandement le travail des "
+"traducteurs."
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1162 best-pkging-practices.dbk:1200
+#: best-pkging-practices.dbk:1284 best-pkging-practices.dbk:1322
msgid "Default field"
msgstr "Champ Default"
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1164
+#: best-pkging-practices.dbk:1286
msgid ""
"If the default value, for a select template, is likely to vary depending on "
"the user language (for instance, if the choice is a language choice), please "
"use the _DefaultChoice trick."
-msgstr "Si la valeur par défaut d'un modèle « select » peut être dépendante de la langue utilisée (par exemple s'il s'agit du choix d'une langue par défaut), pensez à utiliser l'astuce « DefaultChoice »."
+msgstr ""
+"Si la valeur par défaut d'un modèle « select » peut être dépendante de la "
+"langue utilisée (par exemple s'il s'agit du choix d'une langue par défaut), "
+"pensez à utiliser l'astuce « DefaultChoice »."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1169
+#: best-pkging-practices.dbk:1291
+#, fuzzy
msgid ""
"This special field allow translators to put the most appropriate choice "
"according to their own language. It will become the default choice when "
"their language is used while your own mentioned Default Choice will be used "
-"chan using English."
-msgstr "Ce champ spécial permet aux traducteur de mettre le choix le plus adapté à leur langue, qui deviendra le choix par défaut quand cette langue est utilisée, alors que le choix par défaut que vous avez mentionné sera utilisé en anglais."
+"when using English."
+msgstr ""
+"Ce champ spécial permet aux traducteur de mettre le choix le plus adapté à "
+"leur langue, qui deviendra le choix par défaut quand cette langue est "
+"utilisée, alors que le choix par défaut que vous avez mentionné sera utilisé "
+"en anglais."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1175
+#: best-pkging-practices.dbk:1297
msgid "Example, taken from the geneweb package templates:"
msgstr "Exemple, pris dans le paquet geneweb :"
# type: Content of: <chapter><section><section><section><screen>
-#: best-pkging-practices.dbk:1177
+#: best-pkging-practices.dbk:1299
#, no-wrap
msgid ""
"\n"
"_Description: Geneweb default language:\n"
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1189
+#: best-pkging-practices.dbk:1311
msgid ""
"Note the use of brackets which allow internal comments in debconf fields. "
"Also note the use of comments which will show up in files the translators "
"will work with."
-msgstr "Veuillez noter l'utilisation de crochets pour autoriser des commentaires internes dans les champs de debconf. Notez également l'utilisation de commentaires qui apparaîtront dans les fichiers de travail des traducteurs."
+msgstr ""
+"Veuillez noter l'utilisation de crochets pour autoriser des commentaires "
+"internes dans les champs de debconf. Notez également l'utilisation de "
+"commentaires qui apparaîtront dans les fichiers de travail des traducteurs."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1194
+#: best-pkging-practices.dbk:1316
msgid ""
"The comments are needed as the DefaultChoice trick is a bit confusing: the "
"translators may put their own choice"
-msgstr "Les commentaires sont très utiles car l'astuce DefaultChoice est parfois déroutante pour les traducteurs qui doivent y mettre leur propre choix et non une simple traduction."
+msgstr ""
+"Les commentaires sont très utiles car l'astuce DefaultChoice est parfois "
+"déroutante pour les traducteurs qui doivent y mettre leur propre choix et "
+"non une simple traduction."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1202
+#: best-pkging-practices.dbk:1324
msgid ""
"Do NOT use empty default field. If you don't want to use default values, do "
"not use Default at all."
-msgstr "N'utilisez PAS de champ Default vide. Si vous ne souhaitez pas avoir de valeur par défaut, n'utilisez pas du tout ce champ."
+msgstr ""
+"N'utilisez PAS de champ Default vide. Si vous ne souhaitez pas avoir de "
+"valeur par défaut, n'utilisez pas du tout ce champ."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1206
+#: best-pkging-practices.dbk:1328
msgid ""
"If you use po-debconf (and you <emphasis role=\"strong\">should</emphasis>, "
"see 2.2), consider making this field translatable, if you think it may be "
"translated."
-msgstr "Quand vous utilisez po-debconf, pensez à rendre ce champ traduisible si vous pensez qu'il peut l'être."
+msgstr ""
+"Quand vous utilisez po-debconf, pensez à rendre ce champ traduisible si vous "
+"pensez qu'il peut l'être."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1211
+#: best-pkging-practices.dbk:1333
msgid ""
"If the default value may vary depending on language/country (for instance "
"the default value for a language choice), consider using the special "
"_DefaultChoice type documented in <citerefentry> <refentrytitle>po-debconf</"
"refentrytitle> <manvolnum>7</manvolnum> </citerefentry>)."
msgstr ""
-"Si la valeur par défaut peut dépendre de la lanue ou du pays (par exemple une langue par défaut dans un programme), pensez à utiliser le type « _DefaultChoice » documenté dans la page de manuel <citerefentry> <refentrytitle>po-debconf</"
-"refentrytitle> <manvolnum>7</manvolnum> </citerefentry>."
+"Si la valeur par défaut peut dépendre de la lanue ou du pays (par exemple "
+"une langue par défaut dans un programme), pensez à utiliser le type "
+"« _DefaultChoice » documenté dans la page de manuel <citerefentry> "
+"<refentrytitle>po-debconf</refentrytitle> <manvolnum>7</manvolnum> </"
+"citerefentry>."
# type: Content of: <chapter><section><title>
-#: best-pkging-practices.dbk:1223
+#: best-pkging-practices.dbk:1345
msgid "Internationalization"
msgstr "Internationalisation"
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1225
+#: best-pkging-practices.dbk:1347
msgid "Handling debconf translations"
msgstr "Gestion des traductions debconf"
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1227
+#: best-pkging-practices.dbk:1349
msgid ""
"Like porters, translators have a difficult task. They work on many packages "
"and must collaborate with many different maintainers. Moreover, most of the "
"time, they are not native English speakers, so you may need to be "
"particularly patient with them."
-msgstr "Comme les porteurs, les traducteurs ont une tâche difficile. Ils travaillent sur de nombreux paquets et doivent collaborer avec de nombreux responsables. De plus, ils n'ont généralement pas la langue anglaise comme langue maternelle et vous devez donc faire preuve d'une patience particulière avec eux."
+msgstr ""
+"Comme les porteurs, les traducteurs ont une tâche difficile. Ils travaillent "
+"sur de nombreux paquets et doivent collaborer avec de nombreux responsables. "
+"De plus, ils n'ont généralement pas la langue anglaise comme langue "
+"maternelle et vous devez donc faire preuve d'une patience particulière avec "
+"eux."
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1233
+#: best-pkging-practices.dbk:1355
msgid ""
"The goal of <systemitem role=\"package\">debconf</systemitem> was to make "
"packages configuration easier for maintainers and for users. Originally, "
"debconf</systemitem> package. This method is easier both for maintainer and "
"translators; transition scripts are provided."
msgstr ""
-"L'objectif de <systemitem role=\"package\">debconf</systemitem> est de rendre la configuration des paquets plus facile pour les responsables de paquets et pour les utilisateurs. Initialement, la traduction des écrans de debconf était gérée avec <command>debconf-"
-"mergetemplate</command>. Cependant, cette technique est désormais obsolète et la meilleure façon d'internationaliser <systemitem role=\"package\">debconf</systemitem> est d'utiliser le paquet <systemitem role=\"package\">po-"
-"debconf</systemitem>. Cette méthode rend plus simple le travail des traducteurs et des responsables et des scripts de transition sont fournis."
+"L'objectif de <systemitem role=\"package\">debconf</systemitem> est de "
+"rendre la configuration des paquets plus facile pour les responsables de "
+"paquets et pour les utilisateurs. Initialement, la traduction des écrans de "
+"debconf était gérée avec <command>debconf-mergetemplate</command>. "
+"Cependant, cette technique est désormais obsolète et la meilleure façon "
+"d'internationaliser <systemitem role=\"package\">debconf</systemitem> est "
+"d'utiliser le paquet <systemitem role=\"package\">po-debconf</systemitem>. "
+"Cette méthode rend plus simple le travail des traducteurs et des "
+"responsables et des scripts de transition sont fournis."
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1243
+#: best-pkging-practices.dbk:1365
msgid ""
"Using <systemitem role=\"package\">po-debconf</systemitem>, the translation "
"is stored in <filename>po</filename> files (drawing from <command>gettext</"
"the up-to-date translations into the binary packages. Refer to the "
"<citerefentry> <refentrytitle>po-debconf</refentrytitle> <manvolnum>7</"
"manvolnum> </citerefentry> manual page for details."
-msgstr "Avec <systemitem role=\"package\">po-debconf</systemitem>, les traductions sont gérées dans des fichiers <filename>po</filename> (hérités des techniques de traduction utilisées avec <command>gettext</command>). Des fichiers modèles contiennent les messages d'origine et les champs à traduire y sont marqués spécifiquement. Lorsque le contenu d'un champ traduisible est modifié, l'emploi de la commande <command>debconf-updatepo</command> permet d'indiquer que la traduction a besoin d'une mise à jour par les traducteurs. Ensuite, au moment de la construction du paquet, le programme <command>dh_installdebconf</command> s'occupe des opérations nécessaires pour ajouter le modèle avec les traductions à jour dans les paquets binaires. Vous pouvez consulter la page de manuel de <citerefentry> <refentrytitle>po-debconf</refentrytitle> <manvolnum>7</manvolnum> </citerefentry> pour plus d'informations."
+msgstr ""
+"Avec <systemitem role=\"package\">po-debconf</systemitem>, les traductions "
+"sont gérées dans des fichiers <filename>po</filename> (hérités des "
+"techniques de traduction utilisées avec <command>gettext</command>). Des "
+"fichiers modèles contiennent les messages d'origine et les champs à traduire "
+"y sont marqués spécifiquement. Lorsque le contenu d'un champ traduisible est "
+"modifié, l'emploi de la commande <command>debconf-updatepo</command> permet "
+"d'indiquer que la traduction a besoin d'une mise à jour par les traducteurs. "
+"Ensuite, au moment de la construction du paquet, le programme "
+"<command>dh_installdebconf</command> s'occupe des opérations nécessaires "
+"pour ajouter le modèle avec les traductions à jour dans les paquets "
+"binaires. Vous pouvez consulter la page de manuel de <citerefentry> "
+"<refentrytitle>po-debconf</refentrytitle> <manvolnum>7</manvolnum> </"
+"citerefentry> pour plus d'informations."
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1259
+#: best-pkging-practices.dbk:1381
msgid "Internationalized documentation"
msgstr "Documentation internatonalisée"
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1261
+#: best-pkging-practices.dbk:1383
msgid ""
"Internationalizing documentation is crucial for users, but a lot of labor. "
"There's no way to eliminate all that work, but you can make things easier "
"for translators."
-msgstr "L'internationalisation de la documentation est primordiale pour les utilisateurs mais représente un travail très important. Même s'il n'est pas possible de supprimer toute le travail nécessaire, il est possible de faciliter le travail des traducteurs."
+msgstr ""
+"L'internationalisation de la documentation est primordiale pour les "
+"utilisateurs mais représente un travail très important. Même s'il n'est pas "
+"possible de supprimer toute le travail nécessaire, il est possible de "
+"faciliter le travail des traducteurs."
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1266
+#: best-pkging-practices.dbk:1388
msgid ""
"If you maintain documentation of any size, its easier for translators if "
"they have access to a source control system. That lets translators see the "
"file, the revision of the original file the translation is based on. You "
"might wish to adapt and provide that in your CVS area."
msgstr ""
-"Si vous maintenez une documentation de quelque taille que ce soit, il sera plus pratique pour les traducteurs d'avoir accès au système de suivi des versions source. Cela leur permet de voir les différences entre deux versions de la documentation et, par conséquent, de mieux voir où les traductions doivent être modifiées. Il est recommandé que la documentation traduite contienne l'indication du système de suivi des versions source qui est utilisé. Un système pratique est fourni par <ulink url=\"&url-i18n-doc-check;\">doc-check</ulink> du paquet <systemitem role="
-"\"package\">boot-floppies</systemitem>, qui permet un survol de l'état de la traduction pour toute langue, par l'utilisation de commentaires structurés dans la version du fichier à traduire et, pour le fichier traduit, la version du fichier sur laquelle est basée la traduction. Il est possible d'adapter ce système dans votre propre dépôt CVS."
+"Si vous maintenez une documentation de quelque taille que ce soit, il sera "
+"plus pratique pour les traducteurs d'avoir accès au système de suivi des "
+"versions source. Cela leur permet de voir les différences entre deux "
+"versions de la documentation et, par conséquent, de mieux voir où les "
+"traductions doivent être modifiées. Il est recommandé que la documentation "
+"traduite contienne l'indication du système de suivi des versions source qui "
+"est utilisé. Un système pratique est fourni par <ulink url=\"&url-i18n-doc-"
+"check;\">doc-check</ulink> du paquet <systemitem role=\"package\">boot-"
+"floppies</systemitem>, qui permet un survol de l'état de la traduction pour "
+"toute langue, par l'utilisation de commentaires structurés dans la version "
+"du fichier à traduire et, pour le fichier traduit, la version du fichier sur "
+"laquelle est basée la traduction. Il est possible d'adapter ce système dans "
+"votre propre dépôt CVS."
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1280
+#: best-pkging-practices.dbk:1402
msgid ""
"If you maintain XML or SGML documentation, we suggest that you isolate any "
"language-independent information and define those as entities in a separate "
"file which is included by all the different translations. This makes it "
"much easier, for instance, to keep URLs up to date across multiple files."
-msgstr "Si vous maintenez de la documentation en format XML ou SGML, il est conseillé d'isoler l'information indépendant de la langue et de la définir sous forme d'entités dans un fichier à part qui sera inclus par toutes les traductions. Cela rend par exemple plus simple la maintenance d'URL dans de nombreux fichiers."
+msgstr ""
+"Si vous maintenez de la documentation en format XML ou SGML, il est "
+"conseillé d'isoler l'information indépendant de la langue et de la définir "
+"sous forme d'entités dans un fichier à part qui sera inclus par toutes les "
+"traductions. Cela rend par exemple plus simple la maintenance d'URL dans de "
+"nombreux fichiers."
# type: Content of: <chapter><section><title>
-#: best-pkging-practices.dbk:1290
+#: best-pkging-practices.dbk:1412
msgid "Common packaging situations"
msgstr "Situation usuelle de gestion de paquets"
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1301
+#: best-pkging-practices.dbk:1423
msgid "Packages using <command>autoconf</command>/<command>automake</command>"
-msgstr "Paquets qui utilisent <command>autoconf</command>/<command>automake</command>"
+msgstr ""
+"Paquets qui utilisent <command>autoconf</command>/<command>automake</command>"
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1303
+#: best-pkging-practices.dbk:1425
msgid ""
"Keeping <command>autoconf</command>'s <filename>config.sub</filename> and "
"<filename>config.guess</filename> files up to date is critical for porters, "
"recommendations."
msgstr ""
"Pouvoir disposer de fichiers <filename>config.sub</filename> et "
-"<filename>config.guess</filename> à jour est un point critique pour les porteurs, particulièrement pour les architectures assez volatiles. de très bonnes pratiques applicable à tout paquet qui utilise <command>autoconf</command> et/ou "
-"<command>automake</command> ont été résumées dans &file-bpp-autotools; du paquet <systemitem role=\"package\">autotools-dev</systemitem>. Il est fortement recommandé de lire ce fichier et d'en suivre les recommandations."
+"<filename>config.guess</filename> à jour est un point critique pour les "
+"porteurs, particulièrement pour les architectures assez volatiles. de très "
+"bonnes pratiques applicable à tout paquet qui utilise <command>autoconf</"
+"command> et/ou <command>automake</command> ont été résumées dans &file-bpp-"
+"autotools; du paquet <systemitem role=\"package\">autotools-dev</"
+"systemitem>. Il est fortement recommandé de lire ce fichier et d'en suivre "
+"les recommandations."
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1315
+#: best-pkging-practices.dbk:1437
msgid "Libraries"
msgstr "Bibliothèques"
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1317
+#: best-pkging-practices.dbk:1439
msgid ""
"Libraries are always difficult to package for various reasons. The policy "
"imposes many constraints to ease their maintenance and to make sure upgrades "
"are as simple as possible when a new upstream version comes out. Breakage "
"in a library can result in dozens of dependent packages breaking."
-msgstr "Les paquets fournissant des bibliothèques sont plus difficiles à maintenir pour plusieurs raisons. La charte impose de nombreuses contraintes pour en faciliter la maintenance et garantir que les mises à niveau sont aussi simple que possible quand une nouvelle version amont est disponible. Des erreurs dans une bibliothèque sont susceptibles de rendre inutilisables de très nombreux paquets."
+msgstr ""
+"Les paquets fournissant des bibliothèques sont plus difficiles à maintenir "
+"pour plusieurs raisons. La charte impose de nombreuses contraintes pour en "
+"faciliter la maintenance et garantir que les mises à niveau sont aussi "
+"simple que possible quand une nouvelle version amont est disponible. Des "
+"erreurs dans une bibliothèque sont susceptibles de rendre inutilisables de "
+"très nombreux paquets."
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1323
+#: best-pkging-practices.dbk:1445
msgid ""
"Good practices for library packaging have been grouped in <ulink url=\"&url-"
"libpkg-guide;\">the library packaging guide</ulink>."
msgstr ""
-"Les bonnes pratiques pour la maintenance de paquets fournissant des bibliothèques ont été rassemblées dans <ulink url=\"&url-"
-"libpkg-guide;\">le guide de gestion des paquets de bibliothèques</ulink>."
+"Les bonnes pratiques pour la maintenance de paquets fournissant des "
+"bibliothèques ont été rassemblées dans <ulink url=\"&url-libpkg-guide;\">le "
+"guide de gestion des paquets de bibliothèques</ulink>."
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1330
+#: best-pkging-practices.dbk:1452
msgid "Documentation"
msgstr "Documentation"
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1332
+#: best-pkging-practices.dbk:1454
msgid ""
"Be sure to follow the <ulink url=\"&url-debian-policy;ch-docs.html\">Policy "
"on documentation</ulink>."
-msgstr "Veuillez vous assurer que vous suivez la <ulink url=\"&url-debian-policy;ch-docs.html\">charte de documentation</ulink>."
+msgstr ""
+"Veuillez vous assurer que vous suivez la <ulink url=\"&url-debian-policy;ch-"
+"docs.html\">charte de documentation</ulink>."
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1337
+#: best-pkging-practices.dbk:1459
msgid ""
"If your package contains documentation built from XML or SGML, we recommend "
"you not ship the XML or SGML source in the binary package(s). If users want "
"the source of the documentation, they should retrieve the source package."
-msgstr "Si votre paquet contient de la documentation construite à partir de fichiers XML ou SGML, il est recommandé de ne pas fournir ces fichiers source dans les paquets binaires. Les utilisateurs qui souhaiteraient disposer des sources de la documentation peuvent alors récupérer le paquet source."
+msgstr ""
+"Si votre paquet contient de la documentation construite à partir de fichiers "
+"XML ou SGML, il est recommandé de ne pas fournir ces fichiers source dans "
+"les paquets binaires. Les utilisateurs qui souhaiteraient disposer des "
+"sources de la documentation peuvent alors récupérer le paquet source."
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1342
+#: best-pkging-practices.dbk:1464
msgid ""
"Policy specifies that documentation should be shipped in HTML format. We "
"also recommend shipping documentation in PDF and plain text format if "
"convenient and if output of reasonable quality is possible. However, it is "
"generally not appropriate to ship plain text versions of documentation whose "
"source format is HTML."
-msgstr "La charte indique que la documentation devrait être fournie en format HTML. Il est recommandé de la fournir également dans les formats PDF et texte si cela est pratique et si un affichage de qualité raisonnable est possible. Cependant, il est le plus souvent inapproprié de fournir en format texte simple des versions de documentations dont le format source est HTML."
+msgstr ""
+"La charte indique que la documentation devrait être fournie en format HTML. "
+"Il est recommandé de la fournir également dans les formats PDF et texte si "
+"cela est pratique et si un affichage de qualité raisonnable est possible. "
+"Cependant, il est le plus souvent inapproprié de fournir en format texte "
+"simple des versions de documentations dont le format source est HTML."
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1349
+#: best-pkging-practices.dbk:1471
msgid ""
"Major shipped manuals should register themselves with <systemitem role="
"\"package\">doc-base</systemitem> on installation. See the <systemitem role="
"\"package\">doc-base</systemitem> package documentation for more information."
msgstr ""
-"Les manuels les plus importants qui sont fournis devraient être enregistrés avec <systemitem role="
-"\"package\">doc-base</systemitem> lors de leur installation. Veuillez consulter la documentation du paquet <systemitem role=\"package\">doc-base</systemitem> pour plus d'informations."
+"Les manuels les plus importants qui sont fournis devraient être enregistrés "
+"avec <systemitem role=\"package\">doc-base</systemitem> lors de leur "
+"installation. Veuillez consulter la documentation du paquet <systemitem role="
+"\"package\">doc-base</systemitem> pour plus d'informations."
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1357
+#: best-pkging-practices.dbk:1479
msgid "Specific types of packages"
msgstr "Type particuliers de paquets"
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1359
+#: best-pkging-practices.dbk:1481
msgid ""
"Several specific types of packages have special sub-policies and "
"corresponding packaging rules and practices:"
-msgstr "Plusieurs types particuliers de paquets utilisent des chartes spécifiques avec les règles et de bonnes pratiques particulières."
+msgstr ""
+"Plusieurs types particuliers de paquets utilisent des chartes spécifiques "
+"avec les règles et de bonnes pratiques particulières."
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1365
+#: best-pkging-practices.dbk:1487
msgid ""
"Perl related packages have a <ulink url=\"&url-perl-policy;\">Perl policy</"
"ulink>, some examples of packages following that policy are <systemitem role="
"\"package\">libdbd-pg-perl</systemitem> (binary perl module) or <systemitem "
"role=\"package\">libmldbm-perl</systemitem> (arch independent perl module)."
msgstr ""
-"Les paquets liés à Perl utilisent une <ulink url=\"&url-perl-policy;\">charte Perl</"
-"ulink>. Des exemples de tels paquets qui appliquent cette charte spécifique sont <systemitem role="
-"\"package\">libdbd-pg-perl</systemitem> (module Perl binaire) ou <systemitem "
-"role=\"package\">libmldbm-perl</systemitem> (module Perl indépendant de l'architecture)."
+"Les paquets liés à Perl utilisent une <ulink url=\"&url-perl-policy;"
+"\">charte Perl</ulink>. Des exemples de tels paquets qui appliquent cette "
+"charte spécifique sont <systemitem role=\"package\">libdbd-pg-perl</"
+"systemitem> (module Perl binaire) ou <systemitem role=\"package\">libmldbm-"
+"perl</systemitem> (module Perl indépendant de l'architecture)."
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1374
+#: best-pkging-practices.dbk:1496
msgid ""
"Python related packages have their python policy; see &file-python-policy; "
"in the <systemitem role=\"package\">python</systemitem> package."
-msgstr "Les paquets liés à Python utilisent une charte Python. Veuillez consulter le fichier &file-python-policy; du paquet <systemitem role=\"package\">python</systemitem> pour plus d'informations."
+msgstr ""
+"Les paquets liés à Python utilisent une charte Python. Veuillez consulter le "
+"fichier &file-python-policy; du paquet <systemitem role=\"package\">python</"
+"systemitem> pour plus d'informations."
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1381
+#: best-pkging-practices.dbk:1503
msgid ""
"Emacs related packages have the <ulink url=\"&url-emacs-policy;\">emacs "
"policy</ulink>."
-msgstr "Les paquets liés à Emacs utilisent une <ulink url=\"&url-emacs-policy;\">charte Emacs</ulink>."
+msgstr ""
+"Les paquets liés à Emacs utilisent une <ulink url=\"&url-emacs-policy;"
+"\">charte Emacs</ulink>."
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1388
+#: best-pkging-practices.dbk:1510
msgid ""
"Java related packages have their <ulink url=\"&url-java-policy;\">java "
"policy</ulink>."
-msgstr "Les paquets liés à Java utilisent une <ulink url=\"&url-java-policy;\">charte Java</ulink>."
+msgstr ""
+"Les paquets liés à Java utilisent une <ulink url=\"&url-java-policy;"
+"\">charte Java</ulink>."
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1395
+#: best-pkging-practices.dbk:1517
msgid ""
"Ocaml related packages have their own policy, found in &file-ocaml-policy; "
"from the <systemitem role=\"package\">ocaml</systemitem> package. A good "
"example is the <systemitem role=\"package\">camlzip</systemitem> source "
"package."
msgstr ""
-"Les paquets liés à Ocaml utilisent leur propre charte, que l'on peut trouver dans le fichier &file-ocaml-policy; "
-"du paquet <systemitem role=\"package\">ocaml</systemitem>. Un bon exemple est fourni par le paquet source <systemitem role=\"package\">camlzip</systemitem>."
+"Les paquets liés à Ocaml utilisent leur propre charte, que l'on peut trouver "
+"dans le fichier &file-ocaml-policy; du paquet <systemitem role=\"package"
+"\">ocaml</systemitem>. Un bon exemple est fourni par le paquet source "
+"<systemitem role=\"package\">camlzip</systemitem>."
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1403
+#: best-pkging-practices.dbk:1525
msgid ""
"Packages providing XML or SGML DTDs should conform to the recommendations "
"found in the <systemitem role=\"package\">sgml-base-doc</systemitem> package."
-msgstr "Les paquets fournissant des DTD XML ou SGML devraient suivre les recommandations données dans le paquet <systemitem role=\"package\">sgml-base-doc</systemitem>."
+msgstr ""
+"Les paquets fournissant des DTD XML ou SGML devraient suivre les "
+"recommandations données dans le paquet <systemitem role=\"package\">sgml-"
+"base-doc</systemitem>."
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1409
+#: best-pkging-practices.dbk:1531
msgid ""
"Lisp packages should register themselves with <systemitem role=\"package"
"\">common-lisp-controller</systemitem>, about which see &file-lisp-"
"controller;."
msgstr ""
"Les paquets Lisp doivent s'enregistrer avec <systemitem role=\"package"
-"\">common-lisp-controller</systemitem>, pour lequel plus d'information est disponible dans &file-lisp-"
-"controller;."
+"\">common-lisp-controller</systemitem>, pour lequel plus d'information est "
+"disponible dans &file-lisp-controller;."
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1439
+#: best-pkging-practices.dbk:1561
msgid "Architecture-independent data"
msgstr "Données indépendantes de l'architecture"
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1441
+#: best-pkging-practices.dbk:1563
msgid ""
"It is not uncommon to have a large amount of architecture-independent data "
"packaged with a program. For example, audio files, a collection of icons, "
"wallpaper patterns, or other graphic files. If the size of this data is "
"negligible compared to the size of the rest of the package, it's probably "
"best to keep it all in a single package."
-msgstr "Il est fréquent qu'un grand nombre de données indépendantes de l'architecture soient fournies avec un programme. Cela peut être par exemple des fichiers audio, un ensemble d'icônes, des motifs de papier-peint ou d'autres fichiers graphiques. Si la taille de ces données est négligeable par rapport à la taille du reste du paquet, il est probablement préférable de laisser l'ensemble dans un seul paquet."
+msgstr ""
+"Il est fréquent qu'un grand nombre de données indépendantes de "
+"l'architecture soient fournies avec un programme. Cela peut être par exemple "
+"des fichiers audio, un ensemble d'icônes, des motifs de papier-peint ou "
+"d'autres fichiers graphiques. Si la taille de ces données est négligeable "
+"par rapport à la taille du reste du paquet, il est probablement préférable "
+"de laisser l'ensemble dans un seul paquet."
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1448
+#: best-pkging-practices.dbk:1570
msgid ""
"However, if the size of the data is considerable, consider splitting it out "
"into a separate, architecture-independent package (_all.deb). By doing "
"processing time of <command>lintian</command> (see <xref linkend=\"tools-lint"
"\"/> ) when run over the entire Debian archive."
msgstr ""
-"Cependant, si cette taille est importante, vous devriez considérer de les fournir dans un paquet séparé, indépendant de l'architecture (_all.deb). Cela permet ainsi d'aviter la duplication des mêmes données dans de nombreux paquets binaires, un par architecture. Bien que cela ajoute des entrées dans les fichiers <filename>Packages</filename>, cela permet d'économiser une place importante sur les miroirs de Debian. La séparation des données indépendantes de l'architecture réduit également le temps de traitement de <command>lintian</command> (voir <xref linkend=\"tools-lint"
-"\"/> ) lorsqu'il est utilisé sur l'archive Debian en entier."
+"Cependant, si cette taille est importante, vous devriez considérer de les "
+"fournir dans un paquet séparé, indépendant de l'architecture (_all.deb). "
+"Cela permet ainsi d'aviter la duplication des mêmes données dans de nombreux "
+"paquets binaires, un par architecture. Bien que cela ajoute des entrées dans "
+"les fichiers <filename>Packages</filename>, cela permet d'économiser une "
+"place importante sur les miroirs de Debian. La séparation des données "
+"indépendantes de l'architecture réduit également le temps de traitement de "
+"<command>lintian</command> (voir <xref linkend=\"tools-lint\"/> ) lorsqu'il "
+"est utilisé sur l'archive Debian en entier."
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1460
+#: best-pkging-practices.dbk:1582
msgid "Needing a certain locale during build"
-msgstr "Nécessitant des paramètres régionaux spécifiques lors de la construction"
+msgstr ""
+"Nécessitant des paramètres régionaux spécifiques lors de la construction"
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1462
+#: best-pkging-practices.dbk:1584
msgid ""
"If you need a certain locale during build, you can create a temporary file "
"via this trick:"
-msgstr "Si des paramètres régionaux (« locale ») sont nécessaires pour la construction d'un paquet, vous pouvez créer un fichier temporaire avec cette astuce :"
+msgstr ""
+"Si des paramètres régionaux (« locale ») sont nécessaires pour la "
+"construction d'un paquet, vous pouvez créer un fichier temporaire avec cette "
+"astuce :"
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1466
+#: best-pkging-practices.dbk:1588
msgid ""
"If you set <varname>LOCPATH</varname> to the equivalent of <filename>/usr/"
"lib/locale</filename>, and <varname>LC_ALL</varname> to the name of the "
"locale you generate, you should get what you want without being root. "
"Something like this:"
msgstr ""
-"Si la variable <varname>LOCPATH</varname> est placée sur l'équivalent de <filename>/usr/"
-"lib/locale</filename> et <varname>LC_ALL</varname> sur le nom des paramètres régionaux à créer, vous devriez pouvoir obtenir le résultat escompté dans avoir les privilèges du superutilisateur. La séquence ressemblera alors à :"
+"Si la variable <varname>LOCPATH</varname> est placée sur l'équivalent de "
+"<filename>/usr/lib/locale</filename> et <varname>LC_ALL</varname> sur le nom "
+"des paramètres régionaux à créer, vous devriez pouvoir obtenir le résultat "
+"escompté dans avoir les privilèges du superutilisateur. La séquence "
+"ressemblera alors à :"
# type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:1470
+#: best-pkging-practices.dbk:1592
#, no-wrap
msgid ""
"\n"
"LOCPATH=$LOCALE_PATH LC_ALL=$LOCALE_NAME.$LOCALE_CHARSET date\n"
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1484
+#: best-pkging-practices.dbk:1606
msgid "Make transition packages deborphan compliant"
msgstr "Rendre les paquets de transition conformes à deborphan"
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1486
+#: best-pkging-practices.dbk:1608
msgid ""
"Deborphan is a program for helping users to detect which packages can safely "
"be removed from the system, i.e. the ones that have no packages depending "
"on them. The default operation is to search only within the libs and "
"oldlibs sections, to hunt down unused libraries. But when passed the right "
"argument, it tries to catch other useless packages."
-msgstr "Deborphan est un programme qui permet aux utilisateurs d'identifier les paquets qui peuvent être supprimés sans crainte du système, c'est à dire ceux dont aucun autre paquet ne dépend. Par défaut, l'utilitaire n'effectue sa recherche que parmi les paquets de bibliothèques et les sections « oldlibs », afin de traquer les bibliothèques inutilisées. Cependant, avec le paramètre approprié, il peut rechercher d'autres paquets inutiles."
+msgstr ""
+"Deborphan est un programme qui permet aux utilisateurs d'identifier les "
+"paquets qui peuvent être supprimés sans crainte du système, c'est à dire "
+"ceux dont aucun autre paquet ne dépend. Par défaut, l'utilitaire n'effectue "
+"sa recherche que parmi les paquets de bibliothèques et les sections "
+"« oldlibs », afin de traquer les bibliothèques inutilisées. Cependant, avec "
+"le paramètre approprié, il peut rechercher d'autres paquets inutiles."
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1493
+#: best-pkging-practices.dbk:1615
msgid ""
"For example, with <literal>--guess-dummy</literal>, <command>deborphan</"
"command> tries to search all transitional packages which were needed for "
"upgrade but which can now safely be removed. For that, it looks for the "
"string dummy or transitional in their short description."
msgstr ""
-"Par exemple, le paramètre <literal>--guess-dummy</literal> de la commande <command>deborphan</"
-"command> permet de rechercher les paquets de transition qui étaient nécessaires lors de mises à niveau mais peuvent être supprimés sans problème. Pour cela, il recherche la chaîne « dummy » ou « transitional » dans leur description courte."
+"Par exemple, le paramètre <literal>--guess-dummy</literal> de la commande "
+"<command>deborphan</command> permet de rechercher les paquets de transition "
+"qui étaient nécessaires lors de mises à niveau mais peuvent être supprimés "
+"sans problème. Pour cela, il recherche la chaîne « dummy » ou « transitional » "
+"dans leur description courte."
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1500
+#: best-pkging-practices.dbk:1622
msgid ""
"So, when you are creating such a package, please make sure to add this text "
"to your short description. If you are looking for examples, just run: "
"<command>apt-cache search .|grep dummy</command> or <command>apt-cache "
"search .|grep transitional</command>."
msgstr ""
-"Ainsi, lorsque vous avez besoin de créer un tel paquet, veuillez prendre soin d'ajouter ce texte à sa description courte. Il est facile de trouver des exemples avec les commandes <command>apt-cache search .|grep dummy</command> ou <command>apt-cache "
-"search .|grep transitional</command>."
+"Ainsi, lorsque vous avez besoin de créer un tel paquet, veuillez prendre "
+"soin d'ajouter ce texte à sa description courte. Il est facile de trouver "
+"des exemples avec les commandes <command>apt-cache search .|grep dummy</"
+"command> ou <command>apt-cache search .|grep transitional</command>."
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1508
+#: best-pkging-practices.dbk:1630
msgid "Best practices for <filename>orig.tar.gz</filename> files"
-msgstr "Les meilleures pratiques pour les fichiers <filename>orig.tar.gz</filename>"
+msgstr ""
+"Les meilleures pratiques pour les fichiers <filename>orig.tar.gz</filename>"
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1510
+#: best-pkging-practices.dbk:1632
msgid ""
"There are two kinds of original source tarballs: Pristine source and "
"repackaged upstream source."
-msgstr "Il existe deux sortes différentes d'archives source d'origine. Les sources originelles (« pristine ») et les sources reconstruites (« repackaged »)."
+msgstr ""
+"Il existe deux sortes différentes d'archives source d'origine. Les sources "
+"originelles (« pristine ») et les sources reconstruites (« repackaged »)."
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1514
+#: best-pkging-practices.dbk:1636
msgid "Pristine source"
msgstr "Sources originelles (« pristine »)"
# type: Content of: <chapter><section><section><section><para><footnote>
-#: best-pkging-practices.dbk:1516
+#: best-pkging-practices.dbk:1638
msgid ""
"The defining characteristic of a pristine source tarball is that the "
"<literal>.orig.tar.gz</literal> file is byte-for-byte identical to a tarball "
"officially distributed by the upstream author. <footnote>"
-msgstr "La caractéristique principale d'une archive source originelle est que le fichier <literal>.orig.tar.gz</literal> est identique octet pour octet à l'archive distribuée par l'auteur amont. <footnote>"
+msgstr ""
+"La caractéristique principale d'une archive source originelle est que le "
+"fichier <literal>.orig.tar.gz</literal> est identique octet pour octet à "
+"l'archive distribuée par l'auteur amont. <footnote>"
# type: Content of: <chapter><section><section><section><para><footnote><para>
-#: best-pkging-practices.dbk:1518
+#: best-pkging-practices.dbk:1640
+#, fuzzy
msgid ""
"We cannot prevent upstream authors from changing the tarball they distribute "
"without also incrementing the version number, so there can be no guarantee "
"emphasis> distributing at any point in time. All that can be expected is "
"that it is identical to something that upstream once <emphasis>did</"
"emphasis> distribute. If a difference arises later (say, if upstream "
-"notices that he wasn't using maximal comression in his original distribution "
-"and then re-<command>gzip</command>s it), that's just too bad. Since there "
-"is no good way to upload a new <literal>.orig.tar.gz</literal> for the same "
-"version, there is not even any point in treating this situation as a bug."
-msgstr "Il est impossible d'empêcher les auteurs amont de modifier l'archive qu'ils distribuent sans également incrémenter le numéro de version. Il est donc impossible de garantir qu'une archive originelle est identique à ce que l'auteur amont distribue <emphasis>à un instant donné</emphasis>. Tout ce qu'il est possible de garantir est qu'elle a été identique à ce que l'auteur amont <emphasis>a</emphasis> distribué à un moment ou un autre. Si une différence apparaît plus tard (par exemple si l'auteur amont découvre ne pas avoir utilisé la compression maximale dans sa distribution d'origine et la recompresse, c'est tout simplement dommage. Comme il n'existe pas de méthode adaptée pour envoyer un nouveau fichier <literal>.orig.tar.gz</literal> pour la même version, il est même totalement sans objet de traiter cette situation comme un bogue."
+"notices that he wasn't using maximal compression in his original "
+"distribution and then re-<command>gzip</command>s it), that's just too bad. "
+"Since there is no good way to upload a new <literal>.orig.tar.gz</literal> "
+"for the same version, there is not even any point in treating this situation "
+"as a bug."
+msgstr ""
+"Il est impossible d'empêcher les auteurs amont de modifier l'archive qu'ils "
+"distribuent sans également incrémenter le numéro de version. Il est donc "
+"impossible de garantir qu'une archive originelle est identique à ce que "
+"l'auteur amont distribue <emphasis>à un instant donné</emphasis>. Tout ce "
+"qu'il est possible de garantir est qu'elle a été identique à ce que l'auteur "
+"amont <emphasis>a</emphasis> distribué à un moment ou un autre. Si une "
+"différence apparaît plus tard (par exemple si l'auteur amont découvre ne pas "
+"avoir utilisé la compression maximale dans sa distribution d'origine et la "
+"recompresse, c'est tout simplement dommage. Comme il n'existe pas de méthode "
+"adaptée pour envoyer un nouveau fichier <literal>.orig.tar.gz</literal> pour "
+"la même version, il est même totalement sans objet de traiter cette "
+"situation comme un bogue."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1528
+#: best-pkging-practices.dbk:1650
msgid ""
"</footnote> This makes it possible to use checksums to easily verify that "
"all changes between Debian's version and upstream's are contained in the "
"Debian diff. Also, if the original source is huge, upstream authors and "
"others who already have the upstream tarball can save download time if they "
"want to inspect your packaging in detail."
-msgstr "</footnote> Cela permet d'utiliser des sommes de contrôle pour vérifier que toutes les modifications effectuées entre la version Debian et la version amont sont contenues dans le fichier de différences Debian. De même, si la taille des sources d'origine est importante, les auteurs amont et tous ceux qui disposent de l'archive amont d'origine peuvent économiser du temps de téléchargement s'ils souhaitent contrôler le paquet en détail."
+msgstr ""
+"</footnote> Cela permet d'utiliser des sommes de contrôle pour vérifier que "
+"toutes les modifications effectuées entre la version Debian et la version "
+"amont sont contenues dans le fichier de différences Debian. De même, si la "
+"taille des sources d'origine est importante, les auteurs amont et tous ceux "
+"qui disposent de l'archive amont d'origine peuvent économiser du temps de "
+"téléchargement s'ils souhaitent contrôler le paquet en détail."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1536
+#: best-pkging-practices.dbk:1658
msgid ""
"There is no universally accepted guidelines that upstream authors follow "
"regarding to the directory structure inside their tarball, but <command>dpkg-"
"source</command> is nevertheless able to deal with most upstream tarballs as "
"pristine source. Its strategy is equivalent to the following:"
msgstr ""
-"Il n'existe pas de convention universellement acceptée pour la structure de répertoires que devraient adopter les auteurs amont dans les archives qu'ils publient, mais <command>dpkg-"
-"source</command> peut de toute manière traiter le plupart des archives amont comme des sources originelles. La stratégie de cette commande est la suivante :"
+"Il n'existe pas de convention universellement acceptée pour la structure de "
+"répertoires que devraient adopter les auteurs amont dans les archives qu'ils "
+"publient, mais <command>dpkg-source</command> peut de toute manière traiter "
+"le plupart des archives amont comme des sources originelles. La stratégie de "
+"cette commande est la suivante :"
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1544
+#: best-pkging-practices.dbk:1666
msgid "It unpacks the tarball in an empty temporary directory by doing"
msgstr "Elle extrait l'archive dans un répertoire temporaire :"
# type: Content of: <chapter><section><section><section><orderedlist><listitem><screen>
-#: best-pkging-practices.dbk:1546
+#: best-pkging-practices.dbk:1668
#, no-wrap
msgid ""
"\n"
"zcat chemon/vers/<nompaquet>_<version-amont>.orig.tar.gz | tar xf -\n"
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1552
+#: best-pkging-practices.dbk:1674
msgid ""
"If, after this, the temporary directory contains nothing but one directory "
"and no other files, <command>dpkg-source</command> renames that directory to "
"<literal><packagename>-<upstream-version>(.orig)</literal>. The "
"name of the top-level directory in the tarball does not matter, and is "
"forgotten."
-msgstr "Si, après cela, le répertoire temporaire ne contient qu'un seul répertoire sans fichiers, <command>dpkg-source</command> renomme ce répertoire en <literal><nomdupaquet>-<version-amont>(.orig)</literal>. Le nom du répertoire parent de l'archive tar n'a pas d'importance et est oublié;"
+msgstr ""
+"Si, après cela, le répertoire temporaire ne contient qu'un seul répertoire "
+"sans fichiers, <command>dpkg-source</command> renomme ce répertoire en "
+"<literal><nomdupaquet>-<version-amont>(.orig)</literal>. Le nom "
+"du répertoire parent de l'archive tar n'a pas d'importance et est oublié;"
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1561
+#: best-pkging-practices.dbk:1683
msgid ""
"Otherwise, the upstream tarball must have been packaged without a common top-"
"level directory (shame on the upstream author!). In this case, "
"<command>dpkg-source</command> renames the temporary directory "
"<emphasis>itself</emphasis> to <literal><packagename>-<upstream-"
"version>(.orig)</literal>."
-msgstr "Si ce n'est pas le cas, l'archive amont a été créée sans répertoire parent (honte à l'auteur amont !). Dans ce cas, <command>dpkg-source</command> renomme le répertoire temporaire lui-même en <literal><nomdupaquet>-<version-amont>(.orig)</literal>."
+msgstr ""
+"Si ce n'est pas le cas, l'archive amont a été créée sans répertoire parent "
+"(honte à l'auteur amont !). Dans ce cas, <command>dpkg-source</command> "
+"renomme le répertoire temporaire lui-même en <literal><nomdupaquet>-"
+"<version-amont>(.orig)</literal>."
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1572
+#: best-pkging-practices.dbk:1694
msgid "Repackaged upstream source"
msgstr "Source amont reconstruite"
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1574
+#: best-pkging-practices.dbk:1696
msgid ""
"You <emphasis role=\"strong\">should</emphasis> upload packages with a "
"pristine source tarball if possible, but there are various reasons why it "
"might not be possible. This is the case if upstream does not distribute the "
"source as gzipped tar at all, or if upstream's tarball contains non-DFSG-"
"free material that you must remove before uploading."
-msgstr "Vous <emphasis role=\"strong\">devriez</emphasis> envoyer les paquets avec une archive source inchangée, dans la mesure du possible. Il existe cependant plusieurs raisons qui peuvent rendre cela impossible. C'est notamment le cas si les auteurs amont ne distribuent pas d'archive tar compressée du tout ou si l'archive amont contient des parties non conformes aux principes du logiciel libre selon Debian, qui doivent être supprimées avant l'envoi."
+msgstr ""
+"Vous <emphasis role=\"strong\">devriez</emphasis> envoyer les paquets avec "
+"une archive source inchangée, dans la mesure du possible. Il existe "
+"cependant plusieurs raisons qui peuvent rendre cela impossible. C'est "
+"notamment le cas si les auteurs amont ne distribuent pas d'archive tar "
+"compressée du tout ou si l'archive amont contient des parties non conformes "
+"aux principes du logiciel libre selon Debian, qui doivent être supprimées "
+"avant l'envoi."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1581
+#: best-pkging-practices.dbk:1703
msgid ""
"In these cases the developer must construct a suitable <literal>.orig.tar.gz "
"</literal> file himself. We refer to such a tarball as a repackaged "
"number composed of <literal><upstream-version></literal> and "
"<literal><debian-revision></literal>."
msgstr ""
-"Dans ces cas, le responsable doit construire menuellement une archive <literal>.orig.tar.gz "
-"</literal>. Cette archive sera appelée une archive amont reconstruite. Il est important de noter qu'elle reste différente d'un paquet natif. Une archive reconstruite est toujours fournie avec les changements propres à Debian dans un fichier <literal>.diff.gz</literal> séparé et son numéro de version est toujours composé de <literal><version-amont></literal> et "
-"<literal><révision-debian></literal>."
+"Dans ces cas, le responsable doit construire menuellement une archive "
+"<literal>.orig.tar.gz </literal>. Cette archive sera appelée une archive "
+"amont reconstruite. Il est important de noter qu'elle reste différente d'un "
+"paquet natif. Une archive reconstruite est toujours fournie avec les "
+"changements propres à Debian dans un fichier <literal>.diff.gz</literal> "
+"séparé et son numéro de version est toujours composé de <literal><version-"
+"amont></literal> et <literal><révision-debian></literal>."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1590
+#: best-pkging-practices.dbk:1712
msgid ""
"There may be cases where it is desirable to repackage the source even though "
"upstream distributes a <literal>.tar.gz</literal> that could in principle be "
"by removing genuinely useless cruft from the upstream archive. Use your own "
"discretion here, but be prepared to defend your decision if you repackage "
"source that could have been pristine."
-msgstr "Il peut exister des cas où il est souhaitable de reconstruire une archive source alors que les auteurs amont fournissent bien une archive <literal>.tar.gz</literal> qui pourrait être utilisée directement. Le plus évident est la recherche d'un gain de place significatif par recompression ou par suppression de scories inutiles de l'archive source d'origine. Il est important que le responsable exerce avec discernement son propre jugement et soit prêt à le justifier si l'archive source est reconstruite alors qu'elle aurait pu être fournie telle quelle."
+msgstr ""
+"Il peut exister des cas où il est souhaitable de reconstruire une archive "
+"source alors que les auteurs amont fournissent bien une archive <literal>."
+"tar.gz</literal> qui pourrait être utilisée directement. Le plus évident est "
+"la recherche d'un gain de place significatif par recompression ou par "
+"suppression de scories inutiles de l'archive source d'origine. Il est "
+"important que le responsable exerce avec discernement son propre jugement et "
+"soit prêt à le justifier si l'archive source est reconstruite alors qu'elle "
+"aurait pu être fournie telle quelle."
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1599
+#: best-pkging-practices.dbk:1721
msgid "A repackaged <literal>.orig.tar.gz</literal>"
msgstr "Un fichier <literal>.orig.tar.gz</literal> reconstruit"
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1604
+#: best-pkging-practices.dbk:1726
+#, fuzzy
msgid ""
-"<emphasis role=\"strong\">must</emphasis> contain detailed information how "
-"the repackaged source was obtained, and how this can be reproduced in the "
+"<emphasis role=\"strong\">must</emphasis> be documented in the resulting "
+"source package. Detailed information on how the repackaged source was "
+"obtained, and on how this can be reproduced must be provided in "
"<filename>debian/copyright</filename>. It is also a good idea to provide a "
"<literal>get-orig-source</literal> target in your <filename>debian/rules</"
"filename> file that repeats the process, as described in the Policy Manual, "
"<ulink url=\"&url-debian-policy;ch-source.html#s-debianrules\">Main building "
"script: debian/rules</ulink>."
msgstr ""
-"<emphasis role=\"strong\">doit</emphasis> fournir de l'information détaillée sur l'endroit où les sources reconstruites ont été obtenues et comment il est possible de refaire l'opération, dans le fichier <filename>debian/copyright</filename>. Il est également suggéré de fournir une cible <literal>get-orig-source</literal> dans le fichier <filename>debian/rules</"
-"filename>, qui permette de refaire cette opération, comme indiqué dans la Charte Debian, <ulink url=\"&url-debian-policy;ch-source.html#s-debianrules\">Le script de construction principal : debian/rules</ulink>."
+"<emphasis role=\"strong\">doit</emphasis> fournir de l'information détaillée "
+"sur l'endroit où les sources reconstruites ont été obtenues et comment il "
+"est possible de refaire l'opération, dans le fichier <filename>debian/"
+"copyright</filename>. Il est également suggéré de fournir une cible "
+"<literal>get-orig-source</literal> dans le fichier <filename>debian/rules</"
+"filename>, qui permette de refaire cette opération, comme indiqué dans la "
+"Charte Debian, <ulink url=\"&url-debian-policy;ch-source.html#s-debianrules"
+"\">Le script de construction principal : debian/rules</ulink>."
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para><footnote>
-#: best-pkging-practices.dbk:1616
+#: best-pkging-practices.dbk:1739
msgid ""
"<emphasis role=\"strong\">should not</emphasis> contain any file that does "
"not come from the upstream author(s), or whose contents has been changed by "
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para><footnote><para>
-#. or similarly named
-#: best-pkging-practices.dbk:1618
+#. or similarly named
+#: best-pkging-practices.dbk:1741
msgid ""
"As a special exception, if the omission of non-free files would lead to the "
"source failing to build without assistance from the Debian diff, it might be "
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1625
+#: best-pkging-practices.dbk:1748
msgid "</footnote>"
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1630
+#: best-pkging-practices.dbk:1753
msgid ""
"<emphasis role=\"strong\">should</emphasis>, except where impossible for "
"legal reasons, preserve the entire building and portablility infrastructure "
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1639
+#: best-pkging-practices.dbk:1762
msgid ""
"(<emphasis>Rationale:</emphasis> It is common for Debian users who need to "
"build software for non-Debian platforms to fetch the source from a Debian "
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1646
+#: best-pkging-practices.dbk:1769
msgid ""
"<emphasis role=\"strong\">should</emphasis> use <literal><packagename>-"
"<upstream-version>.orig</literal> as the name of the top-level "
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1654
+#: best-pkging-practices.dbk:1777
msgid ""
"<emphasis role=\"strong\">should</emphasis> be gzipped with maximal "
"compression."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1659
+#: best-pkging-practices.dbk:1782
msgid ""
"The canonical way to meet the latter two points is to let <literal>dpkg-"
"source -b</literal> construct the repackaged tarball from an unpacked "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1665
+#: best-pkging-practices.dbk:1788
msgid "Changing binary files in <literal>diff.gz</literal>"
msgstr ""
# type: Content of: <chapter><section><section><section><para><footnote>
-#: best-pkging-practices.dbk:1667
+#: best-pkging-practices.dbk:1790
msgid ""
"Sometimes it is necessary to change binary files contained in the original "
"tarball, or to add binary files that are not in it. If this is done by "
msgstr ""
# type: Content of: <chapter><section><section><section><para><footnote><para>
-#: best-pkging-practices.dbk:1674
+#: best-pkging-practices.dbk:1797
msgid ""
"The file should have a name that makes it clear which binary file it "
"encodes. Usually, some postfix indicating the encoding should be appended "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1682
+#: best-pkging-practices.dbk:1805
msgid ""
"&example-uu; </footnote>. The file would then be decoded and copied to its "
"place during the build process. Thus the change will be visible quite easy."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1688
+#: best-pkging-practices.dbk:1811
msgid ""
"Some packages use <command>dbs</command> to manage patches to their upstream "
"source, and always create a new <literal>orig.tar.gz</literal> file that "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1701
+#: best-pkging-practices.dbk:1824
msgid "Best practices for debug packages"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1703
+#: best-pkging-practices.dbk:1826
msgid ""
"A debug package is a package with a name ending in -dbg, that contains "
"additional information that gdb can use. Since Debian binaries are stripped "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1711
+#: best-pkging-practices.dbk:1834
msgid ""
"It is up to a package's maintainer whether to create a debug package or "
"not. Maintainers are encouraged to create debug packages for library "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1721
+#: best-pkging-practices.dbk:1844
msgid ""
"Some debug packages may contain an entire special debugging build of a "
"library or other binary, but most of them can save space and build time by "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1733
+#: best-pkging-practices.dbk:1856
msgid ""
"The debugging symbols can be extracted from an object file using <command> "
"objcopy --only-keep-debug</command>. Then the object file can be stripped, "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1741
+#: best-pkging-practices.dbk:1864
msgid ""
"The <command>dh_strip</command> command in debhelper supports creating debug "
"packages, and can take care of using <command>objcopy</command> to separate "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1748
+#: best-pkging-practices.dbk:1871
msgid ""
-"Note that the Debian package should depend on the package that it provides "
+"Note that the debug package should depend on the package that it provides "
"debugging symbols for, and this dependency should be versioned. For example:"
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:1751
+#: best-pkging-practices.dbk:1874
#, no-wrap
msgid ""
"\n"
-"Depends: libfoo-dbg (= ${binary:Version})\n"
+"Depends: libfoo (= ${binary:Version})\n"
msgstr ""
+# type: Content of: <chapter><section><section><section><para>
+#~ msgid ""
+#~ "The use of the <command>podebconf-report-po</command> from the "
+#~ "<systemitem role=\"package\">po-debconf</systemitem> package is highly "
+#~ "recommended to warn translators which have incomplete translations and "
+#~ "request them for updates."
+#~ msgstr ""
+#~ "L'utilisation de la commande <command>podebconf-report-po</command> "
+#~ "fournie par le paquet <systemitem role=\"package\">po-debconf</"
+#~ "systemitem> est fortement recommandée pour avertir les traducteurs dont "
+#~ "les traductions sont incomplètes et leur demander de les mettre à jour."
+
+# type: Content of: <chapter><section><section><section><para>
+#~ msgid ""
+#~ "Calls for translations posted to &email-debian-i18n; with the "
+#~ "<filename>debian/po/templates.pot</filename> file attached or referenced "
+#~ "in a URL are encouraged. Be sure to mentions in these calls for new "
+#~ "translations which languages you have existing translations for, in order "
+#~ "to avoid duplicate work."
+#~ msgstr ""
+#~ "Des appels à traductions envoyés dans &email-debian-i18n;, avec le "
+#~ "fichier <filename>debian/po/templates.pot</filename> attaché sont "
+#~ "encouragés. Veuillez vous assurer de bien mentionner dans ces appels à "
+#~ "traductions les langues pour lesquelles des traductions existent déjà, "
+#~ "afin d'éviter du travail en double."
+
+# type: Content of: <chapter><section><section><section><para>
+#~ msgid ""
+#~ "To <literal>unfuzzy</literal> translations, you can proceed the following "
+#~ "way:"
+#~ msgstr ""
+#~ "Pour corriger les traductions, vous pouvez procéder de la manière "
+#~ "suivante :"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2008-08-08 11:36-0300\n"
+"POT-Creation-Date: 2009-01-23 09:48+0100\n"
"PO-Revision-Date: 2007-07-01 23:09+0000\n"
"Last-Translator: <>\n"
"Language-Team: \n"
"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><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:110
+#, no-wrap
+msgid ""
+"\n"
+"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:102
+#: beyond-pkging.dbk:137
msgid "Quality Assurance effort"
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:104
+#: beyond-pkging.dbk:139
msgid "Daily work"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:106
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:120
+#: beyond-pkging.dbk:155
msgid "Bug squashing parties"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:122
+#: 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-"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:131
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:140
+#: 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. "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:147
+#: 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:155
+#: beyond-pkging.dbk:190
msgid "Contacting other maintainers"
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:157
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:163
+#: 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><"
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:171
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><title>
-#: beyond-pkging.dbk:180
+#: beyond-pkging.dbk:215
msgid "Dealing with inactive and/or unreachable maintainers"
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:182
+#: 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. "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:189
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:200
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:206
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: beyond-pkging.dbk:214
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: beyond-pkging.dbk:224
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: beyond-pkging.dbk:233
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:240
+#: beyond-pkging.dbk:275
msgid ""
"A bit of a problem are packages which were sponsored — the maintainer is not "
"an official Debian developer. The <literal>echelon</literal> information is "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:248
+#: beyond-pkging.dbk:283
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:253
+#: beyond-pkging.dbk:288
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:261
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:269
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:275
+#: beyond-pkging.dbk:310
msgid ""
"If you are interested in working in the MIA team, please have a look at the "
"README file in <filename>/org/qa.debian.org/mia</filename> on <literal> qa."
msgstr ""
# type: Content of: <chapter><section><title>
-#: beyond-pkging.dbk:283
+#: beyond-pkging.dbk:318
msgid "Interacting with prospective Debian developers"
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:285
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:291
+#: beyond-pkging.dbk:326
msgid "Sponsoring packages"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:293
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:304
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:311
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:318
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:325
+#: beyond-pkging.dbk:360
msgid "Managing sponsored packages"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:327
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:332
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:341
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:346
+#: 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:348
+#: beyond-pkging.dbk:383
#, no-wrap
msgid ""
"\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:352
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:357
+#: 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, "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:363
+#: 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:367
+#: 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:373
+#: beyond-pkging.dbk:408
msgid "Advocating new developers"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:375
+#: beyond-pkging.dbk:410
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:382
+#: beyond-pkging.dbk:417
msgid "Handling new maintainer applications"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:384
+#: beyond-pkging.dbk:419
msgid ""
"Please see <ulink url=\"&url-newmaint-amchecklist;\">Checklist for "
"Application Managers</ulink> at the Debian web site."
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2008-08-08 11:36-0300\n"
+"POT-Creation-Date: 2009-01-23 09:48+0100\n"
"PO-Revision-Date: 2007-07-01 23:15+0000\n"
"Last-Translator: <>\n"
"Language-Team: \n"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:405
+#: pkgs.dbk:406
msgid ""
-"Delayed uploads are done for the moment via the delayed queue at "
-"<literal>gluck </literal>. The upload-directory is <literal>gluck:~tfheen/"
-"DELAYED/[012345678]-day</literal>. 0-day is uploaded multiple times per day "
-"to <literal>&ftp-master-host;</literal>."
+"It is sometimes useful to upload a package immediately, but to want this "
+"package to arrive in the archive only a few days later. For example, when "
+"preparing a <link linkend=\"nmu\">Non-maintainer Upload</link>, you might "
+"want to give the maintainer a few days to react."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:411
-msgid "With a fairly recent dput, this section"
-msgstr ""
-
-# type: Content of: <chapter><section><section><screen>
#: pkgs.dbk:413
-#, no-wrap
-msgid ""
-"\n"
-"[tfheen_delayed]\n"
-"method = scp\n"
-"fqdn = gluck.debian.org\n"
-"incoming = ~tfheen\n"
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:420
msgid ""
-"in <filename>~/.dput.cf</filename> should work fine for uploading to the "
-"<literal>DELAYED</literal> queue."
+"An upload to the delayed directory keeps the package in <ulink url=\"http://"
+"ftp-master.debian.org/deferred.html\"> the deferred uploads queue\"</"
+"ulink>. When the specified waiting time is over, the package is moved into "
+"the regular incoming directory for processing. This is done through "
+"automatic uploading to <literal>&ftp-master-host;</literal> in upload-"
+"directory <literal>DELAYED/[012345678]-day</literal>. 0-day is uploaded "
+"multiple times per day to <literal>&ftp-master-host;</literal>."
msgstr ""
# type: Content of: <chapter><section><section><para>
#: pkgs.dbk:424
msgid ""
-"<emphasis>Note:</emphasis> Since this upload queue goes to <literal>&ftp-"
-"master-host;</literal>, the prescription found in <xref linkend=\"upload-ftp-"
-"master\"/> applies here as well."
+"With dput, you can use the <literal>--delayed <replaceable>DELAY</"
+"replaceable></literal> parameter to put the package into one of the queues."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:431
+#: pkgs.dbk:430
msgid "Security uploads"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:433
+#: pkgs.dbk:432
msgid ""
"Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security "
"upload queue (<literal>oldstable-security</literal>, <literal>stable-"
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:443
+#: pkgs.dbk:442
msgid "Other upload queues"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:445
+#: pkgs.dbk:444
msgid ""
"The scp queues on <literal>&ftp-master-host;</literal>, and <literal> "
"security.debian.org</literal> are mostly unusable due to the login "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:450
+#: pkgs.dbk:449
msgid ""
"The anonymous queues on ftp.uni-erlangen.de and ftp.uk.debian.org are "
"currently down. Work is underway to resurrect them."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:454
+#: pkgs.dbk:453
msgid ""
"The queues on master.debian.org, samosa.debian.org, master.debian.or.jp, and "
"ftp.chiark.greenend.org.uk are down permanently, and will not be "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:462
+#: pkgs.dbk:461
msgid "Notification that a new package has been installed"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:464
+#: pkgs.dbk:463
msgid ""
"The Debian archive maintainers are responsible for handling package "
"uploads. For the most part, uploads are automatically handled on a daily "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:474
+#: pkgs.dbk:473
msgid ""
"In any case, you will receive an email notification indicating that the "
"package has been added to the archive, which also indicates which bugs will "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:480
+#: pkgs.dbk:479
msgid ""
"The installation notification also includes information on what section the "
"package was inserted into. If there is a disparity, you will receive a "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:485
+#: pkgs.dbk:484
msgid ""
"Note that if you upload via queues, the queue daemon software will also send "
"you a notification by email."
msgstr ""
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:493
+#: pkgs.dbk:492
msgid "Specifying the package section, subsection and priority"
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:495
+#: pkgs.dbk:494
msgid ""
"The <filename>debian/control</filename> file's <literal>Section</literal> "
"and <literal>Priority</literal> fields do not actually specify where the "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:503
+#: pkgs.dbk:502
msgid ""
"The archive maintainers keep track of the canonical sections and priorities "
"for packages in the <literal>override file</literal>. If there is a "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:513
+#: pkgs.dbk:512
msgid ""
"To alter the actual section that a package is put in, you need to first make "
"sure that the <filename>debian/control</filename> file in your package is "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:521
+#: pkgs.dbk:520
msgid ""
"For more information about <literal>override files</literal>, see "
"<citerefentry> <refentrytitle>dpkg-scanpackages</refentrytitle> "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:527
+#: pkgs.dbk:526
msgid ""
"Note that the <literal>Section</literal> field describes both the section as "
"well as the subsection, which are described in <xref linkend=\"archive-"
msgstr ""
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:536
+#: pkgs.dbk:535
msgid "Handling bugs"
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:538
+#: pkgs.dbk:537
msgid ""
"Every developer has to be able to work with the Debian <ulink url=\"&url-bts;"
"\">bug tracking system</ulink>. This includes knowing how to file bug "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:544
+#: pkgs.dbk:543
msgid ""
"The bug tracking system's features are described in the <ulink url=\"&url-"
"bts-devel;\">BTS documentation for developers</ulink>. This includes "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:550
+#: pkgs.dbk:549
msgid ""
"Operations such as reassigning bugs to other packages, merging separate bug "
"reports about the same issue, or reopening bugs when they are prematurely "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:558
+#: pkgs.dbk:557
msgid "Monitoring bugs"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:560
+#: pkgs.dbk:559
msgid ""
"If you want to be a good maintainer, you should periodically check the "
"<ulink url=\"&url-bts;\">Debian bug tracking system (BTS)</ulink> for your "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:567
+#: pkgs.dbk:566
msgid ""
"Maintainers interact with the BTS via email addresses at <literal>&bugs-host;"
"</literal>. Documentation on available commands can be found at <ulink url="
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:574
+#: pkgs.dbk:573
msgid ""
"Some find it useful to get periodic reports on open bugs. You can add a "
"cron job such as the following if you want to get a weekly email outlining "
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:578
+#: pkgs.dbk:577
#, no-wrap
msgid ""
"\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:583
+#: pkgs.dbk:582
msgid ""
"Replace <replaceable>address</replaceable> with your official Debian "
"maintainer address."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:589
+#: pkgs.dbk:588
msgid "Responding to bugs"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:591
+#: pkgs.dbk:590
msgid ""
"When responding to bugs, make sure that any discussion you have about bugs "
"is sent both to the original submitter of the bug, and to the bug itself (e."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:600
+#: pkgs.dbk:599
msgid ""
"If you get a bug which mentions FTBFS, this means Fails to build from "
"source. Porters frequently use this acronym."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:604
+#: pkgs.dbk:603
msgid ""
"Once you've dealt with a bug report (e.g. fixed it), mark it as "
"<literal>done</literal> (close it) by sending an explanation message to "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:611
+#: pkgs.dbk:610
msgid ""
"You should <emphasis>never</emphasis> close bugs via the bug server "
"<literal>close</literal> command sent to &email-bts-control;. If you do so, "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:619
+#: pkgs.dbk:618
msgid "Bug housekeeping"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:621
+#: pkgs.dbk:620
msgid ""
"As a package maintainer, you will often find bugs in other packages or have "
"bugs reported against your packages which are actually bugs in other "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:632
+#: pkgs.dbk:631
msgid ""
"Filing bugs for problems that you find in other packages is one of the civic "
"obligations of maintainership, see <xref linkend=\"submit-bug\"/> for "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:637
+#: pkgs.dbk:636
msgid "Here's a list of steps that you may follow to handle a bug report:"
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:642
+#: pkgs.dbk:641
msgid ""
"Decide whether the report corresponds to a real bug or not. Sometimes users "
"are just calling a program in the wrong way because they haven't read the "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:652
+#: pkgs.dbk:651
msgid ""
"If the bug submitter disagrees with your decision to close the bug, they may "
"reopen it until you find an agreement on how to handle it. If you don't "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:666
+#: pkgs.dbk:665
msgid ""
"If the bug is real but it's caused by another package, just reassign the bug "
"to the right package. If you don't know which package it should be "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:678
+#: pkgs.dbk:677
msgid ""
"If the bug affects the operation of your package, please consider cloning "
"the bug and reassigning the clone to the package that really causes the "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:688
+#: pkgs.dbk:687
msgid ""
"Sometimes you also have to adjust the severity of the bug so that it matches "
"our definition of the severity. That's because people tend to inflate the "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:696
+#: pkgs.dbk:695
msgid ""
"If the bug is real but the same problem has already been reported by someone "
"else, then the two relevant bug reports should be merged into one using the "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:707
+#: pkgs.dbk:706
msgid ""
"The bug submitter may have forgotten to provide some information, in which "
"case you have to ask them for the required information. You may use the "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:718
+#: pkgs.dbk:717
msgid ""
"If the bug is related to the packaging, you just fix it. If you are not "
"able to fix it yourself, then tag the bug as <literal>help</literal>. You "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:732
+#: pkgs.dbk:731
msgid ""
"If you have fixed a bug in your local copy, or if a fix has been committed "
"to the CVS repository, you may tag the bug as <literal>pending</literal> to "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:742
+#: pkgs.dbk:741
msgid ""
"Once a corrected package is available in the archive, the bug should be "
"closed indicating the version in which it was fixed. This can be done "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:751
+#: pkgs.dbk:750
msgid "When bugs are closed by new uploads"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:753
+#: pkgs.dbk:752
msgid ""
"As bugs and problems are fixed in your packages, it is your responsibility "
"as the package maintainer to close these bugs. However, you should not "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:761
+#: pkgs.dbk:760
msgid ""
"However, it's possible to avoid having to manually close bugs after the "
"upload — just list the fixed bugs in your <filename>debian/changelog</"
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:766
+#: pkgs.dbk:765
#, no-wrap
msgid ""
"\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:775
+#: pkgs.dbk:774
msgid ""
"Technically speaking, the following Perl regular expression describes how "
"bug closing changelogs are identified:"
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:778
+#: pkgs.dbk:777
#, no-wrap
msgid ""
"\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:782
+#: pkgs.dbk:781
msgid ""
"We prefer the <literal>closes: #<replaceable>XXX</replaceable></literal> "
"syntax, as it is the most concise entry and the easiest to integrate with "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:791
+#: pkgs.dbk:790
msgid ""
"Historically, uploads identified as <link linkend=\"nmu\">Non-maintainer "
"upload (NMU)</link> were tagged <literal>fixed</literal> instead of being "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:797
+#: pkgs.dbk:796
msgid ""
"If you happen to mistype a bug number or forget a bug in the changelog "
"entries, don't hesitate to undo any damage the error caused. To reopen "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:809
+#: pkgs.dbk:808
msgid ""
"Bear in mind that it is not obligatory to close bugs using the changelog as "
"described above. If you simply want to close bugs that don't have anything "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:817
+#: pkgs.dbk:816
msgid ""
"For general information on how to write your changelog entries, see <xref "
"linkend=\"bpp-debian-changelog\"/> ."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:823
+#: pkgs.dbk:822
msgid "Handling security-related bugs"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:825
+#: pkgs.dbk:824
msgid ""
"Due to their sensitive nature, security-related bugs must be handled "
"carefully. The Debian Security Team exists to coordinate this activity, "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:834
+#: pkgs.dbk:831
msgid ""
"When you become aware of a security-related bug in a Debian package, whether "
"or not you are the maintainer, collect pertinent information about the "
"problem, and promptly contact the security team at &email-security-team; as "
"soon as possible. <emphasis role=\"strong\">DO NOT UPLOAD</emphasis> any "
-"packages for <literal>stable</literal>; the security team will do that. "
-"Useful information includes, for example:"
+"packages for <literal>stable</literal> without contacting the team. Useful "
+"information includes, for example:"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:844
+#: pkgs.dbk:841
msgid ""
"Which versions of the package are known to be affected by the bug. Check "
"each version that is present in a supported Debian release, as well as "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:851
+#: pkgs.dbk:848
msgid ""
"The nature of the fix, if any is available (patches are especially helpful)"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:856
+#: pkgs.dbk:853
msgid ""
"Any fixed packages that you have prepared yourself (send only the <literal>."
"diff.gz</literal> and <literal>.dsc</literal> files and read <xref linkend="
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:863
+#: pkgs.dbk:860
msgid ""
"Any assistance you can provide to help with testing (exploits, regression "
"testing, etc.)"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:869
+#: pkgs.dbk:866
msgid ""
"Any information needed for the advisory (see <xref linkend=\"bug-security-"
"advisories\"/> )"
msgstr ""
+# type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:871
+msgid ""
+"As the maintainer of the package, you have the responsibility to maintain "
+"it, even in the stable release. You are in the best position to evaluate "
+"patches and test updated packages, so please see the sections below on how "
+"to prepare packages for the Security Team to handle."
+msgstr ""
+
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:875
+#: pkgs.dbk:877
+msgid "The Security Tracker"
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:879
+msgid ""
+"The security team maintains a central database, the <ulink url=\"http://"
+"security-tracker.debian.net/\">Debian Security Tracker</ulink>. This "
+"contains all public information that is known about security issues: which "
+"packages and versions are affected or fixed, and thus whether stable, "
+"testing and/or unstable are vulnerable. Information that is still "
+"confidential is not added to the tracker."
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:887
+msgid ""
+"You can search it for a specific issue, but also on package name. Look for "
+"your package to see which issues are still open. If you can, please provide "
+"more information about those issues, or help to address them in your "
+"package. Instructions are on the tracker web pages."
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:895
msgid "Confidentiality"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:877
+#: pkgs.dbk:897
msgid ""
"Unlike most other activities within Debian, information about security "
"issues must sometimes be kept private for a time. This allows software "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:884
+#: pkgs.dbk:904
msgid "There are several ways developers can learn of a security problem:"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:889
+#: pkgs.dbk:909
msgid "they notice it on a public forum (mailing list, web site, etc.)"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:894
+#: pkgs.dbk:914
msgid "someone files a bug report"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:899
+#: pkgs.dbk:919
msgid "someone informs them via private email"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:904
+#: pkgs.dbk:924
msgid ""
"In the first two cases, the information is public and it is important to "
"have a fix as soon as possible. In the last case, however, it might not be "
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:912
+#: pkgs.dbk:932
msgid ""
"If the security exposure is minor, there is sometimes no need to keep the "
"problem a secret and a fix should be made and released."
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:918
+#: pkgs.dbk:938
msgid ""
"If the problem is severe, it is preferable to share the information with "
"other vendors and coordinate a release. The security team keeps in contact "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:925
+#: pkgs.dbk:945
msgid ""
"In all cases if the person who reports the problem asks that it not be "
"disclosed, such requests should be honored, with the obvious exception of "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:932
+#: pkgs.dbk:952
msgid ""
"Please note that if secrecy is needed you may not upload a fix to "
"<literal>unstable</literal> (or anywhere else, such as a public CVS "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:939
+#: pkgs.dbk:959
msgid ""
"There are two reasons for releasing information even though secrecy is "
"requested: the problem has been known for a while, or the problem or exploit "
"has become public."
msgstr ""
+# type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:964
+msgid ""
+"The Security Team has a PGP-key to enable encrypted communication about "
+"sensitive issues. See the <ulink url=\"http://www.debian.org/security/faq.en."
+"html#contact\">Security Team FAQ</ulink> for details."
+msgstr ""
+
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:946
+#: pkgs.dbk:970
msgid "Security Advisories"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:948
+#: pkgs.dbk:972
msgid ""
"Security advisories are only issued for the current, released stable "
"distribution, and <emphasis>not</emphasis> for <literal>testing</literal> or "
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:961
+#: pkgs.dbk:985
msgid "A description of the problem and its scope, including:"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
-#: pkgs.dbk:966
+#: pkgs.dbk:990
msgid "The type of problem (privilege escalation, denial of service, etc.)"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
-#: pkgs.dbk:971
+#: pkgs.dbk:995
msgid "What privileges may be gained, and by whom (if any)"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
-#: pkgs.dbk:976
+#: pkgs.dbk:1000
msgid "How it can be exploited"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
-#: pkgs.dbk:981
+#: pkgs.dbk:1005
msgid "Whether it is remotely or locally exploitable"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
-#: pkgs.dbk:986
+#: pkgs.dbk:1010
msgid "How the problem was fixed"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:991
+#: pkgs.dbk:1015
msgid "This information allows users to assess the threat to their systems."
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:996
+#: pkgs.dbk:1020
msgid "Version numbers of affected packages"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1001
+#: pkgs.dbk:1025
msgid "Version numbers of fixed packages"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1006
+#: pkgs.dbk:1030
msgid ""
"Information on where to obtain the updated packages (usually from the Debian "
"security archive)"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1012
+#: pkgs.dbk:1036
msgid ""
"References to upstream advisories, <ulink url=\"http://cve.mitre.org\">CVE</"
"ulink> identifiers, and any other information useful in cross-referencing "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1021
+#: pkgs.dbk:1045
msgid "Preparing packages to address security issues"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1023
+#: pkgs.dbk:1047
msgid ""
"One way that you can assist the security team in their duties is to provide "
"them with fixed packages suitable for a security advisory for the stable "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1028
+#: pkgs.dbk:1052
msgid ""
"When an update is made to the stable release, care must be taken to avoid "
"changing system behavior or introducing new bugs. In order to do this, make "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1036
+#: pkgs.dbk:1060
msgid ""
"This means that moving to a new upstream version is not a good solution. "
"Instead, the relevant changes should be back-ported to the version present "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1042
+#: pkgs.dbk:1066
msgid ""
"In some cases, it is not possible to back-port a security fix, for example "
"when large amounts of source code need to be modified or rewritten. If this "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1049
+#: pkgs.dbk:1073
msgid ""
"Related to this is another important guideline: always test your changes. "
"If you have an exploit available, try it and see if it indeed succeeds on "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1056
+#: pkgs.dbk:1080
msgid ""
"Do <emphasis role=\"strong\">NOT</emphasis> include any changes in your "
"package which are not directly related to fixing the vulnerability. These "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1066
+#: pkgs.dbk:1090
msgid ""
"Review and test your changes as much as possible. Check the differences "
"from the previous version repeatedly (<command>interdiff</command> from the "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1074
+#: pkgs.dbk:1098
msgid "Be sure to verify the following items:"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1079
+#: pkgs.dbk:1103
msgid ""
-"Target the right distribution in your <filename>debian/changelog</"
-"filename>. For <literal>stable</literal> this is <literal>stable-security</"
-"literal> and for testing this is <literal>testing-security</literal>, and "
-"for the previous stable release, this is <literal>oldstable-security</"
-"literal>. Do not target <replaceable>distribution</replaceable><literal>-"
-"proposed-updates</literal> or <literal>stable</literal>!"
-msgstr ""
-
-# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1089
-msgid "The upload should have urgency=high."
+"<emphasis role=\"strong\">Target the right distribution</emphasis> in your "
+"<filename>debian/changelog</filename>. For <literal>stable</literal> this "
+"is <literal>stable-security</literal> and for testing this is "
+"<literal>testing-security</literal>, and for the previous stable release, "
+"this is <literal>oldstable-security</literal>. Do not target "
+"<replaceable>distribution</replaceable><literal>-proposed-updates</literal> "
+"or <literal>stable</literal>!"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1094
+#: pkgs.dbk:1114
msgid ""
-"Make descriptive, meaningful changelog entries. Others will rely on them to "
-"determine whether a particular bug was fixed. Always include an external "
-"reference, preferably a CVE identifier, so that it can be cross-referenced. "
-"Include the same information in the changelog for <literal>unstable</"
-"literal>, so that it is clear that the same bug was fixed, as this is very "
-"helpful when verifying that the bug is fixed in the next stable release. If "
-"a CVE identifier has not yet been assigned, the security team will request "
-"one so that it can be included in the package and in the advisory."
+"The upload should have <emphasis role=\"strong\">urgency=high</emphasis>."
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1107
+#: pkgs.dbk:1119
msgid ""
-"Make sure the version number is proper. It must be greater than the current "
-"package, but less than package versions in later distributions. If in "
-"doubt, test it with <literal>dpkg --compare-versions</literal>. Be careful "
-"not to re-use a version number that you have already used for a previous "
-"upload. For <literal>testing</literal>, there must be a higher version in "
-"<literal>unstable</literal>. If there is none yet (for example, if "
-"<literal>testing</literal> and <literal>unstable</literal> have the same "
-"version) you must upload a new version to <literal>unstable</literal> first."
+"Make descriptive, meaningful changelog entries. Others will rely on them to "
+"determine whether a particular bug was fixed. Add <literal>closes:</"
+"literal> statements for any <emphasis role=\"strong\">Debian bugs</emphasis> "
+"filed. Always include an external reference, preferably a <emphasis role="
+"\"strong\">CVE identifier</emphasis>, so that it can be cross-referenced. "
+"However, if a CVE identifier has not yet been assigned, do not wait for it "
+"but continue the process. The identifier can be cross-referenced later."
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1119
+#: pkgs.dbk:1130
msgid ""
-"Do not make source-only uploads if your package has any binary-all packages "
-"(do not use the <literal>-S</literal> option to <command>dpkg-buildpackage</"
-"command>). The <command>buildd</command> infrastructure will not build "
-"those. This point applies to normal package uploads as well."
+"Make sure the <emphasis role=\"strong\">version number</emphasis> is "
+"proper. It must be greater than the current package, but less than package "
+"versions in later distributions. If in doubt, test it with <literal>dpkg --"
+"compare-versions</literal>. Be careful not to re-use a version number that "
+"you have already used for a previous upload, or one that conflicts with a "
+"binNMU. The convention is to append <literal>+</"
+"literal><replaceable>codename</replaceable><literal>1</literal>, e.g. "
+"<literal>1:2.4.3-4+etch1</literal>, of course increasing 1 for any "
+"subsequent uploads."
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1128
+#: pkgs.dbk:1143
msgid ""
"Unless the upstream source has been uploaded to <literal>security.debian.org "
-"</literal> before (by a previous security update), build the upload with "
-"full upstream source (<literal>dpkg-buildpackage -sa</literal>). If there "
-"has been a previous upload to <literal>security.debian.org</literal> with "
-"the same upstream version, you may upload without upstream source (<literal> "
-"dpkg-buildpackage -sd</literal>)."
+"</literal> before (by a previous security update), build the upload "
+"<emphasis role=\"strong\">with full upstream source</emphasis> "
+"(<literal>dpkg-buildpackage -sa</literal>). If there has been a previous "
+"upload to <literal>security.debian.org</literal> with the same upstream "
+"version, you may upload without upstream source (<literal> dpkg-buildpackage "
+"-sd</literal>)."
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1138
+#: pkgs.dbk:1153
msgid ""
-"Be sure to use the exact same <filename>*.orig.tar.gz</filename> as used in "
-"the normal archive, otherwise it is not possible to move the security fix "
-"into the main archives later."
+"Be sure to use the <emphasis role=\"strong\">exact same <filename>*.orig.tar."
+"gz</filename></emphasis> as used in the normal archive, otherwise it is not "
+"possible to move the security fix into the main archives later."
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1145
+#: pkgs.dbk:1161
msgid ""
-"Build the package on a clean system which only has packages installed from "
-"the distribution you are building for. If you do not have such a system "
-"yourself, you can use a debian.org machine (see <xref linkend=\"server-"
-"machines\"/> ) or setup a chroot (see <xref linkend=\"pbuilder\"/> and <xref "
-"linkend=\"debootstrap\"/> )."
+"Build the package on a <emphasis role=\"strong\">clean system</emphasis> "
+"which only has packages installed from the distribution you are building "
+"for. If you do not have such a system yourself, you can use a debian.org "
+"machine (see <xref linkend=\"server-machines\"/> ) or setup a chroot (see "
+"<xref linkend=\"pbuilder\"/> and <xref linkend=\"debootstrap\"/> )."
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1156
+#: pkgs.dbk:1172
msgid "Uploading the fixed package"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1158
+#: pkgs.dbk:1174
msgid ""
"Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security "
"upload queue (<literal>oldstable-security</literal>, <literal>stable-"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1165
+#: pkgs.dbk:1181
msgid ""
"Do <emphasis role=\"strong\">NOT</emphasis> upload your fix to <literal> "
"proposed-updates</literal> without coordinating with the security team. "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1175
+#: pkgs.dbk:1191
msgid ""
"Once you have created and tested the new package and it has been approved by "
"the security team, it needs to be uploaded so that it can be installed in "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1181
+#: pkgs.dbk:1197
msgid ""
"Once an upload to the security queue has been accepted, the package will "
-"automatically be rebuilt for all architectures and stored for verification "
-"by the security team."
+"automatically be built for all architectures and stored for verification by "
+"the security team."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1186
+#: pkgs.dbk:1202
msgid ""
"Uploads which are waiting for acceptance or verification are only accessible "
"by the security team. This is necessary since there might be fixes for "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1191
+#: pkgs.dbk:1207
msgid ""
"If a member of the security team accepts a package, it will be installed on "
"<literal>security.debian.org</literal> as well as proposed for the proper "
msgstr ""
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:1203
+#: pkgs.dbk:1219
msgid "Moving, removing, renaming, adopting, and orphaning packages"
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:1205
+#: pkgs.dbk:1221
msgid ""
"Some archive manipulation operations are not automated in the Debian upload "
"process. These procedures should be manually followed by maintainers. This "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1210
+#: pkgs.dbk:1226
msgid "Moving packages"
msgstr ""
# type: Content of: <chapter><section><section><para><footnote>
-#: pkgs.dbk:1212
+#: pkgs.dbk:1228
msgid ""
"Sometimes a package will change its section. For instance, a package from "
"the `non-free' section might be GPL'd in a later version, in which case the "
msgstr ""
# type: Content of: <chapter><section><section><para><footnote><para>
-#: pkgs.dbk:1214
+#: pkgs.dbk:1230
msgid ""
"See the <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> for "
"guidelines on what section a package belongs in."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1216 pkgs.dbk:1648
+#: pkgs.dbk:1232 pkgs.dbk:1664
msgid "</footnote>"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1219
+#: pkgs.dbk:1235
msgid ""
"If you need to change the section for one of your packages, change the "
"package control information to place the package in the desired section, and "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1231
+#: pkgs.dbk:1247
msgid ""
"If, on the other hand, you need to change the <literal>subsection</literal> "
"of one of your packages (e.g., ``devel'', ``admin''), the procedure is "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1240
+#: pkgs.dbk:1256
msgid "Removing packages"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1242
+#: pkgs.dbk:1258
msgid ""
"If for some reason you want to completely remove a package (say, if it is an "
"old compatibility library which is no longer required), you need to file a "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1259
+#: pkgs.dbk:1275
msgid ""
"If you want to remove a package you maintain, you should note this in the "
"bug title by prepending <literal>ROM</literal> (Request Of Maintainer). "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1268
+#: pkgs.dbk:1284
msgid ""
"Note that removals can only be done for the <literal>unstable </literal>, "
"<literal>experimental</literal> and <literal>stable </literal> "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1277
+#: pkgs.dbk:1293
msgid ""
"There is one exception when an explicit removal request is not necessary: If "
"a (source or binary) package is an orphan, it will be removed semi-"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1286
+#: pkgs.dbk:1302
msgid ""
"In your removal request, you have to detail the reasons justifying the "
"request. This is to avoid unwanted removals and to keep a trace of why a "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1292
+#: pkgs.dbk:1308
msgid ""
"Usually you only ask for the removal of a package maintained by yourself. "
"If you want to remove another package, you have to get the approval of its "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1302
+#: pkgs.dbk:1318
msgid ""
"Further information relating to these and other package removal related "
"topics may be found at <ulink url=\"http://wiki.debian.org/ftpmaster_Removals"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1307
+#: pkgs.dbk:1323
msgid ""
"If in doubt concerning whether a package is disposable, email &email-debian-"
"devel; asking for opinions. Also of interest is the <command>apt-cache</"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1320
+#: pkgs.dbk:1336
msgid ""
"Once the package has been removed, the package's bugs should be handled. "
"They should either be reassigned to another package in the case where the "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1327
+#: pkgs.dbk:1343
msgid "Removing packages from <filename>Incoming</filename>"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1329
+#: pkgs.dbk:1345
msgid ""
"In the past, it was possible to remove packages from <filename>incoming</"
"filename>. However, with the introduction of the new incoming system, this "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1344
+#: pkgs.dbk:1360
msgid "Replacing or renaming packages"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1346
+#: pkgs.dbk:1362
msgid ""
"When the upstream maintainers for one of your packages chose to rename their "
"software (or you made a mistake naming your package), you should follow a "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1362
+#: pkgs.dbk:1378
msgid ""
"At other times, you may make a mistake in constructing your package and wish "
"to replace it. The only way to do this is to increase the version number "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1376
+#: pkgs.dbk:1392
msgid "Orphaning a package"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1378
+#: pkgs.dbk:1394
msgid ""
"If you can no longer maintain a package, you need to inform others, and see "
"that the package is marked as orphaned. You should set the package "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1393
+#: pkgs.dbk:1409
msgid ""
"If you just intend to give the package away, but you can keep maintainership "
"for the moment, then you should instead submit a bug against <systemitem "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1401
+#: pkgs.dbk:1417
msgid ""
"More information is on the <ulink url=\"&url-wnpp;\">WNPP web pages</ulink>."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1407
+#: pkgs.dbk:1423
msgid "Adopting a package"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1409
+#: pkgs.dbk:1425
msgid ""
"A list of packages in need of a new maintainer is available in the <ulink "
"url=\"&url-wnpp;\">Work-Needing and Prospective Packages list (WNPP)</"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1416
+#: pkgs.dbk:1432
msgid ""
"It is not OK to simply take over a package that you feel is neglected — that "
"would be package hijacking. You can, of course, contact the current "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1422
+#: pkgs.dbk:1438
msgid ""
"Generally, you may not take over the package without the assent of the "
"current maintainer. Even if they ignore you, that is still not grounds to "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1432
+#: pkgs.dbk:1448
msgid ""
"If you take over an old package, you probably want to be listed as the "
"package's official maintainer in the bug system. This will happen "
msgstr ""
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:1446
+#: pkgs.dbk:1462
msgid "Porting and being ported"
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:1448
+#: pkgs.dbk:1464
msgid ""
"Debian supports an ever-increasing number of architectures. Even if you are "
"not a porter, and you don't use any architecture but one, it is part of your "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:1454
+#: pkgs.dbk:1470
msgid ""
"Porting is the act of building Debian packages for architectures that are "
"different from the original architecture of the package maintainer's binary "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1463
+#: pkgs.dbk:1479
msgid "Being kind to porters"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1465
+#: pkgs.dbk:1481
msgid ""
"Porters have a difficult and unique task, since they are required to deal "
"with a large volume of packages. Ideally, every source package should build "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1473
+#: pkgs.dbk:1489
msgid ""
"The first and most important thing is to respond quickly to bug or issues "
"raised by porters. Please treat porters with courtesy, as if they were in "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1480
+#: pkgs.dbk:1496
msgid ""
"By far, most of the problems encountered by porters are caused by "
"<emphasis>packaging bugs</emphasis> in the source packages. Here is a "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1487
+#: pkgs.dbk:1503
msgid ""
"Make sure that your <literal>Build-Depends</literal> and <literal>Build-"
"Depends-Indep</literal> settings in <filename>debian/control</filename> are "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1502
+#: pkgs.dbk:1518
msgid ""
"If you can't set up a proper chroot, <command>dpkg-depcheck</command> may be "
"of assistance (see <xref linkend=\"dpkg-depcheck\"/> )."
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1506
+#: pkgs.dbk:1522
msgid ""
"See the <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> for "
"instructions on setting build dependencies."
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1512
+#: pkgs.dbk:1528
msgid ""
"Don't set architecture to a value other than <literal>all</literal> or "
"<literal>any</literal> unless you really mean it. In too many cases, "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1522
+#: pkgs.dbk:1538
msgid ""
"Make sure your source package is correct. Do <literal>dpkg-source -x "
"<replaceable>package</replaceable>.dsc</literal> to make sure your source "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1530
+#: pkgs.dbk:1546
msgid ""
"Make sure you don't ship your source package with the <filename>debian/"
"files</filename> or <filename>debian/substvars</filename> files. They "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1538
+#: pkgs.dbk:1554
msgid ""
"Make sure you don't rely on locally installed or hacked configurations or "
"programs. For instance, you should never be calling programs in <filename>/"
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1547
+#: pkgs.dbk:1563
msgid ""
"Don't depend on the package you're building being installed already (a sub-"
"case of the above issue). There are, of course, exceptions to this rule, but "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1555
+#: pkgs.dbk:1571
msgid ""
"Don't rely on the compiler being a certain version, if possible. If not, "
"then make sure your build dependencies reflect the restrictions, although "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1563
+#: pkgs.dbk:1579
msgid ""
"Make sure your debian/rules contains separate <literal>binary-arch</literal> "
"and <literal>binary-indep</literal> targets, as the Debian Policy Manual "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1574
+#: pkgs.dbk:1590
msgid "Guidelines for porter uploads"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1576
+#: pkgs.dbk:1592
msgid ""
"If the package builds out of the box for the architecture to be ported to, "
"you are in luck and your job is easy. This section applies to that case; it "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1584
+#: pkgs.dbk:1600
msgid ""
"For a porter upload, no changes are being made to the source. You do not "
"need to touch any of the files in the source package. This includes "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1589
+#: pkgs.dbk:1605
msgid ""
"The way to invoke <command>dpkg-buildpackage</command> is as <literal>dpkg-"
"buildpackage -B -m<replaceable>porter-email</replaceable></literal>. Of "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1598
+#: pkgs.dbk:1614
msgid ""
"If you are working on a Debian machine for your porting efforts and you need "
"to sign your upload locally for its acceptance in the archive, you can run "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1605
+#: pkgs.dbk:1621
msgid "Recompilation or binary-only NMU"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1607
+#: pkgs.dbk:1623
msgid ""
"Sometimes the initial porter upload is problematic because the environment "
"in which the package was built was not good enough (outdated or obsolete "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1616
+#: pkgs.dbk:1632
msgid ""
"You have to make sure that your binary-only NMU doesn't render the package "
"uninstallable. This could happen when a source package generates arch-"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1623
+#: pkgs.dbk:1639
msgid ""
"Despite the required modification of the changelog, these are called binary-"
"only NMUs — there is no need in this case to trigger all other architectures "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1628
+#: pkgs.dbk:1644
msgid ""
"Such recompilations require special ``magic'' version numbering, so that the "
"archive maintenance tools recognize that, even though there is a new Debian "
msgstr ""
# type: Content of: <chapter><section><section><section><para><footnote>
-#: pkgs.dbk:1635
+#: pkgs.dbk:1651
msgid ""
"The ``magic'' for a recompilation-only NMU is triggered by using a suffix "
"appended to the package version number, following the form <literal> "
msgstr ""
# type: Content of: <chapter><section><section><section><para><footnote><para>
-#: pkgs.dbk:1643
+#: pkgs.dbk:1659
msgid ""
"In the past, such NMUs used the third-level number on the Debian part of the "
"revision to denote their recompilation-only status; however, this syntax was "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1651
+#: pkgs.dbk:1667
msgid ""
"Similar to initial porter uploads, the correct way of invoking <command>dpkg-"
"buildpackage</command> is <literal>dpkg-buildpackage -B</literal> to only "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1658
+#: pkgs.dbk:1674
msgid "When to do a source NMU if you are a porter"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1660
+#: pkgs.dbk:1676
msgid ""
"Porters doing a source NMU generally follow the guidelines found in <xref "
"linkend=\"nmu\"/> , just like non-porters. However, it is expected that the "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1669
+#: pkgs.dbk:1685
msgid ""
"If you are a porter doing an NMU for <literal>unstable</literal>, the above "
"guidelines for porting should be followed, with two variations. Firstly, "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1681
+#: pkgs.dbk:1697
msgid ""
"Secondly, porters doing source NMUs should make sure that the bug they "
"submit to the BTS should be of severity <literal>serious</literal> or "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1689
+#: pkgs.dbk:1705
msgid ""
"Porters should try to avoid patches which simply kludge around bugs in the "
"current version of the compile environment, kernel, or libc. Sometimes such "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1697
+#: pkgs.dbk:1713
msgid ""
"Porters may also have an unofficial location where they can put the results "
"of their work during the waiting period. This helps others running the port "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1707
+#: pkgs.dbk:1723
msgid "Porting infrastructure and automation"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1709
+#: pkgs.dbk:1725
msgid ""
"There is infrastructure and several tools to help automate package porting. "
"This section contains a brief overview of this automation and porting to "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1714
+#: pkgs.dbk:1730
msgid "Mailing lists and web pages"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1716
+#: pkgs.dbk:1732
msgid ""
"Web pages containing the status of each port can be found at <ulink url="
"\"&url-debian-ports;\"></ulink>."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1720
+#: pkgs.dbk:1736
msgid ""
"Each port of Debian has a mailing list. The list of porting mailing lists "
"can be found at <ulink url=\"&url-debian-port-lists;\"></ulink>. These "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1728
+#: pkgs.dbk:1744
msgid "Porter tools"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1730
+#: pkgs.dbk:1746
msgid ""
"Descriptions of several porting tools can be found in <xref linkend=\"tools-"
"porting\"/> ."
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1736
+#: pkgs.dbk:1752
msgid "<systemitem role=\"package\">wanna-build</systemitem>"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1738
+#: pkgs.dbk:1754
msgid ""
"The <systemitem role=\"package\">wanna-build</systemitem> system is used as "
"a distributed, client-server build distribution system. It is usually used "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1746
+#: pkgs.dbk:1762
msgid ""
"<systemitem role=\"package\">wanna-build</systemitem> is not yet available "
"as a package; however, all Debian porting efforts are using it for automated "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1755
+#: pkgs.dbk:1771
msgid ""
"Most of the data produced by <systemitem role=\"package\">wanna-build </"
"systemitem> which is generally useful to porters is available on the web at "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1761
+#: pkgs.dbk:1777
msgid ""
"We are quite proud of this system, since it has so many possible uses. "
"Independent development groups can use the system for different sub-flavors "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1768
+#: pkgs.dbk:1784
msgid ""
"The buildds admins of each arch can be contacted at the mail address "
"<literal><replaceable>arch</replaceable>@buildd.debian.org</literal>."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1776
+#: pkgs.dbk:1792
msgid "When your package is <emphasis>not</emphasis> portable"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1778
+#: pkgs.dbk:1794
msgid ""
"Some packages still have issues with building and/or working on some of the "
"architectures supported by Debian, and cannot be ported at all, or not "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1785
+#: pkgs.dbk:1801
msgid ""
"In order to prevent broken packages from being uploaded to the archive, and "
"wasting buildd time, you need to do a few things:"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1791
+#: pkgs.dbk:1807
msgid ""
"First, make sure your package <emphasis>does</emphasis> fail to build on "
"architectures that it cannot support. There are a few ways to achieve "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1799
+#: pkgs.dbk:1815
msgid ""
"Additionally, if you believe the list of supported architectures is pretty "
"constant, you should change <literal>any</literal> to a list of supported "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1807
+#: pkgs.dbk:1823
msgid ""
"In order to prevent autobuilders from needlessly trying to build your "
"package, it must be included in <filename>packages-arch-specific</filename>, "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1817
+#: pkgs.dbk:1833
msgid ""
"Please note that it is insufficient to only add your package to Packages-"
"arch-specific without making it fail to build on unsupported architectures: "
msgstr ""
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:1830
+#: pkgs.dbk:1846
msgid "Non-Maintainer Uploads (NMUs)"
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:1832
-msgid ""
-"Under certain circumstances it is necessary for someone other than the "
-"official package maintainer to make a release of a package. This is called "
-"a non-maintainer upload, or NMU."
-msgstr ""
-
-# type: Content of: <chapter><section><para>
-#: pkgs.dbk:1837
-msgid ""
-"This section handles only source NMUs, i.e. NMUs which upload a new version "
-"of the package. For binary-only NMUs by porters or QA members, please see "
-"<xref linkend=\"binary-only-nmu\"/> . If a buildd builds and uploads a "
-"package, that too is strictly speaking a binary NMU. See <xref linkend="
-"\"wanna-build\"/> for some more information."
-msgstr ""
-
-# type: Content of: <chapter><section><para>
-#: pkgs.dbk:1844
+#: pkgs.dbk:1848
msgid ""
-"The main reason why NMUs are done is when a developer needs to fix another "
-"developer's package in order to address serious problems or crippling bugs "
-"or when the package maintainer is unable to release a fix in a timely "
-"fashion."
-msgstr ""
-
-# type: Content of: <chapter><section><para>
-#: pkgs.dbk:1849
-msgid ""
-"First and foremost, it is critical that NMU patches to source should be as "
-"non-disruptive as possible. Do not do housekeeping tasks, do not change the "
-"name of modules or files, do not move directories; in general, do not fix "
-"things which are not broken. Keep the patch as small as possible. If "
-"things bother you aesthetically, talk to the Debian maintainer, talk to the "
-"upstream maintainer, or submit a bug. However, aesthetic changes must "
-"<emphasis>not</emphasis> be made in a non-maintainer upload."
-msgstr ""
-
-# type: Content of: <chapter><section><para>
-#: pkgs.dbk:1858
-msgid ""
-"And please remember the Hippocratic Oath: Above all, do no harm. It is "
-"better to leave a package with an open grave bug than applying a non-"
-"functional patch, or one that hides the bug instead of resolving it."
+"Every package has one or more maintainers. Normally, these are the people "
+"who work on and upload new versions of the package. In some situations, it "
+"is useful that other developers can upload a new version as well, for "
+"example if they want to fix a bug in a package they don't maintain, when the "
+"maintainer needs help to respond to issues. Such uploads are called "
+"<emphasis>Non-Maintainer Uploads (NMU)</emphasis>."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1863
-msgid "How to do a NMU"
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1865
-msgid ""
-"NMUs which fix important, serious or higher severity bugs are encouraged and "
-"accepted. You should endeavor to reach the current maintainer of the "
-"package; they might be just about to upload a fix for the problem, or have a "
-"better solution."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1871
-msgid ""
-"NMUs should be made to assist a package's maintainer in resolving bugs. "
-"Maintainers should be thankful for that help, and NMUers should respect the "
-"decisions of maintainers, and try to personally help the maintainer by their "
-"work."
+#: pkgs.dbk:1857
+msgid "When and how to do an NMU"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1877
-msgid ""
-"A NMU should follow all conventions, written down in this section. For an "
-"upload to <literal>testing</literal> or <literal>unstable</literal>, this "
-"order of steps is recommended:"
+#: pkgs.dbk:1860
+msgid "Before doing an NMU, consider the following questions:"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1884
+#: pkgs.dbk:1865
msgid ""
-"Make sure that the package's bugs that the NMU is meant to address are all "
-"filed in the Debian Bug Tracking System (BTS). If they are not, submit them "
-"immediately."
+"Does your NMU really fix bugs? Fixing cosmetic issues or changing the "
+"packaging style in NMUs is discouraged."
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1891
+#: pkgs.dbk:1871
msgid ""
-"Wait a few days for the response from the maintainer. If you don't get any "
-"response, you may want to help them by sending the patch that fixes the "
-"bug. Don't forget to tag the bug with the patch keyword."
+"Did you give enough time to the maintainer? When was the bug reported to the "
+"BTS? Being busy for a week or two isn't unusual. Is the bug so severe that "
+"it needs to be fixed right now, or can it wait a few more days?"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1898
+#: pkgs.dbk:1878
msgid ""
-"Wait a few more days. If you still haven't got an answer from the "
-"maintainer, send them a mail announcing your intent to NMU the package. "
-"Prepare an NMU as described in this section, and test it carefully on your "
-"machine (cf. <xref linkend=\"sanitycheck\"/> ). Double check that your "
-"patch doesn't have any unexpected side effects. Make sure your patch is as "
-"small and as non-disruptive as it can be."
+"How confident are you about your changes? Please remember the Hippocratic "
+"Oath: \"Above all, do no harm.\" It is better to leave a package with an "
+"open grave bug than applying a non-functional patch, or one that hides the "
+"bug instead of resolving it. If you are not 100% sure of what you did, it "
+"might be a good idea to seek advice from others. Remember that if you break "
+"something in your NMU, many people will be very unhappy about it."
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1908
+#: pkgs.dbk:1888
msgid ""
-"Upload your package to incoming in <filename>DELAYED/7-day</filename> (cf. "
-"<xref linkend=\"delayed-incoming\"/> ), send the final patch to the "
-"maintainer via the BTS, and explain to them that they have 7 days to react "
-"if they want to cancel the NMU."
+"Have you clearly expressed your intention to NMU, at least in the BTS? It is "
+"also a good idea to try to contact the maintainer by other means (private "
+"email, IRC)."
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1916
+#: pkgs.dbk:1895
msgid ""
-"Follow what happens, you're responsible for any bug that you introduced with "
-"your NMU. You should probably use <xref linkend=\"pkg-tracking-system\"/> "
-"(PTS) to stay informed of the state of the package after your NMU."
+"If the maintainer is usually active and responsive, have you tried to "
+"contact him? In general it should be considered preferable that a maintainer "
+"takes care of an issue himself and that he is given the chance to review and "
+"correct your patch, because he can be expected to be more aware of potential "
+"issues which an NMUer might miss. It is often a better use of everyone's "
+"time if the maintainer is given an opportunity to upload a fix on their own."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1923
+#: pkgs.dbk:1905
msgid ""
-"At times, the release manager or an organized group of developers can "
-"announce a certain period of time in which the NMU rules are relaxed. This "
-"usually involves shortening the period during which one is to wait before "
-"uploading the fixes, and shortening the DELAYED period. It is important to "
-"notice that even in these so-called bug squashing party times, the NMU'er "
-"has to file bugs and contact the developer first, and act later. Please see "
-"<xref linkend=\"qa-bsp\"/> for details."
+"When doing an NMU, you must first make sure that your intention to NMU is "
+"clear. Then, you must send a patch with the differences between the current "
+"package and your proposed NMU to the BTS. The <literal>nmudiff</literal> "
+"script in the <literal>devscripts</literal> package might be helpful."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1932
+#: pkgs.dbk:1912
msgid ""
-"For the <literal>testing</literal> distribution, the rules may be changed by "
-"the release managers. Please take additional care, and acknowledge that the "
-"usual way for a package to enter <literal>testing</literal> is through "
-"<literal>unstable</literal>."
+"While preparing the patch, you should better be aware of any package-"
+"specific practices that the maintainer might be using. Taking them into "
+"account reduces the burden of getting your changes integrated back in the "
+"normal package workflow and thus increases the possibilities that that will "
+"happen. A good place where to look for for possible package-specific "
+"practices is <ulink url=\"&url-debian-policy;ch-source.html#s-readmesource"
+"\"><literal>debian/README.source</literal></ulink>."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1938
+#: pkgs.dbk:1920
msgid ""
-"For the stable distribution, please take extra care. Of course, the release "
-"managers may also change the rules here. Please verify before you upload "
-"that all your changes are OK for inclusion into the next stable release by "
-"the release manager."
+"Unless you have an excellent reason not to do so, you must then give some "
+"time to the maintainer to react (for example, by uploading to the "
+"<literal>DELAYED</literal> queue). Here are some recommended values to use "
+"for delays:"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1944
-msgid ""
-"When a security bug is detected, the security team may do an NMU, using "
-"their own rules. Please refer to <xref linkend=\"bug-security\"/> for more "
-"information."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1949
-msgid ""
-"For the differences for Porters NMUs, please see <xref linkend=\"source-nmu-"
-"when-porter\"/> ."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1953
-msgid ""
-"Of course, it is always possible to agree on special rules with a maintainer "
-"(like the maintainer asking please upload this fix directly for me, and no "
-"diff required)."
+# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1927
+msgid "Upload fixing only release-critical bugs older than 7 days: 2 days"
msgstr ""
-# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1960
-msgid "NMU version numbering"
+# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1932
+msgid "Upload fixing only release-critical and important bugs: 5 days"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1962
-msgid ""
-"Whenever you have made a change to a package, no matter how trivial, the "
-"version number needs to change. This enables our packing system to function."
+# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1937
+msgid "Other NMUs: 10 days"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1966
+#: pkgs.dbk:1943
msgid ""
-"If you are doing a non-maintainer upload (NMU), you should add a new minor "
-"version number to the <replaceable>debian-revision</replaceable> part of the "
-"version number (the portion after the last hyphen). This extra minor number "
-"will start at `1'. For example, consider the package `foo', which is at "
-"version 1.1-3. In the archive, the source package control file would be "
-"<filename>foo_1.1-3.dsc</filename>. The upstream version is `1.1' and the "
-"Debian revision is `3'. The next NMU would add a new minor number `.1' to "
-"the Debian revision; the new source control file would be <filename>foo_1.1-"
-"3.1.dsc</filename>."
+"Those delays are only examples. In some cases, such as uploads fixing "
+"security issues, or fixes for trivial bugs that blocking a transition, it is "
+"desirable that the fixed package reaches <literal>unstable</literal> sooner."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1977
+#: pkgs.dbk:1949
msgid ""
-"The Debian revision minor number is needed to avoid stealing one of the "
-"package maintainer's version numbers, which might disrupt their work. It "
-"also has the benefit of making it visually clear that a package in the "
-"archive was not made by the official maintainer."
+"Sometimes, release managers decide to allow NMUs with shorter delays for a "
+"subset of bugs (e.g release-critical bugs older than 7 days). Also, some "
+"maintainers list themselves in the <ulink url=\"&url-low-threshold-nmu;"
+"\">Low Threshold NMU list</ulink>, and accept that NMUs are uploaded without "
+"delay. But even in those cases, it's still a good idea to give the "
+"maintainer a few days to react before you upload, especially if the patch "
+"wasn't available in the BTS before, or if you know that the maintainer is "
+"generally active."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1983
+#: pkgs.dbk:1959
msgid ""
-"If there is no <replaceable>debian-revision</replaceable> component in the "
-"version number then one should be created, starting at `0.1' (but in case of "
-"a debian native package still upload it as native package). If it is "
-"absolutely necessary for someone other than the usual maintainer to make a "
-"release based on a new upstream version then the person making the release "
-"should start with the <replaceable>debian-revision</replaceable> value "
-"`0.1'. The usual maintainer of a package should start their "
-"<replaceable>debian-revision</replaceable> numbering at `1'."
+"After you upload an NMU, you are responsible for the possible problems that "
+"you might have introduced. You must keep an eye on the package (subscribing "
+"to the package on the PTS is a good way to achieve this)."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1993
+#: pkgs.dbk:1965
msgid ""
-"If you upload a package to <literal>testing</literal> or <literal>stable </"
-"literal>, sometimes, you need to fork the version number tree. For this, "
-"version numbers like 1.1-3sarge0.1 could be used."
+"This is not a license to perform NMUs thoughtlessly. If you NMU when it is "
+"clear that the maintainers are active and would have acknowledged a patch in "
+"a timely manner, or if you ignore the recommendations of this document, your "
+"upload might be a cause of conflict with the maintainer. You should always "
+"be prepared to defend the wisdom of any NMU you perform on its own merits."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2000
-msgid "Source NMUs must have a new changelog entry"
+#: pkgs.dbk:1975
+msgid "NMUs and debian/changelog"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2002
+#: pkgs.dbk:1977
msgid ""
-"Anyone who is doing a source NMU must create a changelog entry, describing "
-"which bugs are fixed by the NMU, and generally why the NMU was required and "
-"what it fixed. The changelog entry will have the email address of the "
-"person who uploaded it in the log entry and the NMU version number in it."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2008
-msgid "By convention, source NMU changelog entries start with the line"
+"Just like any other (source) upload, NMUs must add an entry to "
+"<literal>debian/changelog</literal>, telling what has changed with this "
+"upload. The first line of this entry must explicitely mention that this "
+"upload is an NMU, e.g.:"
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:2010
+#: pkgs.dbk:1981
#, no-wrap
msgid ""
"\n"
-" * Non-maintainer upload\n"
+" * Non-maintainer upload.\n"
msgstr ""
-# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2016
-msgid "Source NMUs and the Bug Tracking System"
+# type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1986
+msgid ""
+"The version must be the version of the last maintainer upload, plus <literal>"
+"+nmu<replaceable>X</replaceable></literal>, where <replaceable>X</"
+"replaceable> is a counter starting at <literal>1</literal>. If the last "
+"upload was also an NMU, the counter should be increased. For example, if "
+"the current version is <literal>1.5-1</literal>, then an NMU would get "
+"version <literal>1.5-1+nmu1</literal>. If the current version is "
+"<literal>1.5+nmu3</literal> (a native package which has already been NMUed), "
+"the NMU would get version <literal>1.5+nmu4</literal>. If a new upstream "
+"version is packaged in the NMU, the debian revision is set to <literal>0</"
+"literal>, for example <literal>1.6-0+nmu1</literal>."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2018
+#: pkgs.dbk:1999
msgid ""
-"Maintainers other than the official package maintainer should make as few "
-"changes to the package as possible, and they should always send a patch as a "
-"unified context diff (<literal>diff -u</literal>) detailing their changes to "
-"the Bug Tracking System."
+"A special versioning scheme is needed to avoid disrupting the maintainer's "
+"work, since using an integer for the Debian revision will potentially "
+"conflict with a maintainer upload already in preparation at the time of an "
+"NMU, or even one sitting in the ftp NEW queue. It also has the benefit of "
+"making it visually clear that a package in the archive was not made by the "
+"official maintainer."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2024
+#: pkgs.dbk:2009
msgid ""
-"What if you are simply recompiling the package? If you just need to "
-"recompile it for a single architecture, then you may do a binary-only NMU as "
-"described in <xref linkend=\"binary-only-nmu\"/> which doesn't require any "
-"patch to be sent. If you want the package to be recompiled for all "
-"architectures, then you do a source NMU as usual and you will have to send a "
-"patch."
+"If you upload a package to testing or stable, you sometimes need to \"fork\" "
+"the version number tree. This is the case for security uploads, for "
+"example. For this, a version of the form <literal>+deb<replaceable>XY</"
+"replaceable>u<replaceable>Z</replaceable></literal> should be used, where "
+"<replaceable>X</replaceable> and <replaceable>Y</replaceable> are the major "
+"and minor release numbers, and <replaceable>Z</replaceable> is a counter "
+"starting at <literal>1</literal>. When the release number is not yet known "
+"(often the case for <literal>testing</literal>, at the beginning of release "
+"cycles), the lowest release number higher than the last stable release "
+"number must be used. For example, while Etch (Debian 4.0) is stable, a "
+"security NMU to stable for a package at version <literal>1.5-3</literal> "
+"would have version <literal>1.5-3+deb40u1</literal>, whereas a security NMU "
+"to Lenny would get version <literal>1.5-3+deb50u1</literal>. After the "
+"release of Lenny, security uploads to the <literal>testing</literal> "
+"distribution will be versioned <literal>+deb51uZ</literal>, until it is "
+"known whether that release will be Debian 5.1 or Debian 6.0 (if that becomes "
+"the case, uploads will be versioned as <literal>+deb60uZ</literal>."
msgstr ""
-# type: Content of: <chapter><section><section><para>
+# type: Content of: <chapter><section><section><title>
#: pkgs.dbk:2031
+msgid "Using the <literal>DELAYED/</literal> queue"
+msgstr ""
+
+# type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2034
msgid ""
-"Bugs fixed by source NMUs used to be tagged fixed instead of closed, but "
-"since version tracking is in place, such bugs are now also closed with the "
-"NMU version."
+"Having to wait for a response after you request permission to NMU is "
+"inefficient, because it costs the NMUer a context switch to come back to the "
+"issue. The <literal>DELAYED</literal> queue (see <xref linkend=\"delayed-"
+"incoming\"/>) allows the developer doing the NMU to perform all the "
+"necessary tasks at the same time. For instance, instead of telling the "
+"maintainer that you will upload the updated package in 7 days, you should "
+"upload the package to <literal>DELAYED/7</literal> and tell the maintainer "
+"that he has 7 days to react. During this time, the maintainer can ask you "
+"to delay the upload some more, or cancel your upload."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2036
+#: pkgs.dbk:2048
msgid ""
-"Also, after doing an NMU, you have to send the information to the existing "
-"bugs that are fixed by your NMU, including the unified diff. Historically, "
-"it was custom to open a new bug and include a patch showing all the changes "
-"you have made. The normal maintainer will either apply the patch or employ "
-"an alternate method of fixing the problem. Sometimes bugs are fixed "
-"independently upstream, which is another good reason to back out an NMU's "
-"patch. If the maintainer decides not to apply the NMU's patch but to "
-"release a new version, the maintainer needs to ensure that the new upstream "
-"version really fixes each problem that was fixed in the non-maintainer "
-"release."
+"The <literal>DELAYED</literal> queue should not be used to put additional "
+"pressure on the maintainer. In particular, it's important that you are "
+"available to cancel or delay the upload before the delay expires since the "
+"maintainer cannot cancel the upload himself."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2047
+#: pkgs.dbk:2055
msgid ""
-"In addition, the normal maintainer should <emphasis>always</emphasis> retain "
-"the entry in the changelog file documenting the non-maintainer upload -- and "
-"of course, also keep the changes. If you revert some of the changes, please "
-"reopen the relevant bug reports."
+"If you make an NMU to <literal>DELAYED</literal> and the maintainer updates "
+"his package before the delay expires, your upload will be rejected because a "
+"newer version is already available in the archive. Ideally, the maintainer "
+"will take care to include your proposed changes (or at least a solution for "
+"the problems they address) in that upload."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2055
-msgid "Building source NMUs"
+#: pkgs.dbk:2065
+msgid "NMUs from the maintainer's point of view"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2057
+#: pkgs.dbk:2068
msgid ""
-"Source NMU packages are built normally. Pick a distribution using the same "
-"rules as found in <xref linkend=\"distribution\"/> , follow the other "
-"instructions in <xref linkend=\"upload\"/> ."
+"When someone NMUs your package, this means they want to help you to keep it "
+"in good shape. This gives users fixed packages faster. You can consider "
+"asking the NMUer to become a co-maintainer of the package. Receiving an NMU "
+"on a package is not a bad thing; it just means that the package is "
+"interesting enough for other people to work on it."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2062
+#: pkgs.dbk:2077
msgid ""
-"Make sure you do <emphasis>not</emphasis> change the value of the maintainer "
-"in the <filename>debian/control</filename> file. Your name as given in the "
-"NMU entry of the <filename>debian/changelog</filename> file will be used for "
-"signing the changes file."
+"To acknowledge an NMU, include its changes and changelog entry in your next "
+"maintainer upload. If you do not acknowledge the NMU by including the NMU "
+"changelog entry in your changelog, the bugs will remain closed in the BTS "
+"but will be listed as affecting your maintainer version of the package."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2070
-msgid "Acknowledging an NMU"
+#: pkgs.dbk:2086
+msgid "Source NMUs vs Binary-only NMUs (binNMUs)"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2072
+#: pkgs.dbk:2089
msgid ""
-"If one of your packages has been NMU'ed, you have to incorporate the changes "
-"in your copy of the sources. This is easy, you just have to apply the patch "
-"that has been sent to you. Once this is done, you have to close the bugs "
-"that have been tagged fixed by the NMU. The easiest way is to use the "
-"<literal>-v</literal> option of <command>dpkg-buildpackage</command>, as "
-"this allows you to include just all changes since your last maintainer "
-"upload. Alternatively, you can close them manually by sending the required "
-"mails to the BTS or by adding the required <literal>closes: #nnnn</literal> "
-"in the changelog entry of your next upload."
+"The full name of an NMU is <emphasis>source NMU</emphasis>. There is also "
+"another type, namely the <emphasis>binary-only NMU</emphasis>, or "
+"<emphasis>binNMU</emphasis>. A binNMU is also a package upload by someone "
+"other than the package's maintainer. However, it is a binary-only upload."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2083
+#: pkgs.dbk:2096
msgid ""
-"In any case, you should not be upset by the NMU. An NMU is not a personal "
-"attack against the maintainer. It is a proof that someone cares enough "
-"about the package that they were willing to help you in your work, so you "
-"should be thankful. You may also want to ask them if they would be "
-"interested in helping you on a more frequent basis as co-maintainer or "
-"backup maintainer (see <xref linkend=\"collaborative-maint\"/> )."
+"When a library (or other dependency) is updated, the packages using it may "
+"need to be rebuilt. Since no changes to the source are needed, the same "
+"source package is used."
msgstr ""
-# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2093
-msgid "NMU vs QA uploads"
+# type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2102
+msgid ""
+"BinNMUs are usually triggered on the buildds by wanna-build. An entry is "
+"added to debian/changelog, explaining why the upload was needed and "
+"increasing the version number as described in <xref linkend=\"binary-only-nmu"
+"\"/>. This entry should not be included in the next upload."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2095
+#: pkgs.dbk:2110
msgid ""
-"Unless you know the maintainer is still active, it is wise to check the "
-"package to see if it has been orphaned. The current list of orphaned "
-"packages which haven't had their maintainer set correctly is available at "
-"<ulink url=\"&url-debian-qa-orphaned;\"></ulink>. If you perform an NMU on "
-"an improperly orphaned package, please set the maintainer to <literal>Debian "
-"QA Group <packages@qa.debian.org></literal>."
+"Buildds upload packages for their architecture to the archive as binary-only "
+"uploads. Strictly speaking, these are binNMUs. However, they are not "
+"normally called NMU, and they don't add an entry to debian/changelog."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2105
-msgid "Who can do an NMU"
+#: pkgs.dbk:2118
+msgid "NMUs vs QA uploads"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2107
+#: pkgs.dbk:2121
msgid ""
-"Only official, registered Debian Developers can do binary or source NMUs. A "
-"Debian Developer is someone who has their key in the Debian key ring. Non-"
-"developers, however, are encouraged to download the source package and start "
-"hacking on it to fix problems; however, rather than doing an NMU, they "
-"should just submit worthwhile patches to the Bug Tracking System. "
-"Maintainers almost always appreciate quality patches and bug reports."
-msgstr ""
-
-# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2117
-msgid "Terminology"
+"NMUs are uploads of packages by somebody else than their assigned "
+"maintainer. There is another type of upload where the uploaded package is "
+"not yours: QA uploads. QA uploads are uploads of orphaned packages."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2119
+#: pkgs.dbk:2128
msgid ""
-"There are two new terms used throughout this section: ``binary-only NMU'' "
-"and ``source NMU''. These terms are used with specific technical meaning "
-"throughout this document. Both binary-only and source NMUs are similar, "
-"since they involve an upload of a package by a developer who is not the "
-"official maintainer of that package. That is why it's a <literal>non-"
-"maintainer</literal> upload."
+"QA uploads are very much like normal maintainer uploads: they may fix "
+"anything, even minor issues; the version numbering is normal, and there is "
+"no need to use a delayed upload. The difference is that you are not listed "
+"as the Maintainer or Uploader for the package. Also, the changelog entry of "
+"a QA upload has a special first line:"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2127
+# type: Content of: <chapter><section><section><screen>
+#: pkgs.dbk:2135
+#, no-wrap
msgid ""
-"A source NMU is an upload of a package by a developer who is not the "
-"official maintainer, for the purposes of fixing a bug in the package. "
-"Source NMUs always involves changes to the source (even if it is just a "
-"change to <filename>debian/changelog</filename>). This can be either a "
-"change to the upstream source, or a change to the Debian bits of the "
-"source. Note, however, that source NMUs may also include architecture-"
-"dependent packages, as well as an updated Debian diff."
+"\n"
+" * QA upload.\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2136
+#: pkgs.dbk:2140
msgid ""
-"A binary-only NMU is a recompilation and upload of a binary package for a "
-"given architecture. As such, it is usually part of a porting effort. A "
-"binary-only NMU is a non-maintainer uploaded binary version of a package, "
-"with no source changes required. There are many cases where porters must "
-"fix problems in the source in order to get them to compile for their target "
-"architecture; that would be considered a source NMU rather than a binary-"
-"only NMU. As you can see, we don't distinguish in terminology between "
-"porter NMUs and non-porter NMUs."
+"If you want to do an NMU, and it seems that the maintainer is not active, it "
+"is wise to check if the package is orphaned (this information is displayed "
+"on the package's Package Tracking System page). When doing the first QA "
+"upload to an orphaned package, the maintainer should be set to "
+"<literal>Debian QA Group <packages@qa.debian.org></literal>. Orphaned "
+"packages which did not yet have a QA upload still have their old maintainer "
+"set. There is a list of them at <ulink url=\"&url-orphaned-not-qa;\"/>."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2146
+#: pkgs.dbk:2151
msgid ""
-"Both classes of NMUs, source and binary-only, can be lumped under the term "
-"``NMU''. However, this often leads to confusion, since most people think "
-"``source NMU'' when they think ``NMU''. So it's best to be careful: always "
-"use ``binary NMU'' or ``binNMU'' for binary-only NMUs."
+"Instead of doing a QA upload, you can also consider adopting the package by "
+"making yourself the maintainer. You don't need permission from anybody to "
+"adopt an orphaned package, you can just set yourself as maintainer and "
+"upload the new version (see <xref linkend=\"adopting\"/>)."
msgstr ""
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:2156
+#: pkgs.dbk:2162
msgid "Collaborative maintenance"
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:2158
+#: pkgs.dbk:2164
msgid ""
"Collaborative maintenance is a term describing the sharing of Debian package "
"maintenance duties by several people. This collaboration is almost always a "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:2166
+#: pkgs.dbk:2172
msgid ""
"Generally there is a primary maintainer and one or more co-maintainers. The "
"primary maintainer is the person whose name is listed in the "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:2174
+#: pkgs.dbk:2180
msgid ""
"In its most basic form, the process of adding a new co-maintainer is quite "
"easy:"
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2180
+#: pkgs.dbk:2186
msgid ""
"Setup the co-maintainer with access to the sources you build the package "
"from. Generally this implies you are using a network-capable version "
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2188
+#: pkgs.dbk:2194
msgid ""
"Add the co-maintainer's correct maintainer name and address to the "
"<literal>Uploaders</literal> field in the first paragraph of the "
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><screen>
-#: pkgs.dbk:2192
+#: pkgs.dbk:2198
#, no-wrap
msgid ""
"\n"
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2198
+#: pkgs.dbk:2204
msgid ""
"Using the PTS (<xref linkend=\"pkg-tracking-system\"/> ), the co-maintainers "
"should subscribe themselves to the appropriate source package."
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:2204
+#: pkgs.dbk:2210
msgid ""
"Another form of collaborative maintenance is team maintenance, which is "
"recommended if you maintain several packages with the same group of "
msgstr ""
# type: Content of: <chapter><section><orderedlist><listitem><para>
-#: pkgs.dbk:2213
+#: pkgs.dbk:2219
msgid ""
"Put the team member mainly responsible for the package in the Maintainer "
"field. In the Uploaders, put the mailing list address, and the team members "
msgstr ""
# type: Content of: <chapter><section><orderedlist><listitem><para>
-#: pkgs.dbk:2220
+#: pkgs.dbk:2226
msgid ""
"Put the mailing list address in the Maintainer field. In the Uploaders "
"field, put the team members who care for the package. In this case, you "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:2228
+#: pkgs.dbk:2234
msgid ""
"In any case, it is a bad idea to automatically put all team members in the "
"Uploaders field. It clutters the Developer's Package Overview listing (see "
msgstr ""
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:2236
+#: pkgs.dbk:2242
msgid "The testing distribution"
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2238
+#: pkgs.dbk:2244
msgid "Basics"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2240
+#: pkgs.dbk:2246
msgid ""
"Packages are usually installed into the <literal>testing</literal> "
"distribution after they have undergone some degree of <literal>testing</"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2245
+#: pkgs.dbk:2251
msgid ""
"They must be in sync on all architectures and mustn't have dependencies that "
"make them uninstallable; they also have to have generally no known release-"
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2254
+#: pkgs.dbk:2260
msgid "Updates from unstable"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2256
+#: pkgs.dbk:2262
msgid ""
"The scripts that update the <literal>testing</literal> distribution are run "
"twice each day, right after the installation of the updated packages; these "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2264
+#: pkgs.dbk:2270
msgid ""
"The inclusion of a package from <literal>unstable</literal> is conditional "
"on the following:"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2270
+#: pkgs.dbk:2276
msgid ""
"The package must have been available in <literal>unstable</literal> for 2, 5 "
"or 10 days, depending on the urgency (high, medium or low). Please note "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2280
+#: pkgs.dbk:2286
msgid ""
"It must not have new release-critical bugs (RC bugs affecting the version "
"available in <literal>unstable</literal>, but not affecting the version in "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2287
+#: pkgs.dbk:2293
msgid ""
"It must be available on all architectures on which it has previously been "
"built in <literal>unstable</literal>. <xref linkend=\"dak-ls\"/> may be of "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2294
+#: pkgs.dbk:2300
msgid ""
"It must not break any dependency of a package which is already available in "
"<literal>testing</literal>;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2300
+#: pkgs.dbk:2306
msgid ""
"The packages on which it depends must either be available in "
"<literal>testing</literal> or they must be accepted into <literal>testing</"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2308
+#: pkgs.dbk:2314
msgid ""
"To find out whether a package is progressing into <literal>testing</literal> "
"or not, see the <literal>testing</literal> script output on the <ulink url="
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2319
+#: pkgs.dbk:2325
msgid ""
"The <filename>update_excuses</filename> file does not always give the "
"precise reason why the package is refused; you may have to find it on your "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2326
+#: pkgs.dbk:2332
msgid ""
"Sometimes, some packages never enter <literal>testing</literal> because the "
"set of inter-relationship is too complicated and cannot be sorted out by the "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2331
+#: pkgs.dbk:2337
msgid ""
"Some further dependency analysis is shown on <ulink url=\"http://release."
"debian.org/migration/\"></ulink> — but be warned, this page also shows build "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2336
+#: pkgs.dbk:2342
msgid "out-of-date"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
#. FIXME: better rename this file than document rampant professionalism?
-#: pkgs.dbk:2339
+#: pkgs.dbk:2345
msgid ""
"For the <literal>testing</literal> migration script, outdated means: There "
"are different versions in <literal>unstable</literal> for the release "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2347
+#: pkgs.dbk:2353
msgid "Consider this example:"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2354 pkgs.dbk:2387
+#: pkgs.dbk:2360 pkgs.dbk:2393
msgid "alpha"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2355 pkgs.dbk:2388
+#: pkgs.dbk:2361 pkgs.dbk:2394
msgid "arm"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2360 pkgs.dbk:2394 pkgs.dbk:2456
+#: pkgs.dbk:2366 pkgs.dbk:2400 pkgs.dbk:2462
msgid "testing"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2361 pkgs.dbk:2366 pkgs.dbk:2395 pkgs.dbk:2396 pkgs.dbk:2403
+#: pkgs.dbk:2367 pkgs.dbk:2372 pkgs.dbk:2401 pkgs.dbk:2402 pkgs.dbk:2409
msgid "1"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2362 pkgs.dbk:2397 pkgs.dbk:2402
+#: pkgs.dbk:2368 pkgs.dbk:2403 pkgs.dbk:2408
msgid "-"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2365 pkgs.dbk:2400 pkgs.dbk:2457
+#: pkgs.dbk:2371 pkgs.dbk:2406 pkgs.dbk:2463
msgid "unstable"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2367 pkgs.dbk:2401
+#: pkgs.dbk:2373 pkgs.dbk:2407
msgid "2"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2373
+#: pkgs.dbk:2379
msgid ""
"The package is out of date on alpha in <literal>unstable</literal>, and will "
"not go to <literal>testing</literal>. Removing the package would not help at "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2379
+#: pkgs.dbk:2385
msgid ""
"However, if ftp-master removes a package in <literal>unstable</literal> "
"(here on <literal>arm</literal>):"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2389
+#: pkgs.dbk:2395
msgid "hurd-i386"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2409
+#: pkgs.dbk:2415
msgid ""
"In this case, the package is up to date on all release architectures in "
"<literal>unstable</literal> (and the extra <literal>hurd-i386</literal> "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2414
+#: pkgs.dbk:2420
msgid ""
"Sometimes, the question is raised if it is possible to allow packages in "
"that are not yet built on all architectures: No. Just plainly no. (Except "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2421
+#: pkgs.dbk:2427
msgid "Removals from testing"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2423
+#: pkgs.dbk:2429
msgid ""
"Sometimes, a package is removed to allow another package in: This happens "
"only to allow <emphasis>another</emphasis> package to go in if it's ready in "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2430
+#: pkgs.dbk:2436
msgid ""
"Of course, there is another reason to remove a package from <literal>testing "
"</literal>: It's just too buggy (and having a single RC-bug is enough to be "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2435
+#: pkgs.dbk:2441
msgid ""
"Furthermore, if a package has been removed from <literal>unstable</literal>, "
"and no package in <literal>testing</literal> depends on it any more, then it "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2442
+#: pkgs.dbk:2448
msgid "circular dependencies"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2444
+#: pkgs.dbk:2450
msgid ""
"A situation which is not handled very well by britney is if package "
"<literal>a</literal> depends on the new version of package <literal>b</"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2449
+#: pkgs.dbk:2455
msgid "An example of this is:"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2462
+#: pkgs.dbk:2468
msgid "a"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2463
+#: pkgs.dbk:2469
msgid "1; depends: b=1"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2464
+#: pkgs.dbk:2470
msgid "2; depends: b=2"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2467
+#: pkgs.dbk:2473
msgid "b"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2468
+#: pkgs.dbk:2474
msgid "1; depends: a=1"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2469
+#: pkgs.dbk:2475
msgid "2; depends: a=2"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2475
+#: pkgs.dbk:2481
msgid ""
"Neither package <literal>a</literal> nor package <literal>b</literal> is "
"considered for update."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2479
+#: pkgs.dbk:2485
msgid ""
"Currently, this requires some manual hinting from the release team. Please "
"contact them by sending mail to &email-debian-release; if this happens to "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2486
+#: pkgs.dbk:2492
msgid "influence of package in testing"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2488
+#: pkgs.dbk:2494
msgid ""
"Generally, there is nothing that the status of a package in <literal>testing "
"</literal> means for transition of the next version from <literal>unstable </"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2500
+#: pkgs.dbk:2506
msgid ""
"In summary this means: The only influence that a package being in <literal> "
"testing</literal> has on a new version of the same package is that the new "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2507
+#: pkgs.dbk:2513
msgid "details"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2509
+#: pkgs.dbk:2515
msgid "If you are interested in details, this is how britney works:"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2512
+#: pkgs.dbk:2518
msgid ""
"The packages are looked at to determine whether they are valid candidates. "
"This gives the update excuses. The most common reasons why a package is not "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2521
+#: pkgs.dbk:2527
msgid ""
"Now, the more complex part happens: Britney tries to update <literal>testing "
"</literal> with the valid candidates. For that, britney tries to add each "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2531
+#: pkgs.dbk:2537
msgid ""
"If you want to see more details, you can look it up on <filename>merkel:/org/"
"&ftp-debian-org;/testing/update_out/</filename> (or in <filename>merkel:~aba/"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2538
+#: pkgs.dbk:2544
msgid ""
"The hints are available via <ulink url=\"http://&ftp-master-host;/testing/"
"hints/\"></ulink>."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2546
+#: pkgs.dbk:2552
msgid "Direct updates to testing"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2548
+#: pkgs.dbk:2554
msgid ""
"The <literal>testing</literal> distribution is fed with packages from "
"<literal>unstable</literal> according to the rules explained above. "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2555
+#: pkgs.dbk:2561
msgid ""
"Keep in mind that packages uploaded there are not automatically processed, "
"they have to go through the hands of the release manager. So you'd better "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2562
+#: pkgs.dbk:2568
msgid ""
"You should not upload to <literal>testing-proposed-updates</literal> when "
"you can update your packages through <literal>unstable</literal>. If you "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2571
+#: pkgs.dbk:2577
msgid ""
"Version numbers are usually selected by adding the codename of the "
"<literal>testing</literal> distribution and a running number, like "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2578
+#: pkgs.dbk:2584
msgid "Please make sure you didn't miss any of these items in your upload:"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2583
+#: pkgs.dbk:2589
msgid ""
"Make sure that your package really needs to go through <literal>testing-"
"proposed-updates</literal>, and can't go through <literal> unstable</"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2590
+#: pkgs.dbk:2596
msgid "Make sure that you included only the minimal amount of changes;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2595
+#: pkgs.dbk:2601
msgid ""
"Make sure that you included an appropriate explanation in the changelog;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2600
+#: pkgs.dbk:2606
msgid ""
"Make sure that you've written <literal>testing</literal> or <literal>testing-"
"proposed-updates</literal> into your target distribution;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2606
+#: pkgs.dbk:2612
msgid ""
"Make sure that you've built and tested your package in <literal>testing</"
"literal>, not in <literal>unstable</literal>;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2612
+#: pkgs.dbk:2618
msgid ""
"Make sure that your version number is higher than the version in "
"<literal>testing</literal> and <literal>testing-proposed-updates</literal>, "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2619
+#: pkgs.dbk:2625
msgid ""
"After uploading and successful build on all platforms, contact the release "
"team at &email-debian-release; and ask them to approve your upload."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2627
+#: pkgs.dbk:2633
msgid "Frequently asked questions"
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2629
+#: pkgs.dbk:2635
msgid "What are release-critical bugs, and how do they get counted?"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2631
+#: pkgs.dbk:2637
msgid ""
"All bugs of some higher severities are by default considered release-"
"critical; currently, these are <literal>critical</literal>, <literal>grave</"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2636
+#: pkgs.dbk:2642
msgid ""
"Such bugs are presumed to have an impact on the chances that the package "
"will be released with the <literal>stable</literal> release of Debian: in "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2643
+#: pkgs.dbk:2649
msgid ""
"The <literal>unstable</literal> bug count are all release-critical bugs "
"which are marked to apply to <replaceable>package</replaceable>/"
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2651
+#: pkgs.dbk:2657
msgid ""
"How could installing a package into <literal>testing</literal> possibly "
"break other packages?"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2654
+#: pkgs.dbk:2660
msgid ""
"The structure of the distribution archives is such that they can only "
"contain one version of a package; a package is defined by its name. So when "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2662
+#: pkgs.dbk:2668
msgid ""
"However, the old version may have provided a binary package with an old "
"soname of a library, such as <literal>libacme-foo0</literal>. Removing the "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2668
+#: pkgs.dbk:2674
msgid ""
"Evidently, this mainly affects packages which provide changing sets of "
"binary packages in different versions (in turn, mainly libraries). However, "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2674
+#: pkgs.dbk:2680
msgid ""
"When the set of binary packages provided by a source package change in this "
"way, all the packages that depended on the old binaries will have to be "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2685
+#: pkgs.dbk:2691
msgid ""
"If you are having problems with complicated groups of packages like this, "
"contact &email-debian-devel; or &email-debian-release; for help."
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2008-08-08 11:37-0300\n"
+"POT-Creation-Date: 2009-01-22 23:51+0100\n"
"PO-Revision-Date: 2007-07-01 23:19+0000\n"
"Last-Translator: <>\n"
"Language-Team: \n"
msgstr ""
# type: Content of: <appendix><section><section><title>
-#: tools.dbk:503
+#: tools.dbk:504
+msgid "<systemitem role=\"package\">docbook-xml</systemitem>"
+msgstr ""
+
+# type: Content of: <appendix><section><section><para>
+#: tools.dbk:506
+msgid ""
+"<systemitem role=\"package\">docbook-xml</systemitem> provides the DocBook "
+"XML DTDs, which are commonly used for Debian documentation (as is the older "
+"debiandoc SGML DTD). This manual, for instance, is written in DocBook XML."
+msgstr ""
+
+# type: Content of: <appendix><section><section><para>
+#: tools.dbk:512
+msgid ""
+"The <systemitem role=\"package\">docbook-xsl</systemitem> package provides "
+"the XSL files for building and styling the source to various output formats. "
+"You will need an XSLT processor, such as <systemitem role=\"package"
+"\">xsltproc</systemitem>, to use the XSL stylesheets. Documentation for the "
+"stylesheets can be found in the various <systemitem role=\"package\">docbook-"
+"xsl-doc-*</systemitem> packages."
+msgstr ""
+
+# type: Content of: <appendix><section><section><para>
+#: tools.dbk:520
+msgid ""
+"To produce PDF from FO, you need an FO processor, such as <systemitem role="
+"\"package\">xmlroff</systemitem> or <systemitem role=\"package\">fop</"
+"systemitem>. Another tool to generate PDF from DocBook XML is <systemitem "
+"role=\"package\">dblatex</systemitem>."
+msgstr ""
+
+# type: Content of: <appendix><section><section><title>
+#: tools.dbk:528
msgid "<systemitem role=\"package\">debiandoc-sgml</systemitem>"
msgstr ""
# type: Content of: <appendix><section><section><para>
-#: tools.dbk:505
+#: tools.dbk:530
msgid ""
"<systemitem role=\"package\">debiandoc-sgml</systemitem> provides the "
-"DebianDoc SGML DTD, which is commonly used for Debian documentation. This "
-"manual, for instance, is written in DebianDoc. It also provides scripts for "
-"building and styling the source to various output formats."
+"DebianDoc SGML DTD, which is commonly used for Debian documentation, but is "
+"now deprecated (<systemitem role=\"package\">docbook-xml</systemitem> should "
+"be used instead). It also provides scripts for building and styling the "
+"source to various output formats."
msgstr ""
# type: Content of: <appendix><section><section><para>
-#: tools.dbk:511
+#: tools.dbk:539
msgid ""
"Documentation for the DTD can be found in the <systemitem role=\"package"
"\">debiandoc-sgml-doc</systemitem> package."
msgstr ""
# type: Content of: <appendix><section><section><title>
-#: tools.dbk:533
+#: tools.dbk:545
msgid "<systemitem role=\"package\">debian-keyring</systemitem>"
msgstr ""
# type: Content of: <appendix><section><section><para>
-#: tools.dbk:535
+#: tools.dbk:547
msgid ""
"Contains the public GPG and PGP keys of Debian developers. See <xref "
"linkend=\"key-maint\"/> and the package documentation for more information."
msgstr ""
# type: Content of: <appendix><section><section><title>
-#: tools.dbk:541
+#: tools.dbk:553
msgid "<systemitem role=\"package\">debian-maintainers</systemitem>"
msgstr ""
# type: Content of: <appendix><section><section><para>
-#: tools.dbk:543
+#: tools.dbk:555
msgid ""
"Contains the public GPG keys of Debian Maintainers. See <ulink url=\"&url-"
"wiki-dm;\"></ulink> for more information."
msgstr ""
# type: Content of: <appendix><section><section><title>
-#: tools.dbk:549
+#: tools.dbk:561
msgid "<systemitem role=\"package\">debview</systemitem>"
msgstr ""
# type: Content of: <appendix><section><section><para>
-#: tools.dbk:551
+#: tools.dbk:563
msgid ""
"<systemitem role=\"package\">debview</systemitem> provides an Emacs mode for "
"viewing Debian binary packages. This lets you examine a package without "
~ianmdlvl / developers-reference.git / commitdiff