-#: pkgs.dbk:1863
-msgid "How to do a NMU"
-msgstr "NMU のやり方"
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1865
-msgid ""
-"NMUs which fix important, serious or higher severity bugs are encouraged and "
-"accepted. You should endeavor to reach the current maintainer of the "
-"package; they might be just about to upload a fix for the problem, or have a "
-"better solution."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1871
-msgid ""
-"NMUs should be made to assist a package's maintainer in resolving bugs. "
-"Maintainers should be thankful for that help, and NMUers should respect the "
-"decisions of maintainers, and try to personally help the maintainer by their "
-"work."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1877
-msgid ""
-"A NMU should follow all conventions, written down in this section. For an "
-"upload to <literal>testing</literal> or <literal>unstable</literal>, this "
-"order of steps is recommended:"
-msgstr ""
-
-# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1884
-msgid ""
-"Make sure that the package's bugs that the NMU is meant to address are all "
-"filed in the Debian Bug Tracking System (BTS). If they are not, submit them "
-"immediately."
-msgstr ""
-
-# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1891
-msgid ""
-"Wait a few days for the response from the maintainer. If you don't get any "
-"response, you may want to help them by sending the patch that fixes the "
-"bug. Don't forget to tag the bug with the patch keyword."
-msgstr ""
-
-# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1898
-msgid ""
-"Wait a few more days. If you still haven't got an answer from the "
-"maintainer, send them a mail announcing your intent to NMU the package. "
-"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."
-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."
-msgstr ""
-
-# 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><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><para>
-#: pkgs.dbk:1932
-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>."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1938
-msgid ""
-"For the stable distribution, please take extra care. Of course, the release "
-"managers may also change the rules here. Please verify before you upload "
-"that all your changes are OK for inclusion into the next stable release by "
-"the release manager."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1944
-msgid ""
-"When a security bug is detected, the security team may do an NMU, using "
-"their own rules. Please refer to <xref linkend=\"bug-security\"/> for more "
-"information."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
+#. 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><section><para>
+#: pkgs.dbk:1882
+msgid "Before doing an NMU, consider the following questions:"
+msgstr "NMU を行う前に、以下の質問について考えてください:"
+
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1887
+msgid ""
+"Does your NMU really fix bugs? Fixing cosmetic issues or changing the "
+"packaging style in NMUs is discouraged."
+msgstr ""
+"NMU は本当にバグを修正しますか? NMU では、些細な問題の修正やパッケージ方式"
+"の変更は推奨されません。"
+
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1893
+msgid ""
+"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 ""
+"メンテナに十分な時間を与えましたか? BTS にバグが報告されたのは何時ですか? "
+"一、二週間忙しいことはあり得ないことでは無いです。そのバグはすぐに修正しなけ"
+"ればならないほど重大ですか? それとも、あと数日待てるものですか?"
+
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1900
+msgid ""
+"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 ""
+"その変更にどれくらい自信がありますか? ヒポクラテスの誓いを思い出してください: "
+"「何よりも、害を及ぼすことなかれ」 動かないパッチを当てるよりもパッケージの"
+"重大なバグをそのままオープンな状態にしておく方が良いですし、パッチによって"
+"バグを解決するのではなく隠してしまうかもしれません。自分が 100% 何をしたのか"
+"分かっていないのであれば、他の人からアドバイスをもらうのも良い考えでしょう。"
+"NMU で何かを壊したのであれば、多くの人がとても不幸になるであろうことを覚えて"
+"おいてください。"
+
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1910
+msgid ""
+"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 ""
+"少なくとも BTS で、NMU するのを明確に表明しましたか? 他の手段 (プライベート"
+"なメール、IRC) でメンテナに連絡をとるのも良い考えです。"
+
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: pkgs.dbk:1917
+msgid ""
+"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 ""
+"メンテナがいつも活動的で応答してくれる場合、彼に連絡を取ろうとしましたか? "
+"大概の場合、メンテナ自身が問題に対応して、あなたのパッチをレビューする機会が"
+"与えられる方が好ましいと思われます。これは、NMU をする人が見落としているだろう"
+"潜在的な問題にメンテナは気付くことができるからです。大抵、メンテナが自分で"
+"アップロードする機会が与えられる方が、皆の時間を使うよりも良いやり方です。"
+
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1927
+msgid ""
+"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 ""
+"NMU をする際には、まず NMU をする意図を明確にしておかねばなりません。それから"
+"、BTS へ現在のパッケージと提案する NMU との差分をパッチとして送付する必要が"
+"あります。<systemitem role=\"package\">devscripts</systemitem> パッケージに"
+"ある <command>nmudiff</command> スクリプトが役に立つでしょう。"
+
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1934
+msgid ""
+"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 ""
+"パッチを準備している間、メンテナが利用しているであろうパッケージ固有の慣例に"
+"注意を向けた方がいいでしょう。これを考慮に入れることは、通常のパッケージの"
+"作業工程に対してあなたの変更が入る負担を減らし、それに従って変更が入る可能性を"
+"高めます。パッケージ固有の慣例がある可能性があるので探すと良い場所は、<ulink "
+"url=\"&url-debian-policy;ch-source.html#s-readmesource\"><filename>debian/"
+"README.source</filename></ulink> です。"
+
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1942
+msgid ""
+"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 ""
+"そうするべき十二分な理由が無い限り、メンテナに対応する時間を与えるべきです "
+"(例えば <literal>DELAYED</literal> キューにアップロードすることによってこれを"
+"行います)。以下が delayed キューを使う際のお勧めの値です:"
+
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>