|
|
353.
|
|
|
In the example mentioned above it would make sense to ship Ubuntu with the existing version of the project, add the bugfix, get it into Upstream for their next release and ship that (if suitable) in the next Ubuntu release. It would be the best possible compromise and a situation where everybody wins.
|
|
|
|
|
En el ejemplo mencionado anteriormente tendría sentido emitir Ubuntu con una versión existente del proyecto, añadir la corrección del error, integrarla aguas arriba («upstream») para su próxima emisión y distribuirla (si fuera conveniente) en la próxima emisión de Ubuntu. Sería el mejor compromiso posible y una situación en la que todo el mundo gana.
|
|
Translated by
Jose Luis Tirado
|
|
Reviewed by
Jose Luis Tirado
|
|
|
|
Located in
../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:101
|
|
|
354.
|
|
|
To fix a bug in Ubuntu, you would first get the source code for the package, then work on the fix, document it so it is easy to understand for other developers and users, then build the package to test it. After you have tested it, you can easily propose the change to be included in the current Ubuntu development release. A developer with upload rights will review it for you and then get it integrated into Ubuntu.
|
|
|
|
|
Para arreglar un error en Ubuntu, primero debería obtener el código fuente del paquete, después trabajar en la solución, documentarla de forma que sea fácil de entender por otros desarrolladores y usuarios y luego compilar el paquete para probarlo. Una vez lo haya probado, puede proponer fácilmente que el cambio se incluya en la publicación actualmente en desarrollo de Ubuntu. Un desarrollador con permisos para subir el código lo revisará y hará que se integre en Ubuntu.
|
|
Translated by
Ricardo Pérez López
|
|
Reviewed by
Jose Luis Tirado
|
|
|
|
Located in
../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:106
|
|
|
355.
|
|
|
When trying to find a solution it is usually a good idea to check with Upstream and see if the problem (or a possible solution) is known already and, if not, do your best to make the solution a concerted effort.
|
|
|
|
|
Cuando intente encontrar una solución, habitualmente es una buena idea comprobar los proyectos aguas arriba («upstreams») para ver si el problema (o una posible solución) es conocido y, si no, hacer lo posible para que la solución sea un esfuerzo concertado.
|
|
Translated and reviewed by
Jose Luis Tirado
|
|
|
|
Located in
../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:115
|
|
|
356.
|
|
|
Additional steps might involve getting the change backported to an older, still supported version of Ubuntu and forwarding it to Upstream.
|
|
|
|
|
Podrían ser necesarios pasos adicionales para hacer que el cambio se incluya en una versión antigua, aunque todavía soportada de Ubuntu, y enviarlo aguas arriba («upstream»).
|
|
Translated by
Jose Luis Tirado
|
|
|
|
Located in
../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:119
|
|
|
357.
|
|
|
The most important requirements for success in Ubuntu development are: having a knack for "making things work again," not being afraid to read documentation and ask questions, being a team player and enjoying some detective work.
|
|
|
|
|
Los requisitos más importantes para tener éxito en el desarrollo de Ubuntu son: tener una habilidad especial para «hacer que las cosas funcionen de nuevo», no tener miedo a leer documentación y a hacer preguntas, ser un jugador de equipo y disfrutar con algo de trabajo detectivesco.
|
|
Translated by
Ricardo Pérez López
|
|
Reviewed by
Jose Luis Tirado
|
|
|
|
Located in
../ubuntu-packaging-guide/introduction-to-ubuntu-development.rst:122
|
|
|
358.
|
|
|
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/introduction-to-ubuntu-development.rst:126
|
|
|
359.
|
|
|
KDE Packaging
|
|
|
|
|
Empaquetado de KDE
|
|
Translated by
Jose Luis Tirado
|
|
|
|
Located in
../ubuntu-packaging-guide/kde.rst:3
|
|
|
360.
|
|
|
Packaging of KDE programs in Ubuntu is managed by the Kubuntu and MOTU teams. You can contact the Kubuntu team on the `Kubuntu mailing list <KubuntuML_>`_ and ``#kubuntu-devel`` Freenode IRC channel. More information about Kubuntu development is on the `Kubuntu wiki page <Wiki_>`_.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/kde.rst:5
|
|
|
361.
|
|
|
Our packaging follows the practices of the `Debian Qt/KDE Team <QtKDETeam_>`_ and Debian KDE Extras Team. Most of our packages are derived from the packaging of these Debian teams.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/kde.rst:10
|
|
|
362.
|
|
|
Patching Policy
|
|
|
|
|
Política de parches
|
|
Translated by
Jose Luis Tirado
|
|
|
|
Located in
../ubuntu-packaging-guide/kde.rst:15
|
