#
msgid ""
msgstr ""
-"Project-Id-Version: developers-reference 3.3.9\n"
-"POT-Creation-Date: 2008-03-05 18:02+0900\n"
+"Project-Id-Version: developers-reference 3.4.0\n"
+"POT-Creation-Date: 2008-10-03 12:09+0900\n"
"PO-Revision-Date: 2008-03-05 18:30+0900\n"
"Last-Translator: Hideki Yamane (Debian-JP) <henrich@debian.or.jp>\n"
"Language-Team: Debian JP Project <debian-doc@debian.or.jp>\n"
"This chapter contains information related to creating, uploading, "
"maintaining, and porting packages."
msgstr ""
-"ã\81\93ã\81®ç« ã\81¯ã\80\81ã\83\91ã\83\83ã\82±ã\83¼ã\82¸ã\81®ä½\9cæ\88\90ã\80\81ã\82¢ã\83\83ã\83\97ã\83ã\83¼ã\83\89ã\80\81ã\83¡ã\83³ã\83\86ã\83\8aã\83³ã\82¹ã\80\81移æ¤\8dã\81«ã\81¤ã\81\84ã\81¦ã\81®æ\83\85å ±ã\82\92"
-"取り扱っています。"
+"ã\81\93ã\81®ç« ã\81§ã\81¯ã\80\81ã\83\91ã\83\83ã\82±ã\83¼ã\82¸ã\81®ä½\9cæ\88\90ã\80\81ã\82¢ã\83\83ã\83\97ã\83ã\83¼ã\83\89ã\80\81ã\83¡ã\83³ã\83\86ã\83\8aã\83³ã\82¹ã\80\81移æ¤\8dã\81«ã\81¤ã\81\84ã\81¦ã\81®æ\83\85å ±"
+"を取り扱います。"
# type: Content of: <chapter><section><title>
#: pkgs.dbk:13
# type: Content of: <chapter><section><para>
#: pkgs.dbk:31
msgid ""
-"You should set the subject of the bug to ``ITP: <replaceable>foo</"
-"replaceable> -- <replaceable>short description</replaceable>'', substituting "
-"the name of the new package for <replaceable>foo</replaceable>. The "
-"severity of the bug report must be set to <emphasis>wishlist</emphasis>. If "
-"you feel it's necessary, send a copy to &email-debian-devel; by putting the "
-"address in the <literal>X-Debbugs-CC:</literal> header of the message (no, "
-"don't use <literal>CC:</literal>, because that way the message's subject "
-"won't indicate the bug number)."
+"You should set the subject of the bug to <literal>ITP: <replaceable>foo</"
+"replaceable> -- <replaceable>short description</replaceable></literal>, "
+"substituting the name of the new package for <replaceable>foo</"
+"replaceable>. The severity of the bug report must be set to "
+"<literal>wishlist</literal>. Please send a copy to &email-debian-devel; by "
+"using the X-Debbugs-CC header (don't use CC:, because that way the message's "
+"subject won't indicate the bug number). If you are packaging so many new "
+"packages (>10) that notifying the mailing list in seperate messages is too "
+"disruptive, do send a summary after filing the bugs to the debian-devel list "
+"instead. This will inform the other developers about upcoming packages and "
+"will allow a review of your description and package name."
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:41
+#: pkgs.dbk:45
msgid ""
"Please include a <literal>Closes: bug#<replaceable>nnnnn</replaceable></"
"literal> entry in the changelog of the new package in order for the bug "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:47
+#: pkgs.dbk:51
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 "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:55
+#: pkgs.dbk:59
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:61
+#: pkgs.dbk:65
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:67
+#: pkgs.dbk:71
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:73
+#: pkgs.dbk:77
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 "
-"posted to <literal>debian-devel-changes</literal>."
+"posted to &email-debian-devel-changes;."
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:80
+#: pkgs.dbk:84
msgid ""
-"It is helpful to the people who live off unstable (and form our first line "
-"of testers). We should encourage these people."
+"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:86
+#: pkgs.dbk:90
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:92
+#: pkgs.dbk:96
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:98
+#: pkgs.dbk:102
msgid "Recording changes in the package"
msgstr "パッケージの変更を記録する"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:100
+#: pkgs.dbk:104
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:111
+#: pkgs.dbk:115
msgid ""
"The <filename>debian/changelog</filename> file conforms to a certain "
"structure, with a number of different fields. One field of note, the "
-"<emphasis>distribution</emphasis>, is described in <xref linkend="
-"\"distribution\"/> . More information about the structure of this file can "
-"be found in the Debian Policy section titled <filename>debian/changelog</"
-"filename>."
+"<literal>distribution</literal>, is described in <xref linkend=\"distribution"
+"\"/> . More information about the structure of this file can be found in "
+"the Debian Policy section titled <filename>debian/changelog</filename>."
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:119
+#: pkgs.dbk:123
msgid ""
"Changelog entries can be used to automatically close Debian bugs when the "
"package is installed into the archive. See <xref linkend=\"upload-bugfix\"/"
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:123
+#: pkgs.dbk:127
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:126
+#: pkgs.dbk:130
#, fuzzy, no-wrap
msgid ""
"\n"
msgstr "* new upstream version"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:130
+#: pkgs.dbk:134
msgid ""
"There are tools to help you create entries and finalize the "
"<filename>changelog</filename> for release — see <xref linkend=\"devscripts"
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:135
+#: pkgs.dbk:139
msgid "See also <xref linkend=\"bpp-debian-changelog\"/> ."
msgstr "<xref linkend=\"bpp-debian-changelog\"/> も参照してください。"
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:140
+#: pkgs.dbk:144
msgid "Testing the package"
msgstr "パッケージをテストする"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:142
+#: pkgs.dbk:146
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:149
+#: pkgs.dbk:153
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:156
+#: pkgs.dbk:160
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:165
+#: pkgs.dbk:169
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:169
+#: pkgs.dbk:173
msgid ""
"For more information on <command>lintian</command>, see <xref linkend="
"\"lintian\"/> ."
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:175
+#: pkgs.dbk:179
msgid ""
"Optionally run <xref linkend=\"debdiff\"/> to analyze changes from an older "
"version, if one exists."
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:181
+#: pkgs.dbk:185
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:187
+#: pkgs.dbk:191
#, fuzzy
msgid "Remove the package, then reinstall it."
msgstr "パッケージを削除して、再インストールしてください。"
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:192
+#: pkgs.dbk:196
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 "
msgstr ""
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:202
+#: pkgs.dbk:206
#, fuzzy
msgid "Layout of the source package"
msgstr "ソースパッケージの構造"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:204
+#: pkgs.dbk:208
msgid "There are two types of Debian source packages:"
msgstr "Debian のソースパッケージには 2 種類あります："
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:209
+#: pkgs.dbk:213
msgid ""
-"the so-called <emphasis>native</emphasis> packages, where there is no "
+"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:215
+#: pkgs.dbk:219
msgid ""
"the (more common) packages where there's an original source tarball file "
"accompanied by another file that contains the patches applied for Debian"
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:221
+#: pkgs.dbk:225
msgid ""
"For the native packages, the source package includes a Debian source control "
"file (<literal>.dsc</literal>) and the source tarball (<literal>.tar.gz</"
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:229
+#: pkgs.dbk:233
msgid ""
"Whether a package is native or not is determined when it is built by "
"<citerefentry> <refentrytitle>dpkg-buildpackage</refentrytitle> "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:235
+#: pkgs.dbk:239
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:242
+#: pkgs.dbk:246
msgid ""
"By default, <command>dpkg-genchanges</command> and <command>dpkg-"
"buildpackage</command> will include the original source tar file if and only "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:250
+#: pkgs.dbk:254
msgid ""
"If no original source is included in the upload, the original source tar-"
"file used by <command>dpkg-source</command> when constructing the <filename>."
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:257
+#: pkgs.dbk:261
msgid ""
"Please notice that, in non-native packages, permissions on files that are "
"not present in the .orig.tar.gz will not be preserved, as diff does not "
msgstr ""
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:264
+#: pkgs.dbk:268
msgid "Picking a distribution"
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:266
+#: pkgs.dbk:270
msgid ""
"Each upload needs to specify which distribution the package is intended "
"for. The package build process extracts this information from the first "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:272
+#: pkgs.dbk:276
msgid ""
-"There are several possible values for this field: `stable', `unstable', "
-"`testing-proposed-updates' and `experimental'. Normally, packages are "
-"uploaded into <emphasis>unstable</emphasis>."
+"There are several possible values for this field: <literal>stable</literal>, "
+"<literal>unstable</literal>, <literal>testing-proposed-updates</literal> and "
+"<literal>experimental</literal>. Normally, packages are uploaded into "
+"<literal>unstable</literal>."
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:277
+#: pkgs.dbk:282
msgid ""
-"Actually, there are two other possible distributions: `stable-security' and "
-"`testing-security', but read <xref linkend=\"bug-security\"/> for more "
-"information on those."
+"Actually, there are two other possible distributions: <literal>stable-"
+"security </literal> and <literal>testing-security</literal>, but read <xref "
+"linkend=\"bug-security\"/> for more information on those."
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:282
+#: pkgs.dbk:287
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:286
-msgid "Special case: uploads to the <emphasis>stable</emphasis> distribution"
+#: pkgs.dbk:291
+msgid ""
+"Special case: uploads to the <literal>stable</literal> and "
+"<literal>oldstable</literal> distributions"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:288
+#: pkgs.dbk:294
msgid ""
-"Uploading to <emphasis>stable</emphasis> means that the package will "
-"transfered to the <emphasis>p-u-new</emphasis>-queue for review by the "
-"stable release managers, and if approved will be installed in "
+"Uploading to <literal>stable</literal> means that the package will "
+"transfered to the <literal>proposed-updates-new</literal> queue for review "
+"by the stable release managers, and if approved will be installed in "
"<filename>stable-proposed-updates</filename> directory of the Debian "
-"archive. From there, it will be included in <emphasis>stable</emphasis> "
-"with the next point release."
+"archive. From there, it will be included in <literal>stable</literal> with "
+"the next point release."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:296
+#: pkgs.dbk:302
msgid ""
-"Extra care should be taken when uploading to <emphasis>stable</emphasis>. "
-"Basically, a package should only be uploaded to stable if one of the "
-"following happens:"
+"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 "
+"&email-debian-release; mailing list, including the patch you want to apply "
+"to the package version currently in <literal>stable</literal>. Always be "
+"verbose and detailed in your changelog entries for uploads to the "
+"<literal>stable</literal> distribution."
+msgstr ""
+
+# type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:310
+msgid ""
+"Extra care should be taken when uploading to <literal>stable</literal>. "
+"Basically, a package should only be uploaded to <literal>stable</literal> if "
+"one of the following happens:"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:303
+#: pkgs.dbk:317
msgid "a truly critical functionality problem"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:308
+#: pkgs.dbk:322
msgid "the package becomes uninstallable"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:313
+#: pkgs.dbk:327
msgid "a released architecture lacks the package"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:318
+#: pkgs.dbk:332
msgid ""
-"In the past, uploads to <emphasis>stable</emphasis> were used to address "
+"In the past, uploads to <literal>stable</literal> were used to address "
"security problems as well. However, this practice is deprecated, as uploads "
"used for Debian security advisories are automatically copied to the "
"appropriate <filename>proposed-updates</filename> archive when the advisory "
"is released. See <xref linkend=\"bug-security\"/> for detailed information "
-"on handling security problems."
+"on handling security problems. If the security teams deems the problem to be "
+"too benign to be fixed through a <literal>DSA</literal>, the stable release "
+"managers are usually willing to include your fix nonetheless in a regular "
+"upload to <literal>stable</literal>."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:326
+#: pkgs.dbk:343
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:330
+#: pkgs.dbk:347
msgid ""
-"Packages uploaded to <emphasis>stable</emphasis> need to be compiled on "
-"systems running <emphasis>stable</emphasis>, so that their dependencies are "
-"limited to the libraries (and other packages) available in <emphasis>stable</"
-"emphasis>; for example, a package uploaded to <emphasis>stable</emphasis> "
-"that depends on a library package that only exists in unstable will be "
-"rejected. Making changes to dependencies of other packages (by messing with "
-"<literal>Provides</literal> or shlibs files), possibly making those other "
-"packages uninstallable, is strongly discouraged."
+"Packages uploaded to <literal>stable</literal> need to be compiled on "
+"systems running <literal>stable</literal>, so that their dependencies are "
+"limited to the libraries (and other packages) available in <literal>stable</"
+"literal>; for example, a package uploaded to <literal>stable</literal> that "
+"depends on a library package that only exists in <literal>unstable</literal> "
+"will be rejected. Making changes to dependencies of other packages (by "
+"messing with <literal>Provides</literal> or <literal>shlibs</literal> "
+"files), possibly making those other packages uninstallable, is strongly "
+"discouraged."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:340
-msgid ""
-"The Release Team (which can be reached at &email-debian-release;) will "
-"regularly evaluate the uploads To <emphasis>stable-proposed-updates</"
-"emphasis> and decide if your package can be included in <emphasis>stable</"
-"emphasis>. Please be clear (and verbose, if necessary) in your changelog "
-"entries for uploads to <emphasis>stable</emphasis>, because otherwise the "
-"package won't be considered for inclusion."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:349
+#: pkgs.dbk:357
msgid ""
-"It's best practice to speak with the stable release manager "
-"<emphasis>before</emphasis> uploading to <emphasis>stable</emphasis>/"
-"<emphasis>stable-proposed-updates</emphasis>, so that the uploaded package "
-"fits the needs of the next point release."
+"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."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:357
+#: pkgs.dbk:364
msgid ""
-"Special case: uploads to <emphasis>testing/testing-proposed-updates</"
-"emphasis>"
+"Special case: uploads to <literal>testing/testing-proposed-updates</literal>"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:359
+#: pkgs.dbk:366
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:367
+#: pkgs.dbk:374
msgid "Uploading a package"
msgstr "パッケージをアップロードする"
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:369
+#: pkgs.dbk:376
msgid "Uploading to <literal>ftp-master</literal>"
msgstr "<literal>ftp-master</literal> にアップロードする"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:371
+#: pkgs.dbk:378
msgid ""
"To upload a package, you should upload the files (including the signed "
"changes and dsc-file) with anonymous ftp to <literal>&ftp-master-host;</"
"literal> in the directory <ulink url=\"ftp://&ftp-master-host;&upload-queue;"
"\">&upload-queue;</ulink>. To get the files processed there, they need to "
-"be signed with a key in the debian keyring."
+"be signed with a key in the Debian Developers keyring or the Debian "
+"Maintainers keyring (see <ulink url=\"&url-wiki-dm;\"></ulink>)."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:379
+#: pkgs.dbk:387
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:384
+#: pkgs.dbk:392
msgid ""
"You may also find the Debian packages <xref linkend=\"dupload\"/> or <xref "
"linkend=\"dput\"/> useful when uploading packages. These handy programs "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:389
+#: pkgs.dbk:397
msgid ""
"For removing packages, please see the README file in that ftp directory, and "
"the Debian package <xref linkend=\"dcut\"/> ."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:395
+#: pkgs.dbk:403
msgid "Delayed uploads"
msgstr "遅延アップロード"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:397
+#: pkgs.dbk:405
msgid ""
-"Delayed uploads are done for the moment via the delayed queue at gluck. The "
-"upload-directory is <literal>gluck:~tfheen/DELAYED/[012345678]-day</"
-"literal>. 0-day is uploaded multiple times per day to ftp-master."
+"Delayed uploads are done for the moment via the delayed queue at "
+"<literal>gluck </literal>. The upload-directory is <literal>gluck:~tfheen/"
+"DELAYED/[012345678]-day</literal>. 0-day is uploaded multiple times per day "
+"to <literal>&ftp-master-host;</literal>."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:402
+#: pkgs.dbk:411
msgid "With a fairly recent dput, this section"
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:404
+#: pkgs.dbk:413
#, fuzzy, no-wrap
msgid ""
"\n"
"incoming = ~tfheen"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:411
-msgid "in ~/.dput.cf should work fine for uploading to the DELAYED queue."
+#: pkgs.dbk:420
+msgid ""
+"in <filename>~/.dput.cf</filename> should work fine for uploading to the "
+"<literal>DELAYED</literal> queue."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:414
+#: pkgs.dbk:424
msgid ""
-"<emphasis>Note:</emphasis> Since this upload queue goes to <literal>ftp-"
-"master</literal>, the prescription found in <xref linkend=\"upload-ftp-master"
-"\"/> applies here as well."
+"<emphasis>Note:</emphasis> Since this upload queue goes to <literal>&ftp-"
+"master-host;</literal>, the prescription found in <xref linkend=\"upload-ftp-"
+"master\"/> applies here as well."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:421
+#: pkgs.dbk:431
msgid "Security uploads"
msgstr "セキュリティアップロード"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:423
+#: pkgs.dbk:433
msgid ""
"Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security "
-"upload queue (oldstable-security, stable-security, 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\"/> ."
+"upload queue (<literal>oldstable-security</literal>, <literal>stable-"
+"security </literal>, etc.) without prior authorization from the security "
+"team. If the package does not exactly meet the team's requirements, it will "
+"cause many problems and delays in dealing with the unwanted upload. For "
+"details, please see section <xref linkend=\"bug-security\"/> ."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:433
+#: pkgs.dbk:443
msgid "Other upload queues"
msgstr "他のアップロードキュー"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:435
+#: pkgs.dbk:445
msgid ""
-"The scp queues on ftp-master, and security are mostly unusable due to the "
-"login restrictions on those hosts."
+"The scp queues on <literal>&ftp-master-host;</literal>, and <literal> "
+"security.debian.org</literal> are mostly unusable due to the login "
+"restrictions on those hosts."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:439
+#: pkgs.dbk:450
msgid ""
"The anonymous queues on ftp.uni-erlangen.de and ftp.uk.debian.org are "
"currently down. Work is underway to resurrect them."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:443
+#: pkgs.dbk:454
msgid ""
"The queues on master.debian.org, samosa.debian.org, master.debian.or.jp, and "
"ftp.chiark.greenend.org.uk are down permanently, and will not be "
"debian.or.jp some day."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:449
-msgid ""
-"For the time being, the anonymous ftp queue on auric.debian.org (the former "
-"ftp-master) works, but it is deprecated and will be removed at some point in "
-"the future."
-msgstr ""
-
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:456
+#: pkgs.dbk:462
msgid "Notification that a new package has been installed"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:458
+#: pkgs.dbk:464
msgid ""
"The Debian archive maintainers are responsible for handling package "
"uploads. For the most part, uploads are automatically handled on a daily "
"basis by the archive maintenance tools, <command>katie</command>. "
-"Specifically, updates to existing packages to the `unstable' distribution "
-"are handled automatically. In other cases, notably new packages, placing "
-"the uploaded package into the distribution is handled manually. When "
-"uploads are handled manually, the change to the archive may take up to a "
-"month to occur. Please be patient."
+"Specifically, updates to existing packages to the <literal>unstable</"
+"literal> distribution are handled automatically. In other cases, notably "
+"new packages, placing the uploaded package into the distribution is handled "
+"manually. When uploads are handled manually, the change to the archive may "
+"take up to a month to occur. Please be patient."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:467
+#: pkgs.dbk:474
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:473
+#: pkgs.dbk:480
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:478
+#: pkgs.dbk:485
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:486
+#: pkgs.dbk:493
msgid "Specifying the package section, subsection and priority"
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:488
+#: pkgs.dbk:495
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:496
+#: pkgs.dbk:503
msgid ""
"The archive maintainers keep track of the canonical sections and priorities "
-"for packages in the <emphasis>override file</emphasis>. If there is a "
-"disparity between the <emphasis>override file</emphasis> and the package's "
+"for packages in the <literal>override file</literal>. If there is a "
+"disparity between the <literal>override file</literal> and the package's "
"fields as indicated in <filename>debian/control</filename>, then you will "
"receive an email noting the divergence when the package is installed into "
"the archive. You can either correct your <filename>debian/control</"
"filename> file for your next upload, or else you may wish to make a change "
-"in the <emphasis>override file</emphasis>."
+"in the <literal>override file</literal>."
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:506
+#: pkgs.dbk:513
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:514
+#: pkgs.dbk:521
msgid ""
-"For more information about <emphasis>override files</emphasis>, see "
+"For more information about <literal>override files</literal>, see "
"<citerefentry> <refentrytitle>dpkg-scanpackages</refentrytitle> "
"<manvolnum>1</manvolnum> </citerefentry> and <ulink url=\"&url-bts-devel;"
"#maintincorrect\"></ulink>."
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:520
+#: pkgs.dbk:527
msgid ""
"Note that the <literal>Section</literal> field describes both the section as "
"well as the subsection, which are described in <xref linkend=\"archive-"
msgstr ""
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:529
+#: pkgs.dbk:536
msgid "Handling bugs"
msgstr "バグの取扱い"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:531
+#: pkgs.dbk:538
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 "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:537
+#: pkgs.dbk:544
msgid ""
"The bug tracking system's features are described in the <ulink url=\"&url-"
"bts-devel;\">BTS documentation for developers</ulink>. This includes "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:543
+#: pkgs.dbk:550
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:551
+#: pkgs.dbk:558
msgid "Monitoring bugs"
msgstr "バグの監視"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:553
+#: pkgs.dbk:560
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:560
+#: pkgs.dbk:567
msgid ""
"Maintainers interact with the BTS via email addresses at <literal>&bugs-host;"
"</literal>. Documentation on available commands can be found at <ulink url="
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:567
+#: pkgs.dbk:574
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:571
+#: pkgs.dbk:578
#, no-wrap
msgid ""
"\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:576
+#: pkgs.dbk:583
msgid ""
"Replace <replaceable>address</replaceable> with your official Debian "
"maintainer address."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:582
+#: pkgs.dbk:589
msgid "Responding to bugs"
msgstr "バグへの対応"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:584
+#: pkgs.dbk:591
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."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:593
+#: pkgs.dbk:600
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:597
+#: pkgs.dbk:604
msgid ""
"Once you've dealt with a bug report (e.g. fixed it), mark it as "
-"<emphasis>done</emphasis> (close it) by sending an explanation message to "
+"<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\"/> ."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:604
+#: pkgs.dbk:611
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:612
+#: pkgs.dbk:619
msgid "Bug housekeeping"
msgstr "バグを掃除する"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:614
+#: pkgs.dbk:621
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:625
+#: pkgs.dbk:632
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:630
+#: pkgs.dbk:637
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:635
+#: pkgs.dbk:642
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:645
+#: pkgs.dbk:652
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:659
+#: pkgs.dbk:666
msgid ""
"If the bug is real but it's caused by another package, just reassign the bug "
"to the right package. If you don't know which package it should be "
"reassigned to, you should ask for help on <link linkend=\"irc-channels"
-"\">IRC</link> or on &email-debian-devel;. Please make sure that the "
-"maintainer(s) of the package the bug is reassigned to know why you "
-"reassigned it."
+"\">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."
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:667
+#: pkgs.dbk:678
+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 "
+"behavior. Otherwise, the bug will not be shown in your package's bug list, "
+"possibly causing users to report the same bug over and over again. You "
+"should block \"your\" bug with the reassigned, cloned bug to document the "
+"relationship."
+msgstr ""
+
+# type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:688
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:675
+#: pkgs.dbk:696
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:686
+#: pkgs.dbk:707
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:697
+#: pkgs.dbk:718
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:711
+#: pkgs.dbk:732
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 "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:721
+#: pkgs.dbk:742
msgid ""
-"Once a corrected package is available in the <emphasis>unstable</emphasis> "
-"distribution, you can close the bug. This can be done automatically, read "
-"<xref linkend=\"upload-bugfix\"/> ."
+"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 "
+"automatically, read <xref linkend=\"upload-bugfix\"/>."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:730
+#: pkgs.dbk:751
msgid "When bugs are closed by new uploads"
msgstr "新規アップロードでバグがクローズされる時"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:732
+#: pkgs.dbk:753
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:740
+#: pkgs.dbk:761
msgid ""
"However, it's possible to avoid having to manually close bugs after the "
"upload — just list the fixed bugs in your <filename>debian/changelog</"
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:745
+#: pkgs.dbk:766
#, fuzzy, no-wrap
msgid ""
"\n"
" * Added man page. Closes: #98725."
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:754
+#: pkgs.dbk:775
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:757
+#: pkgs.dbk:778
#, fuzzy, no-wrap
msgid ""
"\n"
msgstr "/closes:\\s*(?:bug)?\\#\\s*\\d+(?:,\\s*(?:bug)?\\#\\s*\\d+)*/ig"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:761
+#: pkgs.dbk:782
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:770
+#: pkgs.dbk:791
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:776
+#: pkgs.dbk:797
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:788
+#: pkgs.dbk:809
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:796
+#: pkgs.dbk:817
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:802
+#: pkgs.dbk:823
msgid "Handling security-related bugs"
msgstr "セキュリティ関連バグの取扱い"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:804
+#: pkgs.dbk:825
msgid ""
"Due to their sensitive nature, security-related bugs must be handled "
"carefully. The Debian Security Team exists to coordinate this activity, "
"keeping track of outstanding security problems, helping maintainers with "
"security problems or fixing them themselves, sending security advisories, "
-"and maintaining security.debian.org."
+"and maintaining <literal>security.debian.org</literal>."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:813
+#: pkgs.dbk:834
msgid ""
"When you become aware of a security-related bug in a Debian package, whether "
"or not you are the maintainer, collect pertinent information about the "
"problem, and promptly contact the security team at &email-security-team; as "
"soon as possible. <emphasis role=\"strong\">DO NOT UPLOAD</emphasis> any "
-"packages for stable; the security team will do that. Useful information "
-"includes, for example:"
+"packages for <literal>stable</literal>; the security team will do that. "
+"Useful information includes, for example:"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:823
+#: pkgs.dbk:844
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 "
-"testing and unstable."
+"<literal>testing</literal> and <literal>unstable</literal>."
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:830
+#: pkgs.dbk:851
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:835
+#: pkgs.dbk:856
msgid ""
"Any fixed packages that you have prepared yourself (send only the <literal>."
"diff.gz</literal> and <literal>.dsc</literal> files and read <xref linkend="
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:842
+#: pkgs.dbk:863
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:848
+#: pkgs.dbk:869
msgid ""
"Any information needed for the advisory (see <xref linkend=\"bug-security-"
"advisories\"/> )"
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:854
+#: pkgs.dbk:875
msgid "Confidentiality"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:856
+#: pkgs.dbk:877
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:863
+#: pkgs.dbk:884
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:868
+#: pkgs.dbk:889
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:873
+#: pkgs.dbk:894
msgid "someone files a bug report"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:878
+#: pkgs.dbk:899
msgid "someone informs them via private email"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:883
+#: pkgs.dbk:904
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:891
+#: pkgs.dbk:912
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:897
+#: pkgs.dbk:918
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:904
+#: pkgs.dbk:925
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:911
+#: pkgs.dbk:932
msgid ""
-"Please note that if secrecy is needed you may not upload a fix to unstable "
-"(or anywhere else, such as a public CVS repository). It is not sufficient "
-"to obfuscate the details of the change, as the code itself is public, and "
-"can (and will) be examined by the general public."
+"Please note that if secrecy is needed you may not upload a fix to "
+"<literal>unstable</literal> (or anywhere else, such as a public CVS "
+"repository). It is not sufficient to obfuscate the details of the change, "
+"as the code itself is public, and can (and will) be examined by the general "
+"public."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:917
+#: pkgs.dbk:939
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><title>
-#: pkgs.dbk:924
+#: pkgs.dbk:946
msgid "Security Advisories"
msgstr "セキュリティ勧告"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:926
+#: pkgs.dbk:948
msgid ""
"Security advisories are only issued for the current, released stable "
-"distribution, and <emphasis>not</emphasis> for testing or unstable. When "
-"released, advisories are sent to the &email-debian-security-announce; "
-"mailing list and posted on <ulink url=\"&url-debian-security-advisories;"
-"\">the security web page</ulink>. Security advisories are written and "
-"posted by the security team. However they certainly do not mind if a "
-"maintainer can supply some of the information for them, or write part of the "
-"text. Information that should be in an advisory includes:"
+"distribution, and <emphasis>not</emphasis> for <literal>testing</literal> or "
+"<literal>unstable</literal>. When released, advisories are sent to the "
+"&email-debian-security-announce; mailing list and posted on <ulink url="
+"\"&url-debian-security-advisories;\">the security web page</ulink>. "
+"Security advisories are written and posted by the security team. However "
+"they certainly do not mind if a maintainer can supply some of the "
+"information for them, or write part of the text. Information that should be "
+"in an advisory includes:"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:939
+#: pkgs.dbk:961
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:944
+#: pkgs.dbk:966
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:949
+#: pkgs.dbk:971
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:954
+#: pkgs.dbk:976
msgid "How it can be exploited"
msgstr "どのようにして攻撃が可能なのか"
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
-#: pkgs.dbk:959
+#: pkgs.dbk:981
msgid "Whether it is remotely or locally exploitable"
msgstr "攻撃はリモートから可能なのかそれともローカルから可能なのか"
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
-#: pkgs.dbk:964
+#: pkgs.dbk:986
msgid "How the problem was fixed"
msgstr "どのようにして問題が修正されたのか"
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:969
+#: pkgs.dbk:991
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:974
+#: pkgs.dbk:996
msgid "Version numbers of affected packages"
msgstr "影響を受けるパッケージのバージョン番号"
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:979
+#: pkgs.dbk:1001
msgid "Version numbers of fixed packages"
msgstr "修正されたパッケージのバージョン番号"
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:984
+#: pkgs.dbk:1006
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:990
+#: pkgs.dbk:1012
msgid ""
"References to upstream advisories, <ulink url=\"http://cve.mitre.org\">CVE</"
"ulink> identifiers, and any other information useful in cross-referencing "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:999
+#: pkgs.dbk:1021
msgid "Preparing packages to address security issues"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1001
+#: pkgs.dbk:1023
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:1006
+#: pkgs.dbk:1028
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:1014
+#: pkgs.dbk:1036
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:1020
+#: pkgs.dbk:1042
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:1027
+#: pkgs.dbk:1049
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:1034
+#: pkgs.dbk:1056
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:1044
+#: pkgs.dbk:1066
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:1052
+#: pkgs.dbk:1074
msgid "Be sure to verify the following items:"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1057
+#: pkgs.dbk:1079
msgid ""
"Target the right distribution in your <filename>debian/changelog</"
-"filename>. For stable 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 <replaceable>distribution</replaceable>-proposed-updates or "
-"<literal>stable</literal>!"
+"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 <replaceable>distribution</replaceable><literal>-"
+"proposed-updates</literal> or <literal>stable</literal>!"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1067
+#: pkgs.dbk:1089
+#, fuzzy
msgid "The upload should have urgency=high."
msgstr "アップロードは urgency=high で行う必要があります。"
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1072
+#: pkgs.dbk:1094
msgid ""
"Make descriptive, meaningful changelog entries. Others will rely on them to "
"determine whether a particular bug was fixed. Always include an external "
"reference, preferably a CVE identifier, so that it can be cross-referenced. "
-"Include the same information in the changelog for unstable, so that it is "
-"clear that the same bug was fixed, as this is very helpful when verifying "
-"that the bug is fixed in the next stable release. If a CVE identifier has "
-"not yet been assigned, the security team will request one so that it can be "
-"included in the package and in the advisory."
+"Include the same information in the changelog for <literal>unstable</"
+"literal>, so that it is clear that the same bug was fixed, as this is very "
+"helpful when verifying that the bug is fixed in the next stable release. If "
+"a CVE identifier has not yet been assigned, the security team will request "
+"one so that it can be included in the package and in the advisory."
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1084
+#: pkgs.dbk:1107
msgid ""
"Make sure the version number is proper. It must be greater than the current "
"package, but less than package versions in later distributions. If in "
"doubt, test it with <literal>dpkg --compare-versions</literal>. Be careful "
"not to re-use a version number that you have already used for a previous "
-"upload. For <emphasis>testing</emphasis>, there must be a higher version in "
-"<emphasis>unstable</emphasis>. If there is none yet (for example, if "
-"<emphasis>testing</emphasis> and <emphasis>unstable</emphasis> have the same "
-"version) you must upload a new version to unstable first."
+"upload. For <literal>testing</literal>, there must be a higher version in "
+"<literal>unstable</literal>. If there is none yet (for example, if "
+"<literal>testing</literal> and <literal>unstable</literal> have the same "
+"version) you must upload a new version to <literal>unstable</literal> first."
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1096
+#: pkgs.dbk:1119
msgid ""
"Do not make source-only uploads if your package has any binary-all packages "
"(do not use the <literal>-S</literal> option to <command>dpkg-buildpackage</"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1105
+#: pkgs.dbk:1128
msgid ""
-"Unless the upstream source has been uploaded to security.debian.org before "
-"(by a previous security update), build the upload with full upstream source "
-"(<literal>dpkg-buildpackage -sa</literal>). If there has been a previous "
-"upload to security.debian.org with the same upstream version, you may upload "
-"without upstream source (<literal>dpkg-buildpackage -sd</literal>)."
+"Unless the upstream source has been uploaded to <literal>security.debian.org "
+"</literal> before (by a previous security update), build the upload with "
+"full upstream source (<literal>dpkg-buildpackage -sa</literal>). If there "
+"has been a previous upload to <literal>security.debian.org</literal> with "
+"the same upstream version, you may upload without upstream source (<literal> "
+"dpkg-buildpackage -sd</literal>)."
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1114
+#: pkgs.dbk:1138
msgid ""
"Be sure to use the exact same <filename>*.orig.tar.gz</filename> as used in "
"the normal archive, otherwise it is not possible to move the security fix "
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1121
+#: pkgs.dbk:1145
msgid ""
"Build the package on a clean system which only has packages installed from "
"the distribution you are building for. If you do not have such a system "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1132
+#: pkgs.dbk:1156
msgid "Uploading the fixed package"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1134
+#: pkgs.dbk:1158
msgid ""
"Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security "
-"upload queue (oldstable-security, stable-security, etc.) without prior "
-"authorization from the security team. If the package does not exactly meet "
-"the team's requirements, it will cause many problems and delays in dealing "
-"with the unwanted upload."
+"upload queue (<literal>oldstable-security</literal>, <literal>stable-"
+"security </literal>, etc.) without prior authorization from the security "
+"team. If the package does not exactly meet the team's requirements, it will "
+"cause many problems and delays in dealing with the unwanted upload."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1141
+#: pkgs.dbk:1165
msgid ""
-"Do <emphasis role=\"strong\">NOT</emphasis> upload your fix to proposed-"
-"updates without coordinating with the security team. Packages from security."
-"debian.org will be copied into the proposed-updates 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>
-#: pkgs.dbk:1150
+#: pkgs.dbk:1175
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:1156
+#: pkgs.dbk:1181
msgid ""
"Once an upload to the security queue has been accepted, the package will "
"automatically be rebuilt for all architectures and stored for verification "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1161
+#: pkgs.dbk:1186
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:1166
+#: pkgs.dbk:1191
msgid ""
"If a member of the security team accepts a package, it will be installed on "
-"security.debian.org as well as proposed for the proper "
-"<replaceable>distribution</replaceable>-proposed-updates on ftp-master."
+"<literal>security.debian.org</literal> as well as proposed for the proper "
+"<replaceable>distribution</replaceable><literal>-proposed-updates</literal> "
+"on <literal>&ftp-master-host;</literal>."
msgstr ""
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:1177
+#: pkgs.dbk:1203
msgid "Moving, removing, renaming, adopting, and orphaning packages"
msgstr "パッケージの移動、削除、リネーム、変更、みなしご化"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:1179
+#: pkgs.dbk:1205
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:1184
+#: pkgs.dbk:1210
msgid "Moving packages"
msgstr "パッケージの移動"
# type: Content of: <chapter><section><section><para><footnote>
-#: pkgs.dbk:1186
+#: pkgs.dbk:1212
msgid ""
"Sometimes a package will change its section. For instance, a package from "
"the `non-free' section might be GPL'd in a later version, in which case the "
msgstr ""
# type: Content of: <chapter><section><section><para><footnote><para>
-#: pkgs.dbk:1188
+#: pkgs.dbk:1214
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><section><para>
-#: pkgs.dbk:1190 pkgs.dbk:1576
+#: pkgs.dbk:1216 pkgs.dbk:1648
msgid "</footnote>"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1193
+#: pkgs.dbk:1219
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:1205
+#: pkgs.dbk:1231
msgid ""
-"If, on the other hand, you need to change the <emphasis>subsection</"
-"emphasis> 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\"/"
-"> ."
+"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 "
+"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\"/> ."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1214
+#: pkgs.dbk:1240
msgid "Removing packages"
msgstr "パッケージの削除"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1216
+#: pkgs.dbk:1242
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 "
"bug against <literal>ftp.debian.org</literal> asking that the package be "
-"removed; as all bugs, this bug should normally have normal severity. Make "
-"sure you indicate which distribution the package should be removed from. "
-"Normally, you can only have packages removed from <emphasis>unstable</"
-"emphasis> and <emphasis>experimental</emphasis>. Packages are not removed "
-"from <emphasis>testing</emphasis> directly. Rather, they will be removed "
-"automatically after the package has been removed from <emphasis>unstable</"
-"emphasis> and no package in <emphasis>testing</emphasis> depends on it."
+"removed; as all bugs, this bug should normally have normal severity. The "
+"bug title should be in the form <literal>RM: <replaceable>package </"
+"replaceable> <replaceable>[architecture list]</replaceable> -- "
+"<replaceable>reason</replaceable></literal>, where <replaceable>package</"
+"replaceable> is the package to be removed and <replaceable>reason</"
+"replaceable> is a short summary of the reason for the removal request. "
+"<replaceable>[architecture list]</replaceable> is optional and only needed "
+"if the removal request only applies to some architectures, not all. Note "
+"that the <command>reportbug</command> will create a title conforming to "
+"these rules when you use it to report a bug against the <literal> ftp.debian."
+"org</literal> pseudo-package."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1229
+#: pkgs.dbk:1259
+msgid ""
+"If you want to remove a package you maintain, you should note this in the "
+"bug title by prepending <literal>ROM</literal> (Request Of Maintainer). "
+"There are several other standard acronyms used in the reasoning for a "
+"package removal, see <ulink url=\"http://&ftp-master-host;/removals.html\"></"
+"ulink> for a complete list. That page also provides a convenient overview of "
+"pending removal requests."
+msgstr ""
+
+# type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1268
+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."
+msgstr ""
+
+# type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1277
msgid ""
"There is one exception when an explicit removal request is not necessary: If "
"a (source or binary) package is an orphan, it will be removed semi-"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1238
+#: pkgs.dbk:1286
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:1244
+#: pkgs.dbk:1292
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 "
-"maintainer."
+"maintainer. Should the package be orphaned and thus have no maintainer, you "
+"should first discuss the removal request on &email-debian-qa;. If there is a "
+"consensus that the package should be removed, you should reassign and "
+"retitle the <literal>O:</literal> bug filed against the <literal>wnpp</"
+"literal> package instead of filing a new bug as removal request."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1249
+#: pkgs.dbk:1302
msgid ""
"Further information relating to these and other package removal related "
"topics may be found at <ulink url=\"http://wiki.debian.org/ftpmaster_Removals"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1254
+#: pkgs.dbk:1307
msgid ""
"If in doubt concerning whether a package is disposable, email &email-debian-"
"devel; asking for opinions. Also of interest is the <command>apt-cache</"
"replaceable></literal>, the program will show details for "
"<replaceable>package</replaceable>, including reverse depends. Other useful "
"programs include <literal>apt-cache rdepends</literal>, <command>apt-"
-"rdepends</command> and <command>grep-dctrl</command>. Removal of orphaned "
-"packages is discussed on &email-debian-qa;."
+"rdepends</command>, <command>build-rdeps</command> (in the <systemitem role="
+"\"package\">devscripts</systemitem> package) and <command>grep-dctrl</"
+"command>. Removal of orphaned packages is discussed on &email-debian-qa;."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1265
+#: pkgs.dbk:1320
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:1272
+#: pkgs.dbk:1327
msgid "Removing packages from <filename>Incoming</filename>"
msgstr "<filename>Incoming</filename> からパッケージを削除する"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1274
+#: pkgs.dbk:1329
msgid ""
"In the past, it was possible to remove packages from <filename>incoming</"
"filename>. However, with the introduction of the new incoming system, this "
"is no longer possible. Instead, you have to upload a new revision of your "
"package with a higher version than the package you want to replace. Both "
"versions will be installed in the archive but only the higher version will "
-"actually be available in <emphasis>unstable</emphasis> since the previous "
+"actually be available in <literal>unstable</literal> since the previous "
"version will immediately be replaced by the higher. However, if you do "
"proper testing of your packages, the need to replace a package should not "
"occur too often anyway."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1289
+#: pkgs.dbk:1344
msgid "Replacing or renaming packages"
msgstr "パッケージをリプレースあるいはリネームする"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1291
+#: pkgs.dbk:1346
msgid ""
-"When you make a mistake naming your package, you should follow a two-step "
-"process to rename it. First, set your <filename>debian/control</filename> "
-"file to replace and conflict with the obsolete name of the package (see the "
-"<ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> for "
-"details). Once you've uploaded the package and the package has moved into "
-"the archive, file a bug against <literal>ftp.debian.org</literal> asking to "
-"remove the package with the obsolete name. Do not forget to properly "
-"reassign the package's bugs at the same time."
+"When the upstream maintainers for one of your packages chose to rename their "
+"software (or you made a mistake naming your package), you should follow a "
+"two-step process to rename it. In the first step, change the "
+"<filename>debian/control</filename> file to reflect the new name and to "
+"replace, provide and conflict with the obsolete package name (see the <ulink "
+"url=\"&url-debian-policy;\"> Debian Policy Manual</ulink> for details). "
+"Please note that you should only add a <literal>Provides</literal> relation "
+"if all packages depending on the obsolete package name continue to work "
+"after the renaming. Once you've uploaded the package and the package has "
+"moved into the archive, file a bug against <literal> ftp.debian.org</"
+"literal> asking to remove the package with the obsolete name (see <xref "
+"linkend=\"removing-pkgs\"/>). Do not forget to properly reassign the "
+"package's bugs at the same time."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1301
+#: pkgs.dbk:1362
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:1315
+#: pkgs.dbk:1376
msgid "Orphaning a package"
msgstr "パッケージをみなしご化する"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1317
+#: pkgs.dbk:1378
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 "
"systemitem>. The bug report should be titled <literal>O: "
"<replaceable>package</replaceable> -- <replaceable>short description</"
"replaceable></literal> indicating that the package is now orphaned. The "
-"severity of the bug should be set to <emphasis>normal</emphasis>; if the "
+"severity of the bug should be set to <literal>normal</literal>; if the "
"package has a priority of standard or higher, it should be set to "
"important. If you feel it's necessary, send a copy to &email-debian-devel; "
"by putting the address in the X-Debbugs-CC: header of the message (no, don't "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1332
+#: pkgs.dbk:1393
msgid ""
"If you just intend to give the package away, but you can keep maintainership "
"for the moment, then you should instead submit a bug against <systemitem "
"role=\"package\">wnpp</systemitem> and title it <literal>RFA: "
"<replaceable>package</replaceable> -- <replaceable>short description</"
-"replaceable></literal>. <literal>RFA</literal> stands for <emphasis>Request "
-"For Adoption</emphasis>."
+"replaceable></literal>. <literal>RFA</literal> stands for <literal>Request "
+"For Adoption</literal>."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1340
+#: pkgs.dbk:1401
msgid ""
"More information is on the <ulink url=\"&url-wnpp;\">WNPP web pages</ulink>."
msgstr ""
"す。"
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1346
+#: pkgs.dbk:1407
msgid "Adopting a package"
msgstr "パッケージに変更を加える"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1348
+#: pkgs.dbk:1409
msgid ""
"A list of packages in need of a new maintainer is available in the <ulink "
"url=\"&url-wnpp;\">Work-Needing and Prospective Packages list (WNPP)</"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1355
+#: pkgs.dbk:1416
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:1361
+#: pkgs.dbk:1422
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:1371
+#: pkgs.dbk:1432
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:1385
+#: pkgs.dbk:1446
msgid "Porting and being ported"
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:1387
+#: pkgs.dbk:1448
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:1393
+#: pkgs.dbk:1454
msgid ""
"Porting is the act of building Debian packages for architectures that are "
"different from the original architecture of the package maintainer's binary "
"package. It is a unique and essential activity. In fact, porters do most "
-"of the actual compiling of Debian packages. For instance, for a single "
-"<emphasis>i386</emphasis> binary package, there must be a recompile for each "
-"architecture, which amounts to &number-of-arches; more builds."
+"of the actual compiling of Debian packages. For instance, when a maintainer "
+"uploads a (portable) source packages with binaries for the <literal>i386 </"
+"literal> architecture, it will be built for each of the other architectures, "
+"amounting to &number-of-arches; more builds."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1401
+#: pkgs.dbk:1463
msgid "Being kind to porters"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1403
+#: pkgs.dbk:1465
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:1411
+#: pkgs.dbk:1473
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:1418
+#: pkgs.dbk:1480
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:1425
+#: pkgs.dbk:1487
msgid ""
"Make sure that your <literal>Build-Depends</literal> and <literal>Build-"
"Depends-Indep</literal> settings in <filename>debian/control</filename> are "
"set properly. The best way to validate this is to use the <systemitem role="
-"\"package\">debootstrap</systemitem> package to create an unstable chroot "
-"environment (see <xref linkend=\"debootstrap\"/> ). Within that chrooted "
-"environment, install the <systemitem role=\"package\">build-essential</"
-"systemitem> package and any package dependencies mentioned in <literal>Build-"
-"Depends</literal> and/or <literal>Build-Depends-Indep</literal>. Finally, "
-"try building your package within that chrooted environment. These steps can "
-"be automated by the use of the <command>pbuilder</command> program which is "
-"provided by the package of the same name (see <xref linkend=\"pbuilder\"/> )."
+"\"package\">debootstrap</systemitem> package to create an <literal>unstable</"
+"literal> chroot environment (see <xref linkend=\"debootstrap\"/> ). Within "
+"that chrooted environment, install the <systemitem role=\"package\">build-"
+"essential</systemitem> package and any package dependencies mentioned in "
+"<literal>Build-Depends</literal> and/or <literal>Build-Depends-Indep</"
+"literal>. Finally, try building your package within that chrooted "
+"environment. These steps can be automated by the use of the "
+"<command>pbuilder</command> program which is provided by the package of the "
+"same name (see <xref linkend=\"pbuilder\"/> )."
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1439
+#: pkgs.dbk:1502
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:1443
+#: pkgs.dbk:1506
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:1449
+#: pkgs.dbk:1512
msgid ""
-"Don't set architecture to a value other than ``all'' or ``any'' unless you "
-"really mean it. In too many cases, maintainers don't follow the "
-"instructions in the <ulink url=\"&url-debian-policy;\">Debian Policy Manual</"
-"ulink>. Setting your architecture to ``i386'' is usually incorrect."
+"Don't set architecture to a value other than <literal>all</literal> or "
+"<literal>any</literal> unless you really mean it. In too many cases, "
+"maintainers don't follow the instructions in the <ulink url=\"&url-debian-"
+"policy;\">Debian Policy Manual</ulink>. Setting your architecture to only "
+"one architecture (such as <literal>i386</literal> or <literal>amd64</"
+"literal>) is usually incorrect."
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1457
+#: pkgs.dbk:1522
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:1465
+#: pkgs.dbk:1530
msgid ""
"Make sure you don't ship your source package with the <filename>debian/"
"files</filename> or <filename>debian/substvars</filename> files. They "
-"should be removed by the `clean' target of <filename>debian/rules</filename>."
+"should be removed by the <literal>clean</literal> target of <filename>debian/"
+"rules</filename>."
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1473
+#: pkgs.dbk:1538
msgid ""
"Make sure you don't rely on locally installed or hacked configurations or "
"programs. For instance, you should never be calling programs in <filename>/"
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1482
+#: pkgs.dbk:1547
msgid ""
"Don't depend on the package you're building being installed already (a sub-"
-"case of the above issue)."
+"case of the above issue). There are, of course, exceptions to this rule, but "
+"be aware that any case like this needs manual bootstrapping and cannot be "
+"done by automated package builders."
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1488
+#: pkgs.dbk:1555
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:1496
+#: pkgs.dbk:1563
msgid ""
-"Make sure your debian/rules contains separate ``binary-arch'' and ``binary-"
-"indep'' targets, as the Debian Policy Manual requires. Make sure that both "
-"targets work independently, that is, that you can call the target without "
-"having called the other before. To test this, try to run <literal>dpkg-"
-"buildpackage -B</literal>."
+"Make sure your debian/rules contains separate <literal>binary-arch</literal> "
+"and <literal>binary-indep</literal> targets, as the Debian Policy Manual "
+"requires. Make sure that both targets work independently, that is, that you "
+"can call the target without having called the other before. To test this, "
+"try to run <command>dpkg-buildpackage -B</command>."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1507
+#: pkgs.dbk:1574
msgid "Guidelines for porter uploads"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1509
+#: pkgs.dbk:1576
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:1517
+#: pkgs.dbk:1584
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:1522
+#: pkgs.dbk:1589
msgid ""
"The way to invoke <command>dpkg-buildpackage</command> is as <literal>dpkg-"
"buildpackage -B -m<replaceable>porter-email</replaceable></literal>. Of "
"course, set <replaceable>porter-email</replaceable> to your email address. "
"This will do a binary-only build of only the architecture-dependent portions "
-"of the package, using the `binary-arch' target in <filename>debian/rules</"
-"filename>."
+"of the package, using the <literal>binary-arch</literal> target in "
+"<filename>debian/rules </filename>."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1530
+#: pkgs.dbk:1598
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:1537
+#: pkgs.dbk:1605
msgid "Recompilation or binary-only NMU"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1539
+#: pkgs.dbk:1607
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 "
"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>katie</command> refuses to install new packages if they don't have "
-"a version number greater than the currently available one)."
+"(<command>dak</command> refuses to install new packages if they don't have a "
+"version number greater than the currently available one)."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1548
+#: pkgs.dbk:1616
msgid ""
"You have to make sure that your binary-only NMU doesn't render the package "
"uninstallable. This could happen when a source package generates arch-"
-"dependent and arch-independent packages that depend on each other via "
-"$(Source-Version)."
+"dependent and arch-independent packages that have inter-dependencies "
+"generated using dpkg's substitution variable <literal>$(Source-Version) </"
+"literal>."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1554
+#: pkgs.dbk:1623
msgid ""
"Despite the required modification of the changelog, these are called binary-"
"only NMUs — there is no need in this case to trigger all other architectures "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1559
+#: pkgs.dbk:1628
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>
-#: pkgs.dbk:1566
+#: pkgs.dbk:1635
msgid ""
"The ``magic'' for a recompilation-only NMU is triggered by using a suffix "
-"appended to the package version number, following the form b<number>. "
-"For instance, if the latest version you are recompiling against was version "
-"``2.9-3'', your NMU should carry a version of ``2.9-3+b1''. If the latest "
-"version was ``3.4+b1'' (i.e, a native package with a previous recompilation "
-"NMU), your NMU should have a version number of ``3.4+b2''. <footnote>"
+"appended to the package version number, following the form <literal> "
+"b<replaceable>number</replaceable></literal>. For instance, if the latest "
+"version you are recompiling against was version <literal>2.9-3</literal>, "
+"your binary-only NMU should carry a version of <literal>2.9-3+b1</literal>. "
+"If the latest version was <literal>3.4+b1 </literal> (i.e, a native package "
+"with a previous recompilation NMU), your binary-only NMU should have a "
+"version number of <literal>3.4+b2</literal>. <footnote>"
msgstr ""
# type: Content of: <chapter><section><section><section><para><footnote><para>
-#: pkgs.dbk:1571
+#: pkgs.dbk:1643
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:1579
+#: pkgs.dbk:1651
msgid ""
"Similar to initial porter uploads, the correct way of invoking <command>dpkg-"
"buildpackage</command> is <literal>dpkg-buildpackage -B</literal> to only "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1586
+#: pkgs.dbk:1658
msgid "When to do a source NMU if you are a porter"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1588
+#: pkgs.dbk:1660
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:1597
+#: pkgs.dbk:1669
msgid ""
-"If you are a porter doing an NMU for `unstable', the above guidelines for "
-"porting should be followed, with two variations. Firstly, the acceptable "
-"waiting period — the time between when the bug is submitted to the BTS and "
-"when it is OK to do an NMU — is seven days for porters working on the "
-"unstable distribution. This period can be shortened if the problem is "
-"critical and imposes hardship on the porting effort, at the discretion of "
-"the porter group. (Remember, none of this is Policy, just mutually agreed "
-"upon guidelines.) For uploads to stable or testing, please coordinate with "
-"the appropriate release team first."
+"If you are a porter doing an NMU for <literal>unstable</literal>, the above "
+"guidelines for porting should be followed, with two variations. Firstly, "
+"the acceptable waiting period — the time between when the bug is submitted "
+"to the BTS and when it is OK to do an NMU — is seven days for porters "
+"working on the <literal>unstable</literal> distribution. This period can be "
+"shortened if the problem is critical and imposes hardship on the porting "
+"effort, at the discretion of the porter group. (Remember, none of this is "
+"Policy, just mutually agreed upon guidelines.) For uploads to "
+"<literal>stable</literal> or <literal>testing </literal>, please coordinate "
+"with the appropriate release team first."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1608
+#: pkgs.dbk:1681
msgid ""
"Secondly, porters doing source NMUs should make sure that the bug they "
-"submit to the BTS should be of severity `serious' or greater. This ensures "
-"that a single source package can be used to compile every supported Debian "
-"architecture by release time. It is very important that we have one version "
-"of the binary and source package for all architecture in order to comply "
-"with many licenses."
+"submit to the BTS should be of severity <literal>serious</literal> or "
+"greater. This ensures that a single source package can be used to compile "
+"every supported Debian architecture by release time. It is very important "
+"that we have one version of the binary and source package for all "
+"architectures in order to comply with many licenses."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1616
+#: pkgs.dbk:1689
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:1624
+#: pkgs.dbk:1697
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:1634
+#: pkgs.dbk:1707
msgid "Porting infrastructure and automation"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1636
+#: pkgs.dbk:1709
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:1641
+#: pkgs.dbk:1714
msgid "Mailing lists and web pages"
msgstr "メーリングリストとウェブページ"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1643
+#: pkgs.dbk:1716
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:1647
+#: pkgs.dbk:1720
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:1655
+#: pkgs.dbk:1728
msgid "Porter tools"
msgstr "移植用ツール"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1657
+#: pkgs.dbk:1730
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:1663
-msgid "<systemitem role=\"package\">buildd</systemitem>"
+#: pkgs.dbk:1736
+msgid "<systemitem role=\"package\">wanna-build</systemitem>"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1665
+#: pkgs.dbk:1738
msgid ""
-"The <systemitem role=\"package\">buildd</systemitem> system is used as a "
-"distributed, client-server build distribution system. It is usually used in "
-"conjunction with <emphasis>auto-builders</emphasis>, which are ``slave'' "
-"hosts which simply check out and attempt to auto-build packages which need "
-"to be ported. There is also an email interface to the system, which allows "
-"porters to ``check out'' a source package (usually one which cannot yet be "
-"auto-built) and work on it."
+"The <systemitem role=\"package\">wanna-build</systemitem> system is used as "
+"a distributed, client-server build distribution system. It is usually used "
+"in conjunction with build daemons running the <systemitem role=\"package"
+"\">buildd </systemitem> program. <literal>Build daemons</literal> are "
+"``slave'' hosts which contact the central <systemitem role=\"package\"> "
+"wanna-build</systemitem> system to receive a list of packages that need to "
+"be built."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1674
+#: pkgs.dbk:1746
msgid ""
-"<systemitem role=\"package\">buildd</systemitem> is not yet available as a "
-"package; however, most porting efforts are either using it currently or "
-"planning to use it in the near future. The actual automated builder is "
-"packaged as <systemitem role=\"package\">sbuild</systemitem>, see its "
-"description in <xref linkend=\"sbuild\"/> . The complete <systemitem role="
-"\"package\">buildd</systemitem> system also collects a number of as yet "
-"unpackaged components which are currently very useful and in use "
-"continually, such as <command>andrea</command> and <command>wanna-build</"
-"command>."
+"<systemitem role=\"package\">wanna-build</systemitem> is not yet available "
+"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 "
+"packaged version is not the same as the one used on build daemons, but it is "
+"close enough to reproduce problems."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1684
+#: pkgs.dbk:1755
msgid ""
-"Some of the data produced by <systemitem role=\"package\">buildd</"
+"Most of the data produced by <systemitem role=\"package\">wanna-build </"
"systemitem> which is generally useful to porters is available on the web at "
"<ulink url=\"&url-buildd;\"></ulink>. This data includes nightly updated "
-"information from <command>andrea</command> (source dependencies) and "
-"<systemitem role=\"package\">quinn-diff</systemitem> (packages needing "
-"recompilation)."
+"statistics, queueing information and logs for build attempts."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1692
+#: pkgs.dbk:1761
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:1699
+#: pkgs.dbk:1768
msgid ""
"The buildds admins of each arch can be contacted at the mail address "
-"$arch@buildd.debian.org."
+"<literal><replaceable>arch</replaceable>@buildd.debian.org</literal>."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1707
+#: pkgs.dbk:1776
msgid "When your package is <emphasis>not</emphasis> portable"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1709
+#: pkgs.dbk:1778
msgid ""
"Some packages still have issues with building and/or working on some of the "
"architectures supported by Debian, and cannot be ported at all, or not "
"within a reasonable amount of time. An example is a package that is SVGA-"
-"specific (only i386), or uses other hardware-specific features not supported "
-"on all architectures."
+"specific (only available for <literal>i386</literal> and <literal>amd64</"
+"literal>), or uses other hardware-specific features not supported on all "
+"architectures."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1716
+#: pkgs.dbk:1785
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:1722
+#: pkgs.dbk:1791
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:1730
+#: pkgs.dbk:1799
msgid ""
"Additionally, if you believe the list of supported architectures is pretty "
-"constant, you should change 'any' to a list of supported architectures in "
-"debian/control. This way, the build will fail also, and indicate this to a "
-"human reader without actually trying."
+"constant, you should change <literal>any</literal> to a list of supported "
+"architectures in <filename>debian/control</filename>. This way, the build "
+"will fail also, and indicate this to a human reader without actually trying."
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1738
+#: pkgs.dbk:1807
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:1748
+#: pkgs.dbk:1817
msgid ""
"Please note that it is insufficient to only add your package to Packages-"
"arch-specific without making it fail to build on unsupported architectures: "
msgstr ""
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:1761
+#: pkgs.dbk:1830
msgid "Non-Maintainer Uploads (NMUs)"
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:1763
+#: pkgs.dbk:1832
msgid ""
"Under certain circumstances it is necessary for someone other than the "
"official package maintainer to make a release of a package. This is called "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:1768
+#: pkgs.dbk:1837
msgid ""
"This section handles only source NMUs, i.e. NMUs which upload a new version "
"of the package. For binary-only NMUs by porters or QA members, please see "
"<xref linkend=\"binary-only-nmu\"/> . If a buildd builds and uploads a "
"package, that too is strictly speaking a binary NMU. See <xref linkend="
-"\"buildd\"/> for some more information."
+"\"wanna-build\"/> for some more information."
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:1775
+#: pkgs.dbk:1844
msgid ""
"The main reason why NMUs are done is when a developer needs to fix another "
"developer's package in order to address serious problems or crippling bugs "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:1780
+#: pkgs.dbk:1849
msgid ""
"First and foremost, it is critical that NMU patches to source should be as "
"non-disruptive as possible. Do not do housekeeping tasks, do not change the "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:1789
+#: pkgs.dbk:1858
msgid ""
"And please remember the Hippocratic Oath: Above all, do no harm. It is "
"better to leave a package with an open grave bug than applying a non-"
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1794
+#: pkgs.dbk:1863
msgid "How to do a NMU"
msgstr "NMU のやり方"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1796
+#: pkgs.dbk:1865
msgid ""
"NMUs which fix important, serious or higher severity bugs are encouraged and "
"accepted. You should endeavor to reach the current maintainer of the "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1802
+#: pkgs.dbk:1871
msgid ""
"NMUs should be made to assist a package's maintainer in resolving bugs. "
"Maintainers should be thankful for that help, and NMUers should respect the "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1808
+#: pkgs.dbk:1877
msgid ""
"A NMU should follow all conventions, written down in this section. For an "
-"upload to testing or unstable, this order of steps is recommended:"
+"upload to <literal>testing</literal> or <literal>unstable</literal>, this "
+"order of steps is recommended:"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1814
+#: pkgs.dbk:1884
msgid ""
"Make sure that the package's bugs that the NMU is meant to address are all "
"filed in the Debian Bug Tracking System (BTS). If they are not, submit them "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1821
+#: pkgs.dbk:1891
msgid ""
"Wait a few days for the response from the maintainer. If you don't get any "
"response, you may want to help them by sending the patch that fixes the "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1828
+#: pkgs.dbk:1898
msgid ""
"Wait a few more days. If you still haven't got an answer from the "
"maintainer, send them a mail announcing your intent to NMU the package. "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1838
+#: pkgs.dbk:1908
msgid ""
"Upload your package to incoming in <filename>DELAYED/7-day</filename> (cf. "
"<xref linkend=\"delayed-incoming\"/> ), send the final patch to the "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1846
+#: pkgs.dbk:1916
msgid ""
"Follow what happens, you're responsible for any bug that you introduced with "
"your NMU. You should probably use <xref linkend=\"pkg-tracking-system\"/> "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1853
+#: pkgs.dbk:1923
msgid ""
"At times, the release manager or an organized group of developers can "
"announce a certain period of time in which the NMU rules are relaxed. This "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1862
+#: pkgs.dbk:1932
msgid ""
-"For the testing distribution, the rules may be changed by the release "
-"managers. Please take additional care, and acknowledge that the usual way "
-"for a package to enter testing is through unstable."
+"For the <literal>testing</literal> distribution, the rules may be changed by "
+"the release managers. Please take additional care, and acknowledge that the "
+"usual way for a package to enter <literal>testing</literal> is through "
+"<literal>unstable</literal>."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1867
+#: pkgs.dbk:1938
msgid ""
"For the stable distribution, please take extra care. Of course, the release "
"managers may also change the rules here. Please verify before you upload "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1873
+#: pkgs.dbk:1944
msgid ""
"When a security bug is detected, the security team may do an NMU, using "
"their own rules. Please refer to <xref linkend=\"bug-security\"/> for more "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1878
+#: pkgs.dbk:1949
msgid ""
"For the differences for Porters NMUs, please see <xref linkend=\"source-nmu-"
"when-porter\"/> ."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1882
+#: pkgs.dbk:1953
msgid ""
"Of course, it is always possible to agree on special rules with a maintainer "
"(like the maintainer asking please upload this fix directly for me, and no "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1889
+#: pkgs.dbk:1960
msgid "NMU version numbering"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1891
+#: pkgs.dbk:1962
msgid ""
"Whenever you have made a change to a package, no matter how trivial, the "
"version number needs to change. This enables our packing system to function."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1895
+#: pkgs.dbk:1966
msgid ""
"If you are doing a non-maintainer upload (NMU), you should add a new minor "
"version number to the <replaceable>debian-revision</replaceable> part of the "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1906
+#: pkgs.dbk:1977
msgid ""
"The Debian revision minor number is needed to avoid stealing one of the "
"package maintainer's version numbers, which might disrupt their work. It "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1912
+#: pkgs.dbk:1983
msgid ""
"If there is no <replaceable>debian-revision</replaceable> component in the "
"version number then one should be created, starting at `0.1' (but in case of "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1922
+#: pkgs.dbk:1993
msgid ""
-"If you upload a package to testing or stable, sometimes, you need to fork "
-"the version number tree. For this, version numbers like 1.1-3sarge0.1 could "
-"be used."
+"If you upload a package to <literal>testing</literal> or <literal>stable </"
+"literal>, sometimes, you need to fork the version number tree. For this, "
+"version numbers like 1.1-3sarge0.1 could be used."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1929
+#: pkgs.dbk:2000
msgid "Source NMUs must have a new changelog entry"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1931
+#: pkgs.dbk:2002
msgid ""
"Anyone who is doing a source NMU must create a changelog entry, describing "
"which bugs are fixed by the NMU, and generally why the NMU was required and "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1937
+#: pkgs.dbk:2008
msgid "By convention, source NMU changelog entries start with the line"
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:1939
+#: pkgs.dbk:2010
#, fuzzy, no-wrap
msgid ""
"\n"
msgstr "* Non-maintainer upload"
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1945
+#: pkgs.dbk:2016
msgid "Source NMUs and the Bug Tracking System"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1947
+#: pkgs.dbk:2018
msgid ""
"Maintainers other than the official package maintainer should make as few "
"changes to the package as possible, and they should always send a patch as a "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1953
+#: pkgs.dbk:2024
msgid ""
"What if you are simply recompiling the package? If you just need to "
"recompile it for a single architecture, then you may do a binary-only NMU as "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1960
+#: pkgs.dbk:2031
msgid ""
"Bugs fixed by source NMUs used to be tagged fixed instead of closed, but "
"since version tracking is in place, such bugs are now also closed with the "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1965
+#: pkgs.dbk:2036
msgid ""
"Also, after doing an NMU, you have to send the information to the existing "
"bugs that are fixed by your NMU, including the unified diff. Historically, "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1976
+#: pkgs.dbk:2047
msgid ""
"In addition, the normal maintainer should <emphasis>always</emphasis> retain "
"the entry in the changelog file documenting the non-maintainer upload -- and "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1984
+#: pkgs.dbk:2055
msgid "Building source NMUs"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1986
+#: pkgs.dbk:2057
msgid ""
"Source NMU packages are built normally. Pick a distribution using the same "
"rules as found in <xref linkend=\"distribution\"/> , follow the other "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1991
+#: pkgs.dbk:2062
msgid ""
"Make sure you do <emphasis>not</emphasis> change the value of the maintainer "
"in the <filename>debian/control</filename> file. Your name as given in the "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1999
+#: pkgs.dbk:2070
msgid "Acknowledging an NMU"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2001
+#: pkgs.dbk:2072
msgid ""
"If one of your packages has been NMU'ed, you have to incorporate the changes "
"in your copy of the sources. This is easy, you just have to apply the patch "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2012
+#: pkgs.dbk:2083
msgid ""
"In any case, you should not be upset by the NMU. An NMU is not a personal "
"attack against the maintainer. It is a proof that someone cares enough "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2022
+#: pkgs.dbk:2093
msgid "NMU vs QA uploads"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2024
+#: pkgs.dbk:2095
msgid ""
"Unless you know the maintainer is still active, it is wise to check the "
"package to see if it has been orphaned. The current list of orphaned "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2034
+#: pkgs.dbk:2105
+#, fuzzy
msgid "Who can do an NMU"
msgstr "誰が NMU 可能なのか"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2036
+#: pkgs.dbk:2107
msgid ""
"Only official, registered Debian Developers can do binary or source NMUs. A "
"Debian Developer is someone who has their key in the Debian key ring. Non-"
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2046
+#: pkgs.dbk:2117
msgid "Terminology"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2048
+#: pkgs.dbk:2119
msgid ""
"There are two new terms used throughout this section: ``binary-only NMU'' "
"and ``source NMU''. These terms are used with specific technical meaning "
"throughout this document. Both binary-only and source NMUs are similar, "
"since they involve an upload of a package by a developer who is not the "
-"official maintainer of that package. That is why it's a <emphasis>non-"
-"maintainer</emphasis> upload."
+"official maintainer of that package. That is why it's a <literal>non-"
+"maintainer</literal> upload."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2056
+#: pkgs.dbk:2127
msgid ""
"A source NMU is an upload of a package by a developer who is not the "
"official maintainer, for the purposes of fixing a bug in the package. "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2065
+#: pkgs.dbk:2136
msgid ""
"A binary-only NMU is a recompilation and upload of a binary package for a "
"given architecture. As such, it is usually part of a porting effort. A "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2075
+#: pkgs.dbk:2146
msgid ""
"Both classes of NMUs, source and binary-only, can be lumped under the term "
"``NMU''. However, this often leads to confusion, since most people think "
msgstr ""
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:2085
+#: pkgs.dbk:2156
msgid "Collaborative maintenance"
msgstr "共同メンテナンス"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:2087
+#: pkgs.dbk:2158
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:2095
+#: pkgs.dbk:2166
msgid ""
"Generally there is a primary maintainer and one or more co-maintainers. The "
"primary maintainer is the person whose name is listed in the "
"<literal>Maintainer</literal> field of the <filename>debian/control</"
-"filename> file. Co-maintainers are all the other maintainers."
+"filename> file. Co-maintainers are all the other maintainers, usually "
+"listed in the <literal>Uploaders</literal> field of the <filename>debian/"
+"control</filename> file."
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:2101
+#: pkgs.dbk:2174
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:2107
+#: pkgs.dbk:2180
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:2115
+#: pkgs.dbk:2188
msgid ""
"Add the co-maintainer's correct maintainer name and address to the "
-"<literal>Uploaders</literal> field in the global part of the "
+"<literal>Uploaders</literal> field in the first paragraph of the "
"<filename>debian/control</filename> file."
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><screen>
-#: pkgs.dbk:2119
+#: pkgs.dbk:2192
#, fuzzy, no-wrap
msgid ""
"\n"
msgstr "Uploaders: John Buzz <jbuzz@debian.org>, Adam Rex <arex@debian.org>"
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2125
+#: pkgs.dbk:2198
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:2131
+#: pkgs.dbk:2204
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:2140
+#: pkgs.dbk:2213
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:2147
+#: pkgs.dbk:2220
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:2155
+#: pkgs.dbk:2228
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 "
msgstr ""
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:2163
+#: pkgs.dbk:2236
msgid "The testing distribution"
msgstr "テスト版ディストリビューション"
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2165
+#: pkgs.dbk:2238
msgid "Basics"
msgstr "基本"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2167
+#: pkgs.dbk:2240
msgid ""
-"Packages are usually installed into the `testing' distribution after they "
-"have undergone some degree of testing in unstable."
+"Packages are usually installed into the <literal>testing</literal> "
+"distribution after they have undergone some degree of <literal>testing</"
+"literal> in <literal>unstable</literal>."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2171
+#: pkgs.dbk:2245
msgid ""
"They must be in sync on all architectures and mustn't have dependencies that "
"make them uninstallable; they also have to have generally no known release-"
-"critical bugs at the time they're installed into testing. This way, "
-"`testing' should always be close to being a release candidate. Please see "
-"below for details."
+"critical bugs at the time they're installed into <literal>testing </"
+"literal>. This way, <literal>testing</literal> should always be close to "
+"being a release candidate. Please see below for details."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2180
+#: pkgs.dbk:2254
msgid "Updates from unstable"
msgstr "不安定版からの更新"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2182
+#: pkgs.dbk:2256
msgid ""
-"The scripts that update the <emphasis>testing</emphasis> distribution are "
-"run each day after the installation of the updated packages; these scripts "
-"are called <emphasis>britney</emphasis>. They generate the "
-"<filename>Packages</filename> files for the <emphasis>testing</emphasis> "
+"The scripts that update the <literal>testing</literal> distribution are run "
+"twice each day, right after the installation of the updated packages; these "
+"scripts are called <literal>britney</literal>. They generate the "
+"<filename>Packages</filename> files for the <literal>testing</literal> "
"distribution, but they do so in an intelligent manner; they try to avoid any "
"inconsistency and to use only non-buggy packages."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2190
+#: pkgs.dbk:2264
msgid ""
-"The inclusion of a package from <emphasis>unstable</emphasis> is conditional "
+"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:2196
+#: pkgs.dbk:2270
msgid ""
-"The package must have been available in <emphasis>unstable</emphasis> for 2, "
-"5 or 10 days, depending on the urgency (high, medium or low). Please note "
+"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 testing transition is taken into account. Those delays may be "
-"doubled during a freeze, or testing transitions may be switched off "
-"altogether;"
+"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;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2205
+#: pkgs.dbk:2280
msgid ""
-"It must have the same number or fewer release-critical bugs than the version "
-"currently available in <emphasis>testing</emphasis>;"
+"It must not have new release-critical bugs (RC bugs affecting the version "
+"available in <literal>unstable</literal>, but not affecting the version in "
+"<literal>testing</literal>);"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2211
+#: pkgs.dbk:2287
msgid ""
"It must be available on all architectures on which it has previously been "
-"built in unstable. <xref linkend=\"madison\"/> may be of interest to check "
-"that information;"
+"built in <literal>unstable</literal>. <xref linkend=\"dak-ls\"/> may be of "
+"interest to check that information;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2218
+#: pkgs.dbk:2294
msgid ""
"It must not break any dependency of a package which is already available in "
-"<emphasis>testing</emphasis>;"
+"<literal>testing</literal>;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2224
+#: pkgs.dbk:2300
msgid ""
"The packages on which it depends must either be available in "
-"<emphasis>testing</emphasis> or they must be accepted into "
-"<emphasis>testing</emphasis> at the same time (and they will be if they "
-"fulfill all the necessary criteria);"
+"<literal>testing</literal> or they must be accepted into <literal>testing</"
+"literal> at the same time (and they will be if they fulfill all the "
+"necessary criteria);"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2232
+#: pkgs.dbk:2308
msgid ""
-"To find out whether a package is progressing into testing or not, see the "
-"testing script output on the <ulink url=\"&url-testing-maint;\">web page of "
-"the testing distribution</ulink>, or use the program <command>grep-excuses</"
-"command> which is in the <systemitem role=\"package\">devscripts</"
-"systemitem> package. This utility can easily be used in a <citerefentry> "
-"<refentrytitle>crontab</refentrytitle> <manvolnum>5</manvolnum> </"
-"citerefentry> to keep yourself informed of the progression of your packages "
-"into <emphasis>testing</emphasis>."
+"To find out whether a package is progressing into <literal>testing</literal> "
+"or not, see the <literal>testing</literal> script output on the <ulink url="
+"\"&url-testing-maint;\">web page of the testing distribution</ulink>, or use "
+"the program <command>grep-excuses</command> which is in the <systemitem role="
+"\"package\">devscripts</systemitem> package. This utility can easily be "
+"used in a <citerefentry> <refentrytitle>crontab</refentrytitle> "
+"<manvolnum>5</manvolnum> </citerefentry> to keep yourself informed of the "
+"progression of your packages into <literal>testing</literal>."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2243
+#: pkgs.dbk:2319
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:2250
+#: pkgs.dbk:2326
msgid ""
-"Sometimes, some packages never enter <emphasis>testing</emphasis> because "
-"the set of inter-relationship is too complicated and cannot be sorted out by "
-"the scripts. See below for details."
+"Sometimes, some packages never enter <literal>testing</literal> because the "
+"set of inter-relationship is too complicated and cannot be sorted out by the "
+"scripts. See below for details."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2255
+#: pkgs.dbk:2331
msgid ""
-"Some further dependency analysis is shown on <ulink url=\"http://bjorn.haxx."
-"se/debian/\"></ulink> — but be warned, this page also shows build "
+"Some further dependency analysis is shown on <ulink url=\"http://release."
+"debian.org/migration/\"></ulink> — but be warned, this page also shows build "
"dependencies which are not considered by britney."
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2260
+#: pkgs.dbk:2336
msgid "out-of-date"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
#. FIXME: better rename this file than document rampant professionalism?
-#: pkgs.dbk:2263
+#: pkgs.dbk:2339
msgid ""
-"For the testing migration script, outdated means: There are different "
-"versions in unstable for the release architectures (except for the "
-"architectures in fuckedarches; fuckedarches is a list of architectures that "
-"don't keep up (in update_out.py), but currently, it's empty). outdated has "
-"nothing whatsoever to do with the architectures this package has in testing."
+"For the <literal>testing</literal> migration script, outdated means: There "
+"are different versions in <literal>unstable</literal> for the release "
+"architectures (except for the architectures in fuckedarches; fuckedarches is "
+"a list of architectures that don't keep up (in <filename>update_out.py</"
+"filename>), but currently, it's empty). outdated has nothing whatsoever to "
+"do with the architectures this package has in <literal>testing</literal>."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2270
+#: pkgs.dbk:2347
msgid "Consider this example:"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2277 pkgs.dbk:2308
+#: pkgs.dbk:2354 pkgs.dbk:2387
msgid "alpha"
msgstr "alpha"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2278 pkgs.dbk:2309
+#: pkgs.dbk:2355 pkgs.dbk:2388
msgid "arm"
msgstr "arm"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2283 pkgs.dbk:2315 pkgs.dbk:2375
+#: pkgs.dbk:2360 pkgs.dbk:2394 pkgs.dbk:2456
msgid "testing"
msgstr "テスト版"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2284 pkgs.dbk:2289 pkgs.dbk:2316 pkgs.dbk:2317 pkgs.dbk:2324
+#: pkgs.dbk:2361 pkgs.dbk:2366 pkgs.dbk:2395 pkgs.dbk:2396 pkgs.dbk:2403
msgid "1"
msgstr "1"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2285 pkgs.dbk:2318 pkgs.dbk:2323
+#: pkgs.dbk:2362 pkgs.dbk:2397 pkgs.dbk:2402
msgid "-"
msgstr "-"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2288 pkgs.dbk:2321 pkgs.dbk:2376
+#: pkgs.dbk:2365 pkgs.dbk:2400 pkgs.dbk:2457
msgid "unstable"
msgstr "不安定版"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2290 pkgs.dbk:2322
+#: pkgs.dbk:2367 pkgs.dbk:2401
msgid "2"
msgstr "2"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2296
+#: pkgs.dbk:2373
msgid ""
-"The package is out of date on alpha in unstable, and will not go to "
-"testing. And removing foo from testing would not help at all, the package "
-"is still out of date on alpha, and will not propagate to testing."
+"The package is out of date on alpha in <literal>unstable</literal>, and will "
+"not go to <literal>testing</literal>. Removing the package would not help at "
+"all, the package is still out of date on <literal>alpha</literal>, and will "
+"not propagate to testing."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2301
-msgid "However, if ftp-master removes a package in unstable (here on arm):"
+#: pkgs.dbk:2379
+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:2310
+#: pkgs.dbk:2389
msgid "hurd-i386"
msgstr "hurd-i386"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2330
+#: pkgs.dbk:2409
msgid ""
"In this case, the package is up to date on all release architectures in "
-"unstable (and the extra hurd-i386 doesn't matter, as it's not a release "
-"architecture)."
+"<literal>unstable</literal> (and the extra <literal>hurd-i386</literal> "
+"doesn't matter, as it's not a release architecture)."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2335
+#: pkgs.dbk:2414
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:2342
+#: pkgs.dbk:2421
msgid "Removals from testing"
msgstr "テスト版からの削除"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2344
+#: pkgs.dbk:2423
msgid ""
"Sometimes, a package is removed to allow another package in: This happens "
"only to allow <emphasis>another</emphasis> package to go in if it's ready in "
-"every other sense. Suppose e.g. that <emphasis>a</emphasis> cannot be "
-"installed with the new version of <emphasis>b</emphasis>; then <emphasis>a</"
-"emphasis> may be removed to allow <emphasis>b</emphasis> in."
+"every other sense. Suppose e.g. that <literal>a</literal> cannot be "
+"installed with the new version of <literal>b</literal>; then <literal>a</"
+"literal> may be removed to allow <literal>b</literal> in."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2351
+#: pkgs.dbk:2430
msgid ""
-"Of course, there is another reason to remove a package from testing: It's "
-"just too buggy (and having a single RC-bug is enough to be in this state)."
+"Of course, there is another reason to remove a package from <literal>testing "
+"</literal>: It's just too buggy (and having a single RC-bug is enough to be "
+"in this state)."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2355
+#: pkgs.dbk:2435
msgid ""
-"Furthermore, if a package has been removed from unstable, and no package in "
-"testing depends on it any more, then it will automatically be removed."
+"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 "
+"will automatically be removed."
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2361
+#: pkgs.dbk:2442
msgid "circular dependencies"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2363
+#: pkgs.dbk:2444
msgid ""
"A situation which is not handled very well by britney is if package "
-"<emphasis>a</emphasis> depends on the new version of package <emphasis>b</"
-"emphasis>, and vice versa."
+"<literal>a</literal> depends on the new version of package <literal>b</"
+"literal>, and vice versa."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2368
+#: pkgs.dbk:2449
msgid "An example of this is:"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2381
+#: pkgs.dbk:2462
msgid "a"
msgstr "a"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2382
+#: pkgs.dbk:2463
msgid "1; depends: b=1"
msgstr "1; depends: b=1"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2383
+#: pkgs.dbk:2464
msgid "2; depends: b=2"
msgstr "2; depends: b=2"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2386
+#: pkgs.dbk:2467
msgid "b"
msgstr "b"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2387
+#: pkgs.dbk:2468
msgid "1; depends: a=1"
msgstr "1; depends: a=1"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2388
+#: pkgs.dbk:2469
msgid "2; depends: a=2"
msgstr "2; depends: a=2"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2394
+#: pkgs.dbk:2475
msgid ""
-"Neither package <emphasis>a</emphasis> nor package <emphasis>b</emphasis> is "
+"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:2398
+#: pkgs.dbk:2479
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:2405
+#: pkgs.dbk:2486
msgid "influence of package in testing"
msgstr "テスト版パッケージへの影響"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2407
+#: pkgs.dbk:2488
msgid ""
-"Generally, there is nothing that the status of a package in testing means "
-"for transition of the next version from unstable to testing, with two "
-"exceptions: If the RC-bugginess of the package goes down, it may go in even "
-"if it is still RC-buggy. The second exception is if the version of the "
-"package in testing is out of sync on the different arches: Then any arch "
+"Generally, there is nothing that the status of a package in <literal>testing "
+"</literal> means for transition of the next version from <literal>unstable </"
+"literal> to <literal>testing</literal>, with two exceptions: If the RC-"
+"bugginess of the package goes down, it may go in even if it is still RC-"
+"buggy. The second exception is if the version of the package in <literal> "
+"testing</literal> is out of sync on the different arches: Then any arch "
"might just upgrade to the version of the source package; however, this can "
"happen only if the package was previously forced through, the arch is in "
"fuckedarches, or there was no binary package of that arch present in "
-"unstable at all during the testing migration."
+"<literal>unstable </literal> at all during the <literal>testing</literal> "
+"migration."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2417
+#: pkgs.dbk:2500
msgid ""
-"In summary this means: The only influence that a package being in testing "
-"has on a new version of the same package is that the new version might go in "
-"easier."
+"In summary this means: The only influence that a package being in <literal> "
+"testing</literal> has on a new version of the same package is that the new "
+"version might go in easier."
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2424
+#: pkgs.dbk:2507
msgid "details"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2426
+#: pkgs.dbk:2509
msgid "If you are interested in details, this is how britney works:"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2429
+#: pkgs.dbk:2512
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:2438
+#: pkgs.dbk:2521
msgid ""
-"Now, the more complex part happens: Britney tries to update testing with the "
-"valid candidates; first, each package alone, and then larger and even larger "
-"sets of packages together. Each try is accepted if testing is not more "
-"uninstallable after the update than before. (Before and after this part, "
-"some hints are processed; but as only release masters can hint, this is "
-"probably not so important for you.)"
+"Now, the more complex part happens: Britney tries to update <literal>testing "
+"</literal> with the valid candidates. For that, britney tries to add each "
+"valid candidate to the testing distribution. If the number of uninstallable "
+"packages in <literal>testing</literal> doesn't increase, the package is "
+"accepted. From that point on, the accepted package is considered to be part "
+"of <literal>testing</literal>, such that all subsequent installability tests "
+"include this package. Hints from the release team are processed before or "
+"after this main run, depending on the exact type."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2446
+#: pkgs.dbk:2531
msgid ""
-"If you want to see more details, you can look it up on merkel:/org/&ftp-"
-"debian-org;/testing/update_out/ (or there in ~aba/testing/update_out to see "
-"a setup with a smaller packages file). Via web, it's at <ulink url=\"http://"
-"&ftp-master-host;/testing/update_out_code/\"></ulink>"
+"If you want to see more details, you can look it up on <filename>merkel:/org/"
+"&ftp-debian-org;/testing/update_out/</filename> (or in <filename>merkel:~aba/"
+"testing/update_out</filename> to see a setup with a smaller packages file). "
+"Via web, it's at <ulink url=\"http://&ftp-master-host;/testing/"
+"update_out_code/\"></ulink>"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2453
+#: pkgs.dbk:2538
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:2461
+#: pkgs.dbk:2546
msgid "Direct updates to testing"
msgstr "直接テスト版を更新する"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2463
+#: pkgs.dbk:2548
msgid ""
-"The testing distribution is fed with packages from unstable according to the "
-"rules explained above. However, in some cases, it is necessary to upload "
-"packages built only for testing. For that, you may want to upload to "
-"<emphasis>testing-proposed-updates</emphasis>."
+"The <literal>testing</literal> distribution is fed with packages from "
+"<literal>unstable</literal> according to the rules explained above. "
+"However, in some cases, it is necessary to upload packages built only for "
+"<literal> testing</literal>. For that, you may want to upload to <literal> "
+"testing-proposed-updates</literal>."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2469
+#: pkgs.dbk:2555
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:2476
+#: pkgs.dbk:2562
msgid ""
-"You should not upload to <emphasis>testing-proposed-updates</emphasis> when "
-"you can update your packages through <emphasis>unstable</emphasis>. If you "
+"You should not upload to <literal>testing-proposed-updates</literal> when "
+"you can update your packages through <literal>unstable</literal>. If you "
"can't (for example because you have a newer development version in "
-"unstable), you may use this facility, but it is recommended that you ask for "
-"authorization from the release manager first. Even if a package is frozen, "
-"updates through unstable are possible, if the upload via unstable does not "
-"pull in any new dependencies."
+"<literal>unstable </literal>), you may use this facility, but it is "
+"recommended that you ask for authorization from the release manager first. "
+"Even if a package is frozen, updates through <literal>unstable</literal> are "
+"possible, if the upload via <literal>unstable</literal> does not pull in any "
+"new dependencies."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2485
+#: pkgs.dbk:2571
msgid ""
-"Version numbers are usually selected by adding the codename of the testing "
-"distribution and a running number, like 1.2sarge1 for the first upload "
-"through testing-proposed-updates of package version 1.2."
+"Version numbers are usually selected by adding the codename of the "
+"<literal>testing</literal> distribution and a running number, like "
+"<literal>1.2sarge1</literal> for the first upload through <literal>testing-"
+"proposed-updates</literal> of package version <literal>1.2</literal>."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2490
+#: pkgs.dbk:2578
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:2495
+#: pkgs.dbk:2583
msgid ""
-"Make sure that your package really needs to go through <emphasis>testing-"
-"proposed-updates</emphasis>, and can't go through unstable;"
+"Make sure that your package really needs to go through <literal>testing-"
+"proposed-updates</literal>, and can't go through <literal> unstable</"
+"literal>;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2501
+#: pkgs.dbk:2590
msgid "Make sure that you included only the minimal amount of changes;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2506
+#: pkgs.dbk:2595
msgid ""
"Make sure that you included an appropriate explanation in the changelog;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2511
+#: pkgs.dbk:2600
msgid ""
-"Make sure that you've written <emphasis>testing</emphasis> or "
-"<emphasis>testing-proposed-updates</emphasis> into your target distribution;"
+"Make sure that you've written <literal>testing</literal> or <literal>testing-"
+"proposed-updates</literal> into your target distribution;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2517
+#: pkgs.dbk:2606
msgid ""
-"Make sure that you've built and tested your package in <emphasis>testing</"
-"emphasis>, not in <emphasis>unstable</emphasis>;"
+"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:2523
+#: pkgs.dbk:2612
msgid ""
"Make sure that your version number is higher than the version in "
-"<emphasis>testing</emphasis> and <emphasis>testing-proposed-updates</"
-"emphasis>, and lower than in <emphasis>unstable</emphasis>;"
+"<literal>testing</literal> and <literal>testing-proposed-updates</literal>, "
+"and lower than in <literal>unstable</literal>;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2530
+#: pkgs.dbk:2619
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:2538
+#: pkgs.dbk:2627
msgid "Frequently asked questions"
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2540
+#: pkgs.dbk:2629
msgid "What are release-critical bugs, and how do they get counted?"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2542
+#: pkgs.dbk:2631
msgid ""
"All bugs of some higher severities are by default considered release-"
-"critical; currently, these are critical, grave, and serious bugs."
+"critical; currently, these are <literal>critical</literal>, <literal>grave</"
+"literal> and <literal>serious</literal> bugs."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2546
+#: pkgs.dbk:2636
msgid ""
"Such bugs are presumed to have an impact on the chances that the package "
-"will be released with the stable release of Debian: in general, if a package "
-"has open release-critical bugs filed on it, it won't get into testing, and "
-"consequently won't be released in stable."
+"will be released with the <literal>stable</literal> release of Debian: in "
+"general, if a package has open release-critical bugs filed on it, it won't "
+"get into <literal>testing</literal>, and consequently won't be released in "
+"<literal> stable</literal>."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2552
+#: pkgs.dbk:2643
msgid ""
-"The unstable bug count are all release-critical bugs without either any "
-"release-tag (such as potato, woody) or with release-tag sid; also, only if "
-"they are neither fixed nor set to sarge-ignore. The testing bug count for a "
-"package is considered to be roughly the bug count of unstable count at the "
-"last point when the testing version equalled the unstable version."
-msgstr ""
-
-# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2559
-msgid ""
-"This will change post-sarge, as soon as we have versions in the bug tracking "
-"system."
+"The <literal>unstable</literal> bug count are all release-critical bugs "
+"which are marked to apply to <replaceable>package</replaceable>/"
+"<replaceable>version </replaceable> combinations that are available in "
+"unstable for a release architecture. The <literal>testing</literal> bug "
+"count is defined analogously."
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2565
+#: pkgs.dbk:2651
msgid ""
-"How could installing a package into testing possibly break other packages?"
+"How could installing a package into <literal>testing</literal> possibly "
+"break other packages?"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2567
+#: pkgs.dbk:2654
msgid ""
"The structure of the distribution archives is such that they can only "
"contain one version of a package; a package is defined by its name. So when "
-"the source package acmefoo is installed into testing, along with its binary "
-"packages acme-foo-bin, acme-bar-bin, libacme-foo1 and libacme-foo-dev, the "
-"old version is removed."
+"the source package <literal>acmefoo</literal> is installed into "
+"<literal>testing</literal>, along with its binary packages <literal>acme-foo-"
+"bin</literal>, <literal> acme-bar-bin</literal>, <literal>libacme-foo1</"
+"literal> and <literal> libacme-foo-dev</literal>, the old version is removed."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2574
+#: pkgs.dbk:2662
msgid ""
"However, the old version may have provided a binary package with an old "
-"soname of a library, such as libacme-foo0. Removing the old acmefoo will "
-"remove libacme-foo0, which will break any packages which depend on it."
+"soname of a library, such as <literal>libacme-foo0</literal>. Removing the "
+"old <literal>acmefoo</literal> will remove <literal>libacme-foo0</literal>, "
+"which will break any packages which depend on it."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2579
+#: pkgs.dbk:2668
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:2585
+#: pkgs.dbk:2674
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 "
"updated to depend on the new binaries instead. Because installing such a "
-"source package into testing breaks all the packages that depended on it in "
-"testing, some care has to be taken now: all the depending packages must be "
-"updated and ready to be installed themselves so that they won't be broken, "
-"and, once everything is ready, manual intervention by the release manager or "
-"an assistant is normally required."
+"source package into <literal>testing</literal> breaks all the packages that "
+"depended on it in <literal>testing</literal>, some care has to be taken now: "
+"all the depending packages must be updated and ready to be installed "
+"themselves so that they won't be broken, and, once everything is ready, "
+"manual intervention by the release manager or an assistant is normally "
+"required."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2595
+#: pkgs.dbk:2685
msgid ""
"If you are having problems with complicated groups of packages like this, "
-"contact debian-devel or debian-release for help."
+"contact &email-debian-devel; or &email-debian-release; for help."
msgstr ""
+# type: Content of: <chapter><section><section><title>
+#, fuzzy
+#~ msgid "Using the <literal>DELAYED/</literal> queue"
+#~ msgstr "<literal>ftp-master</literal> にアップロードする"
~ianmdlvl / developers-reference.git / blobdiff