X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=po4a%2Fpo%2Fpkgs.pot;h=8a34e92fce8309356300c9f0d2f8038f6b63a6a4;hb=dd09147814be411e5c238732230be88cf2f54dd4;hp=a77945983880b7448bfa6fd33b24940cea271ea3;hpb=bafa67a2c7b794d78396cf18f8d8e44d3160e3ac;p=developers-reference.git diff --git a/po4a/po/pkgs.pot b/po4a/po/pkgs.pot index a779459..8a34e92 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-05-06 17:34-0400\n" +"POT-Creation-Date: 2011-09-10 17:44-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 @@ -95,12 +96,12 @@ msgstr "" #: pkgs.dbk:57 msgid "" "When closing security bugs include CVE numbers as well as the " -"<literal>Closes: #<replaceable>nnnnn</replaceable></literal> This is useful " -"for the security team to track vulnerabilities. If an upload is made to fix " -"the bug before the advisory ID is known, it is encouraged to modify the " -"historical changelog entry with the next upload. Even in this case, please " -"include all available pointers to background information in the original " -"changelog entry." +"<literal>Closes: #<replaceable>nnnnn</replaceable></literal>. This is " +"useful for the security team to track vulnerabilities. If an upload is made " +"to fix the bug before the advisory ID is known, it is encouraged to modify " +"the historical changelog entry with the next upload. Even in this case, " +"please include all available pointers to background information in the " +"original changelog entry." msgstr "" #. type: Content of: <chapter><section><para> @@ -202,7 +203,7 @@ msgstr "" #. type: Content of: <chapter><section><screen> #: pkgs.dbk:138 #, no-wrap -msgid " * new upstream version\n" +msgid " * New upstream release.\n" msgstr "" #. type: Content of: <chapter><section><para> @@ -256,7 +257,8 @@ msgstr "" #: 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> @@ -322,12 +324,12 @@ msgstr "" #: pkgs.dbk:232 msgid "" "For the native packages, the source package includes a Debian source control " -"file (<literal>.dsc</literal>) and the source tarball " -"(<literal>.tar.{gz,bz2,lzma}</literal>). A source package of a non-native " +"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 " -"(<literal>.orig.tar.{gz,bz2,lzma}</literal>) and the Debian changes " -"(<literal>.diff.gz</literal> for the source format “1.0” or " -"<literal>.debian.tar.{gz,bz2,lzma}</literal> for the source format “3.0 " +"(<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 "" @@ -376,9 +378,9 @@ msgstr "" #: pkgs.dbk:270 msgid "" "Please notice that, in non-native packages, permissions on files that are " -"not present in the .orig.tar.{gz,bz2,lzma} will not be preserved, as diff " -"does not store file permissions in the patch. However when using source " -"format “3.0 (quilt)”, permissions of files inside the " +"not present in the <filename>*.orig.tar.{gz,bz2,lzma}</filename> will not be " +"preserved, as diff does not store file permissions in the patch. However " +"when using source format “3.0 (quilt)”, permissions of files inside the " "<filename>debian</filename> directory are preserved since they are stored in " "a tar archive." msgstr "" @@ -1159,14 +1161,22 @@ msgstr "" msgid "" "When you become aware of a security-related bug in a Debian package, whether " "or not you are the maintainer, collect pertinent information about the " -"problem, and promptly contact the security team at &email-security-team; as " -"soon as possible. <emphasis role=\"strong\">DO NOT UPLOAD</emphasis> any " -"packages for <literal>stable</literal> without contacting the team. Useful " -"information includes, for example:" +"problem, and promptly contact the security team, preferably by filing a " +"ticket in their Request Tracker. See <ulink " +"url=\"http://wiki.debian.org/rt.debian.org#Security_Team\"></ulink>. " +"Alternatively you may email &email-security-team;. <emphasis " +"role=\"strong\">DO NOT UPLOAD</emphasis> any packages for " +"<literal>stable</literal> without contacting the team. Useful information " +"includes, for example:" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:852 +#: pkgs.dbk:855 +msgid "Whether or not the bug is already public." +msgstr "" + +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:860 msgid "" "Which versions of the package are known to be affected by the bug. Check " "each version that is present in a supported Debian release, as well as " @@ -1174,34 +1184,34 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:859 +#: pkgs.dbk:867 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 +#: pkgs.dbk:872 msgid "" "Any fixed packages that you have prepared yourself (send only the " -"<literal>.diff.gz</literal> and <literal>.dsc</literal> files and read <xref " -"linkend=\"bug-security-building\"/> first)" +"<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> -#: pkgs.dbk:871 +#: pkgs.dbk:879 msgid "" "Any assistance you can provide to help with testing (exploits, regression " "testing, etc.)" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:877 +#: pkgs.dbk:885 msgid "" "Any information needed for the advisory (see <xref " "linkend=\"bug-security-advisories\"/>)" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:882 +#: pkgs.dbk:890 msgid "" "As the maintainer of the package, you have the responsibility to maintain " "it, even in the stable release. You are in the best position to evaluate " @@ -1210,12 +1220,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:888 +#: pkgs.dbk:896 msgid "The Security Tracker" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:890 +#: pkgs.dbk:898 msgid "" "The security team maintains a central database, the <ulink " "url=\"http://security-tracker.debian.org/\">Debian Security " @@ -1226,7 +1236,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:898 +#: pkgs.dbk:906 msgid "" "You can search it for a specific issue, but also on package name. Look for " "your package to see which issues are still open. If you can, please provide " @@ -1235,12 +1245,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:906 +#: pkgs.dbk:914 msgid "Confidentiality" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:908 +#: pkgs.dbk:916 msgid "" "Unlike most other activities within Debian, information about security " "issues must sometimes be kept private for a time. This allows software " @@ -1251,27 +1261,27 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:915 +#: pkgs.dbk:923 msgid "There are several ways developers can learn of a security problem:" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:920 +#: pkgs.dbk:928 msgid "they notice it on a public forum (mailing list, web site, etc.)" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:925 +#: pkgs.dbk:933 msgid "someone files a bug report" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:930 +#: pkgs.dbk:938 msgid "someone informs them via private email" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:935 +#: pkgs.dbk:943 msgid "" "In the first two cases, the information is public and it is important to " "have a fix as soon as possible. In the last case, however, it might not be " @@ -1280,14 +1290,14 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:943 +#: pkgs.dbk:951 msgid "" "If the security exposure is minor, there is sometimes no need to keep the " "problem a secret and a fix should be made and released." msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:949 +#: pkgs.dbk:957 msgid "" "If the problem is severe, it is preferable to share the information with " "other vendors and coordinate a release. The security team keeps in contact " @@ -1295,7 +1305,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:956 +#: pkgs.dbk:964 msgid "" "In all cases if the person who reports the problem asks that it not be " "disclosed, such requests should be honored, with the obvious exception of " @@ -1305,17 +1315,17 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:963 +#: pkgs.dbk:971 msgid "" "Please note that if secrecy is needed you may not upload a fix to " -"<literal>unstable</literal> (or anywhere else, such as a public CVS " +"<literal>unstable</literal> (or anywhere else, such as a public VCS " "repository). It is not sufficient to obfuscate the details of the change, " "as the code itself is public, and can (and will) be examined by the general " "public." msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:970 +#: pkgs.dbk:978 msgid "" "There are two reasons for releasing information even though secrecy is " "requested: the problem has been known for a while, or the problem or exploit " @@ -1323,7 +1333,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:975 +#: pkgs.dbk:983 msgid "" "The Security Team has a PGP-key to enable encrypted communication about " "sensitive issues. See the <ulink " @@ -1332,12 +1342,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:981 +#: pkgs.dbk:989 msgid "Security Advisories" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:983 +#: pkgs.dbk:991 msgid "" "Security advisories are only issued for the current, released stable " "distribution, and <emphasis>not</emphasis> for <literal>testing</literal> or " @@ -1351,59 +1361,59 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:996 +#: pkgs.dbk:1004 msgid "A description of the problem and its scope, including:" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:1001 +#: pkgs.dbk:1009 msgid "The type of problem (privilege escalation, denial of service, etc.)" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:1006 +#: pkgs.dbk:1014 msgid "What privileges may be gained, and by whom (if any)" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:1011 +#: pkgs.dbk:1019 msgid "How it can be exploited" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:1016 +#: pkgs.dbk:1024 msgid "Whether it is remotely or locally exploitable" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:1021 +#: pkgs.dbk:1029 msgid "How the problem was fixed" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1026 +#: pkgs.dbk:1034 msgid "This information allows users to assess the threat to their systems." msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1031 +#: pkgs.dbk:1039 msgid "Version numbers of affected packages" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1036 +#: pkgs.dbk:1044 msgid "Version numbers of fixed packages" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1041 +#: pkgs.dbk:1049 msgid "" "Information on where to obtain the updated packages (usually from the Debian " "security archive)" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1047 +#: pkgs.dbk:1055 msgid "" "References to upstream advisories, <ulink " "url=\"http://cve.mitre.org\">CVE</ulink> identifiers, and any other " @@ -1411,12 +1421,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1056 +#: pkgs.dbk:1064 msgid "Preparing packages to address security issues" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1058 +#: pkgs.dbk:1066 msgid "" "One way that you can assist the security team in their duties is to provide " "them with fixed packages suitable for a security advisory for the stable " @@ -1424,7 +1434,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1063 +#: pkgs.dbk:1071 msgid "" "When an update is made to the stable release, care must be taken to avoid " "changing system behavior or introducing new bugs. In order to do this, make " @@ -1435,7 +1445,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1071 +#: pkgs.dbk:1079 msgid "" "This means that moving to a new upstream version is not a good solution. " "Instead, the relevant changes should be back-ported to the version present " @@ -1445,7 +1455,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1077 +#: pkgs.dbk:1085 msgid "" "In some cases, it is not possible to back-port a security fix, for example " "when large amounts of source code need to be modified or rewritten. If this " @@ -1455,7 +1465,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1084 +#: pkgs.dbk:1092 msgid "" "Related to this is another important guideline: always test your changes. " "If you have an exploit available, try it and see if it indeed succeeds on " @@ -1465,7 +1475,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1091 +#: pkgs.dbk:1099 msgid "" "Do <emphasis role=\"strong\">NOT</emphasis> include any changes in your " "package which are not directly related to fixing the vulnerability. These " @@ -1478,7 +1488,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1101 +#: pkgs.dbk:1109 msgid "" "Review and test your changes as much as possible. Check the differences " "from the previous version repeatedly (<command>interdiff</command> from the " @@ -1489,12 +1499,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1109 +#: pkgs.dbk:1117 msgid "Be sure to verify the following items:" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1114 +#: pkgs.dbk:1122 msgid "" "<emphasis role=\"strong\">Target the right distribution</emphasis> in your " "<filename>debian/changelog</filename>. For <literal>stable</literal> this " @@ -1506,12 +1516,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1125 +#: pkgs.dbk:1133 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 +#: pkgs.dbk:1138 msgid "" "Make descriptive, meaningful changelog entries. Others will rely on them to " "determine whether a particular bug was fixed. Add " @@ -1524,7 +1534,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1141 +#: pkgs.dbk:1149 msgid "" "Make sure the <emphasis role=\"strong\">version number</emphasis> is " "proper. It must be greater than the current package, but less than package " @@ -1538,19 +1548,19 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1154 +#: pkgs.dbk:1162 msgid "" -"Unless the upstream source has been uploaded to <literal>security.debian.org " -"</literal> before (by a previous security update), build the upload " -"<emphasis role=\"strong\">with full upstream source</emphasis> " -"(<literal>dpkg-buildpackage -sa</literal>). If there has been a previous " -"upload to <literal>security.debian.org</literal> with the same upstream " -"version, you may upload without upstream source (<literal>dpkg-buildpackage " -"-sd</literal>)." +"Unless the upstream source has been uploaded to " +"<literal>security.debian.org</literal> before (by a previous security " +"update), build the upload <emphasis role=\"strong\">with full upstream " +"source</emphasis> (<literal>dpkg-buildpackage -sa</literal>). If there has " +"been a previous upload to <literal>security.debian.org</literal> with the " +"same upstream version, you may upload without upstream source " +"(<literal>dpkg-buildpackage -sd</literal>)." msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1164 +#: pkgs.dbk:1173 msgid "" "Be sure to use the <emphasis role=\"strong\">exact same " "<filename>*.orig.tar.{gz,bz2,lzma}</filename></emphasis> as used in the " @@ -1559,7 +1569,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1172 +#: pkgs.dbk:1181 msgid "" "Build the package on a <emphasis role=\"strong\">clean system</emphasis> " "which only has packages installed from the distribution you are building " @@ -1569,12 +1579,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1183 +#: pkgs.dbk:1192 msgid "Uploading the fixed package" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1185 +#: pkgs.dbk:1194 msgid "" "Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security " "upload queue (<literal>oldstable-security</literal>, " @@ -1585,7 +1595,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1192 +#: pkgs.dbk:1201 msgid "" "Do <emphasis role=\"strong\">NOT</emphasis> upload your fix to " "<literal>proposed-updates</literal> without coordinating with the security " @@ -1598,7 +1608,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1202 +#: pkgs.dbk:1211 msgid "" "Once you have created and tested the new package and it has been approved by " "the security team, it needs to be uploaded so that it can be installed in " @@ -1607,7 +1617,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1208 +#: pkgs.dbk:1217 msgid "" "Once an upload to the security queue has been accepted, the package will " "automatically be built for all architectures and stored for verification by " @@ -1615,7 +1625,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1213 +#: pkgs.dbk:1222 msgid "" "Uploads which are waiting for acceptance or verification are only accessible " "by the security team. This is necessary since there might be fixes for " @@ -1623,7 +1633,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1218 +#: pkgs.dbk:1227 msgid "" "If a member of the security team accepts a package, it will be installed on " "<literal>security.debian.org</literal> as well as proposed for the proper " @@ -1632,12 +1642,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><title> -#: pkgs.dbk:1230 +#: pkgs.dbk:1239 msgid "Moving, removing, renaming, adopting, and orphaning packages" msgstr "" #. type: Content of: <chapter><section><para> -#: pkgs.dbk:1232 +#: pkgs.dbk:1241 msgid "" "Some archive manipulation operations are not automated in the Debian upload " "process. These procedures should be manually followed by maintainers. This " @@ -1645,28 +1655,28 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1237 +#: pkgs.dbk:1246 msgid "Moving packages" msgstr "" #. type: Content of: <chapter><section><section><para><footnote><para> -#: pkgs.dbk:1241 +#: pkgs.dbk:1250 msgid "" "See the <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> for " "guidelines on what section a package belongs in." msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1239 +#: pkgs.dbk:1248 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\"/>" +"the <literal>non-free</literal> 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\"/>" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1246 +#: pkgs.dbk:1255 msgid "" "If you need to change the section for one of your packages, change the " "package control information to place the package in the desired section, and " @@ -1680,7 +1690,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1258 +#: pkgs.dbk:1267 msgid "" "If, on the other hand, you need to change the <literal>subsection</literal> " "of one of your packages (e.g., ``devel'', ``admin''), the procedure is " @@ -1690,12 +1700,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1267 +#: pkgs.dbk:1276 msgid "Removing packages" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1269 +#: pkgs.dbk:1278 msgid "" "If for some reason you want to completely remove a package (say, if it is an " "old compatibility library which is no longer required), you need to file a " @@ -1710,11 +1720,11 @@ msgid "" "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." +"<literal>ftp.debian.org</literal> pseudo-package." msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1286 +#: pkgs.dbk:1295 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). " @@ -1726,18 +1736,18 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1295 +#: pkgs.dbk:1304 msgid "" -"Note that removals can only be done for the <literal>unstable </literal>, " -"<literal>experimental</literal> and <literal>stable </literal> " -"distribution. Packages are not removed from <literal>testing</literal> " -"directly. Rather, they will be removed automatically after the package has " -"been removed from <literal>unstable</literal> and no package in " -"<literal>testing </literal> depends on it." +"Note that removals can only be done for the <literal>unstable</literal>, " +"<literal>experimental</literal> and <literal>stable</literal> distribution. " +"Packages are not removed from <literal>testing</literal> directly. Rather, " +"they will be removed automatically after the package has been removed from " +"<literal>unstable</literal> and no package in <literal>testing</literal> " +"depends on it." msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1304 +#: pkgs.dbk:1313 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 " @@ -1749,7 +1759,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1313 +#: pkgs.dbk:1322 msgid "" "In your removal request, you have to detail the reasons justifying the " "request. This is to avoid unwanted removals and to keep a trace of why a " @@ -1758,7 +1768,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1319 +#: pkgs.dbk:1328 msgid "" "Usually you only ask for the removal of a package maintained by yourself. " "If you want to remove another package, you have to get the approval of its " @@ -1771,7 +1781,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1329 +#: pkgs.dbk:1338 msgid "" "Further information relating to these and other package removal related " "topics may be found at <ulink " @@ -1780,7 +1790,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1334 +#: pkgs.dbk:1343 msgid "" "If in doubt concerning whether a package is disposable, email " "&email-debian-devel; asking for opinions. Also of interest is the " @@ -1788,8 +1798,8 @@ msgid "" "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 <literal>apt-cache " -"rdepends</literal>, <command>apt-rdepends</command>, " +"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 " @@ -1797,7 +1807,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1347 +#: pkgs.dbk:1356 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 " @@ -1811,12 +1821,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1358 +#: pkgs.dbk:1367 msgid "Removing packages from <filename>Incoming</filename>" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1360 +#: pkgs.dbk:1369 msgid "" "In the past, it was possible to remove packages from " "<filename>incoming</filename>. However, with the introduction of the new " @@ -1830,30 +1840,30 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1375 +#: pkgs.dbk:1384 msgid "Replacing or renaming packages" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1377 +#: pkgs.dbk:1386 msgid "" "When the upstream maintainers for one of your packages chose to rename their " "software (or you made a mistake naming your package), you should follow a " "two-step process to rename it. In the first step, change the " "<filename>debian/control</filename> file to reflect the new name and to " "replace, provide and conflict with the obsolete package name (see the <ulink " -"url=\"&url-debian-policy;\"> Debian Policy Manual</ulink> for details). " +"url=\"&url-debian-policy;\">Debian Policy Manual</ulink> for details). " "Please note that you should only add a <literal>Provides</literal> relation " "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." +"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." msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1393 +#: pkgs.dbk:1402 msgid "" "At other times, you may make a mistake in constructing your package and wish " "to replace it. The only way to do this is to increase the version number " @@ -1869,12 +1879,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1408 +#: pkgs.dbk:1417 msgid "Orphaning a package" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1410 +#: pkgs.dbk:1419 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 " @@ -1892,7 +1902,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1425 +#: pkgs.dbk:1434 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 " @@ -1903,17 +1913,17 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1433 +#: pkgs.dbk:1442 msgid "More information is on the <ulink url=\"&url-wnpp;\">WNPP web pages</ulink>." msgstr "" #. type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1439 +#: pkgs.dbk:1448 msgid "Adopting a package" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1441 +#: pkgs.dbk:1450 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 " @@ -1923,7 +1933,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1448 +#: pkgs.dbk:1457 msgid "" "It is not OK to simply take over a package that you feel is neglected — that " "would be package hijacking. You can, of course, contact the current " @@ -1933,7 +1943,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1454 +#: pkgs.dbk:1463 msgid "" "Generally, you may not take over the package without the assent of the " "current maintainer. Even if they ignore you, that is still not grounds to " @@ -1946,12 +1956,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1464 +#: pkgs.dbk:1473 msgid "" "If you take over an old package, you probably want to be listed as the " "package's official maintainer in the bug system. This will happen " "automatically once you upload a new version with an updated " -"<literal>Maintainer:</literal> field, although it can take a few hours after " +"<literal>Maintainer</literal> field, although it can take a few hours after " "the upload is done. If you do not expect to upload a new version for a " "while, you can use <xref linkend=\"pkg-tracking-system\"/> to get the bug " "reports. However, make sure that the old maintainer has no problem with the " @@ -1959,12 +1969,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><title> -#: pkgs.dbk:1478 +#: pkgs.dbk:1487 msgid "Porting and being ported" msgstr "" #. type: Content of: <chapter><section><para> -#: pkgs.dbk:1480 +#: pkgs.dbk:1489 msgid "" "Debian supports an ever-increasing number of architectures. Even if you are " "not a porter, and you don't use any architecture but one, it is part of your " @@ -1973,24 +1983,24 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><para> -#: pkgs.dbk:1486 +#: pkgs.dbk:1495 msgid "" "Porting is the act of building Debian packages for architectures that are " "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 " +"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> -#: pkgs.dbk:1495 +#: pkgs.dbk:1504 msgid "Being kind to porters" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1497 +#: pkgs.dbk:1506 msgid "" "Porters have a difficult and unique task, since they are required to deal " "with a large volume of packages. Ideally, every source package should build " @@ -2001,7 +2011,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1505 +#: pkgs.dbk:1514 msgid "" "The first and most important thing is to respond quickly to bug or issues " "raised by porters. Please treat porters with courtesy, as if they were in " @@ -2011,7 +2021,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1512 +#: pkgs.dbk:1521 msgid "" "By far, most of the problems encountered by porters are caused by " "<emphasis>packaging bugs</emphasis> in the source packages. Here is a " @@ -2019,7 +2029,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1519 +#: pkgs.dbk:1528 msgid "" "Make sure that your <literal>Build-Depends</literal> and " "<literal>Build-Depends-Indep</literal> settings in " @@ -2037,21 +2047,21 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1534 +#: pkgs.dbk:1543 msgid "" "If you can't set up a proper chroot, <command>dpkg-depcheck</command> may be " "of assistance (see <xref linkend=\"dpkg-depcheck\"/>)." msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1538 +#: pkgs.dbk:1547 msgid "" "See the <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> for " "instructions on setting build dependencies." msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1544 +#: pkgs.dbk:1553 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, " @@ -2062,7 +2072,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1554 +#: pkgs.dbk:1563 msgid "" "Make sure your source package is correct. Do <literal>dpkg-source -x " "<replaceable>package</replaceable>.dsc</literal> to make sure your source " @@ -2071,7 +2081,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1562 +#: pkgs.dbk:1571 msgid "" "Make sure you don't ship your source package with the " "<filename>debian/files</filename> or <filename>debian/substvars</filename> " @@ -2080,7 +2090,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1570 +#: pkgs.dbk:1579 msgid "" "Make sure you don't rely on locally installed or hacked configurations or " "programs. For instance, you should never be calling programs in " @@ -2090,7 +2100,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1579 +#: pkgs.dbk:1588 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, " @@ -2099,7 +2109,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1587 +#: pkgs.dbk:1596 msgid "" "Don't rely on the compiler being a certain version, if possible. If not, " "then make sure your build dependencies reflect the restrictions, although " @@ -2108,22 +2118,23 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1595 +#: pkgs.dbk:1604 msgid "" -"Make sure your debian/rules contains separate <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>." +"Make sure your <filename>debian/rules</filename> contains separate " +"<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>." msgstr "" #. type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1606 +#: pkgs.dbk:1615 msgid "Guidelines for porter uploads" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1608 +#: pkgs.dbk:1617 msgid "" "If the package builds out of the box for the architecture to be ported to, " "you are in luck and your job is easy. This section applies to that case; it " @@ -2134,7 +2145,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1616 +#: pkgs.dbk:1625 msgid "" "For a porter upload, no changes are being made to the source. You do not " "need to touch any of the files in the source package. This includes " @@ -2142,7 +2153,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1621 +#: pkgs.dbk:1630 msgid "" "The way to invoke <command>dpkg-buildpackage</command> is as " "<literal>dpkg-buildpackage -B " @@ -2150,11 +2161,11 @@ msgid "" "<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>." +"<filename>debian/rules</filename>." msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1630 +#: pkgs.dbk:1639 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 " @@ -2164,12 +2175,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1637 +#: pkgs.dbk:1646 msgid "Recompilation or binary-only NMU" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1639 +#: pkgs.dbk:1648 msgid "" "Sometimes the initial porter upload is problematic because the environment " "in which the package was built was not good enough (outdated or obsolete " @@ -2181,17 +2192,17 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1648 +#: pkgs.dbk:1657 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>." +"generated using dpkg's substitution variable " +"<literal>$(Source-Version)</literal>." msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1655 +#: pkgs.dbk:1663 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 " @@ -2199,7 +2210,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1660 +#: pkgs.dbk:1668 msgid "" "Such recompilations require special ``magic'' version numbering, so that the " "archive maintenance tools recognize that, even though there is a new Debian " @@ -2209,7 +2220,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para><footnote><para> -#: pkgs.dbk:1675 +#: pkgs.dbk:1683 msgid "" "In the past, such NMUs used the third-level number on the Debian part of the " "revision to denote their recompilation-only status; however, this syntax was " @@ -2219,21 +2230,21 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1667 +#: pkgs.dbk:1675 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\"/>" +"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\"/>" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1683 +#: pkgs.dbk:1691 msgid "" "Similar to initial porter uploads, the correct way of invoking " "<command>dpkg-buildpackage</command> is <literal>dpkg-buildpackage " @@ -2241,15 +2252,15 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1690 +#: pkgs.dbk:1698 msgid "When to do a source NMU if you are a porter" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1692 +#: pkgs.dbk:1700 msgid "" "Porters doing a source NMU generally follow the guidelines found in <xref " -"linkend=\"nmu\"/> , just like non-porters. However, it is expected that the " +"linkend=\"nmu\"/>, just like non-porters. However, it is expected that the " "wait cycle for a porter's source NMU is smaller than for a non-porter, since " "porters have to cope with a large quantity of packages. Again, the " "situation varies depending on the distribution they are uploading to. It " @@ -2259,7 +2270,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1701 +#: pkgs.dbk:1709 msgid "" "If you are a porter doing an NMU for <literal>unstable</literal>, the above " "guidelines for porting should be followed, with two variations. Firstly, " @@ -2269,12 +2280,12 @@ msgid "" "shortened if the problem is critical and imposes hardship on the porting " "effort, at the discretion of the porter group. (Remember, none of this is " "Policy, just mutually agreed upon guidelines.) For uploads to " -"<literal>stable</literal> or <literal>testing </literal>, please coordinate " +"<literal>stable</literal> or <literal>testing</literal>, please coordinate " "with the appropriate release team first." msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1713 +#: pkgs.dbk:1721 msgid "" "Secondly, porters doing source NMUs should make sure that the bug they " "submit to the BTS should be of severity <literal>serious</literal> or " @@ -2285,7 +2296,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1721 +#: pkgs.dbk:1729 msgid "" "Porters should try to avoid patches which simply kludge around bugs in the " "current version of the compile environment, kernel, or libc. Sometimes such " @@ -2296,7 +2307,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1729 +#: pkgs.dbk:1737 msgid "" "Porters may also have an unofficial location where they can put the results " "of their work during the waiting period. This helps others running the port " @@ -2305,12 +2316,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1739 +#: pkgs.dbk:1747 msgid "Porting infrastructure and automation" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1741 +#: pkgs.dbk:1749 msgid "" "There is infrastructure and several tools to help automate package porting. " "This section contains a brief overview of this automation and porting to " @@ -2319,19 +2330,19 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1746 +#: pkgs.dbk:1754 msgid "Mailing lists and web pages" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1748 +#: pkgs.dbk:1756 msgid "" "Web pages containing the status of each port can be found at <ulink " "url=\"&url-debian-ports;\"></ulink>." msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1752 +#: pkgs.dbk:1760 msgid "" "Each port of Debian has a mailing list. The list of porting mailing lists " "can be found at <ulink url=\"&url-debian-port-lists;\"></ulink>. These " @@ -2340,36 +2351,36 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1760 +#: pkgs.dbk:1768 msgid "Porter tools" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1762 +#: pkgs.dbk:1770 msgid "" "Descriptions of several porting tools can be found in <xref " "linkend=\"tools-porting\"/>." msgstr "" #. type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1768 +#: pkgs.dbk:1776 msgid "<systemitem role=\"package\">wanna-build</systemitem>" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1770 +#: pkgs.dbk:1778 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 " +"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 " +"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> -#: pkgs.dbk:1778 +#: pkgs.dbk:1786 msgid "" "<systemitem role=\"package\">wanna-build</systemitem> is not yet available " "as a package; however, all Debian porting efforts are using it for automated " @@ -2381,16 +2392,17 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1787 +#: pkgs.dbk:1795 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> -#: pkgs.dbk:1793 +#: pkgs.dbk:1801 msgid "" "We are quite proud of this system, since it has so many possible uses. " "Independent development groups can use the system for different sub-flavors " @@ -2400,7 +2412,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1800 +#: pkgs.dbk:1808 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 " @@ -2409,19 +2421,19 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1807 +#: pkgs.dbk:1815 msgid "" "When requesting binNMUs or give-backs (retries after a failed build), please " "use the format described at <ulink url=\"&url-release-wb;\"/>." msgstr "" #. type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1816 +#: pkgs.dbk:1824 msgid "When your package is <emphasis>not</emphasis> portable" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1818 +#: pkgs.dbk:1826 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 " @@ -2432,14 +2444,14 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1825 +#: pkgs.dbk:1833 msgid "" "In order to prevent broken packages from being uploaded to the archive, and " "wasting buildd time, you need to do a few things:" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1831 +#: pkgs.dbk:1839 msgid "" "First, make sure your package <emphasis>does</emphasis> fail to build on " "architectures that it cannot support. There are a few ways to achieve " @@ -2451,7 +2463,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1839 +#: pkgs.dbk:1847 msgid "" "Additionally, if you believe the list of supported architectures is pretty " "constant, you should change <literal>any</literal> to a list of supported " @@ -2460,34 +2472,69 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1847 +#: pkgs.dbk:1855 msgid "" "In order to prevent autobuilders from needlessly trying to build your " -"package, it must be included in <filename>packages-arch-specific</filename>, " +"package, it must be included in <filename>Packages-arch-specific</filename>, " "a list used by the <command>wanna-build</command> script. The current " "version is available as <ulink url=\"&url-buildd-p-a-s;\"/>; please see the " "top of the file for whom to contact for changes." msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1856 +#: pkgs.dbk:1864 msgid "" "Please note that it is insufficient to only add your package to " -"Packages-arch-specific without making it fail to build on unsupported " -"architectures: A porter or any other person trying to build your package " -"might accidently upload it without noticing it doesn't work. If in the past " -"some binary packages were uploaded on unsupported architectures, request " -"their removal by filing a bug against <systemitem " -"role=\"package\">ftp.debian.org</systemitem>" +"<filename>Packages-arch-specific</filename> without making it fail to build " +"on unsupported architectures: A porter or any other person trying to build " +"your package might accidently upload it without noticing it doesn't work. " +"If in the past some binary packages were uploaded on unsupported " +"architectures, request their removal by filing a bug against <systemitem " +"role=\"package\">ftp.debian.org</systemitem>." +msgstr "" + +#. type: Content of: <chapter><section><section><title> +#: pkgs.dbk:1875 +msgid "Marking non-free packages as auto-buildable" +msgstr "" + +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:1877 +msgid "" +"By default packages from the <literal>non-free</literal> section are not " +"built by the autobuilder network (mostly because the license of the packages " +"could disapprove). To enable a package to be build you need to perform the " +"following steps:" +msgstr "" + +#. type: Content of: <chapter><section><section><orderedlist><listitem><para> +#: pkgs.dbk:1885 +msgid "" +"Check whether it is legally allowed and technically possible to auto-build " +"the package;" +msgstr "" + +#. type: Content of: <chapter><section><section><orderedlist><listitem><para> +#: pkgs.dbk:1891 +msgid "" +"Add <literal>XS-Autobuild: yes</literal> into the header part of " +"<filename>debian/control</filename>;" +msgstr "" + +#. type: Content of: <chapter><section><section><orderedlist><listitem><para> +#: pkgs.dbk:1897 +msgid "" +"Send an email to &email-nonfree-release; and explain why the package can " +"legitimately and technically be auto-built." msgstr "" #. type: Content of: <chapter><section><title> -#: pkgs.dbk:1869 +#: pkgs.dbk:1906 msgid "Non-Maintainer Uploads (NMUs)" msgstr "" #. type: Content of: <chapter><section><para> -#: pkgs.dbk:1871 +#: pkgs.dbk:1908 msgid "" "Every package has one or more maintainers. Normally, these are the people " "who work on and upload new versions of the package. In some situations, it " @@ -2498,24 +2545,24 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1880 +#: pkgs.dbk:1917 msgid "When and how to do an NMU" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1883 +#: pkgs.dbk:1920 msgid "Before doing an NMU, consider the following questions:" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1888 +#: pkgs.dbk:1925 msgid "" "Does your NMU really fix bugs? Fixing cosmetic issues or changing the " "packaging style in NMUs is discouraged." msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1894 +#: pkgs.dbk:1931 msgid "" "Did you give enough time to the maintainer? When was the bug reported to the " "BTS? Being busy for a week or two isn't unusual. Is the bug so severe that " @@ -2523,7 +2570,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1901 +#: pkgs.dbk:1938 msgid "" "How confident are you about your changes? Please remember the Hippocratic " "Oath: \"Above all, do no harm.\" It is better to leave a package with an " @@ -2534,7 +2581,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1911 +#: pkgs.dbk:1948 msgid "" "Have you clearly expressed your intention to NMU, at least in the BTS? It is " "also a good idea to try to contact the maintainer by other means (private " @@ -2542,7 +2589,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1918 +#: pkgs.dbk:1955 msgid "" "If the maintainer is usually active and responsive, have you tried to " "contact him? In general it should be considered preferable that a maintainer " @@ -2553,16 +2600,17 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1928 +#: pkgs.dbk:1965 msgid "" "When doing an NMU, you must first make sure that your intention to NMU is " "clear. Then, you must send a patch with the differences between the current " -"package and your proposed NMU to the BTS. The <literal>nmudiff</literal> " -"script in the <literal>devscripts</literal> package might be helpful." +"package and your proposed NMU to the BTS. The <command>nmudiff</command> " +"script in the <systemitem role=\"package\">devscripts</systemitem> package " +"might be helpful." msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1935 +#: pkgs.dbk:1972 msgid "" "While preparing the patch, you should better be aware of any " "package-specific practices that the maintainer might be using. Taking them " @@ -2570,11 +2618,11 @@ msgid "" "the normal package workflow and thus increases the possibilities that that " "will happen. A good place where to look for for possible package-specific " "practices is <ulink " -"url=\"&url-debian-policy;ch-source.html#s-readmesource\"><literal>debian/README.source</literal></ulink>." +"url=\"&url-debian-policy;ch-source.html#s-readmesource\"><filename>debian/README.source</filename></ulink>." msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1943 +#: pkgs.dbk:1980 msgid "" "Unless you have an excellent reason not to do so, you must then give some " "time to the maintainer to react (for example, by uploading to the " @@ -2583,22 +2631,30 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1950 +#: pkgs.dbk:1987 +msgid "" +"Upload fixing only release-critical bugs older than 7 days, with no " +"maintainer activity on the bug for 7 days and no indication that a fix is in " +"progress: 0 days" +msgstr "" + +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:1992 msgid "Upload fixing only release-critical bugs older than 7 days: 2 days" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1955 +#: pkgs.dbk:1997 msgid "Upload fixing only release-critical and important bugs: 5 days" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1960 +#: pkgs.dbk:2002 msgid "Other NMUs: 10 days" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1966 +#: pkgs.dbk:2008 msgid "" "Those delays are only examples. In some cases, such as uploads fixing " "security issues, or fixes for trivial bugs that blocking a transition, it is " @@ -2606,7 +2662,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1972 +#: pkgs.dbk:2014 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 " @@ -2619,7 +2675,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1982 +#: pkgs.dbk:2024 msgid "" "After you upload an NMU, you are responsible for the possible problems that " "you might have introduced. You must keep an eye on the package (subscribing " @@ -2627,7 +2683,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1988 +#: pkgs.dbk:2030 msgid "" "This is not a license to perform NMUs thoughtlessly. If you NMU when it is " "clear that the maintainers are active and would have acknowledged a patch in " @@ -2637,34 +2693,34 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1998 -msgid "NMUs and debian/changelog" +#: pkgs.dbk:2040 +msgid "NMUs and <filename>debian/changelog</filename>" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2000 +#: pkgs.dbk:2042 msgid "" "Just like any other (source) upload, NMUs must add an entry to " -"<literal>debian/changelog</literal>, telling what has changed with this " +"<filename>debian/changelog</filename>, telling what has changed with this " "upload. The first line of this entry must explicitely mention that this " "upload is an NMU, e.g.:" msgstr "" #. type: Content of: <chapter><section><section><screen> -#: pkgs.dbk:2005 +#: pkgs.dbk:2047 #, no-wrap msgid " * Non-maintainer upload.\n" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2009 +#: pkgs.dbk:2051 msgid "The way to version NMUs differs for native and non-native packages." msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2012 +#: pkgs.dbk:2054 msgid "" -"If the package is a native package (without a debian revision in the version " +"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>. " @@ -2674,19 +2730,19 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2022 +#: pkgs.dbk:2064 msgid "" "If the package is a not a native package, you should add a minor version " -"number to the debian revision part of the version number (the portion after " -"the last hyphen). This extra number must start at 1. For example, if the " -"current version is <literal>1.5-2</literal>, then an NMU would get version " -"<literal>1.5-2.1</literal>. If a new upstream version is packaged in the " -"NMU, the debian revision is set to <literal>0</literal>, for example " -"<literal>1.6-0.1</literal>." +"number to the Debian revision part of the version number (the portion after " +"the last hyphen). This extra number must start at <literal>1</literal>. For " +"example, if the current version is <literal>1.5-2</literal>, then an NMU " +"would get version <literal>1.5-2.1</literal>. If a new upstream version is " +"packaged in the NMU, the Debian revision is set to <literal>0</literal>, for " +"example <literal>1.6-0.1</literal>." msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2031 +#: pkgs.dbk:2073 msgid "" "In both cases, if the last upload was also an NMU, the counter should be " "increased. For example, if the current version is " @@ -2695,7 +2751,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2037 +#: pkgs.dbk:2079 msgid "" "A special versioning scheme is needed to avoid disrupting the maintainer's " "work, since using an integer for the Debian revision will potentially " @@ -2706,7 +2762,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2047 +#: pkgs.dbk:2089 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 " @@ -2718,23 +2774,23 @@ msgid "" "When the release number is not yet known (often the case for " "<literal>testing</literal>, at the beginning of release cycles), the lowest " "release number higher than the last stable release number must be used. For " -"example, while Etch (Debian 4.0) is stable, a security NMU to stable for a " +"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+deb40u1</literal>, whereas a security NMU to Lenny would get " -"version <literal>1.5-3+deb50u1</literal>. After the release of Lenny, " +"<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>+deb51uZ</literal>, until it is known whether that " -"release will be Debian 5.1 or Debian 6.0 (if that becomes the case, uploads " -"will be versioned as <literal>+deb60uZ</literal>." +"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> -#: pkgs.dbk:2069 +#: pkgs.dbk:2111 msgid "Using the <literal>DELAYED/</literal> queue" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2072 +#: pkgs.dbk:2114 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 " @@ -2748,7 +2804,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2086 +#: pkgs.dbk:2128 msgid "" "The <literal>DELAYED</literal> queue should not be used to put additional " "pressure on the maintainer. In particular, it's important that you are " @@ -2757,7 +2813,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2093 +#: pkgs.dbk:2135 msgid "" "If you make an NMU to <literal>DELAYED</literal> and the maintainer updates " "his package before the delay expires, your upload will be rejected because a " @@ -2767,12 +2823,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2103 +#: pkgs.dbk:2145 msgid "NMUs from the maintainer's point of view" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2106 +#: pkgs.dbk:2148 msgid "" "When someone NMUs your package, this means they want to help you to keep it " "in good shape. This gives users fixed packages faster. You can consider " @@ -2782,7 +2838,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2115 +#: pkgs.dbk:2157 msgid "" "To acknowledge an NMU, include its changes and changelog entry in your next " "maintainer upload. If you do not acknowledge the NMU by including the NMU " @@ -2791,12 +2847,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2124 +#: pkgs.dbk:2166 msgid "Source NMUs vs Binary-only NMUs (binNMUs)" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2127 +#: pkgs.dbk:2169 msgid "" "The full name of an NMU is <emphasis>source NMU</emphasis>. There is also " "another type, namely the <emphasis>binary-only NMU</emphasis>, or " @@ -2805,7 +2861,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2134 +#: pkgs.dbk:2176 msgid "" "When a library (or other dependency) is updated, the packages using it may " "need to be rebuilt. Since no changes to the source are needed, the same " @@ -2813,30 +2869,31 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2140 +#: pkgs.dbk:2182 msgid "" "BinNMUs are usually triggered on the buildds by wanna-build. An entry is " -"added to debian/changelog, explaining why the upload was needed and " -"increasing the version number as described in <xref " +"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." msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2148 +#: pkgs.dbk:2190 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 debian/changelog." +"normally called NMU, and they don't add an entry to " +"<filename>debian/changelog</filename>." msgstr "" #. type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2156 +#: pkgs.dbk:2198 msgid "NMUs vs QA uploads" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2159 +#: pkgs.dbk:2201 msgid "" "NMUs are uploads of packages by somebody else than their assigned " "maintainer. There is another type of upload where the uploaded package is " @@ -2844,23 +2901,23 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2166 +#: pkgs.dbk:2208 msgid "" "QA uploads are very much like normal maintainer uploads: they may fix " "anything, even minor issues; the version numbering is normal, and there is " "no need to use a delayed upload. The difference is that you are not listed " -"as the Maintainer or Uploader for the package. Also, the changelog entry of " -"a QA upload has a special first line:" +"as the <literal>Maintainer</literal> or <literal>Uploader</literal> for the " +"package. Also, the changelog entry of a QA upload has a special first line:" msgstr "" #. type: Content of: <chapter><section><section><screen> -#: pkgs.dbk:2174 +#: pkgs.dbk:2216 #, no-wrap msgid " * QA upload.\n" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2178 +#: pkgs.dbk:2220 msgid "" "If you want to do an NMU, and it seems that the maintainer is not active, it " "is wise to check if the package is orphaned (this information is displayed " @@ -2872,7 +2929,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2189 +#: pkgs.dbk:2231 msgid "" "Instead of doing a QA upload, you can also consider adopting the package by " "making yourself the maintainer. You don't need permission from anybody to " @@ -2881,41 +2938,48 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2198 +#: pkgs.dbk:2240 msgid "NMUs vs team uploads" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2201 +#: pkgs.dbk:2243 msgid "" "Sometimes you are fixing and/or updating a package because you are member of " -"a packaging team (which uses a mailing list as Maintainer or Uploader, see " -"<xref linkend=\"collaborative-maint\"/>) but you don't want to add yourself " -"to Uploaders 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 Maintainer or Uploader. In " -"that case, you should start your changelog entry with the following line: " -"<code> * Team upload.</code>." +"a packaging team (which uses a mailing list as <literal>Maintainer</literal> " +"or <literal>Uploader</literal>, see <xref linkend=\"collaborative-maint\"/>) " +"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:" +msgstr "" + +#. type: Content of: <chapter><section><section><screen> +#: pkgs.dbk:2253 +#, no-wrap +msgid " * Team upload.\n" msgstr "" #. type: Content of: <chapter><section><title> -#: pkgs.dbk:2215 +#: pkgs.dbk:2261 msgid "Collaborative maintenance" msgstr "" #. type: Content of: <chapter><section><para> -#: pkgs.dbk:2217 +#: pkgs.dbk:2263 msgid "" "Collaborative maintenance is a term describing the sharing of Debian package " "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 " +"of <literal>standard</literal> or which are part of the base set have " "co-maintainers." msgstr "" #. type: Content of: <chapter><section><para> -#: pkgs.dbk:2225 +#: pkgs.dbk:2271 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 " @@ -2926,24 +2990,24 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><para> -#: pkgs.dbk:2233 +#: pkgs.dbk:2279 msgid "" "In its most basic form, the process of adding a new co-maintainer is quite " "easy:" msgstr "" #. type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:2239 +#: pkgs.dbk:2285 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 <command>CVS</command> or " -"<command>Subversion</command>. Alioth (see <xref linkend=\"alioth\"/>) " +"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> -#: pkgs.dbk:2247 +#: pkgs.dbk:2293 msgid "" "Add the co-maintainer's correct maintainer name and address to the " "<literal>Uploaders</literal> field in the first paragraph of the " @@ -2951,7 +3015,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><itemizedlist><listitem><screen> -#: pkgs.dbk:2252 +#: pkgs.dbk:2298 #, no-wrap msgid "" "Uploaders: John Buzz <jbuzz@debian.org>, Adam Rex " @@ -2959,64 +3023,66 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:2257 +#: pkgs.dbk:2303 msgid "" "Using the PTS (<xref linkend=\"pkg-tracking-system\"/>), the co-maintainers " "should subscribe themselves to the appropriate source package." msgstr "" #. type: Content of: <chapter><section><para> -#: pkgs.dbk:2263 +#: pkgs.dbk:2309 msgid "" "Another form of collaborative maintenance is team maintenance, which is " "recommended if you maintain several packages with the same group of " -"developers. In that case, the Maintainer and Uploaders field of each " -"package must be managed with care. It is recommended to choose between one " -"of the two following schemes:" +"developers. In that case, the <literal>Maintainer</literal> and " +"<literal>Uploaders</literal> field of each package must be managed with " +"care. It is recommended to choose between one of the two following schemes:" msgstr "" #. type: Content of: <chapter><section><orderedlist><listitem><para> -#: pkgs.dbk:2272 +#: pkgs.dbk:2318 msgid "" -"Put the team member mainly responsible for the package in the Maintainer " -"field. In the Uploaders, put the mailing list address, and the team members " -"who care for the package." +"Put the team member mainly responsible for the package in the " +"<literal>Maintainer</literal> field. In the <literal>Uploaders</literal>, " +"put the mailing list address, and the team members who care for the package." msgstr "" #. type: Content of: <chapter><section><orderedlist><listitem><para> -#: pkgs.dbk:2279 +#: pkgs.dbk:2325 msgid "" -"Put the mailing list address in the Maintainer field. In the Uploaders " -"field, put the team members who care for the package. In this case, you " -"must make sure the mailing list accept bug reports without any human " -"interaction (like moderation for non-subscribers)." +"Put the mailing list address in the <literal>Maintainer</literal> field. In " +"the <literal>Uploaders</literal> field, put the team members who care for " +"the package. In this case, you must make sure the mailing list accept bug " +"reports without any human interaction (like moderation for non-subscribers)." msgstr "" #. type: Content of: <chapter><section><para> -#: pkgs.dbk:2288 +#: pkgs.dbk:2334 msgid "" "In any case, it is a bad idea to automatically put all team members in the " -"Uploaders field. It clutters the Developer's Package Overview listing (see " -"<xref linkend=\"ddpo\"/>) with packages one doesn't 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 Uploaders 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 Maintainer and no Uploaders." +"<literal>Uploaders</literal> field. It clutters the Developer's Package " +"Overview listing (see <xref linkend=\"ddpo\"/>) with packages one doesn't " +"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 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> -#: pkgs.dbk:2301 +#: pkgs.dbk:2347 msgid "The testing distribution" msgstr "" #. type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2303 +#: pkgs.dbk:2349 msgid "Basics" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2305 +#: pkgs.dbk:2351 msgid "" "Packages are usually installed into the <literal>testing</literal> " "distribution after they have undergone some degree of " @@ -3024,22 +3090,22 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2310 +#: pkgs.dbk:2356 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." +"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> -#: pkgs.dbk:2319 +#: pkgs.dbk:2365 msgid "Updates from unstable" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2321 +#: pkgs.dbk:2367 msgid "" "The scripts that update the <literal>testing</literal> distribution are run " "twice each day, right after the installation of the updated packages; these " @@ -3050,14 +3116,14 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2329 +#: pkgs.dbk:2375 msgid "" "The inclusion of a package from <literal>unstable</literal> is conditional " "on the following:" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2335 +#: pkgs.dbk:2381 msgid "" "The package must have been available in <literal>unstable</literal> for 2, 5 " "or 10 days, depending on the urgency (high, medium or low). Please note " @@ -3068,7 +3134,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2345 +#: pkgs.dbk:2391 msgid "" "It must not have new release-critical bugs (RC bugs affecting the version " "available in <literal>unstable</literal>, but not affecting the version in " @@ -3076,31 +3142,31 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2352 +#: pkgs.dbk:2398 msgid "" "It must be available on all architectures on which it has previously been " -"built in <literal>unstable</literal>. <xref linkend=\"dak-ls\"/> may be of " -"interest to check that information;" +"built in <literal>unstable</literal>. <link linkend=\"dak-ls\">dak ls</link> " +"may be of interest to check that information;" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2359 +#: pkgs.dbk:2405 msgid "" "It must not break any dependency of a package which is already available in " "<literal>testing</literal>;" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2365 +#: pkgs.dbk:2411 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);" +"fulfill all the necessary criteria)." msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2373 +#: pkgs.dbk:2419 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 " @@ -3113,7 +3179,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2384 +#: pkgs.dbk:2430 msgid "" "The <filename>update_excuses</filename> file does not always give the " "precise reason why the package is refused; you may have to find it on your " @@ -3123,15 +3189,15 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2391 +#: pkgs.dbk:2437 msgid "" "Sometimes, some packages never enter <literal>testing</literal> because the " -"set of inter-relationship is too complicated and cannot be sorted out by the " +"set of interrelationship is too complicated and cannot be sorted out by the " "scripts. See below for details." msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2396 +#: pkgs.dbk:2442 msgid "" "Some further dependency analysis is shown on <ulink " "url=\"http://release.debian.org/migration/\"></ulink> — but be warned, this " @@ -3139,13 +3205,13 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2401 -msgid "out-of-date" +#: pkgs.dbk:2447 +msgid "Out-of-date" msgstr "" #. FIXME: better rename this file than document rampant professionalism? #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2404 +#: pkgs.dbk:2450 msgid "" "For the <literal>testing</literal> migration script, outdated means: There " "are different versions in <literal>unstable</literal> for the release " @@ -3157,68 +3223,69 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2412 +#: pkgs.dbk:2458 msgid "Consider this example:" msgstr "" #. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2419 pkgs.dbk:2452 +#: pkgs.dbk:2465 pkgs.dbk:2498 msgid "alpha" msgstr "" #. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2420 pkgs.dbk:2453 +#: pkgs.dbk:2466 pkgs.dbk:2499 msgid "arm" msgstr "" #. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2425 pkgs.dbk:2459 pkgs.dbk:2521 +#: pkgs.dbk:2471 pkgs.dbk:2505 pkgs.dbk:2567 msgid "testing" msgstr "" #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2426 pkgs.dbk:2431 pkgs.dbk:2460 pkgs.dbk:2461 pkgs.dbk:2468 +#: pkgs.dbk:2472 pkgs.dbk:2477 pkgs.dbk:2506 pkgs.dbk:2507 pkgs.dbk:2514 msgid "1" msgstr "" #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2427 pkgs.dbk:2462 pkgs.dbk:2467 +#: pkgs.dbk:2473 pkgs.dbk:2508 pkgs.dbk:2513 msgid "-" msgstr "" #. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2430 pkgs.dbk:2465 pkgs.dbk:2522 +#: pkgs.dbk:2476 pkgs.dbk:2511 pkgs.dbk:2568 msgid "unstable" msgstr "" #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2432 pkgs.dbk:2466 +#: pkgs.dbk:2478 pkgs.dbk:2512 msgid "2" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2438 +#: pkgs.dbk:2484 msgid "" -"The package is out of date on alpha in <literal>unstable</literal>, and will " -"not go to <literal>testing</literal>. Removing the package would not help at " -"all, the package is still out of date on <literal>alpha</literal>, and will " -"not propagate to testing." +"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> -#: pkgs.dbk:2444 +#: pkgs.dbk:2490 msgid "" "However, if ftp-master removes a package in <literal>unstable</literal> " "(here on <literal>arm</literal>):" msgstr "" #. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2454 +#: pkgs.dbk:2500 msgid "hurd-i386" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2474 +#: pkgs.dbk:2520 msgid "" "In this case, the package is up to date on all release architectures in " "<literal>unstable</literal> (and the extra <literal>hurd-i386</literal> " @@ -3226,7 +3293,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2479 +#: pkgs.dbk:2525 msgid "" "Sometimes, the question is raised if it is possible to allow packages in " "that are not yet built on all architectures: No. Just plainly no. (Except " @@ -3234,12 +3301,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2486 +#: pkgs.dbk:2532 msgid "Removals from testing" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2488 +#: pkgs.dbk:2534 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 " @@ -3249,15 +3316,15 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2495 +#: pkgs.dbk:2541 msgid "" -"Of course, there is another reason to remove a package from <literal>testing " -"</literal>: It's just too buggy (and having a single RC-bug is enough to be " -"in this state)." +"Of course, there is another reason to remove a package from " +"<literal>testing</literal>: It's just too buggy (and having a single RC-bug " +"is enough to be in this state)." msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2500 +#: pkgs.dbk:2546 msgid "" "Furthermore, if a package has been removed from <literal>unstable</literal>, " "and no package in <literal>testing</literal> depends on it any more, then it " @@ -3265,12 +3332,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2507 -msgid "circular dependencies" +#: pkgs.dbk:2553 +msgid "Circular dependencies" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2509 +#: pkgs.dbk:2555 msgid "" "A situation which is not handled very well by britney is if package " "<literal>a</literal> depends on the new version of package " @@ -3278,49 +3345,49 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2514 +#: pkgs.dbk:2560 msgid "An example of this is:" msgstr "" #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2527 +#: pkgs.dbk:2573 msgid "a" msgstr "" #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2528 +#: pkgs.dbk:2574 msgid "1; depends: b=1" msgstr "" #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2529 +#: pkgs.dbk:2575 msgid "2; depends: b=2" msgstr "" #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2532 +#: pkgs.dbk:2578 msgid "b" msgstr "" #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2533 +#: pkgs.dbk:2579 msgid "1; depends: a=1" msgstr "" #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2534 +#: pkgs.dbk:2580 msgid "2; depends: a=2" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2540 +#: pkgs.dbk:2586 msgid "" "Neither package <literal>a</literal> nor package <literal>b</literal> is " "considered for update." msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2544 +#: pkgs.dbk:2590 msgid "" "Currently, this requires some manual hinting from the release team. Please " "contact them by sending mail to &email-debian-release; if this happens to " @@ -3328,46 +3395,46 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2551 -msgid "influence of package in testing" +#: pkgs.dbk:2597 +msgid "Influence of package in testing" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2553 +#: pkgs.dbk:2599 msgid "" -"Generally, there is nothing that the status of a package in <literal>testing " -"</literal> means for transition of the next version from <literal>unstable " -"</literal> to <literal>testing</literal>, with two exceptions: If the " -"RC-bugginess of the package goes down, it may go in even if it is still " -"RC-buggy. The second exception is if the version of the package in " -"<literal> testing</literal> is out of sync on the different arches: Then any " -"arch might just upgrade to the version of the source package; however, this " -"can happen only if the package was previously forced through, the arch is in " -"fuckedarches, or there was no binary package of that arch present in " -"<literal>unstable </literal> at all during the <literal>testing</literal> " -"migration." +"Generally, there is nothing that the status of a package in " +"<literal>testing</literal> means for transition of the next version from " +"<literal>unstable</literal> to <literal>testing</literal>, with two " +"exceptions: If the RC-bugginess of the package goes down, it may go in even " +"if it is still RC-buggy. The second exception is if the version of the " +"package in <literal>testing</literal> is out of sync on the different " +"arches: Then any arch might just upgrade to the version of the source " +"package; however, this can happen only if the package was previously forced " +"through, the arch is in fuckedarches, or there was no binary package of that " +"arch present in <literal>unstable</literal> at all during the " +"<literal>testing</literal> migration." msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2565 +#: pkgs.dbk:2611 msgid "" -"In summary this means: The only influence that a package being in <literal> " -"testing</literal> has on a new version of the same package is that the new " -"version might go in easier." +"In summary this means: The only influence that a package being in " +"<literal>testing</literal> has on a new version of the same package is that " +"the new version might go in easier." msgstr "" #. type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2572 -msgid "details" +#: pkgs.dbk:2618 +msgid "Details" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2574 +#: pkgs.dbk:2620 msgid "If you are interested in details, this is how britney works:" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2577 +#: pkgs.dbk:2623 msgid "" "The packages are looked at to determine whether they are valid candidates. " "This gives the update excuses. The most common reasons why a package is not " @@ -3380,52 +3447,50 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2586 +#: pkgs.dbk:2632 msgid "" -"Now, the more complex part happens: Britney tries to update <literal>testing " -"</literal> with the valid candidates. For that, britney tries to add each " -"valid candidate to the testing distribution. If the number of uninstallable " -"packages in <literal>testing</literal> doesn't increase, the package is " -"accepted. From that point on, the accepted package is considered to be part " -"of <literal>testing</literal>, such that all subsequent installability tests " -"include this package. Hints from the release team are processed before or " -"after this main run, depending on the exact type." +"Now, the more complex part happens: Britney tries to update " +"<literal>testing</literal> with the valid candidates. For that, britney " +"tries to add each valid candidate to the testing distribution. If the number " +"of uninstallable packages in <literal>testing</literal> doesn't increase, " +"the package is accepted. From that point on, the accepted package is " +"considered to be part of <literal>testing</literal>, such that all " +"subsequent installability tests include this package. Hints from the " +"release team are processed before or after this main run, depending on the " +"exact type." msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2596 +#: pkgs.dbk:2642 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 <ulink " +"url=\"http://&ftp-master-host;/testing/update_output/\"></ulink>." msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2603 +#: pkgs.dbk:2646 msgid "" "The hints are available via <ulink " "url=\"http://&ftp-master-host;/testing/hints/\"></ulink>." msgstr "" #. type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2611 +#: pkgs.dbk:2654 msgid "Direct updates to testing" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2613 +#: pkgs.dbk:2656 msgid "" "The <literal>testing</literal> distribution is fed with packages from " "<literal>unstable</literal> according to the rules explained above. " "However, in some cases, it is necessary to upload packages built only for " -"<literal> testing</literal>. For that, you may want to upload to <literal> " -"testing-proposed-updates</literal>." +"<literal>testing</literal>. For that, you may want to upload to " +"<literal>testing-proposed-updates</literal>." msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2620 +#: pkgs.dbk:2663 msgid "" "Keep in mind that packages uploaded there are not automatically processed, " "they have to go through the hands of the release manager. So you'd better " @@ -3435,12 +3500,12 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2627 +#: pkgs.dbk:2670 msgid "" "You should not upload to <literal>testing-proposed-updates</literal> when " "you can update your packages through <literal>unstable</literal>. If you " "can't (for example because you have a newer development version in " -"<literal>unstable </literal>), you may use this facility, but it is " +"<literal>unstable</literal>), you may use this facility, but it is " "recommended that you ask for authorization from the release manager first. " "Even if a package is frozen, updates through <literal>unstable</literal> are " "possible, if the upload via <literal>unstable</literal> does not pull in any " @@ -3448,54 +3513,54 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2636 +#: pkgs.dbk:2679 msgid "" "Version numbers are usually selected by adding the codename of the " "<literal>testing</literal> distribution and a running number, like " -"<literal>1.2sarge1</literal> for the first upload through " +"<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> -#: pkgs.dbk:2643 +#: pkgs.dbk:2686 msgid "Please make sure you didn't miss any of these items in your upload:" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2648 +#: pkgs.dbk:2691 msgid "" "Make sure that your package really needs to go through " -"<literal>testing-proposed-updates</literal>, and can't go through <literal> " -"unstable</literal>;" +"<literal>testing-proposed-updates</literal>, and can't go through " +"<literal>unstable</literal>;" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2655 +#: pkgs.dbk:2698 msgid "Make sure that you included only the minimal amount of changes;" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2660 +#: pkgs.dbk:2703 msgid "Make sure that you included an appropriate explanation in the changelog;" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2665 +#: pkgs.dbk:2708 msgid "" "Make sure that you've written <literal>testing</literal> or " "<literal>testing-proposed-updates</literal> into your target distribution;" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2671 +#: pkgs.dbk:2714 msgid "" "Make sure that you've built and tested your package in " "<literal>testing</literal>, not in <literal>unstable</literal>;" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2677 +#: pkgs.dbk:2720 msgid "" "Make sure that your version number is higher than the version in " "<literal>testing</literal> and <literal>testing-proposed-updates</literal>, " @@ -3503,24 +3568,24 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2684 +#: pkgs.dbk:2727 msgid "" "After uploading and successful build on all platforms, contact the release " "team at &email-debian-release; and ask them to approve your upload." msgstr "" #. type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2692 +#: pkgs.dbk:2735 msgid "Frequently asked questions" msgstr "" #. type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2694 +#: pkgs.dbk:2737 msgid "What are release-critical bugs, and how do they get counted?" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2696 +#: pkgs.dbk:2739 msgid "" "All bugs of some higher severities are by default considered " "release-critical; currently, these are <literal>critical</literal>, " @@ -3528,46 +3593,46 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2701 +#: pkgs.dbk:2744 msgid "" "Such bugs are presumed to have an impact on the chances that the package " "will be released with the <literal>stable</literal> release of Debian: in " "general, if a package has open release-critical bugs filed on it, it won't " "get into <literal>testing</literal>, and consequently won't be released in " -"<literal> stable</literal>." +"<literal>stable</literal>." msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2708 +#: pkgs.dbk:2751 msgid "" "The <literal>unstable</literal> bug count are all release-critical bugs " "which are marked to apply to " -"<replaceable>package</replaceable>/<replaceable>version </replaceable> " +"<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> -#: pkgs.dbk:2716 +#: pkgs.dbk:2759 msgid "" "How could installing a package into <literal>testing</literal> possibly " "break other packages?" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2719 +#: pkgs.dbk:2762 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 " +"<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> -#: pkgs.dbk:2727 +#: pkgs.dbk:2770 msgid "" "However, the old version may have provided a binary package with an old " "soname of a library, such as <literal>libacme-foo0</literal>. Removing the " @@ -3576,7 +3641,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2733 +#: pkgs.dbk:2776 msgid "" "Evidently, this mainly affects packages which provide changing sets of " "binary packages in different versions (in turn, mainly libraries). However, " @@ -3585,7 +3650,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2739 +#: pkgs.dbk:2782 msgid "" "When the set of binary packages provided by a source package change in this " "way, all the packages that depended on the old binaries will have to be " @@ -3599,7 +3664,7 @@ msgid "" msgstr "" #. type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2750 +#: pkgs.dbk:2793 msgid "" "If you are having problems with complicated groups of packages like this, " "contact &email-debian-devel; or &email-debian-release; for help."