|
|
221.
|
|
|
``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.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:358
|
|
|
222.
|
|
|
``1.0-1ubuntu1`` shows the new version being used. This makes it easy to see what the new version is.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:362
|
|
|
223.
|
|
|
``.debdiff`` is an extension that makes it clear that it is a debdiff.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:364
|
|
|
224.
|
|
|
While this format is optional, it works well and you can use this.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:366
|
|
|
225.
|
|
|
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::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:368
|
|
|
226.
|
|
|
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.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:376
|
|
|
227.
|
|
|
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.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:383
|
|
|
228.
|
|
|
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.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:389
|
|
|
229.
|
|
|
Additional considerations
|
|
|
|
|
Considerações adicionais
|
|
Translated and reviewed by
Tiago Hillebrandt
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:395
|
|
|
230.
|
|
|
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.
|
|
|
|
|
Se você encontrar um pacote e achar que há algumas coisas pequenas que você pode corrigir ao mesmo tempo, faça isso. Isto irá acelerar a revisão e a inclusão.
|
|
Translated and reviewed by
Neliton Pereira Jr.
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:397
|
