# Debian Developer's Reference (Japanese)
-# Hideki Yamane (Debian-JP) <henrich@debian.or.jp>, 2008.
+# Hideki Yamane (Debian-JP) <henrich@debian.or.jp>, 2008-2010.
#
msgid ""
msgstr ""
-"Project-Id-Version: developers-reference 3.3.9\n"
-"POT-Creation-Date: 2008-06-14 14:15+0900\n"
-"PO-Revision-Date: 2008-03-05 18:30+0900\n"
+"Project-Id-Version: developers-reference 3.4.4\n"
+"POT-Creation-Date: 2010-01-04 00:17+0100\n"
+"PO-Revision-Date: 2010-01-05 18:27+0900\n"
"Last-Translator: Hideki Yamane (Debian-JP) <henrich@debian.or.jp>\n"
"Language-Team: Debian JP Project <debian-doc@debian.or.jp>\n"
"MIME-Version: 1.0\n"
"Content-Transfer-Encoding: 8bit\n"
# type: Content of: <chapter><title>
+#. type: Content of: <chapter><title>
#: pkgs.dbk:7
msgid "Managing Packages"
msgstr "パッケージの取扱い方"
# type: Content of: <chapter><para>
+#. type: Content of: <chapter><para>
#: pkgs.dbk:9
msgid ""
"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>
+#. type: Content of: <chapter><section><title>
#: pkgs.dbk:13
msgid "New packages"
msgstr "新規パッケージ"
# type: Content of: <chapter><section><para>
+#. type: Content of: <chapter><section><para>
#: pkgs.dbk:15
msgid ""
"If you want to create a new package for the Debian distribution, you should "
"duplicated. Read the <ulink url=\"&url-wnpp;\">WNPP web pages</ulink> for "
"more information."
msgstr ""
+"もしあなたが Debian ディストリビューションに対して新たなパッケージを作成した"
+"いという場合、まず <ulink url=\"&url-wnpp;\">作業が望まれるパッケージ (Work-"
+"Needing and Prospective Packages (WNPP))</ulink> の一覧をチェックする必要があ"
+"ります。WNPP 一覧をチェックすることで、まだ誰もそのソフトをパッケージ化してい"
+"ないことや、作業が重複していないことを確認します。詳細については <ulink url="
+"\"&url-wnpp;\">WNPP のページ</ulink> を読んでください。"
# type: Content of: <chapter><section><para>
+# FIXME: "but not limiting yourself to"?
+#. type: Content of: <chapter><section><para>
#: pkgs.dbk:23
msgid ""
"Assuming no one else is already working on your prospective package, you "
"a description of the package, the license of the prospective package, and "
"the current URL where it can be downloaded from."
msgstr ""
+"パッケージ化しようとしているソフトについて誰もまだ作業していないようであれ"
+"ば、まずは <systemitem role=\"package\">wnpp</systemitem> 擬似パッケージ "
+"(pseudo-package) に対してバグ報告を投稿する必要があります (<xref linkend="
+"\"submit-bug\"/>)。このバグ報告には、新規パッケージの作成予定や、パッケージの"
+"説明 (自分自身が分かるだけではないもの)、作業しようとしているパッケージのライ"
+"センス、ダウンロードが可能な現在の URL を含めます。"
# type: Content of: <chapter><section><para>
+#. type: Content of: <chapter><section><para>
#: pkgs.dbk:31
msgid ""
"You should set the subject of the bug to <literal>ITP: <replaceable>foo</"
"instead. This will inform the other developers about upcoming packages and "
"will allow a review of your description and package name."
msgstr ""
+"サブジェクトを <literal>ITP: <replaceable>foo</replaceable> -- "
+"<replaceable>short description</replaceable></literal> に設定する必要がありま"
+"す。ここでは <replaceable>foo</replaceable> は新規パッケージの名前に置き換え"
+"ます。バグ報告の重要度は <literal>wishlist</literal> に設定しなければなりませ"
+"ん。X-Debbugs-CC ヘッダを使ってコピーを &email-debian-devel; に送信してくださ"
+"い (CC: は使わないでください。CC: を使った場合はメールのサブジェクトがバグ番"
+"号を表示しないためです)。大量の新規パッケージの作成 (11 個以上) を行っている"
+"場合、メーリングリストへ個別に通知するのは鬱陶しいので、代わりにバグを登録し"
+"た後で要約を送信してください。これによって、他の開発者らに次に来るパッケージ"
+"を知らせ、説明とパッケージ名のレビューが可能になります。"
# type: Content of: <chapter><section><para>
+#. type: Content of: <chapter><section><para>
#: pkgs.dbk:45
msgid ""
"Please include a <literal>Closes: bug#<replaceable>nnnnn</replaceable></"
"report to be automatically closed once the new package is installed in the "
"archive (see <xref linkend=\"upload-bugfix\"/> )."
msgstr ""
+"新規パッケージがアーカイブへインストールされる際にバグ報告を自動的に閉じるた"
+"め、<literal>Closes: bug#<replaceable>nnnnn</replaceable></literal> というエ"
+"ントリを新規パッケージの changelog 内に含めてください (<xref linkend="
+"\"upload-bugfix\"/> を参照)。"
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: pkgs.dbk:51
msgid ""
+"If you think your package needs some explanations for the administrators of "
+"the NEW package queue, include them in your changelog, send to "
+"ftpmaster@debian.org a reply to the email you receive as a maintainer after "
+"your upload, or reply to the rejection email in case you are already re-"
+"uploading."
+msgstr ""
+"パッケージについて、NEW パッケージキューの管理者への説明が必要だろうと思う場"
+"合は、アップロード後にメンテナとして受け取るメールへの返信、あるいは既に再"
+"アップロードという場合は reject のメールに対しての返信として、説明を "
+"changelog に含めて ftpmaster@debian.org へ送ってください。"
+
+# type: Content of: <chapter><section><para>
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:57
+msgid ""
"When closing security bugs include CVE numbers as well as the Closes: "
"#nnnnn. This is useful for the security team to track vulnerabilities. If "
"an upload is made to fix the bug before the advisory ID is known, it is "
"Even in this case, please include all available pointers to background "
"information in the original changelog entry."
msgstr ""
+"セキュリティバグを閉じる場合は、CVE 番号を Closes: #nnnnnn と同じように含める"
+"ようにしてください。これは、セキュリティチームが脆弱性を追跡するのに役立ちま"
+"す。アドバイザリの ID が分かる前にバグ修正のためのアップロードが行われた場合"
+"は、以前の changelog エントリを次のアップロード時に修正するのが推奨されていま"
+"す。このような場合でも、元々の changelog での記載に、可能な限り背景情報へのポ"
+"インタを全て含めてください。"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:59
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:65
+#, fuzzy
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:65
+#. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:71
+#, fuzzy
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 "
"already."
-msgstr ""
+msgstr "(潜在的な新たな) メンテナ"
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:71
+#. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:77
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:77
+#. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:83
msgid ""
"It lets the rest of the maintainers know more about the package than the one "
"line description and the usual changelog entry ``Initial release'' that gets "
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:84
+#. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:90
msgid ""
"It is helpful to the people who live off <literal>unstable</literal> (and "
"form our first line of testers). We should encourage these people."
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:90
+#. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:96
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:96
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:102
msgid ""
"Please see <ulink url=\"http://&ftp-master-host;/REJECT-FAQ.html\"></ulink> "
"for common rejection reasons for a new package."
msgstr ""
+"新しいパッケージに対する一般的な拒否理由については <ulink url=\"http://&ftp-"
+"master-host;/REJECT-FAQ.html\"></ulink> を参照してください。"
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:102
+#. type: Content of: <chapter><section><title>
+#: pkgs.dbk:108
msgid "Recording changes in the package"
msgstr "パッケージの変更を記録する"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:104
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:110
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:115
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:121
msgid ""
"The <filename>debian/changelog</filename> file conforms to a certain "
"structure, with a number of different fields. One field of note, the "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:123
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:129
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 ""
+"changelog への記載は、パッケージがアーカイブにインストールされる際、自動的に "
+"Debian バグを閉じるのに利用できます。<xref linkend=\"upload-bugfix\"/> を参照"
+"してください。"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:127
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:133
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:130
-#, fuzzy, no-wrap
-msgid ""
-"\n"
-" * new upstream version\n"
-msgstr "* new upstream version"
+#. type: Content of: <chapter><section><screen>
+#: pkgs.dbk:137
+#, no-wrap
+msgid " * new upstream version\n"
+msgstr " * new upstream version\n"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:134
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:140
+#, fuzzy
msgid ""
"There are tools to help you create entries and finalize the "
"<filename>changelog</filename> for release — see <xref linkend=\"devscripts"
"\"/> and <xref linkend=\"dpkg-dev-el\"/> ."
msgstr ""
+"<filename>changelog</filename> <xref linkend=\"devscripts\"/> と <xref "
+"linkend=\"dpkg-dev-el\"/> を参照してください。"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:139
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:145
msgid "See also <xref linkend=\"bpp-debian-changelog\"/> ."
msgstr "<xref linkend=\"bpp-debian-changelog\"/> も参照してください。"
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:144
+#. type: Content of: <chapter><section><title>
+#: pkgs.dbk:150
msgid "Testing the package"
msgstr "パッケージをテストする"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:146
+# FIXME: around
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:152
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 "
"older version of the same Debian package around):"
msgstr ""
+"パッケージをアップロードする前に、基本的なテストをする必要があります。最低"
+"限、以下の作業が必要です (同じ Debian パッケージの古いバージョンなどが必要に"
+"なるでしょう):"
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:153
+#. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:159
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 "
"exists."
msgstr ""
+"パッケージをインストールしてソフトウェアが動作するのを確認する、あるいは既に"
+"そのソフトの Debian パッケージが存在している場合、パッケージを以前のバージョ"
+"ンから新しいバージョンにアップグレードする。"
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:160
+#. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:166
msgid ""
"Run <command>lintian</command> over the package. You can run "
"<command>lintian</command> as follows: <literal>lintian -v "
"the <literal>-i</literal> switch, which will cause <command>lintian</"
"command> to output a very verbose description of the problem."
msgstr ""
+"パッケージに対して <command>lintian</command> を実行する。以下のようにして "
+"<command>lintian</command> を実行できます: <literal>lintian -v "
+"<replaceable>package-version</replaceable>.changes</literal> 。"
+"<command>lintian</command> が生成した出力を理解していない場合は、"
+"<command>lintian</command> が問題の説明を非常に冗長に出力するようにする "
+"<literal>-i</literal> オプションを付けて実行してみてください。"
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:169
+#. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:175
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 ""
+"通常、lintian がエラーを出力するようであれば、パッケージをアップロードしては"
+"<emphasis>いけません</emphasis> (エラーは <literal>E</literal> で始まりま"
+"す)。"
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:173
+#. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:179
msgid ""
"For more information on <command>lintian</command>, see <xref linkend="
"\"lintian\"/> ."
msgstr ""
+"<command>lintian</command> についての詳細は、<xref linkend=\"lintian\"/> を参"
+"照してください。"
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:179
+#. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:185
msgid ""
"Optionally run <xref linkend=\"debdiff\"/> to analyze changes from an older "
"version, if one exists."
msgstr ""
+"もし古いバージョンがあれば、それからの変更点を分析するために追加で <xref "
+"linkend=\"debdiff\"/> を実行する。"
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:185
+#. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:191
msgid ""
"Downgrade the package to the previous version (if one exists) — this tests "
"the <filename>postrm</filename> and <filename>prerm</filename> scripts."
msgstr ""
+"(もしあれば) 以前のバージョンにダウングレードする — これは <filename>postrm</"
+"filename> スクリプトと <filename>prerm</filename> スクリプトをテストします。"
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:191
-#, fuzzy
+#. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:197
msgid "Remove the package, then reinstall it."
-msgstr "ã\83\91ã\83\83ã\82±ã\83¼ã\82¸ã\82\92å\89\8aé\99¤ã\81\97ã\81¦ã\80\81å\86\8dã\82¤ã\83³ã\82¹ã\83\88ã\83¼ã\83«ã\81\97ã\81¦ã\81\8fã\81 ã\81\95ã\81\84。"
+msgstr "ã\83\91ã\83\83ã\82±ã\83¼ã\82¸ã\82\92å\89\8aé\99¤ã\81\97ã\81¦ã\80\81å\86\8dã\82¤ã\83³ã\82¹ã\83\88ã\83¼ã\83«ã\81\99ã\82\8b。"
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:196
+#. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:202
+#, fuzzy
msgid ""
"Copy the source package in a different directory and try unpacking it and "
"rebuilding it. This tests if the package relies on existing files outside "
"of it, or if it relies on permissions being preserved on the files shipped "
"inside the .diff.gz file."
msgstr ""
+"ソースパッケージを違うディレクトリにコピーして展開し、再構築する。これは、"
+"パッケージが外部の既存ファイルに依存しているかどうか、.diff.gz ファイル内に含"
+"まれているファイル"
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:206
-#, fuzzy
+#. type: Content of: <chapter><section><title>
+#: pkgs.dbk:212
msgid "Layout of the source package"
-msgstr "ã\82½ã\83¼ã\82¹ã\83\91ã\83\83ã\82±ã\83¼ã\82¸ã\81®æ§\8bé\80 "
+msgstr "ã\82½ã\83¼ã\82¹ã\83\91ã\83\83ã\82±ã\83¼ã\82¸ã\81®æ¦\82è¦\81"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:208
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:214
msgid "There are two types of Debian source packages:"
msgstr "Debian のソースパッケージには 2 種類あります："
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:213
+#. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:219
msgid ""
"the so-called <literal>native</literal> packages, where there is no "
"distinction between the original sources and the patches applied for Debian"
msgstr ""
-# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:219
+#
. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:225
msgid ""
"the (more common) packages where there's an original source tarball file "
-"accompanied by another file that contains the patches applied for Debian"
+"accompanied by another file that contains the changes made by Debian"
msgstr ""
-# type: Content of: <chapter><section><para>
-#: pkgs.dbk:225
+#
. type: Content of: <chapter><section><para>
+#: pkgs.dbk:231
msgid ""
"For the native packages, the source package includes a Debian source control "
-"file (<literal>.dsc</literal>) and the source tarball (<literal>.tar.gz</"
-"literal>). A source package of a non-native package includes a Debian "
-"source control file, the original source tarball (<literal>.orig.tar.gz</"
-"literal>) and the Debian patches (<literal>.diff.gz</literal>)."
+"file (<literal>.dsc</literal>) and the source tarball (<literal>.tar.{gz,bz2,"
+"lzma}</literal>). A source package of a non-native package includes a Debian "
+"source control file, the original source tarball (<literal>.orig.tar.{gz,bz2,"
+"lzma}</literal>) and the Debian changes (<literal>.diff.gz</literal> for the "
+"source format “1.0” or <literal>.debian.tar.{gz,bz2,lzma}</literal> for the "
+"source format “3.0 (quilt)”)."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: pkgs.dbk:233
+#
. type: Content of: <chapter><section><para>
+#: pkgs.dbk:240
msgid ""
-"Whether a package is native or not is determined when it is built by "
-"<citerefentry> <refentrytitle>dpkg-buildpackage</refentrytitle> "
-"<manvolnum>1</manvolnum> </citerefentry>. The rest of this section relates "
-"only to non-native packages."
+"With source format “1.0”, whether a package is native or not was determined "
+"by <command>dpkg-source</command> at build time. Nowadays it is recommended "
+"to be explicit about the desired source format by putting either “3.0 "
+"(quilt)” or “3.0 (native)” in <filename>debian/source/format</filename>. "
+"The rest of this section relates only to non-native packages."
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:239
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:247
msgid ""
"The first time a version is uploaded which corresponds to a particular "
"upstream version, the original source tar file should be uploaded and "
"filename> files, and will not need to be re-uploaded."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: pkgs.dbk:246
+#
. type: Content of: <chapter><section><para>
+#: pkgs.dbk:254
msgid ""
"By default, <command>dpkg-genchanges</command> and <command>dpkg-"
"buildpackage</command> will include the original source tar file if and only "
-"if the Debian revision part of the source version number is 0 or 1, "
-"indicating a new upstream version. This behavior may be modified by using "
-"<literal>-sa</literal> to always include it or <literal>-sd</literal> to "
-"always leave it out."
+"if the current changelog entry has a different upstream version from the "
+"preceding entry. This behavior may be modified by using <literal>-sa</"
+"literal> to always include it or <literal>-sd</literal> to always leave it "
+"out."
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:254
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:262
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>."
"byte-for-byte identical with the one already in the archive."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: pkgs.dbk:261
+#
. type: Content of: <chapter><section><para>
+#: pkgs.dbk:269
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 "
-"store file permissions in the patch."
+"not present in the .orig.tar.{gz,bz2} will not be preserved, as diff does "
+"not store file permissions in the patch. However when using source format "
+"“3.0 (quilt)”, permissions of files inside the <filename>debian</filename> "
+"directory are preserved since they are stored in a tar archive."
msgstr ""
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:268
+#. type: Content of: <chapter><section><title>
+#: pkgs.dbk:278
msgid "Picking a distribution"
-msgstr ""
+msgstr "ディストリビューションを選ぶ"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:270
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:280
msgid ""
"Each upload needs to specify which distribution the package is intended "
"for. The package build process extracts this information from the first "
"<literal>Distribution</literal> field of the <literal>.changes</literal> "
"file."
msgstr ""
+"アップロードでは、パッケージがどのディストリビューション向けになっているかを"
+"指定してあることが必要です。パッケージの構築プロセスでは、<filename>debian/"
+"changelog</filename> ファイルの最初の行からこの情報を展開し、<literal>."
+"changes</literal> ファイルの <literal>Distribution</literal> 欄に配置します。"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:276
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:286
msgid ""
"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 ""
+"この欄にはいくつか指定可能な値があります: <literal>stable</literal>, "
+"<literal>unstable</literal>, <literal>testing-proposed-updates</literal>, "
+"<literal>experimental</literal> です。通常、パッケージは <literal>unstable</"
+"literal> にアップロードされます。"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:282
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:292
msgid ""
"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 ""
+"実際には、他に二つ指定可能なディストリビューションがあります: "
+"<literal>stable-security </literal> と <literal>testing-security</literal> で"
+"すが、これらについての詳細は <xref linkend=\"bug-security\"/> を読んでくださ"
+"い。"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:287
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:297
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:291
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:301
msgid ""
"Special case: uploads to the <literal>stable</literal> and "
"<literal>oldstable</literal> distributions"
msgstr ""
+"特別な例: <literal>stable</literal> と <literal>oldstable</literal> ディスト"
+"リビューションへアップロードする"
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:294
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:304
msgid ""
"Uploading to <literal>stable</literal> means that the package will "
-"transfered to the <literal>proposed-updates-new</literal> queue for review "
+"transferred 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 <literal>stable</literal> with "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:302
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:312
msgid ""
"To ensure that your upload will be accepted, you should discuss the changes "
"with the stable release team before you upload. For that, send a mail to the "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:310
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:320
msgid ""
"Extra care should be taken when uploading to <literal>stable</literal>. "
"Basically, a package should only be uploaded to <literal>stable</literal> if "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:317
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:327
msgid "a truly critical functionality problem"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:322
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:332
msgid "the package becomes uninstallable"
-msgstr ""
+msgstr "パッケージがインストールできなくなる"
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:327
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:337
msgid "a released architecture lacks the package"
-msgstr ""
+msgstr "リリースされたアーキテクチャにパッケージが無い"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:332
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:342
msgid ""
"In the past, uploads to <literal>stable</literal> were used to address "
"security problems as well. However, this practice is deprecated, as uploads "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:343
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:353
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:347
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:357
msgid ""
"Packages uploaded to <literal>stable</literal> need to be compiled on "
"systems running <literal>stable</literal>, so that their dependencies are "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:357
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:367
msgid ""
"Uploads to the <literal>oldstable</literal> distributions are possible as "
"long as it hasn't been archived. The same rules as for <literal>stable </"
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:364
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:374
msgid ""
"Special case: uploads to <literal>testing/testing-proposed-updates</literal>"
msgstr ""
+"特別な例: <literal>testing/testing-proposed-updates</literal> へアップロード"
+"する"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:366
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:376
msgid ""
"Please see the information in the <link linkend=\"t-p-u\">testing section</"
"link> for details."
msgstr ""
+"詳細については、<link linkend=\"t-p-u\">testing section</link> にある情報を参"
+"照してください。"
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:374
+#. type: Content of: <chapter><section><title>
+#: pkgs.dbk:384
msgid "Uploading a package"
msgstr "パッケージをアップロードする"
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:376
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:386
msgid "Uploading to <literal>ftp-master</literal>"
msgstr "<literal>ftp-master</literal> にアップロードする"
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:378
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:388
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;"
+"changes and dsc-file) with anonymous ftp to <literal>&ftp-upload-host;</"
+"literal> in the directory <ulink url=\"ftp://&ftp-upload-host;&upload-queue;"
"\">&upload-queue;</ulink>. To get the files processed there, they need to "
"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:387
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:397
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:392
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:402
msgid ""
"You may also find the Debian packages <xref linkend=\"dupload\"/> or <xref "
"linkend=\"dput\"/> useful when uploading packages. These handy programs "
"help automate the process of uploading packages into Debian."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:397
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:407
msgid ""
-"For removing packages, please see the README file in that ftp directory, and "
-"the Debian package <xref linkend=\"dcut\"/> ."
+"For removing packages, please see <ulink url=\"ftp://&ftp-upload-host;"
+"&upload-queue;/README\"/> and the Debian package <xref linkend=\"dcut\"/> ."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:403
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:414
msgid "Delayed uploads"
msgstr "遅延アップロード"
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:405
-msgid ""
-"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:411
-msgid "With a fairly recent dput, this section"
-msgstr ""
-
-# type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:413
-#, fuzzy, no-wrap
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:417
msgid ""
-"\n"
-"[tfheen_delayed]\n"
-"method = scp\n"
-"fqdn = gluck.debian.org\n"
-"incoming = ~tfheen\n"
+"It is sometimes useful to upload a package immediately, but to want this "
+"package to arrive in the archive only a few days later. For example, when "
+"preparing a <link linkend=\"nmu\">Non-maintainer Upload</link>, you might "
+"want to give the maintainer a few days to react."
msgstr ""
-"[tfheen_delayed]\n"
-"method = scp\n"
-"fqdn = gluck.debian.org\n"
-"incoming = ~tfheen"
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:420
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:424
msgid ""
-"in <filename>~/.dput.cf</filename> should work fine for uploading to the "
-"<literal>DELAYED</literal> queue."
+"An upload to the delayed directory keeps the package in <ulink url=\"http://"
+"ftp-master.debian.org/deferred.html\"> the deferred uploads queue\"</"
+"ulink>. When the specified waiting time is over, the package is moved into "
+"the regular incoming directory for processing. This is done through "
+"automatic uploading to <literal>&ftp-upload-host;</literal> in upload-"
+"directory <literal>DELAYED/[012345678]-day</literal>. 0-day is uploaded "
+"multiple times per day to <literal>&ftp-upload-host;</literal>."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:424
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:435
msgid ""
-"<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."
+"With dput, you can use the <literal>--delayed <replaceable>DELAY</"
+"replaceable></literal> parameter to put the package into one of the queues."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:431
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:441
msgid "Security uploads"
msgstr "セキュリティアップロード"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:433
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:443
msgid ""
"Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security "
"upload queue (<literal>oldstable-security</literal>, <literal>stable-"
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:443
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:453
msgid "Other upload queues"
msgstr "他のアップロードキュー"
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:445
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:455
msgid ""
-"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."
+"There is an alternative upload queue in Europe at <ulink url=\"ftp://&ftp-eu-"
+"upload-host;&upload-queue;\"/>. It operates in the same way as <literal>&ftp-"
+"upload-host;</literal>, but should be faster for European developers."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: 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:454
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:461
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 "
-"resurrected. The queue in Japan will be replaced with a new queue on hp."
-"debian.or.jp some day."
+"Packages can also be uploaded via ssh to <literal>&ssh-upload-host;</"
+"literal>; files should be put <literal>/srv/upload.debian.org/UploadQueue</"
+"literal>. This queue does not support <xref linkend=\"delayed-incoming"
+"\">delayed uploads</xref>."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:462
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:469
msgid "Notification that a new package has been installed"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:464
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:471
msgid ""
"The Debian archive maintainers are responsible for handling package "
"uploads. For the most part, uploads are automatically handled on a daily "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:474
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:481
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:480
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:487
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:485
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:492
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:493
+#. type: Content of: <chapter><section><title>
+#: pkgs.dbk:500
msgid "Specifying the package section, subsection and priority"
-msgstr ""
+msgstr "パッケージのセクション、サブセクション、優先度を指定する"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:495
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:502
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:503
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:510
msgid ""
"The archive maintainers keep track of the canonical sections and priorities "
"for packages in the <literal>override file</literal>. If there is a "
"in the <literal>override file</literal>."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: pkgs.dbk:513
+#
. type: Content of: <chapter><section><para>
+#: pkgs.dbk:520
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 "
-"accurate. Next, send an email &email-override; or submit a bug against "
-"<systemitem role=\"package\">ftp.debian.org</systemitem> requesting that the "
-"section or priority for your package be changed from the old section or "
-"priority to the new one. Be sure to explain your reasoning."
+"accurate. Next, submit a bug against <systemitem role=\"package\">ftp."
+"debian.org</systemitem> requesting that the section or priority for your "
+"package be changed from the old section or priority to the new one. Use a "
+"Subject like <literal>override: PACKAGE1:section/priority, [...], PACKAGEX:"
+"section/priority</literal>, and include the justification for the change in "
+"the body of the bug report."
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:521
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:531
msgid ""
"For more information about <literal>override files</literal>, see "
"<citerefentry> <refentrytitle>dpkg-scanpackages</refentrytitle> "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:527
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:537
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:536
+#. type: Content of: <chapter><section><title>
+#: pkgs.dbk:546
msgid "Handling bugs"
msgstr "バグの取扱い"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:538
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:548
msgid ""
"Every developer has to be able to work with the Debian <ulink url=\"&url-bts;"
"\">bug tracking system</ulink>. This includes knowing how to file bug "
"reports properly (see <xref linkend=\"submit-bug\"/> ), how to update them "
"and reorder them, and how to process and close them."
msgstr ""
+"すべての開発者は Debian <ulink url=\"&url-bts;\">バグ追跡システム</ulink>を取"
+"り扱えるようでなければいけません。これはどの様にしてバグ報告を正しく登録する"
+"か (<xref linkend=\"submit-bug\"/> 参照)、どの様に更新をして整理しなおすか、"
+"そしてどの様にして処理をして完了するかを知っていることを含みます。"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:544
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:554
msgid ""
"The bug tracking system's features are described in the <ulink url=\"&url-"
"bts-devel;\">BTS documentation for developers</ulink>. This includes "
"closing bugs, sending followup messages, assigning severities and tags, "
"marking bugs as forwarded, and other issues."
msgstr ""
+"バグ追跡システムの機能は<ulink url=\"&url-bts-devel;\"> Debian BTS 開発者向け"
+"情報</ulink>に記載されています。これには、バグの完了処理・追加メッセージの送"
+"信・重要度とタグを割り当てる・バグを転送済み (Forwarded) にする・その他が含ま"
+"れています。"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:550
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:560
msgid ""
"Operations such as reassigning bugs to other packages, merging separate bug "
"reports about the same issue, or reopening bugs when they are prematurely "
"commands available on this server are described in the <ulink url=\"&url-bts-"
"control;\">BTS control server documentation</ulink>."
msgstr ""
+"バグを他のパッケージに割り当てし直す、同じ問題についての別々のバグ報告をマー"
+"ジする、などの作業はいわゆる制御メールサーバと呼ばれるものを使って処理されて"
+"います。このサーバで利用可能なすべてのコマンドは、<ulink url=\"&url-bts-"
+"control;\">BTS 制御サーバドキュメント</ulink>に記載されています。"
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:558
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:568
msgid "Monitoring bugs"
msgstr "バグの監視"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:560
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:570
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 "
"can check them by browsing this page: <literal>http://&bugs-host;/"
"<replaceable>yourlogin</replaceable>@debian.org</literal>."
msgstr ""
+"良いメンテナになりたい場合は、あなたのパッケージに関する <ulink url=\"&url-"
+"bts;\">Debian バグ追跡システム (BTS)</ulink> のページを定期的にチェックする必"
+"要があります。BTS には、あなたのパッケージに対して登録されている全てのバグが"
+"含まれています。登録されているバグについては、以下のページを参照することで確"
+"認できます: <literal>http://&bugs-host;/<replaceable>yourlogin</"
+"replaceable>@debian.org</literal>"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:567
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:577
msgid ""
"Maintainers interact with the BTS via email addresses at <literal>&bugs-host;"
"</literal>. Documentation on available commands can be found at <ulink url="
"\"package\">doc-debian</systemitem> package, you can look at the local files "
"&file-bts-docs;."
msgstr ""
+"メンテナは、<literal>&bugs-host;</literal> のメールアドレス経由で BTS に対応"
+"します。利用可能なコマンドについてのドキュメントは <ulink url=\"&url-bts;"
+"\"></ulink> で参照可能ですし、もし <systemitem role=\"package\">doc-debian</"
+"systemitem> パッケージをインストールしてあれば、ローカルファイル &file-bts-"
+"docs; で見ることも可能です。"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:574
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:584
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 "
"all the open bugs against your packages:"
msgstr ""
-# type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:578
+#. type: Content of: <chapter><section><section><screen>
+#: pkgs.dbk:589
#, no-wrap
msgid ""
-"\n"
"# ask for weekly reports of bugs in my packages\n"
"&cron-bug-report;\n"
msgstr ""
+"# 自分のパッケージにあるバグのレポートを毎週取得する\n"
+"&cron-bug-report;\n"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:583
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:593
msgid ""
"Replace <replaceable>address</replaceable> with your official Debian "
"maintainer address."
msgstr ""
+"<replaceable>address</replaceable> は、あなたの公式な Debian パッケージメンテ"
+"ナとしてのメールアドレスに置き換えてください。"
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:589
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:599
msgid "Responding to bugs"
msgstr "バグへの対応"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:591
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:601
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."
"emphasis> to record your mail within the bug log (that means you don't need "
"to send a copy of the mail to <email>123@&bugs-host;</email>)."
msgstr ""
+"バグに対応する際は、バグについて行った議論がバグの元々の報告者とバグ自身 (例"
+"えば <email>123@&bugs-host;</email>) の両方に送られているのを確認してくださ"
+"い。新しくメールを書いていて元々の報告者のメールアドレスを思い出せない場合"
+"は、<email>123-submitter@&bugs-host;</email> というメールアドレスを報告者へ連"
+"絡するのに使えます。<emphasis>さらに</emphasis>バグのログへあなたのメールを記"
+"録するのにも使えます (これは <email>123@&bugs-host;</email> へメールのコピー"
+"を送らなくても済むことを意味しています)。"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:600
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:610
msgid ""
"If you get a bug which mentions FTBFS, this means Fails to build from "
"source. Porters frequently use this acronym."
msgstr ""
+"FTBFS である旨のバグを受け取った場合、これはソースからビルドできないこと "
+"(Fails to build from source) を意味します。移植作業をしている人たちはこの略語"
+"をよく使います。"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:604
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:614
msgid ""
"Once you've dealt with a bug report (e.g. fixed it), mark it as "
"<literal>done</literal> (close it) by sending an explanation message to "
"uploading the package, you can automate bug closing as described in <xref "
"linkend=\"upload-bugfix\"/> ."
msgstr ""
+"既にバグに対処していた場合 (例えば修正済み)、説明のメッセージを <email>123-"
+"done@&bugs-host;</email> に送ることで <literal>done</literal> とマークしてお"
+"いて (閉じて) ください。パッケージを変更してアップロードすることでバグを修正"
+"する場合は、<xref linkend=\"upload-bugfix\"/> に記載されているように自動的に"
+"バグを閉じることができます。"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:611
+# FIXME: via the bug server ?
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:621
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, "
"the original submitter will not receive any information about why the bug "
"was closed."
msgstr ""
+"<literal>close</literal> コマンドを &email-bts-control; に送って、バグサーバ"
+"経由でバグを閉じるのは<emphasis>決して</emphasis>してはいけません。そのように"
+"した場合、元々の報告者は何故バグが閉じられたのかという情報を得られません。"
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:619
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:629
msgid "Bug housekeeping"
msgstr "バグを掃除する"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:621
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:631
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:632
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:642
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:637
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:647
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:642
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:652
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:652
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:662
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:666
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:676
msgid ""
"If the bug is real but it's caused by another package, just reassign the bug "
"to the right package. If you don't know which package it should be "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:678
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:688
msgid ""
"If the bug affects the operation of your package, please consider cloning "
"the bug and reassigning the clone to the package that really causes the "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:688
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:698
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:696
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:706
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:707
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:717
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:718
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:728
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:732
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:742
msgid ""
"If you have fixed a bug in your local copy, or if a fix has been committed "
"to the CVS repository, you may tag the bug as <literal>pending</literal> to "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:742
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:752
msgid ""
"Once a corrected package is available in the archive, the bug should be "
"closed indicating the version in which it was fixed. This can be done "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:751
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:761
msgid "When bugs are closed by new uploads"
msgstr "新規アップロードでバグがクローズされる時"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:753
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:763
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:761
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:771
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:766
-#, fuzzy, no-wrap
+#. type: Content of: <chapter><section><section><screen>
+#: pkgs.dbk:777
+#, no-wrap
msgid ""
-"\n"
"acme-cannon (3.1415) unstable; urgency=low\n"
"\n"
" * Frobbed with options (closes: Bug#98339)\n"
" * Frobbed with options (closes: Bug#98339)\n"
" * Added safety to prevent operator dismemberment, closes: bug#98765,\n"
" bug#98713, #98714.\n"
-" * Added man page. Closes: #98725."
+" * Added man page. Closes: #98725.\n"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:775
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:785
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:778
-#, fuzzy, no-wrap
-msgid ""
-"\n"
-" /closes:\\s*(?:bug)?\\#\\s*\\d+(?:,\\s*(?:bug)?\\#\\s*\\d+)*/ig\n"
-msgstr "/closes:\\s*(?:bug)?\\#\\s*\\d+(?:,\\s*(?:bug)?\\#\\s*\\d+)*/ig"
+#. type: Content of: <chapter><section><section><screen>
+#: pkgs.dbk:789
+#, no-wrap
+msgid " /closes:\\s*(?:bug)?\\#\\s*\\d+(?:,\\s*(?:bug)?\\#\\s*\\d+)*/ig\n"
+msgstr " /closes:\\s*(?:bug)?\\#\\s*\\d+(?:,\\s*(?:bug)?\\#\\s*\\d+)*/ig\n"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:782
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:792
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:791
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:801
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:797
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:807
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:809
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:819
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:817
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:827
msgid ""
"For general information on how to write your changelog entries, see <xref "
"linkend=\"bpp-debian-changelog\"/> ."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:823
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:833
msgid "Handling security-related bugs"
msgstr "セキュリティ関連バグの取扱い"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:825
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:835
msgid ""
"Due to their sensitive nature, security-related bugs must be handled "
"carefully. The Debian Security Team exists to coordinate this activity, "
"and maintaining <literal>security.debian.org</literal>."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:834
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:842
msgid ""
"When you become aware of a security-related bug in a Debian package, whether "
"or not you are the maintainer, collect pertinent information about the "
"problem, and promptly contact the security team at &email-security-team; as "
"soon as possible. <emphasis role=\"strong\">DO NOT UPLOAD</emphasis> any "
-"packages for <literal>stable</literal>; the security team will do that. "
-"Useful information includes, for example:"
+"packages for <literal>stable</literal> without contacting the team. Useful "
+"information includes, for example:"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:844
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:852
msgid ""
"Which versions of the package are known to be affected by the bug. Check "
"each version that is present in a supported Debian release, as well as "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:851
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:859
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:856
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:864
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:863
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:871
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:869
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:877
msgid ""
"Any information needed for the advisory (see <xref linkend=\"bug-security-"
"advisories\"/> )"
msgstr ""
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:882
+msgid ""
+"As the maintainer of the package, you have the responsibility to maintain "
+"it, even in the stable release. You are in the best position to evaluate "
+"patches and test updated packages, so please see the sections below on how "
+"to prepare packages for the Security Team to handle."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:888
+msgid "The Security Tracker"
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:890
+msgid ""
+"The security team maintains a central database, the <ulink url=\"http://"
+"security-tracker.debian.org/\">Debian Security Tracker</ulink>. This "
+"contains all public information that is known about security issues: which "
+"packages and versions are affected or fixed, and thus whether stable, "
+"testing and/or unstable are vulnerable. Information that is still "
+"confidential is not added to the tracker."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:898
+msgid ""
+"You can search it for a specific issue, but also on package name. Look for "
+"your package to see which issues are still open. If you can, please provide "
+"more information about those issues, or help to address them in your "
+"package. Instructions are on the tracker web pages."
+msgstr ""
+
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:875
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:906
msgid "Confidentiality"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:877
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:908
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:884
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:915
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:889
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:920
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:894
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:925
msgid "someone files a bug report"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:899
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:930
msgid "someone informs them via private email"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:904
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:935
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:912
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:943
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:918
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:949
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:925
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:956
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:932
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:963
msgid ""
"Please note that if secrecy is needed you may not upload a fix to "
"<literal>unstable</literal> (or anywhere else, such as a public CVS "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:939
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:970
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 "
"has become public."
msgstr ""
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:975
+msgid ""
+"The Security Team has a PGP-key to enable encrypted communication about "
+"sensitive issues. See the <ulink url=\"http://www.debian.org/security/faq.en."
+"html#contact\">Security Team FAQ</ulink> for details."
+msgstr ""
+
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:946
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:981
msgid "Security Advisories"
msgstr "セキュリティ勧告"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:948
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:983
msgid ""
"Security advisories are only issued for the current, released stable "
"distribution, and <emphasis>not</emphasis> for <literal>testing</literal> or "
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:961
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:996
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:966
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
+#: pkgs.dbk:1001
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:971
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
+#: pkgs.dbk:1006
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:976
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
+#: pkgs.dbk:1011
msgid "How it can be exploited"
msgstr "どのようにして攻撃が可能なのか"
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
-#: pkgs.dbk:981
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
+#: pkgs.dbk:1016
msgid "Whether it is remotely or locally exploitable"
msgstr "攻撃はリモートから可能なのかそれともローカルから可能なのか"
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
-#: pkgs.dbk:986
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
+#: pkgs.dbk:1021
msgid "How the problem was fixed"
msgstr "どのようにして問題が修正されたのか"
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:991
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1026
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:996
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1031
msgid "Version numbers of affected packages"
msgstr "影響を受けるパッケージのバージョン番号"
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1001
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1036
msgid "Version numbers of fixed packages"
msgstr "修正されたパッケージのバージョン番号"
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1006
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1041
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:1012
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1047
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:1021
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:1056
msgid "Preparing packages to address security issues"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1023
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1058
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:1028
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1063
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:1036
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1071
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:1042
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1077
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:1049
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1084
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:1056
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1091
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:1066
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1101
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:1074
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1109
msgid "Be sure to verify the following items:"
msgstr ""
-# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1079
+#
. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1114
msgid ""
-"Target the right distribution in your <filename>debian/changelog</"
-"filename>. For <literal>stable</literal> this is <literal>stable-security</"
-"literal> and for testing this is <literal>testing-security</literal>, and "
-"for the previous stable release, this is <literal>oldstable-security</"
-"literal>. Do not target <replaceable>distribution</replaceable><literal>-"
-"proposed-updates</literal> or <literal>stable</literal>!"
+"<emphasis role=\"strong\">Target the right distribution</emphasis> in your "
+"<filename>debian/changelog</filename>. For <literal>stable</literal> this "
+"is <literal>stable-security</literal> and for testing this is "
+"<literal>testing-security</literal>, and for the previous stable release, "
+"this is <literal>oldstable-security</literal>. Do not target "
+"<replaceable>distribution</replaceable><literal>-proposed-updates</literal> "
+"or <literal>stable</literal>!"
msgstr ""
# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1089
-msgid "The upload should have urgency=high."
-msgstr "アップロードは urgency=high で行う必要があります。"
-
-# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1094
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1125
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 <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."
+"The upload should have <emphasis role=\"strong\">urgency=high</emphasis>."
msgstr ""
+"アップロードは <emphasis role=\"strong\">urgency=high</emphasis> で行う必要が"
+"あります。"
-# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1107
+#
. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1130
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 <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."
+"Make descriptive, meaningful changelog entries. Others will rely on them to "
+"determine whether a particular bug was fixed. Add <literal>closes:</"
+"literal> statements for any <emphasis role=\"strong\">Debian bugs</emphasis> "
+"filed. Always include an external reference, preferably a <emphasis role="
+"\"strong\">CVE identifier</emphasis>, so that it can be cross-referenced. "
+"However, if a CVE identifier has not yet been assigned, do not wait for it "
+"but continue the process. The identifier can be cross-referenced later."
msgstr ""
-# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1119
+#
. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1141
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</"
-"command>). The <command>buildd</command> infrastructure will not build "
-"those. This point applies to normal package uploads as well."
+"Make sure the <emphasis role=\"strong\">version number</emphasis> 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, or one that conflicts with a "
+"binNMU. The convention is to append <literal>+</"
+"literal><replaceable>codename</replaceable><literal>1</literal>, e.g. "
+"<literal>1:2.4.3-4+etch1</literal>, of course increasing 1 for any "
+"subsequent uploads."
msgstr ""
-# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1128
+#
. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1154
msgid ""
"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>)."
+"</literal> before (by a previous security update), build the upload "
+"<emphasis role=\"strong\">with full upstream source</emphasis> "
+"(<literal>dpkg-buildpackage -sa</literal>). If there has been a previous "
+"upload to <literal>security.debian.org</literal> with the same upstream "
+"version, you may upload without upstream source (<literal> dpkg-buildpackage "
+"-sd</literal>)."
msgstr ""
-# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1138
+#
. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1164
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 "
-"into the main archives later."
+"Be sure to use the <emphasis role=\"strong\">exact same <filename>*.orig.tar."
+"{gz,bz2}</filename></emphasis> as used in the normal archive, otherwise it "
+"is not possible to move the security fix into the main archives later."
msgstr ""
-# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1145
+#
. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1172
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 "
-"yourself, you can use a debian.org machine (see <xref linkend=\"server-"
-"machines\"/> ) or setup a chroot (see <xref linkend=\"pbuilder\"/> and <xref "
-"linkend=\"debootstrap\"/> )."
+"Build the package on a <emphasis role=\"strong\">clean system</emphasis> "
+"which only has packages installed from the distribution you are building "
+"for. If you do not have such a system yourself, you can use a debian.org "
+"machine (see <xref linkend=\"server-machines\"/> ) or setup a chroot (see "
+"<xref linkend=\"pbuilder\"/> and <xref linkend=\"debootstrap\"/> )."
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1156
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:1183
msgid "Uploading the fixed package"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1158
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1185
msgid ""
"Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security "
"upload queue (<literal>oldstable-security</literal>, <literal>stable-"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1165
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1192
msgid ""
"Do <emphasis role=\"strong\">NOT</emphasis> upload your fix to <literal> "
"proposed-updates</literal> without coordinating with the security team. "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1175
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1202
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 "
"literal> ."
msgstr ""
-# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1181
+#
. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1208
msgid ""
"Once an upload to the security queue has been accepted, the package will "
-"automatically be rebuilt for all architectures and stored for verification "
-"by the security team."
+"automatically be built for all architectures and stored for verification by "
+"the security team."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1186
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1213
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:1191
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1218
msgid ""
"If a member of the security team accepts a package, it will be installed on "
"<literal>security.debian.org</literal> as well as proposed for the proper "
msgstr ""
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:1203
+#. type: Content of: <chapter><section><title>
+#: pkgs.dbk:1230
msgid "Moving, removing, renaming, adopting, and orphaning packages"
msgstr "パッケージの移動、削除、リネーム、変更、みなしご化"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:1205
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:1232
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:1210
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:1237
msgid "Moving packages"
msgstr "パッケージの移動"
-# type: Content of: <chapter><section><section><para><footnote>
-#: 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 "
-"package should be moved to `main' or `contrib'.<footnote>"
-msgstr ""
-
# type: Content of: <chapter><section><section><para><footnote><para>
-#: pkgs.dbk:1214
+#. type: Content of: <chapter><section><section><para><footnote><para>
+#: pkgs.dbk:1241
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:1216 pkgs.dbk:1648
-msgid "</footnote>"
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1239
+msgid ""
+"Sometimes a package will change its section. For instance, a package from "
+"the `non-free' section might be GPL'd in a later version, in which case the "
+"package should be moved to `main' or `contrib'.<placeholder type=\"footnote"
+"\" id=\"0\"/>"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1219
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1246
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 "
"re-upload the package (see the <ulink url=\"&url-debian-policy;\">Debian "
"Policy Manual</ulink> for details). You must ensure that you include the "
-"<filename>.orig.tar.gz</filename> in your upload (even if you are not "
+"<filename>.orig.tar.{gz,bz2}</filename> in your upload (even if you are not "
"uploading a new upstream version), or it will not appear in the new section "
"together with the rest of the package. If your new section is valid, it "
"will be moved automatically. If it does not, then contact the ftpmasters in "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1231
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1258
msgid ""
"If, on the other hand, you need to change the <literal>subsection</literal> "
"of one of your packages (e.g., ``devel'', ``admin''), the procedure is "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1240
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:1267
msgid "Removing packages"
msgstr "パッケージの削除"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1242
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1269
msgid ""
"If for some reason you want to completely remove a package (say, if it is an "
"old compatibility library which is no longer required), you need to file a "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1259
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1286
msgid ""
"If you want to remove a package you maintain, you should note this in the "
"bug title by prepending <literal>ROM</literal> (Request Of Maintainer). "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1268
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1295
msgid ""
"Note that removals can only be done for the <literal>unstable </literal>, "
"<literal>experimental</literal> and <literal>stable </literal> "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1277
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1304
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:1286
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1313
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:1292
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1319
msgid ""
"Usually you only ask for the removal of a package maintained by yourself. "
"If you want to remove another package, you have to get the approval of its "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1302
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1329
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:1307
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1334
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</"
"command>. Removal of orphaned packages is discussed on &email-debian-qa;."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1320
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1347
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 "
"actual code has evolved into another package (e.g. <literal>libfoo12</"
"literal> was removed because <literal>libfoo13</literal> supersedes it) or "
-"closed if the software is simply no longer part of Debian."
+"closed if the software is simply no longer part of Debian. When closing the "
+"bugs, to avoid marking the bugs as fixed in versions of the packages in "
+"previous Debian releases, they should be marked as fixed in the version "
+"<literal><most-recent-version-ever-in-Debian>+rm</literal>."
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1327
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:1358
msgid "Removing packages from <filename>Incoming</filename>"
msgstr "<filename>Incoming</filename> からパッケージを削除する"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1329
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1360
msgid ""
"In the past, it was possible to remove packages from <filename>incoming</"
"filename>. However, with the introduction of the new incoming system, this "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1344
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:1375
msgid "Replacing or renaming packages"
msgstr "パッケージをリプレースあるいはリネームする"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1346
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1377
msgid ""
"When the upstream maintainers for one of your packages chose to rename their "
"software (or you made a mistake naming your package), you should follow a "
"package's bugs at the same time."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1362
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1393
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 "
"sources: if you wish to replace the upstream source tarball of your package, "
"you will need to upload it with a different version. An easy possibility is "
"to replace <filename>foo_1.00.orig.tar.gz</filename> with <filename>foo_1.00"
-"+0.orig.tar.gz</filename>. This restriction gives each file on the ftp site "
-"a unique name, which helps to ensure consistency across the mirror network."
+"+0.orig.tar.gz</filename> or <filename>foo_1.00.orig.tar.bz2</filename>. "
+"This restriction gives each file on the ftp site a unique name, which helps "
+"to ensure consistency across the mirror network."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1376
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:1408
msgid "Orphaning a package"
msgstr "パッケージをみなしご化する"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1378
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1410
msgid ""
"If you can no longer maintain a package, you need to inform others, and see "
"that the package is marked as orphaned. You should set the package "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1393
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1425
msgid ""
"If you just intend to give the package away, but you can keep maintainership "
"for the moment, then you should instead submit a bug against <systemitem "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1401
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1433
msgid ""
"More information is on the <ulink url=\"&url-wnpp;\">WNPP web pages</ulink>."
msgstr ""
"す。"
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1407
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:1439
msgid "Adopting a package"
msgstr "パッケージに変更を加える"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1409
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1441
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:1416
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1448
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:1422
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1454
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:1432
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1464
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:1446
+#. type: Content of: <chapter><section><title>
+#: pkgs.dbk:1478
msgid "Porting and being ported"
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:1448
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:1480
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:1454
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:1486
msgid ""
"Porting is the act of building Debian packages for architectures that are "
"different from the original architecture of the package maintainer's binary "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1463
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:1495
msgid "Being kind to porters"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1465
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1497
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:1473
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1505
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:1480
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1512
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:1487
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:1519
msgid ""
"Make sure that your <literal>Build-Depends</literal> and <literal>Build-"
"Depends-Indep</literal> settings in <filename>debian/control</filename> are "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1502
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:1534
msgid ""
"If you can't set up a proper chroot, <command>dpkg-depcheck</command> may be "
"of assistance (see <xref linkend=\"dpkg-depcheck\"/> )."
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1506
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:1538
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:1512
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:1544
msgid ""
"Don't set architecture to a value other than <literal>all</literal> or "
"<literal>any</literal> unless you really mean it. In too many cases, "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1522
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:1554
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:1530
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:1562
msgid ""
"Make sure you don't ship your source package with the <filename>debian/"
"files</filename> or <filename>debian/substvars</filename> files. They "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1538
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:1570
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:1547
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:1579
msgid ""
"Don't depend on the package you're building being installed already (a sub-"
"case of the above issue). There are, of course, exceptions to this rule, but "
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1555
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:1587
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:1563
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: pkgs.dbk:1595
msgid ""
"Make sure your debian/rules contains separate <literal>binary-arch</literal> "
"and <literal>binary-indep</literal> targets, as the Debian Policy Manual "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1574
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:1606
msgid "Guidelines for porter uploads"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1576
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1608
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:1584
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1616
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:1589
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1621
msgid ""
"The way to invoke <command>dpkg-buildpackage</command> is as <literal>dpkg-"
"buildpackage -B -m<replaceable>porter-email</replaceable></literal>. Of "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1598
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1630
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:1605
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:1637
msgid "Recompilation or binary-only NMU"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1607
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1639
msgid ""
"Sometimes the initial porter upload is problematic because the environment "
"in which the package was built was not good enough (outdated or obsolete "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1616
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1648
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-"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1623
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1655
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:1628
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1660
msgid ""
"Such recompilations require special ``magic'' version numbering, so that the "
"archive maintenance tools recognize that, even though there is a new Debian "
"corresponding source code)."
msgstr ""
-# type: Content of: <chapter><section><section><section><para><footnote>
-#: pkgs.dbk:1635
+# type: Content of: <chapter><section><section><section><para><footnote><para>
+#. type: Content of: <chapter><section><section><section><para><footnote><para>
+#: pkgs.dbk:1675
+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 "
+"ambiguous with native packages and did not allow proper ordering of "
+"recompile-only NMUs, source NMUs, and security NMUs on the same package, and "
+"has therefore been abandoned in favor of this new syntax."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1667
msgid ""
"The ``magic'' for a recompilation-only NMU is triggered by using a suffix "
"appended to the package version number, following the form <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: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 "
-"ambiguous with native packages and did not allow proper ordering of "
-"recompile-only NMUs, source NMUs, and security NMUs on the same package, and "
-"has therefore been abandoned in favor of this new syntax."
+"version number of <literal>3.4+b2</literal>. <placeholder type=\"footnote\" "
+"id=\"0\"/>"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1651
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1683
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:1658
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:1690
msgid "When to do a source NMU if you are a porter"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1660
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1692
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:1669
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1701
msgid ""
"If you are a porter doing an NMU for <literal>unstable</literal>, the above "
"guidelines for porting should be followed, with two variations. Firstly, "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1681
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1713
msgid ""
"Secondly, porters doing source NMUs should make sure that the bug they "
"submit to the BTS should be of severity <literal>serious</literal> or "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1689
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1721
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:1697
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1729
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:1707
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:1739
msgid "Porting infrastructure and automation"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1709
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1741
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:1714
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:1746
msgid "Mailing lists and web pages"
msgstr "メーリングリストとウェブページ"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1716
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1748
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:1720
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1752
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:1728
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:1760
msgid "Porter tools"
msgstr "移植用ツール"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1730
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1762
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:1736
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:1768
msgid "<systemitem role=\"package\">wanna-build</systemitem>"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1738
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1770
msgid ""
"The <systemitem role=\"package\">wanna-build</systemitem> system is used as "
"a distributed, client-server build distribution system. It is usually used "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1746
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1778
msgid ""
"<systemitem role=\"package\">wanna-build</systemitem> is not yet available "
"as a package; however, all Debian porting efforts are using it for automated "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1755
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1787
msgid ""
"Most of the data produced by <systemitem role=\"package\">wanna-build </"
"systemitem> which is generally useful to porters is available on the web at "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1761
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1793
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 "
"will also enable Debian to recompile entire distributions quickly."
msgstr ""
-# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1768
+#
. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1800
msgid ""
-"The buildds admins of each arch can be contacted at the mail address "
-"<literal><replaceable>arch</replaceable>@buildd.debian.org</literal>."
+"The wanna-build team, in charge of the buildds, can be reached at "
+"<literal>debian-wb-team@lists.debian.org</literal>. To determine who (wanna-"
+"build team, release team) and how (mail, BTS) to contact, refer to <ulink "
+"url=\"&url-wb-team;\"></ulink>."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:1807
+msgid ""
+"When requesting binNMUs or give-backs (retries after a failed build), please "
+"use the format described at <ulink url=\"&url-release-wb;\"/>."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1776
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:1816
msgid "When your package is <emphasis>not</emphasis> portable"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1778
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1818
msgid ""
"Some packages still have issues with building and/or working on some of the "
"architectures supported by Debian, and cannot be ported at all, or not "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1785
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1825
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:1791
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1831
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:1799
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1839
msgid ""
"Additionally, if you believe the list of supported architectures is pretty "
"constant, you should change <literal>any</literal> to a list of supported "
"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:1807
+#
. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1847
msgid ""
"In order to prevent autobuilders from needlessly trying to build your "
"package, it must be included in <filename>packages-arch-specific</filename>, "
"a list used by the <command>wanna-build</command> script. The current "
-"version is available as <ulink url=\"&url-cvsweb;srcdep/Packages-arch-"
-"specific?cvsroot=dak\"></ulink>; please see the top of the file for whom to "
-"contact for changes."
+"version is available as <ulink url=\"&url-buildd-p-a-s;\"/>; please see the "
+"top of the file for whom to contact for changes."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1817
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1856
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:1830
+#. type: Content of: <chapter><section><title>
+#: pkgs.dbk:1869
msgid "Non-Maintainer Uploads (NMUs)"
msgstr ""
-# type: Content of: <chapter><section><para>
-#: 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 "
-"a non-maintainer upload, or NMU."
-msgstr ""
-
-# type: Content of: <chapter><section><para>
-#: 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="
-"\"wanna-build\"/> for some more information."
-msgstr ""
-
-# type: Content of: <chapter><section><para>
-#: 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 "
-"or when the package maintainer is unable to release a fix in a timely "
-"fashion."
-msgstr ""
-
-# type: Content of: <chapter><section><para>
-#: 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 "
-"name of modules or files, do not move directories; in general, do not fix "
-"things which are not broken. Keep the patch as small as possible. If "
-"things bother you aesthetically, talk to the Debian maintainer, talk to the "
-"upstream maintainer, or submit a bug. However, aesthetic changes must "
-"<emphasis>not</emphasis> be made in a non-maintainer upload."
-msgstr ""
-
-# type: Content of: <chapter><section><para>
-#: 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-"
-"functional patch, or one that hides the bug instead of resolving it."
-msgstr ""
-
-# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1863
-msgid "How to do a NMU"
-msgstr "NMU のやり方"
-
-# type: Content of: <chapter><section><section><para>
-#: 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 "
-"package; they might be just about to upload a fix for the problem, or have a "
-"better solution."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
+#. type: Content of: <chapter><section><para>
#: 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 "
-"decisions of maintainers, and try to personally help the maintainer by their "
-"work."
+"Every package has one or more maintainers. Normally, these are the people "
+"who work on and upload new versions of the package. In some situations, it "
+"is useful that other developers can upload a new version as well, for "
+"example if they want to fix a bug in a package they don't maintain, when the "
+"maintainer needs help to respond to issues. Such uploads are called "
+"<emphasis>Non-Maintainer Uploads (NMU)</emphasis>."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1877
-msgid ""
-"A NMU should follow all conventions, written down in this section. For an "
-"upload to <literal>testing</literal> or <literal>unstable</literal>, this "
-"order of steps is recommended:"
-msgstr ""
+# type: Content of: <chapter><section><section><title>
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:1880
+#, fuzzy
+msgid "When and how to do an NMU"
+msgstr "誰が NMU 可能なのか"
-# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: 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 "
-"immediately."
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1883
+msgid "Before doing an NMU, consider the following questions:"
msgstr ""
-# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1891
+#
. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1888
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 "
-"bug. Don't forget to tag the bug with the patch keyword."
+"Does your NMU really fix bugs? Fixing cosmetic issues or changing the "
+"packaging style in NMUs is discouraged."
msgstr ""
-# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1898
+#
. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1894
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. "
-"Prepare an NMU as described in this section, and test it carefully on your "
-"machine (cf. <xref linkend=\"sanitycheck\"/> ). Double check that your "
-"patch doesn't have any unexpected side effects. Make sure your patch is as "
-"small and as non-disruptive as it can be."
+"Did you give enough time to the maintainer? When was the bug reported to the "
+"BTS? Being busy for a week or two isn't unusual. Is the bug so severe that "
+"it needs to be fixed right now, or can it wait a few more days?"
msgstr ""
-# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1908
+#
. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1901
msgid ""
-"Upload your package to incoming in <filename>DELAYED/7-day</filename> (cf. "
-"<xref linkend=\"delayed-incoming\"/> ), send the final patch to the "
-"maintainer via the BTS, and explain to them that they have 7 days to react "
-"if they want to cancel the NMU."
+"How confident are you about your changes? Please remember the Hippocratic "
+"Oath: \"Above all, do no harm.\" It is better to leave a package with an "
+"open grave bug than applying a non-functional patch, or one that hides the "
+"bug instead of resolving it. If you are not 100% sure of what you did, it "
+"might be a good idea to seek advice from others. Remember that if you break "
+"something in your NMU, many people will be very unhappy about it."
msgstr ""
-# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1916
+#
. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1911
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\"/> "
-"(PTS) to stay informed of the state of the package after your NMU."
+"Have you clearly expressed your intention to NMU, at least in the BTS? It is "
+"also a good idea to try to contact the maintainer by other means (private "
+"email, IRC)."
msgstr ""
-#
type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1923
+#
. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1918
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 "
-"usually involves shortening the period during which one is to wait before "
-"uploading the fixes, and shortening the DELAYED period. It is important to "
-"notice that even in these so-called bug squashing party times, the NMU'er "
-"has to file bugs and contact the developer first, and act later. Please see "
-"<xref linkend=\"qa-bsp\"/> for details."
+"If the maintainer is usually active and responsive, have you tried to "
+"contact him? In general it should be considered preferable that a maintainer "
+"takes care of an issue himself and that he is given the chance to review and "
+"correct your patch, because he can be expected to be more aware of potential "
+"issues which an NMUer might miss. It is often a better use of everyone's "
+"time if the maintainer is given an opportunity to upload a fix on their own."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1932
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1928
msgid ""
-"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>."
+"When doing an NMU, you must first make sure that your intention to NMU is "
+"clear. Then, you must send a patch with the differences between the current "
+"package and your proposed NMU to the BTS. The <literal>nmudiff</literal> "
+"script in the <literal>devscripts</literal> package might be helpful."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1938
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1935
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 "
-"that all your changes are OK for inclusion into the next stable release by "
-"the release manager."
+"While preparing the patch, you should better be aware of any package-"
+"specific practices that the maintainer might be using. Taking them into "
+"account reduces the burden of getting your changes integrated back in the "
+"normal package workflow and thus increases the possibilities that that will "
+"happen. A good place where to look for for possible package-specific "
+"practices is <ulink url=\"&url-debian-policy;ch-source.html#s-readmesource"
+"\"><literal>debian/README.source</literal></ulink>."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1944
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1943
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 "
-"information."
+"Unless you have an excellent reason not to do so, you must then give some "
+"time to the maintainer to react (for example, by uploading to the "
+"<literal>DELAYED</literal> queue). Here are some recommended values to use "
+"for delays:"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1949
-msgid ""
-"For the differences for Porters NMUs, please see <xref linkend=\"source-nmu-"
-"when-porter\"/> ."
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1950
+msgid "Upload fixing only release-critical bugs older than 7 days: 2 days"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: 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 "
-"diff required)."
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1955
+msgid "Upload fixing only release-critical and important bugs: 5 days"
msgstr ""
-# type: Content of: <chapter><section><section><title>
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
#: pkgs.dbk:1960
-msgid "NMU version numbering"
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: 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."
+msgid "Other NMUs: 10 days"
msgstr ""
-# type: Content of: <chapter><section><section><para>
+#
. type: Content of: <chapter><section><section><para>
#: 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 "
-"version number (the portion after the last hyphen). This extra minor number "
-"will start at `1'. For example, consider the package `foo', which is at "
-"version 1.1-3. In the archive, the source package control file would be "
-"<filename>foo_1.1-3.dsc</filename>. The upstream version is `1.1' and the "
-"Debian revision is `3'. The next NMU would add a new minor number `.1' to "
-"the Debian revision; the new source control file would be <filename>foo_1.1-"
-"3.1.dsc</filename>."
+"Those delays are only examples. In some cases, such as uploads fixing "
+"security issues, or fixes for trivial bugs that blocking a transition, it is "
+"desirable that the fixed package reaches <literal>unstable</literal> sooner."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1977
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1972
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 "
-"also has the benefit of making it visually clear that a package in the "
-"archive was not made by the official maintainer."
+"Sometimes, release managers decide to allow NMUs with shorter delays for a "
+"subset of bugs (e.g release-critical bugs older than 7 days). Also, some "
+"maintainers list themselves in the <ulink url=\"&url-low-threshold-nmu;"
+"\">Low Threshold NMU list</ulink>, and accept that NMUs are uploaded without "
+"delay. But even in those cases, it's still a good idea to give the "
+"maintainer a few days to react before you upload, especially if the patch "
+"wasn't available in the BTS before, or if you know that the maintainer is "
+"generally active."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1983
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1982
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 "
-"a debian native package still upload it as native package). If it is "
-"absolutely necessary for someone other than the usual maintainer to make a "
-"release based on a new upstream version then the person making the release "
-"should start with the <replaceable>debian-revision</replaceable> value "
-"`0.1'. The usual maintainer of a package should start their "
-"<replaceable>debian-revision</replaceable> numbering at `1'."
+"After you upload an NMU, you are responsible for the possible problems that "
+"you might have introduced. You must keep an eye on the package (subscribing "
+"to the package on the PTS is a good way to achieve this)."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1993
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1988
msgid ""
-"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."
+"This is not a license to perform NMUs thoughtlessly. If you NMU when it is "
+"clear that the maintainers are active and would have acknowledged a patch in "
+"a timely manner, or if you ignore the recommendations of this document, your "
+"upload might be a cause of conflict with the maintainer. You should always "
+"be prepared to defend the wisdom of any NMU you perform on its own merits."
msgstr ""
-# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2000
-msgid "Source NMUs must have a new changelog entry"
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:1998
+msgid "NMUs and debian/changelog"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2002
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2000
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 "
-"what it fixed. The changelog entry will have the email address of the "
-"person who uploaded it in the log entry and the NMU version number in it."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2008
-msgid "By convention, source NMU changelog entries start with the line"
+"Just like any other (source) upload, NMUs must add an entry to "
+"<literal>debian/changelog</literal>, telling what has changed with this "
+"upload. The first line of this entry must explicitely mention that this "
+"upload is an NMU, e.g.:"
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:2010
+#. type: Content of: <chapter><section><section><screen>
+#: pkgs.dbk:2005
#, fuzzy, no-wrap
-msgid ""
-"\n"
-" * Non-maintainer upload\n"
+msgid " * Non-maintainer upload.\n"
msgstr "* Non-maintainer upload"
-# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2016
-msgid "Source NMUs and the Bug Tracking System"
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2009
+msgid "The way to version NMUs differs for native and non-native packages."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2018
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2012
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 "
-"unified context diff (<literal>diff -u</literal>) detailing their changes to "
-"the Bug Tracking System."
+"If the package is a native package (without a debian revision in the version "
+"number), the version must be the version of the last maintainer upload, plus "
+"<literal>+nmu<replaceable>X</replaceable></literal>, where <replaceable>X</"
+"replaceable> is a counter starting at <literal>1</literal>. If the last "
+"upload was also an NMU, the counter should be increased. For example, if "
+"the current version is <literal>1.5</literal>, then an NMU would get version "
+"<literal>1.5+nmu1</literal>."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2024
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2022
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 "
-"described in <xref linkend=\"binary-only-nmu\"/> which doesn't require any "
-"patch to be sent. If you want the package to be recompiled for all "
-"architectures, then you do a source NMU as usual and you will have to send a "
-"patch."
+"If the package is a not a native package, you should add a minor version "
+"number to the debian revision part of the version number (the portion after "
+"the last hyphen). This extra number must start at 1. For example, if the "
+"current version is <literal>1.5-2</literal>, then an NMU would get version "
+"<literal>1.5-2.1</literal>. If a new upstream version is packaged in the "
+"NMU, the debian revision is set to <literal>0</literal>, for example "
+"<literal>1.6-0.1</literal>."
msgstr ""
-# type: Content of: <chapter><section><section><para>
+#
. type: Content of: <chapter><section><section><para>
#: 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 "
-"NMU version."
+"In both cases, if the last upload was also an NMU, the counter should be "
+"increased. For example, if the current version is <literal>1.5+nmu3</"
+"literal> (a native package which has already been NMUed), the NMU would get "
+"version <literal>1.5+nmu4</literal>. ."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2036
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2037
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, "
-"it was custom to open a new bug and include a patch showing all the changes "
-"you have made. The normal maintainer will either apply the patch or employ "
-"an alternate method of fixing the problem. Sometimes bugs are fixed "
-"independently upstream, which is another good reason to back out an NMU's "
-"patch. If the maintainer decides not to apply the NMU's patch but to "
-"release a new version, the maintainer needs to ensure that the new upstream "
-"version really fixes each problem that was fixed in the non-maintainer "
-"release."
+"A special versioning scheme is needed to avoid disrupting the maintainer's "
+"work, since using an integer for the Debian revision will potentially "
+"conflict with a maintainer upload already in preparation at the time of an "
+"NMU, or even one sitting in the ftp NEW queue. It also has the benefit of "
+"making it visually clear that a package in the archive was not made by the "
+"official maintainer."
msgstr ""
-# type: Content of: <chapter><section><section><para>
+#
. type: Content of: <chapter><section><section><para>
#: 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 "
-"of course, also keep the changes. If you revert some of the changes, please "
-"reopen the relevant bug reports."
+"If you upload a package to testing or stable, you sometimes need to \"fork\" "
+"the version number tree. This is the case for security uploads, for "
+"example. For this, a version of the form <literal>+deb<replaceable>XY</"
+"replaceable>u<replaceable>Z</replaceable></literal> should be used, where "
+"<replaceable>X</replaceable> and <replaceable>Y</replaceable> are the major "
+"and minor release numbers, and <replaceable>Z</replaceable> is a counter "
+"starting at <literal>1</literal>. When the release number is not yet known "
+"(often the case for <literal>testing</literal>, at the beginning of release "
+"cycles), the lowest release number higher than the last stable release "
+"number must be used. For example, while Etch (Debian 4.0) is stable, a "
+"security NMU to stable for a package at version <literal>1.5-3</literal> "
+"would have version <literal>1.5-3+deb40u1</literal>, whereas a security NMU "
+"to Lenny would get version <literal>1.5-3+deb50u1</literal>. After the "
+"release of Lenny, security uploads to the <literal>testing</literal> "
+"distribution will be versioned <literal>+deb51uZ</literal>, until it is "
+"known whether that release will be Debian 5.1 or Debian 6.0 (if that becomes "
+"the case, uploads will be versioned as <literal>+deb60uZ</literal>."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2055
-msgid "Building source NMUs"
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:2069
+msgid "Using the <literal>DELAYED/</literal> queue"
+msgstr "<literal>DELAYED/</literal> キューを使う"
+
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2072
+msgid ""
+"Having to wait for a response after you request permission to NMU is "
+"inefficient, because it costs the NMUer a context switch to come back to the "
+"issue. The <literal>DELAYED</literal> queue (see <xref linkend=\"delayed-"
+"incoming\"/>) allows the developer doing the NMU to perform all the "
+"necessary tasks at the same time. For instance, instead of telling the "
+"maintainer that you will upload the updated package in 7 days, you should "
+"upload the package to <literal>DELAYED/7</literal> and tell the maintainer "
+"that he has 7 days to react. During this time, the maintainer can ask you "
+"to delay the upload some more, or cancel your upload."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2057
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2086
msgid ""
-"Source NMU packages are built normally. Pick a distribution using the same "
-"rules as found in <xref linkend=\"distribution\"/> , follow the other "
-"instructions in <xref linkend=\"upload\"/> ."
+"The <literal>DELAYED</literal> queue should not be used to put additional "
+"pressure on the maintainer. In particular, it's important that you are "
+"available to cancel or delay the upload before the delay expires since the "
+"maintainer cannot cancel the upload himself."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2062
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2093
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 "
-"NMU entry of the <filename>debian/changelog</filename> file will be used for "
-"signing the changes file."
+"If you make an NMU to <literal>DELAYED</literal> and the maintainer updates "
+"his package before the delay expires, your upload will be rejected because a "
+"newer version is already available in the archive. Ideally, the maintainer "
+"will take care to include your proposed changes (or at least a solution for "
+"the problems they address) in that upload."
msgstr ""
-# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2070
-msgid "Acknowledging an NMU"
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:2103
+msgid "NMUs from the maintainer's point of view"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2072
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2106
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 "
-"that has been sent to you. Once this is done, you have to close the bugs "
-"that have been tagged fixed by the NMU. The easiest way is to use the "
-"<literal>-v</literal> option of <command>dpkg-buildpackage</command>, as "
-"this allows you to include just all changes since your last maintainer "
-"upload. Alternatively, you can close them manually by sending the required "
-"mails to the BTS or by adding the required <literal>closes: #nnnn</literal> "
-"in the changelog entry of your next upload."
+"When someone NMUs your package, this means they want to help you to keep it "
+"in good shape. This gives users fixed packages faster. You can consider "
+"asking the NMUer to become a co-maintainer of the package. Receiving an NMU "
+"on a package is not a bad thing; it just means that the package is "
+"interesting enough for other people to work on it."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2083
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2115
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 "
-"about the package that they were willing to help you in your work, so you "
-"should be thankful. You may also want to ask them if they would be "
-"interested in helping you on a more frequent basis as co-maintainer or "
-"backup maintainer (see <xref linkend=\"collaborative-maint\"/> )."
+"To acknowledge an NMU, include its changes and changelog entry in your next "
+"maintainer upload. If you do not acknowledge the NMU by including the NMU "
+"changelog entry in your changelog, the bugs will remain closed in the BTS "
+"but will be listed as affecting your maintainer version of the package."
msgstr ""
-# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2093
-msgid "NMU vs QA uploads"
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:2124
+msgid "Source NMUs vs Binary-only NMUs (binNMUs)"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2095
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2127
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 "
-"packages which haven't had their maintainer set correctly is available at "
-"<ulink url=\"&url-debian-qa-orphaned;\"></ulink>. If you perform an NMU on "
-"an improperly orphaned package, please set the maintainer to <literal>Debian "
-"QA Group <packages@qa.debian.org></literal>."
+"The full name of an NMU is <emphasis>source NMU</emphasis>. There is also "
+"another type, namely the <emphasis>binary-only NMU</emphasis>, or "
+"<emphasis>binNMU</emphasis>. A binNMU is also a package upload by someone "
+"other than the package's maintainer. However, it is a binary-only upload."
msgstr ""
-# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2105
-msgid "Who can do an NMU"
-msgstr "誰が NMU 可能なのか"
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2134
+msgid ""
+"When a library (or other dependency) is updated, the packages using it may "
+"need to be rebuilt. Since no changes to the source are needed, the same "
+"source package is used."
+msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2107
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2140
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-"
-"developers, however, are encouraged to download the source package and start "
-"hacking on it to fix problems; however, rather than doing an NMU, they "
-"should just submit worthwhile patches to the Bug Tracking System. "
-"Maintainers almost always appreciate quality patches and bug reports."
+"BinNMUs are usually triggered on the buildds by wanna-build. An entry is "
+"added to debian/changelog, explaining why the upload was needed and "
+"increasing the version number as described in <xref linkend=\"binary-only-nmu"
+"\"/>. This entry should not be included in the next upload."
msgstr ""
-# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2117
-msgid "Terminology"
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2148
+msgid ""
+"Buildds upload packages for their architecture to the archive as binary-only "
+"uploads. Strictly speaking, these are binNMUs. However, they are not "
+"normally called NMU, and they don't add an entry to debian/changelog."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2119
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:2156
+msgid "NMUs vs QA uploads"
+msgstr "NMU vs QA アップロード"
+
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2159
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 <literal>non-"
-"maintainer</literal> upload."
+"NMUs are uploads of packages by somebody else than their assigned "
+"maintainer. There is another type of upload where the uploaded package is "
+"not yours: QA uploads. QA uploads are uploads of orphaned packages."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2127
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2166
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. "
-"Source NMUs always involves changes to the source (even if it is just a "
-"change to <filename>debian/changelog</filename>). This can be either a "
-"change to the upstream source, or a change to the Debian bits of the "
-"source. Note, however, that source NMUs may also include architecture-"
-"dependent packages, as well as an updated Debian diff."
+"QA uploads are very much like normal maintainer uploads: they may fix "
+"anything, even minor issues; the version numbering is normal, and there is "
+"no need to use a delayed upload. The difference is that you are not listed "
+"as the Maintainer or Uploader for the package. Also, the changelog entry of "
+"a QA upload has a special first line:"
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2136
+#. type: Content of: <chapter><section><section><screen>
+#: pkgs.dbk:2174
+#, no-wrap
+msgid " * QA upload.\n"
+msgstr " * QA upload.\n"
+
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2178
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 "
-"binary-only NMU is a non-maintainer uploaded binary version of a package, "
-"with no source changes required. There are many cases where porters must "
-"fix problems in the source in order to get them to compile for their target "
-"architecture; that would be considered a source NMU rather than a binary-"
-"only NMU. As you can see, we don't distinguish in terminology between "
-"porter NMUs and non-porter NMUs."
+"If you want to do an NMU, and it seems that the maintainer is not active, it "
+"is wise to check if the package is orphaned (this information is displayed "
+"on the package's Package Tracking System page). When doing the first QA "
+"upload to an orphaned package, the maintainer should be set to "
+"<literal>Debian QA Group <packages@qa.debian.org></literal>. Orphaned "
+"packages which did not yet have a QA upload still have their old maintainer "
+"set. There is a list of them at <ulink url=\"&url-orphaned-not-qa;\"/>."
msgstr ""
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2146
+#
. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2189
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 "
-"``source NMU'' when they think ``NMU''. So it's best to be careful: always "
-"use ``binary NMU'' or ``binNMU'' for binary-only NMUs."
+"Instead of doing a QA upload, you can also consider adopting the package by "
+"making yourself the maintainer. You don't need permission from anybody to "
+"adopt an orphaned package, you can just set yourself as maintainer and "
+"upload the new version (see <xref linkend=\"adopting\"/>)."
msgstr ""
# type: Content of: <chapter><section><title>
-#: pkgs.dbk:2156
+#. type: Content of: <chapter><section><title>
+#: pkgs.dbk:2200
msgid "Collaborative maintenance"
msgstr "共同メンテナンス"
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:2158
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:2202
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:2166
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:2210
msgid ""
"Generally there is a primary maintainer and one or more co-maintainers. The "
"primary maintainer is the person whose name is listed in the "
msgstr ""
# type: Content of: <chapter><section><para>
-#: pkgs.dbk:2174
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:2218
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:2180
+#. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:2224
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:2188
+#. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:2232
msgid ""
"Add the co-maintainer's correct maintainer name and address to the "
"<literal>Uploaders</literal> field in the first paragraph of the "
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><screen>
-#: pkgs.dbk:2192
-#, fuzzy, no-wrap
-msgid ""
-"\n"
-"Uploaders: John Buzz <jbuzz@debian.org>, Adam Rex <arex@debian.org>\n"
-msgstr "Uploaders: John Buzz <jbuzz@debian.org>, Adam Rex <arex@debian.org>"
+#. type: Content of: <chapter><section><itemizedlist><listitem><screen>
+#: pkgs.dbk:2237
+#, no-wrap
+msgid "Uploaders: John Buzz <jbuzz@debian.org>, Adam Rex <arex@debian.org>\n"
+msgstr "Uploaders: John Buzz <jbuzz@debian.org>, Adam Rex <arex@debian.org>\n"
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2198
+#. type: Content of: <chapter><section><itemizedlist><listitem><para>
+#: pkgs.dbk:2242
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:2204
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:2248
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:2213
+#. type: Content of: <chapter><section><orderedlist><listitem><para>
+#: pkgs.dbk:2257
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:2220
+#. type: Content of: <chapter><section><orderedlist><listitem><para>
+#: pkgs.dbk:2264
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:2228
+#. type: Content of: <chapter><section><para>
+#: pkgs.dbk:2272
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:2236
+#. type: Content of: <chapter><section><title>
+#: pkgs.dbk:2280
msgid "The testing distribution"
msgstr "テスト版ディストリビューション"
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2238
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:2282
msgid "Basics"
msgstr "基本"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2240
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2284
msgid ""
"Packages are usually installed into the <literal>testing</literal> "
"distribution after they have undergone some degree of <literal>testing</"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2245
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2289
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-"
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2254
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:2298
msgid "Updates from unstable"
msgstr "不安定版からの更新"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2256
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2300
msgid ""
"The scripts that update the <literal>testing</literal> distribution are run "
"twice each day, right after the installation of the updated packages; these "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2264
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2308
msgid ""
"The inclusion of a package from <literal>unstable</literal> is conditional "
"on the following:"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2270
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:2314
msgid ""
"The package must have been available in <literal>unstable</literal> for 2, 5 "
"or 10 days, depending on the urgency (high, medium or low). Please note "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2280
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:2324
msgid ""
"It must not have new release-critical bugs (RC bugs affecting the version "
"available in <literal>unstable</literal>, but not affecting the version in "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2287
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:2331
msgid ""
"It must be available on all architectures on which it has previously been "
-"built in <literal>unstable</literal>. <xref linkend=\"dak ls\"/> may be of "
+"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:2294
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:2338
msgid ""
"It must not break any dependency of a package which is already available in "
"<literal>testing</literal>;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2300
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:2344
msgid ""
"The packages on which it depends must either be available in "
"<literal>testing</literal> or they must be accepted into <literal>testing</"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2308
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2352
msgid ""
"To find out whether a package is progressing into <literal>testing</literal> "
"or not, see the <literal>testing</literal> script output on the <ulink url="
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2319
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2363
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:2326
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2370
msgid ""
"Sometimes, some packages never enter <literal>testing</literal> because the "
"set of inter-relationship is too complicated and cannot be sorted out by the "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2331
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2375
msgid ""
"Some further dependency analysis is shown on <ulink url=\"http://release."
"debian.org/migration/\"></ulink> — but be warned, this page also shows build "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2336
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:2380
msgid "out-of-date"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
#. FIXME: better rename this file than document rampant professionalism?
-#: pkgs.dbk:2339
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2383
msgid ""
"For the <literal>testing</literal> migration script, outdated means: There "
"are different versions in <literal>unstable</literal> for the release "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2347
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2391
msgid "Consider this example:"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2354 pkgs.dbk:2387
+#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
+#: pkgs.dbk:2398 pkgs.dbk:2431
msgid "alpha"
msgstr "alpha"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2355 pkgs.dbk:2388
+#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
+#: pkgs.dbk:2399 pkgs.dbk:2432
msgid "arm"
msgstr "arm"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2360 pkgs.dbk:2394 pkgs.dbk:2456
+#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
+#: pkgs.dbk:2404 pkgs.dbk:2438 pkgs.dbk:2500
msgid "testing"
msgstr "テスト版"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2361 pkgs.dbk:2366 pkgs.dbk:2395 pkgs.dbk:2396 pkgs.dbk:2403
+#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
+#: pkgs.dbk:2405 pkgs.dbk:2410 pkgs.dbk:2439 pkgs.dbk:2440 pkgs.dbk:2447
msgid "1"
msgstr "1"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2362 pkgs.dbk:2397 pkgs.dbk:2402
+#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
+#: pkgs.dbk:2406 pkgs.dbk:2441 pkgs.dbk:2446
msgid "-"
msgstr "-"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2365 pkgs.dbk:2400 pkgs.dbk:2457
+#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
+#: pkgs.dbk:2409 pkgs.dbk:2444 pkgs.dbk:2501
msgid "unstable"
msgstr "不安定版"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2367 pkgs.dbk:2401
+#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
+#: pkgs.dbk:2411 pkgs.dbk:2445
msgid "2"
msgstr "2"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2373
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2417
msgid ""
"The package is out of date on alpha in <literal>unstable</literal>, and will "
"not go to <literal>testing</literal>. Removing the package would not help at "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2379
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2423
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:2389
+#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
+#: pkgs.dbk:2433
msgid "hurd-i386"
msgstr "hurd-i386"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2409
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2453
msgid ""
"In this case, the package is up to date on all release architectures in "
"<literal>unstable</literal> (and the extra <literal>hurd-i386</literal> "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2414
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2458
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:2421
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:2465
msgid "Removals from testing"
msgstr "テスト版からの削除"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2423
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2467
msgid ""
"Sometimes, a package is removed to allow another package in: This happens "
"only to allow <emphasis>another</emphasis> package to go in if it's ready in "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2430
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2474
msgid ""
"Of course, there is another reason to remove a package from <literal>testing "
"</literal>: It's just too buggy (and having a single RC-bug is enough to be "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2435
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2479
msgid ""
"Furthermore, if a package has been removed from <literal>unstable</literal>, "
"and no package in <literal>testing</literal> depends on it any more, then it "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2442
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:2486
msgid "circular dependencies"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2444
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2488
msgid ""
"A situation which is not handled very well by britney is if package "
"<literal>a</literal> depends on the new version of package <literal>b</"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2449
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2493
msgid "An example of this is:"
msgstr ""
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2462
+#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
+#: pkgs.dbk:2506
msgid "a"
msgstr "a"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2463
+#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
+#: pkgs.dbk:2507
msgid "1; depends: b=1"
msgstr "1; depends: b=1"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2464
+#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
+#: pkgs.dbk:2508
msgid "2; depends: b=2"
msgstr "2; depends: b=2"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2467
+#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
+#: pkgs.dbk:2511
msgid "b"
msgstr "b"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2468
+#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
+#: pkgs.dbk:2512
msgid "1; depends: a=1"
msgstr "1; depends: a=1"
# type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2469
+#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
+#: pkgs.dbk:2513
msgid "2; depends: a=2"
msgstr "2; depends: a=2"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2475
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2519
msgid ""
"Neither package <literal>a</literal> nor package <literal>b</literal> is "
"considered for update."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2479
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2523
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:2486
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:2530
msgid "influence of package in testing"
msgstr "テスト版パッケージへの影響"
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2488
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2532
msgid ""
"Generally, there is nothing that the status of a package in <literal>testing "
"</literal> means for transition of the next version from <literal>unstable </"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2500
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2544
msgid ""
"In summary this means: The only influence that a package being in <literal> "
"testing</literal> has on a new version of the same package is that the new "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2507
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:2551
msgid "details"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2509
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2553
msgid "If you are interested in details, this is how britney works:"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2512
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2556
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:2521
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2565
msgid ""
"Now, the more complex part happens: Britney tries to update <literal>testing "
"</literal> with the valid candidates. For that, britney tries to add each "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2531
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2575
msgid ""
"If you want to see more details, you can look it up on <filename>merkel:/org/"
"&ftp-debian-org;/testing/update_out/</filename> (or in <filename>merkel:~aba/"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2538
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2582
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:2546
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:2590
msgid "Direct updates to testing"
msgstr "直接テスト版を更新する"
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2548
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2592
msgid ""
"The <literal>testing</literal> distribution is fed with packages from "
"<literal>unstable</literal> according to the rules explained above. "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2555
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2599
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:2562
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2606
msgid ""
"You should not upload to <literal>testing-proposed-updates</literal> when "
"you can update your packages through <literal>unstable</literal>. If you "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2571
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2615
msgid ""
"Version numbers are usually selected by adding the codename of the "
"<literal>testing</literal> distribution and a running number, like "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2578
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:2622
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:2583
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:2627
msgid ""
"Make sure that your package really needs to go through <literal>testing-"
"proposed-updates</literal>, and can't go through <literal> unstable</"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2590
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:2634
msgid "Make sure that you included only the minimal amount of changes;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2595
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:2639
msgid ""
"Make sure that you included an appropriate explanation in the changelog;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2600
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:2644
msgid ""
"Make sure that you've written <literal>testing</literal> or <literal>testing-"
"proposed-updates</literal> into your target distribution;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2606
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:2650
msgid ""
"Make sure that you've built and tested your package in <literal>testing</"
"literal>, not in <literal>unstable</literal>;"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2612
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:2656
msgid ""
"Make sure that your version number is higher than the version in "
"<literal>testing</literal> and <literal>testing-proposed-updates</literal>, "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2619
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:2663
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:2627
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:2671
msgid "Frequently asked questions"
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2629
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:2673
msgid "What are release-critical bugs, and how do they get counted?"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2631
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2675
msgid ""
"All bugs of some higher severities are by default considered release-"
"critical; currently, these are <literal>critical</literal>, <literal>grave</"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2636
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2680
msgid ""
"Such bugs are presumed to have an impact on the chances that the package "
"will be released with the <literal>stable</literal> release of Debian: in "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2643
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2687
msgid ""
"The <literal>unstable</literal> bug count are all release-critical bugs "
"which are marked to apply to <replaceable>package</replaceable>/"
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2651
+#. type: Content of: <chapter><section><section><section><title>
+#: pkgs.dbk:2695
msgid ""
"How could installing a package into <literal>testing</literal> possibly "
"break other packages?"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2654
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2698
msgid ""
"The structure of the distribution archives is such that they can only "
"contain one version of a package; a package is defined by its name. So when "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2662
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2706
msgid ""
"However, the old version may have provided a binary package with an old "
"soname of a library, such as <literal>libacme-foo0</literal>. Removing the "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2668
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2712
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:2674
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2718
msgid ""
"When the set of binary packages provided by a source package change in this "
"way, all the packages that depended on the old binaries will have to be "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2685
+#. type: Content of: <chapter><section><section><section><para>
+#: pkgs.dbk:2729
msgid ""
"If you are having problems with complicated groups of packages like this, "
"contact &email-debian-devel; or &email-debian-release; for help."
~ianmdlvl / developers-reference.git / blobdiff