|
|
181.
|
|
|
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.
|
|
|
|
|
Há livros inteiros escritos sobre encontrar erros, corrigi-los, testá-los, etc. Se você for um programador novato, tente corrigir erros fáceis primeiro, como erros de digitação óbvios. Tente alterar o mínimo possível, e documente sua alteração e suposições com clareza.
|
|
Translated and reviewed by
Neliton Pereira Jr.
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:175
|
|
|
182.
|
|
|
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:
|
|
|
|
|
Antes de trabalhar na correção você mesmo, tenha certeza de investigar se ninguém já corrigiu ou está trabalhando na correção para a falha. Boas fontes para verificar são:
|
|
Translated and reviewed by
Tiago Hillebrandt
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:180
|
|
|
183.
|
|
|
Upstream (and Debian) bug tracker (open and closed bugs),
|
|
|
|
|
Rastreamento de erros upstream (e Debian) de erros abertos e fechados,
|
|
Translated and reviewed by
Neliton Pereira Jr.
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:183
|
|
|
184.
|
|
|
Upstream revision history (or newer release) might have fixed the problem,
|
|
|
|
|
Histórico de revisão do upstream (ou lançamento recente) poderia ter corrigido o problema,
|
|
Translated and reviewed by
Tiago Hillebrandt
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:184
|
|
|
185.
|
|
|
bugs or package uploads of Debian or other distributions.
|
|
|
|
|
bugs ou envio de pacotes do Debian ou outras distribuições.
|
|
Translated and reviewed by
Tiago Hillebrandt
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:185
|
|
|
186.
|
|
|
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::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:190
|
|
|
187.
|
|
|
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::
|
|
|
|
|
Isso copiará o empacotamento para um diretório temporário. Agora você pode editar arquivos com um editor de textos ou aplicar patches do upstream, por exemplo::
|
|
Translated and reviewed by
Tiago Hillebrandt
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:195
|
|
|
188.
|
|
|
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``.
|
|
|
|
|
Após editar o tipo de arquivo ``exit`` ou pressione ``control-d`` para sair do shell temporário. O novo patch será adicionado em ``debian/patches``.
|
|
Translated and reviewed by
Tiago Hillebrandt
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:200
|
|
|
189.
|
|
|
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::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:203
|
|
|
190.
|
|
|
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.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:210
|
