Browsing Brazilian Portuguese translation

Don't show this notice anymore
Before translating, be sure to go through Ubuntu Translators instructions and Brazilian Portuguese guidelines.
110 of 14 results
2.
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:
(no translation yet)
Located in ../ubuntu-packaging-guide/auto-pkg-test.rst:5
6.
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.
(no translation yet)
Located in ../ubuntu-packaging-guide/auto-pkg-test.rst:17
18.
Now build a testbed with::
(no translation yet)
Located in ../ubuntu-packaging-guide/auto-pkg-test.rst:103
122.
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::
(no translation yet)
Located in ../ubuntu-packaging-guide/debian-dir-overview.rst:268
171.
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.
(no translation yet)
Located in ../ubuntu-packaging-guide/fixing-a-bug.rst:131
201.
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.
(no translation yet)
Located in ../ubuntu-packaging-guide/fixing-a-bug.rst:252
209.
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.
(no translation yet)
Located in ../ubuntu-packaging-guide/fixing-a-bug.rst:296
268.
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).
(no translation yet)
Located in ../ubuntu-packaging-guide/getting-set-up.rst:66
273.
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.
(no translation yet)
Located in ../ubuntu-packaging-guide/getting-set-up.rst:95
275.
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.
(no translation yet)
Located in ../ubuntu-packaging-guide/getting-set-up.rst:104
110 of 14 results

This translation is managed by Ubuntu Brazilian Portuguese Translators, assigned by Ubuntu Translators.

You are not logged in. Please log in to work on translations.

Contributors to this translation: Adriana Miyazaki de Moura, Aliadam, Altair Antonio Julião de Jesus, Fabiano Bovo, Gabriel Barbosa Nascimento, Gerson "fserve" Barreiros, Jose, Kenzo Okamura, Neliton Pereira Jr., Rafael Neri, Rodrigo Soares Fragozo, Rudinei Weschenfelder, Tiago Hillebrandt, Ursula Junque, Vinicius Almeida, semcentro.