3
3
# This file is distributed under the same license as the ubuntu-packaging-guide package.
4
4
# FIRST AUTHOR <EMAIL@ADDRESS>, 2012.
5
5
# Jose Luis Tirado <joseluis.tirado@gmail.com>, 2012.
6
# Francisco Molinero <paco@byasl.com>, 2012.
8
10
"Project-Id-Version: ubuntu-packaging-guide\n"
9
11
"Report-Msgid-Bugs-To: FULL NAME <EMAIL@ADDRESS>\n"
10
"POT-Creation-Date: 2012-05-22 12:36+0000\n"
11
"PO-Revision-Date: 2012-10-18 22:52+0000\n"
12
"Last-Translator: Jose Luis Tirado <Unknown>\n"
13
"Language-Team: Spanish <es@li.org>\n"
12
"POT-Creation-Date: 2012-10-19 14:57+0000\n"
13
"PO-Revision-Date: 2012-10-19 23:21+0000\n"
14
"Last-Translator: Paco Molinero <paco@byasl.com>\n"
15
"Language-Team: Español; Castellano <>\n"
14
16
"MIME-Version: 1.0\n"
15
17
"Content-Type: text/plain; charset=UTF-8\n"
16
18
"Content-Transfer-Encoding: 8bit\n"
17
"X-Launchpad-Export-Date: 2012-10-19 05:58+0000\n"
19
"X-Launchpad-Export-Date: 2012-10-20 05:20+0000\n"
18
20
"X-Generator: Launchpad (build 16165)\n"
23
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:3
24
msgid "autopkgtest: Automatic testing for packages"
25
msgstr "autopkgtest: pruebas automáticas para paquetes"
27
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:5
29
"The `DEP 8 specification`_ defines how automatic testing can very easily be "
30
"integrated into packages. To integrate a test into a package, all you need "
34
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:9
35
msgid "add the following to the Source section in ``debian/control``::"
38
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:13
40
"add a file called ``debian/tests/control`` which specifies the requirements "
44
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:15
45
msgid "add the tests in ``debian/tests/``."
48
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:19
49
msgid "Testbed requirements"
52
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:21
54
"In ``debian/tests/control`` you specify what to expect from the testbed. So "
55
"for example you list all the required packages for the tests, if the testbed "
56
"gets broken during the build or if ``root`` permissions are required. The "
57
"`DEP 8 specification`_ lists all available options."
60
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:26
62
"Below we are having a look at the ``glib2.0`` source package. In a very "
63
"simple case the file would look like this::"
66
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:32
68
"For the test in ``debian/tests/build`` this would ensure that the packages "
69
"``libglib2.0-dev`` and ``build-essential`` are installed."
72
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:35
74
"You can use ``@`` in the ``Depends`` line to indicate that you want all the "
75
"packages installed which are built by the source package in question."
78
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:41
79
msgid "The actual tests"
82
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:43
83
msgid "The accompanying test for the example above might be:"
86
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:75
88
"Here a very simple piece of C code is written to a temporary directory. Then "
89
"this is compiled with system libraries (using flags and library paths as "
90
"provided by `pkg-config`). Then the compiled binary, which just exercises "
91
"some parts of core glib functionality, is run."
94
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:80
96
"While this test is very small and basic, it tests quite a number of core "
97
"components on a system. This may help to uncover critical issues early on."
100
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:84
101
msgid "Executing the test"
104
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:86
106
"The test script can be easily executed on its own, but if you want to make "
107
"sure that the testbed is properly set up, you might want to use ``adt-run`` "
108
"from the ``autopkgtest`` package to execute the test. Simply run this "
109
"command in the source tree::"
112
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:95
113
msgid "Further examples"
114
msgstr "Más ejemplos"
116
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:97
118
"This list is not comprehensive, but might help you get a better idea of how "
119
"automated tests are implemented and used in Ubuntu."
122
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:100
124
"The `libxml2 tests`_ are very similar. They also run a test-build of a "
125
"simple piece of C code and execute it."
128
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:102
130
"The `gtk+3.0 tests`_ also do a compile/link/run check in the \"build\" test. "
131
"There is an additional \"python3-gi\" test which verifies that the GTK "
132
"library can also be used through introspection."
135
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:105
136
msgid "In the `ubiquity tests`_ the upstream test-suite is executed."
139
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:106
141
"The `gvfs tests`_ have comprehensive testing of their functionality and are "
142
"very interesting because they emulate usage of CDs, Samba, DAV and other "
146
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:111
147
msgid "Ubuntu infrastructure"
148
msgstr "Infraestructura de Ubuntu"
150
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:113
152
"Packages which have ``autopkgtest`` enabled will have their tests run "
153
"whenever they get uploaded or any of their reverse-dependencies change. The "
154
"output of `automatically run autopkgtest tests`_ can be viewed on the web "
155
"and is regularly updated."
158
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:118
160
"While Debian does not have an automatic testing infrastructure set up yet, "
161
"they should still be submitted to Debian, as DEP-8 is a Debian specification "
162
"and Debian developers or users can still manually run the tests."
165
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:122
167
"Packages in Debian with a testsuite header will also be automatically added "
168
"when they are synced to Ubuntu."
171
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:126
172
msgid "Getting the test into Ubuntu"
175
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:128
177
"The process of submitting an autopkgtest for a package is largely similar to "
178
":doc:`fixing a bug in Ubuntu<./fixing-a-bug>`. Essentially you simply:"
181
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:131
182
msgid "run ``bzr branch ubuntu:<packagename>``,"
185
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:132
186
msgid "edit ``debian/control`` to enable the tests,"
189
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:133
190
msgid "add the ``debian/tests`` directory,"
193
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:134
195
"write the ``debian/tests/control`` based on the `DEP 8 Specification`_,"
198
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:135
199
msgid "add your test case(s) to ``debian/tests``,"
202
#: ../ubuntu-packaging-guide/auto-pkg-test.rst:136
204
"commit your changes, push them to Launchpad, propose a merge and get it "
205
"reviewed just like any other improvement in a source package."
208
#: ../ubuntu-packaging-guide/backports.rst:3
209
msgid "Backporting software updates"
212
#: ../ubuntu-packaging-guide/backports.rst:5
214
"Sometimes you might want to make new functionality available in a stable "
215
"release which is not connected to a critical bug fix. For these scenarios "
216
"you have two options: either you `upload to a PPA "
217
"<https://help.launchpad.net/Packaging/PPA>`_ or prepare a backport."
220
#: ../ubuntu-packaging-guide/backports.rst:12
221
msgid "Personal Package Archive (PPA)"
224
#: ../ubuntu-packaging-guide/backports.rst:14
226
"Using a PPA has a number of benefits. It is fairly straight-forward, you "
227
"don't need approval of anyone, but the downside of it is that your users "
228
"will have to manually enable it. It is a non-standard software source."
231
#: ../ubuntu-packaging-guide/backports.rst:18
233
"The `PPA documentation on Launchpad`_ is fairly comprehensive and should get "
234
"you up and running in no time."
237
#: ../ubuntu-packaging-guide/backports.rst:25
238
msgid "Official Ubuntu Backports"
241
#: ../ubuntu-packaging-guide/backports.rst:27
243
"The Backports Project is a means to provide new features to users. Because "
244
"of the inherent stability risks in backporting packages, users do not get "
245
"backported packages without some explicit action on their part. This "
246
"generally makes backports an inappropriate avenue for fixing bugs. If a "
247
"package in an Ubuntu release has a bug, it should be fixed either through "
248
"the :doc:`Security Update or the Stable Release Update process<./security-"
249
"and-stable-release-updates>`, as appropriate."
252
#: ../ubuntu-packaging-guide/backports.rst:35
254
"Once you determined you want a package to be backported to a stable release, "
255
"you will need to test-build and test it on the given stable release. "
256
"``pbuilder-dist`` (in the ``ubuntu-dev-tools`` package) is a very handy tool "
260
#: ../ubuntu-packaging-guide/backports.rst:40
262
"To report the backport request and get it processed by the Backporters team, "
263
"you can use the ``requestbackport`` tool (also in the ``ubuntu-dev-tools`` "
264
"package). It will determine the intermediate releases that package needs to "
265
"be backported to, list all reverse-dependencies, and file the backporting "
266
"request. Also will it include a testing checklist in the bug."
21
269
#: ../ubuntu-packaging-guide/chroots.rst:3
22
270
msgid "Using Chroots"
23
271
msgstr "Usar chroots"
1236
1488
"navegador. Localice ahí en enlace «(+) Propose for merging», púlselo para "
1237
1489
"que se revise el cambio por algún desarrollador y se incluya en Ubuntu."
1491
#: ../ubuntu-packaging-guide/fixing-a-bug.rst:208
1493
"Our article about :doc:`seeking sponsorship<./udd-sponsorship>` goes into "
1494
"more detail about getting feedback for your proposed changes."
1497
#: ../ubuntu-packaging-guide/fixing-a-bug.rst:211
1499
"If your branch fixes issues in stable releases or it is a security fix, you "
1500
"might want to have a look at our :doc:`Security and stable release "
1501
"updates<./security-and-stable-release-updates>` article."
1504
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:3
1505
msgid "Tutorial: Fixing a bug in Ubuntu"
1508
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:5
1510
"While the mechanics for :doc:`fixing a bug<./fixing-a-bug>` are the same for "
1511
"every bug, every problem you look at is likely to be different from another. "
1512
"An example of a concrete problem might help to get an idea what to consider "
1516
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:10
1518
"At the time of writing this article this was not fixed yet. When you are "
1519
"reading the article this might actually be fixed. Take this as an example "
1520
"and try to adapt it to the specific problem you are facing."
1523
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:15
1524
msgid "Confirming the problem"
1527
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:17
1529
"Let's say the package ``bumprace`` does not have a homepage in its package "
1530
"description. As a first step you would check if the problem is not solved "
1531
"already. This is easy to check, either take a look at Software Center or "
1535
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:23
1536
msgid "The output should be similar to this::"
1539
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:49
1540
msgid "A counter-example would be ``gedit``, which has a homepage set::"
1543
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:55
1545
"Sometimes you will find that a particular problem you are looking into is "
1546
"already fixed. To avoid wasting efforts and duplicating work it makes sense "
1547
"to first do some detective work."
1550
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:61
1551
msgid "Research bug situation"
1554
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:63
1556
"First we should check if a bug for the problem exists in Ubuntu already. "
1557
"Maybe somebody is working on a fix already, or we can contribute to the "
1558
"solution somehow. For Ubuntu we have a quick look at "
1559
"https://bugs.launchpad.net/ubuntu/+source/bumprace and there is no open bug "
1560
"with our problem there."
1563
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:69
1565
"For Ubuntu the URL ``https://bugs.launchpad.net/ubuntu/+source/<package>`` "
1566
"should always take to the bug page of the source package in question."
1569
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:73
1571
"For Debian, which is the major source for Ubuntu's packages, we have a look "
1572
"at http://bugs.debian.org/src:bumprace and can't find a bug report for our "
1576
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:77
1578
"For Debian the URL ``http://bugs.debian.org/src:<package>`` should always "
1579
"take to the bug page of the source package in question."
1582
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:80
1584
"The problem we are working on is special as it only concerns the packaging-"
1585
"related bits of ``bumprace``. If it was a problem in the source code it "
1586
"would be helpful to also check the Upstream bug tracker. This is "
1587
"unfortunately often different for every package you have a look at, but if "
1588
"you search the web for it, you should in most cases find it pretty easily."
1591
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:88
1592
msgid "Offering help"
1595
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:90
1597
"If you found an open bug and it is not assigned to somebody and you are in a "
1598
"position to fix it, you should comment on it with your solution. Be sure to "
1599
"include as much information as you can: Under which circumstances does the "
1600
"bug occur? How did you fix the problem? Did you test your solution?"
1603
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:95
1605
"If no bug report has been filed, you can file a bug for it. What you might "
1606
"want to bear in mind is: Is the issue so small that just asking for somebody "
1607
"to commit it is good enough? Did you manage to only partially fix the issue "
1608
"and you want to at least share your part of it?"
1611
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:100
1612
msgid "It is great if you can offer help and will surely be appreciated."
1615
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:104
1616
msgid "Fixing the issue"
1619
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:106
1621
"For this specific example it is enough to search the web for ``bumprace`` "
1622
"and find the homepage of it. Be sure it is a live site and not just a "
1623
"software catalogue. http://www.linux-games.com/bumprace/ looks like it is "
1627
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:111
1629
"To address the issue in the source package, we first need the source and we "
1630
"can easily get it by running::"
1633
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:117
1635
"If you read :doc:`the Debian Directory Overview<./debian-dir-overview>` "
1636
"before, you might remember, that the homepage for a package is specified in "
1637
"the first part of ``debian/control``, the section which starts with "
1641
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:121
1642
msgid "So what we do next is run::"
1645
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:125
1647
"and edit ``debian/control`` to add ``Homepage: http://www.linux-"
1648
"games.com/bumprace/``. At the end of the first section should be a good "
1649
"place for it. Once you have done this, save the file."
1652
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:129
1653
msgid "If you now run::"
1656
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:133
1657
msgid "you should see something like this:"
1660
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:149
1662
"The diff is pretty simple to understand. The ``+`` indicates a line which "
1663
"was added. In our cases it was added just before the second section, "
1664
"starting with ``Package``, which indicates a resulting binary package."
1667
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:157
1669
"It is important to explain to your fellow developers what exactly you did. "
1673
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:163
1675
"this will start an editor with a boilerplate changelog entry which you just "
1676
"have to fill out. In our case something like ``debian/control: Added "
1677
"project's homepage.`` should do. Then save the file. To double-check this "
1681
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:170
1682
msgid "and you will see something like this:"
1685
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:189
1686
msgid "A few additional considerations:"
1689
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:191
1691
"If you have a reference to a Launchpad bug which is fixed by the issue, add "
1692
"(``LP: #<bug number>``) to the changelog entry line, ie: ``(LP: #123456)``."
1695
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:193
1697
"If you want to get your fix included in Debian, for a Debian bug the syntax "
1698
"is ``(Closes: #<bug number>)``, ie: ``(Closes: #123456)``."
1701
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:195
1703
"If it is a reference to an upstream or Debian bug or a mailing list "
1704
"discussion, mention it as well."
1707
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:197
1708
msgid "Try to wrap your lines at 80 characters."
1711
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:198
1713
"Try to be specific, not an essay, but enough for somebody (who did not "
1714
"deeply look into the issue) to understand."
1717
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:200
1718
msgid "Mention how you fixed the issue and where."
1721
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:206
1723
"To test the fix, you need to :doc:`have your development environment set "
1724
"up<./getting-set-up>`, then to build the package, install it and verify the "
1725
"problem is solved. In our case this would be::"
1728
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:214
1730
"In step one we build the source package from the branch, then build it by "
1731
"using ``pbuilder``, then inspect the resulting package to check if the "
1732
"Homepage field was added properly."
1735
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:218
1737
"In a lot of cases you will have to actually install the package to make sure "
1738
"it works as expected. Our case is a lot easier. If the build succeeded, you "
1739
"will find the binary packages in ``~/pbuilder/<release>_result``. Install "
1740
"them via ``sudo dpkg -i <package>.deb`` or by double-clicking on them in "
1741
"your file manager."
1744
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:225
1746
"As we verified, the problem is now solved, so the next step is sharing our "
1747
"solution with the world."
1750
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:229
1751
msgid "Getting the fix included"
1754
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:231
1756
"It makes to get fix included as Upstream as possible. Doing that you can "
1757
"guarantee that everybody can take the Upstream source as-is and don't need "
1758
"to have local modifications to fix it."
1761
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:235
1763
"In our case we established that we have a problem with the packaging, both "
1764
"in Ubuntu and Debian. As Ubuntu is based on Debian, we will send the fix to "
1765
"Debian. Once it is included there, it will be picked up by Ubuntu "
1766
"eventually. The issue in our tutorial is clearly non-critical, so this "
1767
"approach makes sense. If it is important to fix the issue as soon as "
1768
"possible, you will need to send the solution to multiple bug trackers. "
1769
"Provided the issue affects all parties in question."
1772
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:243
1773
msgid "To submit the patch to Debian, simply run::"
1776
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:247
1778
"This will take you through a series of steps to make sure the bug ends up in "
1779
"the correct place. Be sure to review the diff again to make sure it does not "
1780
"include random changes you made earlier."
1783
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:251
1785
"Communication is important, so when you add some more description to it to "
1786
"the inclusion request, be friendly, explain it well."
1789
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:254
1791
"If everything went well you should get a mail from Debian's bug tracking "
1792
"system with more information. This might sometimes take a few minutes."
1795
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:257
1797
"If the problem is just in Ubuntu, you might want to consider :doc:`Seeking "
1798
"Review and Sponsorship<./udd-sponsorship>` to get the fix included."
1801
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:263
1802
msgid "Additional considerations"
1805
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:265
1807
"If you find a package and find that there are a couple of trivial things you "
1808
"can fix at the same time, do it. This will speed up review and inclusion."
1811
#: ../ubuntu-packaging-guide/fixing-a-bug-example.rst:268
1813
"If there are multiple big things you want to fix, it might be advisable to "
1814
"send individual patches or merge proposals instead. If there are individual "
1815
"bugs filed for the issues already, this makes it even easier."
1239
1818
#: ../ubuntu-packaging-guide/getting-set-up.rst:3
1240
1819
msgid "Getting Set Up"
1241
1820
msgstr "Fase de preparación"
3394
3902
"mantenedor de Debian o el equipo pertinente de Ubuntu. Si no existe un "
3395
3903
"sistema parches no tenga problemas en añadir Quilt."
3905
#: ../ubuntu-packaging-guide/python-packaging.rst:3
3906
msgid "Packaging Python modules and applications"
3909
#: ../ubuntu-packaging-guide/python-packaging.rst:5
3911
"Our packaging follows Debian’s `Python policy`_. We will use the `python-"
3912
"markdown`_ package as an example, which can be downloaded from `PyPI`_. You "
3913
"can look at its packaging at its `Subversion repository`_."
3916
#: ../ubuntu-packaging-guide/python-packaging.rst:7
3917
msgid "There are two types of Python packages — *modules* and *apps*."
3920
#: ../ubuntu-packaging-guide/python-packaging.rst:9
3922
"At the time of writing, Ubuntu has two incompatible versions of Python — "
3923
"*2.x* and *3.x*. ``/usr/bin/python`` is a symbolic link to a default Python "
3924
"2.x version, and ``/usr/bin/python3`` — to a default Python 3.x version. "
3925
"Python modules should be built against all supported Python versions."
3928
#: ../ubuntu-packaging-guide/python-packaging.rst:11
3930
"If you are going to package a new Python module, you might find the "
3931
"``py2dsc`` tool useful (available in `python-stdeb`_ package)."
3934
#: ../ubuntu-packaging-guide/python-packaging.rst:14
3935
msgid "debian/control"
3938
#: ../ubuntu-packaging-guide/python-packaging.rst:16
3940
"Python 2.x and 3.x versions of the package should be in separate binary "
3941
"packages. Names should have ``python{,3}-modulename`` format (like: "
3942
"``python3-dbus.mainloop.qt``). Here, we will use ``python-markdown`` and "
3943
"``python3-markdown`` for module packages and ``python-markdown-doc`` for the "
3944
"documentation package."
3947
#: ../ubuntu-packaging-guide/python-packaging.rst:18
3948
msgid "Things in ``debian/control`` that are specific for a Python package:"
3951
#: ../ubuntu-packaging-guide/python-packaging.rst:20
3953
"The section of module packages should be ``python``, and ``doc`` for the "
3954
"documentation package. For an application, a single binary package will be "
3958
#: ../ubuntu-packaging-guide/python-packaging.rst:21
3960
"We should add build dependencies on ``python-all (>= 2.6.6-3~)`` and "
3961
"``python3-all (>= 3.1.2-7~)`` to make sure Python helpers are available (see "
3962
"the next section for details)."
3965
#: ../ubuntu-packaging-guide/python-packaging.rst:22
3967
"It’s recommended to add ``X-Python-Version`` and ``X-Python3-Version`` "
3968
"fields — see “`Specifying Supported Versions`_” section of the Policy for "
3969
"details. For example::"
3972
#: ../ubuntu-packaging-guide/python-packaging.rst:27
3974
"If your package works only with Python 2.x or 3.x, build depend only on one "
3975
"``-all`` package and use only one ``-Version`` field."
3978
#: ../ubuntu-packaging-guide/python-packaging.rst:28
3980
"Module packages should have ``{python:Depends}`` and ``{python3:Depends}`` "
3981
"substitution variables (respectively) in their dependency lists."
3984
#: ../ubuntu-packaging-guide/python-packaging.rst:33
3986
"The recommended helpers for python modules are ``dh_python2`` and "
3987
"``dh_python3``. Unfortunately, ``debhelper`` doesn’t yet build Python 3.x "
3988
"packages automatically (see `bug 597105`_ in Debian BTS), so we’ll need to "
3989
"do that manually in override sections (skip this if your package doesn’t "
3990
"support Python 3.x)."
3993
#: ../ubuntu-packaging-guide/python-packaging.rst:35
3994
msgid "Here’s our ``debian/rules`` file (with annotations):"
3997
#: ../ubuntu-packaging-guide/python-packaging.rst:70
3999
"It is also a good practice to run tests during the build, if they are "
4000
"shipped by upstream. Usually tests can be invoked using ``setup.py test`` or "
4001
"``setup.py check``."
4004
#: ../ubuntu-packaging-guide/python-packaging.rst:73
4005
msgid "debian/\\*.install"
4008
#: ../ubuntu-packaging-guide/python-packaging.rst:75
4010
"Python 2.x modules are installed into ``/usr/share/pyshared/`` directory, "
4011
"and symbolic links are created in ``/usr/lib/python2.x/dist-packages/`` for "
4012
"every interpreter version, while Python 3.x ones are all installed into "
4013
"``/usr/lib/python3/dist-packages/``."
4016
#: ../ubuntu-packaging-guide/python-packaging.rst:77
4018
"If your package is an application and has private Python modules, they "
4019
"should be installed in ``/usr/share/module``, or ``/usr/lib/module`` if the "
4020
"modules are architecture-dependent (e.g. extensions) (see “`Programs "
4021
"Shipping Private Modules`_” section of the Policy)."
4024
#: ../ubuntu-packaging-guide/python-packaging.rst:79
4026
"So, our ``python-markdown.install`` file will look like this (we’ll also "
4027
"want to install a ``markdown_py`` executable)::"
4030
#: ../ubuntu-packaging-guide/python-packaging.rst:84
4031
msgid "and ``python3-markdown.install`` will only have one line::"
4034
#: ../ubuntu-packaging-guide/python-packaging.rst:89
4035
msgid "The ``-doc`` package"
4038
#: ../ubuntu-packaging-guide/python-packaging.rst:91
4040
"The tool most commonly used for building Python docs is `Sphinx`_. To add "
4041
"Sphinx documentation to your package (using ``dh_sphinxdoc`` helper), you "
4045
#: ../ubuntu-packaging-guide/python-packaging.rst:93
4047
"Add a build-dependency on ``python-sphinx`` or ``python3-sphinx`` (depending "
4048
"on what Python version do you want to use);"
4051
#: ../ubuntu-packaging-guide/python-packaging.rst:94
4052
msgid "Append ``sphinxdoc`` to the ``dh --with`` line;"
4055
#: ../ubuntu-packaging-guide/python-packaging.rst:95
4057
"Run ``setup.py build_sphinx`` in ``override_dh_auto_build`` (sometimes not "
4061
#: ../ubuntu-packaging-guide/python-packaging.rst:96
4063
"Add ``{sphinxdoc:Depends}`` to the dependency list of your ``-doc`` package;"
4066
#: ../ubuntu-packaging-guide/python-packaging.rst:97
4068
"Add the path of the built docs directory (usually ``build/sphinx/html``) to "
4069
"your ``.docs`` file."
4072
#: ../ubuntu-packaging-guide/python-packaging.rst:99
4074
"In our case, the docs are automatically built in ``build/docs/`` directory "
4075
"when we run ``setup.py build``, so we can simply put this in the ``python-"
4076
"markdown-doc.docs`` file::"
4079
#: ../ubuntu-packaging-guide/python-packaging.rst:103
4081
"Because docs also contain source ``.txt`` files, we’ll also tell "
4082
"``dh_compress`` to not compress them — by adding this to ``debian/rules``:"
4085
#: ../ubuntu-packaging-guide/python-packaging.rst:111
4086
msgid "Checking for packaging mistakes"
4089
#: ../ubuntu-packaging-guide/python-packaging.rst:113
4091
"Along with ``lintian``, there is a special tool for checking Python packages "
4092
"— ``lintian4py``. It is available in the `lintian4python`_ package. For "
4093
"example, these two commands invoke both versions of ``lintian`` and check "
4094
"source and binary packages::"
4097
#: ../ubuntu-packaging-guide/python-packaging.rst:118
4099
"Here, ``-EI`` option is used to enable experimental and informational tags."
4102
#: ../ubuntu-packaging-guide/python-packaging.rst:121
4106
#: ../ubuntu-packaging-guide/python-packaging.rst:123
4107
msgid "The `Python policy`_;"
4110
#: ../ubuntu-packaging-guide/python-packaging.rst:124
4111
msgid "`Python/Packaging`_ article on Debian wiki;"
4114
#: ../ubuntu-packaging-guide/python-packaging.rst:125
4116
"`Python/LibraryStyleGuide`_ and `Python/AppStyleGuide`_ articles on Debian "
4120
#: ../ubuntu-packaging-guide/python-packaging.rst:126
4121
msgid "Debian `python-modules`_ and `python-apps`_ teams."
3397
4124
#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:3
3398
4125
msgid "Security and Stable Release Updates"
3399
4126
msgstr "Actualizaciones de seguridad y de versiones estables"
3643
4370
#: ../ubuntu-packaging-guide/security-and-stable-release-updates.rst:138
3644
4371
msgid "See the `Stable Release Updates wiki page`_ for more information."
3646
"Véase la `página wiki actualizaciones de versiones estables`_ para más "
4372
msgstr "Véase la Stable Release Updates wiki page`_ para más información."
3649
4374
#: ../ubuntu-packaging-guide/traditional-packaging.rst:3
3650
4375
msgid "Traditional Packaging"
3651
4376
msgstr "Empaquetado tradicional"
3653
4378
#: ../ubuntu-packaging-guide/traditional-packaging.rst:5
3654
msgid "FIXME describe traditional packaging here"
3655
msgstr "FIXME describir aquí el empaquetado tradicional"
4380
"The majority of this guide deals with :doc:`Ubuntu Distributed Development "
4381
"<./udd-intro>` (UDD) which utilizes the distributed version control system "
4382
"(DVCS) Bazaar for :ref:`retrieving package sources <branching>` and "
4383
"submitting fixes with :ref:`merge proposals. <merge-proposal>` This article "
4384
"will discuss what we will call traditional packaging methods for lack of a "
4385
"better word. Before Bazaar was adopted for Ubuntu development, these were "
4386
"the typical methods for contributing to Ubuntu."
4389
#: ../ubuntu-packaging-guide/traditional-packaging.rst:13
4391
"In some cases, you may need to use these tools instead of UDD. So it is good "
4392
"to be familiar with them. Before you begin, you should already have read the "
4393
"article :doc:`Getting Set Up. <./getting-set-up>`"
4396
#: ../ubuntu-packaging-guide/traditional-packaging.rst:18
3657
4397
#: ../ubuntu-packaging-guide/udd-getting-the-source.rst:3
3658
4398
msgid "Getting the Source"
3659
4399
msgstr "Obtener el código fuente"
4401
#: ../ubuntu-packaging-guide/traditional-packaging.rst:20
4402
msgid "In order to get a source package, you can simply run::"
4405
#: ../ubuntu-packaging-guide/traditional-packaging.rst:24
4407
"This method has some draw backs though. It downloads the version of the "
4408
"source that is available on **your system.** You are likely running the "
4409
"current stable release, but you want to contribute your change against the "
4410
"package in the development release. Luckily, the ``ubuntu-dev-tools`` "
4411
"package provides a helper script::"
4414
#: ../ubuntu-packaging-guide/traditional-packaging.rst:32
4416
"By default, the latest version in the development release will be "
4417
"downloaded. You can also specify a version or Ubuntu release like::"
4420
#: ../ubuntu-packaging-guide/traditional-packaging.rst:37
4421
msgid "to pull the source from the ``precise`` release, or::"
4424
#: ../ubuntu-packaging-guide/traditional-packaging.rst:41
4426
"to download version ``1.0-1ubuntu1`` of the package. For more information on "
4427
"the command, see ``man pull-lp-source``."
4430
#: ../ubuntu-packaging-guide/traditional-packaging.rst:44
4432
"For our example, let's pretend we got a bug report saying that \"colour\" in "
4433
"the description of ``xicc`` should be \"color,\" and we want to fix it. "
4434
"*(Note: This is just an example of something to change and not really a "
4435
"bug.)* To get the source, run::"
4438
#: ../ubuntu-packaging-guide/traditional-packaging.rst:52
4439
msgid "Creating a Debdiff"
4442
#: ../ubuntu-packaging-guide/traditional-packaging.rst:54
4444
"A ``debdiff`` shows the difference between two Debian packages. The name of "
4445
"the command used to generate one is also ``debdiff``. It is part of the "
4446
"``devscripts`` package. See ``man debdiff`` for all the details. To compare "
4447
"two source packages, pass the two ``dsc`` files as arguments::"
4450
#: ../ubuntu-packaging-guide/traditional-packaging.rst:61
4452
"To continue with our example, let's edit the ``debian/control`` and \"fix\" "
4456
#: ../ubuntu-packaging-guide/traditional-packaging.rst:67
4458
"We also must adhere to the `Debian Maintainer Field Spec "
4459
"<https://wiki.ubuntu.com/DebianMaintainerField>`_ and edit "
4460
"``debian/control`` to replace::"
4463
#: ../ubuntu-packaging-guide/traditional-packaging.rst:73
4467
#: ../ubuntu-packaging-guide/traditional-packaging.rst:78
4469
"You can use the ``update-maintainer`` tool (in the ``ubuntu-dev-tools`` "
4470
"package) to do that."
4473
#: ../ubuntu-packaging-guide/traditional-packaging.rst:81
4475
"Remember to document your changes in ``debian/changelog`` using ``dch -i`` "
4476
"and then we can generate a new source package::"
4479
#: ../ubuntu-packaging-guide/traditional-packaging.rst:86
4480
msgid "Now we can examine our changes using ``debdiff``::"
4483
#: ../ubuntu-packaging-guide/traditional-packaging.rst:91
4485
"To create a patch file that you can send to others or attach to a bug report "
4486
"for sponsorship, run::"
4489
#: ../ubuntu-packaging-guide/traditional-packaging.rst:98
4490
msgid "Applying a Debdiff"
4493
#: ../ubuntu-packaging-guide/traditional-packaging.rst:100
4495
"In order to apply a debdiff, first make sure you have the source code of the "
4496
"version that it was created against::"
4499
#: ../ubuntu-packaging-guide/traditional-packaging.rst:105
4501
"Then in a terminal, change the to the directory where the source was "
4505
#: ../ubuntu-packaging-guide/traditional-packaging.rst:110
4506
msgid "A debdiff is just like a normal patch file. Apply it as usual with::"
3661
4509
#: ../ubuntu-packaging-guide/udd-getting-the-source.rst:6
3662
4510
msgid "Source package URLs"
3663
4511
msgstr "URLs de los paquetes fuente"
4533
5363
"versión 2.5 beta 5 o superior y «bzr-builddeb» version 2.8.1 o superior. Con "
4534
5364
"versiones más antiguas, use en su lugar la orden «bzr merge-package»."
4536
#: ../ubuntu-packaging-guide/udd-newpackage.rst:3
4537
msgid "Building a new package"
4538
msgstr "Construir un paquete nuevo"
4540
#: ../ubuntu-packaging-guide/udd-newpackage.rst:5
4542
"Let's say I have an upstream project that is not yet available for Ubuntu. "
4543
"I want to create a package from this project and make it available as a PPA_ "
4544
"so that other people can more easily use the code. This also makes a good "
4545
"first step in contributing your package to universe_."
4547
"Digamos que tengo un proyecto de aguas arriba que todavía no está disponible "
4548
"para Ubuntu. Quiero crear un paquete para este proyecto y hacerlo disponible "
4549
"como un PPA de forma que otra gente pueda usar el código más fácilmente. "
4550
"Este es también un buen primer paso para contribuir el paquete a universe_."
4552
#: ../ubuntu-packaging-guide/udd-newpackage.rst:12
4553
msgid "Example package"
4554
msgstr "Paquete de ejemplo"
4556
#: ../ubuntu-packaging-guide/udd-newpackage.rst:14
4558
"I started with a Python library called `flufl.enum`_, which is a fairly "
4559
"typical setuptools-based Python package. Fortunately, it's also maintained "
4560
"in Launchpad using Bazaar, so that makes bootstrapping much easier."
4562
"Comencé con una biblioteca de Python llamada `flufl.enum`_, que es un "
4563
"paquete de herramientas de configuración basadas en Python bastante típico. "
4564
"Afortunadamente, también se mantiene en Launchpad usando Bazaar, lo que el "
4565
"arranque mucho más sencillo."
4567
#: ../ubuntu-packaging-guide/udd-newpackage.rst:18
4569
"Because we want to package the trunk branch, getting started is pretty "
4572
"Puesto que queremos empaquetar la rama troncal, comenzar es bastante "
4575
#: ../ubuntu-packaging-guide/udd-newpackage.rst:31
4576
msgid "Bootstrapping"
4579
#: ../ubuntu-packaging-guide/udd-newpackage.rst:33
4581
"You need to create the initial ``debian`` directory, as well as the "
4582
"necessary files inside the ``debian`` directory. Currently, there are many "
4583
"ways to set up this directory, but hopefully there will be `some "
4584
"convergence`_ in the methods, especially if you're building standard Python "
4585
"setuptools-based libraries and applications."
4587
"Necesita crear el directorio «debian» inicial, así como los archivos "
4588
"necesarios dentro del mismo. Actualmente hay muchas maneras de configurar "
4589
"este directorio, pero por suerte se llegará a `alguna convergencia`_ de los "
4590
"métodos, especialmente si está compilando bibliotecas y aplicaciones "
4591
"estándar de Python basadas en herramientas de configuración."
4593
#: ../ubuntu-packaging-guide/udd-newpackage.rst:43
4594
msgid "The bzr-builddeb way"
4595
msgstr "La manera de bzr-builddeb"
4597
#: ../ubuntu-packaging-guide/udd-newpackage.rst:45
4599
"You could use the ``dh_make`` command to get things going, or similarly the "
4600
"``bzr dh-make``. The latter might provide some benefits, and can be run "
4601
"like so from inside your branch::"
4603
"Puede usar la orden «dh_make» para que funcione o de forma parecida «bzr dh-"
4604
"make». La última forma podría tener algunas ventajas y la podemos ejecutar "
4605
"así desde dentro de su rama::"
4607
#: ../ubuntu-packaging-guide/udd-newpackage.rst:52
4609
"If you don't have a URL to download a tarball from, you'll need to create "
4610
"the tarball locally first. Use ``bzr dh-make --help`` for details on this "
4613
"Si no dispone de una URL de la que descargar el archivo tar, necesitará "
4614
"crearlo localmente antes. Use «bzr dh-make --help» para detalles sobre esta "
4617
#: ../ubuntu-packaging-guide/udd-newpackage.rst:55
4619
"After you've created the ``debian`` directory template, be sure to ``bzr "
4620
"rm`` any ``debian`` files you don't need (e.g. the ``*.ex`` files), and edit "
4621
"files such as ``debian/control``, ``debian/watch``, ``debian/copyright`` and "
4622
"``debian/changelog``. The following section may give you some hints about "
4625
"Después de que haya creado la plantilla del directorio «debian», asegúrese "
4626
"de hacer «bzr rm» de cualquier archivo en «debian» que no necesite (por "
4627
"ejemplo, los archivos «*.ex») y edite los archivos como «debian/control», "
4628
"«debian/watch», «debian/copyright» y «debian/changelog». La siguiente "
4629
"sección le puede ofrecer algunas ayudas para hacerlo."
4631
#: ../ubuntu-packaging-guide/udd-newpackage.rst:63
4632
msgid "The stdeb way"
4633
msgstr "La manera de stdeb"
4635
#: ../ubuntu-packaging-guide/udd-newpackage.rst:65
4637
"Another way for creating the initial ``debian`` directory for Python "
4638
"setuptools-based packages, is to use the stdeb_ package. The full "
4639
"documentation for this package is available on the `upstream home`_, but you "
4640
"won't need all of the commands. stdeb has a command that is *exactly* what "
4641
"we're looking for!"
4643
"Otra forma de crear el directorio inicial «debian» para paquetes basados en "
4644
"herramientas de configuración de Python, es usar el paquete stdeb_. Existe "
4645
"documentación completa sobre este paquete en `upstream home`_, pero no le "
4646
"harán falta todas las órdenes. ¡stdeb tiene una orden que es *exactamente* "
4647
"lo que está buscando!"
4649
#: ../ubuntu-packaging-guide/udd-newpackage.rst:71
4651
"In either case, start by putting this in your ``~/.pydistutils.cfg`` file::"
4653
"En ambos casos, comience por poner esto en su archivo «~/.pydistutils.cfg»::"
4655
#: ../ubuntu-packaging-guide/udd-newpackage.rst:78
4656
msgid "Modern stdeb"
4657
msgstr "stdeb moderno"
4659
#: ../ubuntu-packaging-guide/udd-newpackage.rst:80
4660
msgid "Here's how easy it is::"
4661
msgstr "Es así de fácil::"
4663
#: ../ubuntu-packaging-guide/udd-newpackage.rst:86
4665
"We also need a ``debian/copyright`` file. Normally, we'd use ``dh_make -c`` "
4666
"for that but again, that doesn't play nicely with UDD. ``dh_make`` expects "
4667
"a particular file system layout that we don't have. No matter, we'll add "
4668
"the copyright file manually::"
4670
"También se necesita un archivo «debian/copyright». Normalmente se usaría "
4671
"«dh_make -c» de nuevo, pero eso no va bien con UDD. «dh_make» espera una "
4672
"disposición del sistema de archivos particular que no tenemos. No improta, "
4673
"porque añadiremos el archivo copyright manualmente::"
4675
#: ../ubuntu-packaging-guide/udd-newpackage.rst:98
4676
msgid "stdeb <= 0.5.1"
4677
msgstr "stdeb <= 0.5.1"
4679
#: ../ubuntu-packaging-guide/udd-newpackage.rst:100
4681
"If you have an older version of stdeb, use this command to create the basic "
4682
"``debian/`` directory layout::"
4684
"Si tiene una versión más antigua de stdeb, use esta orden para crear la "
4685
"distribución de directorios «debian/» básica."
4687
#: ../ubuntu-packaging-guide/udd-newpackage.rst:105
4689
"This command leaves you with a ``deb_dist`` directory containing a "
4690
"``flufl.enum_3.0.1`` directory. Inside that is your ``debian/`` directory. "
4691
"Because we're using UDD we don't care about anything else that ``sdist_dsc`` "
4692
"produces, so we can shuffle things around and remove the cruft."
4694
"Esta orden le deja con un directorio «deb_dist» que contiene a su vez un "
4695
"directorio «flufl.enum_3.0.1». Dentro de este último está el directorio "
4696
"«debian». Al usar UDD nos da igual todo lo demás que «sdis_dsc» produce, así "
4697
"que podemos mover las cosas y eliminar lo sobrante."
4699
#: ../ubuntu-packaging-guide/udd-newpackage.rst:110
4701
"$ mv deb_dist/munepy-2.0.1/debian . $ rm -rf deb_dist $ bzr add debian $ bzr "
4702
"commit -m'Add debian directory'"
4704
"$ mv deb_dist/munepy-2.0.1/debian . $ rm -rf deb_dist $ bzr add debian $ bzr "
4705
"commit -m'Add debian directory'"
4707
#: ../ubuntu-packaging-guide/udd-newpackage.rst:117
4711
#: ../ubuntu-packaging-guide/udd-newpackage.rst:119
4713
"pkgme_ is a new tool that makes it easy to Debianize a new package. TBD: "
4714
"describe how to use it."
4716
"pkgme_ es una nueva herramienta que facilita Debianizar un paquete nuevo. "
4717
"TBD: describir cómo usarla."
4719
#: ../ubuntu-packaging-guide/udd-newpackage.rst:124
4720
msgid "debian/control file"
4721
msgstr "Archivo debian/control"
4723
#: ../ubuntu-packaging-guide/udd-newpackage.rst:126
4725
"You probably want to edit the ``debian/control`` file at this point, adding "
4726
"any information that's missing, or fixing incorrect default information. "
4727
"For example, I needed to modify the ``Maintainer`` and ``Description`` "
4728
"fields, and add ``X-Python-Version`` and ``Homepage`` fields."
4730
"A estas alturas probablemente desee editar el archivo «debian/control», "
4731
"añadiendo cualquier información que falte o corrigiendo información "
4732
"predeterminada incorrecta. Por ejemplo, yo necesité modificar los campos "
4733
"«Maintainer» y «Description» y añadir los campos «X-Python-Version» y "
4736
#: ../ubuntu-packaging-guide/udd-newpackage.rst:131
4738
"Now we want to build the source package. The easiest way to do that is with "
4739
"the ``bzr-builddeb`` plugin, however this requires a valid ``debian/watch`` "
4740
"file so that builddeb can find the upstream tarball. This really should "
4741
"match the version of the checkout you've made."
4743
"Ahora queremos compilar el paquete fuente. La forma más sencilla de hacerlo "
4744
"es con el complemento «bzr-builddeb», sin embargo, eso necesita un archivo "
4745
"«debian/watch» válido de forma que builddeb pueda encontrar el archivo tar "
4746
"de aguas arriba. Esto debería realmente coincidir con la versión de la "
4747
"extracción que ha realizado."
4749
#: ../ubuntu-packaging-guide/udd-newpackage.rst:138
4750
msgid "debian/watch file"
4751
msgstr "Archivo debian/watch"
4753
#: ../ubuntu-packaging-guide/udd-newpackage.rst:140
4754
msgid "Here for example is the ``debian/watch`` file I'm using::"
4755
msgstr "Este es un ejemplo del archivo «debian/watch» que estoy usando::"
4757
#: ../ubuntu-packaging-guide/udd-newpackage.rst:145
4759
"If your tarballs live on Launchpad, the ``debian/watch`` file is a little "
4760
"more complicated (see `Question 21146`_ and `Bug 231797`_ for why this is). "
4761
"In that case, use something like::"
4763
"Si sus archivos tar residen en Launchpad, el archivo «debian/watch» es algo "
4764
"más complicado (véase Question 21146`_ y `Bug 231797`_ para saber por qué). "
4765
"En este caso, usamos algo como::"
4767
#: ../ubuntu-packaging-guide/udd-newpackage.rst:152
4768
msgid "So, then it's a matter of...::"
4769
msgstr "Así, entonces es una cuestión de...::"
4771
#: ../ubuntu-packaging-guide/udd-newpackage.rst:159
4772
msgid "Building the source package"
4773
msgstr "Construir el paquete fuente"
4775
#: ../ubuntu-packaging-guide/udd-newpackage.rst:161
4777
"Now we can build the source package and publish the package as we normally "
4778
"would, with ``bzr builddeb -S`` and ``dput``."
4780
"Ahora podemos compilar el paquete fuente y publicarlo como haríamos "
4781
"normalmente, con «bzr builddeb -S» y «dput»."
4783
5366
#: ../ubuntu-packaging-guide/udd-patchsys.rst:3
4784
5367
msgid "Working with Patches"
4785
5368
msgstr "Trabajar con parches"
5616
6219
"``pbuilder-dist`` (or ``pbuilder`` or `sbuild`_)."
5618
6221
"Una vez haya obtenido el paquete fuente, puede construirlo de forma normal "
5619
"con «pbuilder-dist» (o «pbuilder» o «sbuild»_)."
6222
"con «pbuilder-dist» (o «pbuilder» o `sbuild`_)."
6225
#~ "You can also set up pbuilder to pause when it comes across a build failure. "
6226
#~ "Copy C10shell from /usr/share/doc/pbuilder/examples into a directory and use "
6227
#~ "the --hookdir= argument to point to it."
6229
#~ "Puede configurar pbuilder para hacer una pausa cuando encuentre un error en "
6230
#~ "la construcción. Copie C10shell desde /usr/share/doc/pbuilder/examples en un "
6231
#~ "directorio y use el parámetro --hookdir= para apuntar a él."
6234
#~ "$ sudo mkdir oneiric/home/<username> $ sudo cp -r ~/.gnupg ~/.ssh ~/.bazaar "
6235
#~ "oneiric/home/<username>"
6237
#~ "$ sudo mkdir oneiric/home/<nombre_de_usuario> $ sudo cp -r ~/.gnupg ~/.ssh "
6238
#~ "~/.bazaar oneiric/home/<nombre_de_usuario>"
6241
#~ "You might want to copy your GPG/ssh keys and Bazaar configuration into the "
6242
#~ "chroot so you can access and sign packages directly."
6244
#~ "Quizás quiera copiar sus claves GPG/ssh y su configuración de Bazaar dentro "
6245
#~ "del chroot de manera que pueda acceder y firmar paquetes directamente."
6248
#~ "Here is a simplified version of the rules file created by ``dh_make`` (which "
6249
#~ "can be found in the ``dh-make`` package)::"
6251
#~ "Aquí se encuentra una versión simplificada del archivo de reglas («rules») "
6252
#~ "generada por el comando «dh_make» (que es parte del paquete «dh-make»)::"
6255
#~ "(`bd` is an alias for `builddeb`.) You can leave the package unsigned by "
6256
#~ "appending `-- -uc -us` to the command."
6258
#~ "(«bd» es un alias de «builddeb») Se puede dejar el paquete sin firmar "
6259
#~ "añadiendo «--- uc-us» a la orden."
6262
#~ "This only works with bzr-builddeb 2.7.5 and bzr 2.4, for older versions use "
6265
#~ "Esto solo funciona con bzr-builddeb 2.7.5 y bzr 2.4, para versiones "
6266
#~ "anteriores use «debcommit»."
6269
#~ "In order to build the package you can use the `bzr builddeb` command from "
6270
#~ "the `bzr-builddeb` package. You can build a source package with::"
6272
#~ "Para de construir el paquete se puede utilizar la orden «bzr builddeb» del "
6273
#~ "paquete «bzr-builddeb». Se puede construir un paquete fuente con::"
6276
#~ "``pbuilder`` -- a tool to do a reproducible builds of a package in a clean "
6277
#~ "and isolated environment."
6279
#~ "«pbuilder» -- una herramienta para realizar compilaciones reproducibles de "
6280
#~ "una paquete en un entorno limpio y aislado."
6283
#~ "``bzr-builddeb`` (and ``bzr``, a dependency) -- distributed version control "
6284
#~ "with Bazaar, a new way of working with packages for Ubuntu that will make it "
6285
#~ "easy for many developers to collaborate and work on the same code while "
6286
#~ "keeping it trivial to merge each others work."
6288
#~ "«bzr-builddeb» (y «bzr», una dependencia) -- sistema de control de versiones "
6289
#~ "distribuido con Bazaar, una nueva forma de trabajar con paquetes para Ubuntu "
6290
#~ "que facilitará a muchos desarrolladores colaborar y trabajar sobre el mismo "
6291
#~ "código, haciendo que resulte sencillo combinar el trabajo de los demás."
6294
#~ "``apt-cache`` (part of the ``apt`` package) provides even more information "
6295
#~ "about packages on Ubuntu."
6297
#~ "«apt-cache» (parte del paquete «apt») proporciona incluso más información "
6298
#~ "sobre los paquetes en Ubuntu."
6301
#~ "For more information on this process, visit the `<creating an SSH keypair "
6302
#~ "<https://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair>`_ page on "
6305
#~ "Para más información sobre este proceso, visite la página `<crear una pareja "
6306
#~ "de claves SSH <https://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair>` "
6310
#~ "Thousands of source packages, billions of lines of code, hundreds of "
6311
#~ "contributors require a lot of communication and planning to maintain high "
6312
#~ "standards of quality. At the beginning of each release cycle we have the "
6313
#~ "Ubuntu Developer Summit where developers and contributors come together to "
6314
#~ "plan the features of the next releases. Every feature is discussed by its "
6315
#~ "stakeholders and a specification is written that contains detailed "
6316
#~ "information about its assumptions, implementation, the necessary changes in "
6317
#~ "other places, how to test it and so on. This is all done in an open and "
6318
#~ "transparent fashion, so even if you can not attend the event in person, you "
6319
#~ "can participate remotely and listen to a streamcast, chat with attendants "
6320
#~ "and subscribe to changes of specifications, so you are always up to date."
6322
#~ "Miles de los paquetes fuente, miles de millones de líneas de código, cientos "
6323
#~ "de contribuyentes requieren de mucha comunicación y de una planificación "
6324
#~ "para mantener altos estándares de calidad. Al principio de cada ciclo de "
6325
#~ "emisión tiene lugar la «Ubuntu Developer Summit» (cumbre de desarrolladores "
6326
#~ "de Ubuntu) en la que los desarrolladores y contribuyentes se juntan para "
6327
#~ "planificar las características de las próximas versiones. Cada "
6328
#~ "característica es discutida por sus accionistas y se escribe una "
6329
#~ "especificación que contiene información detallada sobre sus supuestos, "
6330
#~ "implementación, cambios necesarios en otras partes, cómo probarla y así "
6331
#~ "sucesivamente. Todo esto se hace de forma abierta y transparente, así que "
6332
#~ "incluso si no puede asistir al evento en persona, puede participar de forma "
6333
#~ "remota y escuchar una transmisión, chalar con los asistentes y suscribirse a "
6334
#~ "cambios en las especificaciones, de forma que siempre esté al día."
6337
#~ "Packaging of KDE programs in Ubuntu is managed by the Kubuntu and MOTU "
6338
#~ "teams. You can contact the Kubuntu team on the `Kubuntu mailing list`_ and "
6339
#~ "``#kubuntu-devel`` Freenode IRC channl. More information about Kubuntu "
6340
#~ "development is on the `Kubuntu wiki page`_."
6342
#~ "El empaquetado de programs de KDE en Ubuntu se gestiona por los equipos de "
6343
#~ "Kubuntu y MOTU. Puede contactar con el equipo de Kubuntu en `Kubuntu mailing "
6344
#~ "list`_ (lista de correo de Kubuntu) y en el canal de IRC de Freenode "
6345
#~ "«#kubuntu-devel». Puede encontrar más información sobre el desarrollo de "
6346
#~ "Kubuntu en la página wiki `Kubuntu wiki page`_."
6348
#~ msgid "To find the SONAME of the library run"
6349
#~ msgstr "Para encontrar el SONAME de una biblioteca ejecute"
6351
#~ msgid "$ readelf -a /usr/lib/libnova-0.12.so.2 | grep SONAME"
6352
#~ msgstr "$ readelf -a /usr/lib/libnova-0.12.so.2 | grep SONAME"
6355
#~ "The ``-nc`` will cause it to finish at the end of the compile without "
6356
#~ "removing the build. Change to the build and run ``dpkg-gensymbols`` for the "
6357
#~ "library package::"
6359
#~ "El parámetro «-nc» hará que finalice al terminar la compilación sin eliminar "
6360
#~ "la construcción. Cambie a la construcción y ejecute «dpkg-gensymbols» para "
6361
#~ "el paquete de biblioteca::"
6364
#~ "Which will create a file named similar to ``dpkg-gensymbolsnY_WWI`` that "
6365
#~ "lists all the symbols. It also lists the current package version. We can "
6366
#~ "remove the packaging version from that listed in the symbols file because "
6367
#~ "new symbols are not generally added by new packaging versions::"
6369
#~ "Lo que creará un archivo con un nombre similar a «dpkg-gensymbolsnY_WWI» que "
6370
#~ "lista todos los símbolos. También lista la versión de paquete actual. "
6371
#~ "Podemos eliminar la versión de empaquetado que se lista en el archivo de "
6372
#~ "símbolos porque generalmente no se añaden nuevos símbolos por versiones más "
6373
#~ "modernas de empaquetado::"
6376
#~ "While there are thousands of packages in the Ubuntu archive, there are still "
6377
#~ "a lot nobody has gotten to yet. If there is an exciting new piece of "
6378
#~ "software that you feel needs wider exposure, maybe you want to try your hand "
6379
#~ "at creating a package for Ubuntu or a PPA. This guide will take you through "
6380
#~ "the steps of packaging new software."
6382
#~ "A pesar de que hay miles de paquetes en el repositorio de Ubuntu, todavía "
6383
#~ "hay muchos que nadie ha conseguido. Si hay una nueva y excitante porción de "
6384
#~ "software que siente que necesita una exposición más amplia, quizá quiera "
6385
#~ "intentar crear un paquete para Ubuntu o un PPA. Esta guía le acompañará a "
6386
#~ "través de los pasos del empaquetado de nuevo software."
6389
#~ "If the compile completes successfully you can install and run the program::"
6391
#~ "Si la compilación finaliza con éxito puede instalar y ejecutar el programa::"
6394
#~ "``bzr-builddeb`` includes a plugin to create a new package from a template. "
6395
#~ "The plugin is a wrapper around the ``dh_make`` command. You should already "
6396
#~ "have these if you installed ``packaging-dev`` Run the command providing the "
6397
#~ "package name, version number, and path to the upstream tarball::"
6399
#~ "«bzr-builddeb» incluye un complemento para crear nuevos paquetes a partir de "
6400
#~ "una plantilla. El complemento es un envoltorio alrededor de la orden "
6401
#~ "«dh_make». Ya debería tenerlos instalados si instaló «packaging-dev». "
6402
#~ "Ejecute la orden indicando el nombre del paquete, número de versión y la "
6403
#~ "ruta al archivo tar de aguas arriba::"
6406
#~ "``control`` contains all the metadata of the package. The first paragraph "
6407
#~ "describes the source package. The second and and following paragraphs "
6408
#~ "describe the binary packages to be built. We will need to add the packages "
6409
#~ "needed to compile the application to ``Build-Depends:``. For ``hello``, make "
6410
#~ "sure that it includes at least::"
6412
#~ "«control» contiene todos los metadatos del paquete. El primer párrafo "
6413
#~ "describe el paquete fuente. El segundo y siguientes describen los paquetes "
6414
#~ "binarios a construir. Necesitaremos añadir los paquetes necesarios para "
6415
#~ "compilar la aplicación a «Build-Depends:». Para «hello», asegúrese de que "
6416
#~ "incluye al menos::"
6419
#~ "``debuild`` is a command to build the package in its current location. The "
6420
#~ "``-us -uc`` tell it there is not need to GPG sign the compile. The result "
6421
#~ "will be placed in ``..``."
6423
#~ "«debuild» es una ornde para compilar el paquete en su ubicación actual. Los "
6424
#~ "parámetros «-us -uc» le indicarán que no es necesario firmar con GPG el "
6425
#~ "compilado. El resultado se dejará en «..»."
6428
#~ "Having checked that the package builds locally you should ensure it builds "
6429
#~ "on a clean system using ``pbuilder``. If you haven't set up ``pbuilder-"
6430
#~ "dist`` yet, :doc:`do so now<./getting-set-up>`::"
6432
#~ "Después de comprobar que el paquete se compila en local debería asegurarse "
6433
#~ "de que lo hace también en un sistema limpio usando «pbuilder». Si no ha "
6434
#~ "configurado todavía «pbuilder-dist» todavía, :doc:`hágalo ahora<./getting-"
6438
#~ "Uploading it to a PPA (Personal Package Archive) will ensure it builds and "
6439
#~ "give an easy way for you and others to test the binary packages. You will "
6440
#~ "need to set up a PPA in Launchad then upload with ``dput``::"
6442
#~ "Al subirlo a un PPA («Personal Package Archivo», repositorio de paquetes "
6443
#~ "personal) se asegurará de que se compila y que le proporciona a usted y a "
6444
#~ "los demás una forma fácil de probar los paquetes binarios. Necesitará "
6445
#~ "configurar un PPA en Launchpad y luego subirlo con «dput»::"
6448
#~ "In some cases, it might make sense to go directly into Ubuntu first. For "
6449
#~ "instance, Debian might be in a freeze making it unlikely that you're package "
6450
#~ "will make it into Ubuntu in time for the next release. This process is "
6451
#~ "documented on the `\"New Packages\" section of the Ubuntu wiki`_."
6453
#~ "En algunos casos, podría tener sentido ir directamente a Ubuntu primero. Por "
6454
#~ "ejemplo, Debian podría estar en fase de congelación haciendo improbable que "
6455
#~ "su paquete llegue a Ubuntu a tiempo para la próxima emisión. Este proceso "
6456
#~ "está documentado en la `sección «Nuevos paquetes»\" de la wiki de Ubuntu`_."
6459
#~ "You should start by ensuring no patches are applied. Unfortunately a commit "
6460
#~ "is needed before you can merge in the new upstream (this is `bug 815854`_::"
6462
#~ "Debería comenzar por asegurarse de que no se aplica ningún parche. "
6463
#~ "Desafortunadamente hace falta una confirmación antes de que se pueda "
6464
#~ "combinar con lo nuevo de aguas arriba (este es el error `bug 815854`_)::"
6466
#~ msgid "Then upgrade to the new version"
6467
#~ msgstr "Luego actualice a la nueva versión"
6470
#~ "$ bzr merge-upstream --version 2.0.2 "
6471
#~ "https://launchpad.net/ubuntu/+archive/primary/+files/kamoso_2.0.2.orig.tar.bz"
6474
#~ "$ bzr merge-upstream --version 2.0.2 "
6475
#~ "https://launchpad.net/ubuntu/+archive/primary/+files/kamoso_2.0.2.orig.tar.bz"
6479
#~ "Even older packages will include changes directly to sources and kept in the "
6480
#~ "``diff.gz`` source file. This makes it hard to upgrade to new upstream "
6481
#~ "versions or differentiate between patches and is best avoided."
6483
#~ "Incluso paquetes más antiguos incluirán cambios directamente en los fuentes "
6484
#~ "y los mantendrán el archivo fuente «diff.gz». Est complica la actualización "
6485
#~ "a nuevas versiones de aguas arribas o distinguir entre parches por lo que lo "
6486
#~ "mejor es evitarlo."
6488
#~ msgid "FIXME describe traditional packaging here"
6489
#~ msgstr "FIXME describir aquí el empaquetado tradicional"
6492
#~ "You want to work on the Tomboy package in Natty, and you've verified that "
6493
#~ "the source package is named ``tomboy``. Before actually branching the code "
6494
#~ "for Tomboy, create a shared repository to hold the branches for this "
6495
#~ "package. The shared repository will make future work much more efficient."
6497
#~ "Desea trabajar en el paquete Tomboy de Natty, y ha comprobado que el paquete "
6498
#~ "fuente se llama «tomboy». Antes de efectuar la bifurcación del código de "
6499
#~ "Tomboy, cree un repositorio compartido para mantener las ramas de este "
6500
#~ "paquete. Este repositorio compartido hará que el trabajo futuro sea mucho "
6503
#~ msgid "Ubuntu Distributed Development - Introduction"
6504
#~ msgstr "Desarrollo distribuido de Ubuntu - Introducción"
6507
#~ "With Ubuntu Distributed Development all packages in the Ubuntu (and Debian) "
6508
#~ "archive are automatically imported into Bazaar branches on our code hosting "
6509
#~ "site Launchpad. Changes can be made directly to these branches in "
6510
#~ "incremental steps and by anyone with commit access. Changes can also be "
6511
#~ "made in forked branched and merged back in with Merge Proposals when they "
6512
#~ "are large enough to need review or if they are by someone without direct "
6515
#~ "Con el desarrollo distribuido de Ubuntu todos los paquetes del repositorio "
6516
#~ "de Ubuntu (y de Debian) se importan automáticamente en ramas Bazaar en el "
6517
#~ "sitio de hospedaje de código Launchpad. Los cambios se pueden hacer "
6518
#~ "directamente en eses ramas en pasos incrementales y por cualquiera con "
6519
#~ "permisos para confirmar. Los cambios también se pueden hacer en ramas "
6520
#~ "bifurcadas y vueltas a combinar con propuestas de fusión («merge proposals») "
6521
#~ "cuando son lo suficientemente grandes para necesitar una revisión o si están "
6522
#~ "realizadas por alguien que no tiene permiso de confirmar directamente."
6525
#~ "UDD branches are all in a standard location so doing a checkout is easy::"
6527
#~ "Las ramas UDD están todas en una ubicación estándar así que hacer una "
6528
#~ "extracción es sencillo::"
6531
#~ "Many Ubuntu packages are based on the packages in Debian, UDD also imports "
6532
#~ "the Debian package into our branches. In the *kdetoys* branch above the "
6533
#~ "Debian versions from *unstable* are from the merge with blue circles while "
6534
#~ "those from *Debian experimental* are from the merge with yellow circles. "
6535
#~ "Debian released are tagged with their version number e.g. ``4:4.2.2-1``."
6537
#~ "Muchos paquetes de Ubuntu se basan en paquetes de Debian, UDD también "
6538
#~ "importa el paquete de Debian en nuestras ramas. En la rama *kdetoys* "
6539
#~ "anterior las versiones Debian de *unstable* vienen de la fusión con los "
6540
#~ "círculos azules, mientras que las de *Debian experimental* vienen de "
6541
#~ "fusiones con los círculos amarillos. Las versiones de Debian están "
6542
#~ "etiquetadas con su número de versión, por ejemplo, «4:4.2.2-1»."
6544
#~ msgid "Merging - Updating from Debian and Upstream"
6545
#~ msgstr "Fusionar - Actualizar desde Debian y aguas arriba"
6547
#~ msgid "Building a new package"
6548
#~ msgstr "Construir un paquete nuevo"
6550
#~ msgid "Example package"
6551
#~ msgstr "Paquete de ejemplo"
6553
#~ msgid "The bzr-builddeb way"
6554
#~ msgstr "La manera de bzr-builddeb"
6556
#~ msgid "The stdeb way"
6557
#~ msgstr "La manera de stdeb"
6560
#~ "In either case, start by putting this in your ``~/.pydistutils.cfg`` file::"
6562
#~ "En ambos casos, comience por poner esto en su archivo «~/.pydistutils.cfg»::"
6564
#~ msgid "Modern stdeb"
6565
#~ msgstr "stdeb moderno"
6567
#~ msgid "Here's how easy it is::"
6568
#~ msgstr "Es así de fácil::"
6570
#~ msgid "stdeb <= 0.5.1"
6571
#~ msgstr "stdeb <= 0.5.1"
6574
#~ "If you have an older version of stdeb, use this command to create the basic "
6575
#~ "``debian/`` directory layout::"
6577
#~ "Si tiene una versión más antigua de stdeb, use esta orden para crear la "
6578
#~ "distribución de directorios «debian/» básica."
6581
#~ "$ mv deb_dist/munepy-2.0.1/debian . $ rm -rf deb_dist $ bzr add debian $ bzr "
6582
#~ "commit -m'Add debian directory'"
6584
#~ "$ mv deb_dist/munepy-2.0.1/debian . $ rm -rf deb_dist $ bzr add debian $ bzr "
6585
#~ "commit -m'Add debian directory'"
6591
#~ "pkgme_ is a new tool that makes it easy to Debianize a new package. TBD: "
6592
#~ "describe how to use it."
6594
#~ "pkgme_ es una nueva herramienta que facilita Debianizar un paquete nuevo. "
6595
#~ "TBD: describir cómo usarla."
6597
#~ msgid "debian/control file"
6598
#~ msgstr "Archivo debian/control"
6600
#~ msgid "debian/watch file"
6601
#~ msgstr "Archivo debian/watch"
6603
#~ msgid "Here for example is the ``debian/watch`` file I'm using::"
6604
#~ msgstr "Este es un ejemplo del archivo «debian/watch» que estoy usando::"
6606
#~ msgid "Building the source package"
6607
#~ msgstr "Construir el paquete fuente"
6610
#~ "You probably want to edit the ``debian/control`` file at this point, adding "
6611
#~ "any information that's missing, or fixing incorrect default information. "
6612
#~ "For example, I needed to modify the ``Maintainer`` and ``Description`` "
6613
#~ "fields, and add ``X-Python-Version`` and ``Homepage`` fields."
6615
#~ "A estas alturas probablemente desee editar el archivo «debian/control», "
6616
#~ "añadiendo cualquier información que falte o corrigiendo información "
6617
#~ "predeterminada incorrecta. Por ejemplo, yo necesité modificar los campos "
6618
#~ "«Maintainer» y «Description» y añadir los campos «X-Python-Version» y "
6622
#~ "Let's say I have an upstream project that is not yet available for Ubuntu. "
6623
#~ "I want to create a package from this project and make it available as a PPA_ "
6624
#~ "so that other people can more easily use the code. This also makes a good "
6625
#~ "first step in contributing your package to universe_."
6627
#~ "Digamos que tengo un proyecto de aguas arriba que todavía no está disponible "
6628
#~ "para Ubuntu. Quiero crear un paquete para este proyecto y hacerlo disponible "
6629
#~ "como un PPA de forma que otra gente pueda usar el código más fácilmente. "
6630
#~ "Este es también un buen primer paso para contribuir el paquete a universe_."
6633
#~ "I started with a Python library called `flufl.enum`_, which is a fairly "
6634
#~ "typical setuptools-based Python package. Fortunately, it's also maintained "
6635
#~ "in Launchpad using Bazaar, so that makes bootstrapping much easier."
6637
#~ "Comencé con una biblioteca de Python llamada `flufl.enum`_, que es un "
6638
#~ "paquete de herramientas de configuración basadas en Python bastante típico. "
6639
#~ "Afortunadamente, también se mantiene en Launchpad usando Bazaar, lo que el "
6640
#~ "arranque mucho más sencillo."
6643
#~ "Because we want to package the trunk branch, getting started is pretty "
6646
#~ "Puesto que queremos empaquetar la rama troncal, comenzar es bastante "
6649
#~ msgid "Bootstrapping"
6650
#~ msgstr "Arranque"
6653
#~ "You need to create the initial ``debian`` directory, as well as the "
6654
#~ "necessary files inside the ``debian`` directory. Currently, there are many "
6655
#~ "ways to set up this directory, but hopefully there will be `some "
6656
#~ "convergence`_ in the methods, especially if you're building standard Python "
6657
#~ "setuptools-based libraries and applications."
6659
#~ "Necesita crear el directorio «debian» inicial, así como los archivos "
6660
#~ "necesarios dentro del mismo. Actualmente hay muchas maneras de configurar "
6661
#~ "este directorio, pero por suerte se llegará a `alguna convergencia`_ de los "
6662
#~ "métodos, especialmente si está compilando bibliotecas y aplicaciones "
6663
#~ "estándar de Python basadas en herramientas de configuración."
6666
#~ "You could use the ``dh_make`` command to get things going, or similarly the "
6667
#~ "``bzr dh-make``. The latter might provide some benefits, and can be run "
6668
#~ "like so from inside your branch::"
6670
#~ "Puede usar la orden «dh_make» para que funcione o de forma parecida «bzr dh-"
6671
#~ "make». La última forma podría tener algunas ventajas y la podemos ejecutar "
6672
#~ "así desde dentro de su rama::"
6675
#~ "If you don't have a URL to download a tarball from, you'll need to create "
6676
#~ "the tarball locally first. Use ``bzr dh-make --help`` for details on this "
6679
#~ "Si no dispone de una URL de la que descargar el archivo tar, necesitará "
6680
#~ "crearlo localmente antes. Use «bzr dh-make --help» para detalles sobre esta "
6684
#~ "After you've created the ``debian`` directory template, be sure to ``bzr "
6685
#~ "rm`` any ``debian`` files you don't need (e.g. the ``*.ex`` files), and edit "
6686
#~ "files such as ``debian/control``, ``debian/watch``, ``debian/copyright`` and "
6687
#~ "``debian/changelog``. The following section may give you some hints about "
6690
#~ "Después de que haya creado la plantilla del directorio «debian», asegúrese "
6691
#~ "de hacer «bzr rm» de cualquier archivo en «debian» que no necesite (por "
6692
#~ "ejemplo, los archivos «*.ex») y edite los archivos como «debian/control», "
6693
#~ "«debian/watch», «debian/copyright» y «debian/changelog». La siguiente "
6694
#~ "sección le puede ofrecer algunas ayudas para hacerlo."
6697
#~ "Another way for creating the initial ``debian`` directory for Python "
6698
#~ "setuptools-based packages, is to use the stdeb_ package. The full "
6699
#~ "documentation for this package is available on the `upstream home`_, but you "
6700
#~ "won't need all of the commands. stdeb has a command that is *exactly* what "
6701
#~ "we're looking for!"
6703
#~ "Otra forma de crear el directorio inicial «debian» para paquetes basados en "
6704
#~ "herramientas de configuración de Python, es usar el paquete stdeb_. Existe "
6705
#~ "documentación completa sobre este paquete en `upstream home`_, pero no le "
6706
#~ "harán falta todas las órdenes. ¡stdeb tiene una orden que es *exactamente* "
6707
#~ "lo que está buscando!"
6710
#~ "We also need a ``debian/copyright`` file. Normally, we'd use ``dh_make -c`` "
6711
#~ "for that but again, that doesn't play nicely with UDD. ``dh_make`` expects "
6712
#~ "a particular file system layout that we don't have. No matter, we'll add "
6713
#~ "the copyright file manually::"
6715
#~ "También se necesita un archivo «debian/copyright». Normalmente se usaría "
6716
#~ "«dh_make -c» de nuevo, pero eso no va bien con UDD. «dh_make» espera una "
6717
#~ "disposición del sistema de archivos particular que no tenemos. No improta, "
6718
#~ "porque añadiremos el archivo copyright manualmente::"
6721
#~ "This command leaves you with a ``deb_dist`` directory containing a "
6722
#~ "``flufl.enum_3.0.1`` directory. Inside that is your ``debian/`` directory. "
6723
#~ "Because we're using UDD we don't care about anything else that ``sdist_dsc`` "
6724
#~ "produces, so we can shuffle things around and remove the cruft."
6726
#~ "Esta orden le deja con un directorio «deb_dist» que contiene a su vez un "
6727
#~ "directorio «flufl.enum_3.0.1». Dentro de este último está el directorio "
6728
#~ "«debian». Al usar UDD nos da igual todo lo demás que «sdis_dsc» produce, así "
6729
#~ "que podemos mover las cosas y eliminar lo sobrante."
6732
#~ "Now we want to build the source package. The easiest way to do that is with "
6733
#~ "the ``bzr-builddeb`` plugin, however this requires a valid ``debian/watch`` "
6734
#~ "file so that builddeb can find the upstream tarball. This really should "
6735
#~ "match the version of the checkout you've made."
6737
#~ "Ahora queremos compilar el paquete fuente. La forma más sencilla de hacerlo "
6738
#~ "es con el complemento «bzr-builddeb», sin embargo, eso necesita un archivo "
6739
#~ "«debian/watch» válido de forma que builddeb pueda encontrar el archivo tar "
6740
#~ "de aguas arriba. Esto debería realmente coincidir con la versión de la "
6741
#~ "extracción que ha realizado."
6743
#~ msgid "So, then it's a matter of...::"
6744
#~ msgstr "Así, entonces es una cuestión de...::"
6747
#~ "Now we can build the source package and publish the package as we normally "
6748
#~ "would, with ``bzr builddeb -S`` and ``dput``."
6750
#~ "Ahora podemos compilar el paquete fuente y publicarlo como haríamos "
6751
#~ "normalmente, con «bzr builddeb -S» y «dput»."