|
|
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
|
|
|
202.
|
|
|
In order to get it sponsored in the next section, you need to file a bug report in Launchpad (if there isn't one already, if there is, use that) and explain why your fix should be included in Ubuntu. For example, for tomboy, you would file a bug `here`_ (edit the URL to reflect the package you have a fix for). Once a bug is filed explaining your changes, put that bug number in the changelog.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:259
|
|
|
203.
|
|
|
Testing the fix
|
|
|
|
|
Testando a correção
|
|
Translated and reviewed by
Rafael Neri
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:269
|
|
|
204.
|
|
|
To build a test package with your changes, run these commands::
|
|
|
|
|
Para construir um pacote de teste com suas alterações, e execute estes comandos::
|
|
Translated and reviewed by
Rafael Neri
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:271
|
|
|
205.
|
|
|
This will create a source package from the branch contents (``-us -uc`` will just omit the step to sign the source package and ``-d`` will skip the step where it checks for build dependencies, pbuilder will take care of that) and ``pbuilder-dist`` will build the package from source for whatever ``release`` you choose.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:276
|
|
|
206.
|
|
|
If ``debuild`` errors out with "Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address" then run the ``update-maintainer`` command (from ubuntu-dev-tools) and it will automatically fix this for you. This happens because in Ubuntu, all Ubuntu Developers are responsible for all Ubuntu packages, while in Debian, packages have maintainers.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:283
|
|
|
207.
|
|
|
In this case with bumprace, run this to view the package information::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:289
|
|
|
208.
|
|
|
As expected, there should now be a ``Homepage:`` field.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:293
|
|
|
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
|
|
|
210.
|
|
|
Submitting the fix and getting it included
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:304
|
