-#: pkgs.dbk:1801
-msgid "How to do a NMU"
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1803
-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:1809
-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:1815
-msgid ""
-"A NMU should follow all conventions, written down in this section. For an "
-"upload to testing or unstable, this order of steps is recommended:"
-msgstr ""
-
-# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1821
-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:1828
-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:1835
-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:1845
-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:1853
-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:1860
-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:1869
-msgid ""
-"For the testing distribution, the rules may be changed by the release "
-"managers. Please take additional care, and acknowledge that the usual way "
-"for a package to enter testing is through unstable."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1874
-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:1880
-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>
-#: pkgs.dbk:1885
-msgid ""
-"For the differences for Porters NMUs, please see <xref linkend=\"source-nmu-"
-"when-porter\"/> ."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1889
-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)."
-msgstr ""
-
-# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1896
-msgid "NMU version numbering"
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1898
-msgid ""
-"Whenever you have made a change to a package, no matter how trivial, the "
-"version number needs to change. This enables our packing system to function."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1902
-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>."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1913
-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."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1919
-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'."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1929
-msgid ""
-"If you upload a package to testing or stable, sometimes, you need to fork "
-"the version number tree. For this, version numbers like 1.1-3sarge0.1 could "
-"be used."
-msgstr ""
-
-# type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1936
-msgid "Source NMUs must have a new changelog entry"
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1938
-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:1944
-msgid "By convention, source NMU changelog entries start with the line"
-msgstr ""
+#. 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>
+#: 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:1954
+msgid "Upload fixing only release-critical and important bugs: 5 days"
+msgstr "リリースクリティカルバグや重要なバグの修正のみのアップロード: 5 日"
+
+#. 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:1965
+msgid ""
+"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 ""
+"この値は例に過ぎません。セキュリティ問題を修正するアップロードや、移行を阻む"
+"些細なバグを修正するなど、いくつかのケースでは修正されたパッケージが "
+"<literal>不安定版 (unstable)</literal> にすぐ入るようになるのは望ましいことで"
+"す。"
+
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1971
+msgid ""
+"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 ""
+"時々、リリースマネージャが特定のバグに対して短い delay 日数の NMU を許可を認"
+"めることがあります (7 日より古いリリースクリティカルバグなど)。また、一部のメ"
+"ンテナは <ulink url=\"&url-low-threshold-nmu;\">Low Threshold NMU list</"
+"ulink> に自身を挙げており、遅延なしの NMU アップロードを許可しています。しか"
+"しどのような場合であっても、特にパッチが BTS で以前手に入らなかったり、メンテ"
+"ナが大抵アクティブであるのを知っている場合など、アップロードの前にメンテナに"
+"対して数日与えるのは良い考えです。"
+
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1981
+msgid ""
+"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 ""
+"NMU アップロード後、あなたは自分が導入したであろう問題に責任を持つことになり"
+"ます。パッケージを見張らなければなりません (これを行うには PTS 上のパッケージ"
+"を購読するのが良い方法です)。"
+
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1987
+msgid ""
+"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 ""
+"これは、軽率な NMU を行うための許可証ではありません。明らかにメンテナがアク"
+"ティブで時期を逃さずパッチについて対応している場合や、このドキュメントに書か"
+"れている推奨を無視している場合など、あなたによるアップロードはメンテナと衝突"
+"を起こすでしょう。NMU のメリットについて、自分が行ったことの賢明さを常に弁護"
+"できるようにしておく必要があります。"
+
+#. 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 ""
+"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 ""
+"他の (ソース) アップロード同様、NMU は <filename>debian/changelog</filename> "
+"にそのアップロードで何を変更したのかを示すエントリを追加せねばなりません。エ"
+"ントリの最初の行は、このアップロードが NMU であることを明白に示す必要がありま"
+"す。例えばこうです:"