|
155.
|
|
|
If you don't know the source package containing the code that has the problem, but you do know the path to the affected program on your system, you can discover the source package that you'll need to work on.
|
|
|
|
Si no se conoce el paquete fuente que contiene el código con el problema, pero sí la ruta al programa afectado en su sistema, puede encontrar el paquete en el que necesitará trabajar.
|
|
Translated and reviewed by
Jose Luis Tirado
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:37
|
|
156.
|
|
|
Let's say you've found a bug in Bumprace, a racing game. The Bumprace application can be started by running ``/usr/bin/bumprace`` on the command line. To find the binary package containing this application, use this command::
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:41
|
|
157.
|
|
|
This would print out::
|
|
|
|
Esto mostrará::
|
|
Translated and reviewed by
Jose Luis Tirado
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:47
|
|
158.
|
|
|
Note that the part preceding the colon is the binary package name. It's often the case that the source package and binary package will have different names. This is most common when a single source package is used to build multiple different binary packages. To find the source package for a particular binary package, type::
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:51
|
|
159.
|
|
|
``apt-cache`` is part of the standard installation of Ubuntu.
|
|
|
|
``apt-cache`` es parte de la instalación estándar de Ubuntu.
|
|
Translated by
Jose Luis Tirado
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:62
|
|
160.
|
|
|
Confirming the problem
|
|
|
|
Confirmar el problema
|
|
Translated by
Jose Luis Tirado
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:65
|
|
161.
|
|
|
Once you have figured out which package the problem is in, it's time to confirm that the problem exists.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:67
|
|
162.
|
|
|
Let's say the package ``bumprace`` does not have a homepage in its package description. As a first step you would check if the problem is not solved already. This is easy to check, either take a look at Software Center or run::
|
|
|
|
Digamos que el paquete ``bumprace`` no tiene una página web en su descripción. Como primer paso podría comprobar que el problema no esté ya resuelto. Es fácil de hacer, bien mirando al Centro de software o ejecutando::
|
|
Translated by
Paco Molinero
|
|
Reviewed by
Jose Luis Tirado
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:70
|
|
163.
|
|
|
The output should be similar to this::
|
|
|
|
La salida debería ser algo parecido a esto::
|
|
Translated by
Jose Luis Tirado
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:76
|
|
164.
|
|
|
A counter-example would be ``gedit``, which has a homepage set::
|
|
|
|
Un contraejemplo sería ``gedit``, el cual tiene definida una página web::
|
|
Translated by
Jose Luis Tirado
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:102
|