X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=po4a%2Fpo%2Fpkgs.pot;h=e050e811b7dec823c1644a351ddd2d61af51a3a7;hb=9e33e83b35807524005d98fcaa7ea19a85d8c8d8;hp=294841b145a6a0271f688e910ece7b86da9743ff;hpb=b15bd896f2fb4eebad30139a23104bee6b5eabd4;p=developers-reference.git diff --git a/po4a/po/pkgs.pot b/po4a/po/pkgs.pot index 294841b..e050e81 100644 --- a/po4a/po/pkgs.pot +++ b/po4a/po/pkgs.pot @@ -7,13 +7,14 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2010-06-20 09:23-0400\n" +"POT-Creation-Date: 2011-03-03 11:18-0400\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" +"Language: \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" #. type: Content of: #: pkgs.dbk:7 @@ -57,38 +58,35 @@ msgstr "" #. type: Content of: <chapter><section><para> #: pkgs.dbk:31 msgid "" -"You should set the subject of the bug to <literal>ITP: " -"<replaceable>foo</replaceable> -- <replaceable>short " -"description</replaceable></literal>, substituting the name of the new " -"package for <replaceable>foo</replaceable>. The severity of the bug report " -"must be set to <literal>wishlist</literal>. Please send a copy to " -"&email-debian-devel; by using the X-Debbugs-CC header (don't use CC:, " -"because that way the message's subject won't indicate the bug number). If " -"you are packaging so many new packages (>10) that notifying the mailing " -"list in separate messages is too disruptive, send a summary after filing the " -"bugs to the debian-devel list instead. This will inform the other " -"developers about upcoming packages and will allow a review of your " -"description and package name." +"You should set the subject of the bug to <literal>ITP: <replaceable>foo</" +"replaceable> -- <replaceable>short description</replaceable></literal>, " +"substituting the name of the new package for <replaceable>foo</" +"replaceable>. The severity of the bug report must be set to " +"<literal>wishlist</literal>. Please send a copy to &email-debian-devel; by " +"using the X-Debbugs-CC header (don't use CC:, because that way the message's " +"subject won't indicate the bug number). If you are packaging so many new " +"packages (>10) that notifying the mailing list in separate messages is too " +"disruptive, send a summary after filing the bugs to the debian-devel list " +"instead. This will inform the other developers about upcoming packages and " +"will allow a review of your description and package name." msgstr "" #. type: Content of: <chapter><section><para> #: pkgs.dbk:45 msgid "" -"Please include a <literal>Closes: " -"#<replaceable>nnnnn</replaceable></literal> entry in the changelog of the " -"new package in order for the bug report to be automatically closed once the " -"new package is installed in the archive (see <xref " -"linkend=\"upload-bugfix\"/>)." +"Please include a <literal>Closes: #<replaceable>nnnnn</replaceable></" +"literal> entry in the changelog of the new package in order for the bug " +"report to be automatically closed once the new package is installed in the " +"archive (see <xref linkend=\"upload-bugfix\"/>)." msgstr "" #. type: Content of: <chapter><section><para> #: pkgs.dbk:51 msgid "" "If you think your package needs some explanations for the administrators of " -"the NEW package queue, include them in your changelog, send to " -"&email-ftpmaster; a reply to the email you receive as a maintainer after " -"your upload, or reply to the rejection email in case you are already " -"re-uploading." +"the NEW package queue, include them in your changelog, send to &email-" +"ftpmaster; a reply to the email you receive as a maintainer after your " +"upload, or reply to the rejection email in case you are already re-uploading." msgstr "" #. type: Content of: <chapter><section><para> @@ -166,11 +164,10 @@ msgid "" "<filename>debian/changelog</filename>. These changes should provide a " "concise description of what was changed, why (if it's in doubt), and note if " "any bugs were closed. They also record when the package was completed. " -"This file will be installed in " -"<filename>/usr/share/doc/<replaceable>package</replaceable>/changelog.Debian.gz</filename>, " -"or " -"<filename>/usr/share/doc/<replaceable>package</replaceable>/changelog.gz</filename> " -"for native packages." +"This file will be installed in <filename>/usr/share/doc/" +"<replaceable>package</replaceable>/changelog.Debian.gz</filename>, or " +"<filename>/usr/share/doc/<replaceable>package</replaceable>/changelog.gz</" +"filename> for native packages." msgstr "" #. type: Content of: <chapter><section><para> @@ -178,18 +175,17 @@ msgstr "" msgid "" "The <filename>debian/changelog</filename> file conforms to a certain " "structure, with a number of different fields. One field of note, the " -"<literal>distribution</literal>, is described in <xref " -"linkend=\"distribution\"/>. More information about the structure of this " -"file can be found in the Debian Policy section titled " -"<filename>debian/changelog</filename>." +"<literal>distribution</literal>, is described in <xref linkend=\"distribution" +"\"/>. More information about the structure of this file can be found in the " +"Debian Policy section titled <filename>debian/changelog</filename>." msgstr "" #. type: Content of: <chapter><section><para> #: pkgs.dbk:130 msgid "" "Changelog entries can be used to automatically close Debian bugs when the " -"package is installed into the archive. See <xref " -"linkend=\"upload-bugfix\"/>." +"package is installed into the archive. See <xref linkend=\"upload-bugfix\"/" +">." msgstr "" #. type: Content of: <chapter><section><para> @@ -209,8 +205,8 @@ msgstr "" #: pkgs.dbk:141 msgid "" "There are tools to help you create entries and finalize the " -"<filename>changelog</filename> for release — see <xref " -"linkend=\"devscripts\"/> and <xref linkend=\"dpkg-dev-el\"/>." +"<filename>changelog</filename> for release — see <xref linkend=\"devscripts" +"\"/> and <xref linkend=\"dpkg-dev-el\"/>." msgstr "" #. type: Content of: <chapter><section><para> @@ -247,23 +243,23 @@ msgid "" "<replaceable>package-version</replaceable>.changes</literal>. This will " "check the source package as well as the binary package. If you don't " "understand the output that <command>lintian</command> generates, try adding " -"the <literal>-i</literal> switch, which will cause " -"<command>lintian</command> to output a very verbose description of the " -"problem." +"the <literal>-i</literal> switch, which will cause <command>lintian</" +"command> to output a very verbose description of the problem." msgstr "" #. type: Content of: <chapter><section><itemizedlist><listitem><para> #: pkgs.dbk:176 msgid "" "Normally, a package should <emphasis>not</emphasis> be uploaded if it causes " -"lintian to emit errors (they will start with <literal>E</literal>)." +"<command>lintian</command> to emit errors (they will start with <literal>E</" +"literal>)." msgstr "" #. type: Content of: <chapter><section><itemizedlist><listitem><para> #: pkgs.dbk:180 msgid "" -"For more information on <command>lintian</command>, see <xref " -"linkend=\"lintian\"/>." +"For more information on <command>lintian</command>, see <xref linkend=" +"\"lintian\"/>." msgstr "" #. type: Content of: <chapter><section><itemizedlist><listitem><para> @@ -322,13 +318,12 @@ msgstr "" #: pkgs.dbk:232 msgid "" "For the native packages, the source package includes a Debian source control " -"file (<filename>.dsc</filename>) and the source tarball " -"(<filename>.tar.{gz,bz2,lzma}</filename>). A source package of a non-native " -"package includes a Debian source control file, the original source tarball " -"(<filename>.orig.tar.{gz,bz2,lzma}</filename>) and the Debian changes " -"(<filename>.diff.gz</filename> for the source format “1.0” or " -"<filename>.debian.tar.{gz,bz2,lzma}</filename> for the source format “3.0 " -"(quilt)”)." +"file (<filename>.dsc</filename>) and the source tarball (<filename>.tar.{gz," +"bz2,lzma}</filename>). A source package of a non-native package includes a " +"Debian source control file, the original source tarball (<filename>.orig.tar." +"{gz,bz2,lzma}</filename>) and the Debian changes (<filename>.diff.gz</" +"filename> for the source format “1.0” or <filename>.debian.tar.{gz,bz2,lzma}" +"</filename> for the source format “3.0 (quilt)”)." msgstr "" #. type: Content of: <chapter><section><para> @@ -347,29 +342,28 @@ msgid "" "The first time a version is uploaded which corresponds to a particular " "upstream version, the original source tar file should be uploaded and " "included in the <filename>.changes</filename> file. Subsequently, this very " -"same tar file should be used to build the new diffs and " -"<filename>.dsc</filename> files, and will not need to be re-uploaded." +"same tar file should be used to build the new diffs and <filename>.dsc</" +"filename> files, and will not need to be re-uploaded." msgstr "" #. type: Content of: <chapter><section><para> #: pkgs.dbk:255 msgid "" -"By default, <command>dpkg-genchanges</command> and " -"<command>dpkg-buildpackage</command> will include the original source tar " -"file if and only if the current changelog entry has a different upstream " -"version from the preceding entry. This behavior may be modified by using " -"<literal>-sa</literal> to always include it or <literal>-sd</literal> to " -"always leave it out." +"By default, <command>dpkg-genchanges</command> and <command>dpkg-" +"buildpackage</command> will include the original source tar file if and only " +"if the current changelog entry has a different upstream version from the " +"preceding entry. This behavior may be modified by using <literal>-sa</" +"literal> to always include it or <literal>-sd</literal> to always leave it " +"out." msgstr "" #. type: Content of: <chapter><section><para> #: pkgs.dbk:263 msgid "" -"If no original source is included in the upload, the original source " -"tar-file used by <command>dpkg-source</command> when constructing the " -"<filename>.dsc</filename> file and diff to be uploaded " -"<emphasis>must</emphasis> be byte-for-byte identical with the one already in " -"the archive." +"If no original source is included in the upload, the original source tar-" +"file used by <command>dpkg-source</command> when constructing the <filename>." +"dsc</filename> file and diff to be uploaded <emphasis>must</emphasis> be " +"byte-for-byte identical with the one already in the archive." msgstr "" #. type: Content of: <chapter><section><para> @@ -410,9 +404,9 @@ msgstr "" #. type: Content of: <chapter><section><para> #: pkgs.dbk:293 msgid "" -"Actually, there are two other possible distributions: " -"<literal>stable-security</literal> and <literal>testing-security</literal>, " -"but read <xref linkend=\"bug-security\"/> for more information on those." +"Actually, there are two other possible distributions: <literal>stable-" +"security</literal> and <literal>testing-security</literal>, but read <xref " +"linkend=\"bug-security\"/> for more information on those." msgstr "" #. type: Content of: <chapter><section><para> @@ -500,33 +494,34 @@ msgstr "" msgid "" "Packages uploaded to <literal>stable</literal> need to be compiled on " "systems running <literal>stable</literal>, so that their dependencies are " -"limited to the libraries (and other packages) available in " -"<literal>stable</literal>; for example, a package uploaded to " -"<literal>stable</literal> that depends on a library package that only exists " -"in <literal>unstable</literal> will be rejected. Making changes to " -"dependencies of other packages (by messing with <literal>Provides</literal> " -"or <filename>shlibs</filename> files), possibly making those other packages " -"uninstallable, is strongly discouraged." +"limited to the libraries (and other packages) available in <literal>stable</" +"literal>; for example, a package uploaded to <literal>stable</literal> that " +"depends on a library package that only exists in <literal>unstable</literal> " +"will be rejected. Making changes to dependencies of other packages (by " +"messing with <literal>Provides</literal> or <filename>shlibs</filename> " +"files), possibly making those other packages uninstallable, is strongly " +"discouraged." msgstr "" #. type: Content of: <chapter><section><section><para> #: pkgs.dbk:368 msgid "" "Uploads to the <literal>oldstable</literal> distributions are possible as " -"long as it hasn't been archived. The same rules as for " -"<literal>stable</literal> apply." +"long as it hasn't been archived. The same rules as for <literal>stable</" +"literal> apply." msgstr "" #. type: Content of: <chapter><section><section><title> #: pkgs.dbk:375 -msgid "Special case: uploads to <literal>testing/testing-proposed-updates</literal>" +msgid "" +"Special case: uploads to <literal>testing/testing-proposed-updates</literal>" msgstr "" #. type: Content of: <chapter><section><section><para> #: pkgs.dbk:377 msgid "" -"Please see the information in the <link linkend=\"t-p-u\">testing " -"section</link> for details." +"Please see the information in the <link linkend=\"t-p-u\">testing section</" +"link> for details." msgstr "" #. type: Content of: <chapter><section><title> @@ -543,12 +538,11 @@ msgstr "" #: pkgs.dbk:389 msgid "" "To upload a package, you should upload the files (including the signed " -"changes and dsc-file) with anonymous ftp to " -"<literal>&ftp-upload-host;</literal> in the directory <ulink " -"url=\"ftp://&ftp-upload-host;&upload-queue;\">&upload-queue;</ulink>. To " -"get the files processed there, they need to be signed with a key in the " -"Debian Developers keyring or the Debian Maintainers keyring (see <ulink " -"url=\"&url-wiki-dm;\"></ulink>)." +"changes and dsc-file) with anonymous ftp to <literal>&ftp-upload-host;</" +"literal> in the directory <ulink url=\"ftp://&ftp-upload-host;&upload-queue;" +"\">&upload-queue;</ulink>. To get the files processed there, they need to " +"be signed with a key in the Debian Developers keyring or the Debian " +"Maintainers keyring (see <ulink url=\"&url-wiki-dm;\"></ulink>)." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -562,18 +556,18 @@ msgstr "" #. type: Content of: <chapter><section><section><para> #: pkgs.dbk:403 msgid "" -"You may also find the Debian packages <link " -"linkend=\"dupload\">dupload</link> or <link linkend=\"dput\">dput</link> " -"useful when uploading packages.These handy programs help automate the " -"process of uploading packages into Debian." +"You may also find the Debian packages <link linkend=\"dupload\">dupload</" +"link> or <link linkend=\"dput\">dput</link> useful when uploading packages." +"These handy programs help automate the process of uploading packages into " +"Debian." msgstr "" #. type: Content of: <chapter><section><section><para> #: pkgs.dbk:408 msgid "" -"For removing packages, please see <ulink " -"url=\"ftp://&ftp-upload-host;&upload-queue;README\"/> and the Debian package " -"<link linkend=\"dcut\">dcut</link>." +"For removing packages, please see <ulink url=\"ftp://&ftp-upload-host;" +"&upload-queue;README\"/> and the Debian package <link linkend=\"dcut\">dcut</" +"link>." msgstr "" #. type: Content of: <chapter><section><section><title> @@ -593,21 +587,20 @@ msgstr "" #. type: Content of: <chapter><section><section><para> #: pkgs.dbk:425 msgid "" -"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-upload-host;</literal> in " -"upload-directory <literal>DELAYED/[012345678]-day</literal>. 0-day is " -"uploaded multiple times per day to <literal>&ftp-upload-host;</literal>." +"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-upload-host;</literal> in upload-directory " +"<literal>DELAYED/[012345678]-day</literal>. 0-day is uploaded multiple times " +"per day to <literal>&ftp-upload-host;</literal>." msgstr "" #. type: Content of: <chapter><section><section><para> #: pkgs.dbk:435 msgid "" -"With dput, you can use the <literal>--delayed " -"<replaceable>DELAY</replaceable></literal> parameter to put the package into " -"one of the queues." +"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> @@ -619,11 +612,11 @@ msgstr "" #: pkgs.dbk:443 msgid "" "Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security " -"upload queue (<literal>oldstable-security</literal>, " -"<literal>stable-security</literal>, etc.) without prior authorization from " -"the security team. If the package does not exactly meet the team's " -"requirements, it will cause many problems and delays in dealing with the " -"unwanted upload. For details, please see <xref linkend=\"bug-security\"/>." +"upload queue (<literal>oldstable-security</literal>, <literal>stable-" +"security</literal>, etc.) without prior authorization from the security " +"team. If the package does not exactly meet the team's requirements, it will " +"cause many problems and delays in dealing with the unwanted upload. For " +"details, please see <xref linkend=\"bug-security\"/>." msgstr "" #. type: Content of: <chapter><section><section><title> @@ -634,19 +627,18 @@ msgstr "" #. type: Content of: <chapter><section><section><para> #: pkgs.dbk:455 msgid "" -"There is an alternative upload queue in Europe at <ulink " -"url=\"ftp://&ftp-eu-upload-host;&upload-queue;\"/>. It operates in the same " -"way as <literal>&ftp-upload-host;</literal>, but should be faster for " -"European developers." +"There is an alternative upload queue in Europe at <ulink url=\"ftp://&ftp-eu-" +"upload-host;&upload-queue;\"/>. It operates in the same way as <literal>&ftp-" +"upload-host;</literal>, but should be faster for European developers." msgstr "" #. type: Content of: <chapter><section><section><para> #: pkgs.dbk:461 msgid "" -"Packages can also be uploaded via ssh to " -"<literal>&ssh-upload-host;</literal>; files should be put " -"<literal>/srv/upload.debian.org/UploadQueue</literal>. This queue does not " -"support <link linkend=\"delayed-incoming\">delayed uploads</link>." +"Packages can also be uploaded via ssh to <literal>&ssh-upload-host;</" +"literal>; files should be put <literal>/srv/upload.debian.org/UploadQueue</" +"literal>. This queue does not support <link linkend=\"delayed-incoming" +"\">delayed uploads</link>." msgstr "" #. type: Content of: <chapter><section><section><title> @@ -660,11 +652,11 @@ msgid "" "The Debian archive maintainers are responsible for handling package " "uploads. For the most part, uploads are automatically handled on a daily " "basis by the archive maintenance tools, <command>katie</command>. " -"Specifically, updates to existing packages to the " -"<literal>unstable</literal> distribution are handled automatically. In " -"other cases, notably new packages, placing the uploaded package into the " -"distribution is handled manually. When uploads are handled manually, the " -"change to the archive may take up to a month to occur. Please be patient." +"Specifically, updates to existing packages to the <literal>unstable</" +"literal> distribution are handled automatically. In other cases, notably " +"new packages, placing the uploaded package into the distribution is handled " +"manually. When uploads are handled manually, the change to the archive may " +"take up to a month to occur. Please be patient." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -703,8 +695,8 @@ msgid "" "and <literal>Priority</literal> fields do not actually specify where the " "file will be placed in the archive, nor its priority. In order to retain " "the overall integrity of the archive, it is the archive maintainers who have " -"control over these fields. The values in the " -"<filename>debian/control</filename> file are actually just hints." +"control over these fields. The values in the <filename>debian/control</" +"filename> file are actually just hints." msgstr "" #. type: Content of: <chapter><section><para> @@ -715,9 +707,9 @@ msgid "" "disparity between the <literal>override file</literal> and the package's " "fields as indicated in <filename>debian/control</filename>, then you will " "receive an email noting the divergence when the package is installed into " -"the archive. You can either correct your " -"<filename>debian/control</filename> file for your next upload, or else you " -"may wish to make a change in the <literal>override file</literal>." +"the archive. You can either correct your <filename>debian/control</" +"filename> file for your next upload, or else you may wish to make a change " +"in the <literal>override file</literal>." msgstr "" #. type: Content of: <chapter><section><para> @@ -725,12 +717,12 @@ msgstr "" 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 " -"accurate. Next, submit a bug against <systemitem " -"role=\"package\">ftp.debian.org</systemitem> requesting that the section or " -"priority for your package be changed from the old section or priority to the " -"new one. Use a Subject like <literal>override: PACKAGE1:section/priority, " -"[...], PACKAGEX:section/priority</literal>, and include the justification " -"for the change in the body of the bug report." +"accurate. Next, submit a bug against <systemitem role=\"package\">ftp." +"debian.org</systemitem> requesting that the section or priority for your " +"package be changed from the old section or priority to the new one. Use a " +"Subject like <literal>override: PACKAGE1:section/priority, [...], PACKAGEX:" +"section/priority</literal>, and include the justification for the change in " +"the body of the bug report." msgstr "" #. type: Content of: <chapter><section><para> @@ -738,18 +730,18 @@ msgstr "" msgid "" "For more information about <literal>override files</literal>, see " "<citerefentry> <refentrytitle>dpkg-scanpackages</refentrytitle> " -"<manvolnum>1</manvolnum> </citerefentry> and <ulink " -"url=\"&url-bts-devel;#maintincorrect\"></ulink>." +"<manvolnum>1</manvolnum> </citerefentry> and <ulink url=\"&url-bts-devel;" +"#maintincorrect\"></ulink>." msgstr "" #. type: Content of: <chapter><section><para> #: pkgs.dbk:537 msgid "" "Note that the <literal>Section</literal> field describes both the section as " -"well as the subsection, which are described in <xref " -"linkend=\"archive-sections\"/>. If the section is main, it should be " -"omitted. The list of allowable subsections can be found in <ulink " -"url=\"&url-debian-policy;ch-archive.html#s-subsections\"></ulink>." +"well as the subsection, which are described in <xref linkend=\"archive-" +"sections\"/>. If the section is main, it should be omitted. The list of " +"allowable subsections can be found in <ulink url=\"&url-debian-policy;ch-" +"archive.html#s-subsections\"></ulink>." msgstr "" #. type: Content of: <chapter><section><title> @@ -760,19 +752,19 @@ msgstr "" #. type: Content of: <chapter><section><para> #: pkgs.dbk:548 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 reports properly (see <xref linkend=\"submit-bug\"/>), how to " -"update them and reorder them, and how to process and close them." +"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 " +"reports properly (see <xref linkend=\"submit-bug\"/>), how to update them " +"and reorder them, and how to process and close them." msgstr "" #. type: Content of: <chapter><section><para> #: pkgs.dbk:554 msgid "" -"The bug tracking system's features are described in the <ulink " -"url=\"&url-bts-devel;\">BTS documentation for developers</ulink>. This " -"includes closing bugs, sending followup messages, assigning severities and " -"tags, marking bugs as forwarded, and other issues." +"The bug tracking system's features are described in the <ulink url=\"&url-" +"bts-devel;\">BTS documentation for developers</ulink>. This includes " +"closing bugs, sending followup messages, assigning severities and tags, " +"marking bugs as forwarded, and other issues." msgstr "" #. type: Content of: <chapter><section><para> @@ -781,8 +773,8 @@ msgid "" "Operations such as reassigning bugs to other packages, merging separate bug " "reports about the same issue, or reopening bugs when they are prematurely " "closed, are handled using the so-called control mail server. All of the " -"commands available on this server are described in the <ulink " -"url=\"&url-bts-control;\">BTS control server documentation</ulink>." +"commands available on this server are described in the <ulink url=\"&url-bts-" +"control;\">BTS control server documentation</ulink>." msgstr "" #. type: Content of: <chapter><section><section><title> @@ -796,18 +788,18 @@ 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 " "packages. The BTS contains all the open bugs against your packages. You " -"can check them by browsing this page: " -"<literal>http://&bugs-host;/<replaceable>yourlogin</replaceable>@debian.org</literal>." +"can check them by browsing this page: <literal>http://&bugs-host;/" +"<replaceable>yourlogin</replaceable>@debian.org</literal>." msgstr "" #. type: Content of: <chapter><section><section><para> #: pkgs.dbk:577 msgid "" -"Maintainers interact with the BTS via email addresses at " -"<literal>&bugs-host;</literal>. Documentation on available commands can be " -"found at <ulink url=\"&url-bts;\"></ulink>, or, if you have installed the " -"<systemitem role=\"package\">doc-debian</systemitem> package, you can look " -"at the local files &file-bts-docs;." +"Maintainers interact with the BTS via email addresses at <literal>&bugs-host;" +"</literal>. Documentation on available commands can be found at <ulink url=" +"\"&url-bts;\"></ulink>, or, if you have installed the <systemitem role=" +"\"package\">doc-debian</systemitem> package, you can look at the local files " +"&file-bts-docs;." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -842,14 +834,13 @@ msgstr "" #: pkgs.dbk:601 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.g., <email><replaceable>123</replaceable>@&bugs-host;</email>). If " -"you're writing a new mail and you don't remember the submitter email " -"address, you can use the " -"<email><replaceable>123</replaceable>-submitter@&bugs-host;</email> email to " -"contact the submitter <emphasis>and</emphasis> to record your mail within " -"the bug log (that means you don't need to send a copy of the mail to " -"<email><replaceable>123</replaceable>@&bugs-host;</email>)." +"is sent both to the original submitter of the bug, and to the bug itself (e." +"g., <email><replaceable>123</replaceable>@&bugs-host;</email>). If you're " +"writing a new mail and you don't remember the submitter email address, you " +"can use the <email><replaceable>123</replaceable>-submitter@&bugs-host;</" +"email> email to contact the submitter <emphasis>and</emphasis> to record " +"your mail within the bug log (that means you don't need to send a copy of " +"the mail to <email><replaceable>123</replaceable>@&bugs-host;</email>)." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -934,8 +925,8 @@ msgid "" "decision of the technical committee by reassigning the bug to <systemitem " "role=\"package\">tech-ctte</systemitem> (you may use the clone command of " "the BTS if you wish to keep it reported against your package). Before doing " -"so, please read the <ulink url=\"&url-tech-ctte;\">recommended " -"procedure</ulink>." +"so, please read the <ulink url=\"&url-tech-ctte;\">recommended procedure</" +"ulink>." msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> @@ -943,15 +934,14 @@ msgstr "" 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 " -"reassigned to, you should ask for help on <link " -"linkend=\"irc-channels\">IRC</link> or on &email-debian-devel;. Please " -"inform the maintainer(s) of the package you reassign the bug to, for example " -"by Cc:ing the message that does the reassign to " -"<email><replaceable>packagename</replaceable>@packages.debian.org</email> " -"and explaining your reasons in that mail. Please note that a simple " -"reassignment is <emphasis>not</emphasis> e-mailed to the maintainers of the " -"package being reassigned to, so they won't know about it until they look at " -"a bug overview for their packages." +"reassigned to, you should ask for help on <link linkend=\"irc-channels" +"\">IRC</link> or on &email-debian-devel;. Please inform the maintainer(s) " +"of the package you reassign the bug to, for example by Cc:ing the message " +"that does the reassign to <email><replaceable>packagename</" +"replaceable>@packages.debian.org</email> and explaining your reasons in that " +"mail. Please note that a simple reassignment is <emphasis>not</emphasis> e-" +"mailed to the maintainers of the package being reassigned to, so they won't " +"know about it until they look at a bug overview for their packages." msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> @@ -1010,8 +1000,8 @@ msgid "" "has been fixed or not. If it has, you just close it, otherwise you have to " "remind the author about it. If you have the required skills you can prepare " "a patch that fixes the bug and send it to the author at the same time. Make " -"sure to send the patch to the BTS and to tag the bug as " -"<literal>patch</literal>." +"sure to send the patch to the BTS and to tag the bug as <literal>patch</" +"literal>." msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> @@ -1053,9 +1043,9 @@ msgstr "" #: pkgs.dbk:771 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</filename> file, following a certain syntax, and " -"the archive maintenance software will close the bugs for you. For example:" +"upload — just list the fixed bugs in your <filename>debian/changelog</" +"filename> file, following a certain syntax, and the archive maintenance " +"software will close the bugs for you. For example:" msgstr "" #. type: Content of: <chapter><section><section><screen> @@ -1109,15 +1099,15 @@ msgstr "" 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 " -"wrongly closed bugs, send a <literal>reopen " -"<replaceable>XXX</replaceable></literal> command to the bug tracking " -"system's control address, &email-bts-control;. To close any remaining bugs " -"that were fixed by your upload, email the <filename>.changes</filename> file " -"to <email><replaceable>XXX</replaceable>-done@&bugs-host;</email>, where " -"<replaceable>XXX</replaceable> is the bug number, and put Version: " -"<replaceable>YYY</replaceable> and an empty line as the first two lines of " -"the body of the email, where <replaceable>YYY</replaceable> is the first " -"version where the bug has been fixed." +"wrongly closed bugs, send a <literal>reopen <replaceable>XXX</replaceable></" +"literal> command to the bug tracking system's control address, &email-bts-" +"control;. To close any remaining bugs that were fixed by your upload, email " +"the <filename>.changes</filename> file to <email><replaceable>XXX</" +"replaceable>-done@&bugs-host;</email>, where <replaceable>XXX</replaceable> " +"is the bug number, and put Version: <replaceable>YYY</replaceable> and an " +"empty line as the first two lines of the body of the email, where " +"<replaceable>YYY</replaceable> is the first version where the bug has been " +"fixed." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -1175,15 +1165,16 @@ msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> #: pkgs.dbk:859 -msgid "The nature of the fix, if any is available (patches are especially helpful)" +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:864 msgid "" -"Any fixed packages that you have prepared yourself (send only the " -"<filename>.diff.gz</filename> and <filename>.dsc</filename> files and read " -"<xref linkend=\"bug-security-building\"/> first)" +"Any fixed packages that you have prepared yourself (send only the <filename>." +"diff.gz</filename> and <filename>.dsc</filename> files and read <xref " +"linkend=\"bug-security-building\"/> first)" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> @@ -1196,8 +1187,8 @@ msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> #: pkgs.dbk:877 msgid "" -"Any information needed for the advisory (see <xref " -"linkend=\"bug-security-advisories\"/>)" +"Any information needed for the advisory (see <xref linkend=\"bug-security-" +"advisories\"/>)" msgstr "" #. type: Content of: <chapter><section><section><para> @@ -1217,12 +1208,12 @@ msgstr "" #. type: Content of: <chapter><section><section><section><para> #: pkgs.dbk:890 msgid "" -"The security team maintains a central database, the <ulink " -"url=\"http://security-tracker.debian.org/\">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." +"The security team maintains a central database, the <ulink url=\"http://" +"security-tracker.debian.org/\">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> @@ -1326,9 +1317,8 @@ msgstr "" #: pkgs.dbk:975 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#contact\">Security Team FAQ</ulink> " -"for details." +"sensitive issues. See the <ulink url=\"http://www.debian.org/security/" +"faq#contact\">Security Team FAQ</ulink> for details." msgstr "" #. type: Content of: <chapter><section><section><section><title> @@ -1342,8 +1332,8 @@ msgid "" "Security advisories are only issued for the current, released stable " "distribution, and <emphasis>not</emphasis> for <literal>testing</literal> or " "<literal>unstable</literal>. When released, advisories are sent to the " -"&email-debian-security-announce; mailing list and posted on <ulink " -"url=\"&url-debian-security-advisories;\">the security web page</ulink>. " +"&email-debian-security-announce; mailing list and posted on <ulink url=" +"\"&url-debian-security-advisories;\">the security web page</ulink>. " "Security advisories are written and posted by the security team. However " "they certainly do not mind if a maintainer can supply some of the " "information for them, or write part of the text. Information that should be " @@ -1405,9 +1395,9 @@ msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> #: pkgs.dbk:1047 msgid "" -"References to upstream advisories, <ulink " -"url=\"http://cve.mitre.org\">CVE</ulink> identifiers, and any other " -"information useful in cross-referencing the vulnerability" +"References to upstream advisories, <ulink url=\"http://cve.mitre.org\">CVE</" +"ulink> identifiers, and any other information useful in cross-referencing " +"the vulnerability" msgstr "" #. type: Content of: <chapter><section><section><section><title> @@ -1470,9 +1460,9 @@ msgid "" "Do <emphasis role=\"strong\">NOT</emphasis> include any changes in your " "package which are not directly related to fixing the vulnerability. These " "will only need to be reverted, and this wastes time. If there are other " -"bugs in your package that you would like to fix, make an upload to " -"proposed-updates in the usual way, after the security advisory is issued. " -"The security update mechanism is not a means for introducing changes to your " +"bugs in your package that you would like to fix, make an upload to proposed-" +"updates in the usual way, after the security advisory is issued. The " +"security update mechanism is not a means for introducing changes to your " "package which would otherwise be rejected from the stable release, so please " "do not attempt to do this." msgstr "" @@ -1483,9 +1473,8 @@ msgid "" "Review and test your changes as much as possible. Check the differences " "from the previous version repeatedly (<command>interdiff</command> from the " "<systemitem role=\"package\">patchutils</systemitem> package and " -"<command>debdiff</command> from <systemitem " -"role=\"package\">devscripts</systemitem> are useful tools for this, see " -"<xref linkend=\"debdiff\"/>)." +"<command>debdiff</command> from <systemitem role=\"package\">devscripts</" +"systemitem> are useful tools for this, see <xref linkend=\"debdiff\"/>)." msgstr "" #. type: Content of: <chapter><section><section><section><para> @@ -1507,20 +1496,20 @@ msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> #: pkgs.dbk:1125 -msgid "The upload should have <emphasis role=\"strong\">urgency=high</emphasis>." +msgid "" +"The upload should have <emphasis role=\"strong\">urgency=high</emphasis>." msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> #: pkgs.dbk:1130 msgid "" "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." +"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> @@ -1528,12 +1517,12 @@ msgstr "" msgid "" "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+lenny1</literal>, of course increasing 1 for any " +"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+lenny1</literal>, of course increasing 1 for any " "subsequent uploads." msgstr "" @@ -1545,17 +1534,16 @@ msgid "" "<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>)." +"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:1164 msgid "" -"Be sure to use the <emphasis role=\"strong\">exact same " -"<filename>*.orig.tar.{gz,bz2,lzma}</filename></emphasis> 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,bz2,lzma}</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> @@ -1577,11 +1565,10 @@ msgstr "" #: pkgs.dbk:1185 msgid "" "Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security " -"upload queue (<literal>oldstable-security</literal>, " -"<literal>stable-security</literal>, etc.) without prior authorization from " -"the security team. If the package does not exactly meet the team's " -"requirements, it will cause many problems and delays in dealing with the " -"unwanted upload." +"upload queue (<literal>oldstable-security</literal>, <literal>stable-" +"security</literal>, etc.) without prior authorization from the security " +"team. If the package does not exactly meet the team's requirements, it will " +"cause many problems and delays in dealing with the unwanted upload." msgstr "" #. type: Content of: <chapter><section><section><section><para> @@ -1661,8 +1648,8 @@ msgstr "" 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 " -"package should be moved to `main' or `contrib'.<placeholder " -"type=\"footnote\" id=\"0\"/>" +"package should be moved to `main' or `contrib'.<placeholder type=\"footnote" +"\" id=\"0\"/>" msgstr "" #. type: Content of: <chapter><section><section><para> @@ -1701,16 +1688,16 @@ msgid "" "old compatibility library which is no longer required), you need to file a " "bug against <literal>ftp.debian.org</literal> asking that the package be " "removed; as all bugs, this bug should normally have normal severity. The " -"bug title should be in the form <literal>RM: " -"<replaceable>package</replaceable> <replaceable>[architecture " -"list]</replaceable> -- <replaceable>reason</replaceable></literal>, where " -"<replaceable>package</replaceable> is the package to be removed and " -"<replaceable>reason</replaceable> is a short summary of the reason for the " -"removal request. <replaceable>[architecture list]</replaceable> is optional " -"and only needed if the removal request only applies to some architectures, " -"not all. Note that the <command>reportbug</command> will create a title " -"conforming to these rules when you use it to report a bug against the " -"<literal>ftp.debian.org</literal> pseudo-package." +"bug title should be in the form <literal>RM: <replaceable>package</" +"replaceable> <replaceable>[architecture list]</replaceable> -- " +"<replaceable>reason</replaceable></literal>, where <replaceable>package</" +"replaceable> is the package to be removed and <replaceable>reason</" +"replaceable> is a short summary of the reason for the removal request. " +"<replaceable>[architecture list]</replaceable> is optional and only needed " +"if the removal request only applies to some architectures, not all. Note " +"that the <command>reportbug</command> will create a title conforming to " +"these rules when you use it to report a bug against the <literal>ftp.debian." +"org</literal> pseudo-package." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -1719,10 +1706,9 @@ 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). " "There are several other standard acronyms used in the reasoning for a " -"package removal, see <ulink " -"url=\"http://&ftp-master-host;/removals.html\"></ulink> for a complete " -"list. That page also provides a convenient overview of pending removal " -"requests." +"package removal, see <ulink url=\"http://&ftp-master-host;/removals.html\"></" +"ulink> for a complete list. That page also provides a convenient overview of " +"pending removal requests." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -1740,10 +1726,10 @@ msgstr "" #: pkgs.dbk:1304 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-automatically. For a binary-package, this means if there is no longer " -"any source package producing this binary package; if the binary package is " -"just no longer produced on some architectures, a removal request is still " +"a (source or binary) package is an orphan, it will be removed semi-" +"automatically. For a binary-package, this means if there is no longer any " +"source package producing this binary package; if the binary package is just " +"no longer produced on some architectures, a removal request is still " "necessary. For a source-package, this means that all binary packages it " "refers to have been taken over by another source package." msgstr "" @@ -1765,35 +1751,31 @@ msgid "" "maintainer. Should the package be orphaned and thus have no maintainer, you " "should first discuss the removal request on &email-debian-qa;. If there is a " "consensus that the package should be removed, you should reassign and " -"retitle the <literal>O:</literal> bug filed against the " -"<literal>wnpp</literal> package instead of filing a new bug as removal " -"request." +"retitle the <literal>O:</literal> bug filed against the <literal>wnpp</" +"literal> package instead of filing a new bug as removal request." msgstr "" #. type: Content of: <chapter><section><section><para> #: pkgs.dbk:1329 msgid "" "Further information relating to these and other package removal related " -"topics may be found at <ulink " -"url=\"http://wiki.debian.org/ftpmaster_Removals\"></ulink> and <ulink " -"url=\"&url-debian-qa;howto-remove.html\"></ulink>." +"topics may be found at <ulink url=\"http://wiki.debian.org/ftpmaster_Removals" +"\"></ulink> and <ulink url=\"&url-debian-qa;howto-remove.html\"></ulink>." msgstr "" #. type: Content of: <chapter><section><section><para> #: pkgs.dbk:1334 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</command> program from the <systemitem " -"role=\"package\">apt</systemitem> package. When invoked as " -"<literal>apt-cache showpkg <replaceable>package</replaceable></literal>, the " -"program will show details for <replaceable>package</replaceable>, including " -"reverse depends. Other useful programs include <command>apt-cache " -"rdepends</command>, <command>apt-rdepends</command>, " -"<command>build-rdeps</command> (in the <systemitem " -"role=\"package\">devscripts</systemitem> package) and " -"<command>grep-dctrl</command>. Removal of orphaned packages is discussed on " -"&email-debian-qa;." +"If in doubt concerning whether a package is disposable, email &email-debian-" +"devel; asking for opinions. Also of interest is the <command>apt-cache</" +"command> program from the <systemitem role=\"package\">apt</systemitem> " +"package. When invoked as <literal>apt-cache showpkg <replaceable>package</" +"replaceable></literal>, the program will show details for " +"<replaceable>package</replaceable>, including reverse depends. Other useful " +"programs include <command>apt-cache rdepends</command>, <command>apt-" +"rdepends</command>, <command>build-rdeps</command> (in the <systemitem role=" +"\"package\">devscripts</systemitem> package) and <command>grep-dctrl</" +"command>. Removal of orphaned packages is discussed on &email-debian-qa;." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -1801,12 +1783,11 @@ msgstr "" 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 " -"actual code has evolved into another package (e.g. " -"<literal>libfoo12</literal> was removed because <literal>libfoo13</literal> " -"supersedes it) or closed if the software is simply no longer part of " -"Debian. When closing the bugs, to avoid marking the bugs as fixed in " -"versions of the packages in previous Debian releases, they should be marked " -"as fixed in the version " +"actual code has evolved into another package (e.g. <literal>libfoo12</" +"literal> was removed because <literal>libfoo13</literal> supersedes it) or " +"closed if the software is simply no longer part of Debian. When closing the " +"bugs, to avoid marking the bugs as fixed in versions of the packages in " +"previous Debian releases, they should be marked as fixed in the version " "<literal><most-recent-version-ever-in-Debian>+rm</literal>." msgstr "" @@ -1818,15 +1799,15 @@ msgstr "" #. type: Content of: <chapter><section><section><section><para> #: pkgs.dbk:1360 msgid "" -"In the past, it was possible to remove packages from " -"<filename>incoming</filename>. However, with the introduction of the new " -"incoming system, this is no longer possible. Instead, you have to upload a " -"new revision of your package with a higher version than the package you want " -"to replace. Both versions will be installed in the archive but only the " -"higher version will actually be available in <literal>unstable</literal> " -"since the previous version will immediately be replaced by the higher. " -"However, if you do proper testing of your packages, the need to replace a " -"package should not occur too often anyway." +"In the past, it was possible to remove packages from <filename>incoming</" +"filename>. However, with the introduction of the new incoming system, this " +"is no longer possible. Instead, you have to upload a new revision of your " +"package with a higher version than the package you want to replace. Both " +"versions will be installed in the archive but only the higher version will " +"actually be available in <literal>unstable</literal> since the previous " +"version will immediately be replaced by the higher. However, if you do " +"proper testing of your packages, the need to replace a package should not " +"occur too often anyway." msgstr "" #. type: Content of: <chapter><section><section><title> @@ -1847,9 +1828,9 @@ msgid "" "if all packages depending on the obsolete package name continue to work " "after the renaming. Once you've uploaded the package and the package has " "moved into the archive, file a bug against <literal>ftp.debian.org</literal> " -"asking to remove the package with the obsolete name (see <xref " -"linkend=\"removing-pkgs\"/>). Do not forget to properly reassign the " -"package's bugs at the same time." +"asking to remove the package with the obsolete name (see <xref linkend=" +"\"removing-pkgs\"/>). Do not forget to properly reassign the package's bugs " +"at the same time." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -1862,10 +1843,9 @@ msgid "" "sources: if you wish to replace the upstream source tarball of your package, " "you will need to upload it with a different version. An easy possibility is " "to replace <filename>foo_1.00.orig.tar.gz</filename> with " -"<filename>foo_1.00+0.orig.tar.gz</filename> or " -"<filename>foo_1.00.orig.tar.bz2</filename>. This restriction gives each " -"file on the ftp site a unique name, which helps to ensure consistency across " -"the mirror network." +"<filename>foo_1.00+0.orig.tar.gz</filename> or <filename>foo_1.00.orig.tar." +"bz2</filename>. This restriction gives each file on the ftp site a unique " +"name, which helps to ensure consistency across the mirror network." msgstr "" #. type: Content of: <chapter><section><section><title> @@ -1879,16 +1859,16 @@ 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 " "maintainer to <literal>Debian QA Group &orphan-address;</literal> and submit " -"a bug report against the pseudo package <systemitem " -"role=\"package\">wnpp</systemitem>. The bug report should be titled " -"<literal>O: <replaceable>package</replaceable> -- <replaceable>short " -"description</replaceable></literal> indicating that the package is now " -"orphaned. The severity of the bug should be set to " -"<literal>normal</literal>; if the package has a priority of standard or " -"higher, it should be set to important. If you feel it's necessary, send a " -"copy to &email-debian-devel; by putting the address in the X-Debbugs-CC: " -"header of the message (no, don't use CC:, because that way the message's " -"subject won't indicate the bug number)." +"a bug report against the pseudo package <systemitem role=\"package\">wnpp</" +"systemitem>. The bug report should be titled <literal>O: " +"<replaceable>package</replaceable> -- <replaceable>short description</" +"replaceable></literal> indicating that the package is now orphaned. The " +"severity of the bug should be set to <literal>normal</literal>; if the " +"package has a priority of standard or higher, it should be set to " +"important. If you feel it's necessary, send a copy to &email-debian-devel; " +"by putting the address in the X-Debbugs-CC: header of the message (no, don't " +"use CC:, because that way the message's subject won't indicate the bug " +"number)." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -1897,14 +1877,15 @@ 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 " "role=\"package\">wnpp</systemitem> and title it <literal>RFA: " -"<replaceable>package</replaceable> -- <replaceable>short " -"description</replaceable></literal>. <literal>RFA</literal> stands for " -"<literal>Request For Adoption</literal>." +"<replaceable>package</replaceable> -- <replaceable>short description</" +"replaceable></literal>. <literal>RFA</literal> stands for <literal>Request " +"For Adoption</literal>." msgstr "" #. type: Content of: <chapter><section><section><para> #: pkgs.dbk:1433 -msgid "More information is on the <ulink url=\"&url-wnpp;\">WNPP web pages</ulink>." +msgid "" +"More information is on the <ulink url=\"&url-wnpp;\">WNPP web pages</ulink>." msgstr "" #. type: Content of: <chapter><section><section><title> @@ -1916,10 +1897,10 @@ msgstr "" #: pkgs.dbk:1441 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)</ulink>. If you wish to take over maintenance of any of the packages " -"listed in the WNPP, please take a look at the aforementioned page for " -"information and procedures." +"url=\"&url-wnpp;\">Work-Needing and Prospective Packages list (WNPP)</" +"ulink>. If you wish to take over maintenance of any of the packages listed " +"in the WNPP, please take a look at the aforementioned page for information " +"and procedures." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -1940,9 +1921,8 @@ msgid "" "take over a package. Complaints about maintainers should be brought up on " "the developers' mailing list. If the discussion doesn't end with a positive " "conclusion, and the issue is of a technical nature, consider bringing it to " -"the attention of the technical committee (see the <ulink " -"url=\"&url-tech-ctte;\">technical committee web page</ulink> for more " -"information)." +"the attention of the technical committee (see the <ulink url=\"&url-tech-" +"ctte;\">technical committee web page</ulink> for more information)." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -1979,9 +1959,9 @@ msgid "" "different from the original architecture of the package maintainer's binary " "package. It is a unique and essential activity. In fact, porters do most " "of the actual compiling of Debian packages. For instance, when a maintainer " -"uploads a (portable) source packages with binaries for the " -"<literal>i386</literal> architecture, it will be built for each of the other " -"architectures, amounting to &number-of-arches; more builds." +"uploads a (portable) source packages with binaries for the <literal>i386</" +"literal> architecture, it will be built for each of the other architectures, " +"amounting to &number-of-arches; more builds." msgstr "" #. type: Content of: <chapter><section><section><title> @@ -2021,19 +2001,18 @@ msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> #: pkgs.dbk:1519 msgid "" -"Make sure that your <literal>Build-Depends</literal> and " -"<literal>Build-Depends-Indep</literal> settings in " -"<filename>debian/control</filename> are set properly. The best way to " -"validate this is to use the <systemitem " -"role=\"package\">debootstrap</systemitem> package to create an " -"<literal>unstable</literal> chroot environment (see <xref " -"linkend=\"debootstrap\"/>). Within that chrooted environment, install the " -"<systemitem role=\"package\">build-essential</systemitem> package and any " -"package dependencies mentioned in <literal>Build-Depends</literal> and/or " -"<literal>Build-Depends-Indep</literal>. Finally, try building your package " -"within that chrooted environment. These steps can be automated by the use " -"of the <command>pbuilder</command> program which is provided by the package " -"of the same name (see <xref linkend=\"pbuilder\"/>)." +"Make sure that your <literal>Build-Depends</literal> and <literal>Build-" +"Depends-Indep</literal> settings in <filename>debian/control</filename> are " +"set properly. The best way to validate this is to use the <systemitem role=" +"\"package\">debootstrap</systemitem> package to create an <literal>unstable</" +"literal> chroot environment (see <xref linkend=\"debootstrap\"/>). Within " +"that chrooted environment, install the <systemitem role=\"package\">build-" +"essential</systemitem> package and any package dependencies mentioned in " +"<literal>Build-Depends</literal> and/or <literal>Build-Depends-Indep</" +"literal>. Finally, try building your package within that chrooted " +"environment. These steps can be automated by the use of the " +"<command>pbuilder</command> program which is provided by the package of the " +"same name (see <xref linkend=\"pbuilder\"/>)." msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> @@ -2055,10 +2034,10 @@ msgstr "" 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, " -"maintainers don't follow the instructions in the <ulink " -"url=\"&url-debian-policy;\">Debian Policy Manual</ulink>. Setting your " -"architecture to only one architecture (such as <literal>i386</literal> or " -"<literal>amd64</literal>) is usually incorrect." +"maintainers don't follow the instructions in the <ulink url=\"&url-debian-" +"policy;\">Debian Policy Manual</ulink>. Setting your architecture to only " +"one architecture (such as <literal>i386</literal> or <literal>amd64</" +"literal>) is usually incorrect." msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> @@ -2073,29 +2052,29 @@ msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> #: pkgs.dbk:1562 msgid "" -"Make sure you don't ship your source package with the " -"<filename>debian/files</filename> or <filename>debian/substvars</filename> " -"files. They should be removed by the <literal>clean</literal> target of " -"<filename>debian/rules</filename>." +"Make sure you don't ship your source package with the <filename>debian/" +"files</filename> or <filename>debian/substvars</filename> files. They " +"should be removed by the <literal>clean</literal> target of <filename>debian/" +"rules</filename>." msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> #: pkgs.dbk:1570 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>/usr/local/bin</filename> or the like. Try not to rely on " -"programs being setup in a special way. Try building your package on another " -"machine, even if it's the same architecture." +"programs. For instance, you should never be calling programs in <filename>/" +"usr/local/bin</filename> or the like. Try not to rely on programs being " +"setup in a special way. Try building your package on another machine, even " +"if it's the same architecture." msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> #: pkgs.dbk:1579 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 be aware that any case like this needs manual bootstrapping and cannot " -"be done by automated package builders." +"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 " +"be aware that any case like this needs manual bootstrapping and cannot be " +"done by automated package builders." msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> @@ -2114,8 +2093,8 @@ msgid "" "<literal>binary-arch</literal> and <literal>binary-indep</literal> targets, " "as the Debian Policy Manual requires. Make sure that both targets work " "independently, that is, that you can call the target without having called " -"the other before. To test this, try to run <command>dpkg-buildpackage " -"-B</command>." +"the other before. To test this, try to run <command>dpkg-buildpackage -B</" +"command>." msgstr "" #. type: Content of: <chapter><section><section><title> @@ -2145,12 +2124,11 @@ msgstr "" #. type: Content of: <chapter><section><section><para> #: pkgs.dbk:1621 msgid "" -"The way to invoke <command>dpkg-buildpackage</command> is as " -"<literal>dpkg-buildpackage -B " -"-m<replaceable>porter-email</replaceable></literal>. Of course, set " -"<replaceable>porter-email</replaceable> to your email address. This will do " -"a binary-only build of only the architecture-dependent portions of the " -"package, using the <literal>binary-arch</literal> target in " +"The way to invoke <command>dpkg-buildpackage</command> is as <literal>dpkg-" +"buildpackage -B -m<replaceable>porter-email</replaceable></literal>. Of " +"course, set <replaceable>porter-email</replaceable> to your email address. " +"This will do a binary-only build of only the architecture-dependent portions " +"of the package, using the <literal>binary-arch</literal> target in " "<filename>debian/rules</filename>." msgstr "" @@ -2160,8 +2138,8 @@ 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 " "<command>debsign</command> on your <filename>.changes</filename> file to " -"have it signed conveniently, or use the remote signing mode of " -"<command>dpkg-sig</command>." +"have it signed conveniently, or use the remote signing mode of <command>dpkg-" +"sig</command>." msgstr "" #. type: Content of: <chapter><section><section><section><title> @@ -2185,18 +2163,18 @@ msgstr "" #: pkgs.dbk:1648 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-dependent and arch-independent packages that have inter-dependencies " -"generated using dpkg's substitution variable " -"<literal>$(Source-Version)</literal>." +"uninstallable. This could happen when a source package generates arch-" +"dependent and arch-independent packages that have inter-dependencies " +"generated using dpkg's substitution variable <literal>$(Source-Version)</" +"literal>." msgstr "" #. type: Content of: <chapter><section><section><section><para> #: pkgs.dbk:1654 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 to consider themselves out of date or requiring recompilation." +"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 " +"to consider themselves out of date or requiring recompilation." msgstr "" #. type: Content of: <chapter><section><section><section><para> @@ -2225,20 +2203,20 @@ msgid "" "The ``magic'' for a recompilation-only NMU is triggered by using a suffix " "appended to the package version number, following the form " "<literal>b<replaceable>number</replaceable></literal>. For instance, if the " -"latest version you are recompiling against was version " -"<literal>2.9-3</literal>, your binary-only NMU should carry a version of " -"<literal>2.9-3+b1</literal>. If the latest version was " -"<literal>3.4+b1</literal> (i.e, a native package with a previous " -"recompilation NMU), your binary-only NMU should have a version number of " -"<literal>3.4+b2</literal>.<placeholder type=\"footnote\" id=\"0\"/>" +"latest version you are recompiling against was version <literal>2.9-3</" +"literal>, your binary-only NMU should carry a version of <literal>2.9-3+b1</" +"literal>. If the latest version was <literal>3.4+b1</literal> (i.e, a " +"native package with a previous recompilation NMU), your binary-only NMU " +"should have a version number of <literal>3.4+b2</literal>.<placeholder type=" +"\"footnote\" id=\"0\"/>" msgstr "" #. type: Content of: <chapter><section><section><section><para> #: pkgs.dbk:1682 msgid "" -"Similar to initial porter uploads, the correct way of invoking " -"<command>dpkg-buildpackage</command> is <literal>dpkg-buildpackage " -"-B</literal> to only build the architecture-dependent parts of the package." +"Similar to initial porter uploads, the correct way of invoking <command>dpkg-" +"buildpackage</command> is <literal>dpkg-buildpackage -B</literal> to only " +"build the architecture-dependent parts of the package." msgstr "" #. type: Content of: <chapter><section><section><section><title> @@ -2327,8 +2305,8 @@ msgstr "" #. type: Content of: <chapter><section><section><section><para> #: pkgs.dbk:1747 msgid "" -"Web pages containing the status of each port can be found at <ulink " -"url=\"&url-debian-ports;\"></ulink>." +"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> @@ -2348,8 +2326,8 @@ msgstr "" #. type: Content of: <chapter><section><section><section><para> #: pkgs.dbk:1761 msgid "" -"Descriptions of several porting tools can be found in <xref " -"linkend=\"tools-porting\"/>." +"Descriptions of several porting tools can be found in <xref linkend=\"tools-" +"porting\"/>." msgstr "" #. type: Content of: <chapter><section><section><section><title> @@ -2362,11 +2340,11 @@ msgstr "" msgid "" "The <systemitem role=\"package\">wanna-build</systemitem> system is used as " "a distributed, client-server build distribution system. It is usually used " -"in conjunction with build daemons running the <systemitem " -"role=\"package\">buildd</systemitem> program. <literal>Build " -"daemons</literal> are ``slave'' hosts which contact the central <systemitem " -"role=\"package\">wanna-build</systemitem> system to receive a list of " -"packages that need to be built." +"in conjunction with build daemons running the <systemitem role=\"package" +"\">buildd</systemitem> program. <literal>Build daemons</literal> are " +"``slave'' hosts which contact the central <systemitem role=\"package\">wanna-" +"build</systemitem> system to receive a list of packages that need to be " +"built." msgstr "" #. type: Content of: <chapter><section><section><section><para> @@ -2384,11 +2362,10 @@ msgstr "" #. type: Content of: <chapter><section><section><section><para> #: pkgs.dbk:1786 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 <ulink url=\"&url-buildd;\"></ulink>. " -"This data includes nightly updated statistics, queueing information and logs " -"for build attempts." +"Most of the data produced by <systemitem role=\"package\">wanna-build</" +"systemitem> which is generally useful to porters is available on the web at " +"<ulink url=\"&url-buildd;\"></ulink>. This data includes nightly updated " +"statistics, queueing information and logs for build attempts." msgstr "" #. type: Content of: <chapter><section><section><section><para> @@ -2405,9 +2382,9 @@ msgstr "" #: pkgs.dbk:1799 msgid "" "The wanna-build team, in charge of the buildds, can be reached at " -"<literal>debian-wb-team@lists.debian.org</literal>. To determine who " -"(wanna-build team, release team) and how (mail, BTS) to contact, refer to " -"<ulink url=\"&url-wb-team;\"></ulink>." +"<literal>debian-wb-team@lists.debian.org</literal>. To determine who (wanna-" +"build team, release team) and how (mail, BTS) to contact, refer to <ulink " +"url=\"&url-wb-team;\"></ulink>." msgstr "" #. type: Content of: <chapter><section><section><section><para> @@ -2427,10 +2404,10 @@ msgstr "" 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 " -"within a reasonable amount of time. An example is a package that is " -"SVGA-specific (only available for <literal>i386</literal> and " -"<literal>amd64</literal>), or uses other hardware-specific features not " -"supported on all architectures." +"within a reasonable amount of time. An example is a package that is SVGA-" +"specific (only available for <literal>i386</literal> and <literal>amd64</" +"literal>), or uses other hardware-specific features not supported on all " +"architectures." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -2567,13 +2544,13 @@ msgstr "" #. type: Content of: <chapter><section><section><para> #: pkgs.dbk:1934 msgid "" -"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\"><filename>debian/README.source</filename></ulink>." +"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" +"\"><filename>debian/README.source</filename></ulink>." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -2613,12 +2590,12 @@ msgstr "" msgid "" "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." +"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> @@ -2669,11 +2646,11 @@ msgstr "" msgid "" "If the package is a native package (without a Debian revision in the version " "number), 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</literal>, then an NMU would " -"get version <literal>1.5+nmu1</literal>." +"<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</literal>, then an NMU would get version " +"<literal>1.5+nmu1</literal>." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -2692,9 +2669,9 @@ msgstr "" #: pkgs.dbk:2030 msgid "" "In both cases, if the last upload was also an NMU, the counter should be " -"increased. For example, 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>." +"increased. For example, 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>." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -2713,22 +2690,21 @@ msgstr "" msgid "" "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 Lenny (Debian 5.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+deb50u1</literal>, whereas a security NMU to Squeeze would " -"get version <literal>1.5-3+deb60u1</literal>. After the release of Squeeze, " -"security uploads to the <literal>testing</literal> distribution will be " -"versioned <literal>+deb61uZ</literal>, until it is known whether that " -"release will be Debian 6.1 or Debian 7.0 (if that becomes the case, uploads " -"will be versioned as <literal>+deb70uZ</literal>)." +"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 Lenny (Debian 5.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+deb50u1</literal>, whereas a security NMU " +"to Squeeze would get version <literal>1.5-3+deb60u1</literal>. After the " +"release of Squeeze, security uploads to the <literal>testing</literal> " +"distribution will be versioned <literal>+deb61uZ</literal>, until it is " +"known whether that release will be Debian 6.1 or Debian 7.0 (if that becomes " +"the case, uploads will be versioned as <literal>+deb70uZ</literal>)." msgstr "" #. type: Content of: <chapter><section><section><title> @@ -2741,13 +2717,13 @@ msgstr "" msgid "" "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." +"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> @@ -2820,9 +2796,8 @@ msgstr "" msgid "" "BinNMUs are usually triggered on the buildds by wanna-build. An entry is " "added to <filename>debian/changelog</filename>, 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." +"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> @@ -2830,8 +2805,8 @@ msgstr "" msgid "" "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 " -"<filename>debian/changelog</filename>." +"normally called NMU, and they don't add an entry to <filename>debian/" +"changelog</filename>." msgstr "" #. type: Content of: <chapter><section><section><title> @@ -2898,9 +2873,9 @@ msgid "" "but you don't want to add yourself to <literal>Uploaders</literal> because " "you do not plan to contribute regularly to this specific package. If it " "conforms with your team's policy, you can perform a normal upload without " -"being listed directly as <literal>Maintainer</literal> or " -"<literal>Uploader</literal>. In that case, you should start your changelog " -"entry with the following line:" +"being listed directly as <literal>Maintainer</literal> or <literal>Uploader</" +"literal>. In that case, you should start your changelog entry with the " +"following line:" msgstr "" #. type: Content of: <chapter><section><section><screen> @@ -2921,8 +2896,8 @@ msgid "" "maintenance duties by several people. This collaboration is almost always a " "good idea, since it generally results in higher quality and faster bug fix " "turnaround times. It is strongly recommended that packages with a priority " -"of <literal>standard</literal> or which are part of the base set have " -"co-maintainers." +"of <literal>standard</literal> or which are part of the base set have co-" +"maintainers." msgstr "" #. type: Content of: <chapter><section><para> @@ -2930,10 +2905,10 @@ msgstr "" 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 " -"<literal>Maintainer</literal> field of the " -"<filename>debian/control</filename> file. Co-maintainers are all the other " -"maintainers, usually listed in the <literal>Uploaders</literal> field of the " -"<filename>debian/control</filename> file." +"<literal>Maintainer</literal> field of the <filename>debian/control</" +"filename> file. Co-maintainers are all the other maintainers, usually " +"listed in the <literal>Uploaders</literal> field of the <filename>debian/" +"control</filename> file." msgstr "" #. type: Content of: <chapter><section><para> @@ -2948,9 +2923,9 @@ msgstr "" 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 " -"control system, such as <literal>CVS</literal> or " -"<literal>Subversion</literal>. Alioth (see <xref linkend=\"alioth\"/>) " -"provides such tools, amongst others." +"control system, such as <literal>CVS</literal> or <literal>Subversion</" +"literal>. Alioth (see <xref linkend=\"alioth\"/>) provides such tools, " +"amongst others." msgstr "" #. type: Content of: <chapter><section><itemizedlist><listitem><para> @@ -2964,9 +2939,7 @@ msgstr "" #. type: Content of: <chapter><section><itemizedlist><listitem><screen> #: pkgs.dbk:2255 #, no-wrap -msgid "" -"Uploaders: John Buzz <jbuzz@debian.org>, Adam Rex " -"<arex@debian.org>\n" +msgid "Uploaders: John Buzz <jbuzz@debian.org>, Adam Rex <arex@debian.org>\n" msgstr "" #. type: Content of: <chapter><section><itemizedlist><listitem><para> @@ -3012,10 +2985,10 @@ msgid "" "really care for, and creates a false sense of good maintenance. For the same " "reason, team members do not need to add themselves to the " "<literal>Uploaders</literal> field just because they are uploading the " -"package once, they can do a “Team upload” (see <xref " -"linkend=\"nmu-team-upload\"/>). Conversely, it it a bad idea to keep a " -"package with only the mailing list address as a " -"<literal>Maintainer</literal> and no <literal>Uploaders</literal>." +"package once, they can do a “Team upload” (see <xref linkend=\"nmu-team-" +"upload\"/>). Conversely, it is a bad idea to keep a package with only the " +"mailing list address as a <literal>Maintainer</literal> and no " +"<literal>Uploaders</literal>." msgstr "" #. type: Content of: <chapter><section><title> @@ -3032,18 +3005,18 @@ msgstr "" #: pkgs.dbk:2308 msgid "" "Packages are usually installed into the <literal>testing</literal> " -"distribution after they have undergone some degree of " -"<literal>testing</literal> in <literal>unstable</literal>." +"distribution after they have undergone some degree of <literal>testing</" +"literal> in <literal>unstable</literal>." msgstr "" #. type: Content of: <chapter><section><section><para> #: pkgs.dbk:2313 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-critical bugs at the time they're installed into " -"<literal>testing</literal>. This way, <literal>testing</literal> should " -"always be close to being a release candidate. Please see below for details." +"make them uninstallable; they also have to have generally no known release-" +"critical bugs at the time they're installed into <literal>testing</" +"literal>. This way, <literal>testing</literal> should always be close to " +"being a release candidate. Please see below for details." msgstr "" #. type: Content of: <chapter><section><section><title> @@ -3107,20 +3080,20 @@ msgstr "" #: pkgs.dbk:2368 msgid "" "The packages on which it depends must either be available in " -"<literal>testing</literal> or they must be accepted into " -"<literal>testing</literal> at the same time (and they will be if they " -"fulfill all the necessary criteria)." +"<literal>testing</literal> or they must be accepted into <literal>testing</" +"literal> at the same time (and they will be if they fulfill all the " +"necessary criteria)." msgstr "" #. type: Content of: <chapter><section><section><para> #: pkgs.dbk:2376 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=\"&url-testing-maint;\">web page of the testing distribution</ulink>, or " -"use the program <command>grep-excuses</command> which is in the <systemitem " -"role=\"package\">devscripts</systemitem> package. This utility can easily " -"be used in a <citerefentry> <refentrytitle>crontab</refentrytitle> " +"or not, see the <literal>testing</literal> script output on the <ulink url=" +"\"&url-testing-maint;\">web page of the testing distribution</ulink>, or use " +"the program <command>grep-excuses</command> which is in the <systemitem role=" +"\"package\">devscripts</systemitem> package. This utility can easily be " +"used in a <citerefentry> <refentrytitle>crontab</refentrytitle> " "<manvolnum>5</manvolnum> </citerefentry> to keep yourself informed of the " "progression of your packages into <literal>testing</literal>." msgstr "" @@ -3146,9 +3119,9 @@ msgstr "" #. type: Content of: <chapter><section><section><para> #: pkgs.dbk:2399 msgid "" -"Some further dependency analysis is shown on <ulink " -"url=\"http://release.debian.org/migration/\"></ulink> — but be warned, this " -"page also shows build dependencies which are not considered by britney." +"Some further dependency analysis is shown on <ulink url=\"http://release." +"debian.org/migration/\"></ulink> — but be warned, this page also shows build " +"dependencies which are not considered by britney." msgstr "" #. type: Content of: <chapter><section><section><section><title> @@ -3163,10 +3136,9 @@ msgid "" "For the <literal>testing</literal> migration script, outdated means: There " "are different versions in <literal>unstable</literal> for the release " "architectures (except for the architectures in fuckedarches; fuckedarches is " -"a list of architectures that don't keep up (in " -"<filename>update_out.py</filename>), but currently, it's empty). outdated " -"has nothing whatsoever to do with the architectures this package has in " -"<literal>testing</literal>." +"a list of architectures that don't keep up (in <filename>update_out.py</" +"filename>), but currently, it's empty). outdated has nothing whatsoever to " +"do with the architectures this package has in <literal>testing</literal>." msgstr "" #. type: Content of: <chapter><section><section><section><para> @@ -3212,11 +3184,11 @@ msgstr "" #. type: Content of: <chapter><section><section><section><para> #: pkgs.dbk:2441 msgid "" -"The package is out of date on <literal>alpha</literal> in " -"<literal>unstable</literal>, and will not go to " -"<literal>testing</literal>. Removing the package would not help at all, the " -"package is still out of date on <literal>alpha</literal>, and will not " -"propagate to <literal>testing</literal>." +"The package is out of date on <literal>alpha</literal> in <literal>unstable</" +"literal>, and will not go to <literal>testing</literal>. Removing the " +"package would not help at all, the package is still out of date on " +"<literal>alpha</literal>, and will not propagate to <literal>testing</" +"literal>." msgstr "" #. type: Content of: <chapter><section><section><section><para> @@ -3258,8 +3230,8 @@ 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 " "every other sense. Suppose e.g. that <literal>a</literal> cannot be " -"installed with the new version of <literal>b</literal>; then " -"<literal>a</literal> may be removed to allow <literal>b</literal> in." +"installed with the new version of <literal>b</literal>; then <literal>a</" +"literal> may be removed to allow <literal>b</literal> in." msgstr "" #. type: Content of: <chapter><section><section><section><para> @@ -3287,8 +3259,8 @@ msgstr "" #: pkgs.dbk:2512 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</literal>, and vice versa." +"<literal>a</literal> depends on the new version of package <literal>b</" +"literal>, and vice versa." msgstr "" #. type: Content of: <chapter><section><section><section><para> @@ -3410,18 +3382,18 @@ msgstr "" #. type: Content of: <chapter><section><section><section><para> #: pkgs.dbk:2599 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/testing/update_out</filename> to see a setup with a " -"smaller packages file). Via web, it's at <ulink " -"url=\"http://&ftp-master-host;/testing/update_out_code/\"></ulink>." +"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/" +"testing/update_out</filename> to see a setup with a smaller packages file). " +"Via web, it's at <ulink url=\"http://&ftp-master-host;/testing/" +"update_out_code/\"></ulink>." msgstr "" #. type: Content of: <chapter><section><section><section><para> #: pkgs.dbk:2606 msgid "" -"The hints are available via <ulink " -"url=\"http://&ftp-master-host;/testing/hints/\"></ulink>." +"The hints are available via <ulink url=\"http://&ftp-master-host;/testing/" +"hints/\"></ulink>." msgstr "" #. type: Content of: <chapter><section><section><title> @@ -3467,9 +3439,8 @@ msgstr "" msgid "" "Version numbers are usually selected by adding the codename of the " "<literal>testing</literal> distribution and a running number, like " -"<literal>1.2squeeze1</literal> for the first upload through " -"<literal>testing-proposed-updates</literal> of package version " -"<literal>1.2</literal>." +"<literal>1.2squeeze1</literal> for the first upload through <literal>testing-" +"proposed-updates</literal> of package version <literal>1.2</literal>." msgstr "" #. type: Content of: <chapter><section><section><para> @@ -3480,9 +3451,8 @@ msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> #: pkgs.dbk:2651 msgid "" -"Make sure that your package really needs to go through " -"<literal>testing-proposed-updates</literal>, and can't go through " -"<literal>unstable</literal>;" +"Make sure that your package really needs to go through <literal>testing-" +"proposed-updates</literal>, and can't go through <literal>unstable</literal>;" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> @@ -3492,21 +3462,22 @@ msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> #: pkgs.dbk:2663 -msgid "Make sure that you included an appropriate explanation in the changelog;" +msgid "" +"Make sure that you included an appropriate explanation in the changelog;" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> #: pkgs.dbk:2668 msgid "" -"Make sure that you've written <literal>testing</literal> or " -"<literal>testing-proposed-updates</literal> into your target distribution;" +"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:2674 msgid "" -"Make sure that you've built and tested your package in " -"<literal>testing</literal>, not in <literal>unstable</literal>;" +"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> @@ -3537,9 +3508,9 @@ msgstr "" #. type: Content of: <chapter><section><section><section><para> #: pkgs.dbk:2699 msgid "" -"All bugs of some higher severities are by default considered " -"release-critical; currently, these are <literal>critical</literal>, " -"<literal>grave</literal> and <literal>serious</literal> bugs." +"All bugs of some higher severities are by default considered release-" +"critical; currently, these are <literal>critical</literal>, <literal>grave</" +"literal> and <literal>serious</literal> bugs." msgstr "" #. type: Content of: <chapter><section><section><section><para> @@ -3556,10 +3527,10 @@ msgstr "" #: pkgs.dbk:2711 msgid "" "The <literal>unstable</literal> bug count are all release-critical bugs " -"which are marked to apply to " -"<replaceable>package</replaceable>/<replaceable>version</replaceable> " -"combinations that are available in unstable for a release architecture. The " -"<literal>testing</literal> bug count is defined analogously." +"which are marked to apply to <replaceable>package</replaceable>/" +"<replaceable>version</replaceable> combinations that are available in " +"unstable for a release architecture. The <literal>testing</literal> bug " +"count is defined analogously." msgstr "" #. type: Content of: <chapter><section><section><section><title> @@ -3575,10 +3546,9 @@ 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 " "the source package <literal>acmefoo</literal> is installed into " -"<literal>testing</literal>, along with its binary packages " -"<literal>acme-foo-bin</literal>, <literal>acme-bar-bin</literal>, " -"<literal>libacme-foo1</literal> and <literal>libacme-foo-dev</literal>, the " -"old version is removed." +"<literal>testing</literal>, along with its binary packages <literal>acme-foo-" +"bin</literal>, <literal>acme-bar-bin</literal>, <literal>libacme-foo1</" +"literal> and <literal>libacme-foo-dev</literal>, the old version is removed." msgstr "" #. type: Content of: <chapter><section><section><section><para>