msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2012-06-09 13:51-0400\n"
+"POT-Creation-Date: 2012-06-28 05:40-0400\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"<emphasis>currently</emphasis> distributing at any point in time. All that "
"can be expected is that it is identical to something that upstream once "
"<emphasis>did</emphasis> distribute. If a difference arises later (say, if "
-"upstream notices that he wasn't using maximal compression in his original "
-"distribution and then re-<command>gzip</command>s it), that's just too bad. "
-"Since there is no good way to upload a new "
+"upstream notice that they weren't using maximal compression in their "
+"original distribution and then re-<command>gzip</command> it), that's just "
+"too bad. Since there is no good way to upload a new "
"<filename>.orig.tar.{gz,bz2,xz}</filename> for the same version, there is "
"not even any point in treating this situation as a bug."
msgstr ""
#: best-pkging-practices.dbk:1690
msgid ""
"In these cases the developer must construct a suitable "
-"<filename>.orig.tar.{gz,bz2,xz}</filename> file himself. We refer to such a "
-"tarball as a repackaged upstream source. Note that a repackaged upstream "
-"source is different from a Debian-native package. A repackaged source still "
-"comes with Debian-specific changes in a separate "
+"<filename>.orig.tar.{gz,bz2,xz}</filename> file themselves. We refer to "
+"such a tarball as a repackaged upstream source. Note that a repackaged "
+"upstream source is different from a Debian-native package. A repackaged "
+"source still comes with Debian-specific changes in a separate "
"<filename>.diff.gz</filename> or "
"<filename>.debian.tar.{gz,bz2,xz}</filename> and still has a version number "
"composed of <replaceable>upstream-version</replaceable> and "
#: best-pkging-practices.dbk:1858
msgid ""
"The long description of the meta-package must clearly document its purpose "
-"so that the user knows what he will lose if he removes the package. Being "
+"so that the user knows what they will lose if they remove the package. Being "
"explicit about the consequences is recommended. This is particularly "
"important for meta-packages which are installed during initial installation "
"and that have not been explicitly installed by the user. Those tend to be "
#. type: Content of: <chapter><section><section><para><orderedlist><listitem><para>
#: beyond-pkging.dbk:349
msgid ""
-"The sponsor reviews the source package. If she finds issues, she informs the "
-"maintainer and asks her to provide a fixed version (the process starts over "
+"The sponsor reviews the source package. If they find issues, they inform the "
+"maintainer and ask them to provide a fixed version (the process starts over "
"at step 1)."
msgstr ""
#. type: Content of: <chapter><section><section><para><orderedlist><listitem><para>
#: beyond-pkging.dbk:354
msgid ""
-"The sponsor could not find any remaining problem. She builds the package, "
-"signs it, and uploads it to Debian."
+"The sponsor could not find any remaining problem. They build the package, "
+"sign it, and upload it to Debian."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: beyond-pkging.dbk:371
msgid ""
"You should also ensure that the prospective maintainer is going to be a good "
-"maintainer. Does she already have some experience with other packages? If "
-"yes, is she doing a good job with them (check out some bugs)? Is she "
-"familiar with the package and its programming language? Does she have the "
-"skills needed for this package? If not, is she able to learn them?"
+"maintainer. Do they already have some experience with other packages? If "
+"yes, are they doing a good job with them (check out some bugs)? Are they "
+"familiar with the package and its programming language? Do they have the "
+"skills needed for this package? If not, are they able to learn them?"
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: beyond-pkging.dbk:379
msgid ""
-"It's also a good idea to know where she stands towards Debian: does she "
-"agree with Debian's philosophy and does she intend to join Debian? Given how "
-"easy it is to become a Debian Maintainer, you might want to only sponsor "
+"It's also a good idea to know where they stand with respect to Debian: do "
+"they agree with Debian's philosophy and do they intend to join Debian? Given "
+"how easy it is to become a Debian Maintainer, you might want to only sponsor "
"people who plan to join. That way you know from the start that you won't "
"have to act as a sponsor indefinitely."
msgstr ""
#: beyond-pkging.dbk:474
msgid ""
"If the audit did not reveal any problem, you can build the package and "
-"upload it to Debian. Remember that even if you're not the maintainer, the "
-"sponsor is still responsible of what he uploaded to Debian. That's why "
+"upload it to Debian. Remember that even if you're not the maintainer, as a "
+"sponsor you are still responsible for what you upload to Debian. That's why "
"you're encouraged to keep up with the package through the <xref "
"linkend=\"pkg-tracking-system\"/>."
msgstr ""
"file. The <literal>Maintainer</literal> field of the "
"<filename>control</filename> file and the <filename>changelog</filename> "
"should list the person who did the packaging, i.e. the sponsoree. That way "
-"she will get all the BTS mail."
+"they will get all the BTS mail."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
"linkend=\"pkg-tracking-system\"/>) to verify if the maintainer has not "
"missed something important. Maybe there are translations updates sitting in "
"the BTS that could have been integrated. Maybe the package has been NMUed "
-"and the maintainer forgot to integrate the changes from the NMU in his "
-"package. Maybe there's a release critical bug that he has left unhandled and "
-"that's blocking migration to <literal>testing</literal>. Whatever. If you "
-"find something that she could have done (better), it's time to tell her so "
-"that she can improve for next time, and so that she has a better "
-"understanding of her responsibilities."
+"and the maintainer forgot to integrate the changes from the NMU into their "
+"package. Maybe there's a release critical bug that they have left unhandled "
+"and that's blocking migration to <literal>testing</literal>. If you find "
+"something that they could have done (better), it's time to tell them so that "
+"they can improve for next time, and so that they have a better understanding "
+"of their responsibilities."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
#: developer-duties.dbk:39
msgid ""
"Most of the package maintainer's work goes into providing updated versions "
-"of packages in <literal>unstable</literal>, but his job also entails taking "
-"care of the packages in the current <literal>stable</literal> release."
+"of packages in <literal>unstable</literal>, but their job also entails "
+"taking care of the packages in the current <literal>stable</literal> "
+"release."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: developer-duties.dbk:79
msgid ""
"Lack of attention to RC bugs is often interpreted by the QA team as a sign "
-"that the maintainer has disappeared without properly orphaning his package. "
-"The MIA team might also get involved, which could result in your packages "
-"being orphaned (see <xref linkend=\"mia-qa\" />)."
+"that the maintainer has disappeared without properly orphaning their "
+"package. The MIA team might also get involved, which could result in your "
+"packages being orphaned (see <xref linkend=\"mia-qa\" />)."
msgstr ""
#. type: Content of: <chapter><section><section><title>
#: l10n.dbk:160
msgid ""
"The best solution may be to mark the bug as forwarded to upstream, and "
-"forward it to both the previous translator and his/her team (using the "
+"forward it to both the previous translator and their team (using the "
"corresponding debian-l10n-XXX mailing list)."
msgstr ""
"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."
+"depends on it. (Removals from <literal>testing</literal> are possible though "
+"by filing a removal bug report against the <systemitem "
+"role=\"package\">&release-debian-org;</systemitem> pseudo-package. See the "
+"section <xref linkend=\"removals\"/>.)"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1315
+#: pkgs.dbk:1318
msgid ""
"There is one exception when an explicit removal request is not necessary: If "
"a (source or binary) package is no longer built from source, it will be "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1324
+#: pkgs.dbk:1327
msgid ""
"In your removal request, you have to detail the reasons justifying the "
"request. This is to avoid unwanted removals and to keep a trace of why a "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1330
+#: pkgs.dbk:1333
msgid ""
"Usually you only ask for the removal of a package maintained by yourself. "
"If you want to remove another package, you have to get the approval of its "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1340
+#: pkgs.dbk:1343
msgid ""
"Further information relating to these and other package removal related "
"topics may be found at <ulink "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1345
+#: pkgs.dbk:1348
msgid ""
"If in doubt concerning whether a package is disposable, email "
"&email-debian-devel; asking for opinions. Also of interest is the "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1358
+#: pkgs.dbk:1361
msgid ""
"Once the package has been removed, the package's bugs should be handled. "
"They should either be reassigned to another package in the case where the "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1369
+#: pkgs.dbk:1372
msgid "Removing packages from <filename>Incoming</filename>"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1371
+#: pkgs.dbk:1374
msgid ""
"In the past, it was possible to remove packages from "
"<filename>incoming</filename>. However, with the introduction of the new "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1386
+#: pkgs.dbk:1389
msgid "Replacing or renaming packages"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1388
+#: pkgs.dbk:1391
msgid ""
"When the upstream maintainers for one of your packages chose to rename their "
"software (or you made a mistake naming your package), you should follow a "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1404
+#: pkgs.dbk:1407
msgid ""
"At other times, you may make a mistake in constructing your package and wish "
"to replace it. The only way to do this is to increase the version number "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1419
+#: pkgs.dbk:1422
msgid "Orphaning a package"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1421
+#: pkgs.dbk:1424
msgid ""
"If you can no longer maintain a package, you need to inform others, and see "
"that the package is marked as orphaned. You should set the package "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1436
+#: pkgs.dbk:1439
msgid ""
"If you just intend to give the package away, but you can keep maintainership "
"for the moment, then you should instead submit a bug against <systemitem "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1444
+#: pkgs.dbk:1447
msgid "More information is on the <ulink url=\"&url-wnpp;\">WNPP web pages</ulink>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1450
+#: pkgs.dbk:1453
msgid "Adopting a package"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1452
+#: pkgs.dbk:1455
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 "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1459
+#: pkgs.dbk:1462
msgid ""
"It is not OK to simply take over a package that you feel is neglected — that "
"would be package hijacking. You can, of course, contact the current "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1465
+#: pkgs.dbk:1468
msgid ""
"Generally, you may not take over the package without the assent of the "
"current maintainer. Even if they ignore you, that is still not grounds to "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1475
+#: pkgs.dbk:1478
msgid ""
"If you take over an old package, you probably want to be listed as the "
"package's official maintainer in the bug system. This will happen "
msgstr ""
#. type: Content of: <chapter><section><title>
-#: pkgs.dbk:1489
+#: pkgs.dbk:1492
msgid "Porting and being ported"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:1491
+#: pkgs.dbk:1494
msgid ""
"Debian supports an ever-increasing number of architectures. Even if you are "
"not a porter, and you don't use any architecture but one, it is part of your "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:1497
+#: pkgs.dbk:1500
msgid ""
"Porting is the act of building Debian packages for architectures that are "
"different from the original architecture of the package maintainer's binary "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1506
+#: pkgs.dbk:1509
msgid "Being kind to porters"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1508
+#: pkgs.dbk:1511
msgid ""
"Porters have a difficult and unique task, since they are required to deal "
"with a large volume of packages. Ideally, every source package should build "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1516
+#: pkgs.dbk:1519
msgid ""
"The first and most important thing is to respond quickly to bug or issues "
"raised by porters. Please treat porters with courtesy, as if they were in "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1523
+#: pkgs.dbk:1526
msgid ""
"By far, most of the problems encountered by porters are caused by "
"<emphasis>packaging bugs</emphasis> in the source packages. Here is a "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1530
+#: pkgs.dbk:1533
msgid ""
"Make sure that your <literal>Build-Depends</literal> and "
"<literal>Build-Depends-Indep</literal> settings in "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1545
+#: pkgs.dbk:1548
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:1549
+#: pkgs.dbk:1552
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:1555
+#: pkgs.dbk:1558
msgid ""
"Don't set architecture to a value other than <literal>all</literal> or "
"<literal>any</literal> unless you really mean it. In too many cases, "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1565
+#: pkgs.dbk:1568
msgid ""
"Make sure your source package is correct. Do <literal>dpkg-source -x "
"<replaceable>package</replaceable>.dsc</literal> to make sure your source "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1573
+#: pkgs.dbk:1576
msgid ""
"Make sure you don't ship your source package with the "
"<filename>debian/files</filename> or <filename>debian/substvars</filename> "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1581
+#: pkgs.dbk:1584
msgid ""
"Make sure you don't rely on locally installed or hacked configurations or "
"programs. For instance, you should never be calling programs in "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1590
+#: pkgs.dbk:1593
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, "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1598
+#: pkgs.dbk:1601
msgid ""
"Don't rely on the compiler being a certain version, if possible. If not, "
"then make sure your build dependencies reflect the restrictions, although "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1606
+#: pkgs.dbk:1609
msgid ""
"Make sure your <filename>debian/rules</filename> contains separate "
"<literal>binary-arch</literal> and <literal>binary-indep</literal> targets, "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1617
+#: pkgs.dbk:1620
msgid "Guidelines for porter uploads"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1619
+#: pkgs.dbk:1622
msgid ""
"If the package builds out of the box for the architecture to be ported to, "
"you are in luck and your job is easy. This section applies to that case; it "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1627
+#: pkgs.dbk:1630
msgid ""
"For a porter upload, no changes are being made to the source. You do not "
"need to touch any of the files in the source package. This includes "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1632
+#: pkgs.dbk:1635
msgid ""
"The way to invoke <command>dpkg-buildpackage</command> is as "
"<literal>dpkg-buildpackage -B "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1641
+#: pkgs.dbk:1644
msgid ""
"If you are working on a Debian machine for your porting efforts and you need "
"to sign your upload locally for its acceptance in the archive, you can run "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1648
+#: pkgs.dbk:1651
msgid "Recompilation or binary-only NMU"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1650
+#: pkgs.dbk:1653
msgid ""
"Sometimes the initial porter upload is problematic because the environment "
"in which the package was built was not good enough (outdated or obsolete "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1659
+#: pkgs.dbk:1662
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 "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1665
+#: pkgs.dbk:1668
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 "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1670
+#: pkgs.dbk:1673
msgid ""
"Such recompilations require special ``magic'' version numbering, so that the "
"archive maintenance tools recognize that, even though there is a new Debian "
msgstr ""
#. type: Content of: <chapter><section><section><section><para><footnote><para>
-#: pkgs.dbk:1685
+#: pkgs.dbk:1688
msgid ""
"In the past, such NMUs used the third-level number on the Debian part of the "
"revision to denote their recompilation-only status; however, this syntax was "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1677
+#: pkgs.dbk:1680
msgid ""
"The ``magic'' for a recompilation-only NMU is triggered by using a suffix "
"appended to the package version number, following the form "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1693
+#: pkgs.dbk:1696
msgid ""
"Similar to initial porter uploads, the correct way of invoking "
"<command>dpkg-buildpackage</command> is <literal>dpkg-buildpackage "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1700
+#: pkgs.dbk:1703
msgid "When to do a source NMU if you are a porter"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1702
+#: pkgs.dbk:1705
msgid ""
"Porters doing a source NMU generally follow the guidelines found in <xref "
"linkend=\"nmu\"/>, just like non-porters. However, it is expected that the "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1711
+#: pkgs.dbk:1714
msgid ""
"If you are a porter doing an NMU for <literal>unstable</literal>, the above "
"guidelines for porting should be followed, with two variations. Firstly, "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1723
+#: pkgs.dbk:1726
msgid ""
"Secondly, porters doing source NMUs should make sure that the bug they "
"submit to the BTS should be of severity <literal>serious</literal> or "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1731
+#: pkgs.dbk:1734
msgid ""
"Porters should try to avoid patches which simply kludge around bugs in the "
"current version of the compile environment, kernel, or libc. Sometimes such "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1739
+#: pkgs.dbk:1742
msgid ""
"Porters may also have an unofficial location where they can put the results "
"of their work during the waiting period. This helps others running the port "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1749
+#: pkgs.dbk:1752
msgid "Porting infrastructure and automation"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1751
+#: pkgs.dbk:1754
msgid ""
"There is infrastructure and several tools to help automate package porting. "
"This section contains a brief overview of this automation and porting to "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1756
+#: pkgs.dbk:1759
msgid "Mailing lists and web pages"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1758
+#: pkgs.dbk:1761
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:1762
+#: pkgs.dbk:1765
msgid ""
"Each port of Debian has a mailing list. The list of porting mailing lists "
"can be found at <ulink url=\"&url-debian-port-lists;\"></ulink>. These "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1770
+#: pkgs.dbk:1773
msgid "Porter tools"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1772
+#: pkgs.dbk:1775
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:1778
+#: pkgs.dbk:1781
msgid "<systemitem role=\"package\">wanna-build</systemitem>"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1780
+#: pkgs.dbk:1783
msgid ""
"The <systemitem role=\"package\">wanna-build</systemitem> system is used as "
"a distributed, client-server build distribution system. It is usually used "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1788
+#: pkgs.dbk:1791
msgid ""
"<systemitem role=\"package\">wanna-build</systemitem> is not yet available "
"as a package; however, all Debian porting efforts are using it for automated "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1797
+#: pkgs.dbk:1800
msgid ""
"Most of the data produced by <systemitem "
"role=\"package\">wanna-build</systemitem> which is generally useful to "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1803
+#: pkgs.dbk:1806
msgid ""
"We are quite proud of this system, since it has so many possible uses. "
"Independent development groups can use the system for different sub-flavors "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1810
+#: pkgs.dbk:1813
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 "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1817
+#: pkgs.dbk:1820
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:1826
+#: pkgs.dbk:1829
msgid "When your package is <emphasis>not</emphasis> portable"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1828
+#: pkgs.dbk:1831
msgid ""
"Some packages still have issues with building and/or working on some of the "
"architectures supported by Debian, and cannot be ported at all, or not "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1835
+#: pkgs.dbk:1838
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:1841
+#: pkgs.dbk:1844
msgid ""
"First, make sure your package <emphasis>does</emphasis> fail to build on "
"architectures that it cannot support. There are a few ways to achieve "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1849
+#: pkgs.dbk:1852
msgid ""
"Additionally, if you believe the list of supported architectures is pretty "
"constant, you should change <literal>any</literal> to a list of supported "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1857
+#: pkgs.dbk:1860
msgid ""
"In order to prevent autobuilders from needlessly trying to build your "
"package, it must be included in <filename>Packages-arch-specific</filename>, "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1866
+#: pkgs.dbk:1869
msgid ""
"Please note that it is insufficient to only add your package to "
"<filename>Packages-arch-specific</filename> without making it fail to build "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1877
+#: pkgs.dbk:1880
msgid "Marking non-free packages as auto-buildable"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1879
+#: pkgs.dbk:1882
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 "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1887
+#: pkgs.dbk:1890
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:1893
+#: pkgs.dbk:1896
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:1899
+#: pkgs.dbk:1902
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:1908
+#: pkgs.dbk:1911
msgid "Non-Maintainer Uploads (NMUs)"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:1910
+#: pkgs.dbk:1913
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 "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1919
+#: pkgs.dbk:1922
msgid "When and how to do an NMU"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1922
+#: pkgs.dbk:1925
msgid "Before doing an NMU, consider the following questions:"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1927
+#: pkgs.dbk:1930
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:1933
+#: pkgs.dbk:1936
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 "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1940
+#: pkgs.dbk:1943
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 "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1950
+#: pkgs.dbk:1953
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 "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1957
+#: pkgs.dbk:1960
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 "
-"takes care of an issue himself and that he is given the chance to review and "
-"correct your patch, because he can be expected to be more aware of potential "
-"issues which an NMUer might miss. It is often a better use of everyone's "
-"time if the maintainer is given an opportunity to upload a fix on their own."
+"contact them? In general it should be considered preferable that maintainers "
+"take care of an issue themselves and that they are given the chance to "
+"review and correct your patch, because they can be expected to be more aware "
+"of potential issues which an NMUer might miss. It is often a better use of "
+"everyone's time if the maintainer is given an opportunity to upload a fix on "
+"their own."
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1967
+#: pkgs.dbk:1970
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 "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1974
+#: pkgs.dbk:1977
msgid ""
"While preparing the patch, you should better be aware of any "
"package-specific practices that the maintainer might be using. Taking them "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1982
+#: pkgs.dbk:1985
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 "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1989
+#: pkgs.dbk:1992
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 "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1994
+#: pkgs.dbk:1997
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:1999
+#: pkgs.dbk:2002
msgid "Upload fixing only release-critical and important bugs: 5 days"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2004
+#: pkgs.dbk:2007
msgid "Other NMUs: 10 days"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2010
+#: pkgs.dbk:2013
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 "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2016
+#: pkgs.dbk:2019
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 "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2026
+#: pkgs.dbk:2029
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 "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2032
+#: pkgs.dbk:2035
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 "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2042
+#: pkgs.dbk:2045
msgid "NMUs and <filename>debian/changelog</filename>"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2044
+#: pkgs.dbk:2047
msgid ""
"Just like any other (source) upload, NMUs must add an entry to "
"<filename>debian/changelog</filename>, telling what has changed with this "
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:2049
+#: pkgs.dbk:2052
#, no-wrap
msgid " * Non-maintainer upload.\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2053
+#: pkgs.dbk:2056
msgid "The way to version NMUs differs for native and non-native packages."
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2056
+#: pkgs.dbk:2059
msgid ""
"If the package is a native package (without a Debian revision in the version "
"number), the version must be the version of the last maintainer upload, plus "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2066
+#: pkgs.dbk:2069
msgid ""
"If the package is not a native package, you should add a minor version "
"number to the Debian revision part of the version number (the portion after "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2075
+#: pkgs.dbk:2078
msgid ""
"In both cases, if the last upload was also an NMU, the counter should be "
"increased. For example, if the current version is "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2081
+#: pkgs.dbk:2084
msgid ""
"A special versioning scheme is needed to avoid disrupting the maintainer's "
"work, since using an integer for the Debian revision will potentially "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2091
+#: pkgs.dbk:2094
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 "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2113
+#: pkgs.dbk:2116
msgid "Using the <literal>DELAYED/</literal> queue"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2116
+#: pkgs.dbk:2119
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 "
"perform all the necessary tasks at the same time. For instance, instead of "
"telling the maintainer that you will upload the updated package in 7 days, "
"you should upload the package to <literal>DELAYED/7</literal> and tell the "
-"maintainer that he has 7 days to react. During this time, the maintainer "
+"maintainer that they have 7 days to react. During this time, the maintainer "
"can ask you to delay the upload some more, or cancel your upload."
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2130
+#: pkgs.dbk:2133
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 "
"available to cancel or delay the upload before the delay expires since the "
-"maintainer cannot cancel the upload himself."
+"maintainer cannot cancel the upload themselves."
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2137
+#: pkgs.dbk:2140
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 "
+"the package before the delay expires, your upload will be rejected because a "
"newer version is already available in the archive. Ideally, the maintainer "
"will take care to include your proposed changes (or at least a solution for "
"the problems they address) in that upload."
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2147
+#: pkgs.dbk:2150
msgid "NMUs from the maintainer's point of view"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2150
+#: pkgs.dbk:2153
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 "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2159
+#: pkgs.dbk:2162
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 "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2168
+#: pkgs.dbk:2171
msgid "Source NMUs vs Binary-only NMUs (binNMUs)"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2171
+#: pkgs.dbk:2174
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 "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2178
+#: pkgs.dbk:2181
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 "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2184
+#: pkgs.dbk:2187
msgid ""
"BinNMUs are usually triggered on the buildds by wanna-build. An entry is "
"added to <filename>debian/changelog</filename>, explaining why the upload "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2192
+#: pkgs.dbk:2195
msgid ""
"Buildds upload packages for their architecture to the archive as binary-only "
"uploads. Strictly speaking, these are binNMUs. However, they are not "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2200
+#: pkgs.dbk:2203
msgid "NMUs vs QA uploads"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2203
+#: pkgs.dbk:2206
msgid ""
"NMUs are uploads of packages by somebody else than their assigned "
"maintainer. There is another type of upload where the uploaded package is "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2210
+#: pkgs.dbk:2213
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 "
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:2218
+#: pkgs.dbk:2221
#, no-wrap
msgid " * QA upload.\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2222
+#: pkgs.dbk:2225
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 "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2233
+#: pkgs.dbk:2236
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 "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2242
+#: pkgs.dbk:2245
msgid "NMUs vs team uploads"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2245
+#: pkgs.dbk:2248
msgid ""
"Sometimes you are fixing and/or updating a package because you are member of "
"a packaging team (which uses a mailing list as <literal>Maintainer</literal> "
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:2255
+#: pkgs.dbk:2258
#, no-wrap
msgid " * Team upload.\n"
msgstr ""
#. type: Content of: <chapter><section><title>
-#: pkgs.dbk:2263
+#: pkgs.dbk:2266
msgid "Collaborative maintenance"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:2265
+#: pkgs.dbk:2268
msgid ""
"Collaborative maintenance is a term describing the sharing of Debian package "
"maintenance duties by several people. This collaboration is almost always a "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:2273
+#: pkgs.dbk:2276
msgid ""
"Generally there is a primary maintainer and one or more co-maintainers. The "
"primary maintainer is the person whose name is listed in the "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:2281
+#: pkgs.dbk:2284
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:2287
+#: pkgs.dbk:2290
msgid ""
"Setup the co-maintainer with access to the sources you build the package "
"from. Generally this implies you are using a network-capable version "
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2295
+#: pkgs.dbk:2298
msgid ""
"Add the co-maintainer's correct maintainer name and address to the "
"<literal>Uploaders</literal> field in the first paragraph of the "
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><screen>
-#: pkgs.dbk:2300
+#: pkgs.dbk:2303
#, no-wrap
msgid ""
"Uploaders: John Buzz <jbuzz@debian.org>, Adam Rex "
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2305
+#: pkgs.dbk:2308
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:2311
+#: pkgs.dbk:2314
msgid ""
"Another form of collaborative maintenance is team maintenance, which is "
"recommended if you maintain several packages with the same group of "
msgstr ""
#. type: Content of: <chapter><section><orderedlist><listitem><para>
-#: pkgs.dbk:2320
+#: pkgs.dbk:2323
msgid ""
"Put the team member mainly responsible for the package in the "
"<literal>Maintainer</literal> field. In the <literal>Uploaders</literal>, "
msgstr ""
#. type: Content of: <chapter><section><orderedlist><listitem><para>
-#: pkgs.dbk:2327
+#: pkgs.dbk:2330
msgid ""
"Put the mailing list address in the <literal>Maintainer</literal> field. In "
"the <literal>Uploaders</literal> field, put the team members who care for "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:2336
+#: pkgs.dbk:2339
msgid ""
"In any case, it is a bad idea to automatically put all team members in the "
"<literal>Uploaders</literal> field. It clutters the Developer's Package "
msgstr ""
#. type: Content of: <chapter><section><title>
-#: pkgs.dbk:2349
+#: pkgs.dbk:2352
msgid "The testing distribution"
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2351
+#: pkgs.dbk:2354
msgid "Basics"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2353
+#: pkgs.dbk:2356
msgid ""
"Packages are usually installed into the <literal>testing</literal> "
"distribution after they have undergone some degree of "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2358
+#: pkgs.dbk:2361
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 "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2367
+#: pkgs.dbk:2370
msgid "Updates from unstable"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2369
+#: pkgs.dbk:2372
msgid ""
"The scripts that update the <literal>testing</literal> distribution are run "
"twice each day, right after the installation of the updated packages; these "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2377
+#: pkgs.dbk:2380
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:2383
+#: pkgs.dbk:2386
msgid ""
"The package must have been available in <literal>unstable</literal> for 2, 5 "
"or 10 days, depending on the urgency (high, medium or low). Please note "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2393
+#: pkgs.dbk:2396
msgid ""
"It must not have new release-critical bugs (RC bugs affecting the version "
"available in <literal>unstable</literal>, but not affecting the version in "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2400
+#: pkgs.dbk:2403
msgid ""
"It must be available on all architectures on which it has previously been "
"built in <literal>unstable</literal>. <link linkend=\"dak-ls\">dak ls</link> "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2407
+#: pkgs.dbk:2410
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:2413
+#: pkgs.dbk:2416
msgid ""
"The packages on which it depends must either be available in "
"<literal>testing</literal> or they must be accepted into "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2421
+#: pkgs.dbk:2424
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 "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2432
+#: pkgs.dbk:2435
msgid ""
"The <filename>update_excuses</filename> file does not always give the "
"precise reason why the package is refused; you may have to find it on your "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2439
+#: pkgs.dbk:2442
msgid ""
"Sometimes, some packages never enter <literal>testing</literal> because the "
"set of interrelationship is too complicated and cannot be sorted out by the "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2444
+#: pkgs.dbk:2447
msgid ""
"Some further dependency analysis is shown on <ulink "
"url=\"http://release.debian.org/migration/\"></ulink> — but be warned, this "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2449
+#: pkgs.dbk:2452
msgid "Out-of-date"
msgstr ""
#. FIXME: better rename this file than document rampant professionalism?
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2452
+#: pkgs.dbk:2455
msgid ""
"For the <literal>testing</literal> migration script, outdated means: There "
"are different versions in <literal>unstable</literal> for the release "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2460
+#: pkgs.dbk:2463
msgid "Consider this example:"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2467 pkgs.dbk:2500
+#: pkgs.dbk:2470 pkgs.dbk:2503
msgid "alpha"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2468 pkgs.dbk:2501
+#: pkgs.dbk:2471 pkgs.dbk:2504
msgid "arm"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2473 pkgs.dbk:2507 pkgs.dbk:2569
+#: pkgs.dbk:2476 pkgs.dbk:2510 pkgs.dbk:2572
msgid "testing"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2474 pkgs.dbk:2479 pkgs.dbk:2508 pkgs.dbk:2509 pkgs.dbk:2516
+#: pkgs.dbk:2477 pkgs.dbk:2482 pkgs.dbk:2511 pkgs.dbk:2512 pkgs.dbk:2519
msgid "1"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2475 pkgs.dbk:2510 pkgs.dbk:2515
+#: pkgs.dbk:2478 pkgs.dbk:2513 pkgs.dbk:2518
msgid "-"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2478 pkgs.dbk:2513 pkgs.dbk:2570
+#: pkgs.dbk:2481 pkgs.dbk:2516 pkgs.dbk:2573
msgid "unstable"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2480 pkgs.dbk:2514
+#: pkgs.dbk:2483 pkgs.dbk:2517
msgid "2"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2486
+#: pkgs.dbk:2489
msgid ""
"The package is out of date on <literal>alpha</literal> in "
"<literal>unstable</literal>, and will not go to "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2492
+#: pkgs.dbk:2495
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:2502
+#: pkgs.dbk:2505
msgid "hurd-i386"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2522
+#: pkgs.dbk:2525
msgid ""
"In this case, the package is up to date on all release architectures in "
"<literal>unstable</literal> (and the extra <literal>hurd-i386</literal> "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2527
+#: pkgs.dbk:2530
msgid ""
"Sometimes, the question is raised if it is possible to allow packages in "
"that are not yet built on all architectures: No. Just plainly no. (Except "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2534
+#: pkgs.dbk:2537
msgid "Removals from testing"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2536
+#: pkgs.dbk:2539
msgid ""
"Sometimes, a package is removed to allow another package in: This happens "
"only to allow <emphasis>another</emphasis> package to go in if it's ready in "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2543
+#: pkgs.dbk:2546
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 "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2548
+#: pkgs.dbk:2551
msgid ""
"Furthermore, if a package has been removed from <literal>unstable</literal>, "
"and no package in <literal>testing</literal> depends on it any more, then it "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2555
+#: pkgs.dbk:2558
msgid "Circular dependencies"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2557
+#: pkgs.dbk:2560
msgid ""
"A situation which is not handled very well by britney is if package "
"<literal>a</literal> depends on the new version of package "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2562
+#: pkgs.dbk:2565
msgid "An example of this is:"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2575
+#: pkgs.dbk:2578
msgid "a"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2576
+#: pkgs.dbk:2579
msgid "1; depends: b=1"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2577
+#: pkgs.dbk:2580
msgid "2; depends: b=2"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2580
+#: pkgs.dbk:2583
msgid "b"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2581
+#: pkgs.dbk:2584
msgid "1; depends: a=1"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2582
+#: pkgs.dbk:2585
msgid "2; depends: a=2"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2588
+#: pkgs.dbk:2591
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:2592
+#: pkgs.dbk:2595
msgid ""
"Currently, this requires some manual hinting from the release team. Please "
"contact them by sending mail to &email-debian-release; if this happens to "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2599
+#: pkgs.dbk:2602
msgid "Influence of package in testing"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2601
+#: pkgs.dbk:2604
msgid ""
"Generally, there is nothing that the status of a package in "
"<literal>testing</literal> means for transition of the next version from "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2613
+#: pkgs.dbk:2616
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 "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2620
+#: pkgs.dbk:2623
msgid "Details"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2622
+#: pkgs.dbk:2625
msgid "If you are interested in details, this is how britney works:"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2625
+#: pkgs.dbk:2628
msgid ""
"The packages are looked at to determine whether they are valid candidates. "
"This gives the update excuses. The most common reasons why a package is not "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2634
+#: pkgs.dbk:2637
msgid ""
"Now, the more complex part happens: Britney tries to update "
"<literal>testing</literal> with the valid candidates. For that, britney "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2644
+#: pkgs.dbk:2647
msgid ""
"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:2648
+#: pkgs.dbk:2651
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:2656
+#: pkgs.dbk:2659
msgid "Direct updates to testing"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2658
+#: pkgs.dbk:2661
msgid ""
"The <literal>testing</literal> distribution is fed with packages from "
"<literal>unstable</literal> according to the rules explained above. "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2665
+#: pkgs.dbk:2668
msgid ""
"Keep in mind that packages uploaded there are not automatically processed, "
"they have to go through the hands of the release manager. So you'd better "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2672
+#: pkgs.dbk:2675
msgid ""
"You should not upload to <literal>testing-proposed-updates</literal> when "
"you can update your packages through <literal>unstable</literal>. If you "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2681
+#: pkgs.dbk:2684
msgid ""
"Version numbers are usually selected by adding the codename of the "
"<literal>testing</literal> distribution and a running number, like "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2688
+#: pkgs.dbk:2691
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:2693
+#: pkgs.dbk:2696
msgid ""
"Make sure that your package really needs to go through "
"<literal>testing-proposed-updates</literal>, and can't go through "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2700
+#: pkgs.dbk:2703
msgid "Make sure that you included only the minimal amount of changes;"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2705
+#: pkgs.dbk:2708
msgid "Make sure that you included an appropriate explanation in the changelog;"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2710
+#: pkgs.dbk:2713
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:2716
+#: pkgs.dbk:2719
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:2722
+#: pkgs.dbk:2725
msgid ""
"Make sure that your version number is higher than the version in "
"<literal>testing</literal> and <literal>testing-proposed-updates</literal>, "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2729
+#: pkgs.dbk:2732
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:2737
+#: pkgs.dbk:2740
msgid "Frequently asked questions"
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2739
+#: pkgs.dbk:2742
msgid "What are release-critical bugs, and how do they get counted?"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2741
+#: pkgs.dbk:2744
msgid ""
"All bugs of some higher severities are by default considered "
"release-critical; currently, these are <literal>critical</literal>, "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2746
+#: pkgs.dbk:2749
msgid ""
"Such bugs are presumed to have an impact on the chances that the package "
"will be released with the <literal>stable</literal> release of Debian: in "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2753
+#: pkgs.dbk:2756
msgid ""
"The <literal>unstable</literal> bug count are all release-critical bugs "
"which are marked to apply to "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2761
+#: pkgs.dbk:2764
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:2764
+#: pkgs.dbk:2767
msgid ""
"The structure of the distribution archives is such that they can only "
"contain one version of a package; a package is defined by its name. So when "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2772
+#: pkgs.dbk:2775
msgid ""
"However, the old version may have provided a binary package with an old "
"soname of a library, such as <literal>libacme-foo0</literal>. Removing the "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2778
+#: pkgs.dbk:2781
msgid ""
"Evidently, this mainly affects packages which provide changing sets of "
"binary packages in different versions (in turn, mainly libraries). However, "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2784
+#: pkgs.dbk:2787
msgid ""
"When the set of binary packages provided by a source package change in this "
"way, all the packages that depended on the old binaries will have to be "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2795
+#: pkgs.dbk:2798
msgid ""
"If you are having problems with complicated groups of packages like this, "
"contact &email-debian-devel; or &email-debian-release; for help."
"Subject: header. The nick should be registered: <ulink "
"url=\"http://freenode.net/faq.shtml#nicksetup\">Nick Setup Page</ulink>. "
"The mail needs to be signed by a key in the Debian keyring. Please see "
-"<ulink url=\"http://freenode.net/faq.shtml#projectcloak\">Freenodes "
+"<ulink url=\"http://freenode.net/faq.shtml#projectcloak\">Freenode "
"documentation</ulink> for more information about cloaks."
msgstr ""
msgid ""
"Active development is done in the <literal>unstable</literal> distribution "
"(that's why this distribution is sometimes called the <literal>development "
-"distribution</literal>). Every Debian developer can update his or her "
-"packages in this distribution at any time. Thus, the contents of this "
-"distribution change from day to day. Since no special effort is made to "
-"make sure everything in this distribution is working properly, it is "
-"sometimes literally unstable."
+"distribution</literal>). Every Debian developer can update their packages "
+"in this distribution at any time. Thus, the contents of this distribution "
+"change from day to day. Since no special effort is made to make sure "
+"everything in this distribution is working properly, it is sometimes "
+"literally unstable."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
~ianmdlvl / developers-reference.git / blobdiff