|
|
211.
|
|
|
With the changelog entry written and saved, run ``debuild`` one more time::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:306
|
|
|
212.
|
|
|
and this time it will be signed and you are now ready to get your diff to submit to get sponsored.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:310
|
|
|
213.
|
|
|
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::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:313
|
|
|
214.
|
|
|
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.
|
|
|
|
|
Isto lhe levará por uma série de passos para assegurar que o erro vá parar no lugar correto. Assegure-se de revisar o diff novamente para ter certeza de que não inclui alterações aleatórias que você tenha feito antes.
|
|
Translated and reviewed by
Neliton Pereira Jr.
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:320
|
|
|
215.
|
|
|
Communication is important, so when you add some more description to it to the inclusion request, be friendly, explain it well.
|
|
|
|
|
Comunicação é importante, então quando você adicionar alguma descrição para solicitar a inclusão, seja amigável, explique ela bem.
|
|
Translated and reviewed by
Tiago Hillebrandt
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:324
|
|
|
216.
|
|
|
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.
|
|
|
|
|
Se tudo deu certo você deverá receber um e-mail do sistema de rastreamento de erros do Debian com mais informações. Isto pode levar alguns minutos.
|
|
Translated and reviewed by
Neliton Pereira Jr.
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:327
|
|
|
217.
|
|
|
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.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:330
|
|
|
218.
|
|
|
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::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:340
|
|
|
219.
|
|
|
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::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:348
|
|
|
220.
|
|
|
The format shown in ``1-1.0-1ubuntu1.debdiff`` shows:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:356
|
