#
msgid ""
msgstr ""
-"Project-Id-Version: developers-reference 3.4.4\n"
+"Project-Id-Version: developers-reference 3.4.5\n"
"POT-Creation-Date: 2011-04-20 21:36-0400\n"
-"PO-Revision-Date: 2011-02-13 15:32+0100\n"
+"PO-Revision-Date: 2011-06-30 06:32+0100\n"
"Last-Translator: Hideki Yamane <henrich@debian.org>\n"
"Language-Team: Debian JP Project <debian-doc@debian.or.jp>\n"
"Language: Japanese\n"
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
#: pkgs.dbk:2369
-#, fuzzy
msgid ""
"The packages on which it depends must either be available in "
"<literal>testing</literal> or they must be accepted into <literal>testing</"
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
#: pkgs.dbk:2388
-#, fuzzy
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 "
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
#: pkgs.dbk:2395
-#, fuzzy
msgid ""
"Sometimes, some packages never enter <literal>testing</literal> because the "
"set of interrelationship is too complicated and cannot be sorted out by the "
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
#: pkgs.dbk:2400
-#, fuzzy
msgid ""
"Some further dependency analysis is shown on <ulink url=\"http://release."
"debian.org/migration/\"></ulink> — but be warned, this page also shows build "
#. FIXME: better rename this file than document rampant professionalism?
#. type: Content of: <chapter><section><section><section><para>
#: pkgs.dbk:2408
-#, fuzzy
msgid ""
"For the <literal>testing</literal> migration script, outdated means: There "
"are different versions in <literal>unstable</literal> for the release "
#. type: Content of: <chapter><section><section><section><para>
#: pkgs.dbk:2442
-#, fuzzy
msgid ""
"The package is out of date on <literal>alpha</literal> in <literal>unstable</"
"literal>, and will not go to <literal>testing</literal>. Removing the "
# type: Content of: <chapter><section><section><section><para>
#. type: Content of: <chapter><section><section><section><para>
#: pkgs.dbk:2448
-#, fuzzy
msgid ""
"However, if ftp-master removes a package in <literal>unstable</literal> "
"(here on <literal>arm</literal>):"
# type: Content of: <chapter><section><section><section><para>
#. type: Content of: <chapter><section><section><section><para>
#: pkgs.dbk:2478
-#, fuzzy
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> "
# type: Content of: <chapter><section><section><section><para>
#. type: Content of: <chapter><section><section><section><para>
#: pkgs.dbk:2483
-#, fuzzy
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 "
# type: Content of: <chapter><section><section><section><para>
#. type: Content of: <chapter><section><section><section><para>
#: pkgs.dbk:2492
-#, fuzzy
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 "
# type: Content of: <chapter><section><section><section><para>
#. type: Content of: <chapter><section><section><section><para>
#: pkgs.dbk:2513
-#, fuzzy
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</"
# type: Content of: <chapter><section><section><section><para>
#. type: Content of: <chapter><section><section><section><para>
#: pkgs.dbk:2544
-#, fuzzy
msgid ""
"Neither package <literal>a</literal> nor package <literal>b</literal> is "
"considered for update."
#. type: Content of: <chapter><section><section><section><para>
#: pkgs.dbk:2557
-#, fuzzy
msgid ""
"Generally, there is nothing that the status of a package in "
"<literal>testing</literal> means for transition of the next version from "
#. type: Content of: <chapter><section><section><section><para>
#: pkgs.dbk:2569
-#, fuzzy
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 "
msgid "If you are interested in details, this is how britney works:"
msgstr "詳細について知りたい場合ですが、britney の動作は以下のようになります:"
-# まだ作業中…
# type: Content of: <chapter><section><section><section><para>
#. type: Content of: <chapter><section><section><section><para>
#: pkgs.dbk:2581
-#, fuzzy
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 "
"キテクチャで古くなりすぎている、というものです。britney のこの部分では、リ"
"リースマネージャーが britney がパッケージを検討できるように様々なサイズのハン"
"マーを使います (それから、base freeze が britney のこの部分のコードに記述され"
-"ています)。(バイナリのみの更新 (binary-only update) について同様ですが、ここ"
-"では記述しません。興味がある場合はコードを分析してください)。"
+"ています)。(バイナリのみの更新 (binary-only update) についても同様ですが、ここ"
+"では記述しません。興味がある場合はコードを解析してください)。"
#. type: Content of: <chapter><section><section><section><para>
#: pkgs.dbk:2590
-#, fuzzy
msgid ""
"Now, the more complex part happens: Britney tries to update "
"<literal>testing</literal> with the valid candidates. For that, britney "
"it will also affect packages upon which versioned dependencies have been "
"declared of the ==, <=, or << varieties."
msgstr ""
+"おそらく、これが主に影響するのは、一群のバイナリパッケージを変更したのを"
+"別バージョンで提供しているパッケージ (つまり、主にライブラリ) でしょう。"
+"しかし、バージョン付きの依存関係が ==、<=、<< などで宣言されている"
+"パッケージにも影響は及ぼします。"
# type: Content of: <chapter><section><section><section><para>
#. type: Content of: <chapter><section><section><section><para>
"manual intervention by the release manager or an assistant is normally "
"required."
msgstr ""
+"一つのソースパッケージによって提供されている一群のバイナリパッケージがこのように"
+"して変更された場合、古いバイナリに依存しているすべてのパッケージは新しいバイナリに"
+"依存するように更新する必要があります。このようなソースパッケージを<literal>テスト"
+"版 (testing)</literal> にインストールすると<literal>テスト版 (testing)</literal> "
+"で依存しているすべてのパッケージを壊すことになるので、ここで注意をする必要があります: "
+"すべての依存しているパッケージを更新し、インストールできるように準備しておくことで"
+"壊されないようにしておき、そして、すべての準備ができたら、通常はリリースマネージャ"
+"あるいはリリースアシスタントによる手動作業が必要になります。"
# type: Content of: <chapter><section><section><section><para>
#. type: Content of: <chapter><section><section><section><para>