# # AUTHOR , YEAR. # Ryuunosuke Ayanokouzi , 2015-2019. # Kenshi Muto , 2015. # Yoichi Chonan , 2015. # Osamu Aoki , 2016. # msgid "" msgstr "" "Project-Id-Version: 0\n" "POT-Creation-Date: 2022-07-30 18:23+0200\n" "PO-Revision-Date: 2019-02-03 09:00+0900\n" "Last-Translator: AYANOKOUZI, Ryuunosuke \n" "Language-Team: Japanese \n" "Language: ja\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Backport" msgstr "バックポート" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Rebuild" msgstr "再ビルド" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Source package" msgstr "ソースパッケージ" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Archive" msgstr "アーカイブ" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Meta-package" msgstr "メタパッケージ" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Debian Developer" msgstr "Debian 開発者" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "Creating a Debian Package" msgid "Debian Package" msgstr "Debian パッケージの作成" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Maintainer" msgstr "メンテナ" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Creating a Debian Package" msgstr "Debian パッケージの作成" # Checked-By: Ryuunosuke Ayanokouzi; msgid "It is quite common, for an administrator who has been handling Debian packages in a regular fashion, to eventually feel the need to create their own packages, or to modify an existing package. This chapter aims to answer the most common questions in this field, and provide the required elements to take advantage of the Debian infrastructure in the best way. With any luck, after trying your hand for local packages, you may even feel the need to go further than that and join the Debian project itself!" msgstr "Debian パッケージを標準的な方法で取り扱ってきた管理者がいずれは自分自身のパッケージを作成したり、既存のパッケージを変更したりする必要性を感じるということは極めて普通のことです。この章ではパッケージングに関する最も一般的な質問に答えたり、最良のやり方で Debian インフラをうまく使うために必要な要素を提供したりすることを目標にしています。運が良ければ、ローカルパッケージを取り扱った後、さらに進んで Debian プロジェクト自体に参加する必要性を感じるかもしれません。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Rebuilding a Package from its Sources" msgstr "ソースを使ったパッケージの再ビルド" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "packagebackport" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "packagerebuild" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Rebuilding a binary package is required under several sets of circumstances. In some cases, the administrator needs a software feature that requires the software to be compiled from sources, with a particular compilation option; in others, the software as packaged in the installed version of Debian is not recent enough. In the latter case, the administrator will usually build a more recent package taken from a newer version of Debian — such as Testing or even Unstable — so that this new package works in their Stable distribution; this operation is called “backporting”. As usual, care should be taken, before undertaking such a task, to check whether it has been done already — a quick look on the Debian Package Tracker for that package will reveal that information. backport" msgstr "いくつかの状況下では、バイナリパッケージの再ビルドが必要です。たとえば、管理者は特定のコンパイルオプションを付けてソフトウェアをソースからコンパイルすることで導入されるソフトウェアの機能を必要とする場合があります。そしてまた、インストール済みの Debian のバージョン用にパッケージングされたソフトウェアのバージョンが古い場合があります。ソフトウェアのバージョンが古い場合、管理者はテスト版や不安定版などの Debian の新しいバージョンから取得したより新しいパッケージをビルドすることが多いです。こうすることで、新しいパッケージを安定版ディストリビューションで動かすことが可能です。この操作は「バックポート」と呼ばれています。いつも通り、バックポート作業の前に既にバックポートパッケージが公開されているか否かを注意深く確認するべきです。対象のパッケージに対する Debian Package Tracker を一読するだけでこの種の情報が明らかになります。バックポート" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Getting the Sources" msgstr "ソースの取得" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "packagesource" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "aptsource" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "apt-getsource" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "aptupdate" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "apt-getupdate" msgstr "パッケージ種類" msgid "/etc/etc/apt/APT" msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Build-Depends, control field" msgid "deb-src" msgstr "Build-Depends、コントロールフィールド" msgid "Rebuilding a Debian package starts with getting its source code. The easiest way is to use the apt-get source package-name command. This command requires a deb-src line in the /etc/apt/sources.list file, and up-to-date index files (i.e. apt-get update). These conditions should already be met if you followed the instructions from the chapter dealing with APT configuration (see ). Note, however, that you will be downloading the source packages from the Debian version mentioned in the deb-src line." msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 dget; # Ref: $ man 1 dpkg-source; # Ref: $ man 1 apt-get; # Tag: L-CFMD; #, fuzzy #| msgid "Rebuilding a Debian package starts with getting its source code. The easiest way is to use the apt-get source source-package-name command. This command requires a deb-src line in the /etc/apt/sources.list file, and up-to-date index files (i.e. apt-get update). These conditions should already be met if you followed the instructions from the chapter dealing with APT configuration (see ). Note however, that you will be downloading the source packages from the Debian version mentioned in the deb-src line. If you need another version, you may need to download it manually from a Debian mirror or from the web site. This involves fetching two or three files (with extensions *.dsc — for Debian Source Control — *.tar.comp, and sometimes *.diff.gz or *.debian.tar.comp — comp taking one value among gz, bz2 or xz depending on the compression tool in use), then run the dpkg-source -x file.dsc command. If the *.dsc file is directly accessible at a given URL, there is an even simpler way to fetch it all, with the dget URL command. This command (which can be found in the devscripts package) fetches the *.dsc file at the given address, then analyzes its contents, and automatically fetches the file or files referenced within. Once everything has been downloaded, it extracts the source package (unless the -d or --download-only option is used)." msgid "If you need another version, you may need to download it manually from a Debian mirror or from the web site. This involves fetching two or three files (with extensions *.dsc — for Debian Source Control — *.tar.comp, and sometimes *.diff.gz or *.debian.tar.comp — comp taking one value among gz, bz2 or xz depending on the compression tool in use), then run the dpkg-source -x file.dsc command. If the *.dsc file is directly accessible at a given URL, there is an even simpler way to fetch it all, with the dget URL command. This command (which can be found in the devscripts package) fetches the *.dsc file at the given address, then analyzes its contents, and automatically fetches the file or files referenced within. Once everything has been downloaded, it verifies the integrity of the downloaded source packages using dscverify, and it extracts the source package (unless the -d or --download-only option is used). The Debian keyring is needed, unless the option -u is supplied." msgstr "Debian パッケージの再ビルドはパッケージのソースコードを取得することから始まります。最も簡単な方法は apt-get source source-package-name コマンドを使うことです。このコマンドを実行するには /etc/apt/sources.list ファイルの中に deb-src 行が必要で、さらに最新のインデックスファイルが必要です (たとえば apt-get update を実行する必要があります)。管理者が APT 設定を取り扱う章で説明した内容 (を参照してください) に従っている場合、これらの状況は既に満足されているはずです。しかしながら、apt-get source source-package-name コマンドは deb-src 行で言及されている Debian バージョンのソースパッケージをダウンロードする点に注意してください。もし他のバージョンのソースパッケージが必要な場合、Debian アーカイブミラーや Debian のウェブサイトから手作業でダウンロードする必要があるかもしれません。この場合には 2、3 個のファイルをダウンロードする必要があります (Debian Source Control 用に *.dsc 拡張子を持つファイル、*.tar.comp としばしば *.diff.gz や *.debian.tar.comp 拡張子を持つファイル、ここで comp は使われている圧縮ツールに応じて gz、bz2、xz のうちのどれか 1 つです)。その後、dpkg-source -x file.dsc コマンドを実行します。*.dsc ファイルがある URL から直接利用できるならば、dget URL コマンドを使えばより簡単にすべてを取得することが可能です。dget コマンドは (devscripts パッケージに含まれます) 指定したアドレスから *.dsc ファイルを取得し、内容を解析し、ファイル内で参照されている単一もしくは複数のファイルを自動的に取得します。すべてのダウンロードが完了したら、dget コマンドはソースパッケージを展開します (これは -d または --download-only オプションが使われていない場合に限ります)。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install devscripts; msgid "devscripts" msgstr "devscripts" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debi; #, fuzzy #| msgid "debi" msgid "dscverify" msgstr "debi" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install dput; # Ref: $ man 1 dput; #, fuzzy #| msgid "dput" msgid "dget" msgstr "dput" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install dput; # Ref: $ man 1 dput; #, fuzzy #| msgid "dput" msgid "dpkg-source" msgstr "dput" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Makefile" msgid ".dsc" msgstr "Makefile" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Makefile" msgid ".diff.gz" msgstr "Makefile" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid ".debian.tar.tar.gz" msgstr "パッケージ種類" msgid ".debian.tar.tar.bz2" msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid ".debian.tar.tar.xz" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid ".tar.tar.gz" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid ".tar.tar.bz2" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid ".tar.tar.xz" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "apt--download-only" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "apt-get--download-only" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install devscripts; #, fuzzy #| msgid "devscripts" msgid "debian-archive-keyring" msgstr "devscripts" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Making Changes" msgstr "修正を行う" msgid "Let us use the samba package as an example." msgstr "" msgid "" "$ apt source samba\n" "Reading package lists... Done\n" "NOTICE: 'samba' packaging is maintained in the 'Git' version control system at:\n" "https://salsa.debian.org/samba-team/samba.git\n" "Please use:\n" "git clone https://salsa.debian.org/samba-team/samba.git\n" "to retrieve the latest (possibly unreleased) updates to the package.\n" "Need to get 12.3 MB of source archives.\n" "Get:1 http://security.debian.org/debian-security bullseye-security/main samba 2:4.13.13+dfsg-1~deb11u3 (dsc) [4,514 B]\n" "Get:2 http://security.debian.org/debian-security bullseye-security/main samba 2:4.13.13+dfsg-1~deb11u3 (tar) [11.8 MB]\n" "Get:3 http://security.debian.org/debian-security bullseye-security/main samba 2:4.13.13+dfsg-1~deb11u3 (diff) [468 kB]\n" "Fetched 12.3 MB in 3s (4,582 kB/s)\n" "dpkg-source: info: extracting samba in samba-4.13.13+dfsg\n" "dpkg-source: info: unpacking samba_4.13.13+dfsg.orig.tar.xz\n" "dpkg-source: info: unpacking samba_4.13.13+dfsg-1~deb11u3.debian.tar.xz\n" "dpkg-source: info: using patch list from debian/patches/series\n" "dpkg-source: info: applying 07_private_lib\n" "dpkg-source: info: applying bug_221618_precise-64bit-prototype.patch\n" "dpkg-source: info: applying [...]\n" "" msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ apt-get source samba; # Tag: L-CFMD; #, fuzzy #| msgid "The source of the package is now available in a directory named after the source package and its version (for instance, samba-4.1.17+dfsg); this is where we'll work on our local changes." msgid "The source of the package is now available in a directory named after the source package and its version (samba-4.13.13+dfsg); this is where we'll work on our local changes." msgstr "これでパッケージのソースがソースパッケージとバージョンを基に名付けられたディレクトリ (たとえば samba-4.1.17+dfsg など) の中で利用できるようになりました。修正作業はこのディレクトリ内で行われます。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ dpkg --compare-versions 2:4.1.17+dfsg-2 lt 2:4.1.17+dfsg-2falcot1; # Ref: $ man 1 debchange; # Ref: $ man 1 sensible-editor; # Tag: L-CFMD; #, fuzzy #| msgid "The first thing to do is to change the package version number, so that the rebuilt packages can be distinguished from the original packages provided by Debian. Assuming the current version is 2:4.1.17+dfsg-2, we can create version 2:4.1.17+dfsg-2falcot1, which clearly indicates the origin of the package. This makes the package version number higher than the one provided by Debian, so that the package will easily install as an update to the original package. Such a change is best effected with the dch command (Debian CHangelog) from the devscripts package, with an command such as dch --local falcot. This invokes a text editor (sensible-editor — this should be your favorite editor if it is mentioned in the VISUAL or EDITOR environment variables, and the default editor otherwise) to allow documenting the differences brought by this rebuild. This editor shows us that dch really did change the debian/changelog file." msgid "The first thing to do is to change the package version number, so that the rebuilt packages can be distinguished from the original packages provided by Debian. Assuming the current version is 2:4.13.13+dfsg-1~deb11u3, we can create version 2:4.13.13+dfsg-1~deb11u3+falcot1, which clearly indicates the origin of the package. This makes the package version number higher than the one provided by Debian, so that the package will easily install as an update to the original package. Such a change is best effected with the dch command (Debian CHangelog) from the devscripts package. dch devscripts packageversion" msgstr "最初にパッケージのバージョン番号を変更します。こうすることで、再ビルドされたパッケージを Debian の提供する元パッケージと区別することが可能です。現在のバージョンが 2:4.1.17+dfsg-2 の場合、バージョン 2:4.1.17+dfsg-2falcot1 を作成することが可能です。これはパッケージの出自を明らかに示しています。このパッケージのバージョン番号は Debian が提供する元パッケージのバージョン番号よりも大きいため、このパッケージを元パッケージの更新として簡単にインストールできます。このような作業を極めて効果的に行うには、devscripts パッケージの提供する dch コマンド (Debian CHangelog) を dch --local falcot のように使います。これは最良の効果を発揮します。dch コマンドはテキストエディタ (sensible-editor。このエディタは VISUAL または EDITOR 環境変数で定義されているお気に入りのエディタです。そうでなければデフォルトエディタです) を起動します。ここで、再ビルドによって導入される変更の内容を記述してください。このエディタは dch が debian/changelog ファイルを変更したことを示します。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 dpkg-buildpackage; # Tag: L-CFMD; #, fuzzy #| msgid "" #| "$ dpkg-buildpackage -us -uc\n" #| "[...]\n" #| "" msgid "" "$ cd 4.13.13+dfsg-1~deb11u3\n" "$ dch --local +falcot\n" "" msgstr "" "$ dpkg-buildpackage -us -uc\n" "[...]\n" "" msgid "The last command invokes a text editor (sensible-editor — this should be your favorite editor if it is mentioned in the VISUAL or EDITOR environment variables, and the default editor otherwise) to allow documenting the differences brought by this rebuild. This editor shows us that dch really did change the debian/changelog file." msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debi; #, fuzzy #| msgid "debi" msgid "sensible-editor" msgstr "debi" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Makefile" msgid "VISUAL" msgstr "Makefile" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "environment variableVISUAL" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Makefile" msgid "EDITOR" msgstr "Makefile" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "environment variableEDITOR" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "packagechangelog" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 dh_auto_build; # Ref: $ man 1 dh_auto_configure; # Tag: L-CFMD; #, fuzzy #| msgid "When a change in build options is required, the changes need to be made in debian/rules, which drives the steps in the package build process. In the simplest cases, the lines concerning the initial configuration (./configure …) or the actual build ($(MAKE) … or make …) are easy to spot. If these commands are not explicitly called, they are probably a side effect of another explicit command, in which case please refer to their documentation to learn more about how to change the default behavior. With packages using dh, you might need to add an override for the dh_auto_configure or dh_auto_build commands (see their respective manual pages for explanations on how to achieve this)." msgid "When a change in build options is required, the changes need to be made in debian/rules, which drives the steps in the package build process. In the simplest cases, the lines concerning the initial configuration (./configure …) or the actual build ($(MAKE) … or make … or cmake … or …) are easy to spot. If these commands are not explicitly called, they are probably a side effect of another explicit command, in which case please refer to their documentation to learn more about how to change the default behavior. With packages using dh, you might need to add an override for the dh_auto_configure or dh_auto_build commands (see their respective manual pages and debhelper 7 for explanations on how to achieve this)." msgstr "ビルドオプションの変更が必要な場合、debian/rules を修正します。debian/rules はパッケージビルド作業の各段階を動作させるものです。debian/rules が最も単純に書かれている場合、初期設定 (./configure …) や実際のビルド ($(MAKE) … や make …) を実行するコマンドを簡単に見つけられるでしょう。ファイル内にこれらのコマンドが明示的に書かれていない場合、このファイルの内容は別のコマンドに対する作用を書いているのかもしれません。このような場合、デフォルト挙動を変える方法をより詳細に学ぶために文書を参照してください。dh を使っているパッケージのビルドオプションを変更する場合、dh_auto_configure や dh_auto_build コマンドを再定義する必要があるかもしれません (これを行う方法に関する説明は各コマンドのマニュアルページをご覧ください)。" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "dhdh_auto_build" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "dhdh_auto_configure" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "dhoverride target" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debchange; #, fuzzy #| msgid "dch" msgid "dhdebhelper" msgstr "dch" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packageDebianarchive of" msgid "packagerulesrules" msgstr "パッケージDebianアーカイブ" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "debhelper" msgid "debhelper" msgstr "debhelper" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; msgid "Depending on the local changes to the packages, an update may also be required in the debian/control file, which contains a description of the generated packages. In particular, this file contains Build-Depends lines controlling the list of dependencies that must be fulfilled at package build time. These often refer to versions of packages contained in the distribution the source package comes from, but which may not be available in the distribution used for the rebuild. There is no automated way to determine if a dependency is real or only specified to guarantee that the build should only be attempted with the latest version of a library — this is the only available way to force an autobuilder to use a given package version during build, which is why Debian maintainers frequently use strictly versioned build-dependencies." msgstr "パッケージに対して行った変更の内容によっては、debian/control ファイルの内容もまた更新する必要があります。debian/control ファイルには生成されるパッケージの説明が含まれます。特に、debian/control ファイルにはパッケージのビルド時点で満足されなければいけない依存関係のリストを制御する Build-Depends 行が含まれます。Build-Depends 行で指定されているパッケージのバージョンはソースパッケージが提供されるディストリビューションに含まれるパッケージのバージョンと一致している場合が多いです。しかし、再ビルドを行うディストリビューションではここで指定されているバージョンが利用できないかもしれません。依存関係が本物か、それともビルド時にライブラリの最新版を試すことを保証するためだけ指定されているかを決定する自動的な方法はありません。Build-Depends 行を使うことが自動ビルドロボットにビルド中に与えられたパッケージバージョンを使うことを強制するための唯一の方法なので、Debian メンテナはバージョンを厳しく指定したビルド依存関係を使うことが多いです。" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packageDebianarchive of" msgid "packagecontrolcontrol" msgstr "パッケージDebianアーカイブ" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Build-Depends, control field" msgid "controlBuild-Depends, header field" msgstr "Build-Depends、コントロールフィールド" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; msgid "If you know for sure that these build-dependencies are too strict, you should feel free to relax them locally. Reading the files which document the standard way of building the software — these files are often called INSTALL — will help you figure out the appropriate dependencies. Ideally, all dependencies should be satisfiable from the distribution used for the rebuild; if they are not, a recursive process starts, whereby the packages mentioned in the Build-Depends field must be backported before the target package can be. Some packages may not need backporting, and can be installed as-is during the build process (a notable example is debhelper). Note that the backporting process can quickly become complex if you are not careful. Therefore, backports should be kept to a strict minimum when possible." msgstr "もしあなたが、指定されているビルド依存関係を緩めても問題ないと確信できる場合、手元で自由に依存関係を緩和することが可能です。対象のソフトウェアをビルドする標準的な方法について説明しているファイル (INSTALL と名付けられていることが多いです) を読むことは適切な依存関係を明らかにする助けになります。理想的に言えば、再ビルドに使うディストリビューションの要素を使ってすべての依存関係を満足させるべきです。しかしそれが無理ならば、対象のパッケージをバックポートする前に、再帰的に Build-Depends フィールドで言及されているパッケージを必ずバックポートしなければいけません。一部のパッケージはバックポートの必要がなく、ビルド作業中に現状のままインストールできます (特筆すべき例は debhelper です)。バックポート作業は気を付けないとすぐに複雑になる点に注意してください。それゆえ、バックポートは可能な限り厳密に必要最低限に留めるべきです。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Makefile" msgid "INSTALL" msgstr "Makefile" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; msgid "TIP Installing Build-Depends" msgstr "TIP Build-Depends のインストール" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 apt-get; # Tag: L-CFMD; # Tag: PTAL; #, fuzzy #| msgid "apt-get allows installing all packages mentioned in the Build-Depends fields of a source package available in a distribution mentioned in a deb-src line of the /etc/apt/sources.list file. This is a simple matter of running the apt-get build-dep source-package command." msgid "apt-get allows installing all packages mentioned in the Build-Depends fields of a source package available in a distribution mentioned in a deb-src line of the /etc/apt/sources.list file. This is a simple matter of running the apt-get build-dep package command." msgstr "apt-get を使うことで、あるソースパッケージの Build-Depends フィールドに指定されているすべてのパッケージをインストールすることが可能です。apt-get は /etc/apt/sources.list ファイルの deb-src 行で指定されているディストリビューションに含まれるソースパッケージの Build-Depends フィールドに指定されているパッケージをインストールします。これを行うには、apt-get build-dep source-package コマンドを実行するだけです。" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "APT/etc/apt/sources.list" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install dput; # Ref: $ man 1 dput; #, fuzzy #| msgid "dput" msgid "apt-get" msgstr "dput" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 apt-get; # Tag: L-CFMD; msgid "Starting the Rebuild" msgstr "再ビルドの開始" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 dpkg-buildpackage; # Tag: L-CFMD; msgid "When all the needed changes have been applied to the sources, we can start generating the actual binary package (.deb file). The whole process is managed by the dpkg-buildpackage command." msgstr "ソースに対するすべての必要な変更が完了したら、実際のバイナリパッケージ (.deb ファイル) を生成します。すべてのプロセスは dpkg-buildpackage コマンドで管理されます。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Makefile" msgid ".deb" msgstr "Makefile" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 8 pbuilder; # Tag: L-CFMD; #, fuzzy #| msgid "pbuilder" msgid "dpkg-buildpackage" msgstr "pbuilder" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Rebuilding a package" msgstr "パッケージの再ビルド" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 dpkg-buildpackage; # Tag: L-CFMD; msgid "" "$ dpkg-buildpackage -us -uc\n" "[...]\n" "" msgstr "" "$ dpkg-buildpackage -us -uc\n" "[...]\n" "" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 dpkg-buildpackage; # Tag: L-CFMD; #, fuzzy #| msgid "The previous command can fail if the Build-Depends fields have not been updated, or if the related packages are not installed. In such a case, it is possible to overrule this check by passing the -d option to dpkg-buildpackage. However, explicitly ignoring these dependencies runs the risk of the build process failing at a later stage. Worse, the package may seem to build correctly but fail to run properly: some programs automatically disable some of their features when a required library is not available at build time." msgid "The previous command can fail if the Build-Depends field has not been updated, or if the related packages are not installed. In such a case, it is possible to overrule this check by passing the -d option to dpkg-buildpackage. However, explicitly ignoring these dependencies runs the risk of the build process failing at a later stage. Worse, the package may seem to build correctly but fail to run properly: some programs automatically disable some of their features when a required library is not available at build time. The switch can still be very useful if you only want to create a source package, which is supposed to be passed to clean build environments as described in ." msgstr "Build-Depends フィールドが更新されていなかったり、関連するパッケージがインストールされていなかった場合、dpkg-buildpackage コマンドは失敗します。そのような場合、dpkg-buildpackage に -d オプションを指定して、依存関係確認を行わないようにすることも可能です。しかしながら、依存関係を明示的に無視すると後々の段階でビルド作業が失敗する恐れがあります。さらに悪いことに、パッケージが正常にビルドされたように見えても正しく動かない可能性があります。なぜなら一部のプログラムは必要なライブラリがビルド時に利用できない場合に一部の機能を自動的に無効化するからです。" msgid "The other options used in the above example make sure that neither the source package's .dsc (-us) nor the produced .changes file (-uc) get signed with the package builder's cryptographic key after the asuccessful build." msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 fakeroot; # Tag: L-CFMD; msgid "TOOL fakeroot" msgstr "TOOL fakeroot" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debchange; #, fuzzy #| msgid "dch" msgid "fakeroot" msgstr "dch" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "sponsoring" msgid "root" msgstr "パッケージの支援" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "accountroot account" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 fakeroot; # Ref: $ man 1 dpkg-buildpackage; # Tag: L-CFMD; msgid "In essence, the package creation process is a simple matter of gathering in an archive a set of existing (or built) files; most of the files will end up being owned by root in the archive. However, building the whole package under this user would imply increased risks; fortunately, this can be avoided with the fakeroot command. This tool can be used to run a program and give it the impression that it runs as root and creates files with arbitrary ownership and permissions. When the program creates the archive that will become the Debian package, it is tricked into creating an archive containing files marked as belonging to arbitrary owners, including root. This setup is so convenient that dpkg-buildpackage uses fakeroot by default when building packages." msgstr "基本的に、パッケージ作成作業とは存在する (ビルドされた) ファイル群を 1 つのアーカイブにまとめるという単純な作業に過ぎません。さらにほとんどのファイルは最終的にアーカイブ中で root によって所有されることになります。しかしながら、パッケージ全体を root で作ると暗黙のうちにリスクが増加します。しかし幸いなことに、fakeroot コマンドを使うことでこれを避けることが可能です。fakeroot 環境を使うことで、プログラムを実行したり、プログラムに自分の実行者が root であり任意の所有者とパーミッションを持つファイルを作成することが可能であると認識させたりすることが可能になります。fakeroot 環境下で Debian パッケージとなるアーカイブを作成した場合、fakeroot プログラムは root およびその他のユーザに所有されるファイルを含むアーカイブを作成します。dpkg-buildpackage がパッケージをビルドする際にデフォルトで fakeroot を使っていることからも分かる通り、fakeroot 環境下でパッケージをビルドすることはとても便利な方法です。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 fakeroot; # Tag: L-CFMD; msgid "Note that the program is only tricked into “believing” that it operates as a privileged account, and the process actually runs as the user running fakeroot program (and the files are actually created with that user's permissions). At no time does it actually get root privileges that it could abuse." msgstr "fakeroot 環境下で動作するプログラムはだまされて特権アカウントとして操作するように「信じこまされる」だけです。プロセスは fakeroot program を実行しているユーザの権限で実行されます (作成されるファイルはそのユーザのパーミッションを与えられます)。fakeroot が実際に root 権限を取得してそれを乱用することは決してありません。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 dpkg-buildpackage; # Ref: $ man 1 debuild; # Tag: L-CFMD; #, fuzzy #| msgid "More often than not, Debian developers use a higher-level program such as debuild; this runs dpkg-buildpackage as usual, but it also adds an invocation of a program that runs many checks to validate the generated package against the Debian policy. This script also cleans up the environment so that local environment variables do not “pollute” the package build. The debuild command is one of the tools in the devscripts suite, which share some consistency and configuration to make the maintainers' task easier." msgid "More often than not, Debian developers use a higher-level program such as debuild; this runs dpkg-buildpackage as usual, but it also adds an invocation of a program that runs many checks to validate the generated package against the Debian policy. This script also cleans up the environment so that local environment variables do not “pollute” the package build. The debuild command is one of the tools in the devscripts suite, which share some consistency and configuration to make the maintainers' task easier." msgstr "しばしば、Debian 開発者は debuild などの高レベルプログラムを使います。debuild は通常通り dpkg-buildpackage を実行するだけでなく、生成されたパッケージの Debian ポリシーに対する妥当性を確認するプログラムも実行します。debuild スクリプトは、手元の環境変数がパッケージビルドを「汚染」しないように、ビルド環境を整えます。debuild コマンドは devscripts スイートに含まれるツールの 1 つで、メンテナの作業を簡単にするためのいくつかの一貫性と設定を共有します。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debuild; msgid "debuild" msgstr "debuild" msgid "QUICK LOOK Building packages in chrooted and virtual environments" msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 8 pbuilder; # Tag: L-CFMD; msgid "pbuilder" msgstr "pbuilder" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 8 pbuilder; # Tag: L-CFMD; #, fuzzy #| msgid "pbuilder" msgid "cowbuilder" msgstr "pbuilder" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debchange; #, fuzzy #| msgid "dch" msgid "schroot" msgstr "dch" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debuild; #, fuzzy #| msgid "debuild" msgid "sbuild" msgstr "debuild" msgid "Building a package on an existing system, like a workstation or server, can pose several problems. Maybe the system has packages installed, that conflict with the build requirements. Or maybe it has packages (libraries, headers, etc.) installed, that the project to build is not supposed to use - e.g. from Testing, Unstable, or even from third parties. Also it might have packages installed, which are actually required for the build, but are not listed in debian/control. It is therefore a good practice to build a packages in “clean“ environments." msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 8 pbuilder; # Tag: L-CFMD; #, fuzzy #| msgid "The pbuilder program (in the similarly named package) allows building a Debian package in a chrooted environment. It first creates a temporary directory containing the minimal system required for building the package (including the packages mentioned in the Build-Depends field). This directory is then used as the root directory (/), using the chroot command, during the build process." msgid "The sbuild, pbuilder, or cowbuilder programs (in the similarly named packages) allow building a Debian package in a chrooted environment. Each of them first creates a temporary directory containing the minimal system required for building the package (including the packages mentioned in the Build-Depends field). This directory is then used as the root directory (/), using the chroot command, during the build process." msgstr "pbuilder プログラム (同名のパッケージに含まれます) を使うことで、chroot された環境の中で Debian パッケージをビルドすることが可能になります。pbuilder プログラムは最初にパッケージをビルドするために必要な最低限のシステム (と Build-Depends フィールドで指定されているパッケージ) を含む一時ディレクトリを作成します。このディレクトリは chroot コマンドビルド中に使うルートディレクトリ (/) として使われます。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debchange; #, fuzzy #| msgid "dch" msgid "chroot" msgstr "dch" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 8 pbuilder; # Tag: L-CFMD; #, fuzzy #| msgid "This tool allows the build process to happen in an environment that is not altered by users' manipulations. This also allows for quick detection of the missing build-dependencies (since the build will fail unless the appropriate dependencies are documented). Finally, it allows building a package for a Debian version that is not the one used by the system as a whole: the machine can be using Stable for its normal workload, and a pbuilder running on the same machine can be using Unstable for package builds." msgid "These tools allow the build process to happen in an environment that is not altered by users' manipulations. This also allows for quick detection of the missing build-dependencies (since the build will fail unless the appropriate dependencies are documented). Finally, it allows building a package for a Debian version that is not the one used by the system as a whole: the machine can be using Stable for its normal workload, and the chrooted environments can be running on the same machine using Unstable for package builds. Using these tools, it is also possible to build for a different distribution, like Ubuntu." msgstr "pbuilder ツールを使うことで、ビルド作業をユーザの操作によって変更されない環境の中で行うことが可能になります。さらに、pbuilder ツールを使うことで、言及されていないビルド依存関係を素早く検出することが可能になります (なぜなら、適切な依存関係が指定されていなければビルドは失敗するからです)。最後に、pbuilder ツールを使うことで、システム用に使われている Debian バージョン以外の Debian バージョン向けのパッケージをビルドすることが可能になります。つまり、マシンは通常の作業用に安定版を使うことが可能です。そして、同じマシン上で動作する pbuilder はパッケージビルド専用に不安定版を使うことが可能です。" msgid "schroot, sbuild-shell, or pbuilder allow running a command or a login shell in a chrooted environment." msgstr "" msgid "Sometimes it is not enough to build a package in a chrooted environment. This can be due to building for a different architecture where cross-compilation does not work, or due to the tools not being able to create a chrooted environment for the desired target system. Then one can create virtual machines to build the package there. These setups are usually more complex then the tools mentioned above, and rarely needed, so we will only mention this possibility without going into much detail. Check out for an introduction into this topic." msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "Debian Maintainer" msgid "virtualization" msgstr "Debian メンテナ" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Building your First Package" msgstr "最初のパッケージのビルド" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Meta-Packages or Fake Packages" msgstr "メタパッケージやフェイクパッケージ" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "packagemeta-package" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "package types" msgid "meta-package" msgstr "パッケージの種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "packagefake package" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "key pair" msgid "fake package" msgstr "鍵ペア" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Fake packages and meta-packages are similar, in that they are empty shells that only exist for the effects their meta-data have on the package handling stack." msgstr "フェイクパッケージとメタパッケージは似ています。両者は自分のメタデータをパッケージ取り扱いスタックに置いておくためだけに存在する抜け殻です。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: man 1 dpkg; # Ref: man 1 apt; # Tag: L-CFMD; #, fuzzy #| msgid "The purpose of a fake package is to trick dpkg and apt into believing that some package is installed even though it's only an empty shell. This allows satisfying dependencies on a package when the corresponding software was installed outside the scope of the packaging system. Such a method works, but it should still be avoided whenever possible, since there is no guarantee that the manually installed software behaves exactly like the corresponding package would and other packages depending on it would not work properly." msgid "The purpose of a fake package is to trick dpkg and apt into believing that some package is installed even though it is only an empty shell. This allows satisfying dependencies on a package when the corresponding software was installed outside the scope of the packaging system. Such a method works, but it should still be avoided whenever possible, since there is no guarantee that the manually installed software behaves exactly like the corresponding package would and other packages depending on it would not work properly." msgstr "フェイクパッケージの目的は dpkg と apt をだまして、抜け殻に過ぎないいくつかのパッケージがインストールされていると信じこませることにあります。フェイクパッケージを使うことで、あるソフトウェアの依存関係を満足させるために必要なソフトウェアがパッケージシステムの管轄外にインストールされている場合に、そのソフトウェアの依存関係を満足させることが可能です。フェイクパッケージを使うことで、依存関係の問題は解決されますが、これはできる限り避けるべき方法です。なぜなら、手作業でインストールされたソフトウェアが対応するパッケージと全く同様に振る舞う保証はありませんし、手作業でインストールされたソフトウェアに依存する他のパッケージが適切に動く保証もないからです。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "On the other hand, a meta-package exists mostly as a collection of dependencies, so that installing the meta-package will actually bring in a set of other packages in a single step." msgstr "逆に、メタパッケージはメタパッケージをインストールするだけで一連の他のパッケージをインストールすることが可能になる依存関係の集合体として使われます。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 equivs-control; # Ref: $ man 1 equivs-build; msgid "Both these kinds of packages can be created by the equivs-control and equivs-build commands (in the equivs package). The equivs-control file command creates a Debian package header file that should be edited to contain the name of the expected package, its version number, the name of the maintainer, its dependencies, and its description. Other fields without a default value are optional and can be deleted. The Copyright, Changelog, Readme and Extra-Files fields are not standard fields in Debian packages; they only make sense within the scope of equivs-build, and they will not be kept in the headers of the generated package." msgstr "フェイクパッケージとメタパッケージは equivs-control と equivs-build コマンド (equivs パッケージに含まれます) を使って作成されます。equivs-control file コマンドは Debian パッケージヘッダファイルを作成します。Debian パッケージヘッダファイルには、パッケージの名前、バージョン番号、メンテナ、依存関係、説明を含めるように編集します。デフォルト値を持たない他のフィールドは任意で、削除することも可能です。Copyright、Changelog、Readme、Extra-Files フィールドは Debian パッケージの標準的なフィールドではありません。さらに、これらのフィールドは equivs-build を使う限りにおいて意味を持つものであり、生成されるパッケージのヘッダから削除されます。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install devscripts; #, fuzzy #| msgid "devscripts" msgid "equivs" msgstr "devscripts" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install devscripts; #, fuzzy #| msgid "devscripts" msgid "equivsequivs-control" msgstr "devscripts" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install devscripts; #, fuzzy #| msgid "devscripts" msgid "equivsequivs-build" msgstr "devscripts" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Header file of the libxml-libxml-perl fake package" msgstr "libxml-libxml-perl フェイクパッケージのヘッダファイル" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ dpkg --compare-versions 2.0116+dfsg-1+deb8u1 lt 2.0116-1; #, fuzzy #| msgid "" #| "\n" #| "Section: perl\n" #| "Priority: optional\n" #| "Standards-Version: 3.9.6\n" #| "\n" #| "Package: libxml-libxml-perl\n" #| "Version: 2.0116-1\n" #| "Maintainer: Raphael Hertzog <hertzog@debian.org>\n" #| "Depends: libxml2 (>= 2.7.4)\n" #| "Architecture: all\n" #| "Description: Fake package - module manually installed in site_perl\n" #| " This is a fake package to let the packaging system\n" #| " believe that this Debian package is installed. \n" #| " .\n" #| " In fact, the package is not installed since a newer version\n" #| " of the module has been manually compiled & installed in the\n" #| " site_perl directory." msgid "" "\n" "Depends: libxml2 (>= 2.9.10)\n" "Architecture: all\n" "Description: Fake package - module manually installed in site_perl\n" " This is a fake package to let the packaging system\n" " believe that this Debian package is installed.\n" " .\n" " In fact, the package is not installed since a newer version\n" " of the module has been manually compiled & installed in the\n" " site_perl directory.\n" "]]>" msgstr "" "\n" "Section: perl\n" "Priority: optional\n" "Standards-Version: 3.9.6\n" "\n" "Package: libxml-libxml-perl\n" "Version: 2.0116-1\n" "Maintainer: Raphael Hertzog <hertzog@debian.org>\n" "Depends: libxml2 (>= 2.7.4)\n" "Architecture: all\n" "Description: Fake package - module manually installed in site_perl\n" " This is a fake package to let the packaging system\n" " believe that this Debian package is installed. \n" " .\n" " In fact, the package is not installed since a newer version\n" " of the module has been manually compiled & installed in the\n" " site_perl directory." # Checked-By: Ryuunosuke Ayanokouzi; # Ref: man 1 equivs-build; msgid "The next step is to generate the Debian package with the equivs-build file command. Voilà: the package is created in the current directory and it can be handled like any other Debian package would." msgstr "次のステップでは、equivs-build file コマンドを使って Debian パッケージを生成します。さぁこれでパッケージは現在のディレクトリに作成され、他の Debian パッケージと同様に取り扱うことが可能になります。" msgid "" "$ equivs-build file\n" "\n" "dpkg-buildpackage: info: host architecture amd64\n" " dpkg-source --before-build .\n" " debian/rules clean\n" "dh clean\n" " dh_clean\n" " debian/rules binary\n" "dh binary\n" " dh_update_autotools_config\n" " dh_autoreconf\n" " create-stamp debian/debhelper-build-stamp\n" " dh_prep\n" " dh_install\n" " dh_installdocs\n" " dh_installchangelogs\n" " dh_perl\n" " dh_link\n" " dh_strip_nondeterminism\n" " dh_compress\n" " dh_fixperms\n" " dh_missing\n" " dh_installdeb\n" " dh_gencontrol\n" " dh_md5sums\n" " dh_builddeb\n" "dpkg-deb: building package 'libxml-libxml-perl' in '../libxml-libxml-perl_2.0207-1_all.deb'.\n" " dpkg-genbuildinfo --build=binary\n" " dpkg-genchanges --build=binary >../libxml-libxml-perl_2.0207-1_amd64.changes\n" "dpkg-genchanges: info: binary-only upload (no source code included)\n" " dpkg-source --after-build .\n" "dpkg-buildpackage: info: binary-only upload (no source included)\n" "\n" "The package has been created.\n" "Attention, the package has been created in the current directory,\n" "not in \"..\" as indicated by the messaige above!\n" "]]>" msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Simple File Archive" msgstr "単純なファイルアーカイブ" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debchange; #, fuzzy #| msgid "dch" msgid "dh_make" msgstr "dch" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "dh-make" msgid "dh-make" msgstr "dh-make" # Checked-By: Ryuunosuke Ayanokouzi; msgid "The Falcot Corp administrators need to create a Debian package in order to ease deployment of a set of documents on a large number of machines. The administrator in charge of this task first reads the “New Maintainer's Guide”, then starts working on their first package. " msgstr "Falcot Corp の管理者は大量のマシン上に一連の文書を配備することを簡単に行うために Debian パッケージを作成する必要があります。この作業を担当している管理者は最初に「新メンテナーガイド」を読み、その後最初のパッケージに対する作業に着手します。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 8 dh_make; msgid "The first step is creating a falcot-data-1.0 directory to contain the target source package. The package will logically, be named falcot-data and bear the 1.0 version number. The administrator then places the document files in a data subdirectory. Then they invoke the dh_make command (from the dh-make package) to add files required by the package generation process, which will all be stored in a debian subdirectory:" msgstr "最初に、対象のソースパッケージを含める falcot-data-1.0 ディレクトリを作成します。こうしておけば、パッケージは必然的に falcot-data と名付けられ、バージョン番号は 1.0 になります。その後、管理者は文書ファイルを data サブディレクトリに置きます。その後、管理者は dh_make コマンド (dh-make パッケージに含まれます) を実行し、パッケージ生成作業に必要なファイルを追加します。ここで追加されるファイルは debian サブディレクトリに保存されます。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 8 dh_make; #, fuzzy #| msgid "" #| "\n" #| "$ cd falcot-data-1.0\n" #| "$ dh_make --native\n" #| "\n" #| "Type of package: single binary, indep binary, multiple binary, library, kernel module, kernel patch?\n" #| " [s/i/m/l/k/n] i\n" #| "\n" #| "Maintainer name : Raphael Hertzog\n" #| "Email-Address : hertzog@debian.org\n" #| "Date : Fri, 04 Sep 2015 12:09:39 -0400\n" #| "Package Name : falcot-data\n" #| "Version : 1.0\n" #| "License : gpl3\n" #| "Type of Package : Independent\n" #| "Hit <enter> to confirm:\n" #| "Currently there is no top level Makefile. This may require additional tuning.\n" #| "Done. Please edit the files in the debian/ subdirectory now. You should also\n" #| "check that the falcot-data Makefiles install into $DESTDIR and not in / .\n" #| "$" msgid "" "\n" "$ cd falcot-data-1.0\n" "$ dh_make --native\n" "\n" "Type of package: (single, indep, library, python)\n" "[s/i/l/p]? i\n" "\n" "Maintainer Name : Raphael Hertzog\n" "Email-Address : hertzog@debian.org\n" "Date : Sat, 26 Feb 2021 13:02:06 +0100\n" "Package Name : falcot-data\n" "Version : 1.0\n" "License : gpl3\n" "Package Type : indep\n" "Are the details correct? [Y/n/q]\n" "Currently there is not top level Makefile. This may require additional tuning\n" "Done. Please edit the files in the debian/ subdirectory now.\n" "\n" "$" msgstr "" "\n" "$ cd falcot-data-1.0\n" "$ dh_make --native\n" "\n" "Type of package: single binary, indep binary, multiple binary, library, kernel module, kernel patch?\n" " [s/i/m/l/k/n] i\n" "\n" "Maintainer name : Raphael Hertzog\n" "Email-Address : hertzog@debian.org\n" "Date : Sat, 05 Sep 2015 01:09:39 +0900\n" "Package Name : falcot-data\n" "Version : 1.0\n" "License : gpl3\n" "Type of Package : Independent\n" "Hit <enter> to confirm:\n" "Currently there is no top level Makefile. This may require additional tuning.\n" "Done. Please edit the files in the debian/ subdirectory now. You should also\n" "check that the falcot-data Makefiles install into $DESTDIR and not in / .\n" "$" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 8 dh_make; #, fuzzy #| msgid "The selected type of package (indep binary) indicates that this source package will generate a single binary package that can be shared across all architectures (Architecture: all). single binary acts as a counterpart, and leads to a single binary package that is dependent on the target architecture (Architecture: any). In this case, the former choice is more relevant since the package only contains documents and no binary programs, so it can be used similarly on computers of all architectures." msgid "The selected type of package (indep) indicates that this source package will generate a single binary package that can be shared across all architectures (Architecture: all in debian/control). single acts as a counterpart, and leads to a single binary package that is dependent on the target architecture (Architecture: any). In this case, the former choice is more relevant since the package only contains documents and no binary programs, so it can be used similarly on computers of all architectures." msgstr "パッケージの種類で indep binary を選ぶと、ソースパッケージから単一のバイナリパッケージを生成します。ここで生成されるバイナリパッケージはすべてのアーキテクチャで共有されます (Architecture: all)。single binary はその逆の振る舞いで、対象のアーキテクチャに依存する (Architecture: any) 単一のバイナリを生成します。今回作成するパッケージの場合、indep binary がより適切です。なぜなら、このパッケージは文書だけを含みバイナリプログラムを含まないからです。このため、すべてのアーキテクチャのコンピュータで同様に使うことが可能です。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "packagetypes" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "packagearchitecture" msgstr "パッケージ種類" msgid "controlArchitecture, header field" msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 8 dh_make; #, fuzzy #| msgid "The multiple binary type corresponds to a source package leading to several binary packages. A particular case, library, is useful for shared libraries, since they need to follow strict packaging rules. In a similar fashion, kernel module or kernel patch should be restricted to packages containing kernel modules." msgid "The library type corresponds to a source package leading to several binary packages. It is useful for shared libraries, since they need to follow strict packaging rules." msgstr "multiple binary を選ぶと、ソースパッケージから複数のバイナリパッケージを作成することになります。library は特別な場合で、共有ライブラリ用に用意されています。なぜなら、共有ライブラリは厳しいパッケージング規則に従う必要があるからです。同様に、kernel module および kernel patch はカーネルモジュールを含むパッケージ用に用意されています。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "TIP Maintainer's name and email address" msgstr "TIP メンテナの名前と電子メールアドレス" msgid "DEBFULLNAMEenvironment variable" msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "environment variableDEBFULLNAME" msgstr "パッケージ種類" msgid "DEBEMAILenvironment variable" msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "environment variableDEBEMAIL" msgstr "パッケージ種類" msgid "EMAILenvironment variable" msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "environment variableEMAIL" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Makefile" msgid ".bashrc" msgstr "Makefile" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 8 dh_make; # Ref: $ man 8 bash; msgid "Most of the programs involved in package maintenance will look for your name and email address in the DEBFULLNAME and DEBEMAIL or EMAIL environment variables. Defining them once and for all will avoid you having to type them multiple times. If your usual shell is bash, it is a simple matter of adding the following two lines in your ~/.bashrc file (you will obviously replace the values with more relevant ones!):" msgstr "パッケージメンテナンスに関わるほとんどのプログラムはメンテナの名前と電子メールアドレスを DEBFULLNAME と DEBEMAIL または EMAIL 環境変数から取得します。たった 1 回これらの環境変数を定義するだけで、毎回これらの情報を打ち込む必要がなくなります。通常のシェルが bash の場合、~/.bashrc ファイルに以下の 2 行 (当然ですが、値を自分のものに変えてください!) を追加するだけで簡単にこれを行うことが可能です。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 8 dh_make; # Ref: $ man 8 bash; msgid "" "\n" "export EMAIL=\"hertzog@debian.org\"\n" "export DEBFULLNAME=\"Raphael Hertzog\"" msgstr "" "\n" "export EMAIL=\"hertzog@debian.org\"\n" "export DEBFULLNAME=\"Raphael Hertzog\"" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Makefile" msgid "debian, directory" msgstr "Makefile" msgid "debian, directoryrulesrules" msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Makefile" msgid "rules" msgstr "Makefile" msgid "debian, directorycontrolcontrol" msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Makefile" msgid "control" msgstr "Makefile" msgid "debian, directorychangelogchangelog" msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Makefile" msgid "changelog" msgstr "Makefile" msgid "debian, directorycopyrightcopyright" msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Makefile" msgid "copyright" msgstr "Makefile" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 8 dh_make; # Ref: $ ls debian/rules debian/control debian/changelog debian/copyright; # Ref: $ ls debian/*.ex; # Ref: $ ls debian/compat; # Ref: $ man 7 debhelper; #, fuzzy #| msgid "The dh_make command created a debian subdirectory with many files. Some are required, in particular rules, control, changelog and copyright. Files with the .ex extension are example files that can be used by modifying them (and removing the extension) when appropriate. When they are not needed, removing them is recommended. The compat file should be kept, since it is required for the correct functioning of the debhelper suite of programs (all beginning with the dh_ prefix) used at various stages of the package build process." msgid "The dh_make command created a debian subdirectory with many files. Some are required, in particular rules, control, changelog and copyright. Files with the .ex extension are example files that can be used by modifying them (and removing the extension) when appropriate. When they are not needed, removing them is recommended. The compat file is not used nor created anymore. Instead of defining the debhelper compatibility level as a number in this file, it is now defined as a build-dependency on the debhelper-compat virtual package in the Build-Depends file in debian/control." msgstr "dh_make コマンドによって debian サブディレクトリと各種ファイルが作成されました。特に rules、control、changelog、copyright などの一部のファイルは必須です。.ex 拡張子を持つファイルは例ファイルで、必要ならばこれらのファイルをひな形として (拡張子を削除して) 使うことが可能です。必要なければ例ファイルを削除することを推奨します。compat ファイルはそのままにしておくべきです。なぜなら、compat ファイルはパッケージビルド作業のさまざまな段階で使われる debhelper プログラムスイート (dh_ から始まるプログラム群) を適切に動作させるために必要だからです。" msgid "The copyright file must contain information about the authors of the documents included in the package, and the related copyright and license. In our case, these are internal documents and their use is restricted to within the Falcot Corp company. The default format used for this file is defined in the Format field. " msgstr "" msgid "The default changelog file is generally appropriate; replacing the “Initial release” with a more verbose explanation and changing the distribution from UNRELEASED or unstable to the target release name is enough." msgstr "" msgid "The control file must also be updated: the Section field can be changed to misc and the Homepage, Vcs-Git and Vcs-Browser fields were removed. The Depends fields was completed with firefox-esr | www-browser so as to ensure the availability of a web browser able to display the documents in the package. If the package does not require to run any commands as root (see ), the Rules-Requires-Root field can be left as is." msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "controlDepends, header field" msgstr "パッケージ種類" msgid "controlHomepage, header field" msgstr "" msgid "controlRules-Requires-Root, header field" msgstr "" msgid "controlSection, header field" msgstr "" msgid "controlVcs-Browser, header field" msgstr "" msgid "controlVcs-Git, header field" msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ ls debian/control; msgid "The control file" msgstr "control ファイル" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ cat debian/control; #, fuzzy #| msgid "" #| "\n" #| "Source: falcot-data\n" #| "Section: misc\n" #| "Priority: optional\n" #| "Maintainer: Raphael Hertzog <hertzog@debian.org>\n" #| "Build-Depends: debhelper (>= 9)\n" #| "Standards-Version: 3.9.5\n" #| "\n" #| "Package: falcot-data\n" #| "Architecture: all\n" #| "Depends: iceweasel | www-browser, ${misc:Depends}\n" #| "Description: Internal Falcot Corp Documentation\n" #| " This package provides several documents describing the internal\n" #| " structure at Falcot Corp. This includes:\n" #| " - organization diagram\n" #| " - contacts for each department.\n" #| " .\n" #| " These documents MUST NOT leave the company.\n" #| " Their use is INTERNAL ONLY." msgid "" "\n" "Build-Depends: debhelper-compat (= 13)\n" "Standards-Version: 4.5.1\n" "Rules-Requires-Root: no\n" "\n" "Package: falcot-data\n" "Architecture: all\n" "Depends: firefox-esr | www-browser, ${misc:Depends}\n" "Description: Internal Falcot Corp Documentation\n" " This package provides several documents describing the internal\n" " structure at Falcot Corp. This includes:\n" " - organization diagram\n" " - contacts for each department.\n" " .\n" " These documents MUST NOT leave the company.\n" " Their use is INTERNAL ONLY.\n" "]]>" msgstr "" "\n" "Source: falcot-data\n" "Section: misc\n" "Priority: optional\n" "Maintainer: Raphael Hertzog <hertzog@debian.org>\n" "Build-Depends: debhelper (>= 9)\n" "Standards-Version: 3.9.5\n" "\n" "Package: falcot-data\n" "Architecture: all\n" "Depends: iceweasel | www-browser, ${misc:Depends}\n" "Description: Internal Falcot Corp Documentation\n" " This package provides several documents describing the internal\n" " structure at Falcot Corp. This includes:\n" " - organization diagram\n" " - contacts for each department.\n" " .\n" " These documents MUST NOT leave the company.\n" " Their use is INTERNAL ONLY." # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ ls debian/changelog; msgid "The changelog file" msgstr "changelog ファイル" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ cat debian/changelog; #, fuzzy #| msgid "" #| "\n" #| "falcot-data (1.0) internal; urgency=low\n" #| "\n" #| " * Initial Release.\n" #| " * Let's start with few documents:\n" #| " - internal company structure;\n" #| " - contacts for each department.\n" #| "\n" #| " -- Raphael Hertzog <hertzog@debian.org> Fri, 04 Sep 2015 12:09:39 -0400" msgid "" " Sat, 26 Feb 2022 15:12:06 +0100\n" "]]>" msgstr "" "\n" "falcot-data (1.0) internal; urgency=low\n" "\n" " * Initial Release.\n" " * Let's start with few documents:\n" " - internal company structure;\n" " - contacts for each department.\n" "\n" " -- Raphael Hertzog <hertzog@debian.org> Sat, 05 Sep 2015 01:09:39 +0900" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ ls debian/copyright; msgid "The copyright file" msgstr "copyright ファイル" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ cat debian/copyright; #, fuzzy #| msgid "" #| "\n" #| "Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" #| "Upstream-Name: falcot-data\n" #| "\n" #| "Files: *\n" #| "Copyright: 2004-2015 Falcot Corp\n" #| "License: \n" #| " All rights reserved." msgid "" "\n" "Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" "Upstream-Name: falcot-data\n" "\n" "Files: *\n" "Copyright: 2004-2021 Falcot Corp\n" "License:\n" " All rights reserved." msgstr "" "\n" "Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" "Upstream-Name: falcot-data\n" "\n" "Files: *\n" "Copyright: 2004-2015 Falcot Corp\n" "License: \n" " All rights reserved." # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; msgid "BACK TO BASICS Makefile file" msgstr "BACK TO BASICS Makefile ファイル" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; msgid "Makefile" msgstr "Makefile" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debi; #, fuzzy #| msgid "debi" msgid "make" msgstr "debi" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 make; msgid "A Makefile file is a script used by the make program; it describes rules for how to build a set of files from each other in a tree of dependencies (for instance, a program can be built from a set of source files). The Makefile file describes these rules in the following format:" msgstr "Makefile ファイルは make プログラムによって使われるスクリプトであり、互いに依存関係を持つファイル群をビルドする規則を指定します (たとえば、複数のソースファイル群から 1 つのプログラムをビルドする規則を指定します)。Makefile ファイルはビルド規則を以下のフォーマットで指定します。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: http://www.gnu.org/software/make/manual/make.html#Rule-Introduction; msgid "" "\n" "target: source1 source2 ...\n" " command1\n" " command2" msgstr "" "\n" "target: source1 source2 ...\n" " command1\n" " command2" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: http://www.gnu.org/software/make/manual/make.html#Rule-Introduction; #, fuzzy #| msgid "The interpretation of such a rule is as follows: if one of the source* files is more recent than the target file, then the target needs to be generated, using command1 and command2." msgid "The basic interpretation of such a rule is as follows: if one of the source* files is more recent than the target file, then the target needs to be generated, using command1 and command2." msgstr "ビルド規則の解釈は以下の通り行われます。すなわち、source* ファイルの 1 つが target ファイルよりも新しい場合、command1 と command2 を使って target を生成します。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: http://www.gnu.org/software/make/manual/make.html#Errors; msgid "Note that the command lines must start with a tab character; also note that when a command line starts with a dash character (-), failure of the command does not interrupt the whole process." msgstr "コマンド行は必ずタブ文字で開始しなければいけない点に注意してください。さらに、コマンド行がダッシュ文字 (-) で始まる場合、そのコマンドが失敗しても全体のプロセスは停止されなくなる点に注意してください。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ ls debian/rules; # Ref: $ less /usr/share/dpkg/default.mk; msgid "The rules file usually contains a set of rules used to configure, build and install the software in a dedicated subdirectory (named after the generated binary package). The contents of this subdirectory is then archived within the Debian package as if it were the root of the filesystem. In our case, files will be installed in the debian/falcot-data/usr/share/falcot-data/ subdirectory, so that installing the generated package will deploy the files under /usr/share/falcot-data/. The rules file is used as a Makefile, with a few standard targets (including clean and binary, used respectively to clean the source directory and generate the binary package)." msgstr "rules ファイルには、(生成されるバイナリパッケージにちなんで名付けられた) 専用のサブディレクトリ内で対象のソフトウェアを設定、ビルド、インストールするために使われる一連の規則が定義されています。このサブディレクトリの内容はあたかもサブディレクトリがファイルシステムのルートであるかのように Debian パッケージの中に保存されます。今回の場合、ファイルは debian/falcot-data/usr/share/falcot-data/ サブディレクトリにインストールされます。こうすることで、生成されたパッケージをインストールするとファイルが /usr/share/falcot-data/ の下に配備されます。rules ファイルはいくつかの標準的なターゲットが定義されている Makefile として使われます (定義済みターゲットの clean と binary はそれぞれソースディレクトリを削除する場合とバイナリパッケージを生成する場合に使います)。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: https://www.debian.org/doc/manuals/maint-guide/dother.en.html#install; msgid "Although this file is the heart of the process, it increasingly contains only the bare minimum for running a standard set of commands provided by the debhelper tool. Such is the case for files generated by dh_make. To install our files, we simply configure the behavior of the dh_install command by creating the following debian/falcot-data.install file:" msgstr "rules ファイルはビルド作業の核心で、debhelper ツールによって提供される標準的なコマンド群を実行するために必要な最低限の要素だけを含みます。rules ファイルが面倒を見るのは dh_make によって生成されたファイルだけです。自分のファイルをインストールするためには、以下の debian/falcot-data.install ファイルを作成して、dh_install コマンドの挙動を単純に設定します。" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "dhdh_install" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: https://www.debian.org/doc/manuals/maint-guide/dother.en.html#install; msgid "" "\n" "data/* usr/share/falcot-data/" msgstr "" "\n" "data/* usr/share/falcot-data/" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "At this point, the package can be created. We will however add a lick of paint. Since the administrators want the documents to be easily accessed from the menus of graphical desktop environments, we add a falcot-data.desktop file and get it installed in /usr/share/applications by adding a second line to debian/falcot-data.install." msgid "At this point, the package can be created. We will, however, add a lick of paint. Since the administrators want the documents to be easily accessed from the menus of graphical desktop environments, we add a falcot-data.desktop file and get it installed in /usr/share/applications by adding a second line to debian/falcot-data.install." msgstr "この時点でパッケージを作成することも可能ですが、パッケージにもう少しファイルを追加します。管理者はグラフィカルデスクトップ環境のメニューから文書へ簡単にアクセスできるようにしたいので、パッケージに falcot-data.desktop ファイルを追加します。さらに debian/falcot-data.install に例に示した 2 行目を追加して、/usr/share/applications の中に falcot-data.desktop ファイルをインストールします。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Makefile" msgid ".desktop" msgstr "Makefile" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Makefile" msgid ".install" msgstr "Makefile" # Checked-By: Ryuunosuke Ayanokouzi; msgid "The falcot-data.desktop file" msgstr "falcot-data.desktop ファイル" # Checked-By: Ryuunosuke Ayanokouzi; msgid "" "\n" "[Desktop Entry]\n" "Name=Internal Falcot Corp Documentation\n" "Comment=Starts a browser to read the documentation\n" "Exec=x-www-browser /usr/share/falcot-data/index.html\n" "Terminal=false\n" "Type=Application\n" "Categories=Documentation;" msgstr "" "\n" "[Desktop Entry]\n" "Name=Internal Falcot Corp Documentation\n" "Comment=Starts a browser to read the documentation\n" "Exec=x-www-browser /usr/share/falcot-data/index.html\n" "Terminal=false\n" "Type=Application\n" "Categories=Documentation;" # Checked-By: Ryuunosuke Ayanokouzi; msgid "The updated debian/falcot-data.install looks like this:" msgstr "編集後の debian/falcot-data.install は以下のようになります。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "" "\n" "data/* usr/share/falcot-data/\n" "falcot-data.desktop usr/share/applications/" msgstr "" "\n" "data/* usr/share/falcot-data/\n" "falcot-data.desktop usr/share/applications/" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "Our source package is now ready. All that's left to do is to generate the binary package, with the same method we used previously for rebuilding packages: we run the dpkg-buildpackage -us -uc command from within the falcot-data-1.0 directory." msgid "Our source package is now ready. All that is left to do is to generate the binary package, with the same method we used previously for rebuilding packages: we run the dpkg-buildpackage -us -uc command from within the falcot-data-1.0 directory." msgstr "これでソースパッケージの準備が整いました。最後に残された作業は以前パッケージを再ビルドした際に使った方法と同じ方法を使ってバイナリパッケージを生成することです。具体的に言えば、バイナリパッケージを生成するには、falcot-data-1.0 ディレクトリの中で、dpkg-buildpackage -us -uc コマンドを実行します。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Creating a Package Repository for APT" msgstr "APT 用のパッケージリポジトリの作成" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "packagearchive" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; msgid "packageDebianarchive of" msgstr "パッケージDebianアーカイブ" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Falcot Corp gradually started maintaining a number of Debian packages either locally modified from existing packages or created from scratch to distribute internal data and programs." msgstr "Falcot Corp のメンテナンスする Debian パッケージの数は次第に増えました。この中には既存のパッケージから手元で修正したパッケージや、内部データとプログラムを配布するために最初から作成したパッケージなどがあります。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 5 sources.list; msgid "To make deployment easier, they want to integrate these packages in a package archive that can be directly used by APT. For obvious maintenance reasons, they wish to separate internal packages from locally-rebuilt packages. The goal is for the matching entries in a /etc/apt/sources.list.d/falcot.list file to be as follows:" msgstr "パッケージの配備を簡単にするために、管理者はこれらのパッケージを APT から直接使うことが可能なパッケージアーカイブに組み込みたいと思っています。明らかなメンテナンス上の理由により、管理者は内部パッケージと手元で再ビルドしたパッケージを別にしたいと思っています。すなわち、最終的に /etc/apt/sources.list.d/falcot.list ファイル内のエントリを以下のようにしたいと思っています。" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "APT/etc/apt/sources.list.d/" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 5 sources.list; msgid "" "\n" "deb http://packages.falcot.com/ updates/\n" "deb http://packages.falcot.com/ internal/" msgstr "" "\n" "deb http://packages.falcot.com/ updates/\n" "deb http://packages.falcot.com/ internal/" # Checked-By: Ryuunosuke Ayanokouzi; msgid "mini-dinstall" msgstr "mini-dinstall" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ grep -e '^Distribution: ' ../falcot-data_1.0_amd64.changes; # Ref: $ cat debian/changelog; # Ref: https://www.debian.org/doc/manuals/maint-guide/dreq.html; msgid "The administrators therefore configure a virtual host on their internal HTTP server, with /srv/vhosts/packages/ as the root of the associated web space. The management of the archive itself is delegated to the mini-dinstall command (in the similarly-named package). This tool keeps an eye on an incoming/ directory (in our case, /srv/vhosts/packages/mini-dinstall/incoming/) and waits for new packages there; when a package is uploaded, it is installed into a Debian archive at /srv/vhosts/packages/. The mini-dinstall command reads the *.changes file created when the Debian package is generated. These files contain a list of all other files associated with the version of the package (*.deb, *.dsc, *.diff.gz/*.debian.tar.gz, *.orig.tar.gz, or their equivalents with other compression tools), and these allow mini-dinstall to know which files to install. *.changes files also contain the name of the target distribution (often unstable) mentioned in the latest debian/changelog entry, and mini-dinstall uses this information to decide where the package should be installed. This is why administrators must always change this field before building a package, and set it to internal or updates, depending on the target location. mini-dinstall then generates the files required by APT, such as Packages.gz." msgstr "このため、管理者は内部 HTTP サーバ上に仮想ホストを設定して、APT リポジトリのルートとして /srv/vhosts/packages/ を割り当てます。パッケージアーカイブ自体の管理は mini-dinstall コマンド (同名のパッケージに含まれます) に委託されます。mini-dinstall ツールは incoming/ ディレクトリ (今回の場合、/srv/vhosts/packages/mini-dinstall/incoming/) を監視して、新しいパッケージがこのディレクトリにアップロードされることを待ちます。そしてパッケージがアップロードされたら、mini-dinstall は /srv/vhosts/packages/ のパッケージアーカイブにパッケージをインストールします。mini-dinstall コマンドは Debian パッケージが生成された時に作成される *.changes ファイルを読みます。*.changes ファイルには、パッケージのバージョンに対応するその他のファイル (*.deb、*.dsc、*.diff.gz/*.debian.tar.gz、*.orig.tar.gz、その他の圧縮ツールを使った場合の同等ファイル) のリストが書かれており、mini-dinstall はこのリストに従ってインストールするファイルを把握します。さらに *.changes ファイルの Distribution ヘッダフィールドには、debian/changelog ファイル内の最新エントリに書かれた対象ディストリビューションの名前 (通常 unstable) が書かれており、mini-dinstall はこの名前に従ってパッケージのインストール先を決めます。このため、管理者は対象パッケージをビルドする前に debian/changelog ファイル内の最新エントリに書かれた対象ディストリビューションの名前を必ず変更し、対象パッケージのインストール先に従ってその名前を internal または updates に設定しなければいけません。この後、mini-dinstall は APT が必要とする Packages.gz などのファイルを生成します。" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "ALTERNATIVE apt-ftparchive" msgid "ALTERNATIVE apt-ftparchive, aptly, and reprepro" msgstr "ALTERNATIVE apt-ftparchive" # Checked-By: Ryuunosuke Ayanokouzi; msgid "apt-ftparchive" msgstr "apt-ftparchive" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Tag: PTAL; msgid "If mini-dinstall seems too complex for your Debian archive needs, you can also use the apt-ftparchive command. This tool scans the contents of a directory and displays (on its standard output) a matching Packages file. In the Falcot Corp case, administrators could upload the packages directly into /srv/vhosts/packages/updates/ or /srv/vhosts/packages/internal/, then run the following commands to create the Packages.gz files:" msgstr "必要なパッケージアーカイブが mini-dinstall を使うほど複雑なパッケージアーカイブではない場合、apt-ftparchive コマンドを使うことも可能です。apt-ftparchive ツールは指定したディレクトリの内容を調査して、その内容に対応する Packages ファイルを (標準出力に) 表示します。apt-ftparchive を使う場合、Falcot Corp の管理者はパッケージを直接 /srv/vhosts/packages/updates/ や /srv/vhosts/packages/internal/ にアップロードすることが可能です。その後以下のコマンドを実行して Packages.gz ファイルを作成します。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; msgid "" "\n" "$ cd /srv/vhosts/packages\n" "$ apt-ftparchive packages updates >updates/Packages\n" "$ gzip updates/Packages\n" "$ apt-ftparchive packages internal >internal/Packages\n" "$ gzip internal/Packages" msgstr "" "\n" "$ cd /srv/vhosts/packages\n" "$ apt-ftparchive packages updates >updates/Packages\n" "$ gzip updates/Packages\n" "$ apt-ftparchive packages internal >internal/Packages\n" "$ gzip internal/Packages" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; msgid "The apt-ftparchive sources command allows creating Sources.gz files in a similar fashion." msgstr "apt-ftparchive sources コマンドを使えば、同様の方法で Sources.gz ファイルを作成することが可能です。" msgid "reprepro and aptly are more advanced tools for the same purpose. They can produce, manage and synchronize a number of package repositories, mirror other repositories, even cherry-pick packages from official repositories and provide them locally, create signatures of the generated package indices and thus provide signed repositories. reprepro stores packages and checksums in a Berkeley DB database file, so no database server is needed. aptly provides the same functionality, but it can be easier in handling. Unfortunately, both projects, although probably the most feature-rich solutions, are not actively developed at the moment." msgstr "" msgid "reprepro comes with a lot of documentation and examples in /usr/share/doc/reprepro/, while aptly has a vast online documentation. " msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 8 pbuilder; # Tag: L-CFMD; #, fuzzy #| msgid "pbuilder" msgid "reprepro" msgstr "pbuilder" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install dput; # Ref: $ man 1 dput; #, fuzzy #| msgid "dput" msgid "aptly" msgstr "dput" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 mini-dinstall; # Tag: L-CFMD; msgid "Configuring mini-dinstall requires setting up a ~/.mini-dinstall.conf file; in the Falcot Corp case, the contents are as follows:" msgstr "mini-dinstall を設定するには、~/.mini-dinstall.conf ファイルをセットアップする必要があります。Falcot Corp では以下の通り設定しました。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 mini-dinstall; # Tag: L-CFMD; msgid "" "\n" "[DEFAULT]\n" "archive_style = flat\n" "archivedir = /srv/vhosts/packages\n" "\n" "verify_sigs = 0\n" "mail_to = admin@falcot.com\n" "\n" "generate_release = 1\n" "release_origin = Falcot Corp\n" "release_codename = stable\n" "\n" "[updates]\n" "release_label = Recompiled Debian Packages\n" "\n" "[internal]\n" "release_label = Internal Packages" msgstr "" "\n" "[DEFAULT]\n" "archive_style = flat\n" "archivedir = /srv/vhosts/packages\n" "\n" "verify_sigs = 0\n" "mail_to = admin@falcot.com\n" "\n" "generate_release = 1\n" "release_origin = Falcot Corp\n" "release_codename = stable\n" "\n" "[updates]\n" "release_label = Recompiled Debian Packages\n" "\n" "[internal]\n" "release_label = Internal Packages" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: man 5 apt_preferences; # Tag: L-CFMD; msgid "One decision worth noting is the generation of Release files for each archive. This can help manage package installation priorities using the /etc/apt/preferences configuration file (see for details)." msgstr "各パッケージアーカイブに対して Release ファイルを作成することに決めた点は注目に値します。これは /etc/apt/preferences 設定ファイルを使ってパッケージインストール優先度を管理する場合に役立ちます (詳細はを参照してください)。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 mini-dinstall; # Tag: L-CFMD; msgid "SECURITY mini-dinstall and permissions" msgstr "SECURITY mini-dinstall とパーミッション" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 mini-dinstall; # Tag: L-CFMD; #, fuzzy #| msgid "Since mini-dinstall has been designed to run as a regular user, there's no need to run it as root. The easiest way is to configure everything within the user account belonging to the administrator in charge of creating the Debian packages. Since only this administrator has the required permissions to put files in the incoming/ directory, we can deduce that the administrator authenticated the origin of each package prior to deployment and mini-dinstall does not need to do it again. This explains the verify_sigs = 0 parameter (which means that signatures need not be verified). However, if the contents of packages are sensitive, we can reverse the setting and elect to authenticate with a keyring containing the public keys of persons allowed to create packages (configured with the extra_keyrings parameter); mini-dinstall will then check the origin of each incoming package by analyzing the signature integrated to the *.changes file." msgid "Since mini-dinstall has been designed to run as a regular user, there is no need to run it as root. The easiest way is to configure everything within the user account belonging to the administrator in charge of creating the Debian packages. Since only this administrator has the required permissions to put files in the incoming/ directory, we can deduce that the administrator authenticated the origin of each package prior to deployment and mini-dinstall does not need to do it again. This explains the verify_sigs = 0 parameter (which means that signatures need not be verified). However, if the contents of packages are sensitive, we can reverse the setting and elect to authenticate with a keyring containing the public keys of persons allowed to create packages (configured with the extra_keyrings parameter); mini-dinstall will then check the origin of each incoming package by analyzing the signature integrated to the *.changes file." msgstr "mini-dinstall は標準的なユーザとして実行されるように設計されています。root で実行される必要はありません。最も簡単な方法は Debian パッケージ作成担当の管理者グループに所属するユーザアカウントを使ってすべてを設定することです。incoming/ ディレクトリへファイルを追加するために必要な権限を与えられているのは Debian パッケージ作成担当の管理者だけなので、パッケージを追加する前に各パッケージの出自の確認は済んでいると考えられますし、mini-dinstall を使ってもう一度パッケージの出自を確認する必要もなくなります。この理由により、パラメータ verify_sigs = 0 が設定されています (これは mini-dinstall が署名を確認する必要がないことを意味します)。しかしながら、パッケージの内容が機密に関わるものであれば、この設定を逆にして、パッケージ作成担当者の公開鍵を含む鍵束 (extra_keyrings パラメータを使って設定されます) を使ってパッケージの出自を確認するように設定することが可能です。そしてこのように設定した場合、mini-dinstall は *.changes ファイルに統合された署名を解析することによってアップロードされた各パッケージの出自を確認します。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 mini-dinstall; # Tag: L-CFMD; msgid "Invoking mini-dinstall actually starts a daemon in the background. As long as this daemon runs, it will check for new packages in the incoming/ directory every half-hour; when a new package arrives, it will be moved to the archive and the appropriate Packages.gz and Sources.gz files will be regenerated. If running a daemon is a problem, mini-dinstall can also be manually invoked in batch mode (with the -b option) every time a package is uploaded into the incoming/ directory. Other possibilities provided by mini-dinstall are documented in its mini-dinstall 1 manual page." msgstr "mini-dinstall を実行すると、バックグラウンドでデーモンが開始されます。mini-dinstall デーモンが実行されている限り、デーモンは 30 分ごとに incoming/ ディレクトリにアップロードされた新しいパッケージを確認します。そして新しいパッケージがアップロードされると、パッケージはパッケージアーカイブに移動され、適切な Packages.gz と Sources.gz ファイルが再生成されます。デーモンの実行に問題がある場合、incoming/ ディレクトリにパッケージをアップロードしたら毎回、手作業で mini-dinstall をバッチモードで実行します (-b オプションを付けます)。mini-dinstall 他の使い方は mini-dinstall 1 マニュアルページで説明されています。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "EXTRA Generating a signed archive" msgstr "EXTRA 署名済みパッケージアーカイブの生成" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 mini-dinstall; # Tag: L-CFMD; # Tag: PTAL; msgid "The APT suite checks a chain of cryptographic signatures on the packages it handles before installing them, in order to ensure their authenticity (see ). Private APT archives can then be a problem, since the machines using them will keep displaying warnings about unsigned packages. A diligent administrator will therefore integrate private archives with the secure APT mechanism." msgstr "APT スイートは対象のパッケージをインストールする前にそのパッケージに含まれる一連の暗号署名を確認し、そのパッケージの信頼性を確かめます (を参照してください)。この挙動はプライベートパッケージアーカイブにとって問題です。なぜなら、プライベートパッケージアーカイブを使うマシンでは署名されていないパッケージに関する警告が表示され続けるからです。プライベートパッケージアーカイブを安全な APT メカニズムに適合させるのが真面目な管理者の仕事と言えます。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 mini-dinstall; # Tag: L-CFMD; # Tag: PTAL; msgid "To help with this process, mini-dinstall includes a release_signscript configuration option that allows specifying a script to use for generating the signature. A good starting point is the sign-release.sh script provided by the mini-dinstall package in /usr/share/doc/mini-dinstall/examples/; local changes may be relevant." msgstr "パッケージアーカイブの署名作業を助けるために、mini-dinstall には Release に対する署名の生成に使うスクリプトを指定する release_signscript 設定オプションが含まれます。ここでは mini-dinstall パッケージによって提供された /usr/share/doc/mini-dinstall/examples/ 内に含まれる sign-release.sh スクリプトが良い足掛かりとなるでしょう。しかし、このスクリプトを使うには手元で修正が必要になるかもしれません。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Becoming a Package Maintainer" msgstr "パッケージメンテナになる" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "packagemaintainer" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "packagenew maintainer" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "maintainerpackage maintainer" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Learning to Make Packages" msgstr "パッケージを作るための知識" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "packagecreation" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "Creating a quality Debian package is not always a simple task, and becoming a package maintainer takes some learning, both with theory and practice. It's not a simple matter of building and installing software; rather, the bulk of the complexity comes from understanding the problems and conflicts, and more generally the interactions, with the myriad of other packages available." msgid "Creating a quality Debian package is not always a simple task, and becoming a package maintainer takes some learning, both with theory and practice in technical and legal matters. It is not a simple matter of building and installing software; rather, the bulk of the complexity comes from understanding the problems and conflicts, and more generally the interactions, with the myriad of other packages available." msgstr "上質な Debian パッケージを作成する作業が常に簡単な作業であるとは限りません。パッケージメンテナになるためには理論と実践の両方の知識が必要です。上質な Debian パッケージを作成する作業は単純にソフトウェアをビルドしたりインストールするだけの簡単な作業ではありません。むしろ複雑さの大部分は他の無数の利用できるパッケージとの問題と対立 (より一般には相関性) を理解することに由来します。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Rules" msgstr "規則" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "packagepolicy" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "DebianPolicy" msgstr "パッケージ種類" msgid "controlStandards-Version, header field" msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "A Debian package must comply with the precise rules compiled in the Debian policy, and each package maintainer must know them. There is no requirement to know them by heart, but rather to know they exist and to refer to them whenever a choice presents a non-trivial alternative. Every Debian maintainer has made mistakes by not knowing about a rule, but this is not a huge problem as long as the error gets fixed when a user reports it as a bug report (which tends to happen fairly soon thanks to advanced users). " msgid "A Debian package must comply with the precise rules compiled in the Debian policy, and each package maintainer must know them. There is no requirement to know them by heart, but rather to know they exist and to refer to them whenever a choice presents a non-trivial alternative. Every Debian maintainer has made mistakes by not knowing about a rule, but this is not a huge problem as long as the error gets fixed when a user reports it as a bug report (which tends to happen fairly soon thanks to advanced users). The Standards-Version field in debian/control specifies the version of the Debian policy with which a package complies. Maintainers should comply to the latest version of the Debian policy. " msgstr "Debian パッケージは必ず Debian ポリシーにまとめられた明確な規則に従わなければいけません。各パッケージメンテナはこの規則を知らなければいけません。規則を暗記する必要はありませんが、規則の存在を知り、重要な判断を下す局面では常に規則を参照する必要があります。すべての Debian メンテナは規則をよく知らないことが原因で間違いを犯した経験がありますが、その間違いがバグ報告として報告されて修正される限り (熟練ユーザのおかげでバグ報告はかなり素早く報告されることが多いです)、これは大きな問題ではありません。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Procedures" msgstr "手続き" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "DebianDeveloper's Reference" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "packagedeveloper's reference" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Debian is not a simple collection of individual packages. Everyone's packaging work is part of a collective project; being a Debian developer involves knowing how the Debian project operates as a whole. Every developer will, sooner or later, interact with others. The Debian Developer's Reference (in the developers-reference package) summarizes what every developer must know in order to interact as smoothly as possible with the various teams within the project, and to take the best possible advantages of the available resources. This document also enumerates a number of duties a developer is expected to fulfill. " msgstr "Debian は各パッケージを単純に収集しているだけではありません。全員のパッケージング作業は共同プロジェクトの一部です。そして Debian 開発者になるには、Debian プロジェクトが全体としてどのように運営されているかを知る必要があります。すべての Debian 開発者は遅かれ早かれ他人と協力して行動することになるでしょう。Debian 開発者リファレンス (developers-reference パッケージに含まれます) では、プロジェクト内のさまざまなチームと可能な限り円滑に一緒に作業を行ったり利用できる資源を大いに活用するためにすべての開発者が必ず知らなければいけないことを要約しています。また、Debian 開発者リファレンスは管理者が果たすべき数多くの義務も列挙しています。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Tools" msgstr "ツール" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Many tools help package maintainers in their work. This section describes them quickly, but does not give the full details, since they all have comprehensive documentation of their own." msgstr "パッケージメンテナの作業を手助けする数多くのツールが存在します。この節では、それらのツールを簡単に説明します (詳細は説明しません)。なぜなら、これらのツールには自分自身を解説する総合的な文書が用意されているからです。" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "packagetools" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; msgid "devscripts" msgstr "devscripts" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debchange; msgid "dch" msgstr "dch" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 uscan; msgid "uscan" msgstr "uscan" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debi; msgid "debi" msgstr "debi" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debc; msgid "debc" msgstr "debc" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debi; #, fuzzy #| msgid "debi" msgid "bts" msgstr "debi" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install devscripts; msgid "The devscripts package contains many programs helping with a wide array of a Debian developer's job:" msgstr "devscripts パッケージには、Debian 開発者が行う作業の大部分に対する手助けを行う数多くのプログラムが含まれます。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debuild; # Ref: $ man 1 lintian; # Ref: $ man 1 dpkg-buildpackage; msgid "debuild allows generating a package (with dpkg-buildpackage) and running lintian to check its compliance with the Debian policy afterwards." msgstr "debuild を使うことで、(dpkg-buildpackage から) パッケージを生成したり、Debian ポリシーへの遵守を確認するために後から lintian を実行することが可能です。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debclean; msgid "debclean cleans a source package after a binary package has been generated." msgstr "debclean を使うことで、バイナリパッケージを生成した後にソースパッケージの後片付けをすることが可能です。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debchange; msgid "dch allows quick and easy editing of a debian/changelog file in a source package." msgstr "dch を使うことで、素早く簡単にソースパッケージ中の debian/changelog ファイルを編集することが可能です。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 uscan; msgid "uscan checks whether a new version of a software has been released by the upstream author; this requires a debian/watch file with a description of the location of such releases." msgstr "uscan を使うことで、上流開発者がソフトウェアの新しいバージョンをリリースしたか否かを確認することが可能です。確認を行うにはリリースの場所が書かれた debian/watch ファイルが必要です。" msgid "debian, directorywatch" msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debi; msgid "debi allows installing (with dpkg -i) the Debian package that was just generated without the need to type its full name and path." msgstr "debi を使うことで、Debian パッケージを生成した直後に (dpkg -i を使って) そのパッケージをインストールすることが可能になります。パッケージの完全な名前やパスを指定する必要はありません。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debc; msgid "In a similar fashion, debc allows scanning the contents of the recently-generated package (with dpkg -c), without needing to type its full name and path." msgstr "debc を使うことで、Debian パッケージを生成した直後に (dpkg -c を使って) そのパッケージの内容を調査することが可能です。パッケージの完全な名前やパスを指定する必要はありません。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 bts; #, fuzzy #| msgid "bts controls the bug tracking system from the command line; this program automatically generates the appropriate emails." msgid "bts controls the bug tracking system from the command line; this program automatically generates the appropriate emails. " msgstr "bts を使うことで、コマンドラインからバグ追跡システムを制御することが可能です。bts プログラムは適切なメールを自動的に生成します。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debrelease; msgid "debrelease uploads a recently-generated package to a remote server, without needing to type the full name and path of the related .changes file." msgstr "debrelease を使うことで、Debian パッケージを生成した直後にそのパッケージをリモートサーバにアップロードすることが可能です。関連する .changes ファイルの完全な名前やパスを指定する必要はありません。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Makefile" msgid ".changes" msgstr "Makefile" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debsign; msgid "debsign signs the *.dsc and *.changes files." msgstr "debsign を使うことで、*.dsc と *.changes ファイルに署名することが可能です。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 uupdate; msgid "uupdate automates the creation of a new revision of a package when a new upstream version has been released." msgstr "uupdate を使うことで、新しい上流開発版がリリースされた場合にパッケージの新しい修正版の作成を自動化することが可能です。" msgid "All of the mentioned commands are documented in their respective manual pages. They can further be configured per user in one file: ~/.devscripts." msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install debhelper; # Ref: # apt-get install dh-make; msgid "debhelper and dh-make" msgstr "debhelper と dh-make" # Checked-By: Ryuunosuke Ayanokouzi; msgid "debhelper" msgstr "debhelper" # Checked-By: Ryuunosuke Ayanokouzi; msgid "dh-make" msgstr "dh-make" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debchange; #, fuzzy #| msgid "dch" msgid "dh" msgstr "dch" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "debianrules" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Debhelper is a set of scripts easing the creation of policy-compliant packages; these scripts are invoked from debian/rules. Debhelper has been widely adopted within Debian, as evidenced by the fact that it is used by the majority of official Debian packages. All the commands it contains have a dh_ prefix." msgid "Debhelper is a set of scripts easing the creation of policy-compliant packages; these scripts are invoked from debian/rules. Debhelper has been widely adopted within Debian, as evidenced by the fact that it is used by the majority of official Debian packages. All the commands it contains have a dh_ prefix. Each of them is documented in a manual page. The different compatibility levels and common options are described in debhelper 7." msgstr "debhelper はポリシーを遵守するパッケージの作成を簡単にするスクリプト群です。これらのスクリプトは debian/rules から呼び出されます。大多数の公式 Debian パッケージが debhelper を使っているという事実からも分かる通り、debhelper は Debian の中で広く採用されています。debhelper から提供されるすべてのコマンドは名前の頭に dh_ が付けられています。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 8 dh_make; # Ref: # apt-get install dh-make; msgid "The dh_make script (in the dh-make package) creates files required for generating a Debian package in a directory initially containing the sources for a piece of software. As can be guessed from the name of the program, the generated files use debhelper by default." msgstr "dh_make スクリプト (dh-make パッケージに含まれます) はソフトウェアのソースが含まれるディレクトリ内に Debian パッケージを生成するために必要なファイルを作成します。dh_make という名前から推測される通り、生成されたファイルはデフォルトで debhelper を使います。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 lintian; # Tag: L-CFMD; #, fuzzy #| msgid "The lintian Program" msgid "lintian" msgstr "lintian プログラム" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 lintian; # Tag: L-CFMD; msgid "lintian" msgstr "lintian" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "packagechecker" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 lintian; # Tag: L-CFMD; #, fuzzy #| msgid "This tool is one of the most important: it's the Debian package checker. It is based on a large array of tests created from the Debian policy, and detects quickly and automatically many errors that can then be fixed before packages are released." msgid "This tool is one of the most important: it is the Debian package checker. It is based on a large array of tests created from the Debian policy, and detects quickly and automatically many errors that can then be fixed before packages are released." msgstr "lintian は最も重要なツールの 1 つです。すなわち、lintian は Debian パッケージをチェックするツールです。lintian は Debian ポリシーから作成された大量のテスト群に基づき、多くのエラーを素早く自動的に検出します。lintian を使うことで、パッケージのリリース前に多くのエラーを修正することが可能となります。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 lintian; # Tag: L-CFMD; msgid "This tool is only a helper, and it sometimes gets it wrong (for instance, since the Debian policy changes over time, lintian is sometimes outdated). It is also not exhaustive: not getting any Lintian error should not be interpreted as a proof that the package is perfect; at most, it avoids the most common errors." msgstr "lintian の情報は参考程度にしかならず、間違いを犯すこともあります (たとえば、Debian ポリシーは常に変わるものなので、しばしば lintian は時代遅れになることがあります)。また、lintian は徹底的な調査を行いません。すなわち、lintian がエラーを出さないことを理由に対象のパッケージが完全であると結論付けてはいけません。lintian を使ってわかることはせいぜい最も一般的な間違いを犯していないことだけです。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 piuparts; # Tag: L-CFMD; #, fuzzy #| msgid "The piuparts Program" msgid "piuparts" msgstr "piuparts プログラム" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 piuparts; # Tag: L-CFMD; msgid "piuparts" msgstr "piuparts" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 1 piuparts; # Tag: L-CFMD; msgid "This is another important tool: it automates the installation, upgrade, removal and purge of a package (in an isolated environment), and checks that none of these operations leads to an error. It can help in detecting missing dependencies, and it also detects when files are incorrectly left over after the package got purged." msgstr "piuparts もまた重要なツールの 1 つです。すなわち、piuparts は (隔離環境の中で) パッケージのインストール、アップグレード、削除、完全削除の作業を自動化し、これらの作業中にエラーが起きないことを確認します。piuparts は不足している依存関係を検出したり、パッケージが完全削除された後にファイルが誤って残されたことを検出したりする際にも役立ちます。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install devscripts; #, fuzzy #| msgid "devscripts" msgid "autopkgtest" msgstr "devscripts" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "dh-make" msgid "autopkgtest" msgstr "dh-make" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "packagetests" msgstr "パッケージ種類" msgid "autopkgtest runs tests on binary packages, using the tests supplied in the source package in debian/tests/. Several commands allow the easy creation of chrooted or virtual test environments." msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install devscripts; #, fuzzy #| msgid "devscripts" msgid "reprotest" msgstr "devscripts" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "debhelper" msgid "reprotest" msgstr "debhelper" msgid "reprotest builds the same source code twice in different environments, and then checks the binaries produced by each build for differences. If any are found, then diffoscope (if unavailable, diff) is used to display them in detail for later analysis." msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debchange; #, fuzzy #| msgid "dch" msgid "diffoscope" msgstr "dch" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install dupload; # Ref: $ man 1 dupload; # Ref: # apt-get install dput; # Ref: $ man 1 dput; msgid "dupload and dput" msgstr "dupload と dput" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install dupload; # Ref: $ man 1 dupload; msgid "dupload" msgstr "dupload" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install dput; # Ref: $ man 1 dput; msgid "dput" msgstr "dput" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 dupload; # Ref: $ man 1 dput; #, fuzzy #| msgid "The dupload and dput commands allow uploading a Debian package to a (possibly remote) server. This allows developers to publish their package on the main Debian server (ftp-master.debian.org) so that it can be integrated to the archive and distributed by mirrors. These commands take a *.changes file as a parameter, and deduce the other relevant files from its contents." msgid "The dupload and dput commands allow uploading a Debian package to a (possibly remote) server. This allows developers to publish their package on the main Debian server (ftp-master.debian.org) so that it can be integrated to the archive and distributed by mirrors. These commands take a .changes file as a parameter, and deduce the other relevant files from its contents." msgstr "dupload と dput コマンドを使うことで、Debian パッケージを (場合によってはリモート) サーバにアップロードすることが可能です。dupload と dput コマンドを使うことで、開発者は主たる Debian サーバ (ftp-master.debian.org) 上に自分のパッケージを公開することが可能です。こうすることで、パッケージはパッケージアーカイブに組み込まれ、アーカイブミラーによって配布されます。dupload と dput コマンドは *.changes ファイルをパラメータとして受け取り、*.changes ファイルの内容から他の関連するファイルを推測します。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install debhelper; # Ref: # apt-get install dh-make; #, fuzzy #| msgid "debhelper and dh-make" msgid "git-buildpackage and dgit" msgstr "debhelper と dh-make" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install devscripts; #, fuzzy #| msgid "devscripts" msgid "git-buildpackage" msgstr "devscripts" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: # apt-get install devscripts; #, fuzzy #| msgid "devscripts" msgid "dgit" msgstr "devscripts" msgid "The project has been using various version control systems over the years to store packaging efforts or package source code, or allow collaborative package maintenance. In an effort to unify the systems and efforts, it was ultimately decided in 2017 to move (almost) all package sources into Git () onto a Gitlab instance called salsa.debian.org. " msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Build-Depends, control field" msgid "salsa.debian.org" msgstr "Build-Depends、コントロールフィールド" msgid "To make packaging using Git easier for Debian developers, tools have been developed. These allow not only to store the packaging files in Git, but also to use the Git repositories (and their history) of software projects, put patches applied to package sources into Git history, maintain software versions per distribution, etc." msgstr "" msgid "One of the most famous packages is git-buildpackage. An alternative is dgit. Of course it is still possible to use neither of those." msgstr "" msgid "Below is an example for a ~/.gbp.conf configuration file" msgstr "" msgid "" "" msgstr "" msgid "Building the package is then as easy as running gbp buildpackage in the Git tree. It will start a package build in a Debian Bullseye chroot using sbuild. When the build succeeds, the created files are checked running the autopkgtest-testsuite (if defined). All the various options are explained in gbp.conf 5 and /etc/git-buildpackage/gbp.conf." msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ man 1 debi; #, fuzzy #| msgid "debi" msgid "gbp" msgstr "debi" msgid "/etc/etc/git-buildpackage/gbp.conf" msgstr "" msgid "All the tools mentioned so far have been included in the continuous integration (CI) process in the salsa.debian.org instance as well: " msgstr "" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Acceptance Process" msgstr "受け入れ過程" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "DebianDeveloper" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; #, fuzzy #| msgid "Build-Depends, control field" msgid "nm.debian.org" msgstr "Build-Depends、コントロールフィールド" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Becoming a “Debian developer” is not a simple administrative matter. The process comprises several steps, and is as much an initiation as it is a selection process. In any case, it is formalized and well-documented, so anyone can track their progression on the website dedicated to the new member process. " msgstr "「Debian 開発者」になることは単なる管理上の手続きを経るだけの問題ではありません。受け入れ過程は複数の段階から成り、選考過程に匹敵する入会儀式と言えます。いかなる場合も、受け入れ過程は形式化され明確に文書化されています。そのため、誰でも新メンバー過程専用のウェブサイト上で進み具合を追跡することが可能です。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "EXTRA Lightweight process for “Debian Maintainers”" msgstr "EXTRA 「Debian メンテナ」向けの簡単なプロセス" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "DebianMaintainer" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; msgid "“Debian Maintainer” is another status that gives less privileges than “Debian developer” but whose associated process is quicker. With this status, the contributors can maintain their own packages only. A Debian developer only needs to perform a check on an initial upload, and issue a statement to the effect that they trust the prospective maintainer with the ability to maintain the package on their own." msgstr "「Debian メンテナ」とはもう一つの地位です。「Debian メンテナ」に与えられる特権は「Debian 開発者」よりも低いものですが、「Debian メンテナ」になるためのプロセスは「Debian 開発者」になるためのものよりも短い時間ですみます。「Debian メンテナ」の地位を持っている貢献者がメンテナンスできるのは自分自身のパッケージだけです。あなたが「Debian メンテナ」になりたいならば、少なくとも一人以上の Debian 開発者から最初のアップロードに対する確認を受ける必要があります。そして、あなたが自ら進んでパッケージをメンテナンスする能力を持つ見込みあるメンテナであるという点について、その Debian 開発者から信用されなければいけません。さらに、Debian 開発者があなたを信用するということについて声明を発表する必要があります。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Prerequisites" msgstr "必要条件" # Checked-By: Ryuunosuke Ayanokouzi; msgid "All candidates are expected to have at least a working knowledge of the English language. This is required at all levels: for the initial communications with the examiner, of course, but also later, since English is the preferred language for most of the documentation; also, package users will be communicating in English when reporting bugs, and they will expect replies in English." msgstr "すべての候補者は少なくとも実務に役立つ英語力を持つことを期待されます。英語力はすべての段階で要求されます。たとえば試験官に対する最初の連絡はもちろんその後も必要です。なぜなら、英語はほとんどの文書で推奨される言語だからです。また、パッケージのユーザはバグを報告する際に英語で連絡を取るでしょうし、ユーザは英語で返信をもらうことを期待するでしょう。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "The other prerequisite deals with motivation. Becoming a Debian developer is a process that only makes sense if the candidate knows that their interest in Debian will last for many months. The acceptance process itself may last for several months, and Debian needs developers for the long haul; each package needs permanent maintenance, and not just an initial upload." msgstr "もう一つの必要条件は意欲です。Debian 開発者の受け入れ過程に出願することが合理的な行為と考えられるのは候補者が Debian に対する自分の関心が何カ月も続くことを理解している場合に限ります。受け入れ過程は数カ月間続き、開発者として受け入れられた暁には Debian から長期にわたる苦労を要求されます。すなわち、それぞれのパッケージに対する永久的なメンテナンスが要求され、一回だけアップロードすればメンテナンスを終わらせられるというわけではありません。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Registration" msgstr "登録" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "packagesponsor" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; msgid "The first (real) step consists in finding a sponsor or advocate; this means an official developer willing to state that they believe that accepting X would be a good thing for Debian. This usually implies that the candidate has already been active within the community, and that their work has been appreciated. If the candidate is shy and their work is not publicly touted, they can try to convince a Debian developer to advocate them by showing their work in a private way." msgstr "候補者が最初に (現実的な意味で) やることは保証人か支持者を見つけることです。そしてこれは公式の開発者が候補者を受け入れることが Debian のためになると信じていると喜んで宣言すること意味します。通常これは候補者が既にコミュニティ内で活発に活動し続けており、候補者の業績が受け入れられ続けていることを暗黙的に意味します。候補者が遠慮がちで候補者の業績が公に注目されていなければ、候補者は Debian 開発者に対して個人的な方法で自分の業績を明らかにして自分を支持することを納得するように試みることが可能です。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "key pair" msgstr "鍵ペア" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: https://wiki.debian.org/DebianMaintainer; # Ref: https://wiki.debian.org/Keysigning; # Ref: https://www.debian.org/events/keysigning; # Ref: $ man 1 gpg; msgid "At the same time, the candidate must generate a public/private RSA key pair with GnuPG, which should be signed by at least two official Debian developers. The signature authenticates the name on the key. Effectively, during a key signing party, each participant must show an official identification (usually an ID card or passport) together with their key identifiers. This step confirms the link between the human and the keys. This signature thus requires meeting in real life. If you have not yet met any Debian developers in a public free software conference, you can explicitly seek developers living nearby using the list on the following webpage as a starting point. " msgstr "同時に、候補者は GnuPG を使って RSA 公開鍵と秘密鍵のペアを生成しなければいけません。候補者の公開鍵は少なくとも 2 人の公式 Debian 開発者の秘密鍵によって署名されるべきです。この署名は候補者の公開鍵に書かれた名前が本物であることを証明するものです。実質的なことを言えば、候補者はキーサインパーティで公式 Debian 開発者に直接会って、自分の公開鍵を公式 Debian 開発者の秘密鍵によって署名してもらう必要があります。キーサインパーティの参加者は鍵 ID と一緒に必ず公式の身分証明書 (通常 ID カードかパスポート) を提示しなければいけません。これは人と鍵の関連付けを確認するために必要な措置です。候補者が公のフリーソフトウェアカンファレンスで公式 Debian 開発者に直接会っていない場合、候補者は以下のウェブページに載っているリストを足掛かりとして、近くに住んでいる開発者を探すことが可能です。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: https://www.debian.org/devel/join/nm-amchecklist; msgid "Once the registration on nm.debian.org has been validated by the advocate, an Application Manager is assigned to the candidate. The application manager will then drive the process through multiple pre-defined steps and checks." msgstr "候補者の支持者が nm.debian.org 上の登録内容の正当性を認めたら、対象の候補者に対して 1 人の応募管理者が割り当てられます。応募管理者は複数の事前に定義された段階と確認を通じて作業を進めます。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: https://www.debian.org/devel/join/nm-amchecklist; msgid "The first verification is an identity check. If you already have a key signed by two Debian developers, this step is easy; otherwise, the application manager will try and guide you in your search for Debian developers close by to organize a meet-up and a key signing." msgstr "最初の妥当性確認事項は候補者の本人確認です。既に 2 人の Debian 開発者が自分の秘密鍵で候補者の公開鍵に署名しているならば、この段階は簡単です。そうでなければ、応募管理者はあなたに対して、近くにいる Debian 開発者を探し、直接会ってキーサインする段取りを付けるように指導するでしょう。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Accepting the Principles" msgstr "原則の受け入れ" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: https://www.debian.org/devel/join/nm-amchecklist; msgid "These administrative formalities are followed by philosophical considerations. The point is to make sure that the candidate understands and accepts the social contract and the principles behind Free Software. Joining Debian is only possible if one shares the values that unite the current developers, as expressed in the founding texts (and summarized in )." msgstr "次の管理上の手続きでは哲学の検討を行います。ここで、候補者は社会契約とフリーソフトウェアの背後にある原理を理解して受け入れることに対して確認を取られます。Debian に参加するには、必ず創設理念 (および) で述べられている現在の開発者を団結させている価値に共感する必要があります。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: https://www.debian.org/devel/join/nm-amchecklist; msgid "In addition, each candidate wishing to join the Debian ranks is expected to know the workings of the project, and how to interact appropriately to solve the problems they will doubtless encounter as time passes. All of this information is generally documented in manuals targeting the new maintainers, and in the Debian developer's reference. An attentive reading of this document should be enough to answer the examiner's questions. If the answers are not satisfactory, the candidate will be informed. They will then have to read (again) the relevant documentation before trying again. In the cases where the existing documentation does not contain the appropriate answer for the question, the candidate can usually reach an answer with some practical experience within Debian, or potentially by discussing with other Debian developers. This mechanism ensures that candidates get involved somewhat in Debian before becoming a full part of it. It is a deliberate policy, by which candidates who eventually join the project are integrated as another piece of an infinitely extensible jigsaw puzzle." msgstr "加えて、Debian に参加したいと思っている各候補者はプロジェクトの仕組みと時間がたてば間違いなく直面するであろう問題を解決する際に適切に相互協力する方法を知ることを期待されます。これらに関するすべての情報は新しいメンテナ向けのマニュアルと Debian 開発者リファレンスの中で大ざっぱに説明されています。応募管理者からの質問に答えるには、これらの文書を注意深く読むだけで十分です。回答が不十分な場合、候補者はその旨通知されます。候補者は再試験を受ける前に関連する文書を (もう一度) 読まなければいけません。既存の文書に質問に対する適切な回答が含まれなかった場合、候補者は Debian 内の実務経験を使うか他の Debian 開発者との議論を通じて回答を作成しても構いません。このメカニズムによって、候補者が Debian のすべての部分に参加する前に一部分だけに参加することが保証されます。これは慎重な方針です。この方針によって最終的に Debian プロジェクトに参加する候補者は永久的に広がるジグソーパズルにそのピースの 1 つとして組み込まれます。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: https://www.debian.org/devel/join/nm-amchecklist; msgid "This step is usually known as the Philosophy & Procedures (P&P for short) in the lingo of the developers involved in the new member process." msgstr "この段階は新メンバー過程に参加する開発者の間で使われる用語の Philosophy & Procedures (略して P&P、哲学と手順) として知られています。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: https://www.debian.org/devel/join/nm-amchecklist; msgid "Philosophy & Procedures" msgstr "Philosophy & Procedures" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: https://www.debian.org/devel/join/nm-amchecklist; msgid "Checking Skills" msgstr "能力の確認" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: https://www.debian.org/devel/join/nm-amchecklist; msgid "Each application to become an official Debian developer must be justified. Becoming a project member requires showing that this status is legitimate, and that it facilitates the candidate's job in helping Debian. The most common justification is that being granted Debian developer status eases maintenance of a Debian package, but it is not the only one. Some developers join the project to contribute to porting to a specific architecture, others want to improve documentation, and so on." msgstr "公式 Debian 開発者の受け入れ過程への出願は理に適ったものでなければいけません。プロジェクトメンバーになるには、候補者はプロジェクトメンバーの地位を得ることが合理的な要求であり、プロジェクトメンバーの地位を得ることで Debian の手助けに関する自分の作業が容易になることを示す必要があります。最も一般的な理由付けは Debian 開発者の地位が Debian パッケージのメンテナンスを簡単にするというものです。しかしこれは唯一の理由ではありません。特定のアーキテクチャへの移植に貢献するためにプロジェクトに参加している開発者もいれば、文書を改良したいと思ってプロジェクトに参加している開発者もいます。" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: https://www.debian.org/devel/join/nm-amchecklist; msgid "This step represents the opportunity for the candidate to state what they intend to do within the Debian project and to show what they have already done towards that end. Debian is a pragmatic project and saying something is not enough, if the actions do not match what is announced. Generally, when the intended role within the project is related to package maintenance, a first version of the prospective package will have to be validated technically and uploaded to the Debian servers by a sponsor among the existing Debian developers." msgstr "この段階で、候補者は Debian プロジェクトの中で自分が何をしたいと思っているのか宣言し、その目的のために自分がこれまで何をしてきたか示す機会を与えられます。Debian は実用主義的なプロジェクトで、やっていることが言っていることと食い違っている場合、言うだけでは不十分です。一般的に言って、プロジェクト内で希望する役割がパッケージメンテナンスに関連する場合、候補となっているパッケージの最初のバージョンは必ず技術的な正当性を確認され、既存の Debian 開発者から選ばれた保証人によって Debian サーバにアップロードされることでしょう。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "COMMUNITY Sponsoring" msgstr "COMMUNITY パッケージの支援" # Checked-By: Ryuunosuke Ayanokouzi; msgid "sponsoring" msgstr "パッケージの支援" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "DebianNew Member" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Debian developers can “sponsor” packages prepared by someone else, meaning that they publish them in the official Debian repositories after having performed a careful review. This mechanism enables external persons, who have not yet gone through the new member process, to contribute occasionally to the project. At the same time, it ensures that all packages included in Debian have always been checked by an official member." msgstr "Debian 開発者は誰かによって用意されたパッケージを「支援」することが可能です。これは注意深く調査した後に Debian 開発者が公式の Debian リポジトリの中でパッケージを公開することを意味します。このメカニズムのおかげで、まだ新メンバー過程を通過していない外部の人も時折 Debian プロジェクトに貢献することが可能になります。同時に、Debian に含まれるすべてのパッケージは常に公式メンバーによって確認されていることが保証されます。" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "Finally, the examiner checks the candidate's technical (packaging) skills with a detailed questionnaire. Bad answers are not permitted, but the answer time is not limited. All the documentation is available and several tries are allowed if the first answers are not satisfactory. This step does not intend to discriminate, but to ensure at least a modicum of knowledge common to new contributors." msgid "Finally, the examiner checks the candidate's technical (packaging) skills with a detailed questionnaire. Bad answers are not permitted, but the answer time is not limited. All the documentation is available and several attempts are allowed if the first answers are not satisfactory. This step does not intend to discriminate, but to ensure at least a modicum of knowledge common to new contributors." msgstr "最後に、応募管理者は詳細な質問を投げかけて技術的な (パッケージング) スキルを確認します。間違った回答は許されませんが、回答時間に制限はありません。どんな文書を参考にしても構いませんし、最初の回答が不十分ならば何度も回答を作っても構いません。この段階は候補者を不当に冷遇するためのものではなく、新しい貢献者が共通に認識しておくべき最低限のわずかな知識を保証するためのものです。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "This step is known as the Tasks & Skills step (T&S for short) in the examiners' jargon." msgstr "この段階は応募管理者によって使われる隠語の Tasks & Skills (略して T&S、作業と技能) として知られています。" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Tasks & Skills" msgstr "Tasks & Skills" # Checked-By: Ryuunosuke Ayanokouzi; msgid "Final Approval" msgstr "最後の承認" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "key pair" msgid "DAM" msgstr "鍵ペア" # Checked-By: Ryuunosuke Ayanokouzi; #, fuzzy #| msgid "packagetypes" msgid "DebianAccount ManagersDAM" msgstr "パッケージ種類" # Checked-By: Ryuunosuke Ayanokouzi; msgid "At the very last step, the whole process is reviewed by a DAM (Debian Account Manager). The DAM will review all the information about the candidate that the examiner collected, and makes the decision on whether or not to create an account on the Debian servers. In cases where extra information is required, the account creation may be delayed. Refusals are rather rare if the examiner does a good job of following the process, but they sometimes happen. They are never permanent, and the candidate is free to try again at a later time." msgstr "最後の段階で、DAM (Debian アカウントマネージャ) がすべてのプロセスを再確認します。DAM は応募管理者が集めた候補者に関するすべての情報を再確認し、Debian サーバにアカウントを作成するか否かについて決断を下します。追加的情報が必要な場合、アカウントの作成が遅れるかもしれません。応募管理者がプロセスに従って良い作業をしていれば、この段階で不合格になることはほとんどありません。しかし、不合格なる場合も時々あります。不合格は永久的なものではありません。候補者はしばらくの後に再試験を受けることが可能です。" # Checked-By: Ryuunosuke Ayanokouzi; # Checked-By: Osamu Aoki; msgid "The DAM's decision is authoritative and (almost) without appeal, which explains why the people in that seat have often been criticized in the past." msgstr "DAM の決定は権威あるもので (ほとんど) 覆されません。このおかげで、DAM の役職に就く人はこれまでずっと批判され続けています。" # Checked-By: Ryuunosuke Ayanokouzi; # Tag: L-CFMD; # Ref: $ cat debian/control debian/changelog debian/copyright; #, fuzzy #~| msgid "The copyright file must contain information about the authors of the documents included in the package, and the related license. In our case, these are internal documents and their use is restricted to within the Falcot Corp company. The default changelog file is generally appropriate; replacing the “Initial release” with a more verbose explanation and changing the distribution from unstable to internal is enough. The control file was also updated: the Section field has been changed to misc and the Homepage, Vcs-Git and Vcs-Browser fields were removed. The Depends fields was completed with iceweasel | www-browser so as to ensure the availability of a web browser able to display the documents in the package." #~ msgid "The copyright file must contain information about the authors of the documents included in the package, and the related license. In our case, these are internal documents and their use is restricted to within the Falcot Corp company. The default changelog file is generally appropriate; replacing the “Initial release” with a more verbose explanation and changing the distribution from unstable to internal is enough. The control file was also updated: the Section field has been changed to misc and the Homepage, Vcs-Git and Vcs-Browser fields were removed. The Depends fields was completed with firefox-esr | www-browser so as to ensure the availability of a web browser able to display the documents in the package." #~ msgstr "copyright ファイルには必ずパッケージに含まれる文書の著者と対応するライセンスに関する情報を含めなければいけません。今回の場合、パッケージには内部文書が含まれ、その使用は Falcot Corp の社内だけに制限されています。デフォルトの changelog ファイルはほとんどの場合に適切です。「Initial release」をより詳しい説明に置き換えたり、unstable を internal に変えるだけで十分です。control ファイルも更新します。具体的に言えば、Section フィールドの値を misc に変更し、Homepage、Vcs-Git、Vcs-Browser を削除しました。Depends フィールドの値には iceweasel | www-browser を加えました。これはパッケージ内の文書を表示するために必要なウェブブラウザがインストールされていることを保証するためです。" # Checked-By: Ryuunosuke Ayanokouzi; #~ msgid "package archive" #~ msgstr "パッケージアーカイブ" # Checked-By: Ryuunosuke Ayanokouzi; #~ msgid "Debian Developer's Reference" #~ msgstr "Debian 開発者リファレンス" # Checked-By: Ryuunosuke Ayanokouzi; # Ref: $ man 8 pbuilder; # Tag: L-CFMD; #~ msgid "QUICK LOOK pbuilder" #~ msgstr "QUICK LOOK pbuilder" #~ msgid "The menu file" #~ msgstr "menu ファイル" #~ msgid "The needs field, when set to X11|wm indicates that this entry only makes sense in a graphical interface. It will therefore only be integrated into the menus of the graphical (X11) applications and window managers (hence the wm). The section field states where in the menu the entry should be displayed. In our case, the entry will be in the Help menu. The title field contains the text that will be displayed in the menu. Finally, the command field describes the command to run when the user selects the menu entry." #~ msgstr "needs フィールドが X11|wm に設定された場合、このエントリがグラフィカルインターフェースでのみ意味を持つことを意味します。そのため、このエントリはグラフィカル (X11) アプリケーションとウィンドウマネージャ (wm) のメニューに統合されます。section フィールドはこのエントリが表示されるメニュー内の場所を指定します。今回の場合、このエントリは Help メニューに表示されます。title フィールドはメニューに表示されるテキストを指定します。最後に、command フィールドはユーザがメニューエントリを選択した時に実行するコマンドを指定します。" #~ msgid "The second entry matches the first one, with slight adaptations adapted to the Linux console text mode." #~ msgstr "2 番目のエントリは 1 番目のエントリを Linux コンソールテキストモードに適応させたものです。" #~ msgid "DEBIAN POLICY Menu organization" #~ msgstr "DEBIAN POLICY メニュー統合" #~ msgid "The Debian menus are organized in a formal structure, documented in the following text: " #~ msgstr "Debian メニューは規則に従って統合されます。詳細は以下のテキストに書かれています。" #~ msgid "The section in a menu file should be picked from the list mentioned in this document." #~ msgstr "menu ファイル中の section の値はこの文書で述べられているリストの値を使うべきです。" #~ msgid "Simply creating the debian/menu file is enough to enable the menu in the package, since the dh_installmenu command is automatically invoked by dh during the package build process." #~ msgstr "パッケージ内でメニューを有効化するには、単純に debian/menu ファイルを作成するだけで十分です。なぜなら、パッケージビルド作業の間に dh が dh_installmenu コマンドを自動的に呼び出すからです。" #~ msgid "Hess, Joey" #~ msgstr "Hess、Joey" #~ msgid "ALTERNATIVE CDBS" #~ msgstr "ALTERNATIVE CDBS" #~ msgid "cdbs is another approach to Debian packaging, based exclusively on an inheritance system across Makefile files." #~ msgstr "cdbs は Debian パッケージングに対する別のアプローチで、Makefile ファイルを横断する継承システムだけに基づきます。" #~ msgid "That tool has its advocates, since it avoids duplicating the same list of dh_* commands in the debian/rules file. However, Debhelper version 7 introduced the dh command, which itself automates the appropriate sequence of calls to all the individual commands in the correct order, and CDBS has lost most of its appeal since then." #~ msgstr "CDBS が提唱される理由は、CDBS を使うことで、debian/rules ファイルの中で同じ dh_* コマンドのリストを複製する必要がなくなるからです。しかしながら、debhelper バージョン 7 で dh コマンドが導入されました。dh コマンドはすべての個別のコマンドを正しい順番で呼び出す作業を自動化します。こうなったことで、CDBS の魅力の大部分が失われました。"