msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2010-01-04 00:17+0100\n"
+"POT-Creation-Date: 2010-05-06 17:34-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"
#: pkgs.dbk:23
msgid ""
"Assuming no one else is already working on your prospective package, you "
-"must then submit a bug report (<xref linkend=\"submit-bug\"/> ) against the "
+"must then submit a bug report (<xref linkend=\"submit-bug\"/>) against the "
"pseudo-package <systemitem role=\"package\">wnpp</systemitem> describing "
"your plan to create a new package, including, but not limiting yourself to, "
"a description of the package, the license of the prospective package, and "
"&email-debian-devel; by using the X-Debbugs-CC header (don't use CC:, "
"because that way the message's subject won't indicate the bug number). If "
"you are packaging so many new packages (>10) that notifying the mailing "
-"list in seperate messages is too disruptive, do send a summary after filing "
-"the bugs to the debian-devel list instead. This will inform the other "
+"list in separate messages is too disruptive, send a summary after filing the "
+"bugs to the debian-devel list instead. This will inform the other "
"developers about upcoming packages and will allow a review of your "
"description and package name."
msgstr ""
#: pkgs.dbk:45
msgid ""
"Please include a <literal>Closes: "
-"bug#<replaceable>nnnnn</replaceable></literal> entry in the changelog of the "
+"#<replaceable>nnnnn</replaceable></literal> entry in the changelog of the "
"new package in order for the bug report to be automatically closed once the "
"new package is installed in the archive (see <xref "
-"linkend=\"upload-bugfix\"/> )."
+"linkend=\"upload-bugfix\"/>)."
msgstr ""
#. type: Content of: <chapter><section><para>
msgid ""
"If you think your package needs some explanations for the administrators of "
"the NEW package queue, include them in your changelog, send to "
-"ftpmaster@debian.org a reply to the email you receive as a maintainer after "
+"&email-ftpmaster; a reply to the email you receive as a maintainer after "
"your upload, or reply to the rejection email in case you are already "
"re-uploading."
msgstr ""
#. type: Content of: <chapter><section><para>
#: pkgs.dbk:57
msgid ""
-"When closing security bugs include CVE numbers as well as the Closes: "
-"#nnnnn. This is useful for the security team to track vulnerabilities. If "
-"an upload is made to fix the bug before the advisory ID is known, it is "
-"encouraged to modify the historical changelog entry with the next upload. "
-"Even in this case, please include all available pointers to background "
-"information in the original changelog entry."
+"When closing security bugs include CVE numbers as well as the "
+"<literal>Closes: #<replaceable>nnnnn</replaceable></literal> This is useful "
+"for the security team to track vulnerabilities. If an upload is made to fix "
+"the bug before the advisory ID is known, it is encouraged to modify the "
+"historical changelog entry with the next upload. Even in this case, please "
+"include all available pointers to background information in the original "
+"changelog entry."
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:65
+#: pkgs.dbk:66
msgid ""
"There are a number of reasons why we ask maintainers to announce their "
"intentions:"
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:71
+#: pkgs.dbk:72
msgid ""
"It helps the (potentially new) maintainer to tap into the experience of "
"people on the list, and lets them know if anyone else is working on it "
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:77
+#: pkgs.dbk:78
msgid ""
"It lets other people thinking about working on the package know that there "
"already is a volunteer, so efforts may be shared."
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:83
+#: pkgs.dbk:84
msgid ""
"It lets the rest of the maintainers know more about the package than the one "
"line description and the usual changelog entry ``Initial release'' that gets "
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:90
+#: pkgs.dbk:91
msgid ""
"It is helpful to the people who live off <literal>unstable</literal> (and "
"form our first line of testers). We should encourage these people."
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:96
+#: pkgs.dbk:97
msgid ""
"The announcements give maintainers and other interested parties a better "
"feel of what is going on, and what is new, in the project."
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:102
+#: pkgs.dbk:103
msgid ""
"Please see <ulink url=\"http://&ftp-master-host;/REJECT-FAQ.html\"></ulink> "
"for common rejection reasons for a new package."
msgstr ""
#. type: Content of: <chapter><section><title>
-#: pkgs.dbk:108
+#: pkgs.dbk:109
msgid "Recording changes in the package"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:110
+#: pkgs.dbk:111
msgid ""
"Changes that you make to the package need to be recorded in the "
"<filename>debian/changelog</filename>. These changes should provide a "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:121
+#: pkgs.dbk:122
msgid ""
"The <filename>debian/changelog</filename> file conforms to a certain "
"structure, with a number of different fields. One field of note, the "
"<literal>distribution</literal>, is described in <xref "
-"linkend=\"distribution\"/> . More information about the structure of this "
+"linkend=\"distribution\"/>. More information about the structure of this "
"file can be found in the Debian Policy section titled "
"<filename>debian/changelog</filename>."
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:129
+#: pkgs.dbk:130
msgid ""
"Changelog entries can be used to automatically close Debian bugs when the "
"package is installed into the archive. See <xref "
-"linkend=\"upload-bugfix\"/> ."
+"linkend=\"upload-bugfix\"/>."
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:133
+#: pkgs.dbk:134
msgid ""
"It is conventional that the changelog entry of a package that contains a new "
"upstream version of the software looks like this:"
msgstr ""
#. type: Content of: <chapter><section><screen>
-#: pkgs.dbk:137
+#: pkgs.dbk:138
#, no-wrap
msgid " * new upstream version\n"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:140
+#: pkgs.dbk:141
msgid ""
"There are tools to help you create entries and finalize the "
"<filename>changelog</filename> for release — see <xref "
-"linkend=\"devscripts\"/> and <xref linkend=\"dpkg-dev-el\"/> ."
+"linkend=\"devscripts\"/> and <xref linkend=\"dpkg-dev-el\"/>."
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:145
-msgid "See also <xref linkend=\"bpp-debian-changelog\"/> ."
+#: pkgs.dbk:146
+msgid "See also <xref linkend=\"bpp-debian-changelog\"/>."
msgstr ""
#. type: Content of: <chapter><section><title>
-#: pkgs.dbk:150
+#: pkgs.dbk:151
msgid "Testing the package"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:152
+#: pkgs.dbk:153
msgid ""
"Before you upload your package, you should do basic testing on it. At a "
"minimum, you should try the following activities (you'll need to have an "
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:159
+#: pkgs.dbk:160
msgid ""
"Install the package and make sure the software works, or upgrade the package "
"from an older version to your new version if a Debian package for it already "
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:166
+#: pkgs.dbk:167
msgid ""
"Run <command>lintian</command> over the package. You can run "
"<command>lintian</command> as follows: <literal>lintian -v "
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:175
+#: pkgs.dbk:176
msgid ""
"Normally, a package should <emphasis>not</emphasis> be uploaded if it causes "
"lintian to emit errors (they will start with <literal>E</literal>)."
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:179
+#: pkgs.dbk:180
msgid ""
"For more information on <command>lintian</command>, see <xref "
-"linkend=\"lintian\"/> ."
+"linkend=\"lintian\"/>."
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:185
+#: pkgs.dbk:186
msgid ""
-"Optionally run <xref linkend=\"debdiff\"/> to analyze changes from an older "
-"version, if one exists."
+"Optionally run <command>debdiff</command> (see <xref linkend=\"debdiff\"/>) "
+"to analyze changes from an older version, if one exists."
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:191
+#: pkgs.dbk:192
msgid ""
"Downgrade the package to the previous version (if one exists) — this tests "
"the <filename>postrm</filename> and <filename>prerm</filename> scripts."
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:197
+#: pkgs.dbk:198
msgid "Remove the package, then reinstall it."
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:202
+#: pkgs.dbk:203
msgid ""
"Copy the source package in a different directory and try unpacking it and "
"rebuilding it. This tests if the package relies on existing files outside "
"of it, or if it relies on permissions being preserved on the files shipped "
-"inside the .diff.gz file."
+"inside the <filename>.diff.gz</filename> file."
msgstr ""
#. type: Content of: <chapter><section><title>
-#: pkgs.dbk:212
+#: pkgs.dbk:213
msgid "Layout of the source package"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:214
+#: pkgs.dbk:215
msgid "There are two types of Debian source packages:"
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:219
+#: pkgs.dbk:220
msgid ""
"the so-called <literal>native</literal> packages, where there is no "
"distinction between the original sources and the patches applied for Debian"
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:225
+#: pkgs.dbk:226
msgid ""
"the (more common) packages where there's an original source tarball file "
"accompanied by another file that contains the changes made by Debian"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:231
+#: pkgs.dbk:232
msgid ""
"For the native packages, the source package includes a Debian source control "
"file (<literal>.dsc</literal>) and the source tarball "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:240
+#: pkgs.dbk:241
msgid ""
"With source format “1.0”, whether a package is native or not was determined "
"by <command>dpkg-source</command> at build time. Nowadays it is recommended "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:247
+#: pkgs.dbk:248
msgid ""
"The first time a version is uploaded which corresponds to a particular "
"upstream version, the original source tar file should be uploaded and "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:254
+#: pkgs.dbk:255
msgid ""
"By default, <command>dpkg-genchanges</command> and "
"<command>dpkg-buildpackage</command> will include the original source tar "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:262
+#: pkgs.dbk:263
msgid ""
"If no original source is included in the upload, the original source "
"tar-file used by <command>dpkg-source</command> when constructing the "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:269
+#: pkgs.dbk:270
msgid ""
"Please notice that, in non-native packages, permissions on files that are "
-"not present in the .orig.tar.{gz,bz2} will not be preserved, as diff does "
-"not store file permissions in the patch. However when using source format "
-"“3.0 (quilt)”, permissions of files inside the <filename>debian</filename> "
-"directory are preserved since they are stored in a tar archive."
+"not present in the .orig.tar.{gz,bz2,lzma} will not be preserved, as diff "
+"does not store file permissions in the patch. However when using source "
+"format “3.0 (quilt)”, permissions of files inside the "
+"<filename>debian</filename> directory are preserved since they are stored in "
+"a tar archive."
msgstr ""
#. type: Content of: <chapter><section><title>
-#: pkgs.dbk:278
+#: pkgs.dbk:279
msgid "Picking a distribution"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:280
+#: pkgs.dbk:281
msgid ""
"Each upload needs to specify which distribution the package is intended "
"for. The package build process extracts this information from the first "
"line of the <filename>debian/changelog</filename> file and places it in the "
-"<literal>Distribution</literal> field of the <literal>.changes</literal> "
+"<literal>Distribution</literal> field of the <filename>.changes</filename> "
"file."
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:286
+#: pkgs.dbk:287
msgid ""
"There are several possible values for this field: <literal>stable</literal>, "
"<literal>unstable</literal>, <literal>testing-proposed-updates</literal> and "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:292
+#: pkgs.dbk:293
msgid ""
"Actually, there are two other possible distributions: "
-"<literal>stable-security </literal> and <literal>testing-security</literal>, "
+"<literal>stable-security</literal> and <literal>testing-security</literal>, "
"but read <xref linkend=\"bug-security\"/> for more information on those."
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:297
+#: pkgs.dbk:298
msgid ""
"It is not possible to upload a package into several distributions at the "
"same time."
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:301
+#: pkgs.dbk:302
msgid ""
"Special case: uploads to the <literal>stable</literal> and "
"<literal>oldstable</literal> distributions"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:304
+#: pkgs.dbk:305
msgid ""
"Uploading to <literal>stable</literal> means that the package will "
"transferred to the <literal>proposed-updates-new</literal> queue for review "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:312
+#: pkgs.dbk:313
msgid ""
"To ensure that your upload will be accepted, you should discuss the changes "
"with the stable release team before you upload. For that, send a mail to the "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:320
+#: pkgs.dbk:321
msgid ""
"Extra care should be taken when uploading to <literal>stable</literal>. "
"Basically, a package should only be uploaded to <literal>stable</literal> if "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:327
+#: pkgs.dbk:328
msgid "a truly critical functionality problem"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:332
+#: pkgs.dbk:333
msgid "the package becomes uninstallable"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:337
+#: pkgs.dbk:338
msgid "a released architecture lacks the package"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:342
+#: pkgs.dbk:343
msgid ""
"In the past, uploads to <literal>stable</literal> were used to address "
"security problems as well. However, this practice is deprecated, as uploads "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:353
+#: pkgs.dbk:354
msgid ""
"Changing anything else in the package that isn't important is discouraged, "
"because even trivial fixes can cause bugs later on."
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:357
+#: pkgs.dbk:358
msgid ""
"Packages uploaded to <literal>stable</literal> need to be compiled on "
"systems running <literal>stable</literal>, so that their dependencies are "
"<literal>stable</literal> that depends on a library package that only exists "
"in <literal>unstable</literal> will be rejected. Making changes to "
"dependencies of other packages (by messing with <literal>Provides</literal> "
-"or <literal>shlibs</literal> files), possibly making those other packages "
+"or <filename>shlibs</filename> files), possibly making those other packages "
"uninstallable, is strongly discouraged."
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:367
+#: pkgs.dbk:368
msgid ""
"Uploads to the <literal>oldstable</literal> distributions are possible as "
-"long as it hasn't been archived. The same rules as for <literal>stable "
-"</literal> apply."
+"long as it hasn't been archived. The same rules as for "
+"<literal>stable</literal> apply."
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:374
+#: pkgs.dbk:375
msgid "Special case: uploads to <literal>testing/testing-proposed-updates</literal>"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:376
+#: pkgs.dbk:377
msgid ""
"Please see the information in the <link linkend=\"t-p-u\">testing "
"section</link> for details."
msgstr ""
#. type: Content of: <chapter><section><title>
-#: pkgs.dbk:384
+#: pkgs.dbk:385
msgid "Uploading a package"
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:386
+#: pkgs.dbk:387
msgid "Uploading to <literal>ftp-master</literal>"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:388
+#: pkgs.dbk:389
msgid ""
"To upload a package, you should upload the files (including the signed "
"changes and dsc-file) with anonymous ftp to "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:397
+#: pkgs.dbk:398
msgid ""
"Please note that you should transfer the changes file last. Otherwise, your "
"upload may be rejected because the archive maintenance software will parse "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:402
+#: pkgs.dbk:403
msgid ""
-"You may also find the Debian packages <xref linkend=\"dupload\"/> or <xref "
-"linkend=\"dput\"/> useful when uploading packages. These handy programs "
-"help automate the process of uploading packages into Debian."
+"You may also find the Debian packages <link "
+"linkend=\"dupload\">dupload</link> or <link linkend=\"dput\">dput</link> "
+"useful when uploading packages.These handy programs help automate the "
+"process of uploading packages into Debian."
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:407
+#: pkgs.dbk:408
msgid ""
"For removing packages, please see <ulink "
-"url=\"ftp://&ftp-upload-host;&upload-queue;/README\"/> and the Debian "
-"package <xref linkend=\"dcut\"/> ."
+"url=\"ftp://&ftp-upload-host;&upload-queue;README\"/> and the Debian package "
+"<link linkend=\"dcut\">dcut</link>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:414
+#: pkgs.dbk:415
msgid "Delayed uploads"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:417
+#: pkgs.dbk:418
msgid ""
"It is sometimes useful to upload a package immediately, but to want this "
"package to arrive in the archive only a few days later. For example, when "
-"preparing a <link linkend=\"nmu\">Non-maintainer Upload</link>, you might "
+"preparing a <link linkend=\"nmu\">Non-Maintainer Upload</link>, you might "
"want to give the maintainer a few days to react."
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:424
+#: pkgs.dbk:425
msgid ""
"An upload to the delayed directory keeps the package in <ulink "
-"url=\"http://ftp-master.debian.org/deferred.html\"> the deferred uploads "
-"queue\"</ulink>. When the specified waiting time is over, the package is "
+"url=\"http://ftp-master.debian.org/deferred.html\">the deferred uploads "
+"queue</ulink>. When the specified waiting time is over, the package is "
"moved into the regular incoming directory for processing. This is done "
"through automatic uploading to <literal>&ftp-upload-host;</literal> in "
"upload-directory <literal>DELAYED/[012345678]-day</literal>. 0-day is "
msgid ""
"Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security "
"upload queue (<literal>oldstable-security</literal>, "
-"<literal>stable-security </literal>, etc.) without prior authorization from "
+"<literal>stable-security</literal>, etc.) without prior authorization from "
"the security team. If the package does not exactly meet the team's "
"requirements, it will cause many problems and delays in dealing with the "
-"unwanted upload. For details, please see section <xref "
-"linkend=\"bug-security\"/> ."
+"unwanted upload. For details, please see <xref linkend=\"bug-security\"/>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
"Packages can also be uploaded via ssh to "
"<literal>&ssh-upload-host;</literal>; files should be put "
"<literal>/srv/upload.debian.org/UploadQueue</literal>. This queue does not "
-"support <xref linkend=\"delayed-incoming\">delayed uploads</xref>."
+"support <link linkend=\"delayed-incoming\">delayed uploads</link>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
msgid ""
"Note that the <literal>Section</literal> field describes both the section as "
"well as the subsection, which are described in <xref "
-"linkend=\"archive-sections\"/> . If the section is main, it should be "
+"linkend=\"archive-sections\"/>. If the section is main, it should be "
"omitted. The list of allowable subsections can be found in <ulink "
"url=\"&url-debian-policy;ch-archive.html#s-subsections\"></ulink>."
msgstr ""
msgid ""
"Every developer has to be able to work with the Debian <ulink "
"url=\"&url-bts;\">bug tracking system</ulink>. This includes knowing how to "
-"file bug reports properly (see <xref linkend=\"submit-bug\"/> ), how to "
+"file bug reports properly (see <xref linkend=\"submit-bug\"/>), how to "
"update them and reorder them, and how to process and close them."
msgstr ""
msgid ""
"When responding to bugs, make sure that any discussion you have about bugs "
"is sent both to the original submitter of the bug, and to the bug itself "
-"(e.g., <email>123@&bugs-host;</email>). If you're writing a new mail and "
-"you don't remember the submitter email address, you can use the "
-"<email>123-submitter@&bugs-host;</email> email to contact the submitter "
-"<emphasis>and</emphasis> to record your mail within the bug log (that means "
-"you don't need to send a copy of the mail to "
-"<email>123@&bugs-host;</email>)."
+"(e.g., <email><replaceable>123</replaceable>@&bugs-host;</email>). If "
+"you're writing a new mail and you don't remember the submitter email "
+"address, you can use the "
+"<email><replaceable>123</replaceable>-submitter@&bugs-host;</email> email to "
+"contact the submitter <emphasis>and</emphasis> to record your mail within "
+"the bug log (that means you don't need to send a copy of the mail to "
+"<email><replaceable>123</replaceable>@&bugs-host;</email>)."
msgstr ""
#. type: Content of: <chapter><section><section><para>
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 "
-"<email>123-done@&bugs-host;</email>. If you're fixing a bug by changing and "
-"uploading the package, you can automate bug closing as described in <xref "
-"linkend=\"upload-bugfix\"/> ."
+"<email><replaceable>123</replaceable>-done@&bugs-host;</email>. If you're "
+"fixing a bug by changing and uploading the package, you can automate bug "
+"closing as described in <xref linkend=\"upload-bugfix\"/>."
msgstr ""
#. type: Content of: <chapter><section><section><para>
"linkend=\"irc-channels\">IRC</link> or on &email-debian-devel;. Please "
"inform the maintainer(s) of the package you reassign the bug to, for example "
"by Cc:ing the message that does the reassign to "
-"<email>packagename@packages.debian.org</email> and explaining your reasons "
-"in that mail. Please note that a simple reassignment is "
-"<emphasis>not</emphasis> e-mailed to the maintainers of the package being "
-"reassigned to, so they won't know about it until they look at a bug overview "
-"for their packages."
+"<email><replaceable>packagename</replaceable>@packages.debian.org</email> "
+"and explaining your reasons in that mail. Please note that a simple "
+"reassignment is <emphasis>not</emphasis> e-mailed to the maintainers of the "
+"package being reassigned to, so they won't know about it until they look at "
+"a bug overview for their packages."
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
#: pkgs.dbk:742
msgid ""
"If you have fixed a bug in your local copy, or if a fix has been committed "
-"to the CVS repository, you may tag the bug as <literal>pending</literal> to "
+"to the VCS repository, you may tag the bug as <literal>pending</literal> to "
"let people know that the bug is corrected and that it will be closed with "
"the next upload (add the <literal>closes:</literal> in the "
"<filename>changelog</filename>). This is particularly useful if you are "
"We prefer the <literal>closes: #<replaceable>XXX</replaceable></literal> "
"syntax, as it is the most concise entry and the easiest to integrate with "
"the text of the <filename>changelog</filename>. Unless specified different "
-"by the <replaceable>-v</replaceable>-switch to "
-"<command>dpkg-buildpackage</command>, only the bugs closed in the most "
-"recent changelog entry are closed (basically, exactly the bugs mentioned in "
-"the changelog-part in the <filename>.changes</filename> file are closed)."
+"by the <literal>-v</literal>-switch to <command>dpkg-buildpackage</command>, "
+"only the bugs closed in the most recent changelog entry are closed "
+"(basically, exactly the bugs mentioned in the changelog-part in the "
+"<filename>.changes</filename> file are closed)."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: pkgs.dbk:801
msgid ""
-"Historically, uploads identified as <link linkend=\"nmu\">Non-maintainer "
+"Historically, uploads identified as <link linkend=\"nmu\">non-maintainer "
"upload (NMU)</link> were tagged <literal>fixed</literal> instead of being "
"closed, but that practice was ceased with the advent of version-tracking. "
"The same applied to the tag <literal>fixed-in-experimental</literal>."
"<replaceable>XXX</replaceable></literal> command to the bug tracking "
"system's control address, &email-bts-control;. To close any remaining bugs "
"that were fixed by your upload, email the <filename>.changes</filename> file "
-"to <email>XXX-done@&bugs-host;</email>, where <replaceable>XXX</replaceable> "
-"is the bug number, and put Version: YYY and an empty line as the first two "
-"lines of the body of the email, where <replaceable>YYY</replaceable> is the "
-"first version where the bug has been fixed."
+"to <email><replaceable>XXX</replaceable>-done@&bugs-host;</email>, where "
+"<replaceable>XXX</replaceable> is the bug number, and put Version: "
+"<replaceable>YYY</replaceable> and an empty line as the first two lines of "
+"the body of the email, where <replaceable>YYY</replaceable> is the first "
+"version where the bug has been fixed."
msgstr ""
#. type: Content of: <chapter><section><section><para>
"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 "
"to do with an upload you made, do it by emailing an explanation to "
-"<email>XXX-done@&bugs-host;</email>. Do <emphasis "
-"role=\"strong\">not</emphasis> close bugs in the changelog entry of a "
-"version if the changes in that version of the package don't have any bearing "
-"on the bug."
+"<email><replaceable>XXX</replaceable>-done@&bugs-host;</email>. Do "
+"<emphasis role=\"strong\">not</emphasis> close bugs in the changelog entry "
+"of a version if the changes in that version of the package don't have any "
+"bearing on the bug."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: pkgs.dbk:827
msgid ""
"For general information on how to write your changelog entries, see <xref "
-"linkend=\"bpp-debian-changelog\"/> ."
+"linkend=\"bpp-debian-changelog\"/>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
#: pkgs.dbk:877
msgid ""
"Any information needed for the advisory (see <xref "
-"linkend=\"bug-security-advisories\"/> )"
+"linkend=\"bug-security-advisories\"/>)"
msgstr ""
#. type: Content of: <chapter><section><section><para>
msgid ""
"The Security Team has a PGP-key to enable encrypted communication about "
"sensitive issues. See the <ulink "
-"url=\"http://www.debian.org/security/faq.en.html#contact\">Security Team "
-"FAQ</ulink> for details."
+"url=\"http://www.debian.org/security/faq#contact\">Security Team FAQ</ulink> "
+"for details."
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
"<systemitem role=\"package\">patchutils</systemitem> package and "
"<command>debdiff</command> from <systemitem "
"role=\"package\">devscripts</systemitem> are useful tools for this, see "
-"<xref linkend=\"debdiff\"/> )."
+"<xref linkend=\"debdiff\"/>)."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
msgid ""
"<emphasis role=\"strong\">Target the right distribution</emphasis> in your "
"<filename>debian/changelog</filename>. For <literal>stable</literal> this "
-"is <literal>stable-security</literal> and for testing this is "
-"<literal>testing-security</literal>, and for the previous stable release, "
-"this is <literal>oldstable-security</literal>. Do not target "
+"is <literal>stable-security</literal> and for <literal>testing</literal> "
+"this is <literal>testing-security</literal>, and for the previous stable "
+"release, this is <literal>oldstable-security</literal>. Do not target "
"<replaceable>distribution</replaceable><literal>-proposed-updates</literal> "
"or <literal>stable</literal>!"
msgstr ""
"that you have already used for a previous upload, or one that conflicts with "
"a binNMU. The convention is to append "
"<literal>+</literal><replaceable>codename</replaceable><literal>1</literal>, "
-"e.g. <literal>1:2.4.3-4+etch1</literal>, of course increasing 1 for any "
+"e.g. <literal>1:2.4.3-4+lenny1</literal>, of course increasing 1 for any "
"subsequent uploads."
msgstr ""
"<emphasis role=\"strong\">with full upstream source</emphasis> "
"(<literal>dpkg-buildpackage -sa</literal>). If there has been a previous "
"upload to <literal>security.debian.org</literal> with the same upstream "
-"version, you may upload without upstream source (<literal> dpkg-buildpackage "
+"version, you may upload without upstream source (<literal>dpkg-buildpackage "
"-sd</literal>)."
msgstr ""
#: pkgs.dbk:1164
msgid ""
"Be sure to use the <emphasis role=\"strong\">exact same "
-"<filename>*.orig.tar.{gz,bz2}</filename></emphasis> as used in the normal "
-"archive, otherwise it is not possible to move the security fix into the main "
-"archives later."
+"<filename>*.orig.tar.{gz,bz2,lzma}</filename></emphasis> as used in the "
+"normal archive, otherwise it is not possible to move the security fix into "
+"the main archives later."
msgstr ""
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
"Build the package on a <emphasis role=\"strong\">clean system</emphasis> "
"which only has packages installed from the distribution you are building "
"for. If you do not have such a system yourself, you can use a debian.org "
-"machine (see <xref linkend=\"server-machines\"/> ) or setup a chroot (see "
-"<xref linkend=\"pbuilder\"/> and <xref linkend=\"debootstrap\"/> )."
+"machine (see <xref linkend=\"server-machines\"/>) or setup a chroot (see "
+"<xref linkend=\"pbuilder\"/> and <xref linkend=\"debootstrap\"/>)."
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
msgid ""
"Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security "
"upload queue (<literal>oldstable-security</literal>, "
-"<literal>stable-security </literal>, etc.) without prior authorization from "
+"<literal>stable-security</literal>, etc.) without prior authorization from "
"the security team. If the package does not exactly meet the team's "
"requirements, it will cause many problems and delays in dealing with the "
"unwanted upload."
#. type: Content of: <chapter><section><section><section><para>
#: pkgs.dbk:1192
msgid ""
-"Do <emphasis role=\"strong\">NOT</emphasis> upload your fix to <literal> "
-"proposed-updates</literal> without coordinating with the security team. "
-"Packages from <literal>security.debian.org</literal> will be copied into the "
-"<literal>proposed-updates</literal> directory automatically. If a package "
-"with the same or a higher version number is already installed into the "
-"archive, the security update will be rejected by the archive system. That "
-"way, the stable distribution will end up without a security update for this "
-"package instead."
+"Do <emphasis role=\"strong\">NOT</emphasis> upload your fix to "
+"<literal>proposed-updates</literal> without coordinating with the security "
+"team. Packages from <literal>security.debian.org</literal> will be copied "
+"into the <literal>proposed-updates</literal> directory automatically. If a "
+"package with the same or a higher version number is already installed into "
+"the archive, the security update will be rejected by the archive system. "
+"That way, the stable distribution will end up without a security update for "
+"this package instead."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
"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 "
"the archives. For security uploads, the place to upload to is "
-"<literal>ftp://security-master.debian.org/pub/SecurityUploadQueue/</literal> "
-"."
+"<literal>ftp://security-master.debian.org/pub/SecurityUploadQueue/</literal>."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
"package control information to place the package in the desired section, and "
"re-upload the package (see the <ulink url=\"&url-debian-policy;\">Debian "
"Policy Manual</ulink> for details). You must ensure that you include the "
-"<filename>.orig.tar.{gz,bz2}</filename> in your upload (even if you are not "
-"uploading a new upstream version), or it will not appear in the new section "
-"together with the rest of the package. If your new section is valid, it "
-"will be moved automatically. If it does not, then contact the ftpmasters in "
-"order to understand what happened."
+"<filename>.orig.tar.{gz,bz2,lzma}</filename> in your upload (even if you are "
+"not uploading a new upstream version), or it will not appear in the new "
+"section together with the rest of the package. If your new section is "
+"valid, it will be moved automatically. If it does not, then contact the "
+"ftpmasters in order to understand what happened."
msgstr ""
#. type: Content of: <chapter><section><section><para>
"of one of your packages (e.g., ``devel'', ``admin''), the procedure is "
"slightly different. Correct the subsection as found in the control file of "
"the package, and re-upload that. Also, you'll need to get the override file "
-"updated, as described in <xref linkend=\"override-file\"/> ."
+"updated, as described in <xref linkend=\"override-file\"/>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
"old compatibility library which is no longer required), you need to file a "
"bug against <literal>ftp.debian.org</literal> asking that the package be "
"removed; as all bugs, this bug should normally have normal severity. The "
-"bug title should be in the form <literal>RM: <replaceable>package "
-"</replaceable> <replaceable>[architecture list]</replaceable> -- "
-"<replaceable>reason</replaceable></literal>, where "
+"bug title should be in the form <literal>RM: "
+"<replaceable>package</replaceable> <replaceable>[architecture "
+"list]</replaceable> -- <replaceable>reason</replaceable></literal>, where "
"<replaceable>package</replaceable> is the package to be removed and "
"<replaceable>reason</replaceable> is a short summary of the reason for the "
"removal request. <replaceable>[architecture list]</replaceable> is optional "
"would be package hijacking. You can, of course, contact the current "
"maintainer and ask them if you may take over the package. If you have "
"reason to believe a maintainer has gone AWOL (absent without leave), see "
-"<xref linkend=\"mia-qa\"/> ."
+"<xref linkend=\"mia-qa\"/>."
msgstr ""
#. type: Content of: <chapter><section><section><para>
"validate this is to use the <systemitem "
"role=\"package\">debootstrap</systemitem> package to create an "
"<literal>unstable</literal> chroot environment (see <xref "
-"linkend=\"debootstrap\"/> ). Within that chrooted environment, install the "
+"linkend=\"debootstrap\"/>). Within that chrooted environment, install the "
"<systemitem role=\"package\">build-essential</systemitem> package and any "
"package dependencies mentioned in <literal>Build-Depends</literal> and/or "
"<literal>Build-Depends-Indep</literal>. Finally, try building your package "
"within that chrooted environment. These steps can be automated by the use "
"of the <command>pbuilder</command> program which is provided by the package "
-"of the same name (see <xref linkend=\"pbuilder\"/> )."
+"of the same name (see <xref linkend=\"pbuilder\"/>)."
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
#: pkgs.dbk:1534
msgid ""
"If you can't set up a proper chroot, <command>dpkg-depcheck</command> may be "
-"of assistance (see <xref linkend=\"dpkg-depcheck\"/> )."
+"of assistance (see <xref linkend=\"dpkg-depcheck\"/>)."
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
msgid ""
"Sometimes the initial porter upload is problematic because the environment "
"in which the package was built was not good enough (outdated or obsolete "
-"library, bad compiler, ...). Then you may just need to recompile it in an "
+"library, bad compiler, etc.). Then you may just need to recompile it in an "
"updated environment. However, you have to bump the version number in this "
"case, so that the old bad package can be replaced in the Debian archive "
"(<command>dak</command> refuses to install new packages if they don't have a "
#: pkgs.dbk:1762
msgid ""
"Descriptions of several porting tools can be found in <xref "
-"linkend=\"tools-porting\"/> ."
+"linkend=\"tools-porting\"/>."
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
"as a package; however, all Debian porting efforts are using it for automated "
"package building. The tool used to do the actual package builds, "
"<systemitem role=\"package\">sbuild</systemitem> is available as a package, "
-"see its description in <xref linkend=\"sbuild\"/> . Please note that the "
+"see its description in <xref linkend=\"sbuild\"/>. Please note that the "
"packaged version is not the same as the one used on build daemons, but it is "
"close enough to reproduce problems."
msgstr ""
"In both cases, if the last upload was also an NMU, the counter should be "
"increased. For example, if the current version is "
"<literal>1.5+nmu3</literal> (a native package which has already been NMUed), "
-"the NMU would get version <literal>1.5+nmu4</literal>. ."
+"the NMU would get version <literal>1.5+nmu4</literal>."
msgstr ""
#. type: Content of: <chapter><section><section><para>
"upload the new version (see <xref linkend=\"adopting\"/>)."
msgstr ""
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:2198
+msgid "NMUs vs team uploads"
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2201
+msgid ""
+"Sometimes you are fixing and/or updating a package because you are member of "
+"a packaging team (which uses a mailing list as Maintainer or Uploader, see "
+"<xref linkend=\"collaborative-maint\"/>) but you don't want to add yourself "
+"to Uploaders because you do not plan to contribute regularly to this "
+"specific package. If it conforms with your team's policy, you can perform a "
+"normal upload without being listed directly as Maintainer or Uploader. In "
+"that case, you should start your changelog entry with the following line: "
+"<code> * Team upload.</code>."
+msgstr ""
+
#. type: Content of: <chapter><section><title>
-#: pkgs.dbk:2200
+#: pkgs.dbk:2215
msgid "Collaborative maintenance"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:2202
+#: pkgs.dbk:2217
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:2210
+#: pkgs.dbk:2225
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:2218
+#: pkgs.dbk:2233
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:2224
+#: pkgs.dbk:2239
msgid ""
"Setup the co-maintainer with access to the sources you build the package "
"from. Generally this implies you are using a network-capable version "
"control system, such as <command>CVS</command> or "
-"<command>Subversion</command>. Alioth (see <xref linkend=\"alioth\"/> ) "
+"<command>Subversion</command>. Alioth (see <xref linkend=\"alioth\"/>) "
"provides such tools, amongst others."
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2232
+#: pkgs.dbk:2247
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:2237
+#: pkgs.dbk:2252
#, no-wrap
msgid ""
"Uploaders: John Buzz <jbuzz@debian.org>, Adam Rex "
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2242
+#: pkgs.dbk:2257
msgid ""
-"Using the PTS (<xref linkend=\"pkg-tracking-system\"/> ), the co-maintainers "
+"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:2248
+#: pkgs.dbk:2263
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:2257
+#: pkgs.dbk:2272
msgid ""
"Put the team member mainly responsible for the package in the Maintainer "
"field. In the Uploaders, put the mailing list address, and the team members "
msgstr ""
#. type: Content of: <chapter><section><orderedlist><listitem><para>
-#: pkgs.dbk:2264
+#: pkgs.dbk:2279
msgid ""
"Put the mailing list address in the Maintainer field. In the Uploaders "
"field, put the team members who care for the package. In this case, you "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:2272
+#: pkgs.dbk:2288
msgid ""
"In any case, it is a bad idea to automatically put all team members in the "
-"Uploaders field. It clutters the Developer's Package Overview listing (see "
-"<xref linkend=\"ddpo\"/> ) with packages one doesn't really care for, and "
-"creates a false sense of good maintenance."
+"Uploaders field. It clutters the Developer's Package Overview listing (see "
+"<xref linkend=\"ddpo\"/>) with packages one doesn't really care for, and "
+"creates a false sense of good maintenance. For the same reason, team members "
+"do not need to add themselves to the Uploaders field just because they are "
+"uploading the package once, they can do a “Team upload” (see <xref "
+"linkend=\"nmu-team-upload\"/>). Conversely, it it a bad idea to keep a "
+"package with only the mailing list address as a Maintainer and no Uploaders."
msgstr ""
#. type: Content of: <chapter><section><title>
-#: pkgs.dbk:2280
+#: pkgs.dbk:2301
msgid "The testing distribution"
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2282
+#: pkgs.dbk:2303
msgid "Basics"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2284
+#: pkgs.dbk:2305
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:2289
+#: pkgs.dbk:2310
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:2298
+#: pkgs.dbk:2319
msgid "Updates from unstable"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2300
+#: pkgs.dbk:2321
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:2308
+#: pkgs.dbk:2329
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:2314
+#: pkgs.dbk:2335
msgid ""
"The package must have been available in <literal>unstable</literal> for 2, 5 "
"or 10 days, depending on the urgency (high, medium or low). Please note "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2324
+#: pkgs.dbk:2345
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:2331
+#: pkgs.dbk:2352
msgid ""
"It must be available on all architectures on which it has previously been "
"built in <literal>unstable</literal>. <xref linkend=\"dak-ls\"/> may be of "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2338
+#: pkgs.dbk:2359
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:2344
+#: pkgs.dbk:2365
msgid ""
"The packages on which it depends must either be available in "
"<literal>testing</literal> or they must be accepted into "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2352
+#: pkgs.dbk:2373
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:2363
+#: pkgs.dbk:2384
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:2370
+#: pkgs.dbk:2391
msgid ""
"Sometimes, some packages never enter <literal>testing</literal> because the "
"set of inter-relationship is too complicated and cannot be sorted out by the "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2375
+#: pkgs.dbk:2396
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:2380
+#: pkgs.dbk:2401
msgid "out-of-date"
msgstr ""
#. FIXME: better rename this file than document rampant professionalism?
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2383
+#: pkgs.dbk:2404
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:2391
+#: pkgs.dbk:2412
msgid "Consider this example:"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2398 pkgs.dbk:2431
+#: pkgs.dbk:2419 pkgs.dbk:2452
msgid "alpha"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2399 pkgs.dbk:2432
+#: pkgs.dbk:2420 pkgs.dbk:2453
msgid "arm"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2404 pkgs.dbk:2438 pkgs.dbk:2500
+#: pkgs.dbk:2425 pkgs.dbk:2459 pkgs.dbk:2521
msgid "testing"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2405 pkgs.dbk:2410 pkgs.dbk:2439 pkgs.dbk:2440 pkgs.dbk:2447
+#: pkgs.dbk:2426 pkgs.dbk:2431 pkgs.dbk:2460 pkgs.dbk:2461 pkgs.dbk:2468
msgid "1"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2406 pkgs.dbk:2441 pkgs.dbk:2446
+#: pkgs.dbk:2427 pkgs.dbk:2462 pkgs.dbk:2467
msgid "-"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2409 pkgs.dbk:2444 pkgs.dbk:2501
+#: pkgs.dbk:2430 pkgs.dbk:2465 pkgs.dbk:2522
msgid "unstable"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2411 pkgs.dbk:2445
+#: pkgs.dbk:2432 pkgs.dbk:2466
msgid "2"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2417
+#: pkgs.dbk:2438
msgid ""
"The package is out of date on alpha in <literal>unstable</literal>, and will "
"not go to <literal>testing</literal>. Removing the package would not help at "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2423
+#: pkgs.dbk:2444
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:2433
+#: pkgs.dbk:2454
msgid "hurd-i386"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2453
+#: pkgs.dbk:2474
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:2458
+#: pkgs.dbk:2479
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:2465
+#: pkgs.dbk:2486
msgid "Removals from testing"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2467
+#: pkgs.dbk:2488
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:2474
+#: pkgs.dbk:2495
msgid ""
"Of course, there is another reason to remove a package from <literal>testing "
"</literal>: It's just too buggy (and having a single RC-bug is enough to be "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2479
+#: pkgs.dbk:2500
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:2486
+#: pkgs.dbk:2507
msgid "circular dependencies"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2488
+#: pkgs.dbk:2509
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:2493
+#: pkgs.dbk:2514
msgid "An example of this is:"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2506
+#: pkgs.dbk:2527
msgid "a"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2507
+#: pkgs.dbk:2528
msgid "1; depends: b=1"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2508
+#: pkgs.dbk:2529
msgid "2; depends: b=2"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2511
+#: pkgs.dbk:2532
msgid "b"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2512
+#: pkgs.dbk:2533
msgid "1; depends: a=1"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2513
+#: pkgs.dbk:2534
msgid "2; depends: a=2"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2519
+#: pkgs.dbk:2540
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:2523
+#: pkgs.dbk:2544
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:2530
+#: pkgs.dbk:2551
msgid "influence of package in testing"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2532
+#: pkgs.dbk:2553
msgid ""
"Generally, there is nothing that the status of a package in <literal>testing "
"</literal> means for transition of the next version from <literal>unstable "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2544
+#: pkgs.dbk:2565
msgid ""
"In summary this means: The only influence that a package being in <literal> "
"testing</literal> has on a new version of the same package is that the new "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2551
+#: pkgs.dbk:2572
msgid "details"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2553
+#: pkgs.dbk:2574
msgid "If you are interested in details, this is how britney works:"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2556
+#: pkgs.dbk:2577
msgid ""
"The packages are looked at to determine whether they are valid candidates. "
"This gives the update excuses. The most common reasons why a package is not "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2565
+#: pkgs.dbk:2586
msgid ""
"Now, the more complex part happens: Britney tries to update <literal>testing "
"</literal> with the valid candidates. For that, britney tries to add each "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2575
+#: pkgs.dbk:2596
msgid ""
"If you want to see more details, you can look it up on "
"<filename>merkel:/org/&ftp-debian-org;/testing/update_out/</filename> (or in "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2582
+#: pkgs.dbk:2603
msgid ""
"The hints are available via <ulink "
"url=\"http://&ftp-master-host;/testing/hints/\"></ulink>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2590
+#: pkgs.dbk:2611
msgid "Direct updates to testing"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2592
+#: pkgs.dbk:2613
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:2599
+#: pkgs.dbk:2620
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:2606
+#: pkgs.dbk:2627
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:2615
+#: pkgs.dbk:2636
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:2622
+#: pkgs.dbk:2643
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:2627
+#: pkgs.dbk:2648
msgid ""
"Make sure that your package really needs to go through "
"<literal>testing-proposed-updates</literal>, and can't go through <literal> "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2634
+#: pkgs.dbk:2655
msgid "Make sure that you included only the minimal amount of changes;"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2639
+#: pkgs.dbk:2660
msgid "Make sure that you included an appropriate explanation in the changelog;"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2644
+#: pkgs.dbk:2665
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:2650
+#: pkgs.dbk:2671
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:2656
+#: pkgs.dbk:2677
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:2663
+#: pkgs.dbk:2684
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:2671
+#: pkgs.dbk:2692
msgid "Frequently asked questions"
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2673
+#: pkgs.dbk:2694
msgid "What are release-critical bugs, and how do they get counted?"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2675
+#: pkgs.dbk:2696
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:2680
+#: pkgs.dbk:2701
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:2687
+#: pkgs.dbk:2708
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:2695
+#: pkgs.dbk:2716
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:2698
+#: pkgs.dbk:2719
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:2706
+#: pkgs.dbk:2727
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:2712
+#: pkgs.dbk:2733
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:2718
+#: pkgs.dbk:2739
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:2729
+#: pkgs.dbk:2750
msgid ""
"If you are having problems with complicated groups of packages like this, "
"contact &email-debian-devel; or &email-debian-release; for help."
~ianmdlvl / developers-reference.git / blobdiff