Différences
Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentesRévision précédenteProchaine révision | Révision précédente | ||
| howtofix [Le 21/01/2009, 01:51] – 213.95.41.13 | howtofix [Le 01/08/2026, 18:12] (Version actuelle) – supprimée krodelabestiole | ||
|---|---|---|---|
| Ligne 1: | Ligne 1: | ||
| - | <note tip>Ceci est une ébauche d'une traduction de la page https:// | ||
| - | Attention la traduction est aussi sous une licence défini par ces termes : | ||
| - | |||
| - | The website HTML, text, images audio, video, software or other content that is made available on this website are the property of someone - the author in the case of content produced elsewhere and reproduced here with permission, or Canonical or its content suppliers. Before you use this content in some way please take care to ensure that you have the relevant rights and permissions from the copyright holder. | ||
| - | |||
| - | You are welcome to display on your computer, download and print pages from this website provided the content is only used for personal, educational and non-commercial use. You must retain copyright and other notices on any copies or printouts you make. Certain of the materials available on this site are "open source" | ||
| - | |||
| - | ====== Bugs / Comment corriger un paquet ====== | ||
| - | |||
| - | Chaque paquet installé sur le systeme Ubuntu a été construit a partir de sources. Chaque source a une page dédiée pour rapporter des bugs touchant le paquets fils ( paquet issue de la compilation des sources ). | ||
| - | |||
| - | Prenons pour exemple, la page des bugs du paquet " | ||
| - | |||
| - | Vous ne savez pas comment corriger un problème ( bug ) reporter mais ça aide ! | ||
| - | Il y a certaine chose que n' | ||
| - | ===== Replicating bugs ( Rapport de bugs dupliqué ) ===== | ||
| - | |||
| - | Avant de corriger un bug, assurez vous que le bug peut etre reproduit sur votre machine. Sinon, essayer de corriger un bug que vous ne constater par n'est pas prioritaire pour une résolution Si vous avez besoin d' | ||
| - | |||
| - | ===== Installer les outils nécessaire ===== | ||
| - | |||
| - | De nombreux scripts ont été développé pour aider tout en travaillant avec les outils débian et des patches. Installer ces paquet : | ||
| - | |||
| - | sudo apt-get install devscripts ubuntu-dev-tools | ||
| - | |||
| - | Générer un patch : | ||
| - | |||
| - | Ici le simple exemple pour voir comment créer un patch : | ||
| - | |||
| - | - Imaginons que vous avez un rapport de bug disant que la description du paquet xicc contient une erreur orthographique touchant le mot "color " et que nous voulons corriger. (Très mauvais exemples je vous l' | ||
| - | |||
| - | $ apt-cache show xicc | ||
| - | Package: xicc | ||
| - | Priority: optional | ||
| - | Section: universe/ | ||
| - | Installed-Size: | ||
| - | Maintainer: Ross Burton < | ||
| - | Architecture: | ||
| - | Version: 0.2-2 | ||
| - | Depends: libc6 (>= 2.3.4-1), libglib2.0-0 (>= 2.8.0), libice6, libsm6, libx11-6 | ||
| - | Filename: pool/ | ||
| - | Size: 8224 | ||
| - | MD5sum: a266d60cd721ef91fcb1d3d47ecd6a40 | ||
| - | SHA1: b8da21b8dfba7ed9c7ac6fa5c9c3e70b438d7124 | ||
| - | SHA256: 635c287a1c43df31670a20194e774561479d70d981bf24c143c3711799bd839a | ||
| - | Description: | ||
| - | This utility lets you set an ICC colour profile for an X display, so that | ||
| - | | ||
| - | to specifically look for this atom but several applications such as Gimp and | ||
| - | Eye Of Gnome already do. | ||
| - | Bugs: mailto: | ||
| - | Origin: Ubuntu | ||
| - | |||
| - | - L' | ||
| - | |||
| - | < | ||
| - | |||
| - | - Éditez le fichier debian/ | ||
| - | |||
| - | cd xicc-0.2 | ||
| - | sed -i ' | ||
| - | |||
| - | Bien entendu le patch n'est pas toujours si facile et pourrait nécéssiter un patch bien plus important touchant beaucoup de partie dans le paquet originel. Reportez vous à la partie Patch guidelines. | ||
| - | - Adhérer a DebianMaintainerField: | ||
| - | |||
| - | Maintainer: Ross Burton < | ||
| - | |||
| - | par | ||
| - | |||
| - | Maintainer: Ubuntu MOTU Developers < | ||
| - | XSBC-Original-Maintainer: | ||
| - | |||
| - | Pour cette action, vous pouvez utiliser l' | ||
| - | - Mettre à jour le fichier debian/ | ||
| - | |||
| - | dch -i | ||
| - | |||
| - | et décrire les changements que vous avez effectué. | ||
| - | - Générer le nouveau paquet: | ||
| - | |||
| - | debuild -S | ||
| - | |||
| - | Ou si vous créez un paquet non signé: | ||
| - | |||
| - | debuild -S -us -uc | ||
| - | |||
| - | - Regardez avez debdiff: | ||
| - | |||
| - | cd .. | ||
| - | debdiff xicc_0.2-2.dsc xicc_0.2-2ubuntu1.dsc | less | ||
| - | |||
| - | - Pour créer un fichier patch, vous devez envoyer le résultat de debdiff dans un autre fichier: | ||
| - | |||
| - | debdiff xicc_0.2-2.dsc xicc_0.2-2ubuntu1.dsc > xicc_0.2.2ubuntu1.debdiff | ||
| - | |||
| - | - C'est fait. Vous pouvez maintenant joindre le patch debdiff a un rapport de bugou l' | ||
| - | |||
| - | * Vérifier SponsorshipProcess pour voir comment inclure ce patch à Ubuntu. | ||
| - | * (PackagingGuide contient plus d' | ||
| - | * UbuntuDevelopment/ | ||
| - | |||
| - | ===== Tester les corrections ===== | ||
| - | |||
| - | Une fois que votre patch est générer re-rentre dans le dossier des sources et construire le paquet. | ||
| - | < | ||
| - | cd hello-2.2 | ||
| - | sudo apt-get build-dep hello | ||
| - | debuild -us -uc | ||
| - | </ | ||
| - | If the build fails, please review your changes to verify that they are not the cause of the failure. You can regenerate your patched version of the source with the following commands: | ||
| - | |||
| - | rm -rf hello-2.2 | ||
| - | dpkg-source -x hello_2.2-1.dsc | ||
| - | patch -p0 < hello.patch | ||
| - | |||
| - | If the build succeeds, install the package and make sure you can no longer replicate the bug. The local package can be installed with the following command: | ||
| - | |||
| - | sudo dpkg -i hello_2.2-1_*.deb | ||
| - | |||
| - | If your fix doesn' | ||
| - | |||
| - | Uploading the patch | ||
| - | |||
| - | If your patch fixes the bug, please add a comment to the bug, and attach your patch. Be sure to check the patch checkbox when uploading your patch. Assign the bug to " | ||
| - | |||
| - | N.B. If you are familiar with debian packaging, and would be willing to prepare a new revision candidate including the patches to fix the bug, please review MOTU/ | ||
| - | |||
| - | Check out MOTU/ | ||
| - | |||
| - | Fixing bugs in stable releases | ||
| - | |||
| - | The major focus of development and changes is on the current Ubuntu development release. Once we do a stable Ubuntu release, millions of users out there work with it every day and depend on its stability, thus we restrict changes to stable releases to a minimum, for two reasons: | ||
| - | |||
| - | * A regression in a stable release is a catastrophe. It is much better to keep a stable set of known bugs which people learned to live with and work around, than to break existing functionality. | ||
| - | * Even some bug fixes might cause confusion, if they disrupt the way users previously worked with the software. This particularly affects user interface and string changes, API/ABI breaks, etc. | ||
| - | |||
| - | Nevertheless we do want to provide fixes for critical/ | ||
| - | |||
| - | Besides that, a lot of users also need a newer version of a particular piece of software, without generally updating their entire distribution. For those we provide a " | ||
howtofix.1232499080.txt.gz · Dernière modification : (modification externe)
Sauf mention contraire, le contenu de ce wiki est placé sous les termes de la licence suivante : CC Attribution-Noncommercial-Share Alike 4.0 International