path: root/Documentation/pbuilder-doc.ja.po

# pbuilder-doc documentation
# Copyright (C) 2007 Junichi Uekawa
# Junichi Uekawa <dancer@debian.org>, 2007
#
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: xxx\n"
"POT-Creation-Date: 2007-06-17 22:17+0900\n"
"PO-Revision-Date: 2007-06-19 05:28+0900\n"
"Last-Translator: Junichi Uekawa <dancer@debian.org>\n"
"Language-Team: Junichi Uekawa <dancer@debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: utf-8\n"

# type: Attribute 'xml:lang' of: <book>
#: pbuilder-doc.xml:5
msgid "en"
msgstr "ja"

# type: Content of: <book><bookinfo><date>
#: pbuilder-doc.xml:7
msgid "2007-5-27"
msgstr "2007年5月27日"

# type: Content of: <book><bookinfo><title>
#: pbuilder-doc.xml:8
msgid "pbuilder User's Manual"
msgstr "pbuilder 利用マニュアル"

# type: Content of: <book><bookinfo><abbrev>
#: pbuilder-doc.xml:9
msgid "pbuilder-doc"
msgstr "pbuilder-doc"

# type: Content of: <book><bookinfo><subtitle>
#: pbuilder-doc.xml:10
msgid "Usage and operations"
msgstr "利用と操作方法について"

# type: Content of: <book><bookinfo><releaseinfo>
#: pbuilder-doc.xml:11
msgid "documentation in progress"
msgstr "草稿"

# type: Content of: <book><chapter><title>
#: pbuilder-doc.xml:22
msgid "Introducing pbuilder"
msgstr "pbuilder の紹介"

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:24
msgid "Aims of pbuilder"
msgstr "pbuilder の目的"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:26
msgid ""
"<command>pbuilder</command> stands for Personal Builder, and it is an "
"automatic Debian Package Building system for personal development "
"workstation environments.  <command>pbuilder</command> aims to be an easy-to-"
"setup system for auto-building Debian packages inside a clean-room "
"environment, so that it is possible to verify that a package can be built on "
"most Debian installations.  The clean-room environment is achieved through "
"the use of a base chroot image, so that only minimal packages will be "
"installed inside the chroot."
msgstr ""
"<command>pbuilder</command> は Personal Builder の略です。個人的なワークス"
"テーションなどの開発環境で、Debianパッケージをビルドするためのシステムです。"
"<command>pbuilder</command> はパッケージが Debian のインストール環境のほとん"
"どでビルドできることを確認するため、Debianパッケージをクリーンルーム内部で自"
"動にビルドするシステムとして簡単に利用できるようになることを目指しています。"
"クリーンルーム環境は最小限のパッケージを chroot にインストールすることで実現"
"しています。"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:40
msgid ""
"The Debian distribution consists of free software accompanied with source.  "
"The source code within Debian's \"main\" section must build within Debian "
"\"main\", with only the explicitly specified build-dependencies installed."
msgstr ""
"Debian ディストリビューションはソースコードつきのフリーソフトウェアにより構成"
"されています。Debianの「main」セクションにあるソフトウェアは、Build-depend "
"（ビルド時依存関係）として指定されたDebianの「main」セクションにあるパッケー"
"ジのみがインストールされている状態でビルドできなければなりません。"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:48
msgid ""
"The primary aim of <command>pbuilder</command> is different from other auto-"
"building systems in Debian in that its aim is not to try to build as many "
"packages as possible.  It does not try to guess what a package needs, and in "
"most cases it tries the worst choice of all if there is a choice to be made."
msgstr ""
"主なる <command>pbuilder</command> の目的は、他の自動ビルドシステムとは違いま"
"す。それは、パッケージをできるだけビルドできるようなことを目的としていないと"
"ころです。パッケージが何を必要としているのかを想像しようとはしません。また選"
"択が可能であれば、最悪な選択をする場合もあります。"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:56
msgid ""
"In this way, <command>pbuilder</command> tries to ensure that packages "
"tested against <command>pbuilder</command> will build properly in most "
"Debian installations, hopefully resulting in a good overall Debian source-"
"buildability."
msgstr ""
"この方針を採用することで、 <command>pbuilder</command> は、 "
"<command>pbuilder</command> で試験したパッケージはほとんどのDebianがインス"
"トールされた環境でビルドできるように確認することができます。これによって"
"Debian全体としてのソースコードのビルドしやすさの向上を目指しています。"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:63
msgid ""
"The goal of making Debian buildable from source is somewhat accomplished, "
"and has seen good progress.  In the past age of Debian 3.0, there were many "
"problems when building from source.  More recent versions of Debian is much "
"better."
msgstr ""
"Debian をソースからビルドできるようにするという目標はほぼ完了し、よく進捗して"
"います。Debian 3.0の時代ではソースからビルドするのに問題が多数ありましたが、"
"最近のリリースではましになってきています。"

# type: Content of: <book><chapter><title>
#: pbuilder-doc.xml:71
msgid "Using pbuilder"
msgstr "pbuilder を利用する"

# type: Content of: <book><chapter><para>
#: pbuilder-doc.xml:73
msgid ""
"There are several simple commands for operation.  <command>pbuilder create</"
"command>, <command>pbuilder update</command>, and <command>pbuilder build</"
"command> commands are the typical commands used.  Let us look at the "
"commands one by one."
msgstr ""
"操作には、いくつかの簡単なコマンドがあります。<command>pbuilder create</"
"command>、 <command>pbuilder update</command>、そして <command>pbuilder "
"build</command> コマンドがよく使われます。ひとつづつ見ていきましょう。"

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:80
msgid "Creating a base chroot image tar-ball"
msgstr "base chroot イメージの tar 玉の作成"

# type: Content of: <book><chapter><sect1><para><command>
#: pbuilder-doc.xml:82
msgid ""
"<command>pbuilder create</command> will create a base chroot image tar-ball "
"(base.tgz).  All other commands will operate on the resulting base.tgz If "
"the Debian release to be created within chroot is not going to be \"sid"
"\" (which is the default), the distribution code-name needs to be specified "
"with the <command>"
msgstr ""
"<command>pbuilder create</command> はベース chroot イメージの tar 玉を作成し"
"ます。その他のコマンドはこのコマンドで作成されたベース chroot　イメージにたい"
"しての操作になります。chrootで利用するDebianリリースをsid（デフォルト）以外に"
"するのであればディストリビューションのコード名は <command>"

# type: Content of: <book><chapter><sect1><para><command><option>
#: pbuilder-doc.xml:89
msgid "--distribution"
msgstr "--distribution"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:89 pbuilder-doc.xml:156
msgid "</command> command-line option."
msgstr "</command>コマンドラインオプションで指定する必要があります。"

# type: Content of: <book><chapter><sect1><para><footnote><para>
#: pbuilder-doc.xml:94
msgid "debootstrap or cdebootstrap can be chosen"
msgstr "debootstrap か cdebootstrap か選択することができます"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:95
msgid ""
"</footnote> is used to create the bare minimum Debian installation, and then "
"build-essential packages are installed on top of the minimum installation "
"using <command>apt-get</command> inside the chroot."
msgstr ""
"</footnote> はDebianの最小インストールを作成するために利用されます。その上に "
"<command>apt-get</command> コマンドを利用して Build-Essential パッケージが "
"chroot 内部にインストールされます。"

# type: Content of: <book><chapter><sect1><para><footnote>
#: pbuilder-doc.xml:103
msgid ""
"For fuller documentation of command-line options, see the pbuilder.8 manual "
"page.  Some configuration will be required for <filename>/etc/pbuilderrc</"
"filename> for the mirror site <footnote>"
msgstr ""
"さらに詳しいドキュメントは、pbuilder.8 マニュアルページを参照してください。利"
"用するミラーサイトの設定をするために <filename>/etc/pbuilderrc</filename> で"
"いくつか設定が必要になります<footnote>"

# type: Content of: <book><chapter><sect1><para><footnote><para>
#: pbuilder-doc.xml:109
msgid ""
"The mirror site should preferably be a local mirror or a cache server, so as "
"not to overload the public mirrors with a lot of access.  Use of tools such "
"as apt-proxy would be advisable."
msgstr ""
"公開ミラーに多数のアクセス負荷をかけないため、ミラーはローカルミラーであるこ"
"とが望ましいです。apt-proxy などのツールの活用を推奨します。"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:115
msgid ""
"</footnote> to use, and proxy configuration may be required to allow access "
"through HTTP.  See the pbuilderrc.5 manual page for details."
msgstr ""
"</footnote> 、またプロキシの設定もHTTP経由でのアクセスのため、変更の必要があ"
"るでしょう。詳細は pbuilderrc.5 マニュアルページを参照してください。"

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:122
msgid "Updating the base.tgz"
msgstr "base.tgz の更新"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:123
msgid ""
"<command>pbuilder update</command> will update the base.tgz.  It will "
"extract the chroot, invoke <command>apt-get update</command> and "
"<command>apt-get dist-upgrade</command> inside the chroot, and then recreate "
"the base.tgz (the base tar-ball.)"
msgstr ""
"<command>pbuilder update</command> コマンドが base.tgz を更新します。 chroot "
"を展開し、 <command>apt-get update</command> と <command>apt-get dist-"
"upgrade</command> を chroot 内部で実行し、base.tgz （ベースの tar 玉） を作成"
"します。"

# type: Content of: <book><chapter><sect1><para><command>
#: pbuilder-doc.xml:130
msgid ""
"It is possible to switch the distribution which the base.tgz is targeted at "
"at this point.  Specify <command>"
msgstr ""
"この時点で、base.tgz が対象とするディストリビューションを指定することが可能で"
"す。<command>"

# type: Content of: <book><chapter><sect1><para><command><option>
#: pbuilder-doc.xml:132
msgid "--distribution <parameter>sid</parameter>"
msgstr "--distribution <parameter>sid</parameter>"

# type: Content of: <book><chapter><sect1><para><command><option>
#: pbuilder-doc.xml:132
msgid "--override-config"
msgstr "--override-config"

# type: Content of: <book><chapter><sect1><para><footnote>
#: pbuilder-doc.xml:132
msgid "</command> to change the distribution to sid.  <footnote>"
msgstr ""
"</command> を指定すると、ディストリビューションを sid に変更できます。 "
"<footnote>"

# type: Content of: <book><chapter><sect1><para><footnote><para>
#: pbuilder-doc.xml:135
msgid ""
"Only upgrading is supported.  Debian does not generally support downgrading "
"(yet?)."
msgstr ""
"アップグレードしかサポートされていません。Debianはダウングレードをサポートし"
"ていません（現時点では？）。"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:140 pbuilder-doc.xml:172
msgid ""
"For fuller documentation of command-line options, see the pbuilder.8 manual "
"page"
msgstr ""
"コマンドラインオプションの詳細なドキュメントについては、pbuilder.8 マニュアル"
"を参照"

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:145
msgid "Building a package using the base.tgz"
msgstr "base.tgz を利用してパッケージをビルドする"

# type: Content of: <book><chapter><sect1><para><command>
#: pbuilder-doc.xml:147
msgid "To build a package inside the chroot, invoke <command>pbuilder build"
msgstr "chroot 内部でパッケージをビルドするには、 <command>pbuilder build "

# type: Content of: <book><chapter><sect1><para><command><option>
#: pbuilder-doc.xml:148
msgid "whatever.dsc"
msgstr "なんたら.dsc"

# type: Content of: <book><chapter><sect1><para><command>
#: pbuilder-doc.xml:148
msgid ""
"</command>.  <command>pbuilder</command> will extract the base.tgz to a "
"temporary working directory, enter the directory with chroot, satisfy the "
"build-dependencies inside chroot, and build the package.  The built packages "
"will be moved to a directory specified with the <command>"
msgstr ""
"</command>.  <command>pbuilder</command> は base.tgz を一時作業用のディレクト"
"リに展開し、そこに chroot 内部でビルド時の依存関係（Build-Depends) を満たし、"
"パッケージをビルドします。ビルドされてできたパッケージは次のコマンドで指定し"
"たディレクトリに移動されます： <command>"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para><command><option>
#: pbuilder-doc.xml:156 pbuilder-doc.xml:193 pbuilder-doc.xml:233
msgid "--buildresult"
msgstr "--buildresult"

# type: Content of: <book><chapter><sect1><para><command>
#: pbuilder-doc.xml:160 pbuilder-doc.xml:1466
msgid "The <command>"
msgstr "<command>"

# type: Content of: <book><chapter><sect1><para><command><option>
#: pbuilder-doc.xml:160
msgid "--basetgz"
msgstr "--basetgz"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:160
msgid "</command> option can be used to specify which base.tgz to use."
msgstr ""
"</command> オプションでどの base.tgz を利用するべきかを指定することができま"
"す。"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:164
msgid ""
"<command>pbuilder</command> will extract a fresh base chroot image from base."
"tgz. (base.tgz is created with <command>pbuilder create</command>, and "
"updated with <command>pbuilder update</command>).  The chroot is populated "
"with build-dependencies by parsing debian/control and invoking <command>apt-"
"get</command>."
msgstr ""
"<command>pbuilder</command> は base.tgz から新しい\n"
"chroot イメージを展開します。（base.tgz は  <command>pbuilder create</"
"command> で作成され、 <command>pbuilder update</command> で更新されます)。 "
"chroot には Build-Depend関係のパッケージが debian/control を解析して  "
"<command>apt-get</command> を実行することで追加されます。"

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:177
msgid "Facilitating Debian Developers' typing, pdebuild"
msgstr "Debian Developer のタイピングを省略する、pdebuild"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:179
msgid ""
"<command>pdebuild</command> is a little wrapper script that does the most "
"frequent of all tasks.  A Debian Developer may try to do <command>debuild</"
"command>, and build a package, inside a Debian source directory.  "
"<command>pdebuild</command> will allow similar control, and allow package to "
"be built inside the chroot, to check that the current source tree will build "
"happily inside the chroot."
msgstr ""
"<command>pdebuild</command> は、あらゆる操作の中でももっとも頻繁に行われるだ"
"ろう作業を簡略化するためのラッパースクリプトです。Debian Developerは Debian "
"パッケージのソースディレクトリで <command>debuild</command> コマンドをうつこ"
"とでパッケージをビルドします。\n"
"<command>pdebuild</command> は同様の操作をすることで、パッケージを chroot 内"
"部でビルドし、\n"
"現在のツリーが chroot 内部でもビルドすることを確認します。"

# type: Content of: <book><chapter><sect1><para><command>
#: pbuilder-doc.xml:189
msgid ""
"<command>pdebuild</command> calls <command>dpkg-source</command> to build "
"the source packages, and then invokes <command>pbuilder</command> on the "
"resulting source package.  However, unlike debuild, the resulting deb files "
"will be found in the <command>"
msgstr ""
"<command>pdebuild</command> はまず <command>dpkg-source</command> コマンドを"
"起動し、ソースパッケージを作成し、<command>pbuilder</command> をそのソース"
"パッケージに対して実行します。 debuild とは違い、生成されたdeb ファイルは "
"<command>"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:193
msgid "</command> directory."
msgstr "</command> で指定されたディレクトリに生成されます。"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:197
msgid "See the pdebuild.1 manual page for more details."
msgstr "詳細は pdebuild.1 マニュアルページを参照してください。"

# type: Content of: <book><chapter><sect1><para><command>
#: pbuilder-doc.xml:200
msgid ""
"There is a slightly different mode of operation available in "
"<command>pdebuild</command> since version 0.97. <command>pdebuild</command> "
"usually runs <command>debian/rules clean</command> outside of the chroot; "
"however, it is possible to change the behaviour to run it inside the chroot "
"with the <command>"
msgstr ""
" <command>pdebuild</command> 0.97 から一つ違う実行モードが追加されていま"
"す。 \n"
"<command>pdebuild</command> は <command>debian/rules clean</command> chroot "
"外部で実行するのですが、chroot内部で実行するように <command>"

# type: Content of: <book><chapter><sect1><para><option>
#: pbuilder-doc.xml:205 pbuilder-doc.xml:1124
msgid "--use-pdebuild-internal"
msgstr "--use-pdebuild-internal"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:205
msgid ""
"</command>.  It will try to bind mount the working directory inside chroot, "
"and run <command>dpkg-buildpackage</command> inside.  It has the following "
"characteristics, and is not yet the default mode of operation."
msgstr ""
"</command> を指定することができます。\n"
"chroot 内部に作業中のディレクトリをバインドマウントし、 <command>dpkg-"
"buildpackage</command> を内部で実行します。\n"
"以下の特徴があり、まだデフォルトにはなっていません。"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:214
#, fuzzy
msgid ""
"Satisfies build-dependency inside the chroot before creating source "
"package.  (which is a good point that default <command>pdebuild</command> "
"could not do)."
msgstr ""
"ソースパッケージを作成する際に、Build-Depend を chroot 内部で満たします。\n"
"(以前の <command>pdebuild</command> でできなかったよい点です)。"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:219
msgid "The working directory is modified from inside the chroot."
msgstr "作業ディレクトリに chroot 内部から変更を加えられます。"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:223
msgid ""
"Building with <command>pdebuild</command> does not guarantee that it works "
"with <command>pbuilder</command>."
msgstr "<command>pdebuild</command> でビルドできることは <command>pbuilder</command> で必ず動くということが保証されるわけではないです。"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:227
msgid ""
"If making the source package fails, the session using the chroot is wasted "
"(chroot creation takes a bit of time, which should be improved with "
"cowdancer)."
msgstr "ソースパッケージを作るステップ自体が失敗した場合に、その chroot を利用するセッションは無駄に終わります（chroot の作成には時間がかかる、cowdancer 等で改善します。)"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para><command>
#: pbuilder-doc.xml:232
msgid "Does not work in the same manner as it used to; for example, <command>"
msgstr "以前と同じ方法で動作してくれない。たとえば、<command>"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:233
msgid "</command> does not have any effect."
msgstr "</command> がきかない。"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:237
msgid "The build inside chroot is ran with the current user outside chroot."
msgstr "chroot 内部でのビルドは chroot 外部での現在のユーザで実行される。"

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:243
msgid "Configuration Files"
msgstr "設定ファイル"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:245
msgid ""
"It is possible to specify all settings by command-line options. However, for "
"typing convenience, it is possible to use a configuration file."
msgstr ""
"設定をすべてコマンドラインで指定することも可能です。しかし、入力を簡便にする"
"ために、設定ファイルを利用することもできます。"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:250
msgid ""
"<filename>/etc/pbuilderrc</filename> and <filename>${HOME}/.pbuilderrc</"
"filename> are read in when <command>pbuilder</command> is invoked.  The "
"possible options are documented in the pbuilderrc.5 manual page."
msgstr ""
"<filename>/etc/pbuilderrc</filename> と <filename>${HOME}/.pbuilderrc</"
"filename> が <command>pbuilder</command> を実行すると読み込まれます。可能なオ"
"プションについては、 pbuilderrc.5 に解説されています。"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:257
msgid "It is useful to use"
msgstr "別のディストリビューション向けに複数の設定ファイルを活用するためには"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para><command><option>
#: pbuilder-doc.xml:257 pbuilder-doc.xml:672
msgid "--configfile"
msgstr "--configfile"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:257
msgid ""
"option to load up a preset configuration file when switching between "
"configuration files for different distributions."
msgstr "オプションが便利です"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:262
msgid ""
"Please note <filename>${HOME}/.pbuilderrc</filename> supersede system "
"settings.  For example, if you are upgrading from sarge to etch, you may "
"need to adjust some part of your local setting just like new <filename>/usr/"
"share/pbuilder/pbuilderrc</filename>, e.g., \"unset DEBOOTSTRAPOPTS\", to "
"cope with the use of cdebootstrap.  The same care is needed if you edited "
"old system setting in <filename>/etc/pbuilderrc</filename>."
msgstr ""
" <filename>${HOME}/.pbuilderrc</filename> がシステムの設定より優先されること"
"に注意してください。たとえば、 sarge から etch にアップグレードする場合に、自"
"分の設定の一部を <filename>/usr/share/pbuilder/pbuilderrc</filename> にあわせ"
"て変更する必要がある可能性があります。例えば新しいバージョンの cdebootstrap "
"に対応するために \"unset DEBOOTSTRAPOPTS\" を入れる、などの例が考えられます。"
"同じことが、<filename>/etc/pbuilderrc</filename> にシステムの設定を入れている"
"場合には当てはまります。"

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:271
msgid "Building packages as non-root inside the chroot"
msgstr "chroot 内部で root 以外でパッケージをビルドする"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:273
#, fuzzy
msgid ""
"<command>pbuilder</command> requires full root privilege when it is "
"satisfying the build-dependencies, but most packages do not need root "
"privilege to build, or even refused to build when they are built as root.  "
"<command>pbuilder </command> can create a user which is only used inside "
"<command>pbuilder </command> and use that user id when building, and use the "
"<command>fakeroot</command> command when root privilege is required."
msgstr ""
"<command>pbuilder</command> は依存関係を充足させる際には root 権限を必要とし"
"ます、しかしほとんどのパッケージはビルド時に root 権限を必要とはせず、rootで"
"はビルドできないパッケージも一部存在します。<command>pbuilder </command> は "
"<command>pbuilder </command> 内部専用のユーザを作成し、そのユーザIDを利用して"
"ビルドを実行することができます。root権限が必要な時には<command>fakeroot</"
"command> コマンドを利用します。"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:282
msgid ""
"BUILDUSERID configuration option should be set to a value for a user id that "
"does not already exist on the system, so that it is more difficult for "
"packages that are being built with <command>pbuilder</command> to affect the "
"environment outside the chroot.  When BUILDUSERNAME configuration option is "
"also set, <command>pbuilder</command> will use the specified user name and "
"fakeroot for building packages, instead of running as root inside chroot."
msgstr ""
"BUILDUSERID 設定オプションは既存のユーザIDと異なるIDに設定しておきましょう。"
"そうするとパッケージが <command>pbuilder</command> 内部でビルドしている際に、"
"chroot　外部の環境に影響をあたえにくくなります。BUILDUSERNAME が設定されてい"
"る場合、その名前を <command>pbuilder</command> は利用し、 chroot 内部でroot権"
"限で動作する代わりに、fakeroot を利用してパッケージをビルドします。"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:291
msgid ""
"Even when using the fakerooting method, <command>pbuilder</command> will run "
"with root privilege when it is required.  For example, when installing "
"packages to the chroot, <command>pbuilder</command> will run under root "
"privilege."
msgstr ""
"fakeroot の方法を利用している場合でも、<command>pbuilder</command> は root 権"
"限が必要な場面では root 権限で稼働します。例えば、chroot内部にパッケージをイ"
"ンストールする時には<command>pbuilder</command> は root 権限で稼働します。"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:297
msgid ""
"To be able to invoke <command>pbuilder</command> without being root, you "
"need to use user-mode-linux, as explained in <xref linkend=\"pbuilder-uml\"/"
">."
msgstr ""
"<command>pbuilder</command> を root 権限を必要としないで利用する方法について"
"は、  user-mode-linux の利用が必要です。 <xref linkend=\"pbuilder-uml\"/> で"
"説明しています。"

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:303
msgid "Using pbuilder for back-porting"
msgstr "pbuilder をバックポートに活用する"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:305
msgid ""
"<command>pbuilder</command> can be used for back-porting software from the "
"latest Debian distribution to the older stable distribution, by using a "
"chroot that contains an image of the older distribution, and building "
"packages inside the chroot.  There are several points to consider, and due "
"to the following reasons, automatic back-porting is usually not possible, "
"and manual interaction is required:"
msgstr ""
"<command>pbuilder</command> は古いディストリビューションのchroot を作成し、そ"
"こでパッケージをビルドすることで、Debian の最新版のディストリビューションから"
"ソフトウエアをバックポートするのに利用することが可能です。いくつかの点を検討"
"する必要があり、次の理由により全自動でバックポートすることは現実的では無く、"
"手動での作業も必要になるでしょう:"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:316
msgid ""
"The package from the unstable distribution may depend on packages or "
"versions of packages which are only available in unstable.  Thus, it may not "
"be possible to satisfy Build-Depends: on stable (without additional "
"backporting work)."
msgstr ""
"unstableのパッケージが unstable にしかないパッケージや、unstable にしかない"
"バージョンのパッケージに依存している場合がある。つまり、stable では Build-"
"Depends: を充足することができない(さらなるバックポートが必要になる)。"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:323
msgid ""
"The stable distribution may have bugs that have been fixed in unstable which "
"need to be worked around."
msgstr ""
"stable ディストリビューションには unstable で修正しているバグが含まれており、"
"ワークアラウンドが必要になる。"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:326
msgid ""
"The package in the unstable distribution may have problems building even on "
"unstable."
msgstr "unstable のパッケージが unstable 上であってもビルドしない場合がある。"

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:332
msgid "Mass-building packages"
msgstr "パッケージを大量にビルドする"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:334
msgid ""
"<command>pbuilder</command> can be automated, because its operations are non-"
"interactive.  It is possible to run <command>pbuilder</command> through "
"multiple packages non-interactively.  Several such scripts are known to "
"exist.  Junichi Uekawa has been running such a script since 2001, and has "
"been filing bugs on packages that fail the test of <command>pbuilder</"
"command>. There were several problems with auto-building:"
msgstr "<command>pbuilder</command> は操作がインタラクティブではないため、自動的に動かすことができる。<command>pbuilder</command> を複数のパッケージに関して、インタラクティブじゃないように実行することができます。それをするためのスクリプトはいくつか存在します。上川は2001年からそのようなスクリプトを実行し、 <command>pbuilder</command> でビルドできない場合についてバグ報告をしていました。次のような問題が発見されました:"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:345
msgid ""
"Build-Dependencies need to install non-interactively, but some packages are "
"so broken that they cannot install without interaction (like postgresql)."
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:350
msgid ""
"When a library package breaks, or gcc/gcj/g++ breaks, or even bison, a large "
"number of build failures are reported.  (gcj-3.0 which had no \"javac\", "
"bison which got more strict, etc.)"
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:356
msgid "Some people were quite hostile against build failure reports."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:360
msgid ""
"Most of the initial bugs have been resolved in the <command>pbuilder</"
"command> sweep done around 2002, but these transitional problems which "
"affect a large portion of Debian Archive do arise from time to time.  "
"Regression tests have their values."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:366
msgid ""
"A script that was used by Junichi Uekawa is now included in the "
"<command>pbuilder</command> distribution, as <command>pbuildd.sh</command>.  "
"It is available in <filename>/usr/share/doc/pbuilder/examples/pbuildd/</"
"filename> and its configuration is in <filename>/etc/pbuilder/pbuildd-config."
"sh</filename>.  It should be easy enough to set up for people who are used "
"to <command>pbuilder</command>. It has been running for quite a while, and "
"it should be possible to set the application up on your system also.  "
"However, it is a new introduction, and please file bugs to the Debian BTS if "
"you know of possible problems, or improved on the script considerably."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:378
msgid "To set up pbuildd, there are some points to be aware of."
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:382
msgid ""
"A file <filename>./avoidlist</filename> needs to be available with the list "
"of packages to avoid building."
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:385
msgid ""
"It will try building anything, even packages which are not aimed for your "
"architecture."
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:389
msgid ""
"Because you are running random build scripts, it is better to use the "
"fakeroot option of <command>pbuilder</command>, to avoid running the build "
"under root privilege."
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:394
msgid ""
"Because not all builds are guaranteed to finish in a finite time, setting a "
"timeout is probably necessary, or pbuildd may stall with a bad build."
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:400
msgid ""
"Some packages require a lot of disk space, around 2GB seems to be sufficient "
"for the largest packages for the time being.  If you find otherwise, please "
"inform the maintainer of this documentation."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:408
msgid "Auto-backporting scripts"
msgstr "自動バックポートスクリプト"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:410
msgid ""
"There are some people who use <command>pbuilder</command> to automatically "
"back-port a subset of packages to the stable distribution."
msgstr ""
"一部の人は <command>pbuilder</command> を一部のパッケージを自動的に stable "
"ディストリビューションにバックポートするために利用しています。"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:414
msgid ""
"I would like some information on how people are doing it, I would appreciate "
"any feedback or information on how you are doing, or any examples."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:420
msgid "Using pbuilder for automated testing of packages"
msgstr "pbuilder を自動テストに利用する"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:422
msgid ""
"<command>pbuilder</command> can be used for automated testing of packages.  "
"It has the feature of allowing hooks to be placed, and these hooks can try "
"to install packages inside the chroot, or run them, or whatever else that "
"can be done. Some known tests and ideas:"
msgstr ""
"<command>pbuilder</command> は、自動的なテストのために利用することができま"
"す。フックを配置することができ、そのフックは chroot 内部にパッケージをインス"
"トールしたり実行したりその他のいろいろなことを実行することができます。実行可"
"能なテストとアイデアは次です:"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:430
msgid ""
"Automatic install-remove-upgrade-remove-install-purge-upgrade-purge test-"
"suite (distributed as an example, <filename>B91dpkg-i</filename>), or just "
"check that everything installs somewhat (<filename>execute_installtest.sh</"
"filename>)."
msgstr ""
"自動的にインストール・アップグレード・削除・インストール・パージ・アップグ"
"レード・パージするようなテスト(例として、<filename>B91dpkg-i</filename>が配布"
"されています)、もしくは全部インストールできることを確認する"
"(<filename>execute_installtest.sh</filename>)。"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:435
msgid ""
"Automatically running lintian/linda (distributed as an example in <filename>/"
"usr/share/doc/pbuilder/examples/B90linda</filename>)."
msgstr ""
"自動的にlintian/lindaを実行する (例として <filename>/usr/share/doc/pbuilder/"
"examples/B90linda</filename>が配布されている)。"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:439
msgid ""
"Automatic debian-test of the package? The debian-test package has been "
"removed from Debian.  A <command>pbuilder</command> implementation can be "
"found as debian/pbuilder-test directory, implemented through B92test-pkg "
"script."
msgstr ""

# type: Content of: <book><chapter><sect1><para><footnote>
#: pbuilder-doc.xml:446
msgid ""
"To use B92test-pkg script, first, add it to your hook directory.  <footnote>"
msgstr ""

# type: Content of: <book><chapter><sect1><para><footnote><para>
#: pbuilder-doc.xml:448
msgid ""
"It is possible to specify <command>--hookdir /usr/share/doc/pbuilder/"
"examples</command> command-line option to include all example hooks as well."
msgstr ""

# type: Content of: <book><chapter><sect1><para><footnote>
#: pbuilder-doc.xml:451
msgid ""
"</footnote>.  The test files are shell scripts placed in <filename>debian/"
"pbuilder-test/NN_name</filename> (where NN is number) following run-parts "
"standard<footnote>"
msgstr ""

# type: Content of: <book><chapter><sect1><para><footnote><para>
#: pbuilder-doc.xml:456
msgid "See run-parts(8). For example, no '.' in file names!"
msgstr ""
"run-parts(8) を参照してください。例えば、ファイル名に '.' はふくめられませ"
"ん。"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:459
msgid ""
"</footnote> for file names.  After a successful build, packages are first "
"tested for installation and removal, and then each test is ran inside the "
"chroot.  The current directory is the top directory of the source-code.  "
"This means you can expect to be able to use ./debian/ directory from inside "
"your scripts."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:468
msgid "Using pbuilder for testing builds with alternate compilers"
msgstr "pbuilder でその他のコンパイラでのビルドを試験する"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:470
msgid ""
"Most packages are compiled with <command>gcc</command> or <command>g++</"
"command> and using the default compiler version, which was gcc 2.95 for "
"Debian GNU/Linux 3.0 (i386).  However, Debian 3.0 was distributed with other "
"compilers, under package names such as <command>gcc-3.2</command> for gcc "
"compiler version 3.2.  It was therefore possible to try compiling packages "
"against different compiler versions.  <command>pentium-builder</command> "
"provides an infrastructure for using a different compiler for building "
"packages than the default gcc, by providing a wrapper script called gcc "
"which calls the real gcc.  To use <command>pentium-builder</command> in "
"<command>pbuilder</command>, it is possible to set up the following in the "
"configuration:"
msgstr ""

# type: Content of: <book><chapter><sect1><para><screen>
#: pbuilder-doc.xml:484
#, no-wrap
msgid ""
"EXTRAPACKAGES=\"pentium-builder gcc-3.2 g++-3.2\"\n"
"export DEBIAN_BUILDARCH=athlon\n"
"export DEBIAN_BUILDGCCVER=3.2"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:490
msgid ""
"It will instruct <command>pbuilder</command> to install the <command>pentium-"
"builder</command> package and also the GCC 3.2 compiler packages inside the "
"chroot, and set the environment variables required for <command>pentium-"
"builder</command> to function."
msgstr ""

# type: Content of: <book><chapter><title>
#: pbuilder-doc.xml:498
msgid "Using User-mode-linux with pbuilder"
msgstr "user-mode-linux を pbuilder で利用する"

# type: Content of: <book><chapter><para>
#: pbuilder-doc.xml:500
msgid ""
"It is possible to use user-mode-linux by invoking <command>pbuilder-user-"
"mode-linux</command> instead of <command>pbuilder</command>.  "
"<command>pbuilder-user-mode-linux</command> doesn't require root privileges, "
"and it uses the copy-on-write (COW) disk access method of <command>User-mode-"
"linux</command> which typically makes it much faster than the traditional "
"<command>pbuilder</command>."
msgstr ""

# type: Content of: <book><chapter><para>
#: pbuilder-doc.xml:510
msgid ""
"<command>User-mode-linux</command> is a somewhat less proven platform than "
"the standard Unix tools which <command>pbuilder</command> relies on "
"(<command>chroot</command>, <command>tar</command>, and <command>gzip</"
"command>) but mature enough to support <command>pbuilder-user-mode-linux</"
"command> since its version 0.59.  And since then, <command>pbuilder-user-"
"mode-linux</command> has seen a rapid evolution."
msgstr ""

# type: Content of: <book><chapter><para>
#: pbuilder-doc.xml:521
msgid ""
"The configuration of <command>pbuilder-user-mode-linux</command> goes in "
"three steps:"
msgstr ""

# type: Content of: <book><chapter><para><itemizedlist><listitem><para>
#: pbuilder-doc.xml:525
msgid "Configuration of user-mode-linux"
msgstr "user-mode-linux の設定"

# type: Content of: <book><chapter><para><itemizedlist><listitem><para>
#: pbuilder-doc.xml:528
msgid "Configuration of rootstrap"
msgstr "rootstrap の設定"

# type: Content of: <book><chapter><para><itemizedlist><listitem><para>
#: pbuilder-doc.xml:531
msgid "Configuration of pbuilder-uml"
msgstr "pbuilder-uml の設定"

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:536
msgid "Configuring user-mode-linux"
msgstr "user-mode-linux の設定"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:538
msgid ""
"user-mode-linux isn't completely trivial to set up.  It would probably be "
"useful to acquaint yourself with it a bit before attempting to use "
"<command>rootstrap</command> or <command>pbuilder-user-mode-linux</"
"command>.  For details, read <filename>/usr/share/doc/uml-utilities/README."
"Debian</filename> and the <command>user-mode-linux</command> documentation.  "
"(It's in a separate package, user-mode-linux-doc.)"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:548
msgid ""
"<command>user-mode-linux</command> requires the user to be in the uml-net "
"group in order to configure the network unless you are using slirp."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:553
msgid ""
"If you compile your own kernel, you may want to verify that you enable TUN/"
"TAP support, and you might want to consider the SKAS patch."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:559
msgid "Configuring rootstrap"
msgstr "rootstrap の設定"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:561
msgid ""
"<command>rootstrap</command> is a wrapper around debootstrap.  It creates a "
"Debian disk image for use with UML.  To configure rootstrap, there are "
"several requirements."
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:568
msgid "Install the rootstrap package."
msgstr "rootstrap　パッケージをインストールします。"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:572
msgid ""
"TUN/TAP only: add the user to the uml-net group to allow access to the "
"network"
msgstr ""
"TUN/TAPを利用している場合:ユーザを uml-net グループに追加し、ネットワークが利"
"用できるようにします"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para><screen>
#: pbuilder-doc.xml:575
#, no-wrap
msgid "adduser dancer uml-net"
msgstr "adduser dancer uml-net"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:579
msgid ""
"TUN/TAP only: Check that the kernel supports the TUN/TAP interface, or "
"recompile the kernel if necessary."
msgstr ""
"TUN/TAPを利用している場合: カーネルが TUN/TAP インタフェースをサポートしてい"
"ることを確認してください。必要であればカーネルをリビルドしてください。"

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:585
msgid ""
"Set up <filename>/etc/rootstrap/rootstrap.conf</filename>.  For example, if "
"the current host is 192.168.1.2, changing following entries to something "
"like this seems to work."
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para><screen>
#: pbuilder-doc.xml:590
#, no-wrap
msgid ""
"transport=tuntap\n"
"interface=eth0\n"
"gateway=192.168.1.1\n"
"mirror=http://192.168.1.2:8081/debian\n"
"host=192.168.1.198\n"
"uml=192.168.1.199\n"
"netmask=255.255.255.0"
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:598
msgid ""
"Some experimentation with configuration and running <command>rootstrap ~/"
"test.uml</command> to actually test it would be handy."
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:603
msgid ""
"Using slirp requires less configuration.  The default configuration comes "
"with a working example."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:610
msgid "Configuring pbuilder-uml"
msgstr "pbuilder-uml の設定"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:612
msgid "The following needs to happen:"
msgstr ""

# type: Content of: <book><chapter><sect1><para><itemizedlist><listitem><para>
#: pbuilder-doc.xml:615
msgid "Install the pbuilder-uml package."
msgstr ""

# type: Content of: <book><chapter><sect1><para><itemizedlist><listitem><para>
#: pbuilder-doc.xml:619
msgid ""
"Set up the configuration file <filename>/etc/pbuilder/pbuilder-uml.conf</"
"filename> in the following manner. It will be different for slirp."
msgstr ""

# type: Content of: <book><chapter><sect1><para><itemizedlist><listitem><para><screen>
#: pbuilder-doc.xml:623
#, no-wrap
msgid ""
"MY_ETH0=tuntap,,,192.168.1.198\n"
"UML_IP=192.168.1.199\n"
"UML_NETMASK=255.255.255.0\n"
"UML_NETWORK=192.168.1.0\n"
"UML_BROADCAST=255.255.255.255\n"
"UML_GATEWAY=192.168.1.1\n"
"PBUILDER_UML_IMAGE=\"/home/dancer/uml-image\""
msgstr ""

# type: Content of: <book><chapter><sect1><para><itemizedlist><listitem><para>
#: pbuilder-doc.xml:631
msgid "Also, it needs to match the rootstrap configuration."
msgstr ""

# type: Content of: <book><chapter><sect1><para><itemizedlist><listitem><para>
#: pbuilder-doc.xml:636
msgid ""
"Make sure BUILDPLACE is writable by the user.  Change BUILDPLACE in the "
"configuration file to a place where the user has access."
msgstr ""

# type: Content of: <book><chapter><sect1><para><itemizedlist><listitem><para><command>
#: pbuilder-doc.xml:642
msgid "Run <command>pbuilder-user-mode-linux"
msgstr ""

# type: Content of: <book><chapter><sect1><para><itemizedlist><listitem><para><command><option>
#: pbuilder-doc.xml:642
msgid "create --distribution sid"
msgstr ""

# type: Content of: <book><chapter><sect1><para><itemizedlist><listitem><para>
#: pbuilder-doc.xml:642
msgid "</command> to create the image."
msgstr ""

# type: Content of: <book><chapter><sect1><para><itemizedlist><listitem><para>
#: pbuilder-doc.xml:645
msgid "Try running <command>pbuilder-user-mode-linux build</command>."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:651
msgid "Considerations for running pbuilder-user-mode-linux"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:653
msgid ""
"<command>pbuilder-user-mode-linux</command> emulates most of "
"<command>pbuilder</command>, but there are some differences."
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:659
msgid ""
"<command>pbuilder-user-mode-linux</command> does not support all options of "
"<command>pbuilder</command> properly yet. This is a problem, and will be "
"addressed as specific areas are discovered."
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para><command>
#: pbuilder-doc.xml:666
msgid ""
"/tmp is handled differently inside <command>pbuilder-user-mode-linux</"
"command>.  In <command>pbuilder-user-mode-linux</command>, <filename>/tmp</"
"filename> is mounted as tmpfs inside UML, so accessing files under "
"<filename>/tmp</filename> from outside user-mode-linux does not work.  It "
"affects options like <command>"
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:672
msgid ""
"</command>, and when trying to build packages placed under <filename>/tmp</"
"filename>."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:680
msgid "Parallel running of pbuilder-user-mode-linux"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:682
msgid ""
"To run <command>pbuilder-user-mode-linux</command> in parallel on a system, "
"there are a few things to bear in mind."
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:687
msgid ""
"The create and update methods must not be run when a build is in progress, "
"or the COW file will be invalidated."
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:692
msgid ""
"If you are not using slirp, user-mode-linux processes which are running in "
"parallel need to have different IP addresses.  Just trying to run the "
"<command>pbuilder-user-mode-linux</command> several times will result in "
"failure to access the network.  But something like the following will work:"
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para><screen>
#: pbuilder-doc.xml:698
#, no-wrap
msgid ""
"for IP in 102 103 104 105; do\n"
"  xterm -e pbuilder-user-mode-linux build --uml-ip 192.168.0.$IP \\\n"
"    20030107/whizzytex_1.1.1-1.dsc &amp;\n"
"done"
msgstr ""

# type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
#: pbuilder-doc.xml:703
msgid "When using slirp, this problem does not exist."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:709
msgid ""
"Using pbuilder-user-mode-linux as a wrapper script to start up a virtual "
"machine"
msgstr ""

# type: Content of: <book><chapter><sect1><para><command>
#: pbuilder-doc.xml:711
msgid ""
"It is possible to use <command>pbuilder-user-mode-linux</command> for other "
"uses than just building Debian packages.  <command>pbuilder-user-mode-linux"
msgstr ""

# type: Content of: <book><chapter><sect1><para><command><option>
#: pbuilder-doc.xml:715 pbuilder-doc.xml:823
msgid "login"
msgstr ""

# type: Content of: <book><chapter><sect1><para><command>
#: pbuilder-doc.xml:715
msgid ""
"</command> will let a user use a shell inside the user-mode-linux "
"<command>pbuilder</command> base image, and <command>pbuilder-user-mode-linux"
msgstr ""

# type: Content of: <book><chapter><sect1><para><command><option>
#: pbuilder-doc.xml:718
msgid "execute"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:718
msgid "</command> will allow the user to execute a script inside the image."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:722
msgid ""
"You can use the script to install ssh and add a new user, so that it is "
"possible to access inside the user-mode-linux through ssh."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:726
msgid ""
"Note that it is not possible to use a script from <filename>/tmp</filename> "
"due to the way <command>pbuilder-user-mode-linux</command> mounts a tmpfs at "
"<filename>/tmp</filename>."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:732
msgid ""
"The following example script may be useful in starting a sshd inside user-"
"mode-linux."
msgstr ""

# type: Content of: <book><chapter><sect1><screen>
#: pbuilder-doc.xml:736
#, no-wrap
msgid ""
"#!/bin/bash\n"
"\n"
"apt-get install -y ssh xbase-clients xterm\n"
"echo \"enter root password\"\n"
"passwd\n"
"cp /etc/ssh/sshd_config{,-}\n"
"sed 's/X11Forwarding.*/X11Forwarding yes/' /etc/ssh/sshd_config- &gt; /etc/ssh/sshd_config\n"
"\n"
"/etc/init.d/ssh restart\n"
"ifconfig\n"
"echo \"Hit enter to finish\"\n"
"read"
msgstr ""

# type: Content of: <book><chapter><title>
#: pbuilder-doc.xml:752
msgid "Frequently asked questions"
msgstr "FAQ （よくある質問）"

# type: Content of: <book><chapter><para>
#: pbuilder-doc.xml:755
msgid ""
"Here, known problems and frequently asked questions are documented. This "
"portion was initially available in README.Debian file, but moved here."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:760
msgid "pbuilder create fails"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:762
msgid ""
"It often happens that <command>pbuilder</command> cannot create the latest "
"chroot.  Try upgrading <command>pbuilder</command> and debootstrap.  It is "
"currently only possible to create software that handles the past. Future "
"prediction is a feature which may be added later after we have become "
"comfortable with the past."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:769
msgid ""
"There are people who occasionally back port debootstrap to stable versions; "
"hunt for them."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:773
msgid ""
"When there are errors with the debootstrap phase, the debootstrap script "
"needs to be fixed.  <command>pbuilder</command> does not provide a way to "
"work around debootstrap."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:779
msgid "Directories that cannot be bind-mounted"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:781
msgid ""
"Because of the way <command>pbuilder</command> works, there are several "
"directories which cannot be bind-mounted when running <command>pbuilder</"
"command>.  The directories include <filename>/tmp</filename>, <filename>/var/"
"cache/pbuilder</filename>, and system directories such as <filename>/etc</"
"filename> and <filename>/usr</filename>.  The recommendation is to use "
"directories under the user's home directory for bind-mounts."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:792
msgid "Logging in to pbuilder to investigate build failure"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:794
msgid ""
"It is possible to invoke a shell session after a build failure.  Example "
"hook script are provided as <filename>C10shell</filename> and "
"<filename>C11screen</filename> scripts.  C10shell script will start bash "
"inside chroot, and C11screen script will start GNU screen inside the chroot."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:803
msgid "Logging in to pbuilder to modify the environment"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:805
msgid ""
"It is sometimes necessary to modify the chroot environment.  <command>login</"
"command> will remove the contents of the chroot after logout.  It is "
"possible to invoke a shell using hook scripts.  <command>pbuilder update</"
"command> executes 'E' scripts, and a sample for invoking a shell is provided "
"as <filename>C10shell</filename>."
msgstr ""

# type: Content of: <book><chapter><sect1><screen>
#: pbuilder-doc.xml:813
#, no-wrap
msgid ""
"$ mkdir ~/loginhooks\n"
"$ cp C10shell ~/loginhooks/E10shell\n"
"$ sudo pbuilder update --hookdir ~/loginhooks/E10shell"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:818
msgid "It is also possible to add"
msgstr ""

# type: Content of: <book><chapter><sect1><para><option>
#: pbuilder-doc.xml:818
msgid "--save-after-exec"
msgstr "--save-after-exec"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:819
msgid "and/or"
msgstr ""

# type: Content of: <book><chapter><sect1><para><option>
#: pbuilder-doc.xml:819
msgid "--save-after-login"
msgstr "--save-after-login"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:819
msgid ""
"options to the <command>pbuilder login</command> session to accomplish the "
"goal.  It is possible to add the"
msgstr ""

# type: Content of: <book><chapter><sect1><para><option>
#: pbuilder-doc.xml:822
msgid "--uml-login-nocow"
msgstr "--uml-login-nocow"

# type: Content of: <book><chapter><sect1><para><command>
#: pbuilder-doc.xml:822
msgid "option to <command>pbuilder-user-mode-linux"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:823
msgid "</command> session as well."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:828
msgid "Setting BUILDRESULTUID for sudo sessions"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:830
msgid "It is possible to set"
msgstr ""

# type: Content of: <book><chapter><sect1><para><screen>
#: pbuilder-doc.xml:831
#, no-wrap
msgid "BUILDRESULTUID=$SUDO_UID"
msgstr "BUILDRESULTUID=$SUDO_UID"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:831
msgid ""
"in pbuilderrc to set the proper BUILDRESULTUID when using <command>sudo</"
"command>."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:836
msgid "Notes on usage of $TMPDIR"
msgstr "$TMPDIRの使い方について"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:838
msgid ""
"If you are setting $TMPDIR to an unusual value, of other than <filename>/"
"tmp</filename>, you will find that some errors may occur inside the chroot, "
"such as <command>dpkg-source</command> failing."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:842
msgid ""
"There are two options, you may install a hook to create that directory, or "
"set"
msgstr ""

# type: Content of: <book><chapter><sect1><para><screen>
#: pbuilder-doc.xml:844
#, no-wrap
msgid "export TMPDIR=/tmp"
msgstr "export TMPDIR=/tmp"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:845
msgid "in pbuilderrc. Take your pick."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:848
msgid ""
"An example script is provided as <filename>examples/D10tmp</filename> with "
"<command>pbuilder</command>."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:853
msgid ""
"Creating a shortcut for running <command>pbuilder</command> with a specific "
"distribution"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:855
msgid ""
"When working with multiple chroots, it would be nice to work with scripts "
"that reduce the amount of typing.  An example script <filename>pbuilder-"
"distribution.sh</filename> is provided as an example.  Invoking the script "
"as <filename>pbuilder-etch</filename> will invoke <command>pbuilder</"
"command> with a etch chroot."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:864
msgid "Using special apt sources lists, and local packages"
msgstr ""

# type: Content of: <book><chapter><sect1><para><command>
#: pbuilder-doc.xml:866
msgid ""
"If you have some very specialised requirements on your apt setup inside "
"<command>pbuilder</command>, it is possible to specify that through the "
"<command>"
msgstr ""

# type: Content of: <book><chapter><sect1><para><command><option>
#: pbuilder-doc.xml:869
msgid "--othermirror"
msgstr "--othermirror"

# type: Content of: <book><chapter><sect1><para><command>
#: pbuilder-doc.xml:869
msgid "</command> option.  Try something like: <command>"
msgstr ""

# type: Content of: <book><chapter><sect1><para><command><option>
#: pbuilder-doc.xml:872
msgid ""
"--othermirror \"deb http://local/mirror stable main|deb-src http://local/"
"source/repository ./\""
msgstr ""

# type: Content of: <book><chapter><sect1><para><command>
#: pbuilder-doc.xml:875
msgid ""
"To use the local file system instead of HTTP, it is necessary to do bind-"
"mounting.  <command>"
msgstr ""

# type: Content of: <book><chapter><sect1><para><command><option>
#: pbuilder-doc.xml:877
msgid "--bindmounts"
msgstr "--bindmounts"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:877
msgid "</command> is a command-line option useful for such cases."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:881
msgid ""
"It might be convenient to use your built packages from inside the chroot.  "
"It is possible to automate the task with the following configuration.  "
"First, set up pbuilderrc to bindmount your build results directory."
msgstr ""

# type: Content of: <book><chapter><sect1><para><screen>
#: pbuilder-doc.xml:886
#, no-wrap
msgid "BINDMOUNTS=\"/var/cache/pbuilder/result\""
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:890
msgid "Then, add the following hook"
msgstr ""

# type: Content of: <book><chapter><sect1><para><screen>
#: pbuilder-doc.xml:894
#, no-wrap
msgid ""
"# cat /var/cache/pbuilder/hooks/D70results\n"
"#!/bin/sh\n"
"cd /var/cache/pbuilder/result/\n"
"/usr/bin/dpkg-scanpackages . /dev/null &gt; /var/cache/pbuilder/result/Packages\n"
"/usr/bin/apt-get update"
msgstr ""
"# cat /var/cache/pbuilder/hooks/D70results\n"
"#!/bin/sh\n"
"cd /var/cache/pbuilder/result/\n"
"/usr/bin/dpkg-scanpackages . /dev/null &gt; /var/cache/pbuilder/result/Packages\n"
"/usr/bin/apt-get update"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:902
msgid ""
"This way, you can use <filename>deb file:/var/cache/pbuilder/result</"
"filename>"
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:906
msgid ""
"How to get pbuilder to run apt-get update before trying to satisfy build-"
"dependency"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:908
msgid ""
"You can use hook scripts for this.  D scripts are run before satisfying "
"build-dependency."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:918
msgid "Different bash prompts inside pbuilder login"
msgstr "pbuilder login で bash のプロンプトを変更する"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:920
msgid ""
"To make distinguishing bash prompts inside <command>pbuilder</command> "
"easier, it is possible to set environment variables such as PS1 inside "
"<filename>pbuilderrc</filename>"
msgstr ""

# type: Content of: <book><chapter><sect1><para><footnote>
#: pbuilder-doc.xml:926
msgid ""
"With versions of bash more recent than 2.05b-2-15, the value of the "
"debian_chroot variable, if set, is included in the value of PS1 (the Bash "
"prompt)  inside the chroot.  In prior versions of bash,<footnote>"
msgstr ""

# type: Content of: <book><chapter><sect1><para><footnote><para>
#: pbuilder-doc.xml:931
msgid "Versions of bash from and before Debian 3.0"
msgstr "Debian 3.0 以前のbash "

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:932
msgid "</footnote> setting PS1 in pbuilderrc worked."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:935
msgid "example of debian_chroot"
msgstr ""

# type: Content of: <book><chapter><sect1><screen>
#: pbuilder-doc.xml:937
#, no-wrap
msgid "export debian_chroot=\"pbuild$$\""
msgstr "export debian_chroot=\"pbuild$$\""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:939
msgid "example of PS1"
msgstr ""

# type: Content of: <book><chapter><sect1><screen>
#: pbuilder-doc.xml:941
#, no-wrap
msgid "export PS1=\"pbuild chroot 32165 # \""
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:945
msgid "Creating a chroot reminder"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:947
msgid ""
"Bash prompts will help you remember that you are inside a chroot.  There are "
"other cases where you may want other signs of being inside a chroot.  Check "
"out the <filename>examples/F90chrootmemo</filename> hook script.  It will "
"create a file called <filename>/CHROOT</filename> inside your chroot."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:956
msgid "Using /var/cache/apt/archives for the package cache"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:958
msgid ""
"For the help of low-bandwidth systems, it is possible to use <filename>/var/"
"cache/apt/archives</filename> as the package cache.  Just specify it instead "
"of the default <filename>/var/cache/pbuilder/aptcache</filename>."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:964
msgid ""
"It is however not possible to do so currently with the user-mode-linux "
"version of <command>pbuilder</command>, because <filename>/var/cache/apt/"
"archives</filename> is usually only writable by root."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:970
msgid ""
"Use of dedicated tools such as apt-proxy is recommended, since caching of "
"packages would benefit the system outside the scope of <command>pbuilder</"
"command>."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:976
msgid "pbuilder back ported to stable Debian releases"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:978
msgid "Currently stable back port of pbuilder is avialable at backports.org."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:982
msgid "Warning about LOGNAME not being defined"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:984
msgid ""
"You might see a lot of warning messages when running <command>pbuilder</"
"command>."
msgstr ""

# type: Content of: <book><chapter><sect1><para><screen>
#: pbuilder-doc.xml:988
#, no-wrap
msgid "dpkg-genchanges: warning: no utmp entry available and LOGNAME not defined; using uid of process (1234)"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:992
msgid ""
"It is currently safe to ignore this warning message.  Please report back if "
"you find any problem with having LOGNAME unset.  Setting LOGNAME caused a "
"few problems when invoking <command>chroot</command>. For example, dpkg "
"requires getpwnam to succeed inside chroot, which means LOGNAME and the "
"related user information have to be set up inside chroot."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1001
msgid "Cannot Build-conflict against an essential package"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1003
msgid ""
"<command>pbuilder</command> does not currently allow Build-Conflicts against "
"essential packages.  It should be obvious that essential packages should not "
"be removed from a working Debian system, and a source package should not try "
"to force removal of such packages on people building the package."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1012
msgid "Avoiding the \"ln: Invalid cross-device link\" message"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1014
msgid ""
"By default, <command>pbuilder</command> uses hard links to manage the "
"<command>pbuilder</command> package cache.  It is not possible to make hard "
"links across different devices; and thus this error will occur, depending on "
"your set up.  If this happens, set"
msgstr ""

# type: Content of: <book><chapter><sect1><para><screen>
#: pbuilder-doc.xml:1018 pbuilder-doc.xml:1172
#, no-wrap
msgid "APTCACHEHARDLINK=no"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1018
msgid "in your pbuilderrc file."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1023
msgid "Using fakechroot"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1025
msgid ""
"It is possible to use <command>fakechroot</command> instead of being root to "
"run <command>pbuilder</command>; however, several things make this "
"impractical.  <command>fakechroot</command> overrides library loads and "
"tries to override default libc functions when providing the functionality of "
"virtual <command>chroot</command>.  However, some binaries do no use libc to "
"function, or override the overriding provided by <command>fakechroot</"
"command>.  One example is <command>ldd</command>.  Inside "
"<command>fakechroot</command>, <command>ldd</command> will check the library "
"dependency outside of the chroot, which is not the expected behaviour."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1039
msgid "To work around the problem, debootstrap has a"
msgstr ""

# type: Content of: <book><chapter><sect1><para><option>
#: pbuilder-doc.xml:1040
msgid "--variant fakechroot"
msgstr "--variant fakechroot"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1040
msgid "option.  Use that, so that ldd and ldconfig are overridden."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1044
msgid ""
"Make sure you have set your LD_PRELOAD path correctly, as described in the "
"fakechroot manpage."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1049
msgid "Using debconf inside pbuilder sessions"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1051
msgid ""
"To use debconf inside <command>pbuilder</command>, setting DEBIAN_FRONTEND "
"to <quote>readline</quote> in <filename>pbuilderrc</filename> should work.  "
"Setting it to <quote>dialog</quote> should also work, but make sure whiptail "
"or dialog is installed inside the chroot."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1058
msgid "nodev mount options hinder pbuilder activity"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1060
msgid ""
"If you see messages such as this when building a chroot, you are mounting "
"the file system with the nodev option."
msgstr ""

# type: Content of: <book><chapter><sect1><screen>
#: pbuilder-doc.xml:1064
#, no-wrap
msgid "/var/lib/dpkg/info/base-files.postinst: /dev/null: Permission denied"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1067
msgid ""
"You will also have problems if you mount the file system with the noexec "
"option, or nosuid.  Make sure you do not have these flags set when mounting "
"the file system for <filename>/var/cache/pbuilder</filename> or $BUILDPLACE."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1073
msgid "This is not a problem when using <command>user-mode-linux</command>."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1076
msgid ""
"See <ulink url=\"http://bugs.debian.org/316135\"> 316135 </ulink> for "
"example."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1082
msgid "pbuilder is slow"
msgstr "pbuilder が遅い"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1084
msgid ""
"<command>pbuilder</command> is often slow. The slowest part of "
"<command>pbuilder</command> is extracting the tar.gz every time "
"<command>pbuilder</command> is invoked. That can be avoided by using "
"<command>pbuilder-user-mode-linux</command>.  <command>pbuilder-user-mode-"
"linux</command> uses COW file system, and thus does not need to clean up and "
"recreate the root file system."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1093
msgid ""
"<command>pbuilder-user-mode-linux</command> is slower in executing the "
"actual build system, due to the usual <command>user-mode-linux</command> "
"overhead for system calls. It is more friendly to the hard drive."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1099
msgid ""
"<command>pbuilder</command> with cowdancer is also an alternative that "
"improves speed of pbuilder startup."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1104
msgid "Using pdebuild to sponsor package"
msgstr ""

# type: Content of: <book><chapter><sect1><para><command>
#: pbuilder-doc.xml:1106
msgid ""
"To sign a package marking for sponsorship, it is possible to use<command>"
msgstr ""

# type: Content of: <book><chapter><sect1><screen><command><option>
#: pbuilder-doc.xml:1107 pbuilder-doc.xml:1112
msgid "--auto-debsign"
msgstr ""

# type: Content of: <book><chapter><sect1><para><command>
#: pbuilder-doc.xml:1107
msgid "</command> and <command>"
msgstr ""

# type: Content of: <book><chapter><sect1><screen><command><option>
#: pbuilder-doc.xml:1108 pbuilder-doc.xml:1112
msgid "--debsign-k"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1108
msgid "</command> options of <command>pdebuild</command>."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1116
msgid "Why is there a source.changes file in ../?"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1118
msgid ""
"When running <command>pdebuild</command>, <command>pbuilder</command> will "
"run dpkg-buildpackage to create a Debian source package to pass it on to "
"<command>pbuilder</command>.  File named XXXX_YYY_source.changes is what "
"remains from that process.  It is harmless unless you try to upload it to "
"the Debian archive."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1124
msgid "This behaviour is different when running through"
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1128
msgid "amd64 and i386-mode"
msgstr ""

# type: Content of: <book><chapter><sect1><para><command>
#: pbuilder-doc.xml:1130
msgid ""
"amd64 architectures are capable of running binaries in i386 mode.  It is "
"possible to use <command>pbuilder</command> to run packages, using "
"<command>linux32</command> and <command>debootstrap"
msgstr ""

# type: Content of: <book><chapter><sect1><para><command><option>
#: pbuilder-doc.xml:1133
msgid "--arch"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1133
msgid ""
"</command> option.  Specifically, a command-line option like the following "
"will work."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1146
msgid "How to use ccache"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1148
msgid ""
"To use <command>ccache</command> with <command>pbuilder</command>, use the "
"following for configuration.  Note that the directory used for CCACHE_DIR "
"needs to exist, and be writable by user within <command>chroot</command>.  "
"The default user within <command>chroot</command> is"
msgstr ""

# type: Content of: <book><chapter><sect1><para><screen>
#: pbuilder-doc.xml:1152
#, no-wrap
msgid "uid=1234"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1152 pbuilder-doc.xml:1172
msgid "."
msgstr ""

# type: Content of: <book><chapter><sect1><screen>
#: pbuilder-doc.xml:1155
#, no-wrap
msgid ""
"export CCACHE_DIR=\"/var/cache/pbuilder/ccache\"\n"
"export PATH=\"/usr/lib/ccache:${PATH}\"\n"
"\n"
"EXTRAPACKAGES=ccache\n"
"BINDMOUNTS=\"${CCACHE_DIR}\""
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1167
msgid "Using tmpfs for buildplace"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1169
msgid ""
"To improve speed of operation, it is possible to use tmpfs for pbuilder "
"build location.  Mount tmpfs to <filename>/var/cache/pbuilder/build</"
"filename>, and set"
msgstr ""

# type: Content of: <book><chapter><title>
#: pbuilder-doc.xml:1179
msgid "Troubleshooting and development"
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1181
msgid "Reporting bugs"
msgstr ""

# type: Content of: <book><chapter><sect1><para><command>
#: pbuilder-doc.xml:1183
msgid ""
"To report bugs, it would be important to have a log of what's going wrong.  "
"Most of the time, adding a <command>"
msgstr ""

# type: Content of: <book><chapter><sect1><para><command><option>
#: pbuilder-doc.xml:1185
msgid "--debug"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1185
msgid ""
"</command> option and re-running the session should do the trick.  Please "
"send the log of such session along with your problem to ease the debugging "
"process."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1192
msgid "Mailing list"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1194
msgid ""
"There is a mailing list for <command>pbuilder</command> on alioth (pbuilder-"
"maint@lists.alioth.debian.org).  You can subscribe through the alioth web "
"interface.  <ulink url=\"http://alioth.debian.org/mail/?group_id=30778\"> "
"http://alioth.debian.org/mail/?group_id=30778</ulink>."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1202
msgid "IRC Channel"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1204
msgid ""
"For coordination and communication, IRC channel #pbuilder on irc.oftc.net is "
"used.  Please log your intent there when you are going to start doing some "
"changes and committing some change."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1211
msgid "Information for pbuilder developers"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1213
msgid ""
"This section tries to document current development practices and how things "
"generally operate in development."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1217
msgid ""
"<command>pbuilder</command> is co-maintained with resources provided by "
"Alioth.  There is an Alioth project page at <ulink url=\"http://alioth."
"debian.org/projects/pbuilder\"> http://alioth.debian.org/projects/pbuilder</"
"ulink>.  Home page is also available, at <ulink url=\"http://pbuilder.alioth."
"debian.org/\"> http://alioth.debian.org/projects/pbuilder</ulink> which "
"shows this text.  git repository is available through http, git, or (if you "
"have an account on alioth, ) ssh."
msgstr ""

# type: Content of: <book><chapter><sect1><screen>
#: pbuilder-doc.xml:1231
#, no-wrap
msgid ""
"git-clone git://git.debian.org/git/pbuilder/pbuilder.git\n"
"git-clone http://git.debian.org/git/pbuilder/pbuilder.git\n"
"git-clone ssh://git.debian.org/git/pbuilder/pbuilder.git"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1236
msgid ""
"Test-suites are available in <filename>./testsuite/</filename> directory.  "
"Changes are expected not to break the test-suites.  <filename>./run-test.sh</"
"filename> is a basic test-suite, which puts a summary in <filename>run-test."
"log</filename>, and <filename>run-test-cdebootstrap.log</filename>.  "
"<filename>./run-test-regression.sh</filename> is a regression test-suite, "
"which puts the result in <filename>run-test-regression.log</filename>.  "
"Currently, run-test.sh is ran automatically daily to ensure that pbuilder is "
"working."
msgstr ""

# type: Content of: <book><chapter><sect1><table><title>
#: pbuilder-doc.xml:1245
msgid "Directory structure of the testsuite"
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><thead><row><entry>
#: pbuilder-doc.xml:1251 pbuilder-doc.xml:1511 pbuilder-doc.xml:1575
msgid "Directory"
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><thead><row><entry>
#: pbuilder-doc.xml:1252 pbuilder-doc.xml:1512 pbuilder-doc.xml:1576
msgid "Meaning"
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1258
msgid "Directory for testsuite"
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1262
msgid ""
"Daily regression test to test against Debian Archive changes breaking "
"pbuilder."
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1266
msgid "A summary of testsuite"
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1270
msgid "Directory for testsuite results of running pbuilder with debootstrap"
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1274
msgid "Directory for testsuite results of running pbuilder with cdebootstrap"
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1278
msgid ""
"Regression testsuite, ran every time change is made to pbuilder to make sure "
"there is no regression."
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1282
msgid "Summary of test result"
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1286
msgid "Regression tests, exit 0 for success, exit 1 for failure"
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1290
msgid "Files used for the regression testsuite."
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1294
msgid ""
"Output of the regression test, output from the script is redirected by run-"
"regression.sh"
msgstr ""

# type: Content of: <book><chapter><sect1><para><footnote>
#: pbuilder-doc.xml:1300
msgid ""
"When making changes, a description of the change targeted at developers "
"should be documented in <filename>ChangeLog</filename><footnote>"
msgstr ""

# type: Content of: <book><chapter><sect1><para><footnote><para>
#: pbuilder-doc.xml:1303
msgid "ChangeLog is edited using emacs ChangeLog mode."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1304
msgid ""
"</footnote>, and committed.  A brief summary of the change targeting end "
"users should be documented in <filename>debian/changelog</filename>, so that "
"users can see them.  It is important to note that the description of "
"<filename>debian/changelog</filename> is targeted at users, and "
"<filename>ChangeLog</filename> is targeted at developers.  For git commit "
"messages, a cut-n-paste of <filename>ChangeLog</filename> diff should be "
"enough."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1317
msgid ""
"A TODO file is available in <filename>debian/TODO</filename>.  It's mostly "
"not well-maintained, but hopefully it will be more up-to-date when people "
"start using it.  emacs todoo-mode is used in editing the file."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1323
msgid ""
"When releasing a new version of <command>pbuilder</command>, the version is "
"tagged with the git tag X.XXX (version number).  This is done with "
"<command>./git-tag.sh</command> script available in the source tree."
msgstr ""

# type: Content of: <book><chapter><title>
#: pbuilder-doc.xml:1331
msgid "Other uses of pbuilder"
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1333
msgid "Using pbuilder for small experiments"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1335
msgid ""
"There are cases when some small experimenting is required, and you do not "
"want to damage the main system, like when installing experimental library "
"packages, or compiling with experimental compilers.  For such cases, the "
"<command>pbuilder login</command> command is available."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1342
msgid ""
"<command>pbuilder login </command> is a debugging feature for "
"<command>pbuilder</command> itself, but it also allows users to have a "
"temporary chroot."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1346
msgid ""
"Note that the chroot is cleaned after logging out of the shell, and mounting "
"file systems inside it is considered harmful."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1351
msgid "Running little programs inside the chroot"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1353
msgid ""
"To facilitate using <command>pbuilder</command> for other uses, "
"<command>pbuilder execute</command> is available.  <command>pbuilder execute "
"</command> will take a script specified in the command-line argument, and "
"invoke the script inside the chroot."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1360
msgid ""
"The script can be useful for sequences of operations such as installing ssh "
"and adding a new user inside the chroot."
msgstr ""

# type: Content of: <book><chapter><title>
#: pbuilder-doc.xml:1366
msgid "Experimental or wish-list features of pbuilder"
msgstr ""

# type: Content of: <book><chapter><para>
#: pbuilder-doc.xml:1368
msgid ""
"There are some advanced features, above that of the basic feature of "
"<command>pbuilder</command>, for some specific purposes."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1372
msgid "Using LVM"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1374
msgid ""
"LVM2 has a useful snapshot function that features Copy-on-write images.  "
"That could be used for <command>pbuilder</command> just as it can be used "
"for the user-mode-linux <command>pbuilder</command> port.  It may prove to "
"be faster, but it is not implemented yet, and so no measurement has been "
"made, yet."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1381
msgid ""
"<command>User-mode-linux</command> cow support has been preferred for "
"<command>pbuilder-user-mode-linux</command>, but the idea of using LVM is "
"interesting."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1387
msgid "Using cowdancer"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1389
msgid ""
"<command>cowdancer</command> allows copy-on-write semantics on file system "
"using hard links and hard-link-breaking-on-write tricks.  <command>pbuilder</"
"command> using <command>cowdancer</command> seems to be much faster and it "
"is one ideal point for improvement.  <command>cowbuilder</command>, a "
"wrapper for <command>pbuilder</command> for using <command>cowdancer</"
"command> is available from <command>cowdancer</command> package since 0.14"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1400
msgid "Example command-lines for cowbuilder look like the following."
msgstr ""

# type: Content of: <book><chapter><sect1><para><screen>
#: pbuilder-doc.xml:1404
#, no-wrap
msgid ""
"# cowbuilder --create --distribution sid\n"
"# cowbuilder --update --distribution sid\n"
"# cowbuilder --build XXX.dsc"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1410
msgid ""
"It is also possible to use cowdancer with pdebuild command.  Specify with "
"command-line option"
msgstr ""

# type: Content of: <book><chapter><sect1><para><option>
#: pbuilder-doc.xml:1411
msgid "--pbuilder"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1412
msgid "or set it in PDEBUILD_PBUILDER configuration option."
msgstr ""

# type: Content of: <book><chapter><sect1><para><screen>
#: pbuilder-doc.xml:1416
#, no-wrap
msgid "$ pdebuild --pbuilder cowbuilder"
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><title>
#: pbuilder-doc.xml:1420
msgid "Using cowdancer for sarge"
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><para>
#: pbuilder-doc.xml:1422
msgid ""
"This section is mostly obsolete now that etch is released, but left for "
"reference, and will be removed after lenny release."
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><para>
#: pbuilder-doc.xml:1427
msgid ""
"cowdancer was introduced after the release of Debian sarge; if you want to "
"build packages for sarge with cowbuilder, you will need to workaround its "
"unavailability."
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><para>
#: pbuilder-doc.xml:1432
msgid ""
"One way to workaround the problem is to set APTCONFDIR in pbuilderrc to "
"point to a directory with a list of sources for APT which has both sarge and "
"sarge-backports."
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><para><screen>
#: pbuilder-doc.xml:1438
#, no-wrap
msgid ""
"$ cat sources.list\n"
"# sarge-backports\n"
"deb     http://www.backports.org/debian sarge-backports main\n"
"deb-src http://www.backports.org/debian sarge-backports main\n"
"\n"
"# sarge\n"
"deb     http://ftp.de.debian.org/debian sarge main\n"
"deb-src http://ftp.de.debian.org/debian sarge main"
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><para>
#: pbuilder-doc.xml:1449
msgid ""
"It is recommended to \"Pin\" the cowdancer package appropriately in this "
"case, via the APT preferences mechanism."
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><para><screen>
#: pbuilder-doc.xml:1454
#, no-wrap
msgid ""
"$ cat preferences\n"
"Explanation: use cowdancer from backports\n"
"Package: cowdancer\n"
"Pin: release a=sarge-backports\n"
"Pin-Priority: 950"
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1464
msgid "Using pbuilder without tar.gz"
msgstr "tar.gz を利用しないで pbuilder を利用する"

# type: Content of: <book><chapter><sect1><para><command><option>
#: pbuilder-doc.xml:1466
msgid "--no-targz"
msgstr "--no-targz"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1466
msgid ""
"</command> option of <command>pbuilder</command> will allow usage of "
"<command>pbuilder</command> in a different way from conventional usage.  It "
"will try to use an existing chroot, and will not try to clean up after "
"working on it.  It is an operation mode more like <command>sbuild</command>."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1477
msgid ""
"It should be possible to create base chroot images for <command>dchroot</"
"command> with the following commands:"
msgstr ""

# type: Content of: <book><chapter><sect1><para><screen>
#: pbuilder-doc.xml:1480
#, no-wrap
msgid ""
"# pbuilder create --distribution etch --no-targz --basetgz /chroot/etch\n"
"# pbuilder create --distribution lenny --no-targz --basetgz /chroot/lenny\n"
"# pbuilder create --distribution sid --no-targz --basetgz /chroot/sid"
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1487
msgid "Using pbuilder in a vserver"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1489
msgid ""
"It is possible to use <command>pbuilder</command> in a vserver environment.  "
"This requires either vserver-patches in version 2.1.1-rc14 or higher, or a "
"Linux kernel version 2.6.16 or higher."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1494
msgid ""
"To use <command>pbuilder</command> in a vserver, you need to set the "
"<command>secure_mount</command> <command>CAPS</command> in the "
"<command>ccapabilities</command> of this vserver."
msgstr ""

# type: Content of: <book><chapter><title>
#: pbuilder-doc.xml:1501
msgid "Reference materials"
msgstr "参考文献"

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1503
msgid "Directory structure outside the chroot"
msgstr "chroot 外部のディレクトリ構造"

# type: Content of: <book><chapter><sect1><table><title>
#: pbuilder-doc.xml:1505
msgid "Directory Structure outside the chroot"
msgstr "chroot 内部のディレクトリ構造"

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1518
msgid "configuration file"
msgstr "設定ファイル"

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1522
msgid "Default configuration"
msgstr "デフォルト設定"

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1526
msgid ""
"Default location pbuilder uses for base.tgz, the tar-ball containing a basic "
"Debian installation with only the build-essential packages."
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1532
msgid "Default location pbuilder uses for chroot"
msgstr "pbuilder がデフォルトでchroot のために利用する場所"

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1536
msgid ""
"Default location <command>pbuilder</command> will use as apt cache, to store "
"deb packages required during <command>pbuilder</command> build."
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1540
msgid ""
"Default location <command>pbuilder</command> puts the deb files and other "
"files created after build"
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1544
msgid ""
"Default location <command>pbuilder-user-mode-linux</command> puts the deb "
"files and other files created after build"
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1548
msgid ""
"Default location <command>pbuilder-user-mode-linux</command> uses for "
"mounting the COW file system, for chrooting."
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1552
msgid "<command>pbuilder-user-mode-linux</command> will mount tmpfs for work."
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1556
msgid ""
"<command>pbuilder-user-mode-linux</command> use this directory for location "
"of COW file system."
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1560
msgid ""
"<command>pbuilder-user-mode-linux</command> use this directory for user-mode-"
"linux full disk image."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1567
msgid "Directory structure inside the chroot"
msgstr "chroot 内部のディレクトリ構造"

# type: Content of: <book><chapter><sect1><table><title>
#: pbuilder-doc.xml:1569
msgid "Directory Structure inside the chroot"
msgstr "chroot 内部のディレクトリ構造"

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1583
msgid "symlink to <filename>/proc/mounts</filename>."
msgstr " <filename>/proc/mounts</filename>へのシンボリックリンク。"

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1588
msgid ""
"Default place used in <command>pbuilder</command> to place the Debian "
"package to be processed.  <filename>/tmp/buildd/packagename-version/</"
"filename> will be the root directory of the package being processed.  HOME "
"environment variable is set to this value inside chroot by pbuilder-"
"buildpackage"
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1598
msgid ""
"The script passed as an argument to <command>pbuilder</command> execute is "
"passed on."
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1606
msgid "The location of hooks."
msgstr "フックの場所。"

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1612
msgid ""
"<command>pbuilder</command> copies the content of this directory to and from "
"the aptcache directory of outside chroot."
msgstr ""

# type: Content of: <book><chapter><sect1><table><tgroup><tbody><row><entry>
#: pbuilder-doc.xml:1618
msgid ""
"<command>pbuilder-user-mode-linux</command> uses a script in <filename>/tmp</"
"filename> to bootstrap into user-mode-linux"
msgstr ""

# type: Content of: <book><chapter><title>
#: pbuilder-doc.xml:1628
msgid "Minor archaeological details"
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1630
msgid "Documentation history"
msgstr "マニュアルの履歴"

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1632
msgid ""
"This document was started on 28 Dec 2002 by Junichi Uekawa, trying to "
"document what is known about <command>pbuilder</command>."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1637
msgid ""
"This documentation is available from the <command>pbuilder</command> source "
"tar-ball, and from the git repository of <command>pbuilder</command> (web-"
"based access is possible).  A copy of this documentation can be found on the "
"<ulink url=\"http://pbuilder.alioth.debian.org/pbuilder-doc.html\">Alioth "
"project page for pbuilder</ulink>.  <ulink url=\"http://pbuilder.alioth."
"debian.org/pbuilder-doc.pdf\">There is also a PDF version</ulink>.  The "
"homepage for <command>pbuilder</command> is <ulink url=\"http://pbuilder."
"alioth.debian.org/\"> http://pbuilder.alioth.debian.org/ </ulink> hosted by "
"alioth project."
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1648
msgid ""
"Documentation is written using DocBook XML, with emacs PSGML mode, and using "
"wysidocbookxml for live previewing."
msgstr ""

# type: Content of: <book><chapter><sect1><title>
#: pbuilder-doc.xml:1654
msgid "Possibly inaccurate Background History of pbuilder"
msgstr ""

# type: Content of: <book><chapter><sect1><para>
#: pbuilder-doc.xml:1656
msgid ""
"The following is a most possibly inaccurate account of how "
"<command>pbuilder</command> came to happen, and other attempts to make "
"something like <command>pbuilder</command> happen.  This part of the "
"document was originally in the AUTHORS file, to give credit to those who "
"existed before <command>pbuilder</command>."
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><title>
#: pbuilder-doc.xml:1663
msgid "The Time Before pbuilder"
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><para>
#: pbuilder-doc.xml:1665
msgid ""
"There was once dbuild, which was a shell script to build Debian packages "
"from source. Lars Wirzenius wrote that script, and it was good, short, and "
"simple (probably).  There was nothing like build-depends then (I think), and "
"it was simple.  It could have been improved, I could only find references "
"and no actual source."
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><para>
#: pbuilder-doc.xml:1672
msgid ""
"debbuild was probably written by James Troup. I don't know it because I have "
"never seen the actual code, I could only find some references to it on the "
"net, and mailing list logs."
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><para>
#: pbuilder-doc.xml:1677
msgid ""
"sbuild is a perl script to build Debian packages from source.  It parses "
"Build-Depends, and performs other miscellaneous checks, and has a lot of "
"hacks to actually get things building, including a table of what package to "
"use when virtual packages are specified (does it do that still?).  It "
"supports the use of a local database for packages which do not have build-"
"dependencies. It was written by Ronan Hodek, and I think it was patched and "
"fixed and extended by several people. It is part of wanna-build, and used "
"extensively in the Debian buildd system. I think it was maintained mostly by "
"Ryan Murray."
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><title>
#: pbuilder-doc.xml:1691
msgid "Birth of pbuilder"
msgstr "pbuilder の誕生"

# type: Content of: <book><chapter><sect1><sect2><para>
#: pbuilder-doc.xml:1693
msgid ""
"wanna-build (sbuild) was (at the time of year 2001) quite difficult to set "
"up, and it was never a Debian package. dbuild was something that predated "
"Build-Depends."
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><para>
#: pbuilder-doc.xml:1698
msgid ""
"Building packages from source using Build-Depends information within a "
"chroot sounded trivial; and <command>pbuilder</command> was born. It was "
"initially a shell script with only a few lines, which called debootstrap and "
"chroot and dpkg-buildpackage in the same run, but soon, it was decided that "
"that's too slow."
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><para>
#: pbuilder-doc.xml:1706
msgid ""
"Yes, and it took almost an year to get things somewhat right, and in the "
"middle of the process, Debian 3.0 was released. Yay.  Debian 3.0 wasn't "
"completely buildable with <command>pbuilder</command>, but the amount of "
"packages which are not buildable is steadily decreasing. (I hope)"
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><title>
#: pbuilder-doc.xml:1715
msgid "And the second year of its life"
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><para>
#: pbuilder-doc.xml:1717
msgid ""
"Someone wanted <command>pbuilder</command> to not run as root, and as User-"
"mode-linux has become more useful as time passed, I've started experimenting "
"with <command>pbuilder-user-mode-linux</command>.  <command>pbuilder-user-"
"mode-linux</command> has not stayed functional as much as I would have "
"liked, and bootstrapping <command>user-mode-linux</command> environment has "
"been pretty hard, due to the quality of user-mode-linux code or packaging at "
"that time, which kept on breaking network support in one way or the other."
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><title>
#: pbuilder-doc.xml:1730
msgid "Fifth year of pbuilder"
msgstr "pbuilder の5年目"

# type: Content of: <book><chapter><sect1><sect2><para>
#: pbuilder-doc.xml:1732
msgid ""
"<command>pbuilder</command> is now widely adopted as a 'almost standard' "
"tool for testing packages, and building packages in a pristine environment.  "
"There are other similar tools that do similar tasks, but they do not share "
"the exact same goal.  To commemorate this fact, <command>pbuilder</command> "
"is now co-maintained with several people."
msgstr ""

# type: Content of: <book><chapter><sect1><sect2><para>
#: pbuilder-doc.xml:1740
msgid ""
"<command>sbuild</command> is now a well-maintained Debian package within "
"Debian, and with <command>pbuilder</command> being such a slow monster, some "
"people prefer the approach of sbuild.  Development to use LVM-snapshots, "
"cowloop, or cowdancer is hoped to improve the situation somewhat."
msgstr ""