#: 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 "
#. 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: bug#<replaceable>nnnnn</replaceable></literal> というエ"
+"め、<literal>Closes: #<replaceable>nnnnn</replaceable></literal> というエ"
"ントリを新規パッケージの changelog 内に含めてください (<xref linkend="
"\"upload-bugfix\"/> を参照)。"
msgid ""
"If you think your package needs some explanations for the administrators of "
"the NEW package queue, include them in your changelog, send to "
-"ftpmaster@debian.org a reply to the email you receive as a maintainer after "
+"&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 パッケージキューの管理者への説明が必要だろうと思う場"
"合は、アップロード後にメンテナとして受け取るメールへの返信、あるいは既に再"
"アップロードという場合は reject のメールに対しての返信として、説明を "
-"changelog に含めて ftpmaster@debian.org へ送ってください。"
+"changelog に含めて &email-ftpmaster; へ送ってください。"
# type: Content of: <chapter><section><para>
#. type: Content of: <chapter><section><para>
#: pkgs.dbk:57
msgid ""
-"When closing security bugs include CVE numbers as well as the Closes: "
-"#nnnnn. This is useful for the security team to track vulnerabilities. If "
+"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 番号を Closes: #nnnnnn と同じく含める"
+"セキュリティバグを閉じる場合は、CVE 番号を <literal>Closes: #<replaceable>nnnnn</replaceable></literal> と同じく含める"
"ようにしてください。これは、セキュリティチームが脆弱性を追跡するのに役立ちま"
"す。アドバイザリの ID が分かる前にバグ修正のためのアップロードが行われた場合"
"は、以前の changelog エントリを次のアップロード時に修正するのが推奨されていま"
"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 "
+"\"/>. 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> ファイルは、幾つもの異なった項目からなる"
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><screen>
#: pkgs.dbk:137
#, no-wrap
-msgid " * new upstream version\n"
-msgstr " * new upstream version\n"
+msgid " * New upstream release.\n"
+msgstr " * New upstream release.\n"
# type: Content of: <chapter><section><para>
#. type: Content of: <chapter><section><para>
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>
#. type: Content of: <chapter><section><para>
#: pkgs.dbk:145
-msgid "See also <xref linkend=\"bpp-debian-changelog\"/> ."
+msgid "See also <xref linkend=\"bpp-debian-changelog\"/>."
msgstr "<xref linkend=\"bpp-debian-changelog\"/> も参照してください。"
# type: Content of: <chapter><section><title>
#: pkgs.dbk:179
msgid ""
"For more information on <command>lintian</command>, see <xref linkend="
-"\"lintian\"/> ."
+"\"lintian\"/>."
msgstr ""
"<command>lintian</command> についての詳細は、<xref linkend=\"lintian\"/> を参"
"照してください。"
"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 ""
"ソースパッケージを違うディレクトリにコピーして展開し、再構築する。これは、"
-"パッケージが外部の既存ファイルに依っているか、.diff.gz ファイル内に含"
+"パッケージが外部の既存ファイルに依っているか、<filename>.diff.gz</filename> ファイル内に含"
"まれているファイルで保存されている権限に依るかどうかをテストします。"
# type: Content of: <chapter><section><title>
#FIXME: control ファイル？コントロールファイル？
msgid ""
"For the native packages, the source package includes a Debian source control "
-"file (<literal>.dsc</literal>) and the source tarball (<literal>.tar.{gz,bz2,"
-"lzma}</literal>). A source package of a non-native package includes a Debian "
-"source control file, the original source tarball (<literal>.orig.tar.{gz,bz2,"
-"lzma}</literal>) and the Debian changes (<literal>.diff.gz</literal> for the "
-"source format “1.0” or <literal>.debian.tar.{gz,bz2,lzma}</literal> for the "
+"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 ファイル "
-"(<literal>.dsc</literal>) とソースコードの tarball (<literal>.tar.{gz,bz2,lzma}"
-"</literal>) を含んでいます。native ではないパッケージのソースパッケージは Debian "
-"のソース control ファイルと、オリジナルのソースコードの tarball (<literal>.orig."
-"tar.{gz,bz2,lzma}</literal>)、そして Debian での変更点 (ソース形式“1.0”は "
-"<literal>.diff.gz</literal>、ソース形式“3.0 (quilt)”は <literal>.debian.tar"
-".{gz,bz2,lzma}</literal>) を含んでいます。"
+"(<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:240
"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> ファイルの最初の行からこの情報を展開し、<literal>."
-"changes</literal> ファイルの <literal>Distribution</literal> 欄に配置します。"
+"changelog</filename> ファイルの最初の行からこの情報を展開し、<filename>."
+"changes</filename> ファイルの <literal>Distribution</literal> 欄に配置します。"
# type: Content of: <chapter><section><para>
#. type: Content of: <chapter><section><para>
#: pkgs.dbk:292
msgid ""
"Actually, there are two other possible distributions: <literal>stable-"
-"security </literal> and <literal>testing-security</literal>, but read <xref "
+"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> で"
+"<literal>stable-security</literal> と <literal>testing-security</literal> で"
"すが、これらについての詳細は <xref linkend=\"bug-security\"/> を読んでくださ"
"い。"
#: pkgs.dbk:407
msgid ""
"For removing packages, please see <ulink url=\"ftp://&ftp-upload-host;"
-"&upload-queue;/README\"/> and the Debian package <xref linkend=\"dcut\"/> ."
+"&upload-queue;/README\"/> and the Debian package <xref linkend=\"dcut\"/>."
msgstr ""
# type: Content of: <chapter><section><section><title>
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 section <xref linkend=\"bug-security\"/>."
msgstr ""
"セキュリティアップロードキュー (<literal>oldstable-security</literal>、"
-"<literal>stable-security </literal> 等) には、セキュリティチームからの事前許"
+"<literal>stable-security</literal> 等) には、セキュリティチームからの事前許"
"可無しにパッケージを<emphasis role=\"strong\">アップロードしないでください</"
"emphasis>。パッケージがチームの要求に完全に合致していない場合、望まれないアッ"
"プロードに対処するために多くの問題が引き起こされたり遅延が生じることになりま"
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 ""
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>を取"
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-"
+"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>123@&bugs-host;</email>)."
+"to send a copy of the mail to <email><replaceable>123</replaceable>@&bugs-host;</email>)."
msgstr ""
"バグに対応する際は、バグについて行った議論がバグの元々の報告者とバグ自身 (例"
-"えば <email>123@&bugs-host;</email>) の両方に送られているのを確認してくださ"
+"えば <email><replaceable>123</replaceable>@&bugs-host;</email>) の両方に送られているのを確認してくださ"
"い。新しくメールを書いていて元々の報告者のメールアドレスを思い出せない場合"
-"は、<email>123-submitter@&bugs-host;</email> というメールアドレスを報告者へ連"
+"は、<email><replaceable>123</replaceable>-submitter@&bugs-host;</email> というメールアドレスを報告者へ連"
"絡するのに使えます。<emphasis>さらに</emphasis>バグのログへあなたのメールを記"
-"録するのにも使えます (これは <email>123@&bugs-host;</email> へメールのコピー"
+"録するのにも使えます (これは <email><replaceable>123</replaceable>@&bugs-host;</email> へメールのコピー"
"を送らなくても済むことを意味しています)。"
# type: Content of: <chapter><section><section><para>
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 "
+"<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\"/> ."
+"linkend=\"upload-bugfix\"/>."
msgstr ""
-"既にバグに対処していた場合 (例えば修正済み)、説明のメッセージを <email>123-"
+"既にバグに対処していた場合 (例えば修正済み)、説明のメッセージを <email><replaceable>123</replaceable>-"
"done@&bugs-host;</email> に送ることで <literal>done</literal> とマークしてお"
"いて (閉じて) ください。パッケージを変更してアップロードすることでバグを修正"
"する場合は、<xref linkend=\"upload-bugfix\"/> に記載されているように自動的に"
#: 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><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="
+"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\"/"
-"> を読んで、<literal>.diff.gz</literal> と <literal>.dsc</literal> ファイルだ"
+"> を読んで、<filename>.diff.gz</filename> と <filename>.dsc</filename> ファイルだ"
"けを送ってください)"
# 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\"/> )"
+"advisories\"/>)"
msgstr ""
"勧告に必要になる情報 (<xref linkend=\"bug-security-advisories\"/> 参照)"
"ください。"
# type: Content of: <chapter><section><section><section><para>
-# FIXME: CVS repository ? VCS?
#. 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> (や公開 CVS "
+"機密を要する場合は、修正を<literal>不安定版 (unstable)</literal> (や公開 VCS "
"リポジトリなどその他どこでも) へ修正をアップロードしないよう、注意してくださ"
"い。コードその物が公開されている場合、変更の詳細を難読化するだけでは十分では"
"なく、皆によって解析され得る (そしてされる) でしょう。"
"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 ""
# type: Content of: <chapter><section><section><section><para>
"you have already used for a previous upload, or one that conflicts with a "
"binNMU. The convention is to append <literal>+</"
"literal><replaceable>codename</replaceable><literal>1</literal>, e.g. "
-"<literal>1:2.4.3-4+etch1</literal>, of course increasing 1 for any "
+"<literal>1:2.4.3-4+lenny1</literal>, of course increasing 1 for any "
"subsequent uploads."
msgstr ""
"<emphasis role=\"strong\">バージョン番号</emphasis>が正しいことを確認する。現"
"バージョン番号を再利用しないように注意してください。そうしないと番号が "
"binNMU と衝突します。<literal>+</literal><replaceable>codename</"
"replaceable><literal>1</literal> を追加するのが通例です。例えば "
-"<literal>1:2.4.3-4+etch1</literal> とします。もちろん 1 はアップロードするご"
+"<literal>1:2.4.3-4+lenny1</literal> とします。もちろん 1 はアップロードするご"
"とに増やします。"
# FIXME: remove " "
"<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 "
+"version, you may upload without upstream source (<literal>dpkg-buildpackage "
"-sd</literal>)."
msgstr ""
"これまでに (以前のセキュリティ更新によって) <literal>security.debian.org</"
"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\"/> )."
+"machine (see <xref linkend=\"server-machines\"/>) or setup a chroot (see "
+"<xref linkend=\"pbuilder\"/> and <xref linkend=\"debootstrap\"/>)."
msgstr ""
# type: Content of: <chapter><section><section><section><title>
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 ""
"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>."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
"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 ""
# type: Content of: <chapter><section><section><title>
"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 ""
# type: Content of: <chapter><section><section><para>
"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\"/> )."
+"same name (see <xref linkend=\"pbuilder\"/>)."
msgstr ""
# 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 ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
#: pkgs.dbk:1762
msgid ""
"Descriptions of several porting tools can be found in <xref linkend=\"tools-"
-"porting\"/> ."
+"porting\"/>."
msgstr ""
# type: Content of: <chapter><section><section><section><title>
"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><title>
#: pkgs.dbk:1998
-msgid "NMUs and debian/changelog"
-msgstr "NMU と debian/changelog"
+msgid "NMUs and <filename>debian/changelog</filename>"
+msgstr "NMU と <filename>debian/changelog</filename>"
#. type: Content of: <chapter><section><section><para>
#: pkgs.dbk:2000
msgid ""
"Just like any other (source) upload, NMUs must add an entry to "
-"<literal>debian/changelog</literal>, telling what has changed with this "
+"<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 ""
"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, "
+"command>. Alioth (see <xref linkend=\"alioth\"/>) provides such tools, "
"amongst others."
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
#: pkgs.dbk:2242
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 ""
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 "
+"<xref linkend=\"ddpo\"/>) with packages one doesn't really care for, and "
"creates a false sense of good maintenance."
msgstr ""
~ianmdlvl / developers-reference.git / blobdiff