~debian-janitor/ubuntu-packaging-guide/lintian-fixes

# Chinese (Traditional) translation for ubuntu-packaging-guide
# Copyright (c) 2012 Rosetta Contributors and Canonical Ltd 2012
# This file is distributed under the same license as the ubuntu-packaging-guide package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2012.
#
msgid ""
msgstr ""
"Project-Id-Version: ubuntu-packaging-guide\n"
"Report-Msgid-Bugs-To: FULL NAME <EMAIL@ADDRESS>\n"
"POT-Creation-Date: 2019-01-13 14:36+0300\n"
"PO-Revision-Date: 2015-01-24 18:03+0000\n"
"Last-Translator: Daniel Holbach <daniel@ubuntu.holba.ch>\n"
"Language-Team: Chinese (Traditional) <zh_TW@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Launchpad-Export-Date: 2019-04-27 05:40+0000\n"
"X-Generator: Launchpad (build 18928)\n"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:3
msgid "autopkgtest: Automatic testing for packages"
msgstr "autopkgtest: 套件自動測試"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:5
msgid ""
"The `DEP 8 specification <DEP8_>`_ defines how automatic testing can very "
"easily be integrated into packages. To integrate a test into a package, all "
"you need to do is:"
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:9
msgid ""
"add a file called ``debian/tests/control`` which specifies the requirements "
"for the testbed,"
msgstr "把一個叫做 ``debian/tests/control`` 的檔案加進以指定測試平臺的要求，"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:11
msgid "add the tests in ``debian/tests/``."
msgstr "把測試加進 ``debian/tests/`` 裏。"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:15
msgid "Testbed requirements"
msgstr "測試温床要求"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:17
msgid ""
"In ``debian/tests/control`` you specify what to expect from the testbed. So "
"for example you list all the required packages for the tests, if the testbed "
"gets broken during the build or if ``root`` permissions are required. The "
"`DEP 8 specification <DEP8_>`_ lists all available options."
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:22
msgid ""
"Below we are having a look at the ``glib2.0`` source package. In a very "
"simple case the file would look like this::"
msgstr "下面我們會看一看 ``glib2.0`` 原始碼套件。在一個非常简單的例子中該檔案會是這樣子："

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:28
msgid ""
"For the test in ``debian/tests/build`` this would ensure that the packages "
"``libglib2.0-dev`` and ``build-essential`` are installed."
msgstr ""
"爲了 ``debian/tests/build`` 中的測試，這會確保套件 ``libglib2.0-dev`` 及 ``build-"
"essential`` 會被安装。"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:31
msgid ""
"You can use ``@`` in the ``Depends`` line to indicate that you want all the "
"packages installed which are built by the source package in question."
msgstr "您可以在 ``Depends`` 行裏使用 ``@`` 来指明所有此套件依赖的需要构建的套件。"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:37
msgid "The actual tests"
msgstr "實際的測試"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:39
msgid "The accompanying test for the example above might be:"
msgstr "上面例子的随附測試可能是："

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:71
msgid ""
"Here a very simple piece of C code is written to a temporary directory. Then "
"this is compiled with system libraries (using flags and library paths as "
"provided by `pkg-config`). Then the compiled binary, which just exercises "
"some parts of core glib functionality, is run."
msgstr ""
"在這裏一篇非常简單的 C 代碼會被寫到一個臨時資料夹裏。然後（利用由 `pkg-config` "
"提供的標誌及庫路徑）代码會用系統庫編譯。編譯後，這個只實現了一部分核心 glib 功能的程序會被測試運行。"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:76
msgid ""
"While this test is very small and simple, it covers quite a lot: that your -"
"dev package has all necessary dependencies, that your package installs "
"working pkg-config files, headers and libraries are put into the right "
"place, or that the compiler and linker work. This helps to uncover critical "
"issues early on."
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:82
msgid "Executing the test"
msgstr "運行測試"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:84
msgid ""
"While the test script can be easily executed on its own, it is strongly "
"recommended to actually use ``autopkgtest`` from the ``autopkgtest`` package "
"for verifying that your test works; otherwise, if it fails in the Ubuntu "
"Continuous Integration (CI) system, it will not land in Ubuntu.  This also "
"avoids cluttering your workstation with test packages or test configuration "
"if the test does something more intrusive than the simple example above."
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:91
msgid ""
"The `README.running-tests <running_tests_local_>`_ (`online version "
"<DEP8_>`_) documentation explains all available testbeds (schroot, LXD, "
"QEMU, etc.) and the most common scenarios how to run your tests with "
"``autopkgtest``, e. g. with locally built binaries, locally modified tests, "
"etc."
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:97
msgid ""
"The Ubuntu CI system uses the QEMU runner and runs the tests from the "
"packages in the archive, with ``-proposed`` enabled. To reproduce the exact "
"same environment, first install the necessary packages::"
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:103
msgid "Now build a testbed with::"
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:107
msgid ""
"(Please see its manpage and ``--help`` output for selecting different "
"releases, architectures, output directory, or using proxies). This will "
"build e. g. ``adt-trusty-amd64-cloud.img``."
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:111
msgid ""
"Then run the tests of a source package like ``libpng`` in that QEMU image::"
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:115
msgid ""
"The Ubuntu CI system runs packages with only selected packages from ``-"
"proposed`` available (the package which caused the test to be run); to "
"enable that, run::"
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:121
msgid "or to run with all packages from ``-proposed``::"
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:125
msgid ""
"The ``autopkgtest`` manpage has a lot more valuable information on other "
"testing options."
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:130
msgid "Further examples"
msgstr "更多例子"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:132
msgid ""
"This list is not comprehensive, but might help you get a better idea of how "
"automated tests are implemented and used in Ubuntu."
msgstr "這列單不是太全面，可是有可能幫助您更好了解自動測試如何在Ubuntu裏應用和使用。"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:135
msgid ""
"The `libxml2 tests <libxml2_>`_ are very similar. They also run a test-build "
"of a simple piece of C code and execute it."
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:137
msgid ""
"The `gtk+3.0 tests <gtk3_>`_ also do a compile/link/run check in the "
"\"build\" test. There is an additional \"python3-gi\" test which verifies "
"that the GTK library can also be used through introspection."
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:140
msgid ""
"In the `ubiquity tests <ubiquity_>`_ the upstream test-suite is executed."
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:141
msgid ""
"The `gvfs tests <gvfs_>`_ have comprehensive testing of their functionality "
"and are very interesting because they emulate usage of CDs, Samba, DAV and "
"other bits."
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:146
msgid "Ubuntu infrastructure"
msgstr "Ubuntu架構"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:148
msgid ""
"Packages which have ``autopkgtest`` enabled will have their tests run "
"whenever they get uploaded or any of their dependencies change. The output "
"of `automatically run autopkgtest tests <jenkins_>`_ can be viewed on the "
"web and is regularly updated."
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:153
msgid ""
"Debian also uses ``autopkgtest`` to run package tests, although currently "
"only in schroots, so results may vary a bit. Results and logs can be seen on "
"http://ci.debian.net. So please submit any test fixes or new tests to Debian "
"as well."
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:159
msgid "Getting the test into Ubuntu"
msgstr "把測試放進Ubuntu"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:161
msgid ""
"The process of submitting an autopkgtest for a package is largely similar to "
":doc:`fixing a bug in Ubuntu<./fixing-a-bug>`. Essentially you simply:"
msgstr ""
"提交 autopkgtest 的過程與: doc:`修復 Ubuntu 的 bug<./fixing-a-bug>` 十分相似。基本上您只需："

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:164
msgid "run ``bzr branch ubuntu:<packagename>``,"
msgstr "運行 ``bzr branch ubuntu:<套件名稱>`` ，"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:165
msgid "edit ``debian/control`` to enable the tests,"
msgstr "更改 ``debian/control`` 以啓用測試，"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:166
msgid "add the ``debian/tests`` directory,"
msgstr "建立 ``debian/tests`` 文件夹，"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:167
msgid ""
"write the ``debian/tests/control`` based on the `DEP 8 Specification "
"<dep8_>`_,"
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:168
msgid "add your test case(s) to ``debian/tests``,"
msgstr "把您的測試（們）加進 ``debian/tests`` ，"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:169
msgid ""
"commit your changes, push them to Launchpad, propose a merge and get it "
"reviewed just like any other improvement in a source package."
msgstr "儲下您的改動，把它們推到Launchpad,提出合併和像於其它原始碼套件的改進一樣接受覆核。"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:174
msgid "What you can do"
msgstr "您可以做的事情"

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:176
msgid ""
"The Ubuntu Engineering team put together a `list of required test-cases "
"<requiredtests_>`_, where packages which need tests are put into different "
"categories. Here you can find examples of these tests and easily assign them "
"to yourself."
msgstr ""

#: ../ubuntu-packaging-guide/auto-pkg-test.rst:180
msgid ""
"If you should run into any problems, you can join the `#ubuntu-quality IRC "
"channel <qualityirc_>`_ to get in touch with developers who can help you."
msgstr ""

#: ../ubuntu-packaging-guide/backports.rst:3
msgid "Backporting software updates"
msgstr "把軟件更新帶後"

#: ../ubuntu-packaging-guide/backports.rst:5
msgid ""
"Sometimes you might want to make new functionality available in a stable "
"release which is not connected to a critical bug fix. For these scenarios "
"you have two options: either you `upload to a PPA <ppadoc_>`_ or prepare a "
"backport."
msgstr ""

#: ../ubuntu-packaging-guide/backports.rst:12
msgid "Personal Package Archive (PPA)"
msgstr "個人套件庫（PPA）"

#: ../ubuntu-packaging-guide/backports.rst:14
msgid ""
"Using a PPA has a number of benefits. It is fairly straight-forward, you "
"don't need approval of anyone, but the downside of it is that your users "
"will have to manually enable it. It is a non-standard software source."
msgstr "試用一個個人套件庫有多個好處。它是直来直往，您不要任何人的任可，但缺點是您的用户要手動起動它。它是一個非標準軟件来源。"

#: ../ubuntu-packaging-guide/backports.rst:18
msgid ""
"The `PPA documentation on Launchpad <ppadoc_>`_ is fairly comprehensive and "
"should get you up and running in no time."
msgstr ""

#: ../ubuntu-packaging-guide/backports.rst:25
msgid "Official Ubuntu Backports"
msgstr "官方Ubuntu軟件帶後"

#: ../ubuntu-packaging-guide/backports.rst:27
msgid ""
"The Backports Project is a means to provide new features to users. Because "
"of the inherent stability risks in backporting packages, users do not get "
"backported packages without some explicit action on their part. This "
"generally makes backports an inappropriate avenue for fixing bugs. If a "
"package in an Ubuntu release has a bug, it should be fixed either through "
"the :doc:`Security Update or the Stable Release Update process<./security-"
"and-stable-release-updates>`, as appropriate."
msgstr ""
"軟件帶後計劃是一個提供用户新功能的方法。因為軟件帶後過程中的潜在稳定性的風險，用户如果不做一些行動將不會得到帶後了的套件。這整體上令軟件帶後一個不合當的平"
"台去修復臭蟲。如果一個在一個Ubuntu發行的套件中有臭蟲，它應該用:doc:`保安更新或稳定發行更新程序<./security-and-stable-"
"release-updates>`中合當的選擇去修復。"

#: ../ubuntu-packaging-guide/backports.rst:35
msgid ""
"Once you determined you want a package to be backported to a stable release, "
"you will need to test-build and test it on the given stable release. "
"``pbuilder-dist`` (in the ``ubuntu-dev-tools`` package) is a very handy tool "
"to do this easily."
msgstr ""
"當您决定您要某套件帶後到一個稳定發行，您需要測試建構和測試它在指定的稳定發行。於``ubuntu-dev-tools``套件中的``pbuilder-"
"dist``是一個非常好用的工具来简單地做這個工序。"

#: ../ubuntu-packaging-guide/backports.rst:40
msgid ""
"To report the backport request and get it processed by the Backporters team, "
"you can use the ``requestbackport`` tool (also in the ``ubuntu-dev-tools`` "
"package). It will determine the intermediate releases that package needs to "
"be backported to, list all reverse-dependencies, and file the backporting "
"request.  Also will it include a testing checklist in the bug."
msgstr ""
"以滙报軟件帶後的要求及讓它给軟件帶後團隊處理，您可以試用也在``ubuntu-dev-"
"tools``套件裏的``requestbackport``工具。它會認定該套件需要被帶後到的中期發行，列出所有的反依賴套件，及滙报該軟件帶後的要求。它也"
"會在該臭蟲中包括一個測試程序表。"

#: ../ubuntu-packaging-guide/chroots.rst:3
msgid "Using Chroots"
msgstr "使用 Chroots"

#: ../ubuntu-packaging-guide/chroots.rst:5
msgid ""
"If you are running one version of Ubuntu but working on packages for another "
"versions you can create the environment of the other version with a "
"``chroot``."
msgstr "如果您在一個Ubuntu版本但在開發其它版本的套件您可以使用``chroot``創作其它版本的環境。"

#: ../ubuntu-packaging-guide/chroots.rst:9
msgid ""
"A ``chroot`` allows you to have a full filesystem from another distribution "
"which you can work in quite normally.  It avoids the overhead of running a "
"full virtual machine."
msgstr "一個``chroot``令您有一個從另一個發行来，您可以在裏面正常工作的完整的檔案系統。它避免了運行一個完正虚擬機器的需要。"

#: ../ubuntu-packaging-guide/chroots.rst:14
msgid "Creating a Chroot"
msgstr "建立一個chroot"

#: ../ubuntu-packaging-guide/chroots.rst:16
msgid "Use the command ``debootstrap`` to create a new chroot::"
msgstr "使用``debootstrap``命令去建立一個新chroot:"

#: ../ubuntu-packaging-guide/chroots.rst:20
msgid ""
"This will create a directory ``trusty`` and install a minimal trusty system "
"into it."
msgstr ""

#: ../ubuntu-packaging-guide/chroots.rst:23
msgid ""
"If your version of ``debootstrap`` does not know about Trusty you can try "
"upgrading to the version in ``backports``."
msgstr ""

#: ../ubuntu-packaging-guide/chroots.rst:26
msgid "You can then work inside the chroot::"
msgstr "您現在可以在chroot裏工作：："

#: ../ubuntu-packaging-guide/chroots.rst:30
msgid ""
"Where you can install or remove any package you wish without affecting your "
"main system."
msgstr "在那裏您可以在不影響您的主要系統下安装或移去您想的任何套件。"

#: ../ubuntu-packaging-guide/chroots.rst:33
msgid ""
"You might want to copy your GPG/ssh keys and Bazaar configuration into the "
"chroot so you can access and sign packages directly::"
msgstr "您可能會想覆製您的GPG/ssh錀匙和Bazaar設定到您的chroot裏讓您能直接達到和簽出套件：："

#: ../ubuntu-packaging-guide/chroots.rst:39
msgid ""
"To stop apt and other programs complaining about missing locales you can "
"install your relevant language pack::"
msgstr "要停止apt及其它程試投訴關於消失本地語言您可以安装關乎您的語言套件：："

#: ../ubuntu-packaging-guide/chroots.rst:44
msgid ""
"If you want to run X programs you will need to bind the /tmp directory into "
"the chroot, from outside the chroot run::"
msgstr "如果您想要運行X程式您要把/tmp資料夹合進chroot,從chroot外面運行：："

#: ../ubuntu-packaging-guide/chroots.rst:50
msgid "Some programs may need you to bind /dev or /proc."
msgstr "某些程式可能要您合/dev或/proc。"

#: ../ubuntu-packaging-guide/chroots.rst:52
msgid ""
"For more information on chroots see our `Debootstrap Chroot wiki page "
"<DebootstrapChroot_>`_."
msgstr ""

#: ../ubuntu-packaging-guide/chroots.rst:55
msgid "Alternatives"
msgstr "替代選擇"

#: ../ubuntu-packaging-guide/chroots.rst:57
msgid ""
"SBuild is a system similar to PBuilder for creating an environment to run "
"test package builds in.  It closer matches that used by Launchpad for "
"building packages but takes some more setup compared to PBuilder.  See `the "
"Security Team Build Environment wiki page <SecurityEnv_>`_ for a full "
"explanation."
msgstr ""

#: ../ubuntu-packaging-guide/chroots.rst:62
msgid ""
"Full virtual machines can be useful for packaging and testing programs.  "
"TestDrive is a program to automate syncing and running daily ISO images, see "
"`the TestDrive wiki page <TestDrive_>`_ for more information."
msgstr ""

#: ../ubuntu-packaging-guide/chroots.rst:66
msgid ""
"You can also set up pbuilder to pause when it comes across a build failure.  "
"Copy C10shell from /usr/share/doc/pbuilder/examples into a directory and use "
"the ``--hookdir=`` argument to point to it."
msgstr ""
"您也可以設定pbuilder在遇上建構失败時暫停。從/usr/share/doc/pbuilder/examples複製C10shell到一個文件夹並用`"
"`--hookdir=``選項去指明它。"

#: ../ubuntu-packaging-guide/chroots.rst:70
msgid ""
"Amazon's `EC2 cloud computers <EC2_>`_ allow you to hire a computer paying a "
"few US cents per hour, you can set up Ubuntu machines of any supported "
"version and package on those.  This is useful when you want to compile many "
"packages at the same time or to overcome bandwidth restraints."
msgstr ""

#: ../ubuntu-packaging-guide/communication.rst:3
msgid "Communication in Ubuntu Development"
msgstr "Ubuntu開發通訊"

#: ../ubuntu-packaging-guide/communication.rst:5
msgid ""
"In a project where thousands of lines of code are changed, lots of decisions "
"are made and hundreds of people interact every day, it is important to "
"communicate effectively."
msgstr "在一個每天有數以千計的原始碼被改變，多個决定被定下和數以百計的人溝通的計劃，有效的溝通是重要的。"

#: ../ubuntu-packaging-guide/communication.rst:10
msgid "Mailing lists"
msgstr "郵寄清單"

#: ../ubuntu-packaging-guide/communication.rst:12
msgid ""
"Mailing lists are a very important tool if you want to communicate ideas to "
"a broader team and make sure that you reach everybody, even across timezones."
msgstr "如果您想溝通想法去一個廣闊的團隊及確保您能達到所有人，甚至是跨時區的話，郵寄清單是一個很重要的工具。"

#: ../ubuntu-packaging-guide/communication.rst:16
msgid "In terms of development, these are the most important ones:"
msgstr "對開發来說，這些是最重要的："

#: ../ubuntu-packaging-guide/communication.rst:18
msgid ""
"https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce (announce-"
"only, the most important development announcements go here)"
msgstr ""
"https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce "
"（只是宣布，最重要的開發宣布會到這裏）"

#: ../ubuntu-packaging-guide/communication.rst:20
msgid ""
"https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel (general Ubuntu "
"development discussion)"
msgstr ""
"https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel （整體Ubuntu開發討論）"

#: ../ubuntu-packaging-guide/communication.rst:22
msgid ""
"https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu (MOTU Team discussion, "
"get help with packaging)"
msgstr ""
"https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu （MOTU團隊討論，獲取包装幫助）"

#: ../ubuntu-packaging-guide/communication.rst:27
msgid "IRC Channels"
msgstr "IRC 頻道"

#: ../ubuntu-packaging-guide/communication.rst:29
msgid ""
"For real-time discussions, please connect to irc.freenode.net and join one "
"or any of these channels:"
msgstr "要進行實時通信，請連接到irc.freenode.net及加入任何一個下列的頻道："

#: ../ubuntu-packaging-guide/communication.rst:32
msgid "#ubuntu-devel (for general development discussion)"
msgstr "#ubuntu-devel（综合開發討論）"

#: ../ubuntu-packaging-guide/communication.rst:33
msgid "#ubuntu-motu (for MOTU team discussion and generally getting help)"
msgstr "#ubuntu-motu（MOTU團隊討論和综合求助）"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:2
msgid "Basic Overview of the ``debian/`` Directory"
msgstr "``debian/``資料夹的基本概覽"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:4
msgid ""
"This article will briefly explain the different files important to the "
"packaging of Ubuntu packages which are contained in the ``debian/`` "
"directory. The most important of them are ``changelog``, ``control``, "
"``copyright``, and ``rules``. These are required for all packages. A number "
"of additional files in the ``debian/`` may be used in order to customize and "
"configure the behavior of the package. Some of these files are discussed in "
"this article, but this is not meant to be a complete list."
msgstr ""
"本文章將简單解釋不同於``debian/``資料夹裏對Ubuntu套件包装重要的檔案。當中最重要的是``changelog``，``control``，`"
"`copyright``和``rules``。這些對所有套件都是必要的。一些於``debian/``資料夹裏的附加檔案可以用来指定及設定套件的性質。某些檔"
"案會在這文章中討論到，但這不是一個完整的名單。"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:13
msgid "The changelog"
msgstr "Changelog"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:15
msgid ""
"This file is, as its name implies, a listing of the changes made in each "
"version. It has a specific format that gives the package name, version, "
"distribution, changes, and who made the changes at a given time. If you have "
"a GPG key (see: :doc:`Getting set up<./getting-set-up/>`), make sure to use "
"the same name and email address in ``changelog`` as you have in your key. "
"The following is a template ``changelog``::"
msgstr ""
"本檔案名如其用，是一個每個版本的改變的列表。它有一個特定的規格，列明套件的名稱，版本，發行，改變，和當時做改變的人。如果您有一個GPG錀匙（参見::doc"
":`Getting set up<./getting-set-"
"up/>`)，確保您在``changelog``裏使用與錀匙一樣的名稱和電子郵件地址。下面是一個``changelog``的範本：："

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:31
msgid ""
"The format (especially of the date) is important. The date should be in "
":rfc:`5322` format, which can be obtained by using the command ``date -R``. "
"For convenience, the command ``dch`` may be used to edit changelog. It will "
"update the date automatically."
msgstr ""
"該規格（尤其是日期）是相當重要。該日期該是:rfc:`5322`規格，您可以使用``date -"
"R``命令獲得。為了方便起見，``dch``命令可以用来修改changelog，它會自動更新日期。"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:36
msgid ""
"Minor bullet points are indicated by a dash \"-\", while major points use an "
"asterisk \"*\"."
msgstr "小列點用\"-\"来標示，大列點用星號\"*\"標示。"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:39
msgid ""
"If you are packaging from scratch, ``dch --create`` (``dch`` is in the "
"``devscripts`` package) will create a standard ``debian/changelog`` for you."
msgstr ""
"如果您是從零包装套件，``dch --"
"create``（``dch``是在``devscripts``套件裏）會為您創造一個標準的``debian/changelog``。"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:43
msgid "Here is a sample ``changelog`` file for hello::"
msgstr "這裏是一個為hello套件的``changelog``檔案範本：："

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:52
msgid ""
"Notice that the version has a ``-0ubuntu1`` appended to it, this is the "
"distro revision, used so that the packaging can be updated (to fix bugs for "
"example) with new uploads within the same source release version."
msgstr "留意版本中``-0ubuntu1``是被附加在它旁邊，這是系統版本，能讓包装可以於同一原始碼發行版本裏跟據新上載而更新（例如修復臭蟲）。"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:56
msgid ""
"Ubuntu and Debian have slightly different package versioning schemes to "
"avoid conflicting packages with the same source version. If a Debian package "
"has been changed in Ubuntu, it has ``ubuntuX`` (where ``X`` is the Ubuntu "
"revision number) appended to the end of the Debian version. So if the Debian "
"hello ``2.6-1`` package was changed by Ubuntu, the version string would be "
"``2.6-1ubuntu1``. If a package for the application does not exist in Debian, "
"then the Debian revision is ``0`` (e.g. ``2.6-0ubuntu1``)."
msgstr ""
"Ubuntu和Debian有稍微不同的版本命名系統以避免令有相同原始碼的套件互相分歧。如果一個Debian套件在Ubuntu裏被改變，它的Debian版本"
"後面會加上``ubuntuX``（``X``是Ubuntu的版本號碼）。所以如果Debian的hello``2.6-"
"1``套件被Ubuntu改變，版本名稱將會是``2.6-"
"1ubuntu1``.如果該套件不在Debian裏存在，Debian版本號碼會是``0``（例如``2.6-0ubuntu1``）。"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:64
msgid ""
"For further information, see the `changelog section (Section 4.4) <policy-"
"changelog_>`_ of the Debian Policy Manual."
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:69
msgid "The control file"
msgstr "control檔案"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:71
msgid ""
"The ``control`` file contains the information that the package manager (such "
"as ``apt-get``, ``synaptic``, and ``adept``) uses, build-time dependencies, "
"maintainer information, and much more."
msgstr ""
"``control``檔案包括套件管理員（例如``apt-"
"get``，``synaptic``，和``adpet``）使用的資料，建構時的依賴套件，維護者資訊，和更多。"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:75
msgid ""
"For the Ubuntu ``hello`` package, the ``control`` file looks something like "
"this:"
msgstr "Ubuntu``hello`套件裏的``control``檔案是這個樣子的："

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:100
msgid ""
"The first paragraph describes the source package including the list of "
"packages required to build the package from source in the ``Build-Depends`` "
"field. It also contains some meta-information such as the maintainer's name, "
"the version of Debian Policy that the package complies with, the location of "
"the packaging version control repository, and the upstream home page."
msgstr ""
"第一段描述原始碼套件包括於``Build-"
"Depends``行裏需要用来建構套件的種種套件。它也包括一些综合資訊例如維護者名字，該套件建構時使用的Debian規格版本，包装版本控制分支的位置，及上"
"游軟件的首頁。"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:107
msgid ""
"Note that in Ubuntu, we set the ``Maintainer`` field to a general address "
"because anyone can change any package (this differs from Debian where "
"changing packages is usually restricted to an individual or a team). "
"Packages in Ubuntu should generally have the ``Maintainer`` field set to "
"``Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>``. If the "
"Maintainer field is modified, the old value should be saved in the ``XSBC-"
"Original-Maintainer`` field. This can be done automatically with the  "
"``update-maintainer`` script available in the ``ubuntu-dev-tools`` package. "
"For further information, see the `Debian Maintainer Field spec "
"<MaintField_>`_ on the Ubuntu wiki."
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:118
msgid "Each additional paragraph describes a binary package to be built."
msgstr "每個附加的段落形容一個要建構的程試套件。"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:120
msgid ""
"For further information, see the `control file section (Chapter 5) <policy-"
"control_>`_ of the Debian Policy Manual."
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:125
msgid "The copyright file"
msgstr "copyright檔案"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:127
msgid ""
"This file gives the copyright information for both the upstream source and "
"the packaging. Ubuntu and `Debian Policy (Section 12.5) <policy-"
"copyright_>`_ require that each package installs a verbatim copy of its "
"copyright and license information to "
"``/usr/share/doc/$(package_name)/copyright``."
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:132
msgid ""
"Generally, copyright information is found in the ``COPYING`` file in the "
"program's source directory. This file should include such information as the "
"names of the author and the packager, the URL from which the source came, a "
"Copyright line with the year and copyright holder, and the text of the "
"copyright itself. An example template would be::"
msgstr ""
"總體上，版權資訊會在程試原始碼資料夹中的``COPYING``檔案找到。這檔案應該包括資訊例如作者和包装者的名字，原始碼来原的連接，有年份和版權持有者的版"
"權欄，及版權自己的文字。一個設例範本會是：："

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:174
msgid ""
"This example follows the `Machine-readable debian/copyright <DEP5_>`_ "
"format. You are encouraged to use this format as well."
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:179
msgid "The rules file"
msgstr "rules檔案"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:181
msgid ""
"The last file we need to look at is ``rules``. This does all the work for "
"creating our package. It is a Makefile with targets to compile and install "
"the application, then create the ``.deb`` file from the installed files. It "
"also has a target to clean up all the build files so you end up with just a "
"source package again."
msgstr ""
"最後一個我們要看一看的是``rules``。這擔任所有創造我們的套件的工作。它是一個有目標的建構檔案，會建構並安装該應用程試，然後從安装了的檔案創造``."
"deb``檔案。它也有一個目標去清除所有的建構檔案，所以您會最後再得到一個原始碼套件。"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:189
msgid ""
"Here is a simplified version of the rules file created by ``dh_make`` (which "
"can be found in the ``dh-make`` package):"
msgstr "這是一個從``dh_make``（能在``dh-make``套件中找到）創造的简化了的rules檔案："

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:203
msgid ""
"Let us go through this file in some detail. What this does is pass every "
"build target that ``debian/rules`` is called with as an argument to "
"``/usr/bin/dh``, which itself will call all the necessary ``dh_*`` commands."
msgstr ""
"讓我們詳细地看一看這檔案。這做的是把所有``debian/rules``要求的所有的建構目標傳送為一個給``/usr/bin/dh``的選項，而自己就會運"
"行所有的需要的``dh_*``命令。"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:207
msgid ""
"``dh`` runs a sequence of debhelper commands. The supported sequences "
"correspond to the targets of a ``debian/rules`` file: \"build\", \"clean\", "
"\"install\", \"binary-arch\", \"binary-indep\", and \"binary\". In order to "
"see what commands are run in each target, run::"
msgstr ""
"``dh``運行一系列的debhelper命令。支援的次序相應一個``debian/rules``檔案的目標：\"build\"，\"clean\"，\""
"install“，\"binary-arch\"，\"binary-indep\"，及\"binary\"。要看在每一個目標裏會被運行的命令，請運行：："

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:216
msgid ""
"Commands in the binary-indep sequence are passed the \"-i\" option to ensure "
"they only work on binary independent packages, and commands in the binary-"
"arch sequences are passed the \"-a\" option to ensure they only work on "
"architecture dependent packages."
msgstr ""
"在binary-indep次序的命令會被傳送以\"-i\"選項以確保它們只會在程式獨立套件上運作，而在binary-arch次序裏的命令會被傳送以\"-"
"a\"選項以確保它們只會在位元依賴套件上運作。"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:221
msgid ""
"Each debhelper command will record when it's successfully run in "
"``debian/package.debhelper.log``. (Which dh_clean deletes.) So dh can tell "
"which commands have already been run, for which packages, and skip running "
"those commands again."
msgstr ""
"每個debhelper命令會在``debian/package.debhelper.log``（會被dh_clean删除）裏成功運行時記錄讓dh能分辨哪些"
"命令已經被運行和為哪個套件，和跳過再次運行這些命令。"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:226
msgid ""
"Each time ``dh`` is run, it examines the log, and finds the last logged "
"command that is in the specified sequence. It then continues with the next "
"command in the sequence. The ``--until``, ``--before``, ``--after``, and ``--"
"remaining`` options can override this behavior."
msgstr ""
"每一次``dh``運行，它會檢查記錄，和找出在指定次序裏最後被記錄的命令。它然後會從次序裏下一個命令繼續。``--until``，``--"
"before``，``--after``，及``--remaining``選項能覆盖這種動作。"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:231
msgid ""
"If ``debian/rules`` contains a target with a name like "
"``override_dh_command``, then when it gets to that command in the sequence, "
"``dh`` will run that target from the rules file, rather than running the "
"actual command. The override target can then run the command with additional "
"options, or run entirely different commands instead. (Note that to use this "
"feature, you should Build-Depend on debhelper 7.0.50 or above.)"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:240
msgid ""
"Have a look at ``/usr/share/doc/debhelper/examples/`` and ``man dh`` for "
"more examples. Also see `the rules section (Section 4.9) "
"<http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules>`_ of "
"the Debian Policy Manual."
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:246
msgid "Additional Files"
msgstr "附加檔案"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:249
msgid "The install file"
msgstr "install檔案"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:251
msgid ""
"The ``install`` file is used by ``dh_install`` to install files into the "
"binary package. It has two standard use cases:"
msgstr "``install``檔案是被``dh_install``使用来安装檔案到程試套件。它有两個標準使用個案："

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:254
msgid ""
"To install files into your package that are not handled by the upstream "
"build system."
msgstr "安装不被上游建構系統接手的檔案到您的套件。"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:255
msgid ""
"Splitting a single large source package into multiple binary packages."
msgstr "把一個單一大原始碼套件分開做多個程式套件。"

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:257
msgid ""
"In the first case, the ``install`` file should have one line per file "
"installed, specifying both the file and the installation directory. For "
"example, the following ``install`` file would install the script ``foo`` in "
"the source package's root directory to ``usr/bin`` and a desktop file in the "
"``debian`` directory to ``usr/share/applications``::"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:268
msgid ""
"When a source package is producing multiple binary packages ``dh`` will "
"install the files into ``debian/tmp`` rather than directly into "
"``debian/<package>``. Files installed into ``debian/tmp`` can then be moved "
"into separate binary packages using multiple ``$package_name.install`` "
"files. This is often done to split large amounts of architecture independent "
"data out of architecture dependent packages and into ``Architecture: all`` "
"packages. In this case, only the name of the files (or directories) to be "
"installed are needed without the installation directory. For example, "
"``foo.install`` containing only the architecture dependent files might look "
"like::"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:281
msgid ""
"While ``foo-common.install`` containing only the architecture independent "
"file might look like::"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:289
msgid ""
"This would create two binary packages, ``foo`` and ``foo-common``. Both "
"would require their own paragraph in ``debian/control``."
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:292
msgid ""
"See ``man dh_install`` and the `install file section (Section 5.11) "
"<http://www.debian.org/doc/manuals/maint-guide/dother.en.html#install>`_  of "
"the Debian New Maintainers' Guide for additional details."
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:297
msgid "The watch file"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:299
msgid ""
"The ``debian/watch`` file allows us to check automatically for new upstream "
"versions using the tool ``uscan`` found in the ``devscripts`` package. The "
"first line of the watch file must be the format version (3, at the time of "
"this writing), while the following lines contain any URLs to parse. For "
"example::"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:308
msgid ""
"Running ``uscan`` in the root source directory will now compare the upstream "
"version number in ``debian/changelog`` with the latest available upstream "
"version. If a new upstream version is found, it will be automatically "
"downloaded. For example::"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:321
msgid ""
"If your tarballs live on Launchpad, the ``debian/watch`` file is a little "
"more complicated (see `Question 21146 <Q21146_>`_ and `Bug 231797 "
"<Bug231797_>`_ for why this is).  In that case, use something like::"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:328
msgid ""
"For further information, see ``man uscan`` and the `watch file section "
"(Section 4.11) <http://www.debian.org/doc/debian-policy/ch-source.html#s-"
"debianwatch>`_ of the Debian Policy Manual."
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:332
msgid ""
"For a list of packages where the ``watch`` file reports they are not in sync "
"with upstream see `Ubuntu External Health Status "
"<http://qa.ubuntuwire.org/uehs/no_updated.html>`_."
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:337
msgid "The source/format file"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:339
msgid ""
"This file indicates the format of the source package. It should contain a "
"single line indicating the desired format:"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:342
msgid "``3.0 (native)`` for Debian native packages (no upstream version)"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:344
msgid "``3.0 (quilt)`` for packages with a separate upstream tarball"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:346
msgid "``1.0`` for packages wishing to explicitly declare the default format"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:348
msgid ""
"Currently, the package source format will default to 1.0 if this file does "
"not exist. You can make this explicit in the source/format file. If you "
"choose not to use this file to define the source format, Lintian will warn "
"about the missing file. This warning is informational only and may be safely "
"ignored."
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:353
msgid ""
"You are encouraged to use the newer 3.0 source format. It provides a number "
"of new features:"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:356
msgid "Support for additional compression formats: bzip2, lzma and xz"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:358
msgid "Support for multiple upstream tarballs"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:360
msgid ""
"Not necessary to repack the upstream tarball to strip the debian directory"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:362
msgid ""
"Debian-specific changes are no longer stored in a single .diff.gz but in "
"multiple patches compatible with quilt under ``debian/patches/``"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:365
msgid ""
"https://wiki.debian.org/Projects/DebSrc3.0 summarizes additional information "
"concerning the switch to the 3.0 source package formats."
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:368
msgid ""
"See ``man dpkg-source`` and the `source/format section (Section 5.21) "
"<policy-format_>`_  of  the Debian New Maintainers' Guide for additional "
"details."
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:372
msgid "Additional Resources"
msgstr ""

#: ../ubuntu-packaging-guide/debian-dir-overview.rst:374
msgid ""
"In addition to the links to the Debian Policy Manual in each section above, "
"the Debian New Maintainers' Guide has more detailed descriptions of each "
"file. `Chapter 4, \"Required files under the debian directory\" "
"<RequiredFiles_>`_ further discusses the  control, changelog, copyright and "
"rules files. `Chapter 5, \"Other files under the debian directory\" "
"<OtherFiles_>`_ discusses additional files that may be used."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:3
msgid "Fixing a bug in Ubuntu"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:6
#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:9
msgid "Introduction"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:8
msgid ""
"If you followed the instructions to :doc:`get set up with Ubuntu "
"Development<./getting-set-up>`, you should be all set and ready to go."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:13
msgid ""
"As you can see in the image above, there is no surprises in the process of "
"fixing bugs in Ubuntu: you found a problem, you get the code, work on the "
"fix, test it, push your changes to Launchpad and ask for it to be reviewed "
"and merged. In this guide we will go through all the necessary steps one by "
"one."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:20
msgid "Finding the problem"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:22
msgid ""
"There are a lot of different ways to find things to work on. It might be a "
"bug report you are encountering yourself (which gives you a good opportunity "
"to test the fix), or a problem you noted elsewhere, maybe in a bug report."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:26
msgid ""
"Take a look at `the bitesize bugs`_ in Launchpad, and that might give you an "
"idea of something to work on. It might also interest you to look at the bugs "
"`triaged`_ by the Ubuntu One Hundred Papercuts team."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:35
msgid "Figuring out what to fix"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:37
msgid ""
"If you don't know the source package containing the code that has the "
"problem, but you do know the path to the affected program on your system, "
"you can discover the source package that you'll need to work on."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:41
msgid ""
"Let's say you've found a bug in Bumprace, a racing game. The Bumprace "
"application can be started by running ``/usr/bin/bumprace`` on the command "
"line. To find the binary package containing this application, use this "
"command::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:47
msgid "This would print out::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:51
msgid ""
"Note that the part preceding the colon is the binary package name. It's "
"often the case that the source package and binary package will have "
"different names. This is most common when a single source package is used to "
"build multiple different binary packages. To find the source package for a "
"particular binary package, type::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:62
msgid "``apt-cache`` is part of the standard installation of Ubuntu."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:65
msgid "Confirming the problem"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:67
msgid ""
"Once you have figured out which package the problem is in, it's time to "
"confirm that the problem exists."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:70
msgid ""
"Let's say the package ``bumprace`` does not have a homepage in its package "
"description. As a first step you would check if the problem is not solved "
"already. This is easy to check, either take a look at Software Center or "
"run::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:76
msgid "The output should be similar to this::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:102
msgid "A counter-example would be ``gedit``, which has a homepage set::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:107
msgid ""
"Sometimes you will find that a particular problem you are looking into is "
"already fixed. To avoid wasting efforts and duplicating work it makes sense "
"to first do some detective work."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:112
msgid "Research bug situation"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:114
msgid ""
"First we should check if a bug for the problem exists in Ubuntu already. "
"Maybe somebody is working on a fix already, or we can contribute to the "
"solution somehow. For Ubuntu we have a quick look at "
"https://bugs.launchpad.net/ubuntu/+source/bumprace and there is no open bug "
"with our problem there."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:120
msgid ""
"For Ubuntu the URL ``https://bugs.launchpad.net/ubuntu/+source/<package>`` "
"should always take to the bug page of the source package in question."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:124
msgid ""
"For Debian, which is the major source for Ubuntu's packages, we have a look "
"at http://bugs.debian.org/src:bumprace and can't find a bug report for our "
"problem either."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:128
msgid ""
"For Debian the URL ``http://bugs.debian.org/src:<package>`` should always "
"take to the bug page of the source package in question."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:131
msgid ""
"The problem we are working on is special as it only concerns the packaging-"
"related bits of ``bumprace``. If it was a problem in the source code it "
"would be helpful to also check the Upstream bug tracker. This is "
"unfortunately often different for every package you have a look at, but if "
"you search the web for it, you should in most cases find it pretty easily."
msgstr ""
"我們正在研究的是特別的問題，因爲它僅僅與  ``bumprace`` 包相關。如果源碼包出現問題，最好檢查上游的 bug "
"跟踪系統。雖然通常你查看的每包各不相同，但是如果您在網上搜索，您可以相當容易的找到。"

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:138
msgid "Offering help"
msgstr "提供幫助"

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:140
msgid ""
"If you found an open bug and it is not assigned to somebody and you are in a "
"position to fix it, you should comment on it with your solution. Be sure to "
"include as much information as you can: Under which circumstances does the "
"bug occur? How did you fix the problem? Did you test your solution?"
msgstr ""
"如果您發現了一個開放的錯誤，它沒有分配給某人，您在這個修復者的位置，您應該對此發表評論，附上您的解決方案。一定要包括盡可能多的信息，你可以發表：這是在什麼"
"情況下出現的bug，您是怎麼解決這個問題的，您是否測試您的解決方案。"

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:145
msgid ""
"If no bug report has been filed, you can file a bug for it. What you might "
"want to bear in mind is: Is the issue so small that just asking for somebody "
"to commit it is good enough? Did you manage to only partially fix the issue "
"and you want to at least share your part of it?"
msgstr ""
"如果沒有已提交的錯誤報告，您可以提交一個錯誤報告。您可能要牢記的是：這問題是如此之小，只需要求別人提交夠不夠好？你是不是部分地解決這個問題，你要至少分享你"
"的修復部分嗎？"

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:150
msgid "It is great if you can offer help and will surely be appreciated."
msgstr "如果你能提供幫助，那就太棒了，一定會受讚賞的。"

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:155
msgid "Getting the code"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:157
msgid ""
"Once you know the source package to work on, you will want to get a copy of "
"the code on your system, so that you can debug it. The ubuntu-dev-tools "
"package has a tool called ``pull-lp-source`` that a developer can use to "
"grab the source code for any package. For example, to grab the source code "
"for the tomboy package in ``xenial``, you can type this::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:165
msgid ""
"If you do not specify a release such as ``xenial``, it will automatically "
"get the package from the development version."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:168
msgid ""
"Once you've got a local clone of the source package, you can investigate the "
"bug, create a fix, generate a debdiff, and attach your debdiff to a bug "
"report for other developers to review. We'll describe specifics in the next "
"sections."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:173
msgid "Work on a fix"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:175
msgid ""
"There are entire books written about finding bugs, fixing them, testing "
"them, etc. If you are completely new to programming, try to fix easy bugs "
"such as obvious typos first. Try to keep changes as minimal as possible and "
"document your change and assumptions clearly."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:180
msgid ""
"Before working on a fix yourself, make sure to investigate if nobody else "
"has fixed it already or is currently working on a fix. Good sources to check "
"are:"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:183
msgid "Upstream (and Debian) bug tracker (open and closed bugs),"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:184
msgid ""
"Upstream revision history (or newer release) might have fixed the problem,"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:185
msgid "bugs or package uploads of Debian or other distributions."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:190
msgid ""
"You may want to create a patch which includes the fix. The command ``edit-"
"patch`` is a simple way to add a patch to a package. Run::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:195
msgid ""
"This will copy the packaging to a temporary directory.  You can now edit "
"files with a text editor or apply patches from upstream, for example::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:200
msgid ""
"After editing the file type ``exit`` or press ``control-d`` to quit the "
"temporary shell.  The new patch will have been added into ``debian/patches``."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:203
msgid ""
"You must then add a header to your patch containing meta information so that "
"other developers can know the purpose of the patch and where it came from. "
"To get the template header that you can edit to reflect what the patch does, "
"type this::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:210
msgid ""
"This will open the template in a text editor. Follow the template and make "
"sure to be thorough so you get all the details necessary to describe the "
"patch."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:214
msgid ""
"In this specific case, if you just want to edit ``debian/control``, you do "
"not need a patch. Put ``Homepage: http://www.linux-games.com/bumprace/`` at "
"the end of the first section and the bug should be fixed."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:219
msgid "Documenting the fix"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:221
msgid ""
"It is very important to document your change sufficiently so developers who "
"look at the code in the future won't have to guess what your reasoning was "
"and what your assumptions were. Every Debian and Ubuntu package source "
"includes ``debian/changelog``, where changes of each uploaded package are "
"tracked."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:226
msgid "The easiest way to update this is to run::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:230
msgid ""
"This will add a boilerplate changelog entry for you and launch an editor "
"where you can fill in the blanks. An example of this could be::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:239
msgid ""
"``dch`` should fill out the first and last line of such a changelog entry "
"for you already. Line 1 consists of the source package name, the version "
"number, which Ubuntu release it is uploaded to, the urgency (which almost "
"always is 'low'). The last line always contains the name, email address and "
"timestamp (in :rfc:`5322` format) of the change."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:245
msgid ""
"With that out of the way, let's focus on the actual changelog entry itself: "
"it is very important to document:"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:248
msgid "Where the change was done."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:249
msgid "What was changed."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:250
msgid "Where the discussion of the change happened."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:252
msgid ""
"In our (very sparse) example the last point is covered by ``(LP: #123456)`` "
"which refers to Launchpad bug 123456. Bug reports or mailing list threads or "
"specifications are usually good information to provide as a rationale for a "
"change. As a bonus, if you use the ``LP: #<number>`` notation for Launchpad "
"bugs, the bug will be automatically closed when the package is uploaded to "
"Ubuntu."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:259
msgid ""
"In order to get it sponsored in the next section, you need to file a bug "
"report in Launchpad (if there isn't one already, if there is, use that) and "
"explain why your fix should be included in Ubuntu. For example, for tomboy, "
"you would file a bug `here`_ (edit the URL to reflect the package you have a "
"fix for). Once a bug is filed explaining your changes, put that bug number "
"in the changelog."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:269
msgid "Testing the fix"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:271
msgid "To build a test package with your changes, run these commands::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:276
msgid ""
"This will create a source package from the branch contents (``-us -uc`` will "
"just omit the step to sign the source package and ``-d`` will skip the step "
"where it checks for build dependencies, pbuilder will take care of that) and "
"``pbuilder-dist`` will build the package from source for whatever "
"``release`` you choose."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:283
msgid ""
"If ``debuild`` errors out with \"Version number suggests Ubuntu changes, but "
"Maintainer: does not have Ubuntu address\" then run the ``update-"
"maintainer`` command (from ubuntu-dev-tools) and it will automatically fix "
"this for you. This happens because in Ubuntu, all Ubuntu Developers are "
"responsible for all Ubuntu packages, while in Debian, packages have "
"maintainers."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:289
msgid ""
"In this case with bumprace, run this to view the package information::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:293
msgid "As expected, there should now be a ``Homepage:`` field."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:296
msgid ""
"In a lot of cases you will have to actually install the package to make sure "
"it works as expected. Our case is a lot easier. If the build succeeded, you "
"will find the binary packages in ``~/pbuilder/<release>_result``. Install "
"them via ``sudo dpkg -i <package>.deb`` or by double-clicking on them in "
"your file manager."
msgstr ""
"在很多情況下，你將需要實際安裝包，以確保它如預期工作。我們的這個案例容易得多。如果構建成功，您將會在 "
"``~/pbuider/<release>_result`` 中找到二進制包。使用 ``sudo dpkg -i <package>.deb`` "
"或者雙擊它來安裝。"

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:304
msgid "Submitting the fix and getting it included"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:306
msgid ""
"With the changelog entry written and saved, run ``debuild`` one more time::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:310
msgid ""
"and this time it will be signed and you are now ready to get your diff to "
"submit to get sponsored."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:313
msgid ""
"In a lot of cases, Debian would probably like to have the patch as well "
"(doing this is best practice to make sure a wider audience gets the fix). "
"So, you should submit the patch to Debian, and you can do that by simply "
"running this::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:320
msgid ""
"This will take you through a series of steps to make sure the bug ends up in "
"the correct place. Be sure to review the diff again to make sure it does not "
"include random changes you made earlier."
msgstr "這將帶你通過一系列的步驟，以確保錯誤結束在正確的地方。務必再次檢查diff，以確保它不包括您剛才的隨機更動。"

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:324
msgid ""
"Communication is important, so when you add some more description to it to "
"the inclusion request, be friendly, explain it well."
msgstr "溝通是很重要的，所以當您爲列入請求添加一些更多的描述，友好些，解釋好些。"

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:327
msgid ""
"If everything went well you should get a mail from Debian's bug tracking "
"system with more information. This might sometimes take a few minutes."
msgstr "如果一切順利，你應該得到一封從 Debian 的 bug 跟踪系統郵件，提供更多的信息。有時這可能需要幾分鐘。"

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:330
msgid ""
"It might be beneficial to just get it included in Debian and have it flow "
"down to Ubuntu, in which case you would not follow the below process. But, "
"sometimes in the case of security updates and updates for stable releases, "
"the fix is already in Debian (or ignored for some reason) and you would "
"follow the below process. If you are doing such updates, please read our "
":doc:`Security and stable release updates<./security-and-stable-release-"
"updates>` article. Other cases where it is acceptable to wait to submit "
"patches to Debian are Ubuntu-only packages not building correctly, or Ubuntu-"
"specific problems in general."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:340
msgid ""
"But if you're going to submit your fix to Ubuntu, now it's time to generate "
"a \"debdiff\", which shows the difference between two Debian packages. The "
"name of the command used to generate one is also ``debdiff``. It is part of "
"the ``devscripts`` package. See ``man debdiff`` for all the details. To "
"compare two source packages, pass the two dsc files as arguments::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:348
msgid ""
"In this case, ``debdiff`` the dsc you downloaded with ``pull-lp-source`` and "
"the new dsc file you generated. This will generate a patch that your sponsor "
"can then apply locally (by using ``patch -p1 < /path/to/debdiff``). In this "
"case, pipe the output of the debdiff command to a file that you can then "
"attach to the bug report::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:356
msgid "The format shown in ``1-1.0-1ubuntu1.debdiff`` shows:"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:358
msgid ""
"``1-`` tells the sponsor that this is the first revision of your patch. "
"Nobody is perfect, and sometimes follow-up patches need to be provided. This "
"makes sure that if your patch needs work, that you can keep a consistent "
"naming scheme."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:362
msgid ""
"``1.0-1ubuntu1`` shows the new version being used. This makes it easy to see "
"what the new version is."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:364
msgid ""
"``.debdiff`` is an extension that makes it clear that it is a debdiff."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:366
msgid "While this format is optional, it works well and you can use this."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:368
msgid ""
"Next, go to the bug report, make sure you are logged into Launchpad, and "
"click \"Add attachment or patch\" under where you would add a new comment. "
"Attach the debdiff, and leave a comment telling your sponsor how this patch "
"can be applied and the testing you have done. An example comment can be::"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:376
msgid ""
"Make sure you mark it as a patch (the Ubuntu Sponsors team will "
"automatically be subscribed) and that you are subscribed to the bug report. "
"You will then receive a review anywhere between several hours from "
"submitting the patch to several weeks. If it takes longer than that, please "
"join ``#ubuntu-motu`` on ``freenode`` and mention it there. Stick around "
"until you get an answer from someone, and they can guide you as to what to "
"do next."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:383
msgid ""
"Once you have received a review, your patch was either uploaded, your patch "
"needs work, or is rejected for some other reason (possibly the fix is not "
"fit for Ubuntu or should go to Debian instead). If your patch needs work, "
"follow the same steps and submit a follow-up patch on the bug report, "
"otherwise submit to Debian as shown above."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:389
msgid ""
"Remember: good places to ask your questions are ``ubuntu-"
"motu@lists.ubuntu.com`` and ``#ubuntu-motu`` on freenode. You will easily "
"find a lot of new friends and people with the same passion that you have: "
"making the world a better place by making better Open Source software."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:395
msgid "Additional considerations"
msgstr "其他注意事項"

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:397
msgid ""
"If you find a package and find that there are a couple of trivial things you "
"can fix at the same time, do it. This will speed up review and inclusion."
msgstr "如果你找到一個包，發現有幾個瑣碎的事情而且你同時可以修復它們，那就修復它們吧 。這將加快審查和修復入庫。"

#: ../ubuntu-packaging-guide/fixing-a-bug.rst:400
msgid ""
"If there are multiple big things you want to fix, it might be advisable to "
"send individual patches or merge proposals instead. If there are individual "
"bugs filed for the issues already, this makes it even easier."
msgstr "如果您要修復多個大的問題，最好發送單個補丁或建議，而不是合併。如果是個別臭蟲的問題會更容易解決。"

#: ../ubuntu-packaging-guide/fixing-ftbfs.rst:5
msgid "Fixing FTBFS packages"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-ftbfs.rst:7
msgid ""
"Before a package can be used in Ubuntu, it has to build from source. If it "
"fails this, it will probably wait in -proposed and will not be available in "
"the Ubuntu archives. You can find a complete list of packages that are "
"failing to build from source at http://qa.ubuntuwire.org/ftbfs/. There are 5 "
"main categories shown on the page:"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-ftbfs.rst:13
msgid ""
"Package failed to build (F): Something actually went wrong with the build "
"process."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-ftbfs.rst:15
msgid ""
"Cancelled build (X): The build has been cancelled for some reason. These "
"should probably be avoided to start with."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-ftbfs.rst:17
msgid ""
"Package is waiting on another package (M): This package is waiting on "
"another package to either build, get updated, or (if the package is in main) "
"one of it's dependancies is in the wrong part of the archive."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-ftbfs.rst:20
msgid ""
"Failure in the chroot (C): Part of the chroot failed, this is most likely "
"fixed by a rebuild. Ask a developer to rebuild the package and that should "
"fix it."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-ftbfs.rst:23
msgid ""
"Failed to upload (U): The package could not upload. This is usually just a "
"case of asking for a rebuild, but check the build log first."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-ftbfs.rst:27
msgid "First steps"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-ftbfs.rst:28
msgid ""
"The first thing you'll want to do is see if you can reproduce the FTBFS "
"yourself. Get the code either by running ``bzr branch lp:ubuntu/PACKAGE`` "
"and then getting the tarball or running ``dget PACKAGE_DSC`` on the .dsc "
"file from the launchpad page. Once you have that, build it in a schroot."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-ftbfs.rst:35
msgid ""
"You should be able to reproduce the FTBFS. If not, check if the build is "
"downloading a missing dependency, which means you just need to make that a "
"build-dependency in debian/control. Building the package locally can also "
"help find if the issue is caused by a missing, unlisted, dependency (builds "
"locally but fails on a schroot)."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-ftbfs.rst:42
msgid "Checking Debian"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-ftbfs.rst:43
msgid ""
"Once you have reproduced the issue, it's time to try and find a solution. If "
"the package is in Debian as well, you can check if the package builds there "
"by going to http://packages.qa.debian.org/PACKAGE. If Debian has a newer "
"version, you should merge it. If not, check the buildlogs and bugs linked on "
"that page for any extra information on the ftbfs or patches. Debian also "
"maintains a list of command FTBFSs and how to fix them which can be found at "
"https://wiki.debian.org/qa.debian.org/FTBFS, you will want to check it for "
"solutions too."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-ftbfs.rst:53
msgid "Other causes of a package to FTBFS"
msgstr ""

#: ../ubuntu-packaging-guide/fixing-ftbfs.rst:54
msgid ""
"If a package is in main and missing a dependency that is not in main, you "
"will have to file a MIR bug. https://wiki.ubuntu.com/MainInclusionProcess "
"explains the procedure."
msgstr ""

#: ../ubuntu-packaging-guide/fixing-ftbfs.rst:61
msgid "Fixing the issue"
msgstr "修復問題"

#: ../ubuntu-packaging-guide/fixing-ftbfs.rst:62
msgid ""
"Once you have found a fix to the problem, follow the same process as any "
"other bug. Make a patch, add it to a bzr branch or bug, subscribe ubuntu-"
"sponsors, then try to get it included upstream and/or in Debian."
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:3
msgid "Getting Set Up"
msgstr "快速設置"

#: ../ubuntu-packaging-guide/getting-set-up.rst:5
msgid ""
"There are a number of things you need to do to get started developing for "
"Ubuntu. This article is designed to get your computer set up so that you can "
"start working with packages, and upload your packages to Ubuntu's hosting "
"platform, Launchpad. Here's what we'll cover:"
msgstr ""
"要開始為 Ubuntu 開發，您需要做一些准备。本文的目的是讓您的電腦設置好，您就可以開始开发您的软件包，並上傳您的軟件包到 Ubuntu 的  "
"託管平台， Launchpad。下面我們將討論："

#: ../ubuntu-packaging-guide/getting-set-up.rst:10
msgid "Installing packaging-related software. This includes:"
msgstr "安裝與包裝相關的軟件。這包括："

#: ../ubuntu-packaging-guide/getting-set-up.rst:12
msgid "Ubuntu-specific packaging utilities"
msgstr "Ubuntu的特定打包工具"

#: ../ubuntu-packaging-guide/getting-set-up.rst:13
msgid "Encryption software so your work can be verified as being done by you"
msgstr "加密軟件，所以驗證由您完成的工作是您的付出"

#: ../ubuntu-packaging-guide/getting-set-up.rst:14
msgid "Additional encryption software so you can securely transfer files"
msgstr "額外的加密軟件，這樣你就可以安全地傳輸文件"

#: ../ubuntu-packaging-guide/getting-set-up.rst:16
msgid "Creating and configuring your account on Launchpad"
msgstr "在 Launchpad 上創建和配置您的帳戶"

#: ../ubuntu-packaging-guide/getting-set-up.rst:17
msgid ""
"Setting up your development environment to help you do local builds of "
"packages, interact with other developers, and propose your changes on "
"Launchpad."
msgstr "設置您的開發環境來幫你做本地編譯軟件包，與其他開發人員互動，並提出您的變化到 Launchpad 上。"

#: ../ubuntu-packaging-guide/getting-set-up.rst:22
msgid ""
"It is advisable to do packaging work using the current development version "
"of Ubuntu. Doing so will allow you to test changes in the same environment "
"where those changes will actually be applied and used."
msgstr "建議最好是使用當前開發版本的 Ubuntu 做打包工作。這樣做可以讓你測試在同樣的環境的開發，這些開發成果將實際地被應用和使用。"

#: ../ubuntu-packaging-guide/getting-set-up.rst:26
msgid ""
"Don't want to install the latest development version of Ubuntu? Spin up an "
"`LXD container <https://help.ubuntu.com/lts/serverguide/lxd.html>`_."
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:30
msgid "Install basic packaging software"
msgstr "安裝基本的打包軟件"

#: ../ubuntu-packaging-guide/getting-set-up.rst:32
msgid ""
"There are a number of tools that will make your life as an Ubuntu developer "
"much easier. You will encounter these tools later in this guide. To install "
"most of the tools you will need run this command::"
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:39
msgid "This command will install the following software:"
msgstr "這個命令會安裝以下軟件："

#: ../ubuntu-packaging-guide/getting-set-up.rst:41
msgid ""
"``gnupg`` -- `GNU Privacy Guard <GPG_>`_ contains tools you will need to "
"create a cryptographic key with which you will sign files you want to upload "
"to Launchpad."
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:44
msgid ""
"``pbuilder`` -- a tool to do reproducible builds of a package in a clean and "
"isolated environment."
msgstr "``pbuilder`` —— 一個工具，用來在乾淨的和孤立的環境中重現構建一個包。"

#: ../ubuntu-packaging-guide/getting-set-up.rst:46
msgid ""
"``ubuntu-dev-tools`` (and ``devscripts``, a direct dependency) -- a "
"collection of tools that make many packaging tasks easier."
msgstr "``ubuntu-dev-tools`` （和 ``devscripts`` ，一个直接依賴）——一個工具集，使許多打包任務更容易。"

#: ../ubuntu-packaging-guide/getting-set-up.rst:48
msgid ""
"``apt-file`` provides an easy way to find the binary package that contains a "
"given file."
msgstr "``apt-file`` 提供了一個簡單的方法來查找包含一個給定文件的是哪个二進制包。"

#: ../ubuntu-packaging-guide/getting-set-up.rst:53
msgid "Create your GPG key"
msgstr "創建你的GPG密鑰"

#: ../ubuntu-packaging-guide/getting-set-up.rst:55
msgid ""
"GPG stands for `GNU Privacy Guard <GPG_>`_ and it implements the OpenPGP "
"standard which allows you to sign and encrypt messages and files. This is "
"useful for a number of purposes. In our case it is important that you can "
"sign files with your key so they can be identified as something that you "
"worked on. If you upload a source package to Launchpad, it will only accept "
"the package if it can absolutely determine who uploaded the package."
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:62
msgid "To generate a new GPG key, run::"
msgstr "要生成一個新的GPG密鑰，運行："

#: ../ubuntu-packaging-guide/getting-set-up.rst:66
msgid ""
"GPG will first ask you which kind of key you want to generate. Choosing the "
"default (RSA and DSA) is fine. Next it will ask you about the keysize. The "
"default (currently 2048) is fine, but 4096 is more secure. Afterwards, it "
"will ask you if you want it to expire the key at some stage. It is safe to "
"say \"0\", which means the key will never expire. The last questions will be "
"about your name and email address. Just pick the ones you are going to use "
"for Ubuntu development here, you can add additional email addresses later "
"on. Adding a comment is not necessary. Then you will have to set a "
"passphrase, choose a safe one (a passphrase is just a password which is "
"allowed to include spaces)."
msgstr ""
"GPG "
"首先會問您，您要產生哪一種密鑰。選擇默認（RSA和DSA）的罰款。接下來，它會問你關於密鑰大小。默認值（目前為2048）可以，但4096是更安全的。之後，"
"它會問你，如果你想讓它過期的时间是在什么时候。“0” 就很安全了，這意味著密鑰永遠不會過期。最後一個問題是您的姓名和電子郵件地址。只要挑選那些您要在 "
"Ubuntu "
"開發使用的邮件地址就可以，你也可以之後添加電子郵件地址後。添加評論不是必要的。然後，您必須設置一個密碼，選擇一個安全的密碼（密碼允許包括空格）。"

#: ../ubuntu-packaging-guide/getting-set-up.rst:76
msgid ""
"Now GPG will create a key for you, which can take a little bit of time; it "
"needs random bytes, so if you give the system some work to do it will be "
"just fine.  Move the cursor around, type some paragraphs of random text, "
"load some web page."
msgstr ""
"GPG為您將創建一個密鑰，這可能需要一點點的時間，它需要隨機字節，所以如果你給系統一些工作要做，它會就好了。左右移動光標，​​鍵入一些隨機文本段落，加載一"
"些網頁。"

#: ../ubuntu-packaging-guide/getting-set-up.rst:81
msgid "Once this is done, you will get a message similar to this one::"
msgstr "一旦做到這一點，你會得到一個類似這個消息："

#: ../ubuntu-packaging-guide/getting-set-up.rst:88
msgid "In this case ``43CDE61D`` is the *key ID*."
msgstr "在這裏的情況下  ``43CDE61D`` 就是 *密鑰 ID*."

#: ../ubuntu-packaging-guide/getting-set-up.rst:90
msgid ""
"Next, you need to upload the public part of your key to a keyserver so the "
"world can identify messages and files as yours. To do so, enter::"
msgstr "接下來，您需要上傳你的密鑰的公共部分，所以世界密鑰服務器可以識別您的消息和文件。要做到這一點，請輸入："

#: ../ubuntu-packaging-guide/getting-set-up.rst:95
msgid ""
"This will send your key to the Ubuntu keyserver, but a network of keyservers "
"will automatically sync the key between themselves. Once this syncing is "
"complete, your signed public key will be ready to verify your contributions "
"around the world."
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:102
msgid "Create your SSH key"
msgstr "創建您的 SSH 密鑰"

#: ../ubuntu-packaging-guide/getting-set-up.rst:104
msgid ""
"SSH_ stands for *Secure Shell*, and it is a protocol that allows you to "
"exchange data in a secure way over a network. It is common to use SSH to "
"access and open a shell on another computer, and to use it to securely "
"transfer files. For our purposes, we will mainly be using SSH to securely "
"upload source packages to Launchpad."
msgstr ""
"SSH_ 表示 *Secure Shell* ， 它是一個協議，允許您以安全的方式通過網絡進行數據交換。通常，我們使用 SSH 訪問另一台電腦 "
"，打開一個 shell，並用它來安全地傳輸文件。對於我們這裏目的，我們將主要使用 SSH 安全地把源碼包上傳到 Launchpad。"

#: ../ubuntu-packaging-guide/getting-set-up.rst:110
msgid "To generate an SSH key, enter::"
msgstr "要生成SSH密鑰，輸入："

#: ../ubuntu-packaging-guide/getting-set-up.rst:114
msgid ""
"The default file name usually makes sense, so you can just leave it as it "
"is. For security purposes, it is highly recommended that you use a "
"passphrase."
msgstr "默認的文件名通常是有道理的，所以你可以不用理會它。為了安全起見，我們強烈建議您使用一個口令。"

#: ../ubuntu-packaging-guide/getting-set-up.rst:119
msgid "Set up pbuilder"
msgstr "設置 pbuilder"

#: ../ubuntu-packaging-guide/getting-set-up.rst:121
msgid ""
"``pbuilder`` allows you to build packages locally on your machine. It serves "
"a couple of purposes:"
msgstr "``pbuilder`` 允許您建立您機器上的本地包。它提供許多的用途："

#: ../ubuntu-packaging-guide/getting-set-up.rst:124
msgid ""
"The build will be done in a minimal and clean environment. This helps you "
"make sure your builds succeed in a reproducible way, but without modifying "
"your local system"
msgstr "構建工作將在最小和清潔的環境。這將幫助您確保您以一個可重複的方式成功構建，卻沒有修改您的本地系統"

#: ../ubuntu-packaging-guide/getting-set-up.rst:127
msgid ""
"There is no need to install all necessary *build dependencies* locally"
msgstr "沒有必要本地安裝所有必需的 *構建依賴*"

#: ../ubuntu-packaging-guide/getting-set-up.rst:128
msgid ""
"You can set up multiple instances for various Ubuntu and Debian releases"
msgstr "您可以設置 Ubuntu 和 Debian 發行版的多個不同的實例"

#: ../ubuntu-packaging-guide/getting-set-up.rst:130
msgid "Setting ``pbuilder`` up is very easy, run::"
msgstr "設置 ``pbuilder`` 很簡單，直接運行："

#: ../ubuntu-packaging-guide/getting-set-up.rst:134
msgid ""
"where <release> is for example `xenial`, `zesty`, `artful` or in the case of "
"Debian maybe `sid` or `buster`. This will take a while as it will download "
"all the necessary packages for a \"minimal installation\". These will be "
"cached though."
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:140
msgid "Get set up to work with Launchpad"
msgstr "設置 LaunchPad"

#: ../ubuntu-packaging-guide/getting-set-up.rst:142
msgid ""
"With a basic local configuration in place, your next step will be to "
"configure your system to work with Launchpad. This section will focus on the "
"following topics:"
msgstr "隨著本地的基本配置到位，下一步將是配置您的系統與 Launchpad 工作。本節重點在以下主題："

#: ../ubuntu-packaging-guide/getting-set-up.rst:146
msgid "What Launchpad is and creating a Launchpad account"
msgstr "LaunchPad 介紹和創建一個 Launchpad 帳戶"

#: ../ubuntu-packaging-guide/getting-set-up.rst:147
msgid "Uploading your GPG and SSH keys to Launchpad"
msgstr "上傳您的 GPG 和 SSH 密鑰到 Launchpad"

#: ../ubuntu-packaging-guide/getting-set-up.rst:148
msgid ""
"Configure your shell to recognize you (for putting your name in changelogs)"
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:152
msgid "About Launchpad"
msgstr "關於 Launchpad"

#: ../ubuntu-packaging-guide/getting-set-up.rst:154
msgid ""
"Launchpad is the central piece of infrastructure we use in Ubuntu. It not "
"only stores our packages and our code, but also things like translations, "
"bug reports, and information about the people who work on Ubuntu and their "
"team memberships.  You will also use Launchpad to publish your proposed "
"fixes, and get other Ubuntu developers to review and sponsor them."
msgstr ""
"LaunchPad 是我們使用 Ubuntu 中的 Ubuntu 基礎設施的中心部分。它不僅存儲了我們的包和我們的代碼，還有還翻譯，bug報告，以及在 "
"Ubuntu 工作的人和他們的團隊成員的信息等等。您還將使用 Launchpad 的發布您的建議修復，並得到其他 Ubuntu 的開發者的審查和贊助。"

#: ../ubuntu-packaging-guide/getting-set-up.rst:160
msgid ""
"You will need to register with Launchpad and provide a minimal amount of "
"information. This will allow you to download and upload code, submit bug "
"reports, and more."
msgstr "您需要註冊 Launchpad 和提供少量的信息。這將允許您下載和上傳代碼，提交 bug 報告，以及更多。"

#: ../ubuntu-packaging-guide/getting-set-up.rst:164
msgid ""
"Besides hosting Ubuntu, Launchpad can host any Free Software project. For "
"more information see the `Launchpad Help wiki "
"<https://help.launchpad.net/>`_."
msgstr ""
"除了託管 Ubuntu 的項目，Launchpad 可以舉辦任何自由軟件項目。欲了解更多信息，請參閱 `Launchpad Help wiki "
"<https://help.launchpad.net/>`_ 。"

#: ../ubuntu-packaging-guide/getting-set-up.rst:169
msgid "Get a Launchpad account"
msgstr "獲取 Launchpad 帳戶"

#: ../ubuntu-packaging-guide/getting-set-up.rst:171
msgid ""
"If you don't already have a Launchpad account, you can easily `create one "
"<LP-AccountCreate_>`_. If you have a Launchpad account but cannot remember "
"your Launchpad id, you can find this out by going to https://launchpad.net/~ "
"and looking for the part after the `~` in the URL."
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:176
msgid ""
"Launchpad's registration process will ask you to choose a display name. It "
"is encouraged for you to use your real name here so that your Ubuntu "
"developer colleagues will be able to get to know you better."
msgstr "Launchpad 的註冊過程中會問您選擇的顯示名稱。鼓勵您使用您的真實姓名，讓您的 Ubuntu 開發的同事將能夠得到更好地了解您。"

#: ../ubuntu-packaging-guide/getting-set-up.rst:180
msgid ""
"When you register a new account, Launchpad will send you an email with a "
"link you need to open in your browser in order to verify your email address. "
"If you don't receive it, check in your spam folder."
msgstr ""
"當您註冊一個新帳戶，LaunchPad將發送給您一封電子郵件，其中有個一個鏈接。您需要在您的瀏覽器中打開它，以驗證您的電子郵件地址。如果您未收到郵件，請檢"
"查您的垃圾郵件文件夾中。"

#: ../ubuntu-packaging-guide/getting-set-up.rst:184
msgid ""
"`The new account help page <LP-AccountHelp_>`_ on Launchpad has more "
"information about the process and additional settings you can change."
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:191
msgid "Upload your GPG key to Launchpad"
msgstr "上傳您的 GPG 公鑰到 Launchpad"

#: ../ubuntu-packaging-guide/getting-set-up.rst:193
msgid "First, you will need to get your fingerprint and key ID."
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:195
msgid "To find about your GPG fingerprint, run::"
msgstr "要找到你的 GPG 指紋，運行："

#: ../ubuntu-packaging-guide/getting-set-up.rst:199
msgid "and it will print out something like::"
msgstr "它會打印出類似："

#: ../ubuntu-packaging-guide/getting-set-up.rst:206
msgid "Then run this command to submit your key to Ubuntu keyserver::"
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:210
msgid ""
"where ``43CDE61D`` should be replaced by your key ID (which is in the first "
"line of output of the previous command). Now you can import your key to "
"Launchpad."
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:214
msgid ""
"Head to https://launchpad.net/~/+editpgpkeys and copy the \"Key "
"fingerprint\" into the text box. In the case above this would be ``5C28 0144 "
"FB08 91C0 2CF3  37AC 6F0B F90F 43CD E61D``. Now click on \"Import Key\"."
msgstr ""
"打開連接 https://launchpad.net/~/+editpgpkeys 然後複製 “密鑰指紋”到文本框中。在這裏例子中是 ``5C28 "
"0144 FB08 91C0 2CF3  37AC 6F0B F90F 43CD E61D`` 。現在點擊“導入公鑰”。"

#: ../ubuntu-packaging-guide/getting-set-up.rst:219
msgid ""
"Launchpad will use the fingerprint to check the Ubuntu key server for your "
"key and, if successful, send you an encrypted email asking you to confirm "
"the key import. Check your email account and read the email that Launchpad "
"sent you. `If your email client supports OpenPGP encryption, it will prompt "
"you for the password you chose for the key when GPG generated it. Enter the "
"password, then click the link to confirm that the key is yours.`"
msgstr ""
"LaunchPad 將使用指紋在 Ubuntu "
"的密鑰服務器上查找您的公鑰，如果成功的話，將給您發送一個加密電子郵件，要求您確認導入的公鑰。請檢查您的電子郵件帳戶，閱讀 Launchpad "
"發送您的電子郵件 。` 如果您的電子郵件客戶端支持 OpenPGP 加密，它會提示您選擇 "
"GPG生成的密鑰。輸入對應的密碼，然後點擊鏈接以確認公鑰是您的。`"

#: ../ubuntu-packaging-guide/getting-set-up.rst:226
msgid ""
"Launchpad encrypts the email, using your public key, so that it can be sure "
"that the key is yours. If you are using Thunderbird, the default Ubuntu "
"email client, you can install the `Enigmail plugin <Enigmail_>`_ to easily "
"decrypt the message. If your email software does not support OpenPGP "
"encryption, copy the encrypted email's contents, type ``gpg`` in your "
"terminal, then paste the email contents into your terminal window."
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:236
msgid ""
"Back on the Launchpad website, use the Confirm button and Launchpad will "
"complete the import of your OpenPGP key."
msgstr "返回到 Launchpad 網站上，點擊“確認”按鈕，Launchpad 將完成您的 OpenPGP 公鑰導入。"

#: ../ubuntu-packaging-guide/getting-set-up.rst:239
msgid ""
"Find more information at "
"https://help.launchpad.net/YourAccount/ImportingYourPGPKey"
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:243
msgid "Upload your SSH key to Launchpad"
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:245
msgid ""
"Open https://launchpad.net/~/+editsshkeys in a web browser, also open "
"``~/.ssh/id_rsa.pub`` in a text editor. This is the public part of your SSH "
"key, so it is safe to share it with Launchpad. Copy the contents of the file "
"and paste them into the text box on the web page that says \"Add an SSH "
"key\". Now click \"Import Public Key\"."
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:251
msgid ""
"For more information on this process, visit the `creating an SSH keypair "
"<genssh_>`_ page on Launchpad."
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:258
msgid "Configure your shell"
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:259
msgid ""
"The Debian/Ubuntu packaging tools need to learn about you as well in order "
"to properly credit you in the changelog. Simply open your `~/.bashrc` in a "
"text editor and add something like this to the bottom of it::"
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:266
msgid "Now save the file and either restart your terminal or run::"
msgstr ""

#: ../ubuntu-packaging-guide/getting-set-up.rst:270
msgid ""
"(If you do not use the default shell, which is `bash`, please edit the "
"configuration file for that shell accordingly.)"
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:9
msgid "Ubuntu Packaging Guide"
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:11
msgid "Welcome to the Ubuntu Packaging and Development Guide!"
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:13
msgid ""
"This is the official place for learning all about Ubuntu Development and "
"packaging. After reading this guide you will have:"
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:16
msgid ""
"Heard about the most important players, processes and tools in Ubuntu "
"development,"
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:18
msgid "Your development environment set up correctly,"
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:19
msgid "A better idea of how to join our community,"
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:20
msgid "Fixed an actual Ubuntu bug as part of the tutorials."
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:22
msgid ""
"Ubuntu is not only a free and open source operating system, its platform is "
"also open and developed in a transparent fashion. The source code for every "
"single component can be obtained easily and every single change to the "
"Ubuntu platform can be reviewed."
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:27
msgid ""
"This means you can actively get involved in improving it and the community "
"of Ubuntu platform developers is always interested in helping peers getting "
"started."
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:31
msgid ""
"Ubuntu is also a community of great people who believe in free software and "
"that it should be accessible for everyone. Its members are welcoming and "
"want you to be involved as well. We want you to get involved, to ask "
"questions, to make Ubuntu better together with us."
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:36
msgid ""
"If you run into problems: don't panic! Check out the :doc:`communication "
"article<./communication>` and you will find out how to most easily get in "
"touch with other developers."
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:40
msgid "The guide is split up into two sections:"
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:42
msgid "A list of articles based on tasks, things you want to get done."
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:43
msgid ""
"A set of knowledge-base articles that dig deeper into specific bits of our "
"tools and workflows."
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:47
msgid "Articles"
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:64
msgid "Knowledge Base"
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:79
#: ../ubuntu-packaging-guide/libraries.rst:150
msgid "Further Reading"
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:81
msgid ""
"You can read this guide offline in different formats, if you install one of "
"the `binary packages <BinPkgs_>`_."
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:84
msgid ""
"If you want to learn more about building Debian packages, here are some "
"Debian resources you may find useful:"
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:87
msgid "`How to package for Debian <HowToPackage_>`_;"
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:88
msgid "`Debian Policy Manual <Policy_>`_;"
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:89
msgid ""
"`Debian New Maintainers' Guide <NewMaintGuide_>`_ — available in many "
"languages;"
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:90
msgid ""
"`Packaging tutorial <PkgTutorial_>`_ (also available as a `package "
"<PkgTutorialPkg_>`_);"
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:91
msgid "`Guide for Packaging Python Modules <PythonModules_>`_."
msgstr ""

#: ../ubuntu-packaging-guide/index.rst:93
msgid ""
"We are always looking to improve this guide. If you find any problems or "
"have some suggestions, please `report a bug on Launchpad <Bugs_>`_. If you'd "
"like to help work on the guide, `grab the source <Source_>`_ there as well."
msgstr ""

#: ../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:3
msgid "Introduction to Ubuntu Development"
msgstr ""

#: ../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:5
msgid ""
"Ubuntu is made up of thousands of different components, written in many "
"different programming languages. Every component -  be it a software "
"library, a tool or a graphical application - is available as a source "
"package. Source packages in most cases consist of two parts: the actual "
"source code and metadata. Metadata includes the dependencies of the package, "
"copyright and licensing information, and instructions on how to build the "
"package. Once this source package is compiled, the build process provides "
"binary packages, which are the .deb files users can install."
msgstr ""

#: ../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:14
msgid ""
"Every time a new version of an application is released, or when someone "
"makes a change to the source code that goes into Ubuntu, the source package "
"must be uploaded to Launchpad's build machines to be compiled. The resulting "
"binary packages then are distributed to the archive and its mirrors in "
"different countries. The URLs in ``/etc/apt/sources.list`` point to an "
"archive or mirror. Every day images are built for a selection of different "
"Ubuntu flavours. They can be used in various circumstances. There are images "
"you can put on a USB key, you can burn them on DVDs, you can use netboot "
"images and there are images suitable for your phone and tablet. Ubuntu "
"Desktop, Ubuntu Server, Kubuntu and others specify a list of required "
"packages that get on the image. These images are then used for installation "
"tests and provide the feedback for further release planning."
msgstr ""

#: ../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:27
msgid ""
"Ubuntu's development is very much dependent on the current stage of the "
"release cycle. We release a new version of Ubuntu every six months, which is "
"only possible because we have established strict freeze dates. With every "
"freeze date that is reached developers are expected to make fewer, less "
"intrusive changes. Feature Freeze is the first big freeze date after the "
"first half of the cycle has passed. At this stage features must be largely "
"implemented. The rest of the cycle is supposed to be focused on fixing bugs. "
"After that the user interface, then the documentation, the kernel, etc. are "
"frozen, then the beta release is put out which receives a lot of testing. "
"From the beta release onwards, only critical bugs get fixed and a release "
"candidate release is made and if it does not contain any serious problems, "
"it becomes the final release."
msgstr ""

#: ../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:42
msgid ""
"Thousands of source packages, billions of lines of code, hundreds of "
"contributors require a lot of communication and planning to maintain high "
"standards of quality. At the beginning and in the middle of each release "
"cycle we have the Ubuntu Developer Summit where developers and contributors "
"come together to plan the features of the next releases. Every feature is "
"discussed by its stakeholders and a specification is written that contains "
"detailed information about its assumptions, implementation, the necessary "
"changes in other places, how to test it and so on. This is all done in an "
"open and transparent fashion, so you can participate remotely and listen to "
"a videocast, chat with attendants and subscribe to changes of "
"specifications, so you are always up to date."
msgstr ""

#: ../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:54
msgid ""
"Not every single change can be discussed in a meeting though, particularly "
"because Ubuntu relies on changes that are done in other projects. That is "
"why contributors to Ubuntu constantly stay in touch. Most teams or projects "
"use dedicated mailing lists to avoid too much unrelated noise. For more "
"immediate coordination, developers and contributors use Internet Relay Chat "
"(IRC). All discussions are open and public."
msgstr ""

#: ../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:61
msgid ""
"Another important tool regarding communication is bug reports. Whenever a "
"defect is found in a package or piece of infrastructure, a bug report is "
"filed in Launchpad. All information is collected in that report and its "
"importance, status and assignee updated when necessary. This makes it an "
"effective tool to stay on top of bugs in a package or project and organise "
"the workload."
msgstr ""

#: ../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:68
msgid ""
"Most of the software available through Ubuntu is not written by Ubuntu "
"developers themselves. Most of it is written by developers of other Open "
"Source projects and then integrated into Ubuntu. These projects are called "
"\"Upstreams\", because their source code flows into Ubuntu, where we "
"\"just\" integrate it. The relationship to Upstreams is critically important "
"to Ubuntu. It is not just code that Ubuntu gets from Upstreams, but it is "
"also that Upstreams get users, bug reports and patches from Ubuntu (and "
"other distributions)."
msgstr ""

#: ../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:77
msgid ""
"The most important Upstream for Ubuntu is Debian. Debian is the distribution "
"that Ubuntu is based on and many of the design decisions regarding the "
"packaging infrastructure are made there. Traditionally, Debian has always "
"had dedicated maintainers for every single package or dedicated maintenance "
"teams. In Ubuntu there are teams that have an interest in a subset of "
"packages too, and naturally every developer has a special area of expertise, "
"but participation (and upload rights) generally is open to everyone who "
"demonstrates ability and willingness."
msgstr ""

#: ../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:86
msgid ""
"Getting a change into Ubuntu as a new contributor is not as daunting as it "
"seems and can be a very rewarding experience. It is not only about learning "
"something new and exciting, but also about sharing the solution and solving "
"a problem for millions of users out there."
msgstr ""

#: ../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:91
msgid ""
"Open Source Development happens in a distributed world with different goals "
"and different areas of focus. For example there might be the case that a "
"particular Upstream is interested in working on a new big feature while "
"Ubuntu, because of the tight release schedule, is interested in shipping a "
"solid version with just an additional bug fix. That is why we make use of "
"\"Distributed Development\", where code is being worked on in various "
"branches that are merged with each other after code reviews and sufficient "
"discussion."
msgstr ""

#: ../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:101
msgid ""
"In the example mentioned above it would make sense to ship Ubuntu with the "
"existing version of the project, add the bugfix, get it into Upstream for "
"their next release and ship that (if suitable) in the next Ubuntu release. "
"It would be the best possible compromise and a situation where everybody "
"wins."
msgstr ""

#: ../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:106
msgid ""
"To fix a bug in Ubuntu, you would first get the source code for the package, "
"then work on the fix, document it so it is easy to understand for other "
"developers and users, then build the package to test it. After you have "
"tested it, you can easily propose the change to be included in the current "
"Ubuntu development release. A developer with upload rights will review it "
"for you and then get it integrated into Ubuntu."
msgstr ""

#: ../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:115
msgid ""
"When trying to find a solution it is usually a good idea to check with "
"Upstream and see if the problem (or a possible solution) is known already "
"and, if not, do your best to make the solution a concerted effort."
msgstr ""

#: ../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:119
msgid ""
"Additional steps might involve getting the change backported to an older, "
"still supported version of Ubuntu and forwarding it to Upstream."
msgstr ""

#: ../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:122
msgid ""
"The most important requirements for success in Ubuntu development are: "
"having a knack for \"making things work again,\" not being afraid to read "
"documentation and ask questions, being a team player and enjoying some "
"detective work."
msgstr ""

#: ../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:126
msgid ""
"Good places to ask your questions are ``ubuntu-motu@lists.ubuntu.com`` and "
"``#ubuntu-motu`` on ``freenode.``. You will easily find a lot of new friends "
"and people with the same passion that you have: making the world a better "
"place by making better Open Source software."
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:3
msgid "KDE Packaging"
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:5
msgid ""
"Packaging of KDE programs in Ubuntu is managed by the Kubuntu and MOTU "
"teams.  You can contact the Kubuntu team on the `Kubuntu mailing list "
"<KubuntuML_>`_ and ``#kubuntu-devel`` Freenode IRC channel.  More "
"information about Kubuntu development is on the `Kubuntu wiki page <Wiki_>`_."
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:10
msgid ""
"Our packaging follows the practices of the `Debian Qt/KDE Team "
"<QtKDETeam_>`_ and Debian KDE Extras Team.  Most of our packages are derived "
"from the packaging of these Debian teams."
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:15
msgid "Patching Policy"
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:17
msgid ""
"Kubuntu does not add patches to KDE programs unless they come from the "
"upstream authors or submitted upstream with the expectation they will be "
"merged soon or we have consulted the issue with the upstream authors."
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:22
msgid ""
"Kubuntu does not change the branding of packages except where upstream "
"expects this (such as the top left logo of the Kickoff menu) or to simplify "
"(such as removing splash screens)."
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:27
msgid "debian/rules"
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:29
msgid ""
"Debian packages include some additions to the basic Debhelper usage. These "
"are kept in the ``pkg-kde-tools`` package."
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:32
msgid ""
"Packages which use Debhelper 7 should add the ``--with=kde`` option. This "
"will ensure the correct build flags are used and add options such as "
"handling kdeinit stubs and translations::"
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:39
msgid ""
"Some newer KDE packages use the ``dhmk`` system, an alternative to ``dh`` "
"made by the Debian Qt/KDE team.  You can read about it in /usr/share/pkg-kde-"
"tools/qt-kde-team/2/README.  Packages using this will ``include "
"/usr/share/pkg-kde-tools/qt-kde-team/2/debian-qt-kde.mk`` instead of running "
"``dh``."
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:47
msgid "Translations"
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:49
msgid ""
"Packages in main have their translations imported into Launchpad and "
"exported from Launchpad into Ubuntu's language-packs."
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:52
msgid ""
"So any KDE package in main must generate translation templates, include or "
"make available upstream translations and handle ``.desktop`` file "
"translations."
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:56
msgid ""
"To generate translation templates the package must include a ``Messages.sh`` "
"file; complain to the upstream if it does not.  You can check it works by "
"running ``extract-messages.sh`` which should produce one or more ``.pot`` "
"files in ``po/``.  This will be done automatically during build if you use "
"the ``--with=kde`` option to ``dh``."
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:63
msgid ""
"Upstream will usually have also put the translation ``.po`` files into the "
"``po/`` directory.  If they do not, check if they are in separate upstream "
"language packs such as the KDE SC language packs.  If they are in separate "
"language packs Launchpad will need to associate these together manually, "
"contact `David Planella <dpm_>`_ to do this."
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:69
msgid ""
"If a package is moved from universe to main it will need to be re-uploaded "
"before the translations get imported into Launchpad."
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:72
msgid ""
"``.desktop`` files also need translations.  We patch KDELibs to read "
"translations out of ``.po`` files which are pointed to by a line ``X-Ubuntu-"
"Gettext-Domain=`` added to ``.desktop`` files at package build time.  A .pot "
"file for each package is be generated at build time and .po files need to be "
"downloaded from upstream and included in the package or in our language "
"packs.  The list of .po files to be downloaded from KDE's repositories is in "
"``/usr/lib/kubuntu-desktop-i18n/desktop-template-list``."
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:82
msgid "Library Symbols"
msgstr ""

#: ../ubuntu-packaging-guide/kde.rst:84
msgid ""
"Library symbols are tracked in ``.symbols`` files to ensure none go missing "
"for new releases.  KDE uses C++ libraries which act a little differently "
"compared to C libraries.  Debian's Qt/KDE Team have scripts to handle this. "
"See `Working with symbols files <SymbolsFiles_>`_ for how to create and keep "
"these files up to date."
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:3
msgid "Shared Libraries"
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:5
msgid ""
"Shared libraries are compiled code which is intended to be shared among "
"several different programs.  They are distributed as ``.so`` files in "
"``/usr/lib/``."
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:9
msgid ""
"A library exports symbols which are the compiled versions of functions, "
"classes and variables.  A library has a name called an SONAME which includes "
"a version number.  This SONAME version does not necessarily match the public "
"release version number.  A program gets compiled against a given SONAME "
"version of the library.  If any of the symbols is removed or changes then "
"the version number needs to be changed which forces any packages using that "
"library to be recompiled against the new version.  Version numbers are "
"usually set by upstream and we follow them in our binary package names "
"called an ABI number, but sometimes upstreams do not use sensible version "
"numbers and packagers have to keep separate version numbers."
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:21
msgid ""
"Libraries are usually distributed by upstream as standalone releases. "
"Sometimes they are distributed as part of a program.  In this case they can "
"be included in the binary package along with the program (this is called "
"bundling) if you do not expect any other programs to use the library, more "
"often they should be split out into separate binary packages."
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:27
msgid ""
"The libraries themselves are put into a binary package named ``libfoo1`` "
"where ``foo`` is the name of the library and ``1`` is the version from the "
"SONAME. Development files from the package, such as header files, needed to "
"compile programs against the library are put into a package called ``libfoo-"
"dev``."
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:34
msgid "An Example"
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:36
msgid "We will use libnova as an example::"
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:41
msgid "To find the SONAME of the library run::"
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:45
msgid ""
"The SONAME is ``libnova-0.12.so.2``, which matches the file name (usually "
"the case but not always). Here upstream has put the upstream version number "
"as part of the SONAME and given it an ABI version of ``2``.  Library package "
"names should follow the SONAME of the library they contain. The library "
"binary package is called ``libnova-0.12-2`` where ``libnova-0.12`` is the "
"name of the library and ``2`` is our ABI number."
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:52
msgid ""
"If upstream makes incompatible changes to their library they will have to "
"reversion their SONAME and we will have to rename our library.  Any other "
"packages using our library package will need to recompiled against the new "
"version, this is called a transition and can take some effort. Hopefully our "
"ABI number will continue to match upstream's SONAME but sometimes they "
"introduce incompatibilities without changing their version number and we "
"will need to change ours."
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:60
msgid ""
"Looking in debian/libnova-0.12-2.install we see it includes two files::"
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:65
msgid ""
"The last one is the actual library, complete with minor and point version "
"number.  The first one is a symlink which points to the actual library.  The "
"symlink is what programs using the library will look for, the running "
"programs do not care about the minor version number."
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:70
msgid ""
"``libnova-dev.install`` includes all the files needed to compile a program "
"with this library.  Header files, a config binary, the ``.la`` libtool file "
"and ``libnova.so`` which is another symlink pointing at the library, "
"programs compiling against the library do not care about the major version "
"number (although the binary they compile into will)."
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:76
msgid ""
"``.la`` libtool files are needed on some non-Linux systems with poor library "
"support but usually cause more problems than they solve on Debian systems.  "
"It is a current `Debian goal to remove .la files <LAFileRemoval_>`_ and we "
"should help with this."
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:82
msgid "Static Libraries"
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:84
msgid ""
"The -dev package also ships ``usr/lib/libnova.a``.  This is a static "
"library, an alternative to the shared library.  Any program compiled against "
"the static library will include the code directory into itself.  This gets "
"round worrying about binary compatibility of the library.  However it also "
"means that any bugs, including security issues, will not be updated along "
"with the library until the program is recompiled.  For this reason programs "
"using static libraries are discouraged."
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:94
msgid "Symbol Files"
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:96
msgid ""
"When a package builds against a library the ``shlibs`` mechanism will add a "
"package dependency on that library.  This is why most programs will have "
"``Depends: ${shlibs:Depends}`` in ``debian/control``.  That gets replaced "
"with the library dependencies at build time.  However shlibs can only make "
"it depend on the major ABI version number, ``2`` in our libnova example, so "
"if new symbols get added in libnova 2.1 a program using these symbols could "
"still be installed against libnova ABI 2.0 which would then crash."
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:104
msgid ""
"To make the library dependencies more precise we keep ``.symbols`` files "
"that list all the symbols in a library and the version they appeared in."
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:107
msgid ""
"libnova has no symbols file so we can create one.  Start by compiling the "
"package::"
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:112
msgid ""
"The ``-nc`` will cause it to finish at the end of compilation without "
"removing the built files.  Change to the build and run ``dpkg-gensymbols`` "
"for the library package::"
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:119
msgid "This makes a diff file which you can self apply::"
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:123
msgid ""
"Which will create a file named similar to ``dpkg-gensymbolsnY_WWI`` that "
"lists all the symbols.  It also lists the current package version.  We can "
"remove the packaging version from that listed in the symbols file because "
"new symbols are not generally added by new packaging versions, but by the "
"upstream developers::"
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:130
msgid "Now move the file into its location, commit and do a test build::"
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:138
msgid ""
"If it successfully compiles the symbols file is correct.  With the next "
"upstream version of libnova you would run dpkg-gensymbols again and it will "
"give a diff to update the symbols file."
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:143
msgid "C++ Library Symbols Files"
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:145
msgid ""
"C++ has even more exacting standards of binary compatibility than C.  The "
"Debian Qt/KDE Team maintain some scripts to handle this, see their `Working "
"with symbols files <SymbolsFiles_>`_ page for how to use them."
msgstr ""

#: ../ubuntu-packaging-guide/libraries.rst:152
msgid ""
"Junichi Uekawa's `Debian Library Packaging Guide <LibraryGuide_>`_ goes into "
"this topic in more detail."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:3
msgid "Packaging New Software"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:5
msgid ""
"While there are thousands of packages in the Ubuntu archive, there are still "
"a lot nobody has gotten to yet. If there is an exciting new piece of "
"software that you feel needs wider exposure, maybe you want to try your hand "
"at creating a package for Ubuntu or a PPA_. This guide will take you through "
"the steps of packaging new software."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:11
msgid ""
"You will want to read the :doc:`Getting Set Up<./getting-set-up>` article "
"first in order to prepare your development environment."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:15
msgid "Checking the Program"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:17
msgid ""
"The first stage in packaging is to get the released tar from upstream (we "
"call the authors of applications \"upstream\") and check that it compiles "
"and runs."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:20
msgid ""
"This guide will take you through packaging a simple application called GNU "
"Hello which has been posted on GNU.org_."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:23
msgid "Download GNU Hello::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:27
msgid "Now uncompress it::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:32
msgid ""
"This application uses the autoconf build system so we want to run "
"``./configure`` to prepare for compilation."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:35
msgid ""
"This will check for the required build dependencies. As ``hello`` is a "
"simple example, ``build-essential`` should provide everything we need. For "
"more complex programs, the command will fail if you do not have the needed "
"libraries and development files. Install the needed packages and repeat "
"until the command runs successfully.::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:43
msgid "Now you can compile the source::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:47
msgid ""
"If compilation completes successfully you can install and run the program::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:53
msgid "Starting a Package"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:55
msgid ""
"``bzr-builddeb`` includes a plugin to create a new package from a template. "
"The plugin is a wrapper around the ``dh_make`` command.  Run the command "
"providing the package name, version number, and path to the upstream "
"tarball::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:63
msgid ""
"When it asks what type of package type ``s`` for single binary. This will "
"import the code into a branch and add the ``debian/`` packaging directory.  "
"Have a look at the contents.  Most of the files it adds are only needed for "
"specialist packages (such as Emacs modules) so you can start by removing the "
"optional example files::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:72
msgid "You should now customise each of the files."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:74
msgid ""
"In ``debian/changelog`` change the version number to an Ubuntu version: "
"``2.10-0ubuntu1`` (upstream version 2.10, Debian version 0, Ubuntu version "
"1).  Also change ``unstable`` to the current development Ubuntu release such "
"as ``trusty``."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:79
msgid ""
"Much of the package building work is done by a series of scripts called "
"``debhelper``.  The exact behaviour of ``debhelper`` changes with new major "
"versions, the compat file instructs ``debhelper`` which version to act as.  "
"You will generally want to set this to the most recent version which is "
"``9``."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:85
msgid ""
"``control`` contains all the metadata of the package.  The first paragraph "
"describes the source package. The second and following paragraphs describe "
"the binary packages to be built.  We will need to add the packages needed to "
"compile the application to ``Build-Depends:``. For ``hello``, make sure that "
"it includes at least::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:93
msgid ""
"You will also need to fill in a description of the program in the "
"``Description:`` field."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:96
msgid ""
"``copyright`` needs to be filled in to follow the licence of the upstream "
"source.  According to the hello/COPYING file this is GNU GPL 3 or later."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:99
msgid ""
"``docs`` contains any upstream documentation files you think should be "
"included in the final package."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:102
msgid ""
"``README.source`` and ``README.Debian`` are only needed if your package has "
"any non-standard features, we don't so you can delete them."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:105
msgid ""
"``source/format`` can be left as is, this describes the version format of "
"the source package and should be ``3.0 (quilt)``."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:108
msgid ""
"``rules`` is the most complex file.  This is a Makefile which compiles the "
"code and turns it into a binary package.  Fortunately most of the work is "
"automatically done these days by ``debhelper 7`` so the universal ``%`` "
"Makefile target just runs the ``dh`` script which will run everything needed."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:113
msgid ""
"All of these file are explained in more detail in the :doc:`overview of the "
"debian directory<./debian-dir-overview>` article."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:116
msgid "Finally commit the code to your packaging branch::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:122
msgid "Building the package"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:124
msgid ""
"Now we need to check that our packaging successfully compiles the package "
"and builds the .deb binary package::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:130
msgid ""
"``bzr builddeb`` is a command to build the package in its current location. "
"The ``-us -uc`` tell it there is no need to GPG sign the package.  The "
"result will be placed in ``..``."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:134
msgid "You can view the contents of the package with::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:138
msgid ""
"Install the package and check it works (later you will be able to uninstall "
"it using ``sudo apt-get remove hello`` if you want)::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:143
msgid "You can also install all packages at once using::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:148
msgid "Next Steps"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:150
msgid ""
"Even if it builds the .deb binary package, your packaging may have bugs.  "
"Many errors can be automatically detected by our tool ``lintian`` which can "
"be run on the source .dsc metadata file, .deb binary packages or .changes "
"file::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:158
msgid ""
"To see verbose description of the problems use ``--info`` lintian flag or "
"``lintian-info`` command."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:161
msgid ""
"For Python packages, there is also a ``lintian4python`` tool that provides "
"some additional lintian checks."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:164
msgid ""
"After making a fix to the packaging you can rebuild using ``-nc`` \"no "
"clean\" without having to build from scratch::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:169
msgid ""
"Having checked that the package builds locally you should ensure it builds "
"on a clean system using ``pbuilder``. Since we are going to upload to a PPA "
"(Personal Package Archive) shortly, this upload will need to be *signed* to "
"allow Launchpad to verify that the upload comes from you (you can tell the "
"upload will be signed because the ``-us`` and ``-uc`` flags are not passed "
"to ``bzr builddeb`` like they were before). For signing to work you need to "
"have set up GPG. If you haven't set up ``pbuilder-dist`` or GPG yet, "
":doc:`do so now<./getting-set-up>`::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:182
msgid ""
"When you are happy with your package you will want others to review it.  You "
"can upload the branch to Launchpad for review::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:187
msgid ""
"Uploading it to a PPA will ensure it builds and give an easy way for you and "
"others to test the binary packages.  You will need to set up a PPA in "
"Launchpad and then upload with ``dput``::"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:193
msgid ""
"You can ask for reviews in ``#ubuntu-motu`` IRC channel, or on the `MOTU "
"mailing list <ubuntu-motu_>`_.  There might also be a more specific team you "
"could ask such as the GNU team for more specific questions."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:198
msgid "Submitting for inclusion"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:200
msgid ""
"There are a number of paths that a package can take to enter Ubuntu. In most "
"cases, going through Debian first can be the best path. This way ensures "
"that your package will reach the largest number of users as it will be "
"available in not just Debian and Ubuntu but all of their derivatives as "
"well. Here are some useful links for submitting new packages to Debian:"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:207
msgid ""
"`Debian Mentors FAQ <MentorsFAQ_>`_ - debian-mentors is for the mentoring of "
"new and prospective Debian Developers. It is where you can find a sponsor to "
"upload your package to the archive."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:211
msgid ""
"`Work-Needing and Prospective Packages <WNPP_>`_ - Information on how to "
"file \"Intent to Package\" and \"Request for Package\" bugs as well as list "
"of open ITPs and RFPs."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:215
msgid ""
"`Debian Developer's Reference, 5.1. New packages <DevRef_>`_ - The entire "
"document is invaluable for both Ubuntu and Debian packagers. This section "
"documents processes for submitting new packages."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:219
msgid ""
"In some cases, it might make sense to go directly into Ubuntu first. For "
"instance, Debian might be in a freeze making it unlikely that your package "
"will make it into Ubuntu in time for the next release. This process is "
"documented on the `\"New Packages\" <NewPackages_>`_ section of the Ubuntu "
"wiki."
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:225
msgid "Screenshots"
msgstr ""

#: ../ubuntu-packaging-guide/packaging-new-software.rst:227
msgid ""
"Once you have uploaded a package to debian, you should add screenshots to "
"allow propective users to see what the program is like. These should be "
"uploaded to http://screenshots.debian.net/upload ."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:3
msgid "Patches to Packages"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:5
msgid ""
"Sometimes, Ubuntu package maintainers have to change the upstream source "
"code in order to make it work properly on Ubuntu.  Examples include, patches "
"to upstream that haven't yet made it into a released version, or changes to "
"the upstream's build system needed only for building it on Ubuntu.  We could "
"change the upstream source code directly, but doing this makes it more "
"difficult to remove the patches later when upstream has incorporated them, "
"or extract the change to submit to the upstream project.  Instead, we keep "
"these changes as separate patches, in the form of diff files."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:14
msgid ""
"There are a number of different ways of handling patches in Debian packages, "
"fortunately we are standardizing on one system, `Quilt`_, which is now used "
"by most packages."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:18
msgid "Let's look at an example package, ``kamoso`` in Trusty::"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:22
msgid ""
"The patches are kept in ``debian/patches``.  This package has one patch "
"``kubuntu_01_fix_qmax_on_armel.diff`` to fix a compile failure on ARM.  The "
"patch has been given a name to describe what it does, a number to keep the "
"patches in order (two patches can overlap if they change the same file) and "
"in this case the Kubuntu team adds their own prefix to show the patch comes "
"from them rather than from Debian."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:29
msgid "The order of patches to apply is kept in ``debian/patches/series``."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:32
msgid "Patches with Quilt"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:34
msgid ""
"Before working with Quilt you need to tell it where to find the patches.  "
"Add this to your ``~/.bashrc``::"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:39
msgid "And source the file to apply the new export::"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:43
msgid ""
"By default all patches are applied already to UDD checkouts or downloaded "
"packages.  You can check this with::"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:49
msgid "If you wanted to remove the patch you would run ``pop``::"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:57
msgid "And to apply a patch you use ``push``::"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:67
msgid "Adding a New Patch"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:69
msgid ""
"To add a new patch you need to tell Quilt to create a new patch, tell it "
"which files that patch should change, edit the files then refresh the patch::"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:81
msgid ""
"The ``quilt add`` step is important, if you forget it the files will not end "
"up in the patch."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:84
msgid ""
"The change will now be in "
"``debian/patches/kubuntu_02_program_description.diff`` and the ``series`` "
"file will have had the new patch added to it.  You should add the new file "
"to the packaging::"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:94
msgid ""
"Quilt keeps its metadata in the ``.pc/`` directory, so currently you need to "
"add that to the packaging too.  This should be improved in future."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:97
msgid ""
"As a general rule you should be careful adding patches to programs unless "
"they come from upstream, there is often a good reason why that change has "
"not already been made.  The above example changes a user interface string "
"for example, so it would break all translations.  If in doubt, do ask the "
"upstream author before adding a patch."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:105
msgid "Patch Headers"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:107
msgid ""
"We recommend that you tag every patch with DEP-3_ headers by putting them at "
"the top of patch file. Here are some headers that you can use:"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:0
msgid "Description"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:110
msgid ""
"Description of what the patch does. It is formatted like ``Description`` "
"field in ``debian/control``: first line is short description, starting with "
"lowercase letter, the next lines are long description, indented with a space."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:0
msgid "Author"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:114
msgid "Who wrote the patch (i.e. \"Jane Doe <packager@example.com>\")."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:0
msgid "Origin"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:115
msgid ""
"Where this patch comes from (i.e. \"upstream\"), when *Author* is not "
"present."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:0
msgid "Bug-Ubuntu"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:117
msgid ""
"A link to Launchpad bug, a short form is preferred (like "
"*https://bugs.launchpad.net/bugs/XXXXXXX*). If there are also bugs in "
"upstream or Debian bugtrackers, add *Bug* or *Bug-Debian* headers."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:0
msgid "Forwarded"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:121
msgid ""
"Whether the patch was forwarded upstream. Either \"yes\", \"no\" or \"not-"
"needed\"."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:0
msgid "Last-Update"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:123
msgid "Date of the last revision (in form \"YYYY-MM-DD\")."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:127
msgid "Upgrading to New Upstream Versions"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:129
msgid ""
"To upgrade to the new version, you can use ``bzr merge-upstream`` command::"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:133
msgid ""
"When you run this command, all patches will be unapplied, because they can "
"become out of date. They might need to be refreshed to match the new "
"upstream source or they might need to be removed altogether. To check for "
"problems, apply the patches one at a time::"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:145
msgid ""
"If it can be reverse-applied this means the patch has been applied already "
"by upstream, so we can delete the patch::"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:151
msgid "Then carry on::"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:156
msgid ""
"It is a good idea to run refresh, this will update the patch relative to the "
"changed upstream source::"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:162
msgid "Then commit as usual::"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:168
msgid "Making A Package Use Quilt"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:170
msgid ""
"Modern packages use Quilt by default, it is built into the packaging format. "
" Check in ``debian/source/format`` to ensure it says ``3.0 (quilt)``."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:174
msgid ""
"Older packages using source format 1.0 will need to explicitly use Quilt, "
"usually by including a makefile into ``debian/rules``."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:179
msgid "Configuring Quilt"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:181
msgid ""
"You can use ``~/.quiltrc`` file to configure quilt. Here are some options "
"that can be useful for using quilt with debian/packages:"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:195
msgid "Other Patch Systems"
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:197
msgid ""
"Other patch systems used by packages include ``dpatch`` and ``cdbs simple-"
"patchsys``, these work similarly to Quilt by keeping patches in "
"``debian/patches`` but have different commands to apply, un-apply or create "
"patches. You can find out which patch system is used by a package by using "
"the ``what-patch`` command (from the ``ubuntu-dev-tools`` package). You can "
"use ``edit-patch``, shown in :ref:`previous chapters <working-on-a-fix>`, as "
"a reliable way to work with all systems."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:205
msgid ""
"In even older packages changes will be included directly to sources and kept "
"in the ``diff.gz`` source file.  This makes it hard to upgrade to new "
"upstream versions or differentiate between patches and is best avoided."
msgstr ""

#: ../ubuntu-packaging-guide/patches-to-packages.rst:209
msgid ""
"Do not change a package's patch system without discussing it with the Debian "
"maintainer or relevant Ubuntu team.  If there is no existing patch system "
"then feel free to add Quilt."
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:3
msgid "Security and Stable Release Updates"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:6
msgid "Fixing a Security Bug in Ubuntu"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:11
msgid ""
"Fixing security bugs in Ubuntu is not really any different than :doc:`fixing "
"a regular bug in Ubuntu<./fixing-a-bug>`, and it is assumed that you are "
"familiar with patching normal bugs. To demonstrate where things are "
"different, we will be updating the dbus package in Ubuntu 12.04 LTS (Precise "
"Pangolin) for a security update."
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:19
msgid "Obtaining the source"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:21
msgid ""
"In this example, we already know we want to fix the dbus package in Ubuntu "
"12.04 LTS (Precise Pangolin). So first you need to determine the version of "
"the package you want to download. We can use the ``rmadison`` to help with "
"this::"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:30
msgid ""
"Typically you will want to choose the highest version for the release you "
"want to patch that is not in -proposed or -backports. Since we are updating "
"Precise's dbus, you'll download 1.4.18-1ubuntu1.4 from precise-updates::"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:38
msgid "Patching the source"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:39
msgid ""
"Now that we have the source package, we need to patch it to fix the "
"vulnerability. You may use whatever patch method that is appropriate for the "
"package, but this example will use ``edit-patch`` (from the ubuntu-dev-tools "
"package). ``edit-patch`` is the easiest way to patch packages and it is "
"basically a wrapper around every other patch system you can imagine."
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:45
msgid "To create your patch using ``edit-patch``::"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:50
msgid ""
"This will apply the existing patches and put the packaging in a temporary "
"directory. Now edit the files needed to fix the vulnerability.  Often "
"upstream will have provided a patch so you can apply that patch::"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:56
msgid ""
"After making the necessary changes, you just hit Ctrl-D or type exit to "
"leave the temporary shell."
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:60
msgid "Formatting the changelog and patches"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:62
msgid ""
"After applying your patches you will want to update the changelog. The "
"``dch`` command is used to edit the ``debian/changelog`` file and ``edit-"
"patch`` will launch ``dch`` automatically after un-applying all the patches. "
"If you are not using ``edit-patch``, you can launch ``dch -i`` manually. "
"Unlike with regular patches, you should use the following format (note the "
"distribution name uses precise-security since this is a security update for "
"Precise) for security updates::"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:79
msgid ""
"Update your patch to use the appropriate patch tags. Your patch should have "
"at a minimum the Origin, Description and Bug-Ubuntu tags. For example, edit "
"debian/patches/99-fix-a-vulnerability.patch to have something like::"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:90
msgid ""
"Multiple vulnerabilities can be fixed in the same security upload; just be "
"sure to use different patches for different vulnerabilities."
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:94
msgid "Test and Submit your work"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:96
msgid ""
"At this point the process is the same as for :doc:`fixing a regular bug in "
"Ubuntu<./fixing-a-bug>`. Specifically, you will want to:"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:99
msgid ""
"Build your package and verify that it compiles without error and without any "
"added compiler warnings"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:101
msgid "Upgrade to the new version of the package from the previous version"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:102
msgid ""
"Test that the new package fixes the vulnerability and does not introduce any "
"regressions"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:104
msgid ""
"Submit your work via a Launchpad merge proposal and file a Launchpad bug "
"being sure to mark the bug as a security bug and to subscribe ``ubuntu-"
"security-sponsors``"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:108
msgid ""
"If the security vulnerability is not yet public then do not file a merge "
"proposal and ensure you mark the bug as private."
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:111
msgid ""
"The filed bug should include a Test Case, i.e. a comment which clearly shows "
"how to recreate the bug by running the old version then how to ensure the "
"bug no longer exists in the new version."
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:115
msgid ""
"The bug report should also confirm that the issue is fixed in Ubuntu "
"versions newer than the one with the proposed fix (in the above example "
"newer than Precise).  If the issue is not fixed in newer Ubuntu versions you "
"should prepare updates for those versions too."
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:122
msgid "Stable Release Updates"
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:124
msgid ""
"We also allow updates to releases where a package has a high impact bug such "
"as a severe regression from a previous release or a bug which could cause "
"data loss.  Due to the potential for such updates to themselves introduce "
"bugs we only allow this where the change can be easily understood and "
"verified."
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:129
msgid ""
"The process for Stable Release Updates is just the same as the process for "
"security bugs except you should subscribe ``ubuntu-sru`` to the bug."
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:132
msgid ""
"The update will go into the ``proposed`` archive (for example ``precise-"
"proposed``) where it will need to be checked that it fixes the problem and "
"does not introduce new problems.  After a week without reported problems it "
"can be moved to ``updates``."
msgstr ""

#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:137
msgid ""
"See the `Stable Release Updates wiki page <SRUWiki_>`_ for more information."
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:3
msgid "Setting up sbuild"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:5
msgid ""
"``sbuild`` simplifies building Debian/Ubuntu binary package from source in "
"clean environment. It allows to try debugging packages in environment "
"similar (as opposed to ``pbuild``) to builders used by Launchpad."
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:9
msgid ""
"It works on different architectures and allows to build packages for other "
"releases. It needs kernel supporting overlayfs."
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:13
msgid "Installing sbuild"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:15
msgid ""
"To use sbuild, you need to install sbuild and other required packages and "
"add yourself to the ``sbuild`` group::"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:21
msgid "Create ``.sbuildrc`` in your home directory with following content::"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:50
msgid ""
"Replace “Your Name <user@example.org>” with your name and e-mail address. "
"Change default distribution if you want, but remember that you can specify "
"target distribution when executing command."
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:54
msgid ""
"If you haven’t restarted your session after adding yourself to the "
"``sbuild`` group, enter::"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:59
msgid ""
"Generate GPG keypair for sbuild and create chroot for specified release::"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:64
msgid ""
"This will create chroot for your current architecture. You might want to "
"specify another architecture. For this, you can use ``--arch`` option. "
"Example::"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:71
msgid "Using schroot"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:74
msgid "Entering schroot"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:76
msgid ""
"You can use ``schroot -c <release>-<architecture> [-u <USER>]`` to enter "
"newly created chroot, but that’s not exactly the reason why you are using "
"sbuild::"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:83
msgid "Using schroot for package building"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:85
msgid ""
"To build package using sbuild chroot, we use (surprisingly) the ``sbuild`` "
"command. For example, to build ``hello`` package from x86_64 chroot, after "
"applying some changes::"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:98
msgid ""
"To build package from source package (``.dsc``), use location of the source "
"package as second parameter::"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:103
msgid ""
"To make use of all power of your CPU, you can specify number of threads used "
"for building using standard ``-j<threads>``::"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:109
msgid "Maintaining schroots"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:112
msgid "Listing chroots"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:114
msgid ""
"To get list of all your sbuild chroots, use ``schroot -l``. The ``source:`` "
"chroots are used as base of new schroots. Changes here aren’t recommended, "
"but if you have specific reason, you can open it using something like::"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:122
msgid "Updating schroots"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:124
msgid "To upgrade the whole schroot::"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:129
msgid "Expiring active schroots"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:131
msgid ""
"If because of any reason, you haven’t stopped your schroot, you can expire "
"all active schroots using::"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:137
#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:136
msgid "Further reading"
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:139
msgid "There is `Debian wiki page <DebianWiki_>`_ covering sbuild usage."
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:141
msgid "`Ubuntu Wiki <UbuntuWiki_>`_ also has article about basics of sbuild."
msgstr ""

#: ../ubuntu-packaging-guide/setting-up-sbuild.rst:143
msgid ""
"``sbuild`` manpages are covering details about sbuild usage and available "
"features."
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:3
msgid "ubuntu-dev-tools: Tools for Ubuntu developers"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:5
msgid ""
"``ubuntu-dev-tools`` package is a collection of 30 tools created for making "
"packaging work much easier for Ubuntu developers. It’s similar in scope to "
"Debian ``devscripts`` package."
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:10
msgid "Setting up packaging environment"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:12
msgid ""
"``setup-packaging-environment`` command allows to interactively set up "
"packaging environment, including setting environment variables, installing "
"required packages and ensuring that required repositories are enabled."
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:17
msgid "Environment variables"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:20
msgid "Introducing yourself"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:22
msgid ""
"``ubuntu-dev-tools`` configurations can be set using environment variables. "
"It’s used for example in changelogs. For example, to set e-mail address (and "
"full name), use ``UBUMAIL`` variable. It overrides the ``DEBEMAIL`` and "
"``DEBFULLNAME`` variables used by ``devscripts``. To learn ``ubuntu-dev-"
"tools`` about you, open `~/.bashrc` in text editor and add something like "
"this::"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:30
msgid ""
"Now, save this file and restart your terminal or use ``source ~/.bashrc``."
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:33
msgid "Changing preferred builder"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:35
msgid ""
"Default builder is specified by ``UBUNTUTOOLS_BUILDER`` variable. To set "
"between *pbuilder* (default), *pbuilder-dist*, and *sbuild*, change this "
"variable. Example::"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:41
msgid "Save file and restart terminal."
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:43
msgid ""
"You can also check whether to update the builder every time before building, "
"by changing ``UBUNTUTOOLS_UPDATE_BUILDER`` from ``no`` (default) to ``yes``."
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:47
msgid "Downloading source packages"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:49
msgid ""
"``ubuntu-dev-tools`` comes with ``pull-lp-source`` command, allowing to "
"download source packages from Launchpad. Its usage is simple. To download "
"latest source package for ubuntu-settings, use::"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:55
msgid ""
"You can also specify release from which you want to download source or "
"specify version of source package. ``-d`` option allows to download source "
"package without extracting. A slightly more complex example would look like "
"this::"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:61
msgid ""
"``pull-debian-source`` package allows to do the same for Debian source "
"packages. It has similar syntax."
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:65
msgid "Backporting packages"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:67
msgid ""
"``ubuntu-dev-tools`` provides ``backportpackage`` allowing us to backport a "
"package from specified release of Ubuntu or Debian. For example, to backport "
"``bzr`` package from latest development release for your installed Ubuntu "
"version, simply::"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:74
msgid ""
"This command allows to use more options. To specify Ubuntu release for which "
"you are going to backport a package, use ``-d  dest`` or ``--"
"destination=DEST`` parameter, where ``DEST`` is Ubuntu release, for example "
"``xenial``. You can specify more than one destination. In turn, ``-s "
"SOURCE`` and ``--source=SOURCE`` specifies the Ubuntu or Debian release from "
"which you are going to backport a package. ``-w DIR`` and ``--workdir=DIR`` "
"specifies directory, where package files will be downloaded, unpacked and "
"built. By default, it will create temporary directory that will be "
"automatically deleted. ``-U`` or ``--update`` allows to update build "
"environment before building package. ``-u`` or ``--upload`` allows to upload "
"package after building (for example to PPAs) using ``dput``."
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:86
msgid "Requesting backports"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:88
msgid ""
"``requestbackport`` command makes creating backports through Launchpad bugs "
"much easier. It creates testing checklist that will be included in the bug. "
"For example, to request backporting libqt5webkit5 from latest development "
"branch to current stable release (without optional parameters)::"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:95
msgid ""
"You should fulfill the checklist if you have already tested the backport."
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:97
msgid ""
"Additional options allows to specify destination of backport and its source, "
"by using ``-d DEST`` or ``--destination=DEST`` and ``s SRC`` or ``--"
"source=SRC``."
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:101
msgid "Other simple commands"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:103
msgid ""
"``ubuntu-dev-tools`` also includes small utilities allowing to do simple "
"tasks like checking whether .iso file is an Ubuntu installation media."
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:107
msgid "``ubuntu-iso``"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:109
msgid "To do this, use ``ubuntu-iso <pathtoiso>``, for example::"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:114
msgid "``bitesize``"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:116
msgid ""
"“Bitesize” tag is used on Launchpad to describe tasks that are suitable for "
"begineers who want to contribute to one of the projects. ``bitesize`` "
"command allows to add “bitesize” tag to Launchpad bug with just simple "
"command, by providing its number, like::"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:124
msgid "``404main``"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:126
msgid ""
"``404main`` allows to check whether all of package build dependencies are "
"included in main repository of specified Ubuntu distribution. Example::"
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:131
msgid ""
"If any of the required packages isn’t part of Ubuntu main repository, you "
"can check whether the package fulfill `Ubuntu main inclusion requirements "
"<Requirements_>`_ and request it."
msgstr ""

#: ../ubuntu-packaging-guide/ubuntu-dev-tools.rst:138
msgid ""
"``ubuntu-dev-tools`` manpages are covering more about usage of this package."
msgstr ""

msgid "translator-credits"
msgstr ""
"Launchpad Contributions:\n"
"  Cheng-Chia Tseng https://launchpad.net/~zerng07\n"
"  Daniel Holbach https://launchpad.net/~dholbach\n"
"  Howard Chan https://launchpad.net/~smartboyhw\n"
"  Z.X.Lyn https://launchpad.net/~newzxl"

#~ msgid ""
#~ "While Debian does not have an automatic testing infrastructure set up yet, "
#~ "they should still be submitted to Debian, as DEP-8 is a Debian specification "
#~ "and Debian developers or users can still manually run the tests."
#~ msgstr ""
#~ "Debian没有設定它們自己的自動測試建構，但它們也應該被提交給Debian, 因為DEP-"
#~ "8是一個Debian規範而Debian開發者或用户也能手動測行測試。"

#~ msgid ""
#~ "Packages in Debian with a testsuite header will also be automatically added "
#~ "when they are synced to Ubuntu."
#~ msgstr "有測試套件頭置於Debian裏的套件在同步到Ubuntu中也會被自動加進。"

#~ msgid ""
#~ "The `PPA documentation on Launchpad`_ is fairly comprehensive and should get "
#~ "you up and running in no time."
#~ msgstr "`Launchpad裏的個人套件庫文件`_是較為全面且應該能夠令您在短時间内設定好。"

#~ msgid ""
#~ "If you should run into any problems, you can join the `#ubuntu-quality IRC "
#~ "channel`_ to get in touch with developers who can help you."
#~ msgstr "如果您有甚麼問题，您可以加入`#ubuntu-quality 網络接力通訊频道`_去聯络能幫助您的開發者。"

#~ msgid ""
#~ "Sometimes you might want to make new functionality available in a stable "
#~ "release which is not connected to a critical bug fix. For these scenarios "
#~ "you have two options: either you `upload to a PPA "
#~ "<https://help.launchpad.net/Packaging/PPA>`_ or prepare a backport."
#~ msgstr ""
#~ "有時後您可能會想把一些不關乎重要臭蟲修復的新功能提供在稳定發行中。在這些情境下您有两個選擇：您可以`上載到個人套件庫 "
#~ "<https://help.launchpad.net/Packaging/PPA>`_或準備一個軟件帶後。"

#~ msgid ""
#~ "This will create a directory ``oneiric`` and install a minimal oneiric "
#~ "system into it."
#~ msgstr "這會建立一個資料夹``oneiric``及在裏面安装一個最小oneiric系統。"

#~ msgid ""
#~ "If your version of ``debootstrap`` does not know about oneiric you can try "
#~ "upgrading to the version in ``backports``."
#~ msgstr "如果您的``debootstrap``版本不知道oneiric您可以試更新到``backports``裏的版本。"

#~ msgid ""
#~ "Full virtual machines can be useful for packaging and testing programs.  "
#~ "TestDrive is a program to automate syncing and running daily ISO images, see "
#~ "`the TestDrive wiki page`_ for more information."
#~ msgstr ""
#~ "完正虚擬機器可以是在包装和測試程式上有用。TestDrive是一個自動同步及運行映像檔的程式，請参阅`TestDrive維基頁面`_以獲取更多資訊。"

#~ msgid ""
#~ "For more information on chroots see our `Debootstrap Chroot wiki page`_."
#~ msgstr "關於chroots的更多資訊請参阅我們的`Debootstrap Chroot 維基頁面`_。"

#~ msgid ""
#~ "SBuild is a system similar to PBuilder for creating an environment to run "
#~ "test package builds in.  It closer matches that used by Launchpad for "
#~ "building packages but takes some more setup compared to PBuilder.  See `the "
#~ "Security Team Build Environment wiki page`_ for a full explanation."
#~ msgstr ""
#~ "SBuild是一個相類於Pbuilder的系統， "
#~ "用於創做一個可以運行測試套件建構的環境。它相似於Launchpad建構套件的系統但需要比Pbuilder更多設定。請参阅`保安隊伍建構維基頁面`_以獲取完"
#~ "整的解釋。"

#~ msgid ""
#~ "Amazon's `EC2 cloud computers`_ allow you to hire a computer paying a few US "
#~ "cents per hour, you can set up Ubuntu machines of any supported version and "
#~ "package on those.  This is useful when you want to compile many packages at "
#~ "the same time or to overcome bandwidth restraints."
#~ msgstr ""
#~ "亞馬遜的`EC2雲端電腦`_讓您在付款每小時數美仙租用一部電腦，您可以設立任何支援的Ubuntu版本的系統並在那包装。如果您想同時间建構很多套件或除去網速"
#~ "限制，這會有幫助。"

#~ msgid ""
#~ "For further information, see the `changelog section (Section 4.4) "
#~ "<http://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog>`_ "
#~ "of the Debian Policy Manual."
#~ msgstr ""
#~ "更多資訊，請参閱Debian規格手册裏的`changelog段落（段4.4）<http://www.debian.org/doc/debian-"
#~ "policy/ch-source.html#s-dpkgchangelog>`_"

#~ msgid ""
#~ "Note that in Ubuntu, we set the ``Maintainer`` field to a general address "
#~ "because anyone can change any package (this differs from Debian where "
#~ "changing packages is usually restricted to an individual or a team). "
#~ "Packages in Ubuntu should generally have the ``Maintainer`` field set to "
#~ "``Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>``. If the "
#~ "Maintainer field is modified, the old value should be saved in the ``XSBC-"
#~ "Original-Maintainer`` field. This can be done automatically with the  "
#~ "``update-maintainer`` script available in the ``ubuntu-dev-tools`` package. "
#~ "For further information, see the `Debian Maintainer Field spec "
#~ "<https://wiki.ubuntu.com/DebianMaintainerField>`_ on the Ubuntu wiki."
#~ msgstr ""
#~ "要注意的是在Ubuntu，我們設定``Maintainer``欄為一個總體地址因為任何人能更改任何套件（這與更改套件是限制到一個人或一個團隊的Debian"
#~ "有不同。Ubuntu的套件總體應把``Maintainer``欄設定為``Ubuntu Developers <ubuntu-devel-"
#~ "discuss@lists.ubuntu.com>``。如果``Maintainer``欄被改變，舊的選項應該被儲存在``XSBC-Original-"
#~ "Maintainer``欄裏。這可以由在``ubuntu-dev-tools``套件裏的``update-maintainer``去自動完成。"

#~ msgid ""
#~ "This file gives the copyright information for both the upstream source and "
#~ "the packaging. Ubuntu and `Debian Policy (Section 12.5) "
#~ "<http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile>`_ "
#~ "require that each package installs a verbatim copy of its copyright and "
#~ "license information to ``/usr/share/doc/$(package_name)/copyright``."
#~ msgstr ""
#~ "這檔案提供上游原始碼及包装的版權資訊。Ubuntu及`Debian規格（段12.5）<http://www.debian.org/doc/debian-"
#~ "policy/ch-docs.html#s-"
#~ "copyrightfile>`_要求每個套件安装一個詳细的版權和許可証資訊到``/usr/share/doc/$(套件名稱)/copyright``。"

#~ msgid ""
#~ "For further information, see the `control file section (Chapter 5) "
#~ "<http://www.debian.org/doc/debian-policy/ch-controlfields.html>`_ of the "
#~ "Debian Policy Manual."
#~ msgstr ""
#~ "更多資訊，請参閱Debian規格手册裏的`control檔案段落（段5）<http://www.debian.org/doc/debian-"
#~ "policy/ch-controlfields.html>`_"

#~ msgid ""
#~ "This example follows the `Machine-readable debian/copyright "
#~ "<http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/>`_ "
#~ "format. You are encouraged to use this format as well."
#~ msgstr ""
#~ "本例子根據`機器能閱讀的debian/copyright <http://www.debian.org/doc/packaging-"
#~ "manuals/copyright-format/1.0>`_規格。您會被推介去一樣使用本規格。"

#~ msgid ""
#~ "The `DEP 8 specification`_ defines how automatic testing can very easily be "
#~ "integrated into packages. To integrate a test into a package, all you need "
#~ "to do is:"
#~ msgstr "`DEP 8 規格`_ 介定了自動測試如何非常容易融入套件中。要把測試融入一個套件，您需要做的是："

#~ msgid "add the following to the Source section in ``debian/control``::"
#~ msgstr "把下列文字加入 ``debian/control`` 裏的原始碼分類中："

#~ msgid "And provision a Raring AMD64 system::"
#~ msgstr "和建立一個 Raring64 位元系統："

#~ msgid ""
#~ "This command will create a pristine Raring AMD64 VM from a cloud image. To "
#~ "run the tests, simply run::"
#~ msgstr "這命令會從雲端映像檔創立一個原始 Raring64 位元虚擬機器。要運行測試，简單地運行："

#~ msgid ""
#~ "While this test is very small and basic, it tests quite a number of core "
#~ "components on a system. This may help to uncover critical issues early on."
#~ msgstr "雖然這個測試是非常小和基本的，但它測試系統上的相當數量的核心組件。這可能有助於早期發現關鍵問題。"

#~ msgid "Then, get the source code from Launchpad::"
#~ msgstr "然後，從 Launchpad 獲取原始碼："

#~ msgid ""
#~ "The downside of this approach is that you test it locally, but can't ensure "
#~ "that this will work in a minimal environment. For example will it be hard to "
#~ "ensure that all the required packages are installed for the tests. With "
#~ "`lp:auto-package-testing`_ we have a more comprehensive testing tool. It "
#~ "uses a pristine virtual machine to run the tests. To set it up, firstly "
#~ "install the needed dependencies::"
#~ msgstr ""
#~ "這方法的壞處是您是在本機上測試，但是不能保正這會在一個最小環境下運作。例如確保所有要求的套件已經為測試而安装好會有困難。利用 `lp:auto-"
#~ "package-testing`_ 我們有一個更全面的測試工具。它使用一個原始虚擬機器以運行測試。要把它設定好，先安装需要的依賴套件："

#~ msgid "In the `ubiquity tests`_ the upstream test-suite is executed."
#~ msgstr "於`ubiquity 測試`_ 裏上游的測試套件也會被運行。"

#~ msgid ""
#~ "The `auto-package-testing documentation`_ has a lot more valuable "
#~ "information on other testing options."
#~ msgstr "`auto-package-testing 文件`_ 有更多關於其他測試選項的有價值的資訊。"

#~ msgid "So what we do next is run::"
#~ msgstr "所以，我們下一步要做的就是運行："

#~ msgid ""
#~ "If you read :doc:`the Debian Directory Overview<./debian-dir-overview>` "
#~ "before, you might remember, that the homepage for a package is specified in "
#~ "the first part of ``debian/control``, the section which starts with "
#~ "``Source:``."
#~ msgstr ""
#~ "在此之前，如果您閱讀了 doc:`the Debian Directory Overview<./debian-dir-overview>` "
#~ "，您可能還記得軟件包的主頁在 ``debian/control`` 的 ``Source:`` 處指定的。"

#~ msgid ""
#~ "To address the issue in the source package, we first need the source and we "
#~ "can easily get it by running::"
#~ msgstr "為了在源代碼包中解決這個問題，我們首先需要得到源代碼，我們可以通過運行下面的命令很容易地得到它："

#~ msgid ""
#~ "For this specific example it is enough to search the web for ``bumprace`` "
#~ "and find the homepage of it. Be sure it is a live site and not just a "
#~ "software catalogue. http://www.linux-games.com/bumprace/ looks like it is "
#~ "the proper place."
#~ msgstr "對於這個特定的例子，使用搜索引擎找尋到 ``bumprace`` 的主頁就可以了。當然要確定它是這個軟件的主頁而不是一個軟件目錄。"

#~ msgid "and you will see something like this:"
#~ msgstr "您會看到："

#~ msgid "A few additional considerations:"
#~ msgstr "另外幾個注意事項："

#~ msgid ""
#~ "It is important to explain to your fellow developers what exactly you did. "
#~ "If you run::"
#~ msgstr "向您的開發者夥伴解釋究竟你做了什麼非常重要。如果你運行："

#~ msgid ""
#~ "this will start an editor with a boilerplate changelog entry which you just "
#~ "have to fill out. In our case something like ``debian/control: Added "
#~ "project's homepage.`` should do. Then save the file. To double-check this "
#~ "worked out, run::"
#~ msgstr ""
#~ "這將啟動一個編輯器，你只需要填寫一個 changelog 樣板的條目。在我們的這個例子中會是這樣 ``debian/control:Added "
#~ "project's homepage.`` 。然後保存文件。再次查看這個文件，可以運行："

#~ msgid ""
#~ "If you have a reference to a Launchpad bug which is fixed by the issue, add "
#~ "(``LP: #<bug number>``) to the changelog entry line, ie: ``(LP: #123456)``."
#~ msgstr ""
#~ "如果您的提交，有一個相關的 Launchpad 的 bug 號，請添加 (``LP: #<bug number>``) 到 changelog "
#~ "條目，例如： ``(LP: #123456)`` 。"

#~ msgid ""
#~ "If you want to get your fix included in Debian, for a Debian bug the syntax "
#~ "is ``(Closes: #<bug number>)``, ie: ``(Closes: #123456)``."
#~ msgstr ""
#~ "如果您想要讓您的修復放入到 Debian 中，Debian 的語法錯誤是 ``(Closes: #<bug number>)`` ，也就是： "
#~ "``(Closes: #123456)`` 。"

#~ msgid "If you now run::"
#~ msgstr "如果你現在運行："

#~ msgid ""
#~ "and edit ``debian/control`` to add ``Homepage: http://www.linux-"
#~ "games.com/bumprace/``. At the end of the first section should be a good "
#~ "place for it. Once you have done this, save the file."
#~ msgstr ""
#~ "編輯 ``debian/control`` ，在第一節的最後一行添加 ``Homepage: http://www.linux-"
#~ "games.com/bumprace/``，之後保存文件。"

#~ msgid ""
#~ "The diff is pretty simple to understand. The ``+`` indicates a line which "
#~ "was added. In our cases it was added just before the second section, "
#~ "starting with ``Package``, which indicates a resulting binary package."
#~ msgstr ""
#~ "diff 文件相當容易理解。 ``+`` 號表示添加的一行。在我們這個例子中，添加主頁到了第二節 ``Package`` 的前邊， "
#~ "``Package`` 表示所產生的二進制軟件包。"

#~ msgid "you should see something like this:"
#~ msgstr "你應該看到像這樣的東西："

#~ msgid ""
#~ "If it is a reference to an upstream or Debian bug or a mailing list "
#~ "discussion, mention it as well."
#~ msgstr "如果它相關與一個上游或 Debian 錯誤或郵件列表討論，提及它。"

#~ msgid "Try to wrap your lines at 80 characters."
#~ msgstr "嘗試編輯使得每行80個字符。"

#~ msgid ""
#~ "Try to be specific, not an essay, but enough for somebody (who did not "
#~ "deeply look into the issue) to understand."
#~ msgstr "這不是寫一篇短文，足夠明確讓人理解就可以（沒有誰深入研究這個問題）。"

#~ msgid "Mention how you fixed the issue and where."
#~ msgstr "提提您是如何以及在哪里修復它的。"

#~ msgid ""
#~ "It makes to get fix included as Upstream as possible. Doing that you can "
#~ "guarantee that everybody can take the Upstream source as-is and don't need "
#~ "to have local modifications to fix it."
#~ msgstr "這盡可能使上游得到修復。這樣做，您能保證每個人都可以採取上游源而不需要有本地的修改來解決它。"

#~ msgid "Getting the fix included"
#~ msgstr "提交修復"

#~ msgid ""
#~ "As we verified, the problem is now solved, so the next step is sharing our "
#~ "solution with the world."
#~ msgstr "正如我們核實的，這個問題現在已經解決了，所以下一步就是與世界分享我們的解決方案。"

#~ msgid ""
#~ "In step one we build the source package from the branch, then build it by "
#~ "using ``pbuilder``, then inspect the resulting package to check if the "
#~ "Homepage field was added properly."
#~ msgstr "第一個步驟，我們從分支編譯源代碼包，然後通過使用 ``pbuilder`` 構建它，再查生成的包看看是否正確添加了包的主頁字段。"

#~ msgid ""
#~ "To test the fix, you need to :doc:`have your development environment set "
#~ "up<./getting-set-up>`, then to build the package, install it and verify the "
#~ "problem is solved. In our case this would be::"
#~ msgstr ""
#~ "要測試修復，您需要 doc:`have your development environment set up<./getting-set-up>` "
#~ "，然後構建包，安裝它驗證問題是否解決。在我們的這個例子中："

#~ msgid ""
#~ "If the problem is just in Ubuntu, you might want to consider :doc:`Seeking "
#~ "Review and Sponsorship<./udd-sponsorship>` to get the fix included."
#~ msgstr ""
#~ "如果問題僅僅是在Ubuntu，你可能要考慮 doc:`Seeking Review and Sponsorship<./udd-"
#~ "sponsorship>` 來釋出修復。"

#~ msgid "To submit the patch to Debian, simply run::"
#~ msgstr "要提交補丁到 Debian，只需運行："

#~ msgid ""
#~ "In our case we established that we have a problem with the packaging, both "
#~ "in Ubuntu and Debian. As Ubuntu is based on Debian, we will send the fix to "
#~ "Debian. Once it is included there, it will be picked up by Ubuntu "
#~ "eventually. The issue in our tutorial is clearly non-critical, so this "
#~ "approach makes sense. If it is important to fix the issue as soon as "
#~ "possible, you will need to send the solution to multiple bug trackers. "
#~ "Provided the issue affects all parties in question."
#~ msgstr ""
#~ "在我們的例子中，我們我们确定我们有一个问题，打包給 Ubuntu 和 Debian。由於 Ubuntu 是基於 Debian 的，我們將修復發送給 "
#~ "Debian 使用。一旦它被包括在其中，最終 Ubuntu "
#~ "會啓用它。我們的教程中解決的是個非關鍵的問題，這種做法是有道理的(簡明地說明問題)。如果某個問題需要盡快解決，您將需要發送解決方案到多個 bug "
#~ "跟踪系統。假如問題會影響所有各方。"

#~ msgid ""
#~ "Don't worry though, the `Ubuntu development release wiki page "
#~ "<https://wiki.ubuntu.com/UsingDevelopmentReleases>`_ shows a variety of ways "
#~ "to safely use the development release."
#~ msgstr ""
#~ "別擔心，Ubuntu 開發版本的 wiki <https://wiki.ubuntu.com/UsingDevelopmentReleases>`_ "
#~ "顯示各種各樣的方式安全地使用開發版本。"

#~ msgid ""
#~ "``bzr-builddeb`` (and ``bzr``, a dependency) -- distributed version control "
#~ "with Bazaar, a new way of working with packages for Ubuntu that will make it "
#~ "easy for many developers to collaborate and work on the same code while "
#~ "keeping it trivial to merge each other's work."
#~ msgstr ""
#~ "``bzr-builddeb`` （和 ``bzr`` ，一个依赖）—— Bazaar 分佈式版本控制 ，一種新的 Ubuntu "
#~ "的軟件包开发方式，這將使很多開發人員在相同的代碼上協作和工作，同時保持它的细微差别，很容易地合併彼此的成果。"

#~ msgid ""
#~ "GPG stands for `GNU Privacy Guard`_ and it implements the OpenPGP standard "
#~ "which allows you to sign and encrypt messages and files. This is useful for "
#~ "a number of purposes. In our case it is important that you can sign files "
#~ "with your key so they can be identified as something that you worked on. If "
#~ "you upload a source package to Launchpad, it will only accept the package if "
#~ "it can absolutely determine who uploaded the package."
#~ msgstr ""
#~ "GPG代表 `GNU Privacy Guard`_ ，它是 OpenPGP "
#~ "標準的實現，它允許您進行簽名和加密消息和文件。這对很多事情都有用。在我們的情況下，重要的是你可以用你的鑰匙簽署文件。这样文件就可以被确认是您的工作。如果您"
#~ "要上傳一個源碼包到 Launchpad，它將只接受那些可以确定是誰上传的包。"

#~ msgid ""
#~ "There are a number of tools that will make your life as an Ubuntu developer "
#~ "much easier.  You will encounter these tools later in this guide.  To "
#~ "install most of the tools you will need run this command::"
#~ msgstr "有許多開發工具可以使你的 Ubuntu 開發者生活更輕鬆。本指南中，你會遇到這些工具。要安裝的大部分工具，你需要運行這個命令："

#~ msgid ""
#~ "Note: Since Ubuntu 11.10 \"Oneiric Ocelot\" (or if you have Backports "
#~ "enabled on a currently supported release), the following command will "
#~ "install the above and other tools which are quite common in Ubuntu "
#~ "development::"
#~ msgstr ""
#~ "注意：自從 Ubuntu 11.10 \"Oneiric Ocelot\" （或者如果您在 backports "
#~ "中啟用當前支持的版本），下面的命令將安裝上述和其他工具，這些工具在在 Ubuntu 開發中很常見。"

#~ msgid ""
#~ "``gnupg`` -- `GNU Privacy Guard`_ contains tools you will need to create a "
#~ "cryptographic key with which you will sign files you want to upload to "
#~ "Launchpad."
#~ msgstr ""
#~ "``gnupg`` -- `GNU Privacy Guard`_ 包含工具，你需要創建一個加密用的密鑰，你將用它簽署要上傳到 Launchpad "
#~ "的文件。"

#~ msgid ""
#~ "This will send your key to one keyserver, but a network of keyservers will "
#~ "automatically sync the key between themselves. Once this syncing is "
#~ "complete, your signed public key will be ready to verify your contributions "
#~ "around the world."
#~ msgstr ""
#~ "這將發送您的密鑰到一個密鑰服務器，但它們之間的網絡密鑰服務器會自動同步密鑰。一旦此同步完成後，您簽名的公鑰已準備好在世界範圍上驗證您的貢獻。"

#~ msgid ""
#~ "where <release> is for example `natty`, `maverick`, `lucid` or in the case "
#~ "of Debian maybe `sid`. This will take a while as it will download all the "
#~ "necessary packages for a \"minimal installation\". These will be cached "
#~ "though."
#~ msgstr ""
#~ "其中 <release> 如 `natty`, `maverick`, `lucid` 或其他情況如 Debian "
#~ "`sid`。這將需要一段時間，因為它會下載一個“最小化安裝”的所有必要的軟件包。這些（安裝）會有緩存。"

#~ msgid "Configuring Bash to work with Bazaar"
#~ msgstr "配置 Bash 與 bazaar 工作"

#~ msgid "Configuring Bazaar to work with Launchpad"
#~ msgstr "配置 bazaar 於 LaunchPad 工作"

#~ msgid ""
#~ "If you don't already have a Launchpad account, you can easily `create one`_. "
#~ "If you have a Launchpad account but cannot remember your Launchpad id, you "
#~ "can find this out by going to https://launchpad.net/~ and looking for the "
#~ "part after the `~` in the URL."
#~ msgstr ""
#~ "如果您還沒有一個啟動帳戶，您可以很容易 `create one`_ 。如果您有一個 Launchpad 但是忘記了您的 ID ，您可以看一下 "
#~ "https://launchpad.net/~ ，您的 ID 就在 URL 連接的～後邊。"

#~ msgid ""
#~ "Launchpad encrypts the email, using your public key, so that it can be sure "
#~ "that the key is yours. If you are using Thunderbird, the default Ubuntu "
#~ "email client, you can install the `Enigmail plugin "
#~ "<https://apps.ubuntu.com/cat/applications/enigmail/>`_ to easily decrypt the "
#~ "message. If your email software does not support OpenPGP encryption, copy "
#~ "the encrypted email's contents, type ``gpg`` in your terminal, then paste "
#~ "the email contents into your terminal window."
#~ msgstr ""
#~ "Launchpad 使用您的公鑰加密了電子郵件,因此它可以肯定公鑰是您的。如果您正在使用Thunderbird，Ubuntu "
#~ "默認的電子郵件客戶端，你可以安裝 `Enigmail plugin "
#~ "<https://apps.ubuntu.com/cat/applications/enigmail/>`_ 來方便的（用您的密鑰）解密信息。"

#~ msgid ""
#~ "`The new account help page "
#~ "<https://help.launchpad.net/YourAccount/NewAccount>`_ on Launchpad has more "
#~ "information about the process and additional settings you can change."
#~ msgstr ""
#~ "Launchpad 上的 `新帳戶幫助頁面 <https://help.launchpad.net/YourAccount/NewAccount>`_  "
#~ "有更多信息關於此過程和您可以改變的額外設置。"

#~ msgid ""
#~ "In ``debian/tests/control`` you specify what to expect from the testbed. So "
#~ "for example you list all the required packages for the tests, if the testbed "
#~ "gets broken during the build or if ``root`` permissions are required. The "
#~ "`DEP 8 specification`_ lists all available options."
#~ msgstr ""
#~ "在 ``debian/tests/control`` "
#~ "裏您指定從測試平臺裏預計甚麼。例如您列明測試要求的所有套件，測試平臺會不會在建構中被破壞或需不需要使用 ``root`` 權限。`DEP 8 規格`_ "
#~ "列出所有能提供的選擇。"

#~ msgid ""
#~ "The test script can be easily executed on its own, but if you want to make "
#~ "sure that the testbed is properly set up, you might want to use ``adt-run`` "
#~ "from the ``autopkgtest`` package to execute the test. The easiest way to do "
#~ "this is to run this command in the source tree::"
#~ msgstr ""
#~ "測試腳本可以很容易執行自己，但如果您想確保正確設置了測試平台，您可能要使用 ``adt-run`` ``autopkgtest`` "
#~ "包來執行測試。做到這一點最簡單的方法是在源代碼樹來運行這個命令："

#~ msgid ""
#~ "The `libxml2 tests`_ are very similar. They also run a test-build of a "
#~ "simple piece of C code and execute it."
#~ msgstr "`libxml2 測試`_ 与之非常相似。它們也會運行一片简單 C 碼的建構測試並運行它。"

#~ msgid ""
#~ "The `gtk+3.0 tests`_ also do a compile/link/run check in the \"build\" test. "
#~ "There is an additional \"python3-gi\" test which verifies that the GTK "
#~ "library can also be used through introspection."
#~ msgstr ""
#~ "`gtk+3.0 測試`_ 也會在 \"build\" 測試裏進行一個建構/連接/運行檢查。那裏也有一個额外的 \"python3-gi\" 測試来確應 "
#~ "GTK 庫可以經内部使用。"

#~ msgid ""
#~ "This would use the source package in ``/tmp/glib2.0-2.35.7/`` and run the "
#~ "tests from this tree against the package ``glib2.0`` from the archive. The "
#~ "option ``-S`` also supports schemes for bzr, git, and apt sources. If you "
#~ "only specify a source with ``-S`` but do not specify a package name, this "
#~ "will instead build the branch and install the binaries from that build; this "
#~ "is useful if you want to run tests on a newer version than the one packaged "
#~ "in Ubuntu, or the package is not in Ubuntu at all. If use the ``-k`` flag "
#~ "you can log into the virtual machine after the tests were run. This makes it "
#~ "very easy to debug issues."
#~ msgstr ""
#~ "這會使用 ``/tmp/glib2.0-2.35.7`` 中的原始碼套件運行，而不是對檔案庫裏的 ``glib2.0`` 測試。選項 ``-S`` "
#~ "會同時支持 bzr, git 和 apt 原始碼的計劃。如果您只標明原始碼以 ``-S`` "
#~ "但没有標明套件名稱，這會另外建構分支並從那構建和安装程式；如果您想给 Ubuntu 更新的套件，或那套件不在 Ubuntu 裏，這會較為有用。如果使用 "
#~ "``-k`` 選項您可以在測試運行後登入虚擬機器。這讓解臭蟲問题非常简單。"

#~ msgid ""
#~ "The `gvfs tests`_ have comprehensive testing of their functionality and are "
#~ "very interesting because they emulate usage of CDs, Samba, DAV and other "
#~ "bits."
#~ msgstr "`gvfs 測試`_ 全面測試它們的功能，非常有趣，因為它們虚擬了镭射光碟，Samba，DAV和其它部分。"

#~ msgid ""
#~ "Packages which have ``autopkgtest`` enabled will have their tests run "
#~ "whenever they get uploaded or any of their reverse-dependencies change. The "
#~ "output of `automatically run autopkgtest tests`_ can be viewed on the web "
#~ "and is regularly updated."
#~ msgstr ""
#~ "開啓 ``自動打包測試`` 的套件，每當它們被上傳或它們的反向依賴套件改變時，都可以運行測試。`自動運行autopkgtest測試`_ "
#~ "的結果可以在網上瀏覽和會定時更新。"

#~ msgid ""
#~ "The Ubuntu Engineering team put together a `list of required test-cases`_, "
#~ "where packages which need tests are put into different categories. Here you "
#~ "can find examples of these tests and easily assign them to yourself."
#~ msgstr ""
#~ "Ubuntu工程隊伍建構了一個 `需要測試的列表`_ ，在那裏需要測試的套件會被放進不同類别。在這裏您可以找到這些測試的例子並指定它們給您。"

#~ msgid ""
#~ "write the ``debian/tests/control`` based on the `DEP 8 Specification`_,"
#~ msgstr "基於 `DEP 8 規格`_ 下寫出 ``debian/tests/control`` ，"