X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=po4a%2Fja%2Fpkgs.po;h=835f0af334b183f7debc6e2799a6775270523780;hp=d8f4741a05f789f5ca8296aa9eedb1d4ae696b59;hb=15d1283ae81e825d20f2d5f72810f608a7b53011;hpb=643c04845a63460b5b6a4a41bad65a9c31cd8a57 diff --git a/po4a/ja/pkgs.po b/po4a/ja/pkgs.po index d8f4741..835f0af 100644 --- a/po4a/ja/pkgs.po +++ b/po4a/ja/pkgs.po @@ -1,37 +1,42 @@ # Debian Developer's Reference (Japanese) -# Hideki Yamane (Debian-JP) , 2008. +# Hideki Yamane (Debian-JP) , 2008-2010. # msgid "" msgstr "" -"Project-Id-Version: developers-reference 3.4.0\n" -"POT-Creation-Date: 2008-10-03 12:09+0900\n" -"PO-Revision-Date: 2008-03-05 18:30+0900\n" -"Last-Translator: Hideki Yamane (Debian-JP) \n" +"Project-Id-Version: developers-reference 3.4.4\n" +"POT-Creation-Date: 2010-11-21 07:59-0400\n" +"PO-Revision-Date: 2010-08-23 18:27+0900\n" +"Last-Translator: Hideki Yamane \n" "Language-Team: Debian JP Project \n" +"Language: Japanese\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" # type: Content of: +#. 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 "" "この章では、パッケージの作成、アップロード、メンテナンス、移植についての情報" -"を取り扱います。" +"を扱います。" # 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 " @@ -41,19 +46,34 @@ msgid "" "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 " -"must then submit a bug report (<xref linkend=\"submit-bug\"/> ) against the " +"must then submit a bug report (<xref linkend=\"submit-bug\"/>) against the " "pseudo-package <systemitem role=\"package\">wnpp</systemitem> describing " "your plan to create a new package, including, but not limiting yourself to, " "a description of the package, the license of the prospective package, and " "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</" @@ -63,90 +83,152 @@ msgid "" "<literal>wishlist</literal>. Please send a copy to &email-debian-devel; by " "using the X-Debbugs-CC header (don't use CC:, because that way the message's " "subject won't indicate the bug number). If you are packaging so many new " -"packages (>10) that notifying the mailing list in seperate messages is too " -"disruptive, do send a summary after filing the bugs to the debian-devel list " +"packages (>10) that notifying the mailing list in separate messages is too " +"disruptive, send a summary after filing the bugs to the debian-devel list " "instead. This will inform the other developers about upcoming packages and " "will allow a review of your description and package name." msgstr "" +"サブジェクトを <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></" +"Please include a <literal>Closes: #<replaceable>nnnnn</replaceable></" "literal> entry in the changelog of the new package in order for the bug " "report to be automatically closed once the new package is installed in the " -"archive (see <xref linkend=\"upload-bugfix\"/> )." +"archive (see <xref linkend=\"upload-bugfix\"/>)." msgstr "" +"新規パッケージがアーカイブへインストールされる際にバグ報告を自動的に閉じるた" +"め、<literal>Closes: #<replaceable>nnnnn</replaceable></literal> というエント" +"リを新規パッケージの changelog 内に含めてください (<xref linkend=\"upload-" +"bugfix\"/> を参照)。" -# type: Content of: <chapter><section><para> +# FIXME: ftpmaster@debian.org +#. type: Content of: <chapter><section><para> #: pkgs.dbk:51 msgid "" -"When closing security bugs include CVE numbers as well as the Closes: " -"#nnnnn. This is useful for the security team to track vulnerabilities. If " -"an upload is made to fix the bug before the advisory ID is known, it is " -"encouraged to modify the historical changelog entry with the next upload. " -"Even in this case, please include all available pointers to background " -"information in the original changelog entry." +"If you think your package needs some explanations for the administrators of " +"the NEW package queue, include them in your changelog, send to &email-" +"ftpmaster; a reply to the email you receive as a maintainer after your " +"upload, or reply to the rejection email in case you are already re-uploading." msgstr "" +"パッケージについて、NEW パッケージキューの管理者への説明が必要だろうと思う場" +"合は、changelog に説明を含めて &email-ftpmaster; へ送ってください。アップロー" +"ド後であればメンテナとして受け取ったメールに返信してください。もしくは既に再" +"アップロードをの最中の場合は reject のメールに対して返信してください。" + +# 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 " +"<literal>Closes: #<replaceable>nnnnn</replaceable></literal>. This is " +"useful for the security team to track vulnerabilities. If an upload is made " +"to fix the bug before the advisory ID is known, it is encouraged to modify " +"the historical changelog entry with the next upload. Even in this case, " +"please include all available pointers to background information in the " +"original changelog entry." +msgstr "" +"セキュリティバグを閉じる場合は、CVE 番号を <literal>Closes: " +"#<replaceable>nnnnn</replaceable></literal> と同じく含めるようにしてくださ" +"い。これは、セキュリティチームが脆弱性を追跡するのに役立ちます。アドバイザリ" +"の ID が分かる前にバグ修正のためのアップロードが行われた場合は、以前の " +"changelog エントリを次のアップロード時に修正するのが推奨されています。このよ" +"うな場合でも、元々の changelog での記載に可能な限り背景情報へのポインタを全て" +"含めてください。" # type: Content of: <chapter><section><para> -#: pkgs.dbk:59 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:66 msgid "" "There are a number of reasons why we ask maintainers to announce their " "intentions:" msgstr "" +"我々がメンテナに意図しているところをアナウンスする様に求めるのには、いくつも" +"の理由があります。" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:65 +#. type: Content of: <chapter><section><itemizedlist><listitem><para> +#: pkgs.dbk:72 msgid "" "It helps the (potentially new) maintainer to tap into the experience of " "people on the list, and lets them know if anyone else is working on it " "already." msgstr "" +"(潜在的な新たな) メンテナが、メーリングリストの人々の経験を活かすのを手助け" +"し、もし他の誰かが既に作業を行っていた場合に知らせる。" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:71 +#. type: Content of: <chapter><section><itemizedlist><listitem><para> +#: pkgs.dbk:78 msgid "" "It lets other people thinking about working on the package know that there " "already is a volunteer, so efforts may be shared." msgstr "" +"そのパッケージについて作業することを検討している他の人へ、既に作業をしている" +"ボランティアがいることを知らせ、労力が共有される。" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:77 +#. type: Content of: <chapter><section><itemizedlist><listitem><para> +#: pkgs.dbk:84 msgid "" "It lets the rest of the maintainers know more about the package than the one " "line description and the usual changelog entry ``Initial release'' that gets " "posted to &email-debian-devel-changes;." msgstr "" +"&email-debian-devel-changes; に流される一行の説明文 (description) と通常どお" +"りの「Intial release」という changelog エントリよりも、残った他のメンテナが" +"パッケージに関してより深く知ることができる。" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:84 +#. type: Content of: <chapter><section><itemizedlist><listitem><para> +#: pkgs.dbk:91 msgid "" "It is helpful to the people who live off <literal>unstable</literal> (and " "form our first line of testers). We should encourage these people." msgstr "" +"<literal>不安定版 (unstable)</literal> で暮らす人 (そして最前線のテスターであ" +"る人) の助けになる。" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:90 +#. type: Content of: <chapter><section><itemizedlist><listitem><para> +#: pkgs.dbk:97 msgid "" "The announcements give maintainers and other interested parties a better " "feel of what is going on, and what is new, in the project." msgstr "" +"メンテナや他に興味を持つ人々へ、プロジェクトで何が行われているのか、何か新し" +"いことがあるかということ関して、告知は良い印象を与える。" # type: Content of: <chapter><section><para> -#: pkgs.dbk:96 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:103 msgid "" "Please see <ulink url=\"http://&ftp-master-host;/REJECT-FAQ.html\"></ulink> " "for common rejection reasons for a new package." msgstr "" +"新しいパッケージに対する一般的な拒否理由については <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:109 msgid "Recording changes in the package" msgstr "パッケージの変更を記録する" # type: Content of: <chapter><section><para> -#: pkgs.dbk:104 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:111 msgid "" "Changes that you make to the package need to be recorded in the " "<filename>debian/changelog</filename>. These changes should provide a " @@ -157,76 +239,111 @@ msgid "" "<filename>/usr/share/doc/<replaceable>package</replaceable>/changelog.gz</" "filename> for native packages." msgstr "" +"パッケージについて行った変更は <filename>debian/changelog</filename> に記録さ" +"れなくてはいけません。これらの変更には、何が変更されたのか、(不確かであれば) " +"何故なのか、そしてどのバグが閉じられたのかの簡潔な説明文を付加する必要があり" +"ます。このファイルは <filename>/usr/share/doc/<replaceable>package</" +"replaceable>/changelog.Debian.gz</filename>、あるいは native パッケージの場合" +"は <filename>/usr/share/doc/<replaceable>package</replaceable>/changelog.gz</" +"filename> にインストールされます。" # type: Content of: <chapter><section><para> -#: pkgs.dbk:115 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:122 msgid "" "The <filename>debian/changelog</filename> file conforms to a certain " "structure, with a number of different fields. One field of note, the " "<literal>distribution</literal>, is described in <xref linkend=\"distribution" -"\"/> . More information about the structure of this file can be found in " -"the Debian Policy section titled <filename>debian/changelog</filename>." +"\"/>. More information about the structure of this file can be found in the " +"Debian Policy section titled <filename>debian/changelog</filename>." msgstr "" +"<filename>debian/changelog</filename> ファイルは、幾つもの異なった項目からな" +"る特定の構造に従っています。一点を取り上げてみると、<literal>distribution</" +"literal> については<xref linkend=\"distribution\"/>に記述されています。この" +"ファイルの構造について、より詳細な情報は Debian ポリシーの <filename>debian/" +"changelog</filename> という章で確認できます。" # type: Content of: <chapter><section><para> -#: pkgs.dbk:123 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:130 msgid "" "Changelog entries can be used to automatically close Debian bugs when the " "package is installed into the archive. See <xref linkend=\"upload-bugfix\"/" -"> ." +">." msgstr "" +"changelog への記載は、パッケージがアーカイブにインストールされる際、自動的に " +"Debian バグを閉じるのに利用できます。<xref linkend=\"upload-bugfix\"/> を参照" +"してください。" # type: Content of: <chapter><section><para> -#: pkgs.dbk:127 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:134 msgid "" "It is conventional that the changelog entry of a package that contains a new " "upstream version of the software looks like this:" msgstr "" +"ソフトウェアの新しい開発元のバージョン (new upstream version) を含むパッケー" +"ジの changelog エントリは、以下のようにするのが慣習です:" # 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:138 +#, no-wrap +msgid " * New upstream release.\n" +msgstr " * New upstream release.\n" # type: Content of: <chapter><section><para> -#: pkgs.dbk:134 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:141 msgid "" "There are tools to help you create entries and finalize the " "<filename>changelog</filename> for release — see <xref linkend=\"devscripts" -"\"/> and <xref linkend=\"dpkg-dev-el\"/> ." +"\"/> 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 -msgid "See also <xref linkend=\"bpp-debian-changelog\"/> ." +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:146 +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:151 msgid "Testing the package" msgstr "パッケージをテストする" # type: Content of: <chapter><section><para> -#: pkgs.dbk:146 +# FIXME: around +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:153 msgid "" "Before you upload your package, you should do basic testing on it. At a " "minimum, you should try the following activities (you'll need to have an " "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:160 msgid "" "Install the package and make sure the software works, or upgrade the package " "from an older version to your new version if a Debian package for it already " "exists." msgstr "" +"パッケージをインストールしてソフトウェアが動作するのを確認する、あるいは既に" +"そのソフトの Debian パッケージが存在している場合、パッケージを以前のバージョ" +"ンから新しいバージョンにアップグレードする。" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:160 +#. type: Content of: <chapter><section><itemizedlist><listitem><para> +#: pkgs.dbk:167 msgid "" "Run <command>lintian</command> over the package. You can run " "<command>lintian</command> as follows: <literal>lintian -v " @@ -236,96 +353,142 @@ msgid "" "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:176 msgid "" "Normally, a package should <emphasis>not</emphasis> be uploaded if it causes " "lintian to emit errors (they will start with <literal>E</literal>)." msgstr "" +"通常、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:180 msgid "" "For more information on <command>lintian</command>, see <xref linkend=" -"\"lintian\"/> ." +"\"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:186 msgid "" -"Optionally run <xref linkend=\"debdiff\"/> to analyze changes from an older " -"version, if one exists." +"Optionally run <command>debdiff</command> (see <xref linkend=\"debdiff\"/>) " +"to analyze changes from an older version, if one exists." msgstr "" +"もし古いバージョンがあれば、それからの変更点を分析するために追加で " +"<command>debdiff</command> を実行する (<xref linkend=\"debdiff\"/> を参照) 。" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:185 +#. type: Content of: <chapter><section><itemizedlist><listitem><para> +#: pkgs.dbk:192 msgid "" "Downgrade the package to the previous version (if one exists) — this tests " "the <filename>postrm</filename> and <filename>prerm</filename> scripts." msgstr "" +"(もしあれば) 以前のバージョンにダウングレードする — これは <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:198 msgid "Remove the package, then reinstall it." -msgstr "パッケージを削除して、再インストールしてください。" +msgstr "パッケージを削除して、再インストールする。" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:196 +#. type: Content of: <chapter><section><itemizedlist><listitem><para> +#: pkgs.dbk:203 msgid "" "Copy the source package in a different directory and try unpacking it and " "rebuilding it. This tests if the package relies on existing files outside " "of it, or if it relies on permissions being preserved on the files shipped " -"inside the .diff.gz file." +"inside the <filename>.diff.gz</filename> file." msgstr "" +"ソースパッケージを違うディレクトリにコピーして展開し、再構築する。これは、" +"パッケージが外部の既存ファイルに依っているか、<filename>.diff.gz</filename> " +"ファイル内に含まれているファイルで保存されている権限に依るかどうかをテストし" +"ます。" # type: Content of: <chapter><section><title> -#: pkgs.dbk:206 -#, fuzzy +#. type: Content of: <chapter><section><title> +#: pkgs.dbk:213 msgid "Layout of the source package" -msgstr "ソースパッケージの構造" +msgstr "ソースパッケージの概要" # type: Content of: <chapter><section><para> -#: pkgs.dbk:208 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:215 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:220 msgid "" "the so-called <literal>native</literal> packages, where there is no " "distinction between the original sources and the patches applied for Debian" msgstr "" +"いわゆる <literal>native</literal>パッケージ。元のソースと Debian で当てられ" +"たパッチの間に差が無いもの" -# type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:219 +#. type: Content of: <chapter><section><itemizedlist><listitem><para> +#: pkgs.dbk:226 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 "" +"オリジナルのソースコードの tarball ファイルに、Debian によって作成された変更" +"点を含む別のファイルが付随している (より一般的な) パッケージ" -# type: Content of: <chapter><section><para> -#: pkgs.dbk:225 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:232 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>)." -msgstr "" - -# type: Content of: <chapter><section><para> -#: pkgs.dbk:233 -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." -msgstr "" +"file (<filename>.dsc</filename>) and the source tarball (<filename>.tar.{gz," +"bz2,lzma}</filename>). A source package of a non-native package includes a " +"Debian source control file, the original source tarball (<filename>.orig.tar." +"{gz,bz2,lzma}</filename>) and the Debian changes (<filename>.diff.gz</" +"filename> for the source format “1.0” or <filename>.debian.tar.{gz,bz2,lzma}" +"</filename> for the source format “3.0 (quilt)”)." +msgstr "" +"native パッケージの場合、ソースパッケージは Debian のソース control ファイル " +"(<filename>.dsc</filename>) とソースコードの tarball (<filename>.tar.{gz,bz2," +"lzma}</filename>) を含んでいます。native ではないパッケージのソースパッケージ" +"は Debian のソース control ファイルと、オリジナルのソースコードの tarball " +"(<filename>.orig.tar.{gz,bz2,lzma}</filename>)、そして Debian での変更点 " +"(ソース形式“1.0”は <filename>.diff.gz</filename>、ソース形式“3.0 (quilt)”は " +"<filename>.debian.tar.{gz,bz2,lzma}</filename>) を含んでいます。" + +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:241 +msgid "" +"With source format “1.0”, whether a package is native or not was determined " +"by <command>dpkg-source</command> at build time. Nowadays it is recommended " +"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 "" +"ソース形式“1.0”では、パッケージが native かどうかはビルド時に <command>dpkg-" +"source</command> によって決められていました。最近では望むソース形式を " +"<filename>debian/source/format</filename> に“3.0 (quilt)”または“3.0 " +"(native)”と記述することによって明示することが推奨されています。この章の残りの" +"部分は native ではないパッケージについてのみ記しています。" # type: Content of: <chapter><section><para> -#: pkgs.dbk:239 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:248 msgid "" "The first time a version is uploaded which corresponds to a particular " "upstream version, the original source tar file should be uploaded and " @@ -333,94 +496,148 @@ msgid "" "same tar file should be used to build the new diffs and <filename>.dsc</" "filename> files, and will not need to be re-uploaded." msgstr "" +"初回には、特定の開発元のバージョン (upstream version) に該当するバージョンが" +"アップロードされます。元のソース tar ファイルは、アップロードされて " +"<filename>.changes</filename> ファイルに含まれている必要があります。その後、" +"新しい diff ファイルや <filename>.dsc</filename> ファイルの生成には全く同じ " +"tar ファイルを使わなければならず、これを再アップロードする必要はありません。" -# type: Content of: <chapter><section><para> -#: pkgs.dbk:246 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:255 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 "" +"デフォルトでは、<command>dpkg-genchanges</command> および <command>dpkg-" +"buildpackage</command> は前述されている changelog エントリと現在のエントリが" +"異なった upstream バージョンを持つ場合にのみ、オリジナルのソース tar ファイル" +"を含めようとします。この挙動は、<literal>-sa</literal> を使って常に含めたり、" +"<literal>-sd</literal> を使うことで常に含めないようにするように変更できます。" # type: Content of: <chapter><section><para> -#: pkgs.dbk:254 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:263 msgid "" "If no original source is included in the upload, the original source tar-" "file used by <command>dpkg-source</command> when constructing the <filename>." "dsc</filename> file and diff to be uploaded <emphasis>must</emphasis> be " "byte-for-byte identical with the one already in the archive." msgstr "" +"アップロード時にオリジナルのソースが含まれていない場合、アップロードされる " +"<filename>.dsc</filename> と diff ファイルを構築する際に <command>dpkg-" +"source</command> が使用するオリジナルの tar ファイルは、<emphasis>必ず</" +"emphasis>既にアーカイブにあるものと 1 バイトも違わぬものでなくてはなりませ" +"ん。" -# type: Content of: <chapter><section><para> -#: pkgs.dbk:261 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:270 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." -msgstr "" +"not present in the <filename>*.orig.tar.{gz,bz2,lzma}</filename> 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 "" +"注意していただきたいのですが、native ではないパッケージでは、diff はパッチ内" +"のファイルパーミッションを保存しないので、<filename>*.orig.tar.{gz,bz2,lzma}" +"</filename> 内に存在しないファイルのパーミッションは保持されません。しかし、" +"ソース形式“3.0 (quilt)”を使っている場合、<filename>debian</filename> ディレク" +"トリ内にあるファイルのパーミッションは tar アーカイブで保存されるのでそのまま" +"になります。" # type: Content of: <chapter><section><title> -#: pkgs.dbk:268 +#. type: Content of: <chapter><section><title> +#: pkgs.dbk:279 msgid "Picking a distribution" -msgstr "" +msgstr "ディストリビューションを選ぶ" # type: Content of: <chapter><section><para> -#: pkgs.dbk:270 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:281 msgid "" "Each upload needs to specify which distribution the package is intended " "for. The package build process extracts this information from the first " "line of the <filename>debian/changelog</filename> file and places it in the " -"<literal>Distribution</literal> field of the <literal>.changes</literal> " +"<literal>Distribution</literal> field of the <filename>.changes</filename> " "file." msgstr "" +"アップロードでは、パッケージがどのディストリビューション向けになっているかを" +"指定してあることが必要です。パッケージの構築プロセスでは、<filename>debian/" +"changelog</filename> ファイルの最初の行からこの情報を展開し、<filename>." +"changes</filename> ファイルの <literal>Distribution</literal> 欄に配置しま" +"す。" # type: Content of: <chapter><section><para> -#: pkgs.dbk:276 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:287 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:293 msgid "" "Actually, there are two other possible distributions: <literal>stable-" -"security </literal> and <literal>testing-security</literal>, but read <xref " +"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:298 msgid "" "It is not possible to upload a package into several distributions at the " "same time." msgstr "" +"同時に複数のディストリビューションへパッケージをアップロードすることはできま" +"せん。" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:291 +#. type: Content of: <chapter><section><section><title> +#: pkgs.dbk:302 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:305 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 " "the next point release." msgstr "" +"<literal>安定版 (stable)</literal> へのアップロードは、安定版リリースマネー" +"ジャによるレビューのため、パッケージが <literal>proposed-updates-new</" +"literal> キューに転送され、許可された場合は Debian アーカイブの " +"<filename>stable-proposed-updates</filename> ディレクトリにインストールされま" +"す。" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:302 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:313 msgid "" "To ensure that your upload will be accepted, you should discuss the changes " "with the stable release team before you upload. For that, send a mail to the " @@ -429,32 +646,46 @@ msgid "" "verbose and detailed in your changelog entries for uploads to the " "<literal>stable</literal> distribution." msgstr "" +"アップロードが許可されるのを確実にするには、アップロードの前に変更点について" +"安定版リリースチームと協議する必要があります。そのためには、<literal>安定版 " +"(stable)</literal> にある現在のパッケージバージョンに適用したいパッチを含めた" +"メールを &email-debian-release; メーリングリストに送ってください。<literal>安" +"定版 (stable)</literal> ディストリビューションへアップロードするパッケージの " +"changelog のエントリには常にくどいほど詳細にしてください。" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:310 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:321 msgid "" "Extra care should be taken when uploading to <literal>stable</literal>. " "Basically, a package should only be uploaded to <literal>stable</literal> if " "one of the following happens:" msgstr "" +"<literal>安定版 (stable)</literal> へのアップロード時には特に注意を払うことが" +"必要です。基本的に、以下のいずれかが起こった際にのみ <literal>安定版 (stable)" +"</literal> へパッケージはアップロードされます:" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:317 +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:328 msgid "a truly critical functionality problem" -msgstr "" +msgstr "本当に致命的な機能の問題がある" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:322 +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:333 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:338 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:343 msgid "" "In the past, uploads to <literal>stable</literal> were used to address " "security problems as well. However, this practice is deprecated, as uploads " @@ -466,16 +697,28 @@ msgid "" "managers are usually willing to include your fix nonetheless in a regular " "upload to <literal>stable</literal>." msgstr "" +"以前、<literal>安定版 (stable)</literal> へのアップロードはセキュリティ問題へ" +"の対処と同等に取り扱われていました。しかし、この慣習は廃れており、Debian セ" +"キュリティ勧告がリリースされた際、セキュリティ勧告へのアップロードに使われた" +"ものが自動的に適切な <filename>proposed-updates</filename> アーカイブにコピー" +"されます。セキュリティ情報の取り扱い方の詳細については <xref linkend=\"bug-" +"security\"/> を参照してください。セキュリティチームがその問題は " +"<literal>DSA</literal> を通じて修正するには軽微過ぎると思った場合であっても、" +"安定版のリリースマネージャらはそれに関わらず <literal>安定版 (stable)</" +"literal> への定期アップロードに修正を含めようとするでしょう。" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:343 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:354 msgid "" "Changing anything else in the package that isn't important is discouraged, " "because even trivial fixes can cause bugs later on." msgstr "" +"些細な修正でも後ほどバグを引き起こすことがあるので、重要でないものは何であろ" +"うと変更するのは推奨されません。" -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:347 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:358 msgid "" "Packages uploaded to <literal>stable</literal> need to be compiled on " "systems running <literal>stable</literal>, so that their dependencies are " @@ -483,177 +726,227 @@ msgid "" "literal>; for example, a package uploaded to <literal>stable</literal> that " "depends on a library package that only exists in <literal>unstable</literal> " "will be rejected. Making changes to dependencies of other packages (by " -"messing with <literal>Provides</literal> or <literal>shlibs</literal> " +"messing with <literal>Provides</literal> or <filename>shlibs</filename> " "files), possibly making those other packages uninstallable, is strongly " "discouraged." msgstr "" +"<literal>安定版 (stable)</literal> にアップロードされるパッケージは<literal>" +"安定版 (stable)</literal> を動作しているシステム上でコンパイルされていなけれ" +"ばならず、ライブラリ (やその他のパッケージ) への依存は<literal>安定版 " +"(stable)</literal> で入手可能なものに限られます。例えば、<literal>安定版 " +"(stable)</literal> にアップロードされたパッケージが<literal>不安定版 " +"(unstable)</literal> にのみ存在するライブラリパッケージに依存していると " +"reject されます。他のパッケージへの依存を (<literal>提供 (Provides)</" +"literal> や <filename>shlibs</filename> をいじることで) 変更するのは、他の" +"パッケージをインストールできないようにする可能性があるので認められません。" -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:357 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:368 msgid "" "Uploads to the <literal>oldstable</literal> distributions are possible as " -"long as it hasn't been archived. The same rules as for <literal>stable </" +"long as it hasn't been archived. The same rules as for <literal>stable</" "literal> apply." msgstr "" +"<literal>旧安定版 (oldstable)</literal> ディストリビューションへのアップロー" +"ドはアーカイブされてない限り可能です。<literal>安定版 (stable)</literal>と同" +"じルールが適用されます。" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:364 +#. type: Content of: <chapter><section><section><title> +#: pkgs.dbk:375 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:377 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:385 msgid "Uploading a package" msgstr "パッケージをアップロードする" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:376 +#. type: Content of: <chapter><section><section><title> +#: pkgs.dbk:387 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:389 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 "" +"パッケージをアップロードするには、ファイル (署名された changes ファイルと " +"dsc ファイル) を anonymous ftp で <literal>&ftp-upload-host;</literal> の " +"<ulink url=\"ftp://&ftp-upload-host;&upload-queue;\">&upload-queue;</ulink> " +"へアップロードする必要があります。そこでファイルを処理するためには、Debian " +"Developers keyring または Debian Maintainers keyring (<ulink url=\"&url-wiki-" +"dm;\"></ulink> 参照) にある鍵で署名しておく必要があります。" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:387 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:398 msgid "" "Please note that you should transfer the changes file last. Otherwise, your " "upload may be rejected because the archive maintenance software will parse " "the changes file and see that not all files have been uploaded." msgstr "" +"changes ファイルは最後に転送する必要があることに注意してください。そうしない" +"とアーカイブのメンテナンスを行っているソフトが changes ファイルをパースして全" +"てのファイルがアップロードされていないと判断して、アップロードは reject され" +"るかもしれません。" -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:392 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:403 msgid "" -"You may also find the Debian packages <xref linkend=\"dupload\"/> or <xref " -"linkend=\"dput\"/> useful when uploading packages. These handy programs " -"help automate the process of uploading packages into Debian." +"You may also find the Debian packages <link linkend=\"dupload\">dupload</" +"link> or <link linkend=\"dput\">dput</link> useful when uploading packages." +"These handy programs help automate the process of uploading packages into " +"Debian." msgstr "" +"パッケージのアップロードを行う際には <link linkend=\"dupload\">dupload</" +"link> や <link linkend=\"dput\">dput</link> が便利なことにも気づくことでしょ" +"う。これらの便利なプログラムは、パッケージを Debian にアップロードする作業を" +"自動化するのに役立ちます。" -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:397 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:408 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 <link linkend=\"dcut\">dcut</" +"link>." msgstr "" +"パッケージを削除するには <ulink url=\"ftp://&ftp-upload-host;&upload-queue;" +"README\"/> と <link linkend=\"dcut\">dcut</link> Debian パッケージを参照して" +"ください。" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:403 +#. type: Content of: <chapter><section><section><title> +#: pkgs.dbk:415 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:418 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" +"パッケージを直ちにアップロードするのが良い時もありますが、パッケージがアーカ" +"イブに入るのが数日後であるのが良いと思う時もあります。例えば、<link linkend=" +"\"nmu\">Non-Maintainer アップロード</link>の準備をする際は、メンテナに対して" +"猶予期間を数日間与えたいと思うでしょう。" -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:420 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:425 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 "" +"delayed ディレクトリにアップロードされると、パッケージは <ulink url=\"http://" +"ftp-master.debian.org/deferred.html\">the deferred uploads queue</ulink> に保" +"存されます。指定した待ち時間が終わると、パッケージは処理のため通常の " +"incoming ディレクトリに移動されます。この作業は <literal>&ftp-upload-host;</" +"literal> の <literal>DELAYED/[012345678]-day</literal> ディレクトリへのアップ" +"ロードを通じて自動的に処理されます。0-day は一日に複数回 <literal>&ftp-" +"upload-host;</literal> へアップロードするのに使われます。" -# 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 "" +"dput を使うと、パッケージを遅延キューに入れるのに <literal>--delayed " +"<replaceable>DELAY</replaceable></literal> パラメータを使えます。" # 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-" -"security </literal>, etc.) without prior authorization from the security " +"security</literal>, etc.) without prior authorization from the security " "team. If the package does not exactly meet the team's requirements, it will " "cause many problems and delays in dealing with the unwanted upload. For " -"details, please see section <xref linkend=\"bug-security\"/> ." +"details, please see <xref linkend=\"bug-security\"/>." msgstr "" +"セキュリティアップロードキュー (<literal>oldstable-security</literal>、" +"<literal>stable-security</literal> 等) には、セキュリティチームからの事前許可" +"無しにパッケージを<emphasis role=\"strong\">アップロードしないでください</" +"emphasis>。パッケージがチームの要求に完全に合致していない場合、望まれないアッ" +"プロードに対処するために多くの問題が引き起こされたり遅延が生じることになりま" +"す。詳細については <xref linkend=\"bug-security\"/> を参照してください。" # 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." -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." +"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 "" +"ヨーロッパにはもう一つのアップロードキューが <ulink url=\"ftp://&ftp-eu-" +"upload-host;&upload-queue;\"/> にあります。操作方法は <literal>&ftp-upload-" +"host;</literal> と同じですが、ヨーロッパ圏の開発者に対しては、より速いはずで" +"す。" -# 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 <link linkend=\"delayed-incoming" +"\">delayed uploads</link>." msgstr "" +"パッケージは ssh を使って <literal>&ssh-upload-host;</literal> へアップロード" +"することも可能です。ファイルは <literal>/srv/upload.debian.org/UploadQueue</" +"literal> に置く必要があります。このキューは<link linkend=\"delayed-incoming" +"\">遅延アップロード</link>をサポートしていません。" # 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 "" +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 " @@ -664,38 +957,60 @@ msgid "" "manually. When uploads are handled manually, the change to the archive may " "take up to a month to occur. Please be patient." msgstr "" +"Debian アーカイブメンテナはパッケージのアップロードに関して責任を持っていま" +"す。多くの部分は、アップロードはアーカイブ用のメンテナンスツール " +"<command>katie</command> によって日々自動的に行われています。特に、<literal>" +"不安定版 (unstable)</literal> に存在しているパッケージの更新は自動的に処理さ" +"れます。それ以外の場合、特に新規パッケージの場合は、アップロードされたパッ" +"ケージをディストリビューションに含めるのは手動で行われます。アップロードが手" +"動で処理される場合は、アーカイブへの変更は実施されるまでに一ヶ月ほどかかりま" +"す。お待ちください。" # 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 " "be closed by the upload. Please examine this notification carefully, " "checking if any bugs you meant to close didn't get triggered." 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 " "separate email notifying you of that. Read on below." 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 " @@ -704,9 +1019,15 @@ msgid "" "control over these fields. The values in the <filename>debian/control</" "filename> file are actually just hints." msgstr "" +"<filename>debian/control</filename> ファイルの <literal>セクション (Section)" +"</literal> フィールドと <literal>優先度 (Priority)</literal> フィールドは実際" +"にアーカイブ内でどこに配置されるか、あるいはプライオリティが何かという指定で" +"はありません。<filename>debian/control</filename> ファイル中の値は、実際のと" +"ころは単なるヒントです。" # 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 " @@ -717,62 +1038,101 @@ msgid "" "filename> file for your next upload, or else you may wish to make a change " "in the <literal>override file</literal>." msgstr "" +"アーカイブメンテナは、<literal>override ファイル</literal>内でパッケージにつ" +"いて定められたセクションと優先度を常に確認しています。<literal>override ファ" +"イル</literal>と <filename>debian/control</filename> で指定されたパッケージの" +"フィールドに不一致がある場合、パッケージがアーカイブにインストールされる際に" +"相違について記述されたメールを受け取ります。<filename>debian/control</" +"filename> ファイルを次回のアップロード時に修正することもできますし、" +"<literal>override ファイル</literal>に変更を加えるように依頼するのもよいで" +"しょう。" -# 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." -msgstr "" +"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 "" +"パッケージが現状で置かれているセクションを変更するには、まずパッケージの " +"<filename>debian/control</filename> ファイルが正しいことを確認する必要があり" +"ます。次に、<systemitem role=\"package\">ftp.debian.org</systemitem> に対し、" +"あなたのパッケージに対するセクションあるいは優先度について古いものから新しい" +"ものへ変更する依頼のバグ登録をします。<literal>override: PACKAGE1:section/" +"priority, [...], PACKAGEX:section/priority</literal> のようなサブジェクトを使" +"い、バグ報告の本文に変更に関する根拠を記述してください。" # 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> " "<manvolnum>1</manvolnum> </citerefentry> and <ulink url=\"&url-bts-devel;" "#maintincorrect\"></ulink>." msgstr "" +"<literal>override ファイル</literal> についての詳細は、<citerefentry> " +"<refentrytitle>dpkg-scanpackages</refentrytitle> <manvolnum>1</manvolnum> </" +"citerefentry> と <ulink url=\"&url-bts-devel;#maintincorrect\"></ulink> を参" +"照してください。" -# 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-" -"sections\"/> . If the section is main, it should be omitted. The list of " +"sections\"/>. If the section is main, it should be omitted. The list of " "allowable subsections can be found in <ulink url=\"&url-debian-policy;ch-" "archive.html#s-subsections\"></ulink>." msgstr "" +"<xref linkend=\"archive-sections\"/> で書かれているように、<literal>セクショ" +"ン (Section)</literal>フィールドにはセクション同様にサブセクションも記述する" +"のに注意ください。セクションが main の場合は、それは書かないようにしてくださ" +"い。利用可能なサブセクションは <ulink url=\"&url-debian-policy;ch-archive." +"html#s-subsections\"></ulink> で検索できます。" # 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 " +"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 " @@ -780,14 +1140,20 @@ msgid "" "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 " @@ -795,9 +1161,16 @@ msgid "" "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=" @@ -805,81 +1178,122 @@ msgid "" "\"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 "" +"定期的にオープンになっているバグについてのレポートを受け取るのも良いでしょ" +"う。あなたのパッケージでオープンになっているバグの全一覧を毎週受け取りたい場" +"合、以下のような cron ジョブを追加します:" -# 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." -"g., <email>123@&bugs-host;</email>). If you're writing a new mail and you " -"don't remember the submitter email address, you can use the <email>123-" -"submitter@&bugs-host;</email> email to contact the submitter <emphasis>and</" -"emphasis> to record your mail within the bug log (that means you don't need " -"to send a copy of the mail to <email>123@&bugs-host;</email>)." -msgstr "" +"g., <email><replaceable>123</replaceable>@&bugs-host;</email>). If you're " +"writing a new mail and you don't remember the submitter email address, you " +"can use the <email><replaceable>123</replaceable>-submitter@&bugs-host;</" +"email> email to contact the submitter <emphasis>and</emphasis> to record " +"your mail within the bug log (that means you don't need to send a copy of " +"the mail to <email><replaceable>123</replaceable>@&bugs-host;</email>)." +msgstr "" +"バグに対応する際は、バグについて行った議論がバグの元々の報告者とバグ自身 (例" +"えば <email><replaceable>123</replaceable>@&bugs-host;</email>) の両方に送ら" +"れているのを確認してください。新しくメールを書いていて元々の報告者のメールア" +"ドレスを思い出せない場合は、<email><replaceable>123</replaceable>-" +"submitter@&bugs-host;</email> というメールアドレスが報告者へ連絡するのと、" +"<emphasis>さらに</emphasis>バグのログへあなたがメールしたのを記録するのにも使" +"えます (これは <email><replaceable>123</replaceable>@&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 " -"<email>123-done@&bugs-host;</email>. If you're fixing a bug by changing and " -"uploading the package, you can automate bug closing as described in <xref " -"linkend=\"upload-bugfix\"/> ." +"<email><replaceable>123</replaceable>-done@&bugs-host;</email>. If you're " +"fixing a bug by changing and uploading the package, you can automate bug " +"closing as described in <xref linkend=\"upload-bugfix\"/>." msgstr "" +"既にバグに対処していた場合 (例えば修正済みの時)、説明のメッセージを " +"<email><replaceable>123</replaceable>-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 " @@ -890,23 +1304,37 @@ msgid "" "documentation</ulink>. This section contains some guidelines for managing " "your own bugs, based on the collective Debian developer experience." msgstr "" +"パッケージメンテナになると、他のパッケージにバグを見つけたり、自分のパッケー" +"ジに対して報告されたバグが実際には他のパッケージにあるバグであったりというこ" +"とが頻繁にあるでしょう。バグ追跡システムの機能は <ulink url=\"&url-bts-devel;" +"\">Debian 開発者向けの BTS ドキュメント</ulink> に記載されています。バグ報告" +"の再指定 (reassign) やマージ (merge)、そしてタグ付けなどの作業は <ulink url=" +"\"&url-bts-control;\">BTS 制御サーバのドキュメント</ulink> に記述されていま" +"す。この章では、Debian 開発者から集められた経験を元にしたバグの扱い方のガイド" +"ラインを含んでいます。" # 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 " "details. However, handling the bugs in your own packages is even more " "important." msgstr "" +"他のパッケージで見つけた問題についてバグを登録するのは、メンテナとしての責務" +"の一つです。詳細については <xref linkend=\"submit-bug\"/> を参照してくださ" +"い。しかし、自分のパッケージのバグを管理するのはさらに重要です。" # 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 "" +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 " @@ -917,9 +1345,18 @@ msgid "" "shouldn't detect its misuse in order to give an informative error message. " "This is an issue that may need to be brought up with the upstream author." msgstr "" +"報告が実際にバグに関連するものか否かを決めてください。ユーザはドキュメントを" +"読んでいないため、誤ったプログラムの使い方をしているだけのことが時々ありま" +"す。このように判断した場合は、ユーザに問題を修正するのに十分な情報を与えて " +"(良いドキュメントへのポインタを教えるなどして) バグを閉じます。同じ報告が何度" +"も繰り返し来る場合には、ドキュメントが十分なものかどうか、あるいは有益なエ" +"ラーメッセージを与えるよう、誤った使い方を検知していないのでは、と自身に問い" +"直してください。これは開発元の作者に伝える必要がある問題かもしれません。" +# FIXME-trans: "If you don't find any," - any what? # 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 " @@ -932,24 +1369,44 @@ msgid "" "so, please read the <ulink url=\"&url-tech-ctte;\">recommended procedure</" "ulink>." msgstr "" +"バグを閉じるという貴方の判断にバグ報告者らが同意しない場合には、それをどう取" +"り扱うかについての同意が見つかるまで、彼らは再度オープンな状態 (reopen) にす" +"るでしょう。そのバグについてもう議論することが無いという場合は、バグは存在す" +"るが修正することはないと知らせるため、バグに対して <literal>wontfix</" +"literal> タグを付けることになります。この決定が受け入れがたい時には、あなた " +"(あるいは報告者) はバグを <systemitem role=\"package\">tech-ctte</" +"systemitem> に再指定 (reassign) して技術委員会 (technical committee) の判断を" +"仰いでください (パッケージへ報告されたものをそのままにしておきたい場合は、" +"BTS の clone コマンドを使ってください)。これを行う前には<ulink url=\"&url-" +"tech-ctte;\">推奨手順</ulink>を読んでおいてください。" -# 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 " "reassigned to, you should ask for help on <link linkend=\"irc-channels" "\">IRC</link> or on &email-debian-devel;. Please inform the maintainer(s) " "of the package you reassign the bug to, for example by Cc:ing the message " -"that does the reassign to <email>packagename@packages.debian.org</email> and " -"explaining your reasons in that mail. Please note that a simple reassignment " -"is <emphasis>not</emphasis> e-mailed to the maintainers of the package being " -"reassigned to, so they won't know about it until they look at a bug overview " -"for their packages." -msgstr "" +"that does the reassign to <email><replaceable>packagename</" +"replaceable>@packages.debian.org</email> and explaining your reasons in that " +"mail. Please note that a simple reassignment is <emphasis>not</emphasis> e-" +"mailed to the maintainers of the package being reassigned to, so they won't " +"know about it until they look at a bug overview for their packages." +msgstr "" +"バグが実際にあるが、他のパッケージによって引き起こされている場合は、バグを正" +"しいパッケージに再指定 (reassign) します。どのパッケージに再指定するべきかが" +"分からない場合は、<link linkend=\"irc-channels\">IRC</link> か &email-debian-" +"devel; で聞いてください。再指定するパッケージのメンテナに通知をしてください。" +"例えば <email><replaceable>packagename</replaceable>@packages.debian.org</" +"email> 宛にメッセージを Cc: してメール中に理由を説明するなどします。単に再指" +"定しただけでは再指定された先のメンテナにはメールは<emphasis>送信されません</" +"emphasis>ので、彼らがパッケージのバグ一覧を見るまでそれを知ることはありませ" +"ん。" # 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 " @@ -958,9 +1415,16 @@ msgid "" "should block \"your\" bug with the reassigned, cloned bug to document the " "relationship." msgstr "" +"バグがあなたのパッケージの動作に影響する場合は、バグを複製し (clone)、複製し" +"たバグをその挙動を実際に起こしているパッケージに再指定することを検討してくだ" +"さい。さもなければ、あなたのパッケージのバグ一覧にバグが見つからないので、多" +"分ユーザに同じバグを何度も繰り返し報告される羽目になる可能性があります。あな" +"たは、再指定 (reassign) によって「自分の」バグということを防ぎ、バグの複製 " +"(clone) によって関係があることを記載しておく必要があります。" # 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 " @@ -968,9 +1432,14 @@ msgid "" "even be dropped to wishlist severity when the requested change is just " "cosmetic." msgstr "" +"時々、重要度の定義に合うようにバグの重要度を調整する必要もあります。これは、" +"人々はバグ修正を確実に早くしてもらうために重要度を極端に上げようとするからで" +"す。要望された変更点が単に体裁的なものな時には、バグは要望 (wishlist) に格下" +"げされるでしょう。" # 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 " @@ -980,9 +1449,16 @@ msgid "" "submitter.) For more details on the technicalities of the merge command and " "its relative, the unmerge command, see the BTS control server documentation." msgstr "" +"バグが確かにあるが既に他の誰かによって同じ問題が報告されている場合は、2 つの" +"関連したバグを BTS の merge コマンドを使って 1 つにマージします。このようにす" +"ると、バグが修正された時に全ての投稿者に通知がいきます (ですが、そのバグ報告" +"の投稿者へのメールは報告の他の投稿者には自動的には通知されないことに注意して" +"ください)。merge コマンドや類似の unmerge コマンドの技術詳細については、BTS " +"制御サーバドキュメントを参照してください。" # 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 " @@ -992,9 +1468,16 @@ msgid "" "on how to reproduce it. After a few months, if this information has not " "been sent by someone, the bug may be closed." msgstr "" +"バグ報告者は情報を書き漏らしている場合、必要な情報を尋ねる必要があります。そ" +"の様なバグに印をつけるには <literal>moreinfo</literal> タグを使います。さら" +"に、そのバグを再現できない場合には、<literal>unreproducible</literal> タグを" +"付けます。誰もそのバグを再現できない場合、どうやって再現するのか、さらに情報" +"を何ヶ月経っても、この情報が誰からも送られてこない場合はバグは閉じても構いま" +"せん。" # 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 " @@ -1007,33 +1490,53 @@ msgid "" "sure to send the patch to the BTS and to tag the bug as <literal>patch</" "literal>." msgstr "" - -# type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:732 +"バグがパッケージに起因する場合、さっさと直します。自分では直せない場合は、バ" +"グに <literal>help</literal> タグを付けます。&email-debian-devel; や &email-" +"debian-qa; で助けを求めることも出来ます。開発元 (upstream) の問題であれば、作" +"者に転送する必要があります。バグを転送するだけでは十分ではありません。リリー" +"スごとにバグが修正されているかどうかを確認しなければいけません。もし修正され" +"ていれば、それを閉じ、そうでなければ作者に確認を取る必要があります。必要な技" +"能を持っていてバグを修正するパッチが用意できる場合は、同時に作者に送りましょ" +"う。パッチを BTS に送付してバグに <literal>patch</literal> タグを付けるのを忘" +"れないでください。" + +#. type: Content of: <chapter><section><section><orderedlist><listitem><para> +#: pkgs.dbk:742 msgid "" "If you have fixed a bug in your local copy, or if a fix has been committed " -"to the CVS repository, you may tag the bug as <literal>pending</literal> to " +"to the VCS repository, you may tag the bug as <literal>pending</literal> to " "let people know that the bug is corrected and that it will be closed with " "the next upload (add the <literal>closes:</literal> in the " "<filename>changelog</filename>). This is particularly useful if you are " "several developers working on the same package." msgstr "" +"ローカル環境でバグを修正した、あるいは VCS リポジトリに修正をコミットした場合" +"には、バグに <literal>pending</literal> タグを付けてバグが修正されたことと次" +"のアップロードでバグが閉じられるであろうことを回りに知らせます " +"(<filename>changelog</filename> に <literal>closes:</literal> を追加します)。" +"これは複数の開発者が同一のパッケージで作業している際に特に役立ちます。" # 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 " "automatically, read <xref linkend=\"upload-bugfix\"/>." msgstr "" +"一旦修正されたパッケージがアーカイブから入手可能になったら、バグはどのバー" +"ジョンで修正されたかを指定して閉じられる必要があります。これは自動的に行われ" +"ます。<xref linkend=\"upload-bugfix\"/> を読んでください。" # 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 " @@ -1042,21 +1545,32 @@ msgid "" "package has been installed into the archive, you can and should close the " "bug in the BTS. Also, the bug should be closed with the correct version." msgstr "" +"バグや問題があなたのパッケージで修正されたとしたら、そのバグを閉じるのはパッ" +"ケージメンテナとしての責任になります。しかし、バグを修正したパッケージが " +"Debian アーカイブに受け入れられるまではバグを閉じてはいけません。従って、一旦" +"更新したパッケージがアーカイブにインストールされたという通知を受け取った場合" +"は、BTS でバグを閉じることができますし、そうしなければいけません。もちろん、" +"バグは正しいバージョンで閉じなくてはいけません。" # 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</" "filename> file, following a certain syntax, and the archive maintenance " "software will close the bugs for you. For example:" msgstr "" +"ですが、アップロード後に手動でバグをクローズしなくても済む方法があります — " +"<filename>debian/changelog</filename> に以下の特定の書き方にて修正したバグを" +"列挙すれば、それだけで後はアーカイブのメンテナンスソフトがバグをクローズして" +"くれます。例:" # 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" @@ -1069,84 +1583,120 @@ msgstr "" " * 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 "" +"技術的に言うと、どの様にしてバグを閉じる changelog が判別されているかを以下" +"の Perl の正規表現にて記述しています:" # 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 " "the text of the <filename>changelog</filename>. Unless specified different " -"by the <replaceable>-v</replaceable>-switch to <command>dpkg-buildpackage</" -"command>, only the bugs closed in the most recent changelog entry are closed " +"by the <literal>-v</literal>-switch to <command>dpkg-buildpackage</command>, " +"only the bugs closed in the most recent changelog entry are closed " "(basically, exactly the bugs mentioned in the changelog-part in the " "<filename>.changes</filename> file are closed)." msgstr "" +"<literal>closes: #<replaceable>XXX</replaceable></literal> という書き方が推奨" +"されています。これは、最も分かり易いエントリで、<filename>changelog</" +"filename> の本文に挿入するのがもっとも簡単だからです。<command>dpkg-" +"buildpackage</command> に <literal>-v</literal> スイッチを指定して別バージョ" +"ンを指定しない限り、最も新しい changelog のエントリにあるバグだけが閉じられま" +"す (基本的には、です。正確には <filename>.changes</filename> ファイルの " +"changelog-part で明示されたバグが閉じられます)。" -# 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 " +"Historically, uploads identified as <link linkend=\"nmu\">non-maintainer " "upload (NMU)</link> were tagged <literal>fixed</literal> instead of being " "closed, but that practice was ceased with the advent of version-tracking. " "The same applied to the tag <literal>fixed-in-experimental</literal>." msgstr "" +"歴史的に、<link linkend=\"nmu\">non-maintainer upload (NMU)</link> と判別され" +"るアップロードは closed ではなく <literal>fixed</literal> とタグがされてきま" +"したが、この習慣はバージョントラッキングの進化によって廃れています。同じこと" +"が <literal>fixed-in-experimental</literal> タグにも言えます。" -# 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 " "wrongly closed bugs, send a <literal>reopen <replaceable>XXX</replaceable></" "literal> command to the bug tracking system's control address, &email-bts-" "control;. To close any remaining bugs that were fixed by your upload, email " -"the <filename>.changes</filename> file to <email>XXX-done@&bugs-host;</" -"email>, where <replaceable>XXX</replaceable> is the bug number, and put " -"Version: YYY and an empty line as the first two lines of the body of the " -"email, where <replaceable>YYY</replaceable> is the first version where the " -"bug has been fixed." -msgstr "" - -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:809 +"the <filename>.changes</filename> file to <email><replaceable>XXX</" +"replaceable>-done@&bugs-host;</email>, where <replaceable>XXX</replaceable> " +"is the bug number, and put Version: <replaceable>YYY</replaceable> and an " +"empty line as the first two lines of the body of the email, where " +"<replaceable>YYY</replaceable> is the first version where the bug has been " +"fixed." +msgstr "" +"もしバグ場号を間違って入力したり、changelog のエントリにバグを入れ忘れた場" +"合、そのミスが起こすであろうダメージを防ぐのを躊躇わないでください。誤って閉" +"じたバグを再度オープンにするには、バグトラッキングシステムのコントロールアド" +"レスである &email-bts-control; に <literal>reopen <replaceable>XXX</" +"replaceable></literal> コマンドを投げます。アップロードで修正されたがまだ残っ" +"ているバグを閉じるには <filename>.changes</filename> ファイルを " +"<email><replaceable>XXX</replaceable>-done@&bugs-host;</email> にメールしま" +"す。<replaceable>XXX</replaceable> はバグ番号で、メールの本文の最初の 2 行に " +"Version: <replaceable>YYY</replaceable> と空白行を入れます。" +"<replaceable>YYY</replaceable> はバグが修正された最初のバージョンです。" + +#. 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 " "to do with an upload you made, do it by emailing an explanation to " -"<email>XXX-done@&bugs-host;</email>. Do <emphasis role=\"strong\">not</" -"emphasis> close bugs in the changelog entry of a version if the changes in " -"that version of the package don't have any bearing on the bug." -msgstr "" +"<email><replaceable>XXX</replaceable>-done@&bugs-host;</email>. Do " +"<emphasis role=\"strong\">not</emphasis> close bugs in the changelog entry " +"of a version if the changes in that version of the package don't have any " +"bearing on the bug." +msgstr "" +"上に書いたような changelog を使ったバグの閉じ方は必須ではない、ということは念" +"頭に置いておいてください。行ったアップロードとは無関係に単にバグを閉じたい、" +"という場合は、説明をメールに書いて <email><replaceable>XXX</replaceable>-" +"done@&bugs-host;</email> に送ってバグを閉じてください。そのバージョンのパッ" +"ケージでの変更がバグに何も関係ない場合は、そのバージョンの changelog エントリ" +"ではバグを<emphasis role=\"strong\">閉じないで</emphasis>ください。" # 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\"/> ." +"linkend=\"bpp-debian-changelog\"/>." msgstr "" +"どのように changelog のエントリを書くのか、一般的な情報については <xref " +"linkend=\"bpp-debian-changelog\"/> を参照してください。" # 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, " @@ -1154,61 +1704,137 @@ msgid "" "security problems or fixing them themselves, sending security advisories, " "and maintaining <literal>security.debian.org</literal>." msgstr "" +"機密性が高いその性質上、セキュリティ関連のバグは注意深く取り扱わねばなりませ" +"ん。この作業をコーディネイトし、未処理のセキュリティ問題を追い続け、セキュリ" +"ティ問題についてメンテナを手助けしたり修正自体を行い、セキュリティ勧告を出" +"し、<literal>security.debian.org</literal> を維持するために Debian セキュリ" +"ティチームが存在します。" -# 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 "" +"Debian パッケージ中のセキュリティ関連のバグに気づいたら、あなたがメンテナであ" +"るかどうかに関わらず、問題に関する正確な情報を集めて、まずは可能な限り早く " +"&email-security-team; 宛でセキュリティチームに連絡を取ってください。チームに" +"問い合わせること無く <literal>安定版 (stable)</literal> 向けのパッケージを" +"<emphasis role=\"strong\">アップロードしないでください</emphasis>。例えば、役" +"に立つ情報は以下を含んでいます:" # 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 " "<literal>testing</literal> and <literal>unstable</literal>." msgstr "" +"バグによって、どのバージョンが影響を受けると分かっているか。サポートされてい" +"る Debian のリリース、ならびに <literal>テスト版 (testing)</literal> 及び " +"<literal>不安定版 (unstable)</literal> にある各バージョンをチェックしてくださ" +"い。" # 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 "" +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=" -"\"bug-security-building\"/> first)" +"Any fixed packages that you have prepared yourself (send only the <filename>." +"diff.gz</filename> and <filename>.dsc</filename> files and read <xref " +"linkend=\"bug-security-building\"/> first)" msgstr "" +"自身で準備した修正パッケージ (まずは <xref linkend=\"bug-security-building\"/" +"> を読んで、<filename>.diff.gz</filename> と <filename>.dsc</filename> ファイ" +"ルだけを送ってください)" # 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 "" +"advisories\"/>)" +msgstr "" +"勧告に必要になる情報 (<xref linkend=\"bug-security-advisories\"/> 参照)" + +#. 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 "" +"セキュリティチームは集約的なデータベース、<ulink url=\"http://security-" +"tracker.debian.org/\">Debian セキュリティ追跡システム</ulink>をメンテナンスし" +"ています。これはセキュリティ問題として知られている全ての公開情報を含んでいま" +"す: どのパッケージ／バージョンが影響を受ける／修正されているか、つまりは安定" +"版、テスト版、不安定版が脆弱かどうか、という情報です。まだ機密扱いの情報は追" +"跡システムには追加されません。" + +#. 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 "" +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 " @@ -1217,53 +1843,74 @@ msgid "" "problem and corresponding fix, and whether it is already a matter of public " "knowledge." msgstr "" +"Debian 内での他の多くの活動とは違い、セキュリティ問題に関する情報については、" +"暫くの間秘密にしておく必要がしばしばあります。これによって、ソフトウェアの" +"ディストリビュータがユーザが危険にさらされるのを最小限にするため、公開時期を" +"合わせることができます。今回がそうであるかは、問題と対応する修正の性質や、既" +"に既知のものとなっているかどうかによります。" # 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 "" +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 "" +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 "" +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 "" +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 " "public information. In that case there are a few possible options for " "dealing with the problem:" 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 " "with the various organizations and individuals and can take care of that." 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 " @@ -1271,32 +1918,60 @@ msgid "" "release of Debian. When sending confidential information to the security " "team, be sure to mention this fact." msgstr "" +"どのような場合でも、問題を報告した人がこれを公開しないように求めているのであ" +"れば、明白な例外として Debian の安定版リリースに対する修正を作成してもらうた" +"めにセキュリティチームへ連絡すること以外、この様な要求は尊重されるべきです。" +"機密情報をセキュリティチームに送る場合は、この点を明示しておくのを忘れないで" +"ください。" # 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 " +"<literal>unstable</literal> (or anywhere else, such as a public VCS " "repository). It is not sufficient to obfuscate the details of the change, " "as the code itself is public, and can (and will) be examined by the general " "public." msgstr "" +"機密を要する場合は、修正を<literal>不安定版 (unstable)</literal> (や公開 VCS " +"リポジトリなどその他どこへも) へ修正をアップロードしないよう、注意してくださ" +"い。コードその物が公開されている場合、変更の詳細を難読化するだけでは十分では" +"なく、皆によって解析され得る (そしてされる) でしょう。" # 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 "" +"機密であることを要求されたにも関わらず、情報を公開するのには 2 つの理由があり" +"ます: 問題が一定期間既知の状態になっている、あるいは問題や攻撃コードが公開さ" +"れた場合です。" + +#. 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#contact\">Security Team FAQ</ulink> for details." +msgstr "" +"セキュリティチームは、機密事項に関して通信を暗号化できる PGP 鍵を持っていま" +"す。詳細については、<ulink url=\"http://www.debian.org/security/faq#contact" +"\">セキュリティチーム FAQ</ulink> を参照してください。" # 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 +# FIXME: how about oldstable? +#. 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 " @@ -1308,82 +1983,113 @@ msgid "" "information for them, or write part of the text. Information that should be " "in an advisory includes:" msgstr "" +"セキュリティ勧告は現在のところ、リリースされた安定版ディストリビューションに" +"ついてのみ、取り扱われます。<literal>テスト版 (testing)</literal> や " +"<literal>不安定版 (unstable)</literal> についてでは<emphasis>ありません</" +"emphasis>。リリースされると、セキュリティ勧告は email-debian-security-" +"announce; メーリングリストに送られ、<ulink url=\"&url-debian-security-" +"advisories;\">セキュリティのウェブページ</ulink>に掲載されます。セキュリティ" +"勧告はセキュリティチームによって記述、掲載されます。しかし、メンテナが情報を" +"提供できたり、文章の一部を書けるのであれば、彼らは当然そんなことは気にしませ" +"ん。勧告にあるべき情報は以下を含んでいます:" # 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 "" +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 "" +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 "" +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 "" +"どこで更新されたパッケージを得るかという情報 (通常は Debian のセキュリティ" +"アーカイブからです)" # 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 " "the vulnerability" msgstr "" +"開発元のアドバイザリへの参照、<ulink url=\"http://cve.mitre.org\">CVE</" +"ulink> 番号、脆弱性の相互参照について役立つその他の情報" # 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 "" +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 " "Debian release." msgstr "" +"あなたがセキュリティチームに対し、彼らの職務に関して手助けできる方法の一つ" +"は、安定版 Debian リリース用のセキュリティ勧告に適した修正版パッケージを提供" +"することです。" # 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 " @@ -1392,9 +2098,16 @@ msgid "" "might break someone's system. This is especially true of libraries: make " "sure you never change the API or ABI, no matter how small the change." msgstr "" +"安定版について更新が作成される際、システムの挙動の変化や新しいバグの導入を避" +"けるように注意が必要です。これを行うため、バグを修正するための変更は可能な限" +"り少なくします。ユーザや管理者は一旦リリースされたものの厳密な挙動を当てにし" +"ている、どのような変更でも誰かのシステムを壊しかねません。これは特にライブラ" +"リについて当てはまります: API や ABI を決して変更していないことを確認してくだ" +"さい。変更がどれほど小さいものでも関係ありません。" # 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 " @@ -1402,9 +2115,15 @@ msgid "" "willing to help if needed. If not, the Debian security team may be able to " "help." msgstr "" +"これは、開発元の新しいリリースバージョン (new upstream version) への移行が良" +"い解決策ではないことを意味しています。代わりに、関連する変更を現在の Debian " +"安定版リリースに存在しているバージョンへバックポートするべきです。通常、開発" +"元のメンテナは助けが必要であれば手伝おうとしてくれます。そうでない場合は、" +"Debian セキュリティチームが手助けすることができます。" # 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 " @@ -1412,9 +2131,15 @@ msgid "" "this is only done in extreme situations, and you must always coordinate that " "with the security team beforehand." msgstr "" +"いくつかのケースでは、例えば大量のソースコードの変更や書き直しが必要など、セ" +"キュリティ修正をバックポートできないことがあります。この様な場合、新しいバー" +"ジョン (new upstream version) へ移行する必要があるかもしれません。しかし、こ" +"れは極端な状況の場合にのみ行われるものであり、実行する前に必ずセキュリティ" +"チームと調整をしなければなりません。" # 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 " @@ -1422,9 +2147,16 @@ msgid "" "actions as well, as sometimes a security fix can break seemingly unrelated " "features in subtle ways." msgstr "" +"これに関してはもう一つ重要な指針があります: 必ず変更についてテストをしてくだ" +"さい。攻撃用コード (exploit) が入手可能な場合には、それを試してみて、パッチを" +"当てていないパッケージで成功するか、修正したパッケージでは失敗することかどう" +"かを確かめてみてください。他の確認として、セキュリティ修正は時折表面上はそれ" +"と関係が無いような機能を壊すことがあるので、通常の動作も同様にテストしてくだ" +"さい。" # 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 " @@ -1435,241 +2167,350 @@ msgid "" "package which would otherwise be rejected from the stable release, so please " "do not attempt to do this." msgstr "" +"脆弱性の修正に直接関係しない変更をパッケージへ<emphasis role=\"strong\">加え" +"ない</emphasis>ようにしてください。この様な変更は元に戻さなくてはならなくなる" +"だけで、時間を無駄にします。他に直したいバグがパッケージにある場合は、セキュ" +"リティ勧告が発行された後、通常通りに proposed-update にアップロードを行ってく" +"ださい。セキュリティ更新の仕組みは、それ以外の方法では安定版リリースから " +"reject されるであろう変更をあなたのパッケージに加える方法ではありませんので、" +"この様な事はしないでください。" -# 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 " "<systemitem role=\"package\">patchutils</systemitem> package and " "<command>debdiff</command> from <systemitem role=\"package\">devscripts</" -"systemitem> are useful tools for this, see <xref linkend=\"debdiff\"/> )." +"systemitem> are useful tools for this, see <xref linkend=\"debdiff\"/>)." msgstr "" +"変更点を可能な限り見直してください。以前のバージョンとの変更点を繰り返し確認" +"してください (これには <systemitem role=\"package\">patchutils</systemitem> " +"パッケージの <command>interdiff</command> や <systemitem role=\"package" +"\">devscripts</systemitem> の <command>debdiff</command> が役立ちます。<xref " +"linkend=\"debdiff\"/> を参照してください)。" # 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 -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>!" -msgstr "" - -# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1089 -#, fuzzy -msgid "The upload should have urgency=high." -msgstr "アップロードは urgency=high で行う必要があります。" +msgstr "以下の項目を必ず確認してください" -# 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:1114 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." +"<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 <literal>testing</literal> " +"this is <literal>testing-security</literal>, and for the previous stable " +"release, this is <literal>oldstable-security</literal>. Do not target " +"<replaceable>distribution</replaceable><literal>-proposed-updates</literal> " +"or <literal>stable</literal>!" msgstr "" +"<filename>debian/changelog</filename> で <emphasis role=\"strong\">正しいディ" +"ストリビューションを対象にする</emphasis>。<literal>安定版 (stable)</" +"literal> の場合、これは <literal>stable-security</literal> になり、<literal>" +"テスト版 (testing)</literal> の場合は <literal>testing-security</literal> " +"に、そして以前の安定版リリースへの場合は <literal>oldstable-security</" +"literal> となります。<replaceable>distribution</replaceable><literal>-" +"proposed-updates</literal> や <literal>stable</literal> を対象にしないでくだ" +"さい!" # 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:1125 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." +"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:1119 +#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:1130 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." -msgstr "" - -# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1128 +"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 "" +"説明が十分にされている、意味がある changelog エントリを書くこと。他の人は、こ" +"れらを元に特定のバグが修正されているのかを見つけ出します。登録されている " +"<emphasis role=\"strong\">Debian バグ</emphasis> に対して <literal>closes:</" +"literal> 行を追加すること。外部のリファレンス、できれば <emphasis role=" +"\"strong\">CVE 識別番号</emphasis> を常に含めること、そうすれば相互参照が可能" +"になります。しかし、CVE 識別番号がまだ付与されていない場合には、それを待たず" +"に作業を進めてください。識別番号は後ほど付与することができます。" + +# FIXME: etch1 -> <stable code> +# convention +#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:1141 +msgid "" +"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+lenny1</literal>, of course increasing 1 for any " +"subsequent uploads." +msgstr "" +"<emphasis role=\"strong\">バージョン番号</emphasis>が正しいことを確認する。現" +"在のパッケージより大きく、しかし以降のディストリビューションよりパッケージ" +"バージョンが小さい必要があります。分からない場合は <literal>dpkg --compare-" +"versions</literal> でテストしてください。以前のアップロードで既に使っている" +"バージョン番号を再利用しないように注意してください。そうしないと番号が " +"binNMU と衝突します。<literal>+</literal><replaceable>codename</" +"replaceable><literal>1</literal> を追加するのが通例です。例えば " +"<literal>1:2.4.3-4+lenny1</literal> とします。もちろん 1 はアップロードするご" +"とに増やします。" + +# FIXME: remove " " +# FIXME: how about debuild -sa ? +#. 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>)." -msgstr "" - -# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1138 -msgid "" -"Be sure to use the exact same <filename>*.orig.tar.gz</filename> as used in " -"the normal archive, otherwise it is not possible to move the security fix " -"into the main archives later." -msgstr "" - -# type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1145 -msgid "" -"Build the package on a clean system which only has packages installed from " -"the distribution you are building for. If you do not have such a system " -"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 "" +"</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 "" +"これまでに (以前のセキュリティ更新によって) <literal>security.debian.org</" +"literal> へ開発元のソースコードをアップロードしていなければ、<emphasis role=" +"\"strong\">開発元のソースコードを全て含めて</emphasis>アップロードするパッ" +"ケージをビルドする (<literal>dpkg-buildpackage -sa</literal>)。以前、同じ開発" +"元のバージョンで <literal>security.debian.org</literal> にアップロードしたこ" +"とがある場合は、開発元のソースコード無しでアップロードしても構いません " +"(<literal>dpkg-buildpackage -sd</literal>)。" + +#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:1164 +msgid "" +"Be sure to use the <emphasis role=\"strong\">exact same <filename>*.orig.tar." +"{gz,bz2,lzma}</filename></emphasis> as used in the normal archive, otherwise " +"it is not possible to move the security fix into the main archives later." +msgstr "" +"通常のアーカイブで使われているのと<emphasis role=\"strong\">全く同じ " +"<filename>*.orig.tar.{gz,bz2,lzma}</filename></emphasis>を必ず使うようにして" +"ください。さもなくば、後ほどセキュリティ習性を main アーカイブに移動すること" +"ができません。" + +#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:1172 +msgid "" +"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 "" +"ビルドを行っているディストリビューションからインストールしたパッケージだけが" +"含まれている<emphasis role=\"strong\">クリーンなシステム上で</emphasis>パッ" +"ケージをビルドしてください。その様なシステムを自分で持っていない場合は、" +"debian.org マシン (<xref linkend=\"server-machines\"/> を参照してください) を" +"使うこともできますし、chroot を設定することもできます (<xref linkend=" +"\"pbuilder\"/> と <xref linkend=\"debootstrap\"/> を参照してください)。" # 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 "" +msgstr "修正したパッケージをアップロードする" -# type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1158 +# type: Content of: <chapter><section><section><para> +#. 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-" -"security </literal>, etc.) without prior authorization from the security " +"security</literal>, etc.) without prior authorization from the security " "team. If the package does not exactly meet the team's requirements, it will " "cause many problems and delays in dealing with the unwanted upload." msgstr "" - -# type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1165 -msgid "" -"Do <emphasis role=\"strong\">NOT</emphasis> upload your fix to <literal> " -"proposed-updates</literal> without coordinating with the security team. " -"Packages from <literal>security.debian.org</literal> will be copied into the " -"<literal>proposed-updates</literal> directory automatically. If a package " -"with the same or a higher version number is already installed into the " -"archive, the security update will be rejected by the archive system. That " -"way, the stable distribution will end up without a security update for this " -"package instead." -msgstr "" - -# type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1175 +"セキュリティアップロードキュー (<literal>oldstable-security</literal>、" +"<literal>stable-security </literal> 等) には、セキュリティチームからの事前許" +"可無しにパッケージを<emphasis role=\"strong\">アップロードしないでください</" +"emphasis>。パッケージがチームの要求に完全に合致していない場合、望まれないアッ" +"プロードに対処するために多くの問題が引き起こされたり遅延が生じることになりま" +"す。詳細については <xref linkend=\"bug-security\"/> を参照してください。" + +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:1192 +msgid "" +"Do <emphasis role=\"strong\">NOT</emphasis> upload your fix to " +"<literal>proposed-updates</literal> without coordinating with the security " +"team. Packages from <literal>security.debian.org</literal> will be copied " +"into the <literal>proposed-updates</literal> directory automatically. If a " +"package with the same or a higher version number is already installed into " +"the archive, the security update will be rejected by the archive system. " +"That way, the stable distribution will end up without a security update for " +"this package instead." +msgstr "" +"セキュリティチームと調整する事無しに <literal>proposed-updates</literal> へ修" +"正したものをアップロード<emphasis role=\"strong\">しない</emphasis>ようにして" +"ください。<literal>security.debian.org</literal> からパッケージは " +"<literal>proposed-updates</literal> ディレクトリに自動的にコピーされます。" +"アーカイブに同じ、あるいはより高いバージョン番号のものが既にインストールされ" +"ている場合は、セキュリティアップデートはアーカイブシステムに reject されま" +"す。そうすると、安定版ディストリビューションはこのパッケージに対するセキュリ" +"ティ更新無しで終了してしまうでしょう。" + +#. 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 " "the archives. For security uploads, the place to upload to is " -"<literal>ftp://security-master.debian.org/pub/SecurityUploadQueue/</" -"literal> ." +"<literal>ftp://security-master.debian.org/pub/SecurityUploadQueue/</literal>." msgstr "" +"一旦、新しいパッケージを作成してテストし、セキュリティチームによって許可を受" +"けたら、アーカイブへインストールできるようにするためにアップロードをする必要" +"があります。セキュリティに関するアップロードの場合、アップロード先は " +"<literal>ftp://security-master.debian.org/pub/SecurityUploadQueue/</literal> " +"になります。" -# 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 " "security problems that cannot be disclosed yet." 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 " "<replaceable>distribution</replaceable><literal>-proposed-updates</literal> " "on <literal>&ftp-master-host;</literal>." msgstr "" +"セキュリティチームのメンバーがパッケージを許可した場合は、proposed パッケージ" +"に対する <literal>&ftp-master-host;</literal> 上の適切な " +"<replaceable>distribution</replaceable><literal>-proposed-updates</literal> " +"と同様に <literal>security.debian.org</literal> 上にインストールされます。" # 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 " "chapter gives guidelines on what to do in these cases." msgstr "" +"アーカイブの変更作業のいくつかは、Debian のアップロードプロセスでは自動的なも" +"のにはなっていません。これらの手続きはメンテナによる手動での作業である必要が" +"あります。この章では、この様な場合に何をするかのガイドラインを提供します。" # 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 "" +"パッケージがどのセクションに属するかのガイドラインは <ulink url=\"&url-" +"debian-policy;\">Debian ポリシーマニュアル</ulink>を参照してください。" -# 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 "" +"時折、パッケージは属しているセクションが変わることがあります。例えば「non-" +"free」セクションのパッケージが新しいバージョンで GPL になった場合、パッケージ" +"は「main」か「contrib」に移動する必要があります。<placeholder type=\"footnote" +"\" id=\"0\"/>" -# 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 " -"uploading a new upstream version), or it will not appear in the new section " -"together with the rest of the package. If your new section is valid, it " -"will be moved automatically. If it does not, then contact the ftpmasters in " -"order to understand what happened." -msgstr "" - -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1231 +"<filename>.orig.tar.{gz,bz2,lzma}</filename> in your upload (even if you are " +"not uploading a new upstream version), or it will not appear in the new " +"section together with the rest of the package. If your new section is " +"valid, it will be moved automatically. If it does not, then contact the " +"ftpmasters in order to understand what happened." +msgstr "" +"パッケージのどれかがセクションを変更する必要がある場合、希望するセクションに" +"パッケージを配置するためパッケージの control 情報を変更してから再アップロード" +"します (詳細については <ulink url=\"&url-debian-policy;\">Debian ポリシーマ" +"ニュアル</ulink>を参照してください)。必ず <filename>.orig.tar.{gz,bz2,lzma}</" +"filename> を (開発元のバージョンが新しいものになったのではなくても) アップ" +"ロードに含める必要があります。新しいセクションが正しい場合は、自動的に移動さ" +"れます。移動されない場合には、何が起こったのかを理解するために ftpmaster に連" +"絡を取ります。" + +#. 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 " "slightly different. Correct the subsection as found in the control file of " "the package, and re-upload that. Also, you'll need to get the override file " -"updated, as described in <xref linkend=\"override-file\"/> ." +"updated, as described in <xref linkend=\"override-file\"/>." msgstr "" +"一方で、もしパッケージの一つの<literal>サブセクション</literal> (例:「devel」" +"「admin」) を変更する必要がある、という場合には、手順は全く異なります。パッ" +"ケージの control ファイルにあるサブセクションを修正して、再アップロードしま" +"す。また、<xref linkend=\"override-file\"/> に記述してあるように override " +"ファイルを更新する必要が出てくるでしょう。" # 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 " "bug against <literal>ftp.debian.org</literal> asking that the package be " "removed; as all bugs, this bug should normally have normal severity. The " -"bug title should be in the form <literal>RM: <replaceable>package </" +"bug title should be in the form <literal>RM: <replaceable>package</" "replaceable> <replaceable>[architecture list]</replaceable> -- " "<replaceable>reason</replaceable></literal>, where <replaceable>package</" "replaceable> is the package to be removed and <replaceable>reason</" @@ -1677,12 +2518,26 @@ msgid "" "<replaceable>[architecture list]</replaceable> is optional and only needed " "if the removal request only applies to some architectures, not all. Note " "that the <command>reportbug</command> will create a title conforming to " -"these rules when you use it to report a bug against the <literal> ftp.debian." +"these rules when you use it to report a bug against the <literal>ftp.debian." "org</literal> pseudo-package." msgstr "" +"何らかの理由でパッケージを完全に削除したくなった場合 (もう必要がなくなった古" +"い互換用ライブラリの場合、など)、パッケージを削除するよう <literal>ftp." +"debian.org</literal> に対してバグ登録をする必要があります; すべてのバグ同様、" +"通常このバグは重要度 normal です。バグの題名は <literal>RM: <replaceable>パッ" +"ケージ名</replaceable> <replaceable>[アーキテクチャ一覧]</replaceable> -- " +"<replaceable>理由</replaceable></literal> という形式である必要があります。" +"<replaceable>パッケージ名</replaceable>は削除されるパッケージ、<replaceable>" +"理由</replaceable>は削除を依頼する理由の短い要約です。<replaceable>[アーキテ" +"クチャ一覧]</replaceable>はオプションで、削除依頼が全アーキテクチャではなく一" +"部のアーキテクチャのみに適用される場合にのみ、必要となります。" +"<command>reportbug</command> は <literal>ftp.debian.org</literal> 擬似パッ" +"ケージに対してバグを報告しようとした場合に、これらのルールに則ってバグの題名" +"を作成しようとすることに注意してください。" # 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). " @@ -1691,20 +2546,36 @@ msgid "" "ulink> for a complete list. That page also provides a convenient overview of " "pending removal requests." msgstr "" +"あなたがメンテナンスしているパッケージを削除したくなった場合は、題名の先頭に " +"<literal>ROM</literal> (Request Of Maintainer) という文字を付けたバグにこれを" +"記述する必要があります。パッケージの削除理由に使われる他の一般的な略語が幾つ" +"かありますので、完全な一覧については <ulink url=\"http://&ftp-master-host;/" +"removals.html\"></ulink> を参照してください。このページでは、まだ作業されてい" +"ない削除依頼の便利な一覧も見ることができます。" + +# FIXME-TRANS: experimental は試験版？実験版 +#. 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> distribution. " +"Packages are not removed from <literal>testing</literal> directly. Rather, " +"they will be removed automatically after the package has been removed from " +"<literal>unstable</literal> and no package in <literal>testing</literal> " +"depends on it." +msgstr "" +"削除は<literal>不安定版 (unstable)</literal>、<literal>実験版 (experimental)" +"</literal>、<literal>安定版 (stable)</literal> ディストリビューションに対して" +"のみ実施が可能であることに注意してください。パッケージは <literal>テスト版 " +"(testing)</literal> から直接は削除されません。代わりに<literal>不安定版 " +"(unstable)</literal> から削除された後で自動的に削除され、<literal>テスト版 " +"(testing)</literal> にあるパッケージは削除されたパッケージに依存しなくなりま" +"す。" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1268 -msgid "" -"Note that removals can only be done for the <literal>unstable </literal>, " -"<literal>experimental</literal> and <literal>stable </literal> " -"distribution. Packages are not removed from <literal>testing</literal> " -"directly. Rather, they will be removed automatically after the package has " -"been removed from <literal>unstable</literal> and no package in " -"<literal>testing </literal> depends on it." -msgstr "" - -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1277 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:1304 +#, fuzzy 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-" @@ -1714,18 +2585,31 @@ msgid "" "necessary. For a source-package, this means that all binary packages it " "refers to have been taken over by another source package." msgstr "" +"例外として、明示的な削除依頼が必要ない場合が一つあります: (ソース、あるいはバ" +"イナリ) パッケージがみなしご化された場合、半自動的に削除されます。バイナリ" +"パッケージの場合は、これはこのバイナリパッケージを生成するソースパッケージは" +"最早存在しないということを意味します。バイナリパッケージがいくつかのアーキテ" +"クチャで生成されなくなった場合は、削除依頼は必要です。ソースパッケージの場合" +"は、関連の全バイナリパッケージが別のソースパッケージによって上書きされるのを" +"意味しています。" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1286 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:1313 +#, fuzzy 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 " "package has been removed. For example, you can provide the name of the " "package that supersedes the one to be removed." 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 " @@ -1735,17 +2619,29 @@ msgid "" "retitle the <literal>O:</literal> bug filed against the <literal>wnpp</" "literal> package instead of filing a new bug as removal request." msgstr "" +"通常は自分がメンテナンスしているパッケージの削除のみを依頼します。その他の" +"パッケージを削除したい場合は、メンテナの許可を取る必要があります。パッケージ" +"がみなしご化されたのでメンテナがいない場合は、まず &email-debian-qa; で削除依" +"頼について議論をしてください。パッケージの削除についての合意ができたら、削除" +"依頼の新規バグを登録するのではなく、<literal>wnpp</literal> パッケージに対し" +"て登録されているバグを reassign して <literal>O:</literal> に題名を変更するべ" +"きです。" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1302 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:1329 +#, fuzzy msgid "" "Further information relating to these and other package removal related " "topics may be found at <ulink url=\"http://wiki.debian.org/ftpmaster_Removals" "\"></ulink> and <ulink url=\"&url-debian-qa;howto-remove.html\"></ulink>." msgstr "" +"この件、あるいはパッケージ削除に関するその他のトピックについて、さらなる情報" +"を <ulink url=\"http://wiki.debian.org/ftpmaster_Removals\"></ulink> や " +"<ulink url=\"&url-debian-qa;howto-remove.html\"></ulink> で参照できます。" -# 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</" @@ -1753,29 +2649,54 @@ msgid "" "package. When invoked as <literal>apt-cache showpkg <replaceable>package</" "replaceable></literal>, the program will show details for " "<replaceable>package</replaceable>, including reverse depends. Other useful " -"programs include <literal>apt-cache rdepends</literal>, <command>apt-" +"programs include <command>apt-cache rdepends</command>, <command>apt-" "rdepends</command>, <command>build-rdeps</command> (in the <systemitem role=" "\"package\">devscripts</systemitem> package) and <command>grep-dctrl</" "command>. Removal of orphaned packages is discussed on &email-debian-qa;." msgstr "" - -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1320 +"パッケージを破棄しても構わないか迷う場合には、意見を聞きに &email-debian-" +"devel; へメールしてください。<systemitem role=\"package\">apt</systemitem> " +"の <command>apt-cache</command> プログラムも重要です。<literal>apt-cache" +"showpkg <replaceable>パッケージ名</replaceable></literal> として起動した際、" +"プログラムは<replaceable>パッケージ名</replaceable>の非依存関係を含む詳細を" +"表示します。他にも <command>apt-cache rdepends</command>、<command>" +"apt-rdepends</command>、<command>build-rdeps</command> (<systemitem " +"role=\"package\">devscripts</systemitem> パッケージに含まれる)、<command>" +"grep-dctrl</command> などの有用なプログラムが非依存関係を含む情報を表示" +"します。みなしご化されたパッケージの削除は、&email-debian-qa; で話し合われ" +"ます。" + +#. 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." -msgstr "" +"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 "" +"一旦パッケージが削除されたら、パッケージのバグを処理する必要があります。" +"実際のコードが別のパッケージに含まれるようになったので、別のパッケージへ" +"バグを付け替える (例えば、<literal>libfoo13</literal> が上書きするので、" +"<literal>libfoo12</literal> が削除される) か、あるいはソフトウェアがもう " +"Debian の一部では無くなった場合にはバグを閉じるかする必要があります。" +"バグを閉じる場合、過去の Debian のリリースにあるパッケージバージョンで" +"修正されたとマークするのを避けてください。バージョン <literal>" +"<most-recent-version-ever-in-Debian>+rm</literal> で修正されたと" +"マークしなければなりません。" # 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 " @@ -1787,32 +2708,54 @@ msgid "" "proper testing of your packages, the need to replace a package should not " "occur too often anyway." msgstr "" +"以前は、<filename>incoming</filename> からパッケージを削除することが可能でし" +"た。しかし、新しい incoming システムが導入されたことにより、これはもはや不可" +"能となっています。その代わりに、置き換えたいパッケージよりも高いバージョンの" +"リビジョンの新しいパッケージをアップロードする必要があります。両方のバージョ" +"ンのパッケージがアーカイブにインストールされますが、一つ前のバージョンはすぐ" +"に高いバージョンで置き換えられるため、実際にはバージョンが高い方だけが " +"<literal>不安定版 (unstable)</literal> で利用可能になります。しかし、もしあな" +"たがパッケージをきちんとテストしていれば、パッケージを置き換える必要はそんな" +"に頻繁には無いはずです。" # 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 " "two-step process to rename it. In the first step, change the " "<filename>debian/control</filename> file to reflect the new name and to " "replace, provide and conflict with the obsolete package name (see the <ulink " -"url=\"&url-debian-policy;\"> Debian Policy Manual</ulink> for details). " +"url=\"&url-debian-policy;\">Debian Policy Manual</ulink> for details). " "Please note that you should only add a <literal>Provides</literal> relation " "if all packages depending on the obsolete package name continue to work " "after the renaming. Once you've uploaded the package and the package has " -"moved into the archive, file a bug against <literal> ftp.debian.org</" -"literal> asking to remove the package with the obsolete name (see <xref " -"linkend=\"removing-pkgs\"/>). Do not forget to properly reassign the " -"package's bugs at the same time." -msgstr "" - -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1362 +"moved into the archive, file a bug against <literal>ftp.debian.org</literal> " +"asking to remove the package with the obsolete name (see <xref linkend=" +"\"removing-pkgs\"/>). Do not forget to properly reassign the package's bugs " +"at the same time." +msgstr "" +"あなたのパッケージのどれかの開発元のメンテナらがソフトウェアをリネームするの" +"を決めた時 (あるいはパッケージを間違えて名前を付けた時)、以下の二段階の" +"リネーム手続きに従う必要があります。最初の段階では、<filename>debian/control" +"</filename> ファイルに新しい名前を反映し、利用しなくなるパッケージ名に対して " +" Replace、Provides、Conflicts を設定する変更をします (詳細に関しては <ulink " +"url=\"&url-debian-policy;\">Debian ポリシーマニュアルl</ulink> を参照)。" +"注意してほしいのは、もし利用しなくなるパッケージ名がリネーム後も動作する場合に" +"のみ <literal>Provides</literal> を付け加えるべきだということです。" +"一旦パッケージをアップロードがアップロードされてアーカイブに移動したら、" +"<literal>ftp.debian.org</literal> に対してバグを報告してください (<xref " +"linkend=\"removing-pkgs\"/> 参照)。同時にパッケージのバグを正しく付け替え" +"するのを忘れないでください。" + +#. 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 " @@ -1820,18 +2763,31 @@ msgid "" "manner. Note that this applies to each part of your package, including the " "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." -msgstr "" +"to replace <filename>foo_1.00.orig.tar.gz</filename> with " +"<filename>foo_1.00+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 "" +"他に、パッケージの作成でミスを犯したので置き換えたいという場合があるかも" +"しれません。これを行う方法は唯一つ、バージョン番号を上げて新しいバージョンを" +"アップロードすることです。通常、古いバージョンは無効になります。これはソース" +"を含めた各パッケージ部分に適用されることに注意してください: パッケージの開発元" +"のソース tarball を入れ替えたい場合には、別のバージョンをつけてアップロード" +"する必要があります。よくある例は <filename>foo_1.00.orig.tar.gz</filename> " +"を <filename>foo_1.00+0.orig.tar.gz</filename>、あるいは <filename>" +"foo_1.00.orig.tar.bz2</filename> で置き換えるというものです。" +"この制約によって、ftp サイト上で各ファイルが一意の名前を持つことになり、" +"ミラーネットワークをまたがった一貫性を保障するのに役立ちます。" # 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 " @@ -1847,9 +2803,23 @@ msgid "" "use CC:, because that way the message's subject won't indicate the bug " "number)." msgstr "" +"パッケージをもうメンテナンスできなくなってしまった場合、ほかの人に知らせて、" +"パッケージがみなしご化 (orphaned) とマークされたのが分かるようにする必要があ" +"ります。パッケージメンテナを <literal>Debian QA Group &orphan-address;</" +"literal> に設定し、疑似パッケージ<systemitem role=\"package\">wnpp</" +"systemitem> に対してバグ報告を送信しなければなりません。バグ報告は、パッケー" +"ジが今みなしご化されていることを示すように <literal>O: <replaceable>パッケー" +"ジ名</replaceable> -- <replaceable>短い要約</replaceable></literal> というタ" +"イトルにする必要があります。バグの重要度は <literal>通常 (normal)</literal> " +"に設定しなければなりません; パッケージの重要 (priority) が standard より高い" +"場合には重要 (important) に設定する必要があります。必要だと思うのならば、メッ" +"セージの X-Debbugs-CC: ヘッダのアドレスに &email-debian-devel; を入れてコピー" +"を送ってください (そう、CC: を使わないでください。その理由は、CC: を使うと、" +"メッセージの題名がバグ番号を含まないからです)。" # 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 " @@ -1858,9 +2828,16 @@ msgid "" "replaceable></literal>. <literal>RFA</literal> stands for <literal>Request " "For Adoption</literal>." msgstr "" +"パッケージを手放したいが、しばらくの間はメンテナンスを継続できる場合には、代" +"わりに <systemitem role=\"package\">wnpp</systemitem> へ <literal>RFA: " +"<replaceable>パッケージ名</replaceable> -- <replaceable>短い要約</" +"replaceable></literal> という題名でバグ報告を送信する必要があります。" +"<literal>RFA</literal> は <literal>Request For Adoption (引き取り依頼)</" +"literal> を意味しています。" # 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 "" @@ -1868,12 +2845,14 @@ 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)</" @@ -1881,19 +2860,30 @@ msgid "" "in the WNPP, please take a look at the aforementioned page for information " "and procedures." msgstr "" +"新たなメンテナが必要なパッケージの一覧は <ulink url=\"&url-wnpp;\">作業が" +"望まれるパッケージ (WNPP、Work-Needing and Prospective Packages list)" +"</ulink> で入手できます。WNPP でリストに挙がっているパッケージのどれかに" +"対するメンテナンスを引き継ぎたい場合には、情報と手続きについては前述の" +"ページを確認してください。" -# 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 " "maintainer and ask them if you may take over the package. If you have " "reason to believe a maintainer has gone AWOL (absent without leave), see " -"<xref linkend=\"mia-qa\"/> ." +"<xref linkend=\"mia-qa\"/>." msgstr "" +"メンテナンスされていないと思うパッケージを単純に持っていっても構いませんか? " +"- それはパッケージの乗っ取り (hijacking) です。できますが、もちろんのこと、" +"現在のメンテナに確認をとってパッケージを持って行って良いか尋ねましょう。" +"メンテナが AWOL (absent without leave、無届け欠席状態) であると信ずる理由が" +"あれば、<xref linkend=\"mia-qa\"/> を参照してください。" # 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 " @@ -1903,53 +2893,82 @@ msgid "" "the attention of the technical committee (see the <ulink url=\"&url-tech-" "ctte;\">technical committee web page</ulink> for more information)." msgstr "" +"一般的に、現在のメンテナの同意なしでパッケージを引き取るべきではありません。" +"彼らがあなたのことを無視したのだとしても、それはパッケージを引き取る理由とは" +"なりません。メンテナへの不満は開発者のメーリングリストへ送られるべきです。" +"議論が良い結論に至らない、かつ問題が技術的なものなのであれば、技術委員会に" +"相談することを検討してください (より詳細については、<ulink url=\"&url-tech-ctte;\">" +"Debian 技術委員会のページ</ulink> を参照してください)。" -# 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 " "automatically once you upload a new version with an updated " -"<literal>Maintainer:</literal> field, although it can take a few hours after " +"<literal>Maintainer</literal> field, although it can take a few hours after " "the upload is done. If you do not expect to upload a new version for a " "while, you can use <xref linkend=\"pkg-tracking-system\"/> to get the bug " "reports. However, make sure that the old maintainer has no problem with the " "fact that they will continue to receive the bugs during that time." msgstr "" +"古いパッケージを引き継いだ場合は、おそらくバグ追跡システムでパッケージの" +"公式メンテナとして表示されるようにしたいことでしょう。これは、一旦 " +"<literal>Maintainer</literal> 欄を更新した新しいバージョンをアップロードすれば" +"自動的に行われますが、アップロードが完了してから数時間はかかります。しばらくは" +"新しいバージョンをアップロードする予定が無い場合は、<xref " +"linkend=\"pkg-tracking-system\"/> を使ってバグ報告を受け取ることができます。" +"しかし、以前のメンテナにしばらくの間はバグ報告が届き続けても問題無いことを" +"確認してください。" # type: Content of: <chapter><section><title> -#: pkgs.dbk:1446 +#. type: Content of: <chapter><section><title> +#: pkgs.dbk:1478 msgid "Porting and being ported" -msgstr "" +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 " "duty as a maintainer to be aware of issues of portability. Therefore, even " "if you are not a porter, you should read most of this chapter." msgstr "" +"Debian がサポートするアーキテクチャの数は増え続けています。あなたが移植作業者" +"ではない、あるいは別のアーキテクチャを使うことが無いという場合であっても、移" +"植性の問題に注意を払うことはメンテナとしてのあなたの義務です。従って、あなた" +"が移植作業者でなくても、この章の大半を読む必要があります。" -# 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 " "package. It is a unique and essential activity. In fact, porters do most " "of the actual compiling of Debian packages. For instance, when a maintainer " -"uploads a (portable) source packages with binaries for the <literal>i386 </" +"uploads a (portable) source packages with binaries for the <literal>i386</" "literal> architecture, it will be built for each of the other architectures, " "amounting to &number-of-arches; more builds." msgstr "" +"移植作業 (Porting) とは、パッケージメンテナが生成したバイナリパッケージの元々" +"のアーキテクチャとは違うアーキテクチャの Debian パッケージをビルドする作業です。" +"これは非常にユニークかつ極めて重要な活動です。事実、移植作業者は実際の Debian " +"パッケージのコンパイルの大半を行っています。例えば、メンテナが (移植可能な) " +"ソースパッケージと <literal>i386</literal> のバイナリをアップロードすると、" +"他の各アーキテクチャ、&number-of-arches; 以上の数のビルドが生成されます。" # 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 "" +msgstr "移植作業者に対して協力的になる" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1465 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:1497 +#, fuzzy 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 " @@ -1958,9 +2977,15 @@ msgid "" "maintainers — common problems which often stymie porters, and make their " "jobs unnecessarily difficult." 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 " @@ -1968,48 +2993,74 @@ msgid "" "tolerant of succinct or even unclear bug reports; do your best to hunt down " "whatever the problem is." msgstr "" +"まず初めの、そして最も重要な点はバグや移植作業者から投げかけられた問題に" +"素早く回答することです。移植作業者をパッケージの副メンテナ (co-maintainer) " +"であるように丁重に扱ってください (ある意味、その通りではあります)。簡潔、" +"あるいは不明瞭なバグ報告に寛容になってください。問題が何であれ、原因を捕える" +"ことに最善を尽くしてください。" # 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 " "checklist of things you should check or be aware of." msgstr "" +"移植作業者が遭遇する問題のほとんどは、何といっても、ソースパッケージ内での" +"<emphasis>パッケージ作成のバグ</emphasis>によって引き起こされます。以下は" +"、確認あるいは注意すべき項目のリストです。" -# 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 " "set properly. The best way to validate this is to use the <systemitem role=" "\"package\">debootstrap</systemitem> package to create an <literal>unstable</" -"literal> chroot environment (see <xref linkend=\"debootstrap\"/> ). Within " +"literal> chroot environment (see <xref linkend=\"debootstrap\"/>). Within " "that chrooted environment, install the <systemitem role=\"package\">build-" "essential</systemitem> package and any package dependencies mentioned in " "<literal>Build-Depends</literal> and/or <literal>Build-Depends-Indep</" "literal>. Finally, try building your package within that chrooted " "environment. These steps can be automated by the use of the " "<command>pbuilder</command> program which is provided by the package of the " -"same name (see <xref linkend=\"pbuilder\"/> )." -msgstr "" - -# type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1502 +"same name (see <xref linkend=\"pbuilder\"/>)." +msgstr "" +"<filename>debian/control</filename> 中の <literal>Build-Depends</literal> と " +"<literal>Build-Depends-Indep</literal> の設定が正しいことを確認してください。" +"これを検証するのに最も良い方法は <systemitem role=\"package\">debootstrap" +"</systemitem> パッケージを使って <literal>不安定版 (unstable)</literal> " +"の chroot 環境を作成することです (<xref linkend=\"debootstrap\"/> 参照)。" +"chroot 環境内では、<systemitem role=\"package\">build-essential</systemitem> " +"パッケージと、<literal>Build-Depends</literal> または <literal>Build-Depends-Indep" +"</literal> に記載されている依存パッケージをインストールしてください。" +"最後に、chroot 環境でパッケージの生成を試してください。これらの手順は " +"<command>pbuilder</command> パッケージで提供される同名のプログラムの利用に" +"よって自動化することができます (<xref linkend=\"pbuilder\"/> 参照)。" + +#. type: Content of: <chapter><section><section><orderedlist><listitem><para> +#: pkgs.dbk:1534 msgid "" "If you can't set up a proper chroot, <command>dpkg-depcheck</command> may be " -"of assistance (see <xref linkend=\"dpkg-depcheck\"/> )." +"of assistance (see <xref linkend=\"dpkg-depcheck\"/>)." msgstr "" +"chroot を正しく設定できない場合は、<command>dpkg-depcheck</command> が手助け" +"になることでしょう (<xref linkend=\"dpkg-depcheck\"/> 参照)。" # 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 "" +"ビルドの依存情報の指定方法については、<ulink url=\"&url-debian-policy;" +"\">Debian ポリシーマニュアル</ulink>を参照してください。" # 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, " @@ -2018,9 +3069,15 @@ msgid "" "one architecture (such as <literal>i386</literal> or <literal>amd64</" "literal>) is usually incorrect." msgstr "" +"意図がある場合以外は、アーキテクチャの値を <literal>all</literal> または " +"<literal>any</literal> 以外に指定しないでください。非常に多くの場合、メンテナ" +"が <ulink url=\"&url-debian-policy;\">Debianポリシーマニュアル</ulink> の指示" +"に従っていません。アーキテクチャを単一のものに指定する (<literal>i386</" +"literal> あるいは <literal>amd64</literal> など) は大抵誤りです。" # 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 " @@ -2029,7 +3086,8 @@ msgid "" 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 " @@ -2038,7 +3096,8 @@ msgid "" 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>/" @@ -2048,7 +3107,8 @@ msgid "" 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 " @@ -2057,7 +3117,8 @@ msgid "" 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 " @@ -2065,23 +3126,26 @@ msgid "" "standardize on different compilers." 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 " -"requires. Make sure that both targets work independently, that is, that you " -"can call the target without having called the other before. To test this, " -"try to run <command>dpkg-buildpackage -B</command>." +"Make sure your <filename>debian/rules</filename> contains separate " +"<literal>binary-arch</literal> and <literal>binary-indep</literal> targets, " +"as the Debian Policy Manual requires. Make sure that both targets work " +"independently, that is, that you can call the target without having called " +"the other before. To test this, try to run <command>dpkg-buildpackage -B</" +"command>." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk: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 " @@ -2092,26 +3156,28 @@ msgid "" 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 " "<filename>debian/changelog</filename>." 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 " "course, set <replaceable>porter-email</replaceable> to your email address. " "This will do a binary-only build of only the architecture-dependent portions " "of the package, using the <literal>binary-arch</literal> target in " -"<filename>debian/rules </filename>." +"<filename>debian/rules</filename>." 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 " @@ -2121,34 +3187,36 @@ msgid "" 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 "" +msgstr "再コンパイル、あるいは binary-only NMU" -# 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 " -"library, bad compiler, ...). Then you may just need to recompile it in an " +"library, bad compiler, etc.). Then you may just need to recompile it in an " "updated environment. However, you have to bump the version number in this " "case, so that the old bad package can be replaced in the Debian archive " "(<command>dak</command> refuses to install new packages if they don't have a " "version number greater than the currently available one)." 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-" "dependent and arch-independent packages that have inter-dependencies " -"generated using dpkg's substitution variable <literal>$(Source-Version) </" +"generated using dpkg's substitution variable <literal>$(Source-Version)</" "literal>." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1623 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:1654 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 " @@ -2156,7 +3224,8 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1628 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:1659 msgid "" "Such recompilations require special ``magic'' version numbering, so that the " "archive maintenance tools recognize that, even though there is a new Debian " @@ -2165,21 +3234,9 @@ msgid "" "corresponding source code)." msgstr "" -# type: Content of: <chapter><section><section><section><para><footnote> -#: pkgs.dbk:1635 -msgid "" -"The ``magic'' for a recompilation-only NMU is triggered by using a suffix " -"appended to the package version number, following the form <literal> " -"b<replaceable>number</replaceable></literal>. For instance, if the latest " -"version you are recompiling against was version <literal>2.9-3</literal>, " -"your binary-only NMU should carry a version of <literal>2.9-3+b1</literal>. " -"If the latest version was <literal>3.4+b1 </literal> (i.e, a native package " -"with a previous recompilation NMU), your binary-only NMU should have a " -"version number of <literal>3.4+b2</literal>. <footnote>" -msgstr "" - # type: Content of: <chapter><section><section><section><para><footnote><para> -#: pkgs.dbk:1643 +#. type: Content of: <chapter><section><section><section><para><footnote><para> +#: pkgs.dbk:1674 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 " @@ -2188,8 +3245,23 @@ msgid "" "has therefore been abandoned in favor of this new syntax." msgstr "" +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:1666 +msgid "" +"The ``magic'' for a recompilation-only NMU is triggered by using a suffix " +"appended to the package version number, following the form " +"<literal>b<replaceable>number</replaceable></literal>. For instance, if the " +"latest version you are recompiling against was version <literal>2.9-3</" +"literal>, your binary-only NMU should carry a version of <literal>2.9-3+b1</" +"literal>. If the latest version was <literal>3.4+b1</literal> (i.e, a " +"native package with a previous recompilation NMU), your binary-only NMU " +"should have a version number of <literal>3.4+b2</literal>.<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:1682 msgid "" "Similar to initial porter uploads, the correct way of invoking <command>dpkg-" "buildpackage</command> is <literal>dpkg-buildpackage -B</literal> to only " @@ -2197,15 +3269,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1658 +#. type: Content of: <chapter><section><section><section><title> +#: pkgs.dbk:1689 +#, fuzzy msgid "When to do a source NMU if you are a porter" -msgstr "" +msgstr "あなたが移植作業者の場合、source NMU を行う時は何時か" -# type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1660 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:1691 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 " +"linkend=\"nmu\"/>, just like non-porters. However, it is expected that the " "wait cycle for a porter's source NMU is smaller than for a non-porter, since " "porters have to cope with a large quantity of packages. Again, the " "situation varies depending on the distribution they are uploading to. It " @@ -2214,8 +3288,8 @@ msgid "" "architectures are candidates." msgstr "" -# type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1669 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:1700 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, " @@ -2225,12 +3299,13 @@ msgid "" "shortened if the problem is critical and imposes hardship on the porting " "effort, at the discretion of the porter group. (Remember, none of this is " "Policy, just mutually agreed upon guidelines.) For uploads to " -"<literal>stable</literal> or <literal>testing </literal>, please coordinate " +"<literal>stable</literal> or <literal>testing</literal>, please coordinate " "with the appropriate release team first." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1681 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:1712 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 " @@ -2241,7 +3316,8 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1689 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:1720 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 " @@ -2252,7 +3328,8 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1697 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:1728 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 " @@ -2261,12 +3338,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1707 +#. type: Content of: <chapter><section><section><title> +#: pkgs.dbk:1738 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:1740 msgid "" "There is infrastructure and several tools to help automate package porting. " "This section contains a brief overview of this automation and porting to " @@ -2275,78 +3354,92 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1714 +#. type: Content of: <chapter><section><section><section><title> +#: pkgs.dbk:1745 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:1747 msgid "" "Web pages containing the status of each port can be found at <ulink url=" "\"&url-debian-ports;\"></ulink>." msgstr "" +"各移植版についての状況を含んだウェブページは <ulink url=\"&url-debian-ports;" +"\"></ulink> から参照できます。" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1720 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:1751 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 " "lists are used to coordinate porters, and to connect the users of a given " "port with the porters." msgstr "" +"Debian の各移植版はメーリングリストを持っています。移植作業のメーリングリスト" +"は <ulink url=\"&url-debian-port-lists;\"></ulink> で見ることができます。これ" +"らのリストは移植作業者の作業の調整や移植版のユーザと移植作業者をつなぐために" +"使われています。" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1728 +#. type: Content of: <chapter><section><section><section><title> +#: pkgs.dbk:1759 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:1761 msgid "" "Descriptions of several porting tools can be found in <xref linkend=\"tools-" -"porting\"/> ." +"porting\"/>." msgstr "" +"移植用のツールの説明をいくつか <xref linkend=\"tools-porting\"/> で見ることが" +"できます。" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1736 +#. type: Content of: <chapter><section><section><section><title> +#: pkgs.dbk:1767 msgid "<systemitem role=\"package\">wanna-build</systemitem>" -msgstr "" +msgstr "<systemitem role=\"package\">wanna-build</systemitem>" -# type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1738 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:1769 msgid "" "The <systemitem role=\"package\">wanna-build</systemitem> system is used as " "a distributed, client-server build distribution system. It is usually used " "in conjunction with build daemons running the <systemitem role=\"package" -"\">buildd </systemitem> program. <literal>Build daemons</literal> are " -"``slave'' hosts which contact the central <systemitem role=\"package\"> " -"wanna-build</systemitem> system to receive a list of packages that need to " -"be built." +"\">buildd</systemitem> program. <literal>Build daemons</literal> are " +"``slave'' hosts which contact the central <systemitem role=\"package\">wanna-" +"build</systemitem> system to receive a list of packages that need to be " +"built." msgstr "" -# type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1746 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:1777 msgid "" "<systemitem role=\"package\">wanna-build</systemitem> is not yet available " "as a package; however, all Debian porting efforts are using it for automated " "package building. The tool used to do the actual package builds, " "<systemitem role=\"package\">sbuild</systemitem> is available as a package, " -"see its description in <xref linkend=\"sbuild\"/> . Please note that the " +"see its description in <xref linkend=\"sbuild\"/>. Please note that the " "packaged version is not the same as the one used on build daemons, but it is " "close enough to reproduce problems." msgstr "" -# type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1755 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:1786 msgid "" -"Most of the data produced by <systemitem role=\"package\">wanna-build </" +"Most of the data produced by <systemitem role=\"package\">wanna-build</" "systemitem> which is generally useful to porters is available on the web at " "<ulink url=\"&url-buildd;\"></ulink>. This data includes nightly updated " "statistics, queueing information and logs for build attempts." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1761 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:1792 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 " @@ -2355,20 +3448,31 @@ msgid "" "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:1799 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:1806 +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:1815 msgid "When your package is <emphasis>not</emphasis> portable" -msgstr "" +msgstr "あなたのパッケージが移植可能なものでは<emphasis>ない</emphasis>場合" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1778 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:1817 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 " @@ -2379,14 +3483,16 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1785 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:1824 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:1830 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 " @@ -2398,7 +3504,8 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1799 +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:1838 msgid "" "Additionally, if you believe the list of supported architectures is pretty " "constant, you should change <literal>any</literal> to a list of supported " @@ -2406,502 +3513,477 @@ msgid "" "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:1846 msgid "" "In order to prevent autobuilders from needlessly trying to build your " -"package, it must be included in <filename>packages-arch-specific</filename>, " +"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:1855 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: " -"A porter or any other person trying to build your package might accidently " -"upload it without noticing it doesn't work. If in the past some binary " -"packages were uploaded on unsupported architectures, request their removal " -"by filing a bug against <systemitem role=\"package\">ftp.debian.org</" -"systemitem>" +"Please note that it is insufficient to only add your package to " +"<filename>Packages-arch-specific</filename> without making it fail to build " +"on unsupported architectures: A porter or any other person trying to build " +"your package might accidently upload it without noticing it doesn't work. " +"If in the past some binary packages were uploaded on unsupported " +"architectures, request their removal by filing a bug against <systemitem " +"role=\"package\">ftp.debian.org</systemitem>." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:1830 +#. type: Content of: <chapter><section><title> +#: pkgs.dbk:1868 msgid "Non-Maintainer Uploads (NMUs)" -msgstr "" +msgstr "Non-Maintainer Upload (NMU)" -# type: Content of: <chapter><section><para> -#: pkgs.dbk:1832 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:1870 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." +"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><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><section><title> +#. type: Content of: <chapter><section><section><title> +#: pkgs.dbk:1879 +msgid "When and how to do an NMU" +msgstr "いつ、どうやって NMU を行うか" -# 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><section><para> +#: pkgs.dbk:1882 +msgid "Before doing an NMU, consider the following questions:" +msgstr "NMU を行う前に、以下の質問について考えてください:" -# type: Content of: <chapter><section><para> -#: pkgs.dbk:1849 +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:1887 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." +"Does your NMU really fix bugs? Fixing cosmetic issues or changing the " +"packaging style in NMUs is discouraged." msgstr "" -# type: Content of: <chapter><section><para> -#: pkgs.dbk:1858 +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:1893 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." +"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><title> -#: pkgs.dbk:1863 -msgid "How to do a NMU" -msgstr "NMU のやり方" - -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1865 +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:1900 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." +"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><para> -#: pkgs.dbk:1871 +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:1910 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." +"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:1877 +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:1917 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:" +"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><itemizedlist><listitem><para> -#: pkgs.dbk:1884 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:1927 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." +"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 <command>nmudiff</command> " +"script in the <systemitem role=\"package\">devscripts</systemitem> package " +"might be helpful." msgstr "" -# type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1891 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:1934 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." +"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" +"\"><filename>debian/README.source</filename></ulink>." msgstr "" -# type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1898 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:1942 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." +"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><itemizedlist><listitem><para> -#: pkgs.dbk:1908 -msgid "" -"Upload your package to incoming in <filename>DELAYED/7-day</filename> (cf. " -"<xref linkend=\"delayed-incoming\"/> ), send the final patch to the " -"maintainer via the BTS, and explain to them that they have 7 days to react " -"if they want to cancel the NMU." +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:1949 +msgid "Upload fixing only release-critical bugs older than 7 days: 2 days" msgstr "" +"7 日以上経っているリリースクリティカルバグのみを修正するアップロード: 2 日" -# type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1916 -msgid "" -"Follow what happens, you're responsible for any bug that you introduced with " -"your NMU. You should probably use <xref linkend=\"pkg-tracking-system\"/> " -"(PTS) to stay informed of the state of the package after your NMU." -msgstr "" +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:1954 +msgid "Upload fixing only release-critical and important bugs: 5 days" +msgstr "リリースクリティカルバグや重要なバグの修正のみのアップロード: 5 日" -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1923 -msgid "" -"At times, the release manager or an organized group of developers can " -"announce a certain period of time in which the NMU rules are relaxed. This " -"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." -msgstr "" +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:1959 +msgid "Other NMUs: 10 days" +msgstr "他の NMU: 10 日" -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1932 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:1965 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>." +"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:1938 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:1971 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." +"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:1944 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:1981 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." +"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:1949 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:1987 msgid "" -"For the differences for Porters NMUs, please see <xref linkend=\"source-nmu-" -"when-porter\"/> ." +"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><para> -#: pkgs.dbk:1953 +#. type: Content of: <chapter><section><section><title> +#: pkgs.dbk:1997 +msgid "NMUs and <filename>debian/changelog</filename>" +msgstr "NMU と <filename>debian/changelog</filename>" + +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:1999 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)." +"Just like any other (source) upload, NMUs must add an entry to " +"<filename>debian/changelog</filename>, 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><title> -#: pkgs.dbk:1960 -msgid "NMU version numbering" -msgstr "" +# type: Content of: <chapter><section><section><screen> +#. type: Content of: <chapter><section><section><screen> +#: pkgs.dbk:2004 +#, no-wrap +msgid " * Non-maintainer upload.\n" +msgstr " * Non-maintainer upload.\n" -# 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." +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2008 +msgid "The way to version NMUs differs for native and non-native packages." msgstr "" -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1966 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2011 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>." +"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:1977 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2021 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." +"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 <literal>1</literal>. 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> -#: pkgs.dbk:1983 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2030 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'." +"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:1993 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2036 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." +"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> +#: pkgs.dbk:2046 +msgid "" +"If you upload a package to testing or stable, you sometimes need to \"fork\" " +"the version number tree. This is the case for security uploads, for " +"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 Lenny (Debian 5.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+deb50u1</literal>, whereas a security NMU " +"to Squeeze would get version <literal>1.5-3+deb60u1</literal>. After the " +"release of Squeeze, security uploads to the <literal>testing</literal> " +"distribution will be versioned <literal>+deb61uZ</literal>, until it is " +"known whether that release will be Debian 6.1 or Debian 7.0 (if that becomes " +"the case, uploads will be versioned as <literal>+deb70uZ</literal>)." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2000 -msgid "Source NMUs must have a new changelog entry" -msgstr "" +#. type: Content of: <chapter><section><section><title> +#: pkgs.dbk:2068 +msgid "Using the <literal>DELAYED/</literal> queue" +msgstr "<literal>DELAYED/</literal> キューを使う" -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2002 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2071 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" +"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><screen> -#: pkgs.dbk:2010 -#, fuzzy, no-wrap +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2085 msgid "" -"\n" -" * 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" +"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:2018 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2092 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 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><para> -#: pkgs.dbk:2024 -msgid "" -"What if you are simply recompiling the package? If you just need to " -"recompile it for a single architecture, then you may do a binary-only NMU as " -"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." -msgstr "" +#. type: Content of: <chapter><section><section><title> +#: pkgs.dbk:2102 +msgid "NMUs from the maintainer's point of view" +msgstr "メンテナの視点から見た NMU" -# 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." -msgstr "" - -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2036 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2105 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." +"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:2047 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2114 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." +"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:2055 -msgid "Building source NMUs" -msgstr "" +#. type: Content of: <chapter><section><section><title> +#: pkgs.dbk:2123 +msgid "Source NMUs vs Binary-only NMUs (binNMUs)" +msgstr "ソース NMU vs バイナリのみの NMU (binNMU)" -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2057 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2126 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 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><para> -#: pkgs.dbk:2062 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2133 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." +"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><title> -#: pkgs.dbk:2070 -msgid "Acknowledging an NMU" -msgstr "" - -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2072 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2139 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." +"BinNMUs are usually triggered on the buildds by wanna-build. An entry is " +"added to <filename>debian/changelog</filename>, 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><para> -#: pkgs.dbk:2083 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2147 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\"/> )." +"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 <filename>debian/" +"changelog</filename>." msgstr "" -# type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2093 -msgid "NMU vs QA uploads" -msgstr "" +#. type: Content of: <chapter><section><section><title> +#: pkgs.dbk:2155 +msgid "NMUs vs QA uploads" +msgstr "NMU vs QA アップロード" -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2095 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2158 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>." +"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><title> -#: pkgs.dbk:2105 -#, fuzzy -msgid "Who can do an NMU" -msgstr "誰が NMU 可能なのか" - -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2107 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2165 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." +"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 <literal>Maintainer</literal> or <literal>Uploader</literal> for the " +"package. Also, the changelog entry of a QA upload has a special first line:" msgstr "" -# type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2117 -msgid "Terminology" -msgstr "" +#. type: Content of: <chapter><section><section><screen> +#: pkgs.dbk:2173 +#, no-wrap +msgid " * QA upload.\n" +msgstr " * QA upload.\n" -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2119 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2177 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." +"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:2127 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2188 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." +"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><section><para> -#: pkgs.dbk:2136 -msgid "" -"A binary-only NMU is a recompilation and upload of a binary package for a " -"given architecture. As such, it is usually part of a porting effort. A " -"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." -msgstr "" +#. type: Content of: <chapter><section><section><title> +#: pkgs.dbk:2197 +msgid "NMUs vs team uploads" +msgstr "NMU vs チームアップロード" -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2146 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2200 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." +"Sometimes you are fixing and/or updating a package because you are member of " +"a packaging team (which uses a mailing list as <literal>Maintainer</literal> " +"or <literal>Uploader</literal>, see <xref linkend=\"collaborative-maint\"/>) " +"but you don't want to add yourself to <literal>Uploaders</literal> because " +"you do not plan to contribute regularly to this specific package. If it " +"conforms with your team's policy, you can perform a normal upload without " +"being listed directly as <literal>Maintainer</literal> or <literal>Uploader</" +"literal>. In that case, you should start your changelog entry with the " +"following line:" msgstr "" +#. type: Content of: <chapter><section><section><screen> +#: pkgs.dbk:2210 +#, no-wrap +msgid " * Team upload.\n" +msgstr " * Team upload.\n" + # type: Content of: <chapter><section><title> -#: pkgs.dbk:2156 +#. type: Content of: <chapter><section><title> +#: pkgs.dbk:2218 msgid "Collaborative maintenance" msgstr "共同メンテナンス" -# type: Content of: <chapter><section><para> -#: pkgs.dbk:2158 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:2220 msgid "" "Collaborative maintenance is a term describing the sharing of Debian package " "maintenance duties by several people. This collaboration is almost always a " "good idea, since it generally results in higher quality and faster bug fix " "turnaround times. It is strongly recommended that packages with a priority " -"of <literal>Standard</literal> or which are part of the base set have co-" +"of <literal>standard</literal> or which are part of the base set have co-" "maintainers." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:2166 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:2228 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 " @@ -2912,24 +3994,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:2174 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:2236 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:2242 msgid "" "Setup the co-maintainer with access to the sources you build the package " "from. Generally this implies you are using a network-capable version " -"control system, such as <command>CVS</command> or <command>Subversion</" -"command>. Alioth (see <xref linkend=\"alioth\"/> ) provides such tools, " +"control system, such as <literal>CVS</literal> or <literal>Subversion</" +"literal>. Alioth (see <xref linkend=\"alioth\"/>) provides such tools, " "amongst others." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:2188 +#. type: Content of: <chapter><section><itemizedlist><listitem><para> +#: pkgs.dbk:2250 msgid "" "Add the co-maintainer's correct maintainer name and address to the " "<literal>Uploaders</literal> field in the first paragraph of the " @@ -2937,91 +4021,101 @@ msgid "" 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:2255 +#, 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:2260 msgid "" -"Using the PTS (<xref linkend=\"pkg-tracking-system\"/> ), the co-maintainers " +"Using the PTS (<xref linkend=\"pkg-tracking-system\"/>), the co-maintainers " "should subscribe themselves to the appropriate source package." msgstr "" -# type: Content of: <chapter><section><para> -#: pkgs.dbk:2204 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:2266 msgid "" "Another form of collaborative maintenance is team maintenance, which is " "recommended if you maintain several packages with the same group of " -"developers. In that case, the Maintainer and Uploaders field of each " -"package must be managed with care. It is recommended to choose between one " -"of the two following schemes:" +"developers. In that case, the <literal>Maintainer</literal> and " +"<literal>Uploaders</literal> field of each package must be managed with " +"care. It is recommended to choose between one of the two following schemes:" msgstr "" -# type: Content of: <chapter><section><orderedlist><listitem><para> -#: pkgs.dbk:2213 +#. type: Content of: <chapter><section><orderedlist><listitem><para> +#: pkgs.dbk:2275 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 " -"who care for the package." +"Put the team member mainly responsible for the package in the " +"<literal>Maintainer</literal> field. In the <literal>Uploaders</literal>, " +"put the mailing list address, and the team members who care for the package." msgstr "" -# type: Content of: <chapter><section><orderedlist><listitem><para> -#: pkgs.dbk:2220 +#. type: Content of: <chapter><section><orderedlist><listitem><para> +#: pkgs.dbk:2282 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 " -"must make sure the mailing list accept bug reports without any human " -"interaction (like moderation for non-subscribers)." +"Put the mailing list address in the <literal>Maintainer</literal> field. In " +"the <literal>Uploaders</literal> field, put the team members who care for " +"the package. In this case, you must make sure the mailing list accept bug " +"reports without any human interaction (like moderation for non-subscribers)." msgstr "" -# type: Content of: <chapter><section><para> -#: pkgs.dbk:2228 +#. type: Content of: <chapter><section><para> +#: pkgs.dbk:2291 msgid "" "In any case, it is a bad idea to automatically put all team members in the " -"Uploaders field. It clutters the Developer's Package Overview listing (see " -"<xref linkend=\"ddpo\"/> ) with packages one doesn't really care for, and " -"creates a false sense of good maintenance." +"<literal>Uploaders</literal> field. It clutters the Developer's Package " +"Overview listing (see <xref linkend=\"ddpo\"/>) with packages one doesn't " +"really care for, and creates a false sense of good maintenance. For the same " +"reason, team members do not need to add themselves to the " +"<literal>Uploaders</literal> field just because they are uploading the " +"package once, they can do a “Team upload” (see <xref linkend=\"nmu-team-" +"upload\"/>). Conversely, it is a bad idea to keep a package with only the " +"mailing list address as a <literal>Maintainer</literal> and no " +"<literal>Uploaders</literal>." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:2236 +#. type: Content of: <chapter><section><title> +#: pkgs.dbk:2304 msgid "The testing distribution" msgstr "テスト版ディストリビューション" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2238 +#. type: Content of: <chapter><section><section><title> +#: pkgs.dbk:2306 msgid "Basics" msgstr "基本" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2240 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2308 msgid "" "Packages are usually installed into the <literal>testing</literal> " "distribution after they have undergone some degree of <literal>testing</" "literal> in <literal>unstable</literal>." msgstr "" -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2245 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2313 msgid "" "They must be in sync on all architectures and mustn't have dependencies that " "make them uninstallable; they also have to have generally no known release-" -"critical bugs at the time they're installed into <literal>testing </" +"critical bugs at the time they're installed into <literal>testing</" "literal>. This way, <literal>testing</literal> should always be close to " "being a release candidate. Please see below for details." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2254 +#. type: Content of: <chapter><section><section><title> +#: pkgs.dbk:2322 msgid "Updates from unstable" msgstr "不安定版からの更新" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2256 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2324 msgid "" "The scripts that update the <literal>testing</literal> distribution are run " "twice each day, right after the installation of the updated packages; these " @@ -3032,14 +4126,16 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2264 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2332 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:2338 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 " @@ -3050,39 +4146,42 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2280 +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:2348 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 " "<literal>testing</literal>);" msgstr "" -# type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2287 +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:2355 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 " -"interest to check that information;" +"built in <literal>unstable</literal>. <link linkend=\"dak-ls\">dak ls</link> " +"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:2362 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:2368 msgid "" "The packages on which it depends must either be available in " "<literal>testing</literal> or they must be accepted into <literal>testing</" "literal> at the same time (and they will be if they fulfill all the " -"necessary criteria);" +"necessary criteria)." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2308 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2376 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=" @@ -3095,7 +4194,8 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2319 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2387 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 " @@ -3105,7 +4205,8 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2326 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2394 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 " @@ -3113,21 +4214,23 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2331 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2399 msgid "" "Some further dependency analysis is shown on <ulink url=\"http://release." "debian.org/migration/\"></ulink> — but be warned, this page also shows build " "dependencies which are not considered by britney." msgstr "" -# type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2336 -msgid "out-of-date" +#. type: Content of: <chapter><section><section><section><title> +#: pkgs.dbk:2404 +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:2407 msgid "" "For the <literal>testing</literal> migration script, outdated means: There " "are different versions in <literal>unstable</literal> for the release " @@ -3138,68 +4241,80 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2347 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2415 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:2422 pkgs.dbk:2455 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:2423 pkgs.dbk:2456 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:2428 pkgs.dbk:2462 pkgs.dbk:2524 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:2429 pkgs.dbk:2434 pkgs.dbk:2463 pkgs.dbk:2464 pkgs.dbk:2471 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:2430 pkgs.dbk:2465 pkgs.dbk:2470 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:2433 pkgs.dbk:2468 pkgs.dbk:2525 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:2435 pkgs.dbk:2469 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:2441 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 " -"all, the package is still out of date on <literal>alpha</literal>, and will " -"not propagate to testing." +"The package is out of date on <literal>alpha</literal> in <literal>unstable</" +"literal>, and will not go to <literal>testing</literal>. Removing the " +"package would not help at all, the package is still out of date on " +"<literal>alpha</literal>, and will not propagate to <literal>testing</" +"literal>." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2379 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2447 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:2457 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:2477 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> " @@ -3207,7 +4322,8 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2414 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2482 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 " @@ -3215,12 +4331,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2421 +#. type: Content of: <chapter><section><section><section><title> +#: pkgs.dbk:2489 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:2491 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 " @@ -3229,29 +4347,31 @@ msgid "" "literal> may be removed to allow <literal>b</literal> in." msgstr "" -# type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2430 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2498 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 " -"in this state)." +"Of course, there is another reason to remove a package from " +"<literal>testing</literal>: It's just too buggy (and having a single RC-bug " +"is enough to be in this state)." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2435 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2503 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 " "will automatically be removed." msgstr "" -# type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2442 -msgid "circular dependencies" -msgstr "" +#. type: Content of: <chapter><section><section><section><title> +#: pkgs.dbk:2510 +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:2512 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</" @@ -3259,49 +4379,58 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2449 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2517 msgid "An example of this is:" -msgstr "" +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:2530 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:2531 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:2532 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:2535 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:2536 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:2537 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:2543 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:2547 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 " @@ -3309,46 +4438,49 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2486 -msgid "influence of package in testing" -msgstr "テスト版パッケージへの影響" +#. type: Content of: <chapter><section><section><section><title> +#: pkgs.dbk:2554 +msgid "Influence of package in testing" +msgstr "テスト版 (testing) にあるパッケージへの影響" -# type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2488 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2556 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 </" -"literal> to <literal>testing</literal>, with two exceptions: If the RC-" -"bugginess of the package goes down, it may go in even if it is still RC-" -"buggy. The second exception is if the version of the package in <literal> " -"testing</literal> is out of sync on the different arches: Then any arch " -"might just upgrade to the version of the source package; however, this can " -"happen only if the package was previously forced through, the arch is in " -"fuckedarches, or there was no binary package of that arch present in " -"<literal>unstable </literal> at all during the <literal>testing</literal> " -"migration." +"Generally, there is nothing that the status of a package in " +"<literal>testing</literal> means for transition of the next version from " +"<literal>unstable</literal> to <literal>testing</literal>, with two " +"exceptions: If the RC-bugginess of the package goes down, it may go in even " +"if it is still RC-buggy. The second exception is if the version of the " +"package in <literal>testing</literal> is out of sync on the different " +"arches: Then any arch might just upgrade to the version of the source " +"package; however, this can happen only if the package was previously forced " +"through, the arch is in fuckedarches, or there was no binary package of that " +"arch present in <literal>unstable</literal> at all during the " +"<literal>testing</literal> migration." msgstr "" -# type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2500 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2568 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 " -"version might go in easier." +"In summary this means: The only influence that a package being in " +"<literal>testing</literal> has on a new version of the same package is that " +"the new version might go in easier." msgstr "" -# type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2507 -msgid "details" -msgstr "" +#. type: Content of: <chapter><section><section><section><title> +#: pkgs.dbk:2575 +msgid "Details" +msgstr "詳細について" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2509 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2577 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:2580 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 " @@ -3360,53 +4492,57 @@ msgid "" "the code.)" msgstr "" -# type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2521 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2589 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 " -"valid candidate to the testing distribution. If the number of uninstallable " -"packages in <literal>testing</literal> doesn't increase, the package is " -"accepted. From that point on, the accepted package is considered to be part " -"of <literal>testing</literal>, such that all subsequent installability tests " -"include this package. Hints from the release team are processed before or " -"after this main run, depending on the exact type." +"Now, the more complex part happens: Britney tries to update " +"<literal>testing</literal> with the valid candidates. For that, britney " +"tries to add each valid candidate to the testing distribution. If the number " +"of uninstallable packages in <literal>testing</literal> doesn't increase, " +"the package is accepted. From that point on, the accepted package is " +"considered to be part of <literal>testing</literal>, such that all " +"subsequent installability tests include this package. Hints from the " +"release team are processed before or after this main run, depending on the " +"exact type." msgstr "" -# type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2531 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2599 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/" "testing/update_out</filename> to see a setup with a smaller packages file). " "Via web, it's at <ulink url=\"http://&ftp-master-host;/testing/" -"update_out_code/\"></ulink>" +"update_out_code/\"></ulink>." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2538 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2606 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:2614 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:2616 msgid "" "The <literal>testing</literal> distribution is fed with packages from " "<literal>unstable</literal> according to the rules explained above. " "However, in some cases, it is necessary to upload packages built only for " -"<literal> testing</literal>. For that, you may want to upload to <literal> " -"testing-proposed-updates</literal>." +"<literal>testing</literal>. For that, you may want to upload to " +"<literal>testing-proposed-updates</literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2555 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2623 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 " @@ -3415,68 +4551,73 @@ msgid "" "regularly give on &email-debian-devel-announce;." msgstr "" -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2562 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2630 msgid "" "You should not upload to <literal>testing-proposed-updates</literal> when " "you can update your packages through <literal>unstable</literal>. If you " "can't (for example because you have a newer development version in " -"<literal>unstable </literal>), you may use this facility, but it is " +"<literal>unstable</literal>), you may use this facility, but it is " "recommended that you ask for authorization from the release manager first. " "Even if a package is frozen, updates through <literal>unstable</literal> are " "possible, if the upload via <literal>unstable</literal> does not pull in any " "new dependencies." msgstr "" -# type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2571 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2639 msgid "" "Version numbers are usually selected by adding the codename of the " "<literal>testing</literal> distribution and a running number, like " -"<literal>1.2sarge1</literal> for the first upload through <literal>testing-" +"<literal>1.2squeeze1</literal> for the first upload through <literal>testing-" "proposed-updates</literal> of package version <literal>1.2</literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2578 +#. type: Content of: <chapter><section><section><para> +#: pkgs.dbk:2646 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:2651 msgid "" "Make sure that your package really needs to go through <literal>testing-" -"proposed-updates</literal>, and can't go through <literal> unstable</" -"literal>;" +"proposed-updates</literal>, and can't go through <literal>unstable</literal>;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2590 +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:2658 msgid "Make sure that you included only the minimal amount of changes;" -msgstr "" +msgstr "必ず最小限な量だけの変更を含めるようにする;" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2595 +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:2663 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:2668 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:2674 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:2680 msgid "" "Make sure that your version number is higher than the version in " "<literal>testing</literal> and <literal>testing-proposed-updates</literal>, " @@ -3484,79 +4625,111 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2619 +#. type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: pkgs.dbk:2687 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:2695 msgid "Frequently asked questions" -msgstr "" +msgstr "よく聞かれる質問とその答え (FAQ)" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2629 +#. type: Content of: <chapter><section><section><section><title> +#: pkgs.dbk:2697 msgid "What are release-critical bugs, and how do they get counted?" -msgstr "" +msgstr "リリースクリティカルバグとは何ですか、どうやって数えるのですか?" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2631 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2699 msgid "" "All bugs of some higher severities are by default considered release-" "critical; currently, these are <literal>critical</literal>, <literal>grave</" "literal> and <literal>serious</literal> bugs." msgstr "" +"ある重要度以上のバグすべてが通常リリースクリティカルであると見なされます。現" +"在のところ、<literal>critical (致命的)</literal>、<literal>grave (重大)</" +"literal>、<literal>serious (深刻)</literal> バグがそれにあたります。" -# type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2636 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2704 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 " "general, if a package has open release-critical bugs filed on it, it won't " "get into <literal>testing</literal>, and consequently won't be released in " -"<literal> stable</literal>." +"<literal>stable</literal>." msgstr "" +"そのようなバグは、Debian の <literal>安定版 (stable)</literal> リリース時に、" +"そのパッケージがリリースされる見込みに影響があるものと仮定されます: 一般的" +"に、パッケージでオープンになっているリリースクリティカルバグがある場合、その" +"パッケージは<literal>テスト版 (testing)</literal> に入らず、その結果<literal>" +"安定版 (stable)</literal> ではリリースされません。" -# type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2643 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2711 msgid "" "The <literal>unstable</literal> bug count are all release-critical bugs " "which are marked to apply to <replaceable>package</replaceable>/" -"<replaceable>version </replaceable> combinations that are available in " +"<replaceable>version</replaceable> combinations that are available in " "unstable for a release architecture. The <literal>testing</literal> bug " "count is defined analogously." msgstr "" +"<literal>不安定版 (unstable)</literal> でのバグのカウント数は、リリース対象" +"アーキテクチャの不安定版 (unstable) で利用可能な<replaceable>パッケージ</" +"replaceable>/<replaceable>バージョン</replaceable>の組み合わせに適用されると" +"マークされたすべてのリリースクリティカルバグです。<literal>テスト版 (testing)" +"</literal> のバグのカウント数も同様に定義します。" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2651 +#. type: Content of: <chapter><section><section><section><title> +#: pkgs.dbk:2719 msgid "" "How could installing a package into <literal>testing</literal> possibly " "break other packages?" msgstr "" +"どのようにすれば、他のパッケージを壊す可能性があるパッケージを<literal>テスト" +"版 (testing)</literal> へインストールできますか?" -# type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2654 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2722 msgid "" "The structure of the distribution archives is such that they can only " "contain one version of a package; a package is defined by its name. So when " "the source package <literal>acmefoo</literal> is installed into " "<literal>testing</literal>, along with its binary packages <literal>acme-foo-" -"bin</literal>, <literal> acme-bar-bin</literal>, <literal>libacme-foo1</" -"literal> and <literal> libacme-foo-dev</literal>, the old version is removed." +"bin</literal>, <literal>acme-bar-bin</literal>, <literal>libacme-foo1</" +"literal> and <literal>libacme-foo-dev</literal>, the old version is removed." msgstr "" +"ディストリビューションにおけるアーカイブの構造では、一つのバージョンのパッ" +"ケージだけを持つことができ、パッケージは名前によって定義されています。そのた" +"め、ソースパッケージ <literal>acmefoo</literal> が<literal>テスト版 (testing)" +"</literal> にインストールされると、付随するバイナリパッケージ <literal>acme-" +"foo-bin</literal>、<literal>acme-bar-bin</literal>、<literal>libacme-foo1</" +"literal>、<literal>libacme-foo-dev</literal> の古いバージョンが削除されます。" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2662 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2730 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 " "old <literal>acmefoo</literal> will remove <literal>libacme-foo0</literal>, " "which will break any packages which depend on it." msgstr "" +"しかし、古いバージョンではライブラリに古い soname を含んだ <literal>libacme-" +"foo0</literal> のようなバイナリパッケージを提供しているかもしれません。古い " +"<literal>acmefoo</literal> を削除するのは <literal>libacme-foo0</literal> を" +"削除することになり、これに依存しているパッケージを壊してしまいます。" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2668 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2736 msgid "" "Evidently, this mainly affects packages which provide changing sets of " "binary packages in different versions (in turn, mainly libraries). However, " @@ -3565,7 +4738,8 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2674 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2742 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 " @@ -3579,13 +4753,11 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2685 +#. type: Content of: <chapter><section><section><section><para> +#: pkgs.dbk:2753 msgid "" "If you are having problems with complicated groups of packages like this, " "contact &email-debian-devel; or &email-debian-release; for help." msgstr "" - -# type: Content of: <chapter><section><section><title> -#, fuzzy -#~ msgid "Using the <literal>DELAYED/</literal> queue" -#~ msgstr "<literal>ftp-master</literal> にアップロードする" +"この様に複雑な組み合わせのパッケージで問題がある場合は、&email-debian-devel; " +"あるいは &email-debian-release; に連絡を取って手助けを求めてください。"