msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2012-04-25 09:19-0400\n"
+"POT-Creation-Date: 2012-08-08 21:41-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 ""
"queue</ulink>. When the specified waiting time is over, the package is "
"moved into the regular incoming directory for processing. This is done "
"through automatic uploading to <literal>&ftp-upload-host;</literal> in "
-"upload-directory <literal>DELAYED/[012345678]-day</literal>. 0-day is "
-"uploaded multiple times per day to <literal>&ftp-upload-host;</literal>."
+"upload-directory <literal>DELAYED/<replaceable>X</replaceable>-day</literal> "
+"(<replaceable>X</replaceable> between 0 and 15). 0-day is uploaded multiple "
+"times per day to <literal>&ftp-upload-host;</literal>."
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:436
+#: pkgs.dbk:437
msgid ""
"With dput, you can use the <literal>--delayed "
"<replaceable>DELAY</replaceable></literal> parameter to put the package into "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:442
+#: pkgs.dbk:443
msgid "Security uploads"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:444
+#: pkgs.dbk:445
msgid ""
"Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security "
"upload queue (<literal>oldstable-security</literal>, "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:454
+#: pkgs.dbk:455
msgid "Other upload queues"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:456
+#: pkgs.dbk:457
msgid ""
"There is an alternative upload queue in Europe at <ulink "
"url=\"ftp://&ftp-eu-upload-host;&upload-queue;\"/>. It operates in the same "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:462
+#: pkgs.dbk:463
msgid ""
"Packages can also be uploaded via ssh to "
"<literal>&ssh-upload-host;</literal>; files should be put "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:470
+#: pkgs.dbk:471
msgid "Notification that a new package has been installed"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:472
+#: pkgs.dbk:473
msgid ""
"The Debian archive maintainers are responsible for handling package "
"uploads. For the most part, uploads are automatically handled on a daily "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:482
+#: pkgs.dbk:483
msgid ""
"In any case, you will receive an email notification indicating that the "
"package has been added to the archive, which also indicates which bugs will "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:488
+#: pkgs.dbk:489
msgid ""
"The installation notification also includes information on what section the "
"package was inserted into. If there is a disparity, you will receive a "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:493
+#: pkgs.dbk:494
msgid ""
"Note that if you upload via queues, the queue daemon software will also send "
"you a notification by email."
msgstr ""
#. type: Content of: <chapter><section><title>
-#: pkgs.dbk:501
+#: pkgs.dbk:502
msgid "Specifying the package section, subsection and priority"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:503
+#: pkgs.dbk:504
msgid ""
"The <filename>debian/control</filename> file's <literal>Section</literal> "
"and <literal>Priority</literal> fields do not actually specify where the "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:511
+#: pkgs.dbk:512
msgid ""
"The archive maintainers keep track of the canonical sections and priorities "
"for packages in the <literal>override file</literal>. If there is a "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:521
+#: pkgs.dbk:522
msgid ""
"To alter the actual section that a package is put in, you need to first make "
"sure that the <filename>debian/control</filename> file in your package is "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:532
+#: pkgs.dbk:533
msgid ""
"For more information about <literal>override files</literal>, see "
"<citerefentry> <refentrytitle>dpkg-scanpackages</refentrytitle> "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:538
+#: pkgs.dbk:539
msgid ""
"Note that the <literal>Section</literal> field describes both the section as "
"well as the subsection, which are described in <xref "
msgstr ""
#. type: Content of: <chapter><section><title>
-#: pkgs.dbk:547
+#: pkgs.dbk:548
msgid "Handling bugs"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:549
+#: pkgs.dbk:550
msgid ""
"Every developer has to be able to work with the Debian <ulink "
"url=\"&url-bts;\">bug tracking system</ulink>. This includes knowing how to "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:555
+#: pkgs.dbk:556
msgid ""
"The bug tracking system's features are described in the <ulink "
"url=\"&url-bts-devel;\">BTS documentation for developers</ulink>. This "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:561
+#: pkgs.dbk:562
msgid ""
"Operations such as reassigning bugs to other packages, merging separate bug "
"reports about the same issue, or reopening bugs when they are prematurely "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:569
+#: pkgs.dbk:570
msgid "Monitoring bugs"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:571
+#: pkgs.dbk:572
msgid ""
"If you want to be a good maintainer, you should periodically check the "
"<ulink url=\"&url-bts;\">Debian bug tracking system (BTS)</ulink> for your "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:578
+#: pkgs.dbk:579
msgid ""
"Maintainers interact with the BTS via email addresses at "
"<literal>&bugs-host;</literal>. Documentation on available commands can be "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:585
+#: pkgs.dbk:586
msgid ""
"Some find it useful to get periodic reports on open bugs. You can add a "
"cron job such as the following if you want to get a weekly email outlining "
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:590
+#: pkgs.dbk:591
#, no-wrap
msgid ""
"# ask for weekly reports of bugs in my packages\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:594
+#: pkgs.dbk:595
msgid ""
"Replace <replaceable>address</replaceable> with your official Debian "
"maintainer address."
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:600
+#: pkgs.dbk:601
msgid "Responding to bugs"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:602
+#: pkgs.dbk:603
msgid ""
"When responding to bugs, make sure that any discussion you have about bugs "
"is sent both to the original submitter of the bug, and to the bug itself "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:611
+#: pkgs.dbk:612
msgid ""
"If you get a bug which mentions FTBFS, this means Fails to build from "
"source. Porters frequently use this acronym."
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:615
+#: pkgs.dbk:616
msgid ""
"Once you've dealt with a bug report (e.g. fixed it), mark it as "
"<literal>done</literal> (close it) by sending an explanation message to "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:622
+#: pkgs.dbk:623
msgid ""
"You should <emphasis>never</emphasis> close bugs via the bug server "
"<literal>close</literal> command sent to &email-bts-control;. If you do so, "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:630
+#: pkgs.dbk:631
msgid "Bug housekeeping"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:632
+#: pkgs.dbk:633
msgid ""
"As a package maintainer, you will often find bugs in other packages or have "
"bugs reported against your packages which are actually bugs in other "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:643
+#: pkgs.dbk:644
msgid ""
"Filing bugs for problems that you find in other packages is one of the civic "
"obligations of maintainership, see <xref linkend=\"submit-bug\"/> for "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:648
+#: pkgs.dbk:649
msgid "Here's a list of steps that you may follow to handle a bug report:"
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:653
+#: pkgs.dbk:654
msgid ""
"Decide whether the report corresponds to a real bug or not. Sometimes users "
"are just calling a program in the wrong way because they haven't read the "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:663
+#: pkgs.dbk:664
msgid ""
"If the bug submitter disagrees with your decision to close the bug, they may "
"reopen it until you find an agreement on how to handle it. If you don't "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:677
+#: pkgs.dbk:678
msgid ""
"If the bug is real but it's caused by another package, just reassign the bug "
"to the right package. If you don't know which package it should be "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:689
+#: pkgs.dbk:690
msgid ""
"If the bug affects the operation of your package, please consider cloning "
"the bug and reassigning the clone to the package that really causes the "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:699
+#: pkgs.dbk:700
msgid ""
"Sometimes you also have to adjust the severity of the bug so that it matches "
"our definition of the severity. That's because people tend to inflate the "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:707
+#: pkgs.dbk:708
msgid ""
"If the bug is real but the same problem has already been reported by someone "
"else, then the two relevant bug reports should be merged into one using the "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:718
+#: pkgs.dbk:719
msgid ""
"The bug submitter may have forgotten to provide some information, in which "
"case you have to ask them for the required information. You may use the "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:729
+#: pkgs.dbk:730
msgid ""
"If the bug is related to the packaging, you just fix it. If you are not "
"able to fix it yourself, then tag the bug as <literal>help</literal>. You "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:743
+#: pkgs.dbk:744
msgid ""
"If you have fixed a bug in your local copy, or if a fix has been committed "
"to the VCS repository, you may tag the bug as <literal>pending</literal> to "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:753
+#: pkgs.dbk:754
msgid ""
"Once a corrected package is available in the archive, the bug should be "
"closed indicating the version in which it was fixed. This can be done "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:762
+#: pkgs.dbk:763
msgid "When bugs are closed by new uploads"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:764
+#: pkgs.dbk:765
msgid ""
"As bugs and problems are fixed in your packages, it is your responsibility "
"as the package maintainer to close these bugs. However, you should not "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:772
+#: pkgs.dbk:773
msgid ""
"However, it's possible to avoid having to manually close bugs after the "
"upload — just list the fixed bugs in your "
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:778
+#: pkgs.dbk:779
#, no-wrap
msgid ""
"acme-cannon (3.1415) unstable; urgency=low\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:786
+#: pkgs.dbk:787
msgid ""
"Technically speaking, the following Perl regular expression describes how "
"bug closing changelogs are identified:"
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:790
+#: pkgs.dbk:791
#, no-wrap
msgid " /closes:\\s*(?:bug)?\\#\\s*\\d+(?:,\\s*(?:bug)?\\#\\s*\\d+)*/ig\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:793
+#: pkgs.dbk:794
msgid ""
"We prefer the <literal>closes: #<replaceable>XXX</replaceable></literal> "
"syntax, as it is the most concise entry and the easiest to integrate with "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:802
+#: pkgs.dbk:803
msgid ""
"Historically, uploads identified as <link linkend=\"nmu\">non-maintainer "
"upload (NMU)</link> were tagged <literal>fixed</literal> instead of being "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:808
+#: pkgs.dbk:809
msgid ""
"If you happen to mistype a bug number or forget a bug in the changelog "
"entries, don't hesitate to undo any damage the error caused. To reopen "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:820
+#: pkgs.dbk:821
msgid ""
"Bear in mind that it is not obligatory to close bugs using the changelog as "
"described above. If you simply want to close bugs that don't have anything "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:828
+#: pkgs.dbk:829
msgid ""
"For general information on how to write your changelog entries, see <xref "
"linkend=\"bpp-debian-changelog\"/>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:834
+#: pkgs.dbk:835
msgid "Handling security-related bugs"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:836
+#: pkgs.dbk:837
msgid ""
"Due to their sensitive nature, security-related bugs must be handled "
"carefully. The Debian Security Team exists to coordinate this activity, "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:843
+#: pkgs.dbk:844
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 "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:856
+#: pkgs.dbk:857
msgid "Whether or not the bug is already public."
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:861
+#: pkgs.dbk:862
msgid ""
"Which versions of the package are known to be affected by the bug. Check "
"each version that is present in a supported Debian release, as well as "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:868
+#: pkgs.dbk:869
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:873
+#: pkgs.dbk:874
msgid ""
"Any fixed packages that you have prepared yourself (send only the "
"<filename>.diff.gz</filename> and <filename>.dsc</filename> files and read "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:880
+#: pkgs.dbk:881
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:886
+#: pkgs.dbk:887
msgid ""
"Any information needed for the advisory (see <xref "
"linkend=\"bug-security-advisories\"/>)"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:891
+#: pkgs.dbk:892
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 "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:897
+#: pkgs.dbk:898
msgid "The Security Tracker"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:899
+#: pkgs.dbk:900
msgid ""
"The security team maintains a central database, the <ulink "
"url=\"http://security-tracker.debian.org/\">Debian Security "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:907
+#: pkgs.dbk:908
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 "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:915
+#: pkgs.dbk:916
msgid "Confidentiality"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:917
+#: pkgs.dbk:918
msgid ""
"Unlike most other activities within Debian, information about security "
"issues must sometimes be kept private for a time. This allows software "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:924
+#: pkgs.dbk:925
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:929
+#: pkgs.dbk:930
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:934
+#: pkgs.dbk:935
msgid "someone files a bug report"
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:939
+#: pkgs.dbk:940
msgid "someone informs them via private email"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:944
+#: pkgs.dbk:945
msgid ""
"In the first two cases, the information is public and it is important to "
"have a fix as soon as possible. In the last case, however, it might not be "
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:952
+#: pkgs.dbk:953
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:958
+#: pkgs.dbk:959
msgid ""
"If the problem is severe, it is preferable to share the information with "
"other vendors and coordinate a release. The security team keeps in contact "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:965
+#: pkgs.dbk:966
msgid ""
"In all cases if the person who reports the problem asks that it not be "
"disclosed, such requests should be honored, with the obvious exception of "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:972
+#: pkgs.dbk:973
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 VCS "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:979
+#: pkgs.dbk:980
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 "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:984
+#: pkgs.dbk:985
msgid ""
"The Security Team has a PGP-key to enable encrypted communication about "
"sensitive issues. See the <ulink "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:990
+#: pkgs.dbk:991
msgid "Security Advisories"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:992
+#: pkgs.dbk:993
msgid ""
"Security advisories are only issued for the current, released stable "
"distribution, and <emphasis>not</emphasis> for <literal>testing</literal> or "
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1005
+#: pkgs.dbk:1006
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:1010
+#: pkgs.dbk:1011
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:1015
+#: pkgs.dbk:1016
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:1020
+#: pkgs.dbk:1021
msgid "How it can be exploited"
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
-#: pkgs.dbk:1025
+#: pkgs.dbk:1026
msgid "Whether it is remotely or locally exploitable"
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
-#: pkgs.dbk:1030
+#: pkgs.dbk:1031
msgid "How the problem was fixed"
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1035
+#: pkgs.dbk:1036
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:1040
+#: pkgs.dbk:1041
msgid "Version numbers of affected packages"
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1045
+#: pkgs.dbk:1046
msgid "Version numbers of fixed packages"
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1050
+#: pkgs.dbk:1051
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:1056
+#: pkgs.dbk:1057
msgid ""
"References to upstream advisories, <ulink "
"url=\"http://cve.mitre.org\">CVE</ulink> identifiers, and any other "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1065
+#: pkgs.dbk:1066
msgid "Preparing packages to address security issues"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1067
+#: pkgs.dbk:1068
msgid ""
"One way that you can assist the security team in their duties is to provide "
"them with fixed packages suitable for a security advisory for the stable "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1072
+#: pkgs.dbk:1073
msgid ""
"When an update is made to the stable release, care must be taken to avoid "
"changing system behavior or introducing new bugs. In order to do this, make "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1080
+#: pkgs.dbk:1081
msgid ""
"This means that moving to a new upstream version is not a good solution. "
"Instead, the relevant changes should be back-ported to the version present "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1086
+#: pkgs.dbk:1087
msgid ""
"In some cases, it is not possible to back-port a security fix, for example "
"when large amounts of source code need to be modified or rewritten. If this "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1093
+#: pkgs.dbk:1094
msgid ""
"Related to this is another important guideline: always test your changes. "
"If you have an exploit available, try it and see if it indeed succeeds on "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1100
+#: pkgs.dbk:1101
msgid ""
"Do <emphasis role=\"strong\">NOT</emphasis> include any changes in your "
"package which are not directly related to fixing the vulnerability. These "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1110
+#: pkgs.dbk:1111
msgid ""
"Review and test your changes as much as possible. Check the differences "
"from the previous version repeatedly (<command>interdiff</command> from the "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1118
+#: pkgs.dbk:1119
msgid "Be sure to verify the following items:"
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1123
+#: pkgs.dbk:1124
msgid ""
"<emphasis role=\"strong\">Target the right distribution</emphasis> in your "
"<filename>debian/changelog</filename>. For <literal>stable</literal> this "
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1134
+#: pkgs.dbk:1135
msgid "The upload should have <emphasis role=\"strong\">urgency=high</emphasis>."
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1139
+#: pkgs.dbk:1140
msgid ""
"Make descriptive, meaningful changelog entries. Others will rely on them to "
"determine whether a particular bug was fixed. Add "
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1150
+#: pkgs.dbk:1151
msgid ""
"Make sure the <emphasis role=\"strong\">version number</emphasis> is "
"proper. It must be greater than the current package, but less than package "
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1163
+#: pkgs.dbk:1164
msgid ""
"Unless the upstream source has been uploaded to "
"<literal>security.debian.org</literal> before (by a previous security "
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1174
+#: pkgs.dbk:1175
msgid ""
"Be sure to use the <emphasis role=\"strong\">exact same "
"<filename>*.orig.tar.{gz,bz2,xz}</filename></emphasis> as used in the normal "
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1182
+#: pkgs.dbk:1183
msgid ""
"Build the package on a <emphasis role=\"strong\">clean system</emphasis> "
"which only has packages installed from the distribution you are building "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1193
+#: pkgs.dbk:1194
msgid "Uploading the fixed package"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1195
+#: pkgs.dbk:1196
msgid ""
"Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security "
"upload queue (<literal>oldstable-security</literal>, "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1202
+#: pkgs.dbk:1203
msgid ""
"Do <emphasis role=\"strong\">NOT</emphasis> upload your fix to "
"<literal>proposed-updates</literal> without coordinating with the security "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1212
+#: pkgs.dbk:1213
msgid ""
"Once you have created and tested the new package and it has been approved by "
"the security team, it needs to be uploaded so that it can be installed in "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1218
+#: pkgs.dbk:1219
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 "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1223
+#: pkgs.dbk:1224
msgid ""
"Uploads which are waiting for acceptance or verification are only accessible "
"by the security team. This is necessary since there might be fixes for "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1228
+#: pkgs.dbk:1229
msgid ""
"If a member of the security team accepts a package, it will be installed on "
"<literal>security.debian.org</literal> as well as proposed for the proper "
msgstr ""
#. type: Content of: <chapter><section><title>
-#: pkgs.dbk:1240
+#: pkgs.dbk:1241
msgid "Moving, removing, renaming, adopting, and orphaning packages"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:1242
+#: pkgs.dbk:1243
msgid ""
"Some archive manipulation operations are not automated in the Debian upload "
"process. These procedures should be manually followed by maintainers. This "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1247
+#: pkgs.dbk:1248
msgid "Moving packages"
msgstr ""
#. type: Content of: <chapter><section><section><para><footnote><para>
-#: pkgs.dbk:1251
+#: pkgs.dbk:1252
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:1249
+#: pkgs.dbk:1250
msgid ""
"Sometimes a package will change its section. For instance, a package from "
"the <literal>non-free</literal> section might be GPL'd in a later version, "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1256
+#: pkgs.dbk:1257
msgid ""
"If you need to change the section for one of your packages, change the "
"package control information to place the package in the desired section, and "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1268
+#: pkgs.dbk:1269
msgid ""
"If, on the other hand, you need to change the <literal>subsection</literal> "
"of one of your packages (e.g., ``devel'', ``admin''), the procedure is "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1277
+#: pkgs.dbk:1278
msgid "Removing packages"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1279
+#: pkgs.dbk:1280
msgid ""
"If for some reason you want to completely remove a package (say, if it is an "
"old compatibility library which is no longer required), you need to file a "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1296
+#: pkgs.dbk:1297
msgid ""
"If you want to remove a package you maintain, you should note this in the "
"bug title by prepending <literal>ROM</literal> (Request Of Maintainer). "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1305
+#: pkgs.dbk:1306
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."
+"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:1314
+#: 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:1323
+#: 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:1329
+#: 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:1339
+#: 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:1344
+#: 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:1357
+#: 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:1368
+#: pkgs.dbk:1372
msgid "Removing packages from <filename>Incoming</filename>"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1370
+#: 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:1385
+#: pkgs.dbk:1389
msgid "Replacing or renaming packages"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1387
+#: 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:1403
+#: 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:1418
+#: pkgs.dbk:1422
msgid "Orphaning a package"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1420
+#: 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:1435
+#: 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:1443
+#: 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:1449
+#: pkgs.dbk:1453
msgid "Adopting a package"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1451
+#: 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:1458
+#: 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:1464
+#: 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:1474
+#: 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:1488
+#: pkgs.dbk:1492
msgid "Porting and being ported"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:1490
+#: 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:1496
+#: 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:1505
+#: pkgs.dbk:1509
msgid "Being kind to porters"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1507
+#: 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:1515
+#: 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:1522
+#: 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:1529
+#: 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:1544
+#: 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:1548
+#: 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:1554
+#: 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:1564
+#: 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:1572
+#: 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:1580
+#: 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:1589
+#: 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:1597
+#: 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:1605
+#: 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:1616
+#: pkgs.dbk:1620
msgid "Guidelines for porter uploads"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1618
+#: 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:1626
+#: 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:1631
+#: 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:1640
+#: 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:1647
+#: pkgs.dbk:1651
msgid "Recompilation or binary-only NMU"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1649
+#: 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:1658
+#: 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:1664
+#: 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:1669
+#: 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:1684
+#: 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:1676
+#: 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:1692
+#: 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:1699
+#: 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:1701
+#: 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:1710
+#: 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:1722
+#: 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:1730
+#: 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:1738
+#: 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:1748
+#: pkgs.dbk:1752
msgid "Porting infrastructure and automation"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1750
+#: 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:1755
+#: pkgs.dbk:1759
msgid "Mailing lists and web pages"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1757
+#: 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:1761
+#: 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:1769
+#: pkgs.dbk:1773
msgid "Porter tools"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1771
+#: 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:1777
+#: pkgs.dbk:1781
msgid "<systemitem role=\"package\">wanna-build</systemitem>"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1779
+#: 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:1787
+#: 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:1796
+#: 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:1802
+#: 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:1809
+#: 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:1816
+#: 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:1825
+#: pkgs.dbk:1829
msgid "When your package is <emphasis>not</emphasis> portable"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1827
+#: 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:1834
+#: 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:1840
+#: 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:1848
+#: 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:1856
+#: 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:1865
+#: 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:1876
+#: pkgs.dbk:1880
msgid "Marking non-free packages as auto-buildable"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1878
+#: 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:1886
+#: 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:1892
+#: 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:1898
+#: 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:1907
+#: pkgs.dbk:1911
msgid "Non-Maintainer Uploads (NMUs)"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:1909
+#: 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:1918
+#: pkgs.dbk:1922
msgid "When and how to do an NMU"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1921
+#: pkgs.dbk:1925
msgid "Before doing an NMU, consider the following questions:"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1926
+#: 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:1932
+#: 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:1939
+#: 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:1949
+#: 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:1956
+#: 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:1966
+#: 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:1973
+#: 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:1981
+#: 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:1988
+#: 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:1993
+#: 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:1998
+#: 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:2003
+#: pkgs.dbk:2007
msgid "Other NMUs: 10 days"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2009
+#: 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:2015
+#: 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:2025
+#: 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:2031
+#: 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:2041
+#: pkgs.dbk:2045
msgid "NMUs and <filename>debian/changelog</filename>"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2043
+#: 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:2048
+#: pkgs.dbk:2052
#, no-wrap
msgid " * Non-maintainer upload.\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2052
+#: 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:2055
+#: 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:2065
+#: 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:2074
+#: 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:2080
+#: 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:2090
+#: 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:2112
+#: pkgs.dbk:2116
msgid "Using the <literal>DELAYED/</literal> queue"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2115
+#: 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:2129
+#: 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:2136
+#: 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:2146
+#: pkgs.dbk:2150
msgid "NMUs from the maintainer's point of view"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2149
+#: 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:2158
+#: 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:2167
+#: pkgs.dbk:2171
msgid "Source NMUs vs Binary-only NMUs (binNMUs)"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2170
+#: 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:2177
+#: 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:2183
+#: 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:2191
+#: 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:2199
+#: pkgs.dbk:2203
msgid "NMUs vs QA uploads"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2202
+#: 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:2209
+#: 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:2217
+#: pkgs.dbk:2221
#, no-wrap
msgid " * QA upload.\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2221
+#: 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:2232
+#: 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:2241
+#: pkgs.dbk:2245
msgid "NMUs vs team uploads"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2244
+#: 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:2254
+#: pkgs.dbk:2258
#, no-wrap
msgid " * Team upload.\n"
msgstr ""
#. type: Content of: <chapter><section><title>
-#: pkgs.dbk:2262
+#: pkgs.dbk:2266
msgid "Collaborative maintenance"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:2264
+#: 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:2272
+#: 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:2280
+#: 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:2286
+#: 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:2294
+#: 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:2299
+#: 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:2304
+#: 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:2310
+#: 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:2319
+#: 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:2326
+#: 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:2335
+#: 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:2348
+#: pkgs.dbk:2352
msgid "The testing distribution"
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2350
+#: pkgs.dbk:2354
msgid "Basics"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2352
+#: 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:2357
+#: 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:2366
+#: pkgs.dbk:2370
msgid "Updates from unstable"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2368
+#: 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:2376
+#: 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:2382
+#: 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 "
"that the urgency is sticky, meaning that the highest urgency uploaded since "
-"the previous <literal>testing</literal> transition is taken into account. "
-"Those delays may be doubled during a freeze, or <literal>testing</literal> "
-"transitions may be switched off altogether;"
+"the previous <literal>testing</literal> transition is taken into account;"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2392
+#: pkgs.dbk:2394
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:2399
+#: pkgs.dbk:2401
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:2406
+#: pkgs.dbk:2408
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:2412
+#: pkgs.dbk:2414
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><itemizedlist><listitem><para>
+#: pkgs.dbk:2422
+msgid ""
+"The phase of the project. I.e. automatic transitions are turned off during "
+"the <emphasis>freeze</emphasis> of the <literal>testing</literal> "
+"distribution."
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2420
+#: pkgs.dbk:2428
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:2431
+#: pkgs.dbk:2439
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:2438
+#: pkgs.dbk:2446
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:2443
+#: pkgs.dbk:2451
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:2448
+#: pkgs.dbk:2456
msgid "Out-of-date"
msgstr ""
#. FIXME: better rename this file than document rampant professionalism?
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2451
+#: pkgs.dbk:2459
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:2459
+#: pkgs.dbk:2467
msgid "Consider this example:"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2466 pkgs.dbk:2499
+#: pkgs.dbk:2474 pkgs.dbk:2507
msgid "alpha"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2467 pkgs.dbk:2500
+#: pkgs.dbk:2475 pkgs.dbk:2508
msgid "arm"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2472 pkgs.dbk:2506 pkgs.dbk:2568
+#: pkgs.dbk:2480 pkgs.dbk:2514 pkgs.dbk:2576
msgid "testing"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2473 pkgs.dbk:2478 pkgs.dbk:2507 pkgs.dbk:2508 pkgs.dbk:2515
+#: pkgs.dbk:2481 pkgs.dbk:2486 pkgs.dbk:2515 pkgs.dbk:2516 pkgs.dbk:2523
msgid "1"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2474 pkgs.dbk:2509 pkgs.dbk:2514
+#: pkgs.dbk:2482 pkgs.dbk:2517 pkgs.dbk:2522
msgid "-"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2477 pkgs.dbk:2512 pkgs.dbk:2569
+#: pkgs.dbk:2485 pkgs.dbk:2520 pkgs.dbk:2577
msgid "unstable"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2479 pkgs.dbk:2513
+#: pkgs.dbk:2487 pkgs.dbk:2521
msgid "2"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2485
+#: pkgs.dbk:2493
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:2491
+#: pkgs.dbk:2499
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:2501
+#: pkgs.dbk:2509
msgid "hurd-i386"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2521
+#: pkgs.dbk:2529
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:2526
+#: pkgs.dbk:2534
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:2533
+#: pkgs.dbk:2541
msgid "Removals from testing"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2535
+#: pkgs.dbk:2543
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:2542
+#: pkgs.dbk:2550
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:2547
+#: pkgs.dbk:2555
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:2554
+#: pkgs.dbk:2562
msgid "Circular dependencies"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2556
+#: pkgs.dbk:2564
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:2561
+#: pkgs.dbk:2569
msgid "An example of this is:"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2574
+#: pkgs.dbk:2582
msgid "a"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2575
+#: pkgs.dbk:2583
msgid "1; depends: b=1"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2576
+#: pkgs.dbk:2584
msgid "2; depends: b=2"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2579
+#: pkgs.dbk:2587
msgid "b"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2580
+#: pkgs.dbk:2588
msgid "1; depends: a=1"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2581
+#: pkgs.dbk:2589
msgid "2; depends: a=2"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2587
+#: pkgs.dbk:2595
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:2591
+#: pkgs.dbk:2599
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:2598
+#: pkgs.dbk:2606
msgid "Influence of package in testing"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2600
+#: pkgs.dbk:2608
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:2612
+#: pkgs.dbk:2620
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:2619
+#: pkgs.dbk:2627
msgid "Details"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2621
+#: pkgs.dbk:2629
msgid "If you are interested in details, this is how britney works:"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2624
+#: pkgs.dbk:2632
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 "
"considered are too young, RC-bugginess, and out of date on some arches. For "
-"this part of britney, the release managers have hammers of various sizes to "
-"force britney to consider a package. (Also, the base freeze is coded in "
-"that part of britney.) (There is a similar thing for binary-only updates, "
-"but this is not described here. If you're interested in that, please peruse "
-"the code.)"
+"this part of britney, the release managers have hammers of various sizes, "
+"called hints (see below), to force britney to consider a package."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2633
+#: pkgs.dbk:2639
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:2643
+#: pkgs.dbk:2649
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:2647
+#: pkgs.dbk:2653
msgid ""
"The hints are available via <ulink "
-"url=\"http://&ftp-master-host;/testing/hints/\"></ulink>."
+"url=\"http://&ftp-master-host;/testing/hints/\"></ulink>, where you can find "
+"the <ulink "
+"url=\"http://&ftp-master-host;/testing/hints/README\">description</ulink> as "
+"well. With the hints, the Debian Release team can block or unblock "
+"packages, ease or force packages into <literal>testing</literal>, remove "
+"packages from <literal>testing</literal>, approve uploads to <link "
+"linkend=\"t-p-u\">testing-proposed-updates</link> or override the urgency."
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2655
+#: pkgs.dbk:2667
msgid "Direct updates to testing"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2657
+#: pkgs.dbk:2669
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:2664
+#: pkgs.dbk:2676
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:2671
+#: pkgs.dbk:2683
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:2680
+#: pkgs.dbk:2692
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:2687
+#: pkgs.dbk:2699
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:2692
+#: pkgs.dbk:2704
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:2699
+#: pkgs.dbk:2711
msgid "Make sure that you included only the minimal amount of changes;"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2704
+#: pkgs.dbk:2716
msgid "Make sure that you included an appropriate explanation in the changelog;"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2709
+#: pkgs.dbk:2721
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:2715
+#: pkgs.dbk:2727
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:2721
+#: pkgs.dbk:2733
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:2728
+#: pkgs.dbk:2740
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:2736
+#: pkgs.dbk:2748
msgid "Frequently asked questions"
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2738
+#: pkgs.dbk:2750
msgid "What are release-critical bugs, and how do they get counted?"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2740
+#: pkgs.dbk:2752
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:2745
+#: pkgs.dbk:2757
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:2752
+#: pkgs.dbk:2764
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:2760
+#: pkgs.dbk:2772
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:2763
+#: pkgs.dbk:2775
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:2771
+#: pkgs.dbk:2783
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:2777
+#: pkgs.dbk:2789
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:2783
+#: pkgs.dbk:2795
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:2794
+#: pkgs.dbk:2806
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