# Roland Mas , 2015. msgid "" msgstr "" "Project-Id-Version: 0\n" "POT-Creation-Date: 2022-07-30 18:23+0200\n" "PO-Revision-Date: 2022-07-30 18:44+0200\n" "Last-Translator: Galina Anikina \n" "Language-Team: French \n" "Language: fr-FR\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n > 1;\n" "X-Generator: Weblate 2.18-dev\n" msgid "Backport" msgstr "Rétroportage" msgid "Rebuild" msgstr "Recompilation" msgid "Source package" msgstr "Paquet source" msgid "Archive" msgstr "Archive" msgid "Meta-package" msgstr "Métapaquet" msgid "Debian Developer" msgstr "Développeur Debian" #, fuzzy #| msgid "Creating a Debian Package" msgid "Debian Package" msgstr "Conception d'un paquet Debian" msgid "Maintainer" msgstr "Mainteneur" msgid "Creating a Debian Package" msgstr "Conception d'un paquet Debian" msgid "It is quite common, for an administrator who has been handling Debian packages in a regular fashion, to eventually feel the need to create their own packages, or to modify an existing package. This chapter aims to answer the most common questions in this field, and provide the required elements to take advantage of the Debian infrastructure in the best way. With any luck, after trying your hand for local packages, you may even feel the need to go further than that and join the Debian project itself!" msgstr "Manipuler régulièrement des paquets Debian provoque tôt ou tard le besoin de créer le sien ou d'en modifier un. Ce chapitre essaie de répondre à vos interrogations en la matière et fournit des éléments pour tirer le meilleur parti de l'infrastructure offerte par Debian. Qui sait, en ayant ainsi mis la main à la pâte, peut-être irez-vous plus loin et deviendrez-vous développeur Debian !" msgid "Rebuilding a Package from its Sources" msgstr "Recompiler un paquet depuis ses sources" #, fuzzy #| msgid "packagetypes" msgid "packagebackport" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid "packagerebuild" msgstr "paquettypes" msgid "Rebuilding a binary package is required under several sets of circumstances. In some cases, the administrator needs a software feature that requires the software to be compiled from sources, with a particular compilation option; in others, the software as packaged in the installed version of Debian is not recent enough. In the latter case, the administrator will usually build a more recent package taken from a newer version of Debian — such as Testing or even Unstable — so that this new package works in their Stable distribution; this operation is called “backporting”. As usual, care should be taken, before undertaking such a task, to check whether it has been done already — a quick look on the Debian Package Tracker for that package will reveal that information. backport" msgstr "Plusieurs éléments justifient la recompilation d'un paquet depuis ses sources. L'administrateur peut avoir besoin d'une fonctionnalité du logiciel qui implique de recompiler le programme en activant une option particulière ou souhaiter en installer une version plus récente que celle fournie dans sa version de Debian (dans ce cas, il recompilera un paquet plus récent récupéré dans la version Testing ou Unstable pour qu'il fonctionne parfaitement dans sa distribution Stable, opération appelée le rétroportage). On prendra soin de vérifier, avant de se lancer dans une recompilation, que personne d'autre ne s'en est déjà chargé ; on pourra vérifier en particulier sur la page dédiée du système de suivi de paquets. rétroportage" msgid "Getting the Sources" msgstr "Récupérer les sources" #, fuzzy #| msgid "packagetypes" msgid "packagesource" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid "aptsource" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid "apt-getsource" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid "aptupdate" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid "apt-getupdate" msgstr "paquettypes" msgid "/etc/etc/apt/APT" msgstr "" #, fuzzy #| msgid "Build-Depends, control field" msgid "deb-src" msgstr "Build-Depends, champ d'en-tête du paquet source" msgid "Rebuilding a Debian package starts with getting its source code. The easiest way is to use the apt-get source package-name command. This command requires a deb-src line in the /etc/apt/sources.list file, and up-to-date index files (i.e. apt-get update). These conditions should already be met if you followed the instructions from the chapter dealing with APT configuration (see ). Note, however, that you will be downloading the source packages from the Debian version mentioned in the deb-src line." msgstr "" #, fuzzy #| msgid "Rebuilding a Debian package starts with getting its source code. The easiest way is to use the apt-get source source-package-name command. This command requires a deb-src line in the /etc/apt/sources.list file, and up-to-date index files (i.e. apt-get update). These conditions should already be met if you followed the instructions from the chapter dealing with APT configuration (see ). Note however, that you will be downloading the source packages from the Debian version mentioned in the deb-src line. If you need another version, you may need to download it manually from a Debian mirror or from the web site. This involves fetching two or three files (with extensions *.dsc — for Debian Source Control — *.tar.comp, and sometimes *.diff.gz or *.debian.tar.comp — comp taking one value among gz, bz2 or xz depending on the compression tool in use), then run the dpkg-source -x file.dsc command. If the *.dsc file is directly accessible at a given URL, there is an even simpler way to fetch it all, with the dget URL command. This command (which can be found in the devscripts package) fetches the *.dsc file at the given address, then analyzes its contents, and automatically fetches the file or files referenced within. Once everything has been downloaded, it extracts the source package (unless the -d or --download-only option is used)." msgid "If you need another version, you may need to download it manually from a Debian mirror or from the web site. This involves fetching two or three files (with extensions *.dsc — for Debian Source Control — *.tar.comp, and sometimes *.diff.gz or *.debian.tar.comp — comp taking one value among gz, bz2 or xz depending on the compression tool in use), then run the dpkg-source -x file.dsc command. If the *.dsc file is directly accessible at a given URL, there is an even simpler way to fetch it all, with the dget URL command. This command (which can be found in the devscripts package) fetches the *.dsc file at the given address, then analyzes its contents, and automatically fetches the file or files referenced within. Once everything has been downloaded, it verifies the integrity of the downloaded source packages using dscverify, and it extracts the source package (unless the -d or --download-only option is used). The Debian keyring is needed, unless the option -u is supplied." msgstr "Pour recompiler un paquet Debian, il faut commencer par rapatrier son code source. Le moyen le plus simple est d'employer la commande apt-get source nom-paquet-source, qui nécessite la présence d'une ligne de type deb-src dans le fichier /etc/apt/sources.list et l'exécution préalable de la commande apt-get update. C'est déjà le cas si vous avez suivi les instructions du chapitre portant sur la configuration d'APT (voir ). Notez cependant que vous téléchargerez les paquetages sources du paquet disponible dans la version de Debian désignée par la ligne deb-src de ce fichier de configuration. Si vous souhaitez en rapatrier une version particulière, il vous faudra peut-être la télécharger manuellement depuis un miroir Debian ou depuis le site web : récupérer deux ou trois fichiers (d'extensions *.dsc — pour Debian Source Control — *.tar.comp et parfois *.diff.gz ou *.debian.tar.comp — comp pouvant prendre les valeurs gz, bz2 ou xz selon l'outil de compression employé), puis exécuter la commande dpkg-source -x fichier.dsc. Si le fichier *.dsc est disponible à une URL donnée, on pourra même se simplifier la vie en utilisant dget URL : cette commande (qui fait partie du paquet devscripts) récupère le *.dsc à l'adresse indiquée, en analyse le contenu et récupère automatiquement le ou les fichiers qu'il référence. Le paquet source est même extrait localement (à moins que l'option -d ou --download-only soit spécifiée)." msgid "devscripts" msgstr "devscripts" #, fuzzy #| msgid "debi" msgid "dscverify" msgstr "debi" #, fuzzy #| msgid "dput" msgid "dget" msgstr "dput" #, fuzzy #| msgid "dput" msgid "dpkg-source" msgstr "dput" #, fuzzy #| msgid "Makefile" msgid ".dsc" msgstr "Makefile" #, fuzzy #| msgid "Makefile" msgid ".diff.gz" msgstr "Makefile" #, fuzzy #| msgid "packagetypes" msgid ".debian.tar.tar.gz" msgstr "paquettypes" msgid ".debian.tar.tar.bz2" msgstr "" #, fuzzy #| msgid "packagetypes" msgid ".debian.tar.tar.xz" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid ".tar.tar.gz" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid ".tar.tar.bz2" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid ".tar.tar.xz" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid "apt--download-only" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid "apt-get--download-only" msgstr "paquettypes" #, fuzzy #| msgid "devscripts" msgid "debian-archive-keyring" msgstr "devscripts" msgid "Making Changes" msgstr "Effectuer les modifications" msgid "Let us use the samba package as an example." msgstr "" msgid "" "$ apt source samba\n" "Reading package lists... Done\n" "NOTICE: 'samba' packaging is maintained in the 'Git' version control system at:\n" "https://salsa.debian.org/samba-team/samba.git\n" "Please use:\n" "git clone https://salsa.debian.org/samba-team/samba.git\n" "to retrieve the latest (possibly unreleased) updates to the package.\n" "Need to get 12.3 MB of source archives.\n" "Get:1 http://security.debian.org/debian-security bullseye-security/main samba 2:4.13.13+dfsg-1~deb11u3 (dsc) [4,514 B]\n" "Get:2 http://security.debian.org/debian-security bullseye-security/main samba 2:4.13.13+dfsg-1~deb11u3 (tar) [11.8 MB]\n" "Get:3 http://security.debian.org/debian-security bullseye-security/main samba 2:4.13.13+dfsg-1~deb11u3 (diff) [468 kB]\n" "Fetched 12.3 MB in 3s (4,582 kB/s)\n" "dpkg-source: info: extracting samba in samba-4.13.13+dfsg\n" "dpkg-source: info: unpacking samba_4.13.13+dfsg.orig.tar.xz\n" "dpkg-source: info: unpacking samba_4.13.13+dfsg-1~deb11u3.debian.tar.xz\n" "dpkg-source: info: using patch list from debian/patches/series\n" "dpkg-source: info: applying 07_private_lib\n" "dpkg-source: info: applying bug_221618_precise-64bit-prototype.patch\n" "dpkg-source: info: applying [...]\n" "" msgstr "" #, fuzzy #| msgid "The source of the package is now available in a directory named after the source package and its version (for instance, samba-4.1.17+dfsg); this is where we'll work on our local changes." msgid "The source of the package is now available in a directory named after the source package and its version (samba-4.13.13+dfsg); this is where we'll work on our local changes." msgstr "Les sources maintenant disponibles dans un répertoire portant le nom du paquet source et sa version (par exemple samba-4.1.17+dfsg), nous pouvons nous y rendre pour y effectuer nos modifications." #, fuzzy #| msgid "The first thing to do is to change the package version number, so that the rebuilt packages can be distinguished from the original packages provided by Debian. Assuming the current version is 2:4.1.17+dfsg-2, we can create version 2:4.1.17+dfsg-2falcot1, which clearly indicates the origin of the package. This makes the package version number higher than the one provided by Debian, so that the package will easily install as an update to the original package. Such a change is best effected with the dch command (Debian CHangelog) from the devscripts package, with an command such as dch --local falcot. This invokes a text editor (sensible-editor — this should be your favorite editor if it is mentioned in the VISUAL or EDITOR environment variables, and the default editor otherwise) to allow documenting the differences brought by this rebuild. This editor shows us that dch really did change the debian/changelog file." msgid "The first thing to do is to change the package version number, so that the rebuilt packages can be distinguished from the original packages provided by Debian. Assuming the current version is 2:4.13.13+dfsg-1~deb11u3, we can create version 2:4.13.13+dfsg-1~deb11u3+falcot1, which clearly indicates the origin of the package. This makes the package version number higher than the one provided by Debian, so that the package will easily install as an update to the original package. Such a change is best effected with the dch command (Debian CHangelog) from the devscripts package. dch devscripts packageversion" msgstr "La première modification à apporter est de changer le numéro de version du paquet pour distinguer les paquets recompilés des originaux fournis par Debian. Supposons que la version actuelle soit 2:4.1.17+dfsg-2 ; nous pouvons créer une version 2:4.1.17+dfsg-2falcot1, ce qui désigne clairement l'origine du paquet. De cette manière, la version est supérieure à celle fournie par Debian et le paquet s'installera facilement en tant que mise à jour de l'original. Pour effectuer ce changement, il est préférable d'utiliser le programme dch (Debian CHangelog) du paquet devscripts en saisissant dch --local falcot. Cette commande démarre un éditeur de texte (sensible-editor — votre éditeur favori si vous l'avez précisé dans la variable d'environnement VISUAL ou EDITOR, un éditeur par défaut dans les autres cas) où l'on pourra documenter les différences apportées par cette recompilation. On peut constater que dch a bien modifié le fichier debian/changelog." #, fuzzy #| msgid "" #| "$ dpkg-buildpackage -us -uc\n" #| "[...]\n" #| "" msgid "" "$ cd 4.13.13+dfsg-1~deb11u3\n" "$ dch --local +falcot\n" "" msgstr "" "$ dpkg-buildpackage -us -uc\n" "[...]\n" "" msgid "The last command invokes a text editor (sensible-editor — this should be your favorite editor if it is mentioned in the VISUAL or EDITOR environment variables, and the default editor otherwise) to allow documenting the differences brought by this rebuild. This editor shows us that dch really did change the debian/changelog file." msgstr "" #, fuzzy #| msgid "debi" msgid "sensible-editor" msgstr "debi" #, fuzzy #| msgid "Makefile" msgid "VISUAL" msgstr "Makefile" #, fuzzy #| msgid "packagetypes" msgid "environment variableVISUAL" msgstr "paquettypes" #, fuzzy #| msgid "Makefile" msgid "EDITOR" msgstr "Makefile" #, fuzzy #| msgid "packagetypes" msgid "environment variableEDITOR" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid "packagechangelog" msgstr "paquettypes" #, fuzzy #| msgid "When a change in build options is required, the changes need to be made in debian/rules, which drives the steps in the package build process. In the simplest cases, the lines concerning the initial configuration (./configure …) or the actual build ($(MAKE) … or make …) are easy to spot. If these commands are not explicitly called, they are probably a side effect of another explicit command, in which case please refer to their documentation to learn more about how to change the default behavior. With packages using dh, you might need to add an override for the dh_auto_configure or dh_auto_build commands (see their respective manual pages for explanations on how to achieve this)." msgid "When a change in build options is required, the changes need to be made in debian/rules, which drives the steps in the package build process. In the simplest cases, the lines concerning the initial configuration (./configure …) or the actual build ($(MAKE) … or make … or cmake … or …) are easy to spot. If these commands are not explicitly called, they are probably a side effect of another explicit command, in which case please refer to their documentation to learn more about how to change the default behavior. With packages using dh, you might need to add an override for the dh_auto_configure or dh_auto_build commands (see their respective manual pages and debhelper 7 for explanations on how to achieve this)." msgstr "Si une modification des options de compilation s'avère nécessaire, il faudra modifier le fichier debian/rules, qui pilote les différentes étapes de la compilation du paquet. Dans les cas les plus simples, vous repérerez facilement les lignes concernant la configuration initiale (./configure …) ou déclenchant la compilation ($(MAKE) … ou make …). En les adaptant convenablement, il est possible d'obtenir l'effet souhaité. Si ces commandes n'apparaissent pas directement, elles sont vraisemblablement appelées par une des commandes présentes. Il faudra se référer à leur documentation pour en apprendre plus sur la manière de changer le comportement par défaut. Pour les paquets qui utilisent dh, il sera peut-être nécessaire de surcharger les commandes dh_auto_configure ou dh_auto_build (voir leurs pages de manuel respectives pour des explications à ce sujet)." #, fuzzy #| msgid "packagetypes" msgid "dhdh_auto_build" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid "dhdh_auto_configure" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid "dhoverride target" msgstr "paquettypes" #, fuzzy #| msgid "dch" msgid "dhdebhelper" msgstr "dch" #, fuzzy #| msgid "packageDebianarchive of" msgid "packagerulesrules" msgstr "paquetDebianarchive de" #, fuzzy #| msgid "debhelper" msgid "debhelper" msgstr "debhelper" msgid "Depending on the local changes to the packages, an update may also be required in the debian/control file, which contains a description of the generated packages. In particular, this file contains Build-Depends lines controlling the list of dependencies that must be fulfilled at package build time. These often refer to versions of packages contained in the distribution the source package comes from, but which may not be available in the distribution used for the rebuild. There is no automated way to determine if a dependency is real or only specified to guarantee that the build should only be attempted with the latest version of a library — this is the only available way to force an autobuilder to use a given package version during build, which is why Debian maintainers frequently use strictly versioned build-dependencies." msgstr "Il convient parfois de s'occuper du fichier debian/control, qui renferme la description des paquets générés. Il peut être intéressant de la modifier pour qu'elle reflète les changements apportés. Par ailleurs, ce fichier contient aussi des champs Build-Depends qui donnent la liste des dépendances de génération du paquet. Celles-ci se rapportent souvent à des versions de paquets contenus dans la distribution d'origine du paquet source, qui ne sont peut-être pas disponibles dans la version utilisée pour la recompilation. Il n'existe pas de moyen automatique pour savoir si une dépendance est réelle ou si elle a été créée pour garantir que la compilation s'effectue bien avec les dernières versions d'une bibliothèque (c'est le seul moyen disponible pour forcer un autobuilder à recompiler le paquet avec une version prédéfinie d'un paquet — c'est pourquoi les mainteneurs Debian utilisent fréquemment ce procédé)." #, fuzzy #| msgid "packageDebianarchive of" msgid "packagecontrolcontrol" msgstr "paquetDebianarchive de" #, fuzzy #| msgid "Build-Depends, control field" msgid "controlBuild-Depends, header field" msgstr "Build-Depends, champ d'en-tête du paquet source" msgid "If you know for sure that these build-dependencies are too strict, you should feel free to relax them locally. Reading the files which document the standard way of building the software — these files are often called INSTALL — will help you figure out the appropriate dependencies. Ideally, all dependencies should be satisfiable from the distribution used for the rebuild; if they are not, a recursive process starts, whereby the packages mentioned in the Build-Depends field must be backported before the target package can be. Some packages may not need backporting, and can be installed as-is during the build process (a notable example is debhelper). Note that the backporting process can quickly become complex if you are not careful. Therefore, backports should be kept to a strict minimum when possible." msgstr "N'hésitez donc pas à modifier ces dépendances pour les assouplir si vous savez qu'elles sont trop strictes. La lecture d'éventuels fichiers documentant le mode de compilation du logiciel (souvent nommés INSTALL) vous sera sans doute utile pour retrouver les bonnes dépendances. Idéalement, il faudrait satisfaire toutes les dépendances avec les paquets disponibles dans la version utilisée pour la recompilation. Sans cela, on entre dans un processus récursif où il faut préalablement rétroporter les paquets donnés dans les champs Build-Depends avant de pouvoir compléter le rétroportage souhaité. Certains paquets, qui n'ont pas besoin d'être rétroportés, seront installés tels quels pour les besoins de la recompilation (c'est souvent le cas de debhelper). Cependant, le processus peut se compliquer rapidement si l'on n'y prend garde, aussi faut-il éviter autant que possible tout rétroportage non strictement nécessaire." #, fuzzy #| msgid "Makefile" msgid "INSTALL" msgstr "Makefile" msgid "TIP Installing Build-Depends" msgstr "ASTUCE Installer les Build-Depends" #, fuzzy #| msgid "apt-get allows installing all packages mentioned in the Build-Depends fields of a source package available in a distribution mentioned in a deb-src line of the /etc/apt/sources.list file. This is a simple matter of running the apt-get build-dep source-package command." msgid "apt-get allows installing all packages mentioned in the Build-Depends fields of a source package available in a distribution mentioned in a deb-src line of the /etc/apt/sources.list file. This is a simple matter of running the apt-get build-dep package command." msgstr "apt-get aide à installer rapidement tous les paquets cités dans le ou les champs Build-Depends d'un paquet source disponible dans une distribution donnée sur une ligne deb-src du fichier /etc/apt/sources.list. Il suffit pour cela d'exécuter la commande apt-get build-dep paquet-source." #, fuzzy #| msgid "packagetypes" msgid "APT/etc/apt/sources.list" msgstr "paquettypes" #, fuzzy #| msgid "dput" msgid "apt-get" msgstr "dput" msgid "Starting the Rebuild" msgstr "Démarrer la recompilation" msgid "When all the needed changes have been applied to the sources, we can start generating the actual binary package (.deb file). The whole process is managed by the dpkg-buildpackage command." msgstr "Toutes les modifications souhaitables étant apportées sur les sources, il faut maintenant régénérer le paquet binaire correspondant (fichier .deb). Tout ce processus de création est contrôlé par le programme dpkg-buildpackage." #, fuzzy #| msgid "Makefile" msgid ".deb" msgstr "Makefile" #, fuzzy #| msgid "pbuilder" msgid "dpkg-buildpackage" msgstr "pbuilder" msgid "Rebuilding a package" msgstr "Recompilation d'un paquet" msgid "" "$ dpkg-buildpackage -us -uc\n" "[...]\n" "" msgstr "" "$ dpkg-buildpackage -us -uc\n" "[...]\n" "" #, fuzzy #| msgid "The previous command can fail if the Build-Depends fields have not been updated, or if the related packages are not installed. In such a case, it is possible to overrule this check by passing the -d option to dpkg-buildpackage. However, explicitly ignoring these dependencies runs the risk of the build process failing at a later stage. Worse, the package may seem to build correctly but fail to run properly: some programs automatically disable some of their features when a required library is not available at build time." msgid "The previous command can fail if the Build-Depends field has not been updated, or if the related packages are not installed. In such a case, it is possible to overrule this check by passing the -d option to dpkg-buildpackage. However, explicitly ignoring these dependencies runs the risk of the build process failing at a later stage. Worse, the package may seem to build correctly but fail to run properly: some programs automatically disable some of their features when a required library is not available at build time. The switch can still be very useful if you only want to create a source package, which is supposed to be passed to clean build environments as described in ." msgstr "La commande précédente échoue si les champs Build-Depends n'ont pas été corrigés ou si les dépendances correspondantes n'ont pas été installées. Dans ce cas, on outrepasse cette vérification en ajoutant le paramètre -d à l'invocation de dpkg-buildpackage. En ignorant volontairement ces dépendances, on s'expose cependant à ce que la compilation échoue plus tard. Pire, il se peut que le paquet compile correctement mais que son fonctionnement soit altéré car certains programmes désactivent automatiquement des fonctionnalités s'ils détectent l'absence d'une bibliothèque lors de la compilation." msgid "The other options used in the above example make sure that neither the source package's .dsc (-us) nor the produced .changes file (-uc) get signed with the package builder's cryptographic key after the asuccessful build." msgstr "" msgid "TOOL fakeroot" msgstr "OUTIL fakeroot" #, fuzzy #| msgid "dch" msgid "fakeroot" msgstr "dch" # TODO: INTEGRATE ALTERNATE STRING: sponsoring #, fuzzy #| msgid "sponsoring" msgid "root" msgstr "parrainage" #, fuzzy #| msgid "packagetypes" msgid "accountroot account" msgstr "paquettypes" msgid "In essence, the package creation process is a simple matter of gathering in an archive a set of existing (or built) files; most of the files will end up being owned by root in the archive. However, building the whole package under this user would imply increased risks; fortunately, this can be avoided with the fakeroot command. This tool can be used to run a program and give it the impression that it runs as root and creates files with arbitrary ownership and permissions. When the program creates the archive that will become the Debian package, it is tricked into creating an archive containing files marked as belonging to arbitrary owners, including root. This setup is so convenient that dpkg-buildpackage uses fakeroot by default when building packages." msgstr "Le processus de création de paquet, qui finalement se contente de rassembler dans une archive des fichiers existant localement (ou compilés), a besoin de créer des fichiers dont le propriétaire sera le plus souvent root. Pour éviter de compiler les paquets sous l'identité de l'administrateur, ce qui induirait des risques inutiles, on peut utiliser l'utilitaire nommé fakeroot. Lorsqu'il est utilisé pour lancer un programme, fakeroot laisse croire à ce programme qu'il tourne sous l'identité de root, et que les fichiers qu'il crée appartiennent également à l'administrateur. Lorsque le programme va créer l'archive qui deviendra le paquet Debian, il pourra ainsi y placer des fichiers appartenant à divers propriétaires. C'est pourquoi dpkg-buildpackage utilise par défaut fakeroot pour la préparation des paquets." msgid "Note that the program is only tricked into “believing” that it operates as a privileged account, and the process actually runs as the user running fakeroot program (and the files are actually created with that user's permissions). At no time does it actually get root privileges that it could abuse." msgstr "Notez qu'il ne s'agit que d'une impression donnée au programme lancé et qu'on ne peut donc pas utiliser cet outil pour obtenir des privilèges quelconques. Le programme tourne réellement sous l'identité de l'utilisateur qui lance fakeroot programme et les fichiers qu'il crée réellement continuent de lui appartenir." #, fuzzy #| msgid "More often than not, Debian developers use a higher-level program such as debuild; this runs dpkg-buildpackage as usual, but it also adds an invocation of a program that runs many checks to validate the generated package against the Debian policy. This script also cleans up the environment so that local environment variables do not “pollute” the package build. The debuild command is one of the tools in the devscripts suite, which share some consistency and configuration to make the maintainers' task easier." msgid "More often than not, Debian developers use a higher-level program such as debuild; this runs dpkg-buildpackage as usual, but it also adds an invocation of a program that runs many checks to validate the generated package against the Debian policy. This script also cleans up the environment so that local environment variables do not “pollute” the package build. The debuild command is one of the tools in the devscripts suite, which share some consistency and configuration to make the maintainers' task easier." msgstr "Les développeurs Debian utilisent plus volontiers un programme comme debuild, qui fera suivre l'appel de dpkg-buildpackage par l'exécution d'un programme chargé de vérifier que le paquet généré est conforme à la charte Debian. Par ailleurs, ce script nettoie l'environnement pour que les variables d'environnement locales n'affectent pas la compilation du paquet. debuild fait partie de la série d'outils du paquet devscripts, qui partagent une certaine cohérence et une configuration commune simplifiant le travail des mainteneurs." msgid "debuild" msgstr "debuild" msgid "QUICK LOOK Building packages in chrooted and virtual environments" msgstr "" msgid "pbuilder" msgstr "pbuilder" #, fuzzy #| msgid "pbuilder" msgid "cowbuilder" msgstr "pbuilder" msgid "schroot" msgstr "schroot" #, fuzzy #| msgid "debuild" msgid "sbuild" msgstr "debuild" msgid "Building a package on an existing system, like a workstation or server, can pose several problems. Maybe the system has packages installed, that conflict with the build requirements. Or maybe it has packages (libraries, headers, etc.) installed, that the project to build is not supposed to use - e.g. from Testing, Unstable, or even from third parties. Also it might have packages installed, which are actually required for the build, but are not listed in debian/control. It is therefore a good practice to build a packages in “clean“ environments." msgstr "" #, fuzzy #| msgid "The pbuilder program (in the similarly named package) allows building a Debian package in a chrooted environment. It first creates a temporary directory containing the minimal system required for building the package (including the packages mentioned in the Build-Depends field). This directory is then used as the root directory (/), using the chroot command, during the build process." msgid "The sbuild, pbuilder, or cowbuilder programs (in the similarly named packages) allow building a Debian package in a chrooted environment. Each of them first creates a temporary directory containing the minimal system required for building the package (including the packages mentioned in the Build-Depends field). This directory is then used as the root directory (/), using the chroot command, during the build process." msgstr "Le programme pbuilder (du paquet éponyme) sert à recompiler un paquet Debian dans un environnement chrooté : il crée un répertoire temporaire contenant un système minimal nécessaire à la reconstruction du paquet (en se basant sur les informations contenues dans le champ Build-Depends). Grâce à la commande chroot, ce répertoire sert ensuite de racine (/) lors du processus de recompilation." #, fuzzy #| msgid "dch" msgid "chroot" msgstr "dch" #, fuzzy #| msgid "This tool allows the build process to happen in an environment that is not altered by users' manipulations. This also allows for quick detection of the missing build-dependencies (since the build will fail unless the appropriate dependencies are documented). Finally, it allows building a package for a Debian version that is not the one used by the system as a whole: the machine can be using Stable for its normal workload, and a pbuilder running on the same machine can be using Unstable for package builds." msgid "These tools allow the build process to happen in an environment that is not altered by users' manipulations. This also allows for quick detection of the missing build-dependencies (since the build will fail unless the appropriate dependencies are documented). Finally, it allows building a package for a Debian version that is not the one used by the system as a whole: the machine can be using Stable for its normal workload, and the chrooted environments can be running on the same machine using Unstable for package builds. Using these tools, it is also possible to build for a different distribution, like Ubuntu." msgstr "Cette technique permet de compiler le paquet dans un environnement non dégradé (notamment par les manipulations des utilisateurs), de détecter rapidement les manques éventuels dans les dépendances de compilation (qui échouera si un élément essentiel n'est pas documenté) et de compiler un paquet pour une version de Debian différente de celle employée par le système (la machine peut utiliser Stable pour le fonctionnement quotidien et pbuilder peut employer Unstable pour la recompilation)." msgid "schroot, sbuild-shell, or pbuilder allow running a command or a login shell in a chrooted environment." msgstr "" msgid "Sometimes it is not enough to build a package in a chrooted environment. This can be due to building for a different architecture where cross-compilation does not work, or due to the tools not being able to create a chrooted environment for the desired target system. Then one can create virtual machines to build the package there. These setups are usually more complex then the tools mentioned above, and rarely needed, so we will only mention this possibility without going into much detail. Check out for an introduction into this topic." msgstr "" # TODO: INTEGRATE ALTERNATE STRING: Mainteneur Debian #, fuzzy #| msgid "Debian Maintainer" msgid "virtualization" msgstr "Debian Maintainer" msgid "Building your First Package" msgstr "Construire son premier paquet" msgid "Meta-Packages or Fake Packages" msgstr "Métapaquet ou faux paquet" #, fuzzy #| msgid "packagetypes" msgid "packagemeta-package" msgstr "paquettypes" #, fuzzy #| msgid "package types" msgid "meta-package" msgstr "types de paquets" #, fuzzy #| msgid "packagetypes" msgid "packagefake package" msgstr "paquettypes" #, fuzzy #| msgid "key pair" msgid "fake package" msgstr "biclé" msgid "Fake packages and meta-packages are similar, in that they are empty shells that only exist for the effects their meta-data have on the package handling stack." msgstr "Faux paquet et métapaquet se concrétisent tous deux par un paquet vide qui n'existe que pour les effets de ses informations d'en-têtes sur la chaîne logicielle de gestion des paquets." #, fuzzy #| msgid "The purpose of a fake package is to trick dpkg and apt into believing that some package is installed even though it's only an empty shell. This allows satisfying dependencies on a package when the corresponding software was installed outside the scope of the packaging system. Such a method works, but it should still be avoided whenever possible, since there is no guarantee that the manually installed software behaves exactly like the corresponding package would and other packages depending on it would not work properly." msgid "The purpose of a fake package is to trick dpkg and apt into believing that some package is installed even though it is only an empty shell. This allows satisfying dependencies on a package when the corresponding software was installed outside the scope of the packaging system. Such a method works, but it should still be avoided whenever possible, since there is no guarantee that the manually installed software behaves exactly like the corresponding package would and other packages depending on it would not work properly." msgstr "Le faux paquet existe pour tromper dpkg et apt en leur faisant croire que le paquet correspondant est installé alors qu'il ne s'agit que d'une coquille vide. Cela aide à satisfaire les dépendances lorsque le logiciel en question a été installé manuellement. Cette méthode fonctionne, mais il faut l'éviter autant que possible ; rien ne garantit en effet que le logiciel installé manuellement constitue un remplaçant parfait du paquet concerné et certains autres paquets, qui en dépendent, pourraient donc ne pas fonctionner." msgid "On the other hand, a meta-package exists mostly as a collection of dependencies, so that installing the meta-package will actually bring in a set of other packages in a single step." msgstr "Le métapaquet existe en tant que collection de paquets par le biais de ses dépendances, que son installation installera donc toutes." msgid "Both these kinds of packages can be created by the equivs-control and equivs-build commands (in the equivs package). The equivs-control file command creates a Debian package header file that should be edited to contain the name of the expected package, its version number, the name of the maintainer, its dependencies, and its description. Other fields without a default value are optional and can be deleted. The Copyright, Changelog, Readme and Extra-Files fields are not standard fields in Debian packages; they only make sense within the scope of equivs-build, and they will not be kept in the headers of the generated package." msgstr "Pour créer ces deux types de paquets, on peut recourir aux programmes equivs-control et equivs-build (du paquet Debian equivs). La commande equivs-control fichier crée un fichier contenant des en-têtes de paquet Debian qu'on modifiera pour indiquer le nom du paquet souhaité, son numéro de version, le nom du mainteneur, ses dépendances, sa description. Tous les autres champs dépourvus de valeur par défaut sont optionnels et peuvent être supprimés. Les champs Copyright, Changelog, Readme et Extra-Files ne sont pas standards pour un paquet Debian. Propres à equivs-build, ils disparaîtront des en-têtes réels du paquet généré." #, fuzzy #| msgid "devscripts" msgid "equivs" msgstr "devscripts" #, fuzzy #| msgid "devscripts" msgid "equivsequivs-control" msgstr "devscripts" #, fuzzy #| msgid "devscripts" msgid "equivsequivs-build" msgstr "devscripts" msgid "Header file of the libxml-libxml-perl fake package" msgstr "Fichier d'en-têtes d'un faux paquet libxml-libxml-perl" #, fuzzy #| msgid "" #| "\n" #| "Section: perl\n" #| "Priority: optional\n" #| "Standards-Version: 3.9.6\n" #| "\n" #| "Package: libxml-libxml-perl\n" #| "Version: 2.0116-1\n" #| "Maintainer: Raphael Hertzog <hertzog@debian.org>\n" #| "Depends: libxml2 (>= 2.7.4)\n" #| "Architecture: all\n" #| "Description: Fake package - module manually installed in site_perl\n" #| " This is a fake package to let the packaging system\n" #| " believe that this Debian package is installed. \n" #| " .\n" #| " In fact, the package is not installed since a newer version\n" #| " of the module has been manually compiled & installed in the\n" #| " site_perl directory." msgid "" "\n" "Depends: libxml2 (>= 2.9.10)\n" "Architecture: all\n" "Description: Fake package - module manually installed in site_perl\n" " This is a fake package to let the packaging system\n" " believe that this Debian package is installed.\n" " .\n" " In fact, the package is not installed since a newer version\n" " of the module has been manually compiled & installed in the\n" " site_perl directory.\n" "]]>" msgstr "" "\n" "Section: perl\n" "Priority: optional\n" "Standards-Version: 3.9.6\n" "\n" "Package: libxml-libxml-perl\n" "Version: 2.0116-1\n" "Maintainer: Raphael Hertzog <hertzog@debian.org>\n" "Depends: libxml2 (>= 2.7.4)\n" "Architecture: all\n" "Description: Fake package - module manually installed in site_perl\n" " This is a fake package to let the packaging system\n" " believe that this Debian package is installed. \n" " .\n" " In fact, the package is not installed since a newer version\n" " of the module has been manually compiled & installed in the\n" " site_perl directory." msgid "The next step is to generate the Debian package with the equivs-build file command. Voilà: the package is created in the current directory and it can be handled like any other Debian package would." msgstr "L'étape suivante consiste à générer le paquet Debian en invoquant la commande equivs-build fichier. Le tour est joué : le paquet est disponible dans le répertoire courant et vous pouvez désormais le manipuler comme tous les autres paquets Debian." msgid "" "$ equivs-build file\n" "\n" "dpkg-buildpackage: info: host architecture amd64\n" " dpkg-source --before-build .\n" " debian/rules clean\n" "dh clean\n" " dh_clean\n" " debian/rules binary\n" "dh binary\n" " dh_update_autotools_config\n" " dh_autoreconf\n" " create-stamp debian/debhelper-build-stamp\n" " dh_prep\n" " dh_install\n" " dh_installdocs\n" " dh_installchangelogs\n" " dh_perl\n" " dh_link\n" " dh_strip_nondeterminism\n" " dh_compress\n" " dh_fixperms\n" " dh_missing\n" " dh_installdeb\n" " dh_gencontrol\n" " dh_md5sums\n" " dh_builddeb\n" "dpkg-deb: building package 'libxml-libxml-perl' in '../libxml-libxml-perl_2.0207-1_all.deb'.\n" " dpkg-genbuildinfo --build=binary\n" " dpkg-genchanges --build=binary >../libxml-libxml-perl_2.0207-1_amd64.changes\n" "dpkg-genchanges: info: binary-only upload (no source code included)\n" " dpkg-source --after-build .\n" "dpkg-buildpackage: info: binary-only upload (no source included)\n" "\n" "The package has been created.\n" "Attention, the package has been created in the current directory,\n" "not in \"..\" as indicated by the messaige above!\n" "]]>" msgstr "" msgid "Simple File Archive" msgstr "Simple archive de fichiers" #, fuzzy #| msgid "dch" msgid "dh_make" msgstr "dch" #, fuzzy #| msgid "dh-make" msgid "dh-make" msgstr "dh-make" msgid "The Falcot Corp administrators need to create a Debian package in order to ease deployment of a set of documents on a large number of machines. The administrator in charge of this task first reads the “New Maintainer's Guide”, then starts working on their first package. " msgstr "Les administrateurs de Falcot SA souhaitent créer un paquet Debian pour déployer facilement un ensemble de documents sur un grand nombre de machines. Après avoir étudié le guide du nouveau mainteneur, l'administrateur en charge de cette tâche se lance dans la création de son premier paquet. " msgid "The first step is creating a falcot-data-1.0 directory to contain the target source package. The package will logically, be named falcot-data and bear the 1.0 version number. The administrator then places the document files in a data subdirectory. Then they invoke the dh_make command (from the dh-make package) to add files required by the package generation process, which will all be stored in a debian subdirectory:" msgstr "Il commence par créer un répertoire falcot-data-1.0, qui abritera le paquet source qu'il a choisi de réaliser. Ce paquet se nommera donc falcot-data et portera le numéro de version 1.0. L'administrateur place ensuite les fichiers des documents qu'il souhaite distribuer dans un sous-répertoire data. Il invoque la commande dh_make (du paquet dh-make) pour ajouter les fichiers requis par le processus de génération d'un paquet (tous contenus dans un sous-répertoire debian) :" #, fuzzy #| msgid "" #| "\n" #| "$ cd falcot-data-1.0\n" #| "$ dh_make --native\n" #| "\n" #| "Type of package: single binary, indep binary, multiple binary, library, kernel module, kernel patch?\n" #| " [s/i/m/l/k/n] i\n" #| "\n" #| "Maintainer name : Raphael Hertzog\n" #| "Email-Address : hertzog@debian.org\n" #| "Date : Fri, 04 Sep 2015 12:09:39 -0400\n" #| "Package Name : falcot-data\n" #| "Version : 1.0\n" #| "License : gpl3\n" #| "Type of Package : Independent\n" #| "Hit <enter> to confirm:\n" #| "Currently there is no top level Makefile. This may require additional tuning.\n" #| "Done. Please edit the files in the debian/ subdirectory now. You should also\n" #| "check that the falcot-data Makefiles install into $DESTDIR and not in / .\n" #| "$" msgid "" "\n" "$ cd falcot-data-1.0\n" "$ dh_make --native\n" "\n" "Type of package: (single, indep, library, python)\n" "[s/i/l/p]? i\n" "\n" "Maintainer Name : Raphael Hertzog\n" "Email-Address : hertzog@debian.org\n" "Date : Sat, 26 Feb 2021 13:02:06 +0100\n" "Package Name : falcot-data\n" "Version : 1.0\n" "License : gpl3\n" "Package Type : indep\n" "Are the details correct? [Y/n/q]\n" "Currently there is not top level Makefile. This may require additional tuning\n" "Done. Please edit the files in the debian/ subdirectory now.\n" "\n" "$" msgstr "" "\n" "$ cd falcot-data-1.0\n" "$ dh_make --native\n" "\n" "Type of package: single binary, indep binary, multiple binary, library, kernel module, kernel patch?\n" " [s/i/m/l/k/n] i\n" "\n" "Maintainer name : Raphael Hertzog\n" "Email-Address : hertzog@debian.org\n" "Date : Fri, 04 Sep 2015 12:09:39 -0400\n" "Package Name : falcot-data\n" "Version : 1.0\n" "License : gpl3\n" "Type of Package : Independent\n" "Hit <enter> to confirm:\n" "Currently there is no top level Makefile. This may require additional tuning.\n" "Done. Please edit the files in the debian/ subdirectory now. You should also\n" "check that the falcot-data Makefiles install into $DESTDIR and not in / .\n" "$" #, fuzzy #| msgid "The selected type of package (indep binary) indicates that this source package will generate a single binary package that can be shared across all architectures (Architecture: all). single binary acts as a counterpart, and leads to a single binary package that is dependent on the target architecture (Architecture: any). In this case, the former choice is more relevant since the package only contains documents and no binary programs, so it can be used similarly on computers of all architectures." msgid "The selected type of package (indep) indicates that this source package will generate a single binary package that can be shared across all architectures (Architecture: all in debian/control). single acts as a counterpart, and leads to a single binary package that is dependent on the target architecture (Architecture: any). In this case, the former choice is more relevant since the package only contains documents and no binary programs, so it can be used similarly on computers of all architectures." msgstr "Le type de paquet indep binary indique que ce paquet source ne générera qu'un seul paquet binaire indépendant de l'architecture (Architecture: all). single binary est le pendant de indep binary pour un seul paquet binaire dépendant de l'architecture (Architecture: any). Nous optons pour le premier choix puisque le paquet abrite des documents et non des programmes binaires : il est donc exploitable sur toutes les architectures." msgid "packagetypes" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid "packagearchitecture" msgstr "paquettypes" msgid "controlArchitecture, header field" msgstr "" #, fuzzy #| msgid "The multiple binary type corresponds to a source package leading to several binary packages. A particular case, library, is useful for shared libraries, since they need to follow strict packaging rules. In a similar fashion, kernel module or kernel patch should be restricted to packages containing kernel modules." msgid "The library type corresponds to a source package leading to several binary packages. It is useful for shared libraries, since they need to follow strict packaging rules." msgstr "multiple binary est à employer pour un paquet source générant plusieurs paquets binaires. Le type library est un cas particulier pour les bibliothèques partagées qui doivent suivre des règles de mise en paquet très strictes. Il en est de même pour kernel module et kernel patch, réservés aux paquets contenant des modules noyau." msgid "TIP Maintainer's name and email address" msgstr "ASTUCE Nom et adresse électronique du mainteneur" msgid "DEBFULLNAMEenvironment variable" msgstr "" #, fuzzy #| msgid "packagetypes" msgid "environment variableDEBFULLNAME" msgstr "paquettypes" msgid "DEBEMAILenvironment variable" msgstr "" #, fuzzy #| msgid "packagetypes" msgid "environment variableDEBEMAIL" msgstr "paquettypes" msgid "EMAILenvironment variable" msgstr "" #, fuzzy #| msgid "packagetypes" msgid "environment variableEMAIL" msgstr "paquettypes" #, fuzzy #| msgid "Makefile" msgid ".bashrc" msgstr "Makefile" msgid "Most of the programs involved in package maintenance will look for your name and email address in the DEBFULLNAME and DEBEMAIL or EMAIL environment variables. Defining them once and for all will avoid you having to type them multiple times. If your usual shell is bash, it is a simple matter of adding the following two lines in your ~/.bashrc file (you will obviously replace the values with more relevant ones!):" msgstr "La plupart des programmes qui recherchent vos nom et adresse électronique de responsable de paquet utilisent les valeurs contenues dans les variables d'environnement DEBFULLNAME et DEBEMAIL ou EMAIL. En les définissant une fois pour toutes, vous vous éviterez de devoir les saisir à de multiples reprises. Si votre shell habituel est bash, il suffit pour cela d'ajouter les deux lignes suivantes dans votre fichier ~/.bashrc (en remplaçant évidemment ces valeurs par celles qui vous correspondent !) :" msgid "" "\n" "export EMAIL=\"hertzog@debian.org\"\n" "export DEBFULLNAME=\"Raphael Hertzog\"" msgstr "" "\n" "export EMAIL=\"hertzog@debian.org\"\n" "export DEBFULLNAME=\"Raphael Hertzog\"" #, fuzzy #| msgid "Makefile" msgid "debian, directory" msgstr "Makefile" msgid "debian, directoryrulesrules" msgstr "" #, fuzzy #| msgid "Makefile" msgid "rules" msgstr "Makefile" msgid "debian, directorycontrolcontrol" msgstr "" #, fuzzy #| msgid "Makefile" msgid "control" msgstr "Makefile" msgid "debian, directorychangelogchangelog" msgstr "" #, fuzzy #| msgid "Makefile" msgid "changelog" msgstr "Makefile" msgid "debian, directorycopyrightcopyright" msgstr "" #, fuzzy #| msgid "Makefile" msgid "copyright" msgstr "Makefile" #, fuzzy #| msgid "The dh_make command created a debian subdirectory with many files. Some are required, in particular rules, control, changelog and copyright. Files with the .ex extension are example files that can be used by modifying them (and removing the extension) when appropriate. When they are not needed, removing them is recommended. The compat file should be kept, since it is required for the correct functioning of the debhelper suite of programs (all beginning with the dh_ prefix) used at various stages of the package build process." msgid "The dh_make command created a debian subdirectory with many files. Some are required, in particular rules, control, changelog and copyright. Files with the .ex extension are example files that can be used by modifying them (and removing the extension) when appropriate. When they are not needed, removing them is recommended. The compat file is not used nor created anymore. Instead of defining the debhelper compatibility level as a number in this file, it is now defined as a build-dependency on the debhelper-compat virtual package in the Build-Depends file in debian/control." msgstr "Le programme dh_make a créé un sous-répertoire debian contenant de nombreux fichiers. Certains sont nécessaires : c'est notamment le cas des fichiers rules, control, changelog et copyright. Les fichiers d'extension .ex sont des fichiers d'exemples qu'on peut modifier et rebaptiser (en supprimant simplement cette extension) si cela s'avère utile. Dans le cas contraire, il convient de les supprimer. Le fichier compat doit être conservé car il est nécessaire au bon fonctionnement des programmes de l'ensemble appelé debhelper, dont les noms commencent par le préfixe dh_ et qui sont employés à diverses étapes de la création de paquet." msgid "The copyright file must contain information about the authors of the documents included in the package, and the related copyright and license. In our case, these are internal documents and their use is restricted to within the Falcot Corp company. The default format used for this file is defined in the Format field. " msgstr "" msgid "The default changelog file is generally appropriate; replacing the “Initial release” with a more verbose explanation and changing the distribution from UNRELEASED or unstable to the target release name is enough." msgstr "" msgid "The control file must also be updated: the Section field can be changed to misc and the Homepage, Vcs-Git and Vcs-Browser fields were removed. The Depends fields was completed with firefox-esr | www-browser so as to ensure the availability of a web browser able to display the documents in the package. If the package does not require to run any commands as root (see ), the Rules-Requires-Root field can be left as is." msgstr "" #, fuzzy #| msgid "packagetypes" msgid "controlDepends, header field" msgstr "paquettypes" msgid "controlHomepage, header field" msgstr "" msgid "controlRules-Requires-Root, header field" msgstr "" msgid "controlSection, header field" msgstr "" msgid "controlVcs-Browser, header field" msgstr "" msgid "controlVcs-Git, header field" msgstr "" msgid "The control file" msgstr "Le fichier control" #, fuzzy #| msgid "" #| "\n" #| "Source: falcot-data\n" #| "Section: misc\n" #| "Priority: optional\n" #| "Maintainer: Raphael Hertzog <hertzog@debian.org>\n" #| "Build-Depends: debhelper (>= 9)\n" #| "Standards-Version: 3.9.5\n" #| "\n" #| "Package: falcot-data\n" #| "Architecture: all\n" #| "Depends: iceweasel | www-browser, ${misc:Depends}\n" #| "Description: Internal Falcot Corp Documentation\n" #| " This package provides several documents describing the internal\n" #| " structure at Falcot Corp. This includes:\n" #| " - organization diagram\n" #| " - contacts for each department.\n" #| " .\n" #| " These documents MUST NOT leave the company.\n" #| " Their use is INTERNAL ONLY." msgid "" "\n" "Build-Depends: debhelper-compat (= 13)\n" "Standards-Version: 4.5.1\n" "Rules-Requires-Root: no\n" "\n" "Package: falcot-data\n" "Architecture: all\n" "Depends: firefox-esr | www-browser, ${misc:Depends}\n" "Description: Internal Falcot Corp Documentation\n" " This package provides several documents describing the internal\n" " structure at Falcot Corp. This includes:\n" " - organization diagram\n" " - contacts for each department.\n" " .\n" " These documents MUST NOT leave the company.\n" " Their use is INTERNAL ONLY.\n" "]]>" msgstr "" "\n" "Source: falcot-data\n" "Section: misc\n" "Priority: optional\n" "Maintainer: Raphael Hertzog <hertzog@debian.org>\n" "Build-Depends: debhelper (>= 9)\n" "Standards-Version: 3.9.5\n" "\n" "Package: falcot-data\n" "Architecture: all\n" "Depends: iceweasel | www-browser, ${misc:Depends}\n" "Description: Documentation interne de Falcot SA\n" " Ce paquet fournit plusieurs documents décrivant\n" " la structure interne de Falcot SA. Cela comprend:\n" " - l'organigramme\n" " - les contacts pour chaque département\n" " .\n" " Ces documents NE DOIVENT PAS sortir de la société.\n" " Ils sont réservés à un USAGE INTERNE." msgid "The changelog file" msgstr "Le fichier changelog" #, fuzzy #| msgid "" #| "\n" #| "falcot-data (1.0) internal; urgency=low\n" #| "\n" #| " * Initial Release.\n" #| " * Let's start with few documents:\n" #| " - internal company structure;\n" #| " - contacts for each department.\n" #| "\n" #| " -- Raphael Hertzog <hertzog@debian.org> Fri, 04 Sep 2015 12:09:39 -0400" msgid "" " Sat, 26 Feb 2022 15:12:06 +0100\n" "]]>" msgstr "" "\n" "falcot-data (1.0) internal; urgency=low\n" "\n" " * Initial Release.\n" " * Commençons avec peu de documents:\n" " - la structure interne de la société\n" " - les contacts de chaque département\n" "\n" " -- Raphael Hertzog <hertzog@debian.org> Fri, 04 Sep 2015 12:09:39 -0400" msgid "The copyright file" msgstr "Le fichier copyright" #, fuzzy #| msgid "" #| "\n" #| "Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" #| "Upstream-Name: falcot-data\n" #| "\n" #| "Files: *\n" #| "Copyright: 2004-2015 Falcot Corp\n" #| "License: \n" #| " All rights reserved." msgid "" "\n" "Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" "Upstream-Name: falcot-data\n" "\n" "Files: *\n" "Copyright: 2004-2021 Falcot Corp\n" "License:\n" " All rights reserved." msgstr "" "\n" "Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" "Upstream-Name: falcot-data\n" "\n" "Files: *\n" "Copyright: 2004-2015 Falcot Corp\n" "License: \n" " All rights reserved." msgid "BACK TO BASICS Makefile file" msgstr "B.A.-BA Fichier Makefile" msgid "Makefile" msgstr "Makefile" #, fuzzy #| msgid "debi" msgid "make" msgstr "debi" msgid "A Makefile file is a script used by the make program; it describes rules for how to build a set of files from each other in a tree of dependencies (for instance, a program can be built from a set of source files). The Makefile file describes these rules in the following format:" msgstr "Un fichier Makefile est un script détaillant au programme make les règles nécessaires pour reconstruire des fichiers issus d'un réseau de dépendances (un programme, fruit de la compilation de fichiers sources, en est un exemple). Le fichier Makefile contient la liste de ces règles en respectant le format suivant :" msgid "" "\n" "target: source1 source2 ...\n" " command1\n" " command2" msgstr "" "\n" "cible: source1 source2 ...\n" " commande1\n" " commande2" #, fuzzy #| msgid "The interpretation of such a rule is as follows: if one of the source* files is more recent than the target file, then the target needs to be generated, using command1 and command2." msgid "The basic interpretation of such a rule is as follows: if one of the source* files is more recent than the target file, then the target needs to be generated, using command1 and command2." msgstr "Cette règle peut se traduire ainsi : si l'un des fichiers source* est plus récent que le fichier cible, il faut exécuter command1 et command2 pour régénérer la cible à partir des sources." msgid "Note that the command lines must start with a tab character; also note that when a command line starts with a dash character (-), failure of the command does not interrupt the whole process." msgstr "Attention, un caractère de tabulation doit impérativement précéder toutes les commandes. Sachez aussi que si la ligne de commande débute par un signe moins (-), la commande peut échouer sans que tout le processus avorte." msgid "The rules file usually contains a set of rules used to configure, build and install the software in a dedicated subdirectory (named after the generated binary package). The contents of this subdirectory is then archived within the Debian package as if it were the root of the filesystem. In our case, files will be installed in the debian/falcot-data/usr/share/falcot-data/ subdirectory, so that installing the generated package will deploy the files under /usr/share/falcot-data/. The rules file is used as a Makefile, with a few standard targets (including clean and binary, used respectively to clean the source directory and generate the binary package)." msgstr "Le fichier rules contient normalement un ensemble de règles employées pour configurer, compiler et installer le logiciel dans un sous-répertoire dédié (portant le nom du paquet binaire généré). Le contenu de ce sous-répertoire est ensuite intégré au paquet Debian comme s'il était la racine du système de fichiers. Dans le cas qui nous concerne, les fichiers seront installés dans le répertoire debian/falcot-data/usr/share/falcot-data/ pour que les documents ainsi diffusés soient disponibles sous /usr/share/falcot-data/ dans le paquet généré. Le fichier rules est de type Makefile avec quelques cibles standardisées (notamment clean et binary, respectivement pour nettoyer et produire le binaire)." msgid "Although this file is the heart of the process, it increasingly contains only the bare minimum for running a standard set of commands provided by the debhelper tool. Such is the case for files generated by dh_make. To install our files, we simply configure the behavior of the dh_install command by creating the following debian/falcot-data.install file:" msgstr "Bien que ce fichier soit au cœur du processus, il est fréquent qu'il ne contienne que le strict minimum pour lancer un ensemble standardisé de commandes qui sont fournies par le paquet debhelper. C'est le cas dans le fichier préparé par dh_make. Pour installer nos fichiers, nous allons simplement modifier le comportement de la commande dh_install en créant le fichier debian/falcot-data.install :" #, fuzzy #| msgid "packagetypes" msgid "dhdh_install" msgstr "paquettypes" msgid "" "\n" "data/* usr/share/falcot-data/" msgstr "" "\n" "data/* usr/share/falcot-data/" #, fuzzy #| msgid "At this point, the package can be created. We will however add a lick of paint. Since the administrators want the documents to be easily accessed from the menus of graphical desktop environments, we add a falcot-data.desktop file and get it installed in /usr/share/applications by adding a second line to debian/falcot-data.install." msgid "At this point, the package can be created. We will, however, add a lick of paint. Since the administrators want the documents to be easily accessed from the menus of graphical desktop environments, we add a falcot-data.desktop file and get it installed in /usr/share/applications by adding a second line to debian/falcot-data.install." msgstr "À ce stade, il est déjà possible de créer le paquet. Nous allons toutefois y ajouter une dernière touche. Les administrateurs souhaitent que ces documents soient facilement accessibles depuis les menus des bureaux graphiques. Pour cela, ils ajoutent un fichier falcot-data.desktop et l'installent dans /usr/share/applications en ajoutant une deuxième ligne au fichier debian/falcot-data.install." #, fuzzy #| msgid "Makefile" msgid ".desktop" msgstr "Makefile" #, fuzzy #| msgid "Makefile" msgid ".install" msgstr "Makefile" msgid "The falcot-data.desktop file" msgstr "Le fichier falcot-data.desktop" msgid "" "\n" "[Desktop Entry]\n" "Name=Internal Falcot Corp Documentation\n" "Comment=Starts a browser to read the documentation\n" "Exec=x-www-browser /usr/share/falcot-data/index.html\n" "Terminal=false\n" "Type=Application\n" "Categories=Documentation;" msgstr "" "\n" "[Desktop Entry]\n" "Name=Internal Falcot Corp Documentation\n" "Comment=Starts a browser to read the documentation\n" "Name[fr]=Documentation interne Falcot SA\n" "Comment[fr]=Lance un navigateur pour lire la documentation\n" "Exec=x-www-browser /usr/share/falcot-data/index.html\n" "Terminal=false\n" "Type=Application\n" "Categories=Documentation;" msgid "The updated debian/falcot-data.install looks like this:" msgstr "Le fichier debian/falcot-data.install mis à jour ressemble donc à ceci :" msgid "" "\n" "data/* usr/share/falcot-data/\n" "falcot-data.desktop usr/share/applications/" msgstr "" "\n" "data/* usr/share/falcot-data/\n" "falcot-data.desktop usr/share/applications/" #, fuzzy #| msgid "Our source package is now ready. All that's left to do is to generate the binary package, with the same method we used previously for rebuilding packages: we run the dpkg-buildpackage -us -uc command from within the falcot-data-1.0 directory." msgid "Our source package is now ready. All that is left to do is to generate the binary package, with the same method we used previously for rebuilding packages: we run the dpkg-buildpackage -us -uc command from within the falcot-data-1.0 directory." msgstr "Le paquet source est prêt ! Il ne reste plus qu'à générer le paquet binaire avec la commande déjà employée pour des recompilations de paquets : on se place dans le répertoire falcot-data-1.0 et on exécute dpkg-buildpackage -us -uc." msgid "Creating a Package Repository for APT" msgstr "Créer une archive de paquets pour APT" #, fuzzy #| msgid "packagetypes" msgid "packagearchive" msgstr "paquettypes" msgid "packageDebianarchive of" msgstr "paquetDebianarchive de" msgid "Falcot Corp gradually started maintaining a number of Debian packages either locally modified from existing packages or created from scratch to distribute internal data and programs." msgstr "Les administrateurs de Falcot SA maintiennent désormais un certain nombre de paquets Debian modifiés ou créés par eux et qui leur servent à diffuser des données et programmes internes." msgid "To make deployment easier, they want to integrate these packages in a package archive that can be directly used by APT. For obvious maintenance reasons, they wish to separate internal packages from locally-rebuilt packages. The goal is for the matching entries in a /etc/apt/sources.list.d/falcot.list file to be as follows:" msgstr "Pour faciliter leur déploiement, ils souhaitent les intégrer dans une archive de paquets directement utilisable par APT. Pour des raisons évidentes de maintenance, ils désirent y séparer les paquets internes des paquets officiels recompilés. Les entrées qui correspondraient à cette situation dans un fichier /etc/apt/sources.list.d/falcot.list seraient les suivantes :" #, fuzzy #| msgid "packagetypes" msgid "APT/etc/apt/sources.list.d/" msgstr "paquettypes" msgid "" "\n" "deb http://packages.falcot.com/ updates/\n" "deb http://packages.falcot.com/ internal/" msgstr "" "\n" "deb http://packages.falcot.com/ updates/\n" "deb http://packages.falcot.com/ internal/" msgid "mini-dinstall" msgstr "mini-dinstall" msgid "The administrators therefore configure a virtual host on their internal HTTP server, with /srv/vhosts/packages/ as the root of the associated web space. The management of the archive itself is delegated to the mini-dinstall command (in the similarly-named package). This tool keeps an eye on an incoming/ directory (in our case, /srv/vhosts/packages/mini-dinstall/incoming/) and waits for new packages there; when a package is uploaded, it is installed into a Debian archive at /srv/vhosts/packages/. The mini-dinstall command reads the *.changes file created when the Debian package is generated. These files contain a list of all other files associated with the version of the package (*.deb, *.dsc, *.diff.gz/*.debian.tar.gz, *.orig.tar.gz, or their equivalents with other compression tools), and these allow mini-dinstall to know which files to install. *.changes files also contain the name of the target distribution (often unstable) mentioned in the latest debian/changelog entry, and mini-dinstall uses this information to decide where the package should be installed. This is why administrators must always change this field before building a package, and set it to internal or updates, depending on the target location. mini-dinstall then generates the files required by APT, such as Packages.gz." msgstr "Les administrateurs configurent donc un hôte virtuel sur leur serveur HTTP interne. La racine de l'espace web associé est /srv/vhosts/packages/. Pour gérer ces archives, ils ont décidé d'employer le programme mini-dinstall (du paquet éponyme). Celui-ci scrute un répertoire d'arrivée incoming/ (en l'occurrence, il s'agira de /srv/vhosts/packages/mini-dinstall/incoming/) pour y récupérer tout paquet Debian déposé et l'installer dans une archive Debian (dont le répertoire est /srv/vhosts/packages/). Ce programme fonctionne en traitant les fichiers .changes créés lors de la génération d'un paquet Debian. Un tel fichier contient en effet la liste de tous les autres fichiers associés à cette version du paquet (.deb, .dsc, .diff.gz/debian.tar.gz, .orig.tar.gz ou fichiers équivalents utilisant d'autres outils de compression) et indique donc à mini-dinstall quels fichiers installer. Accessoirement, ce fichier reprend le nom de la distribution de destination (c'est souvent unstable) indiquée en tête du fichier debian/changelog, information utilisée par mini-dinstall pour décider de l'emplacement d'installation du paquet. C'est la raison pour laquelle les administrateurs doivent systématiquement modifier ce champ avant la génération d'un paquet et y placer internal ou updates, selon l'emplacement souhaité. mini-dinstall génère alors les fichiers indispensables au bon fonctionnement d'APT, par exemple Packages.gz." #, fuzzy #| msgid "ALTERNATIVE apt-ftparchive" msgid "ALTERNATIVE apt-ftparchive, aptly, and reprepro" msgstr "ALTERNATIVE apt-ftparchive" msgid "apt-ftparchive" msgstr "apt-ftparchive" msgid "If mini-dinstall seems too complex for your Debian archive needs, you can also use the apt-ftparchive command. This tool scans the contents of a directory and displays (on its standard output) a matching Packages file. In the Falcot Corp case, administrators could upload the packages directly into /srv/vhosts/packages/updates/ or /srv/vhosts/packages/internal/, then run the following commands to create the Packages.gz files:" msgstr "Si l'emploi de mini-dinstall semble trop complexe par rapport à vos besoins de création d'une archive Debian, il est possible d'utiliser directement le programme apt-ftparchive. Ce dernier inspecte le contenu d'un répertoire et affiche sur sa sortie standard le contenu du fichier Packages correspondant. Pour reprendre le cas de Falcot SA, les administrateurs pourraient directement déposer les paquets dans /srv/vhosts/packages/updates/ ou /srv/vhosts/packages/internal/ et exécuter les commandes suivantes pour créer les fichiers Packages.gz :" msgid "" "\n" "$ cd /srv/vhosts/packages\n" "$ apt-ftparchive packages updates >updates/Packages\n" "$ gzip updates/Packages\n" "$ apt-ftparchive packages internal >internal/Packages\n" "$ gzip internal/Packages" msgstr "" "\n" "$ cd /srv/vhosts/packages\n" "$ apt-ftparchive packages updates >updates/Packages\n" "$ gzip updates/Packages\n" "$ apt-ftparchive packages internal >internal/Packages\n" "$ gzip internal/Packages" msgid "The apt-ftparchive sources command allows creating Sources.gz files in a similar fashion." msgstr "La commande apt-ftparchive sources crée de manière similaire les fichiers Sources.gz." msgid "reprepro and aptly are more advanced tools for the same purpose. They can produce, manage and synchronize a number of package repositories, mirror other repositories, even cherry-pick packages from official repositories and provide them locally, create signatures of the generated package indices and thus provide signed repositories. reprepro stores packages and checksums in a Berkeley DB database file, so no database server is needed. aptly provides the same functionality, but it can be easier in handling. Unfortunately, both projects, although probably the most feature-rich solutions, are not actively developed at the moment." msgstr "" msgid "reprepro comes with a lot of documentation and examples in /usr/share/doc/reprepro/, while aptly has a vast online documentation. " msgstr "" #, fuzzy #| msgid "pbuilder" msgid "reprepro" msgstr "pbuilder" #, fuzzy #| msgid "dput" msgid "aptly" msgstr "dput" msgid "Configuring mini-dinstall requires setting up a ~/.mini-dinstall.conf file; in the Falcot Corp case, the contents are as follows:" msgstr "La configuration de mini-dinstall nécessite de mettre en place un fichier ~/.mini-dinstall.conf, que les administrateurs de Falcot SA ont renseigné comme suit :" msgid "" "\n" "[DEFAULT]\n" "archive_style = flat\n" "archivedir = /srv/vhosts/packages\n" "\n" "verify_sigs = 0\n" "mail_to = admin@falcot.com\n" "\n" "generate_release = 1\n" "release_origin = Falcot Corp\n" "release_codename = stable\n" "\n" "[updates]\n" "release_label = Recompiled Debian Packages\n" "\n" "[internal]\n" "release_label = Internal Packages" msgstr "" "\n" "[DEFAULT]\n" "archive_style = flat\n" "archivedir = /srv/vhosts/packages\n" "\n" "verify_sigs = 0\n" "mail_to = admin@falcot.com\n" "\n" "generate_release = 1\n" "release_origin = Falcot SA\n" "release_codename = stable\n" "\n" "[updates]\n" "release_label = Recompiled Debian Packages\n" "\n" "[internal]\n" "release_label = Internal Packages" msgid "One decision worth noting is the generation of Release files for each archive. This can help manage package installation priorities using the /etc/apt/preferences configuration file (see for details)." msgstr "Il est intéressant d'y remarquer la décision de générer des fichiers Release pour chacune des archives. Cela permettra éventuellement de gérer les priorités d'installation des paquets à l'aide du fichier de configuration /etc/apt/preferences (voir pour les détails)." msgid "SECURITY mini-dinstall and permissions" msgstr "SÉCURITÉ mini-dinstall et droits" #, fuzzy #| msgid "Since mini-dinstall has been designed to run as a regular user, there's no need to run it as root. The easiest way is to configure everything within the user account belonging to the administrator in charge of creating the Debian packages. Since only this administrator has the required permissions to put files in the incoming/ directory, we can deduce that the administrator authenticated the origin of each package prior to deployment and mini-dinstall does not need to do it again. This explains the verify_sigs = 0 parameter (which means that signatures need not be verified). However, if the contents of packages are sensitive, we can reverse the setting and elect to authenticate with a keyring containing the public keys of persons allowed to create packages (configured with the extra_keyrings parameter); mini-dinstall will then check the origin of each incoming package by analyzing the signature integrated to the *.changes file." msgid "Since mini-dinstall has been designed to run as a regular user, there is no need to run it as root. The easiest way is to configure everything within the user account belonging to the administrator in charge of creating the Debian packages. Since only this administrator has the required permissions to put files in the incoming/ directory, we can deduce that the administrator authenticated the origin of each package prior to deployment and mini-dinstall does not need to do it again. This explains the verify_sigs = 0 parameter (which means that signatures need not be verified). However, if the contents of packages are sensitive, we can reverse the setting and elect to authenticate with a keyring containing the public keys of persons allowed to create packages (configured with the extra_keyrings parameter); mini-dinstall will then check the origin of each incoming package by analyzing the signature integrated to the *.changes file." msgstr "mini-dinstall étant prévu pour fonctionner dans un compte utilisateur, il ne serait pas raisonnable de l'employer avec le compte root. La solution la plus simple est de tout configurer au sein du compte utilisateur de l'administrateur qui a la responsabilité de créer les paquets Debian. Étant donné que lui seul a le droit de déposer des fichiers dans le répertoire incoming/, il n'est pas nécessaire d'authentifier l'origine de chaque paquet à installer : on peut considérer que l'administrateur l'aura fait préalablement. Cela justifie le paramètre verify_sigs = 0 (pas de vérification des signatures). Toutefois, si le contenu des paquets est très sensible, il est possible de revenir sur ce choix et d'avoir un trousseau de clés publiques identifiant les personnes habilitées à créer des paquets (le paramètre extra_keyrings existe à cette fin) ; mini-dinstall vérifiera la provenance de chaque paquet déposé en analysant la signature intégrée au fichier .changes." msgid "Invoking mini-dinstall actually starts a daemon in the background. As long as this daemon runs, it will check for new packages in the incoming/ directory every half-hour; when a new package arrives, it will be moved to the archive and the appropriate Packages.gz and Sources.gz files will be regenerated. If running a daemon is a problem, mini-dinstall can also be manually invoked in batch mode (with the -b option) every time a package is uploaded into the incoming/ directory. Other possibilities provided by mini-dinstall are documented in its mini-dinstall 1 manual page." msgstr "L'exécution de mini-dinstall démarre en fait le démon en arrière-plan. Tant qu'il fonctionne, il vérifie toutes les demi-heures si un nouveau paquet est disponible dans le répertoire incoming/, le place dans l'archive et régénère les différents fichiers Packages.gz et Sources.gz. Si la présence d'un démon constitue un problème, il est possible de l'invoquer en mode non interactif (ou batch), à l'aide de l'option -b, à chaque fois qu'un paquet aura été déposé dans le répertoire incoming/. Découvrez les autres possibilités offertes par mini-dinstall en consultant sa page de manuel mini-dinstall1." msgid "EXTRA Generating a signed archive" msgstr "COMPLÉMENTS Générer une archive signée" msgid "The APT suite checks a chain of cryptographic signatures on the packages it handles before installing them, in order to ensure their authenticity (see ). Private APT archives can then be a problem, since the machines using them will keep displaying warnings about unsigned packages. A diligent administrator will therefore integrate private archives with the secure APT mechanism." msgstr "Les outils APT effectuent par défaut une vérification d'une chaîne de signatures cryptographiques apposées sur les paquets qu'ils manipulent, avant de les installer, dans le but de s'assurer de leur authenticité (voir la ). Les archives APT privées posent alors problème, car les machines qui doivent les utiliser vont sans arrêt afficher des messages d'avertissement pour signaler que les paquets que ces archives contiennent ne sont pas signés. Il est donc souvent judicieux de s'assurer que même les archives privées bénéficient du mécanisme secure APT." msgid "To help with this process, mini-dinstall includes a release_signscript configuration option that allows specifying a script to use for generating the signature. A good starting point is the sign-release.sh script provided by the mini-dinstall package in /usr/share/doc/mini-dinstall/examples/; local changes may be relevant." msgstr "mini-dinstall propose pour cela l'option de configuration release_signscript, qui permet de spécifier un script à utiliser pour générer la signature. On pourra par exemple utiliser le script sign-release.sh fourni par le paquet mini-dinstall dans /usr/share/doc/mini-dinstall/examples/, après l'avoir éventuellement adapté aux besoins locaux." msgid "Becoming a Package Maintainer" msgstr "Devenir mainteneur de paquet" #, fuzzy #| msgid "packagetypes" msgid "packagemaintainer" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid "packagenew maintainer" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid "maintainerpackage maintainer" msgstr "paquettypes" msgid "Learning to Make Packages" msgstr "Apprendre à faire des paquets" #, fuzzy #| msgid "packagetypes" msgid "packagecreation" msgstr "paquettypes" #, fuzzy #| msgid "Creating a quality Debian package is not always a simple task, and becoming a package maintainer takes some learning, both with theory and practice. It's not a simple matter of building and installing software; rather, the bulk of the complexity comes from understanding the problems and conflicts, and more generally the interactions, with the myriad of other packages available." msgid "Creating a quality Debian package is not always a simple task, and becoming a package maintainer takes some learning, both with theory and practice in technical and legal matters. It is not a simple matter of building and installing software; rather, the bulk of the complexity comes from understanding the problems and conflicts, and more generally the interactions, with the myriad of other packages available." msgstr "Construire un paquet Debian de qualité n'est pas chose facile et on ne s'improvise pas responsable de paquet. C'est une activité qui s'apprend par la pratique et par la théorie. Elle ne se limite pas à compiler et installer un logiciel. Elle implique surtout de maîtriser les problèmes, conflits et interactions qui se produiront avec les milliers d'autres paquets logiciels." msgid "Rules" msgstr "Les règles" #, fuzzy #| msgid "packagetypes" msgid "packagepolicy" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid "DebianPolicy" msgstr "paquettypes" msgid "controlStandards-Version, header field" msgstr "" #, fuzzy #| msgid "A Debian package must comply with the precise rules compiled in the Debian policy, and each package maintainer must know them. There is no requirement to know them by heart, but rather to know they exist and to refer to them whenever a choice presents a non-trivial alternative. Every Debian maintainer has made mistakes by not knowing about a rule, but this is not a huge problem as long as the error gets fixed when a user reports it as a bug report (which tends to happen fairly soon thanks to advanced users). " msgid "A Debian package must comply with the precise rules compiled in the Debian policy, and each package maintainer must know them. There is no requirement to know them by heart, but rather to know they exist and to refer to them whenever a choice presents a non-trivial alternative. Every Debian maintainer has made mistakes by not knowing about a rule, but this is not a huge problem as long as the error gets fixed when a user reports it as a bug report (which tends to happen fairly soon thanks to advanced users). The Standards-Version field in debian/control specifies the version of the Debian policy with which a package complies. Maintainers should comply to the latest version of the Debian policy. " msgstr "Un paquet Debian est conforme aux règles précises édictées dans la charte Debian. Chaque responsable de paquet se doit de les connaître. Il ne s'agit pas de les réciter par cœur, mais de savoir qu'elles existent et de s'y référer lorsque l'on n'est pas sûr de son choix. Tout mainteneur Debian officiel a déjà commis des erreurs en ignorant l'existence d'une règle, mais ce n'est pas dramatique : un utilisateur avancé de ses paquets finit tôt ou tard par signaler cette négligence sous la forme d'un rapport de bogue. " msgid "Procedures" msgstr "Les procédures" #, fuzzy #| msgid "packagetypes" msgid "DebianDeveloper's Reference" msgstr "paquettypes" #, fuzzy #| msgid "packagetypes" msgid "packagedeveloper's reference" msgstr "paquettypes" msgid "Debian is not a simple collection of individual packages. Everyone's packaging work is part of a collective project; being a Debian developer involves knowing how the Debian project operates as a whole. Every developer will, sooner or later, interact with others. The Debian Developer's Reference (in the developers-reference package) summarizes what every developer must know in order to interact as smoothly as possible with the various teams within the project, and to take the best possible advantages of the available resources. This document also enumerates a number of duties a developer is expected to fulfill. " msgstr "Debian n'est pas une collection de paquets réalisés individuellement. Le travail de chacun s'inscrit dans un projet collectif et, à ce titre, on ne peut être développeur Debian et ignorer le fonctionnement global de la distribution. Tôt ou tard, chaque développeur doit interagir avec d'autres volontaires. La référence du développeur Debian (paquet developers-reference-fr) reprend tout ce qu'il faut savoir pour interagir au mieux avec les différentes équipes du projet et profiter au maximum des ressources mises à disposition. Ce document précise également un certain nombre de devoirs que chaque développeur se doit de remplir. " msgid "Tools" msgstr "Les outils" msgid "Many tools help package maintainers in their work. This section describes them quickly, but does not give the full details, since they all have comprehensive documentation of their own." msgstr "Toute une panoplie d'outils aide les responsables de paquets dans leur travail. Ce chapitre les décrit rapidement sans détailler leur emploi, car ils sont tous bien documentés." #, fuzzy #| msgid "packagetypes" msgid "packagetools" msgstr "paquettypes" msgid "devscripts" msgstr "devscripts" msgid "dch" msgstr "dch" msgid "uscan" msgstr "uscan" msgid "debi" msgstr "debi" msgid "debc" msgstr "debc" #, fuzzy #| msgid "debi" msgid "bts" msgstr "debi" msgid "The devscripts package contains many programs helping with a wide array of a Debian developer's job:" msgstr "Le paquet devscripts contient de nombreux programmes couvrant bien des aspects du travail d'un développeur Debian :" msgid "debuild allows generating a package (with dpkg-buildpackage) and running lintian to check its compliance with the Debian policy afterwards." msgstr "debuild sert à générer un paquet (dpkg-buildpackage) et à vérifier dans la foulée s'il est conforme à la charte Debian (lintian)." msgid "debclean cleans a source package after a binary package has been generated." msgstr "debclean nettoie un paquet source après la génération d'un paquet binaire." msgid "dch allows quick and easy editing of a debian/changelog file in a source package." msgstr "dch permet d'éditer facilement un fichier debian/changelog dans un paquet source." msgid "uscan checks whether a new version of a software has been released by the upstream author; this requires a debian/watch file with a description of the location of such releases." msgstr "uscan vérifie si l'auteur amont a publié une nouvelle version de son logiciel. Ce programme nécessite un fichier debian/watch décrivant l'emplacement de publication de ces archives." msgid "debian, directorywatch" msgstr "" msgid "debi allows installing (with dpkg -i) the Debian package that was just generated without the need to type its full name and path." msgstr "debi installe (dpkg -i) le paquet Debian qui vient d'être généré (sans devoir saisir son nom complet)." msgid "In a similar fashion, debc allows scanning the contents of the recently-generated package (with dpkg -c), without needing to type its full name and path." msgstr "debc sert à consulter le contenu (dpkg -c) du paquet qui vient d'être généré (sans devoir saisir son nom complet)." #, fuzzy #| msgid "bts controls the bug tracking system from the command line; this program automatically generates the appropriate emails." msgid "bts controls the bug tracking system from the command line; this program automatically generates the appropriate emails. " msgstr "bts manipule le système de suivi de bogues depuis la ligne de commande ; ce programme génère automatiquement les courriers électroniques adéquats." msgid "debrelease uploads a recently-generated package to a remote server, without needing to type the full name and path of the related .changes file." msgstr "debrelease envoie la nouvelle version du paquet sur un serveur distant sans devoir saisir le nom complet du fichier .changes concerné." #, fuzzy #| msgid "Makefile" msgid ".changes" msgstr "Makefile" msgid "debsign signs the *.dsc and *.changes files." msgstr "debsign signe les fichiers .dsc et .changes." msgid "uupdate automates the creation of a new revision of a package when a new upstream version has been released." msgstr "uupdate crée automatiquement une nouvelle révision du paquet lors de la publication d'une nouvelle version amont." msgid "All of the mentioned commands are documented in their respective manual pages. They can further be configured per user in one file: ~/.devscripts." msgstr "" msgid "debhelper and dh-make" msgstr "debhelper et dh-make" msgid "debhelper" msgstr "debhelper" msgid "dh-make" msgstr "dh-make" #, fuzzy #| msgid "dch" msgid "dh" msgstr "dch" #, fuzzy #| msgid "packagetypes" msgid "debianrules" msgstr "paquettypes" #, fuzzy #| msgid "Debhelper is a set of scripts easing the creation of policy-compliant packages; these scripts are invoked from debian/rules. Debhelper has been widely adopted within Debian, as evidenced by the fact that it is used by the majority of official Debian packages. All the commands it contains have a dh_ prefix." msgid "Debhelper is a set of scripts easing the creation of policy-compliant packages; these scripts are invoked from debian/rules. Debhelper has been widely adopted within Debian, as evidenced by the fact that it is used by the majority of official Debian packages. All the commands it contains have a dh_ prefix. Each of them is documented in a manual page. The different compatibility levels and common options are described in debhelper 7." msgstr "debhelper est un ensemble de scripts facilitant la création d'un paquet conforme à la charte Debian, invoqués depuis debian/rules. Il a conquis de très nombreux développeurs Debian ; pour preuve, la majorité des paquets officiels l'utilisent. Tous les scripts sont préfixés par dh_." msgid "The dh_make script (in the dh-make package) creates files required for generating a Debian package in a directory initially containing the sources for a piece of software. As can be guessed from the name of the program, the generated files use debhelper by default." msgstr "Le script dh_make (du paquet dh-make) intègre les fichiers nécessaires à la génération d'un paquet Debian dans un répertoire contenant les sources d'un logiciel. Les fichiers qu'il ajoute utilisent debhelper de manière standard, comme son nom le laisse supposer." #, fuzzy #| msgid "The lintian Program" msgid "lintian" msgstr "Le programme lintian" msgid "lintian" msgstr "lintian" #, fuzzy #| msgid "packagetypes" msgid "packagechecker" msgstr "paquettypes" #, fuzzy #| msgid "This tool is one of the most important: it's the Debian package checker. It is based on a large array of tests created from the Debian policy, and detects quickly and automatically many errors that can then be fixed before packages are released." msgid "This tool is one of the most important: it is the Debian package checker. It is based on a large array of tests created from the Debian policy, and detects quickly and automatically many errors that can then be fixed before packages are released." msgstr "Ce programme fait partie des outils les plus importants : c'est le vérificateur de paquets Debian. Il dispose d'une vaste batterie de tests créés en fonction de la charte Debian. Il permet de trouver rapidement et automatiquement de nombreuses erreurs et donc de les corriger avant de publier les paquets." msgid "This tool is only a helper, and it sometimes gets it wrong (for instance, since the Debian policy changes over time, lintian is sometimes outdated). It is also not exhaustive: not getting any Lintian error should not be interpreted as a proof that the package is perfect; at most, it avoids the most common errors." msgstr "Cet outil ne fournit qu'une aide et il arrive qu'il se trompe (la charte Debian évolue parfois, lintian peut alors être momentanément en retard). Par ailleurs, il n'est pas exhaustif : qu'il ne signale aucune erreur ne signifie pas qu'un paquet est parfait, tout au plus qu'il évite les erreurs les plus communes." #, fuzzy #| msgid "The piuparts Program" msgid "piuparts" msgstr "Le programme piuparts" msgid "piuparts" msgstr "piuparts" msgid "This is another important tool: it automates the installation, upgrade, removal and purge of a package (in an isolated environment), and checks that none of these operations leads to an error. It can help in detecting missing dependencies, and it also detects when files are incorrectly left over after the package got purged." msgstr "Il s'agit d'un autre outil important : il automatise l'installation, la mise à jour, la suppression et la purge d'un paquet (dans un environnement isolé) et vérifie qu'aucune de ces opérations n'entraîne d'erreur. Il peut aider à détecter les dépendances manquantes et détecte également lorsque des fichiers subsistent de manière inattendue après que le paquet a été purgé." #, fuzzy #| msgid "devscripts" msgid "autopkgtest" msgstr "devscripts" msgid "autopkgtest" msgstr "autopkgtest" #, fuzzy #| msgid "packagetypes" msgid "packagetests" msgstr "paquettypes" msgid "autopkgtest runs tests on binary packages, using the tests supplied in the source package in debian/tests/. Several commands allow the easy creation of chrooted or virtual test environments." msgstr "" #, fuzzy #| msgid "devscripts" msgid "reprotest" msgstr "devscripts" msgid "reprotest" msgstr "reprotest" msgid "reprotest builds the same source code twice in different environments, and then checks the binaries produced by each build for differences. If any are found, then diffoscope (if unavailable, diff) is used to display them in detail for later analysis." msgstr "" #, fuzzy #| msgid "dch" msgid "diffoscope" msgstr "dch" msgid "dupload and dput" msgstr "dupload et dput" msgid "dupload" msgstr "dupload" msgid "dput" msgstr "dput" #, fuzzy #| msgid "The dupload and dput commands allow uploading a Debian package to a (possibly remote) server. This allows developers to publish their package on the main Debian server (ftp-master.debian.org) so that it can be integrated to the archive and distributed by mirrors. These commands take a *.changes file as a parameter, and deduce the other relevant files from its contents." msgid "The dupload and dput commands allow uploading a Debian package to a (possibly remote) server. This allows developers to publish their package on the main Debian server (ftp-master.debian.org) so that it can be integrated to the archive and distributed by mirrors. These commands take a .changes file as a parameter, and deduce the other relevant files from its contents." msgstr "dupload et dput servent à envoyer une nouvelle version d'un paquet Debian sur un serveur local ou distant. C'est ainsi que les développeurs envoient leur paquet sur le serveur principal de Debian (ftp-master.debian.org) pour qu'il soit intégré à l'archive et distribué par les miroirs. Ces commandes prennent en paramètre un fichier .changes et en déduisent les autres fichiers à envoyer." #, fuzzy #| msgid "debhelper and dh-make" msgid "git-buildpackage and dgit" msgstr "debhelper et dh-make" #, fuzzy #| msgid "devscripts" msgid "git-buildpackage" msgstr "devscripts" #, fuzzy #| msgid "devscripts" msgid "dgit" msgstr "devscripts" msgid "The project has been using various version control systems over the years to store packaging efforts or package source code, or allow collaborative package maintenance. In an effort to unify the systems and efforts, it was ultimately decided in 2017 to move (almost) all package sources into Git () onto a Gitlab instance called salsa.debian.org. " msgstr "" #, fuzzy #| msgid "Build-Depends, control field" msgid "salsa.debian.org" msgstr "Build-Depends, champ d'en-tête du paquet source" msgid "To make packaging using Git easier for Debian developers, tools have been developed. These allow not only to store the packaging files in Git, but also to use the Git repositories (and their history) of software projects, put patches applied to package sources into Git history, maintain software versions per distribution, etc." msgstr "" msgid "One of the most famous packages is git-buildpackage. An alternative is dgit. Of course it is still possible to use neither of those." msgstr "" msgid "Below is an example for a ~/.gbp.conf configuration file" msgstr "" msgid "" "" msgstr "" msgid "Building the package is then as easy as running gbp buildpackage in the Git tree. It will start a package build in a Debian Bullseye chroot using sbuild. When the build succeeds, the created files are checked running the autopkgtest-testsuite (if defined). All the various options are explained in gbp.conf 5 and /etc/git-buildpackage/gbp.conf." msgstr "" #, fuzzy #| msgid "debi" msgid "gbp" msgstr "debi" msgid "/etc/etc/git-buildpackage/gbp.conf" msgstr "" msgid "All the tools mentioned so far have been included in the continuous integration (CI) process in the salsa.debian.org instance as well: " msgstr "" msgid "Acceptance Process" msgstr "Processus d'acceptation" #, fuzzy #| msgid "packagetypes" msgid "DebianDeveloper" msgstr "paquettypes" #, fuzzy #| msgid "Build-Depends, control field" msgid "nm.debian.org" msgstr "Build-Depends, champ d'en-tête du paquet source" msgid "Becoming a “Debian developer” is not a simple administrative matter. The process comprises several steps, and is as much an initiation as it is a selection process. In any case, it is formalized and well-documented, so anyone can track their progression on the website dedicated to the new member process. " msgstr "Ne devient pas développeur Debian qui veut. Différentes étapes jalonnent le processus d'acceptation, qui se veut autant un parcours initiatique qu'une sélection. Ce processus est formalisé et chacun peut suivre sa progression sur le site web des nouveaux mainteneurs (nm est l'abréviation de New Maintainer). " msgid "EXTRA Lightweight process for “Debian Maintainers”" msgstr "COMPLÉMENTS Processus allégé pour les « Mainteneurs Debian »" #, fuzzy #| msgid "packagetypes" msgid "DebianMaintainer" msgstr "paquettypes" msgid "“Debian Maintainer” is another status that gives less privileges than “Debian developer” but whose associated process is quicker. With this status, the contributors can maintain their own packages only. A Debian developer only needs to perform a check on an initial upload, and issue a statement to the effect that they trust the prospective maintainer with the ability to maintain the package on their own." msgstr "Un statut de « Mainteneur Debian » (Debian Maintainer, DM) a été introduit. Le processus associé est plus léger et les droits que ce statut accorde se restreignent à pouvoir maintenir ses propres paquets. Il suffit qu'un développeur Debian vérifie préalablement tout nouveau paquet et qu'il indique qu'il considère le mainteneur capable de gérer son paquet tout seul." msgid "Prerequisites" msgstr "Prérequis" msgid "All candidates are expected to have at least a working knowledge of the English language. This is required at all levels: for the initial communications with the examiner, of course, but also later, since English is the preferred language for most of the documentation; also, package users will be communicating in English when reporting bugs, and they will expect replies in English." msgstr "Il est demandé à tous les candidats de maîtriser un minimum l'anglais. Cela est nécessaire à tous les niveaux : dans un premier temps pour communiquer avec l'examinateur, mais c'est aussi la langue de prédilection pour une grande partie de la documentation. De plus, les utilisateurs de vos paquets communiqueront avec vous en anglais pour vous signaler des bogues et il faudra être capable de leur répondre." msgid "The other prerequisite deals with motivation. Becoming a Debian developer is a process that only makes sense if the candidate knows that their interest in Debian will last for many months. The acceptance process itself may last for several months, and Debian needs developers for the long haul; each package needs permanent maintenance, and not just an initial upload." msgstr "Le deuxième prérequis porte sur la motivation. Il faut être pleinement conscient que la démarche consistant à devenir développeur Debian n'a de sens que si vous savez par avance que Debian restera un sujet d'intérêt pendant de nombreux mois. En effet, la procédure en elle-même dure plusieurs mois et Debian a besoin de mainteneurs qui s'inscrivent dans la durée, car chaque paquet a besoin d'un mainteneur en permanence (et pas seulement lorsqu'il est créé)." msgid "Registration" msgstr "Inscription" #, fuzzy #| msgid "packagetypes" msgid "packagesponsor" msgstr "paquettypes" msgid "The first (real) step consists in finding a sponsor or advocate; this means an official developer willing to state that they believe that accepting X would be a good thing for Debian. This usually implies that the candidate has already been active within the community, and that their work has been appreciated. If the candidate is shy and their work is not publicly touted, they can try to convince a Debian developer to advocate them by showing their work in a private way." msgstr "La première étape (réelle) consiste à trouver un sponsor, ou avocat (advocate) ; c'est un développeur officiel qui affirme « je pense que l'acceptation de X serait une bonne chose pour Debian ». Cela implique normalement que le candidat ait déjà été actif au sein de la communauté et que quelqu'un ait apprécié son travail. Si le candidat est timide et n'affiche pas en public le fruit de son travail, il peut tenter de convaincre individuellement un développeur Debian officiel de le soutenir en lui présentant ses travaux en privé." msgid "key pair" msgstr "biclé" msgid "At the same time, the candidate must generate a public/private RSA key pair with GnuPG, which should be signed by at least two official Debian developers. The signature authenticates the name on the key. Effectively, during a key signing party, each participant must show an official identification (usually an ID card or passport) together with their key identifiers. This step confirms the link between the human and the keys. This signature thus requires meeting in real life. If you have not yet met any Debian developers in a public free software conference, you can explicitly seek developers living nearby using the list on the following webpage as a starting point. " msgstr "En parallèle, le candidat doit se générer une biclé (paire publique-privée) RSA avec GnuPG, qu'il doit faire signer par au moins deux développeurs Debian officiels. La signature certifie l'authenticité du nom présent sur la clé. En effet, lors d'une séance de signature de clés, il est d'usage de présenter des papiers d'identité (habituellement une carte d'identité ou un passeport) et les identifiants de ses clés pour officialiser la correspondance entre la personne physique et les clés. Cette signature nécessite donc une rencontre réelle ; si vous n'avez pas encore eu l'occasion de croiser un développeur Debian lors d'une manifestation de logiciels libres, il est possible de solliciter expressément les développeurs en demandant qui serait dans la région concernée par le biais de la liste de diffusion debian-devel-french@lists.debian.org. Il existe également une liste de personnes disponibles pour signer des clés, organisée par pays et par ville. " msgid "Once the registration on nm.debian.org has been validated by the advocate, an Application Manager is assigned to the candidate. The application manager will then drive the process through multiple pre-defined steps and checks." msgstr "Une fois l'inscription sur nm.debian.org validée par le sponsor, un Application Manager (« gestionnaire de candidature ») sera chargé de suivre le candidat dans ses démarches et de réaliser les différentes vérifications prévues dans le processus." msgid "The first verification is an identity check. If you already have a key signed by two Debian developers, this step is easy; otherwise, the application manager will try and guide you in your search for Debian developers close by to organize a meet-up and a key signing." msgstr "La première vérification est celle de l'identité. Si vous avez une clé signée par un développeur Debian, cette étape est facile. Dans le cas contraire, l'Application Manager essaiera de guider le candidat dans sa recherche de développeurs Debian à proximité de chez lui pour qu'une rencontre et une signature de clés puissent être arrangées." msgid "Accepting the Principles" msgstr "Acceptation des principes" msgid "These administrative formalities are followed by philosophical considerations. The point is to make sure that the candidate understands and accepts the social contract and the principles behind Free Software. Joining Debian is only possible if one shares the values that unite the current developers, as expressed in the founding texts (and summarized in )." msgstr "Ces formalités administratives sont suivies de considérations philosophiques. Il est question de s'assurer que le candidat comprend le contrat social et les principes du logiciel libre. En effet, il n'est pas possible de rejoindre Debian si l'on ne partage pas les valeurs qui unissent les développeurs actuels, exprimées dans les deux textes fondateurs (et résumées au )." msgid "In addition, each candidate wishing to join the Debian ranks is expected to know the workings of the project, and how to interact appropriately to solve the problems they will doubtless encounter as time passes. All of this information is generally documented in manuals targeting the new maintainers, and in the Debian developer's reference. An attentive reading of this document should be enough to answer the examiner's questions. If the answers are not satisfactory, the candidate will be informed. They will then have to read (again) the relevant documentation before trying again. In the cases where the existing documentation does not contain the appropriate answer for the question, the candidate can usually reach an answer with some practical experience within Debian, or potentially by discussing with other Debian developers. This mechanism ensures that candidates get involved somewhat in Debian before becoming a full part of it. It is a deliberate policy, by which candidates who eventually join the project are integrated as another piece of an infinitely extensible jigsaw puzzle." msgstr "En plus de cela, il est souhaité que chaque personne qui rejoint les rangs de Debian connaisse déjà son fonctionnement et sache interagir comme il se doit pour résoudre les problèmes qu'elle rencontrera au fil du temps. Toutes ces informations sont généralement documentées dans les divers manuels ciblant les nouveaux mainteneurs, mais aussi et surtout dans le guide de référence du développeur Debian. Une lecture attentive de ce document devrait suffire pour répondre aux questions de l'examinateur. Si les réponses ne sont pas satisfaisantes, il le fera savoir et invitera le candidat à se documenter davantage avant de retenter sa chance. Si la documentation ne semble pas répondre à la question, c'est qu'un peu de pratique au sein de Debian permet de découvrir la réponse par soi-même (éventuellement en discutant avec d'autres développeurs Debian). Ce mécanisme entraîne les gens dans les rouages de Debian avant de pouvoir totalement prendre part au projet. C'est une politique volontaire et les gens qui arrivent finalement à rejoindre le projet s'intègrent comme une pièce supplémentaire d'un puzzle extensible à l'infini." msgid "This step is usually known as the Philosophy & Procedures (P&P for short) in the lingo of the developers involved in the new member process." msgstr "Cette étape est couramment désignée par le terme de Philosophy & Procedures (P&P) dans le jargon des personnes impliquées dans le processus d'acceptation de nouveaux mainteneurs." msgid "Philosophy & Procedures" msgstr "Philosophy & Procedures" msgid "Checking Skills" msgstr "Vérification des compétences" msgid "Each application to become an official Debian developer must be justified. Becoming a project member requires showing that this status is legitimate, and that it facilitates the candidate's job in helping Debian. The most common justification is that being granted Debian developer status eases maintenance of a Debian package, but it is not the only one. Some developers join the project to contribute to porting to a specific architecture, others want to improve documentation, and so on." msgstr "Chaque demande pour devenir développeur Debian officiel doit être justifiée. En effet, on ne devient membre que si l'on peut démontrer que ce statut est légitime et qu'il permettra de faciliter le travail du candidat. La justification habituelle est que le statut de développeur Debian facilite la maintenance d'un paquet Debian, mais elle n'est pas universelle. Certains développeurs rejoignent le projet pour contribuer à un portage sur une architecture, d'autres pour contribuer à la documentation, etc." msgid "This step represents the opportunity for the candidate to state what they intend to do within the Debian project and to show what they have already done towards that end. Debian is a pragmatic project and saying something is not enough, if the actions do not match what is announced. Generally, when the intended role within the project is related to package maintenance, a first version of the prospective package will have to be validated technically and uploaded to the Debian servers by a sponsor among the existing Debian developers." msgstr "Cette étape est donc l'occasion pour chaque candidat d'affirmer ce qu'il a l'intention de réaliser dans le cadre de Debian et de montrer ce qu'il a déjà fait dans ce sens. Debian privilégie en effet le pragmatisme et il ne suffit pas de dire quelque chose pour le faire prendre en compte : il faut montrer sa capacité à faire ce qui a été annoncé. En général, lorsqu'il s'agit de mise en paquet, il faudra montrer une première version du paquet et trouver un parrain (parmi les développeurs officiels) qui contrôle sa réalisation technique et l'envoie sur le serveur principal de Debian." msgid "COMMUNITY Sponsoring" msgstr "COMMUNAUTÉ Parrainage" # TODO: INTEGRATE ALTERNATE STRING: sponsoring msgid "sponsoring" msgstr "parrainage" #, fuzzy #| msgid "packagetypes" msgid "DebianNew Member" msgstr "paquettypes" msgid "Debian developers can “sponsor” packages prepared by someone else, meaning that they publish them in the official Debian repositories after having performed a careful review. This mechanism enables external persons, who have not yet gone through the new member process, to contribute occasionally to the project. At the same time, it ensures that all packages included in Debian have always been checked by an official member." msgstr "Le parrainage (ou sponsoring) est un mécanisme par lequel un développeur Debian ou un mainteneur Debian vérifie un paquet préparé par quelqu'un d'autre et y appose sa signature pour le publier dans les dépôts officiels. Il permet ainsi à des personnes externes au projet, n'ayant pas suivi la procédure des nouveaux mainteneurs, de contribuer ponctuellement au projet, tout en garantissant que les paquets réellement inclus dans Debian ont toujours subi une vérification par un membre officiel." #, fuzzy #| msgid "Finally, the examiner checks the candidate's technical (packaging) skills with a detailed questionnaire. Bad answers are not permitted, but the answer time is not limited. All the documentation is available and several tries are allowed if the first answers are not satisfactory. This step does not intend to discriminate, but to ensure at least a modicum of knowledge common to new contributors." msgid "Finally, the examiner checks the candidate's technical (packaging) skills with a detailed questionnaire. Bad answers are not permitted, but the answer time is not limited. All the documentation is available and several attempts are allowed if the first answers are not satisfactory. This step does not intend to discriminate, but to ensure at least a modicum of knowledge common to new contributors." msgstr "Enfin, l'examinateur vérifiera les compétences techniques du candidat en matière de mise en paquet grâce à un questionnaire assez étoffé. Une erreur bloque le processus (sans l'interrompre définitivement), mais le temps pour répondre n'est pas limité, toute la documentation est disponible et il est possible d'essayer plusieurs fois en cas d'erreur. Le questionnaire ne se veut pas discriminatoire mais a pour seul objectif de garantir un niveau minimum de connaissances aux nouveaux contributeurs." msgid "This step is known as the Tasks & Skills step (T&S for short) in the examiners' jargon." msgstr "Cette étape se nomme Tasks & Skills (T&S en abrégé) dans le jargon des examinateurs." msgid "Tasks & Skills" msgstr "Tasks & Skills" msgid "Final Approval" msgstr "Approbation finale" #, fuzzy #| msgid "key pair" msgid "DAM" msgstr "biclé" #, fuzzy #| msgid "packagetypes" msgid "DebianAccount ManagersDAM" msgstr "paquettypes" msgid "At the very last step, the whole process is reviewed by a DAM (Debian Account Manager). The DAM will review all the information about the candidate that the examiner collected, and makes the decision on whether or not to create an account on the Debian servers. In cases where extra information is required, the account creation may be delayed. Refusals are rather rare if the examiner does a good job of following the process, but they sometimes happen. They are never permanent, and the candidate is free to try again at a later time." msgstr "La toute dernière étape est la validation du parcours par un DAM (Debian Account Manager, ou gestionnaire des comptes Debian). Il consulte les informations fournies à propos du candidat par l'examinateur et prend la décision de lui créer ou non un compte sur les serveurs Debian. Parfois, il temporisera cette création dans l'attente d'informations supplémentaires s'il le juge nécessaire. Les refus sont assez rares si l'examinateur a bien fait son travail d'encadrement, mais ils se produisent parfois. Ils ne sont jamais définitifs et le candidat est libre de retenter sa chance ultérieurement." msgid "The DAM's decision is authoritative and (almost) without appeal, which explains why the people in that seat have often been criticized in the past." msgstr "La décision du DAM est souveraine et quasiment incontestable. C'est pourquoi les responsables concernés ont souvent été la cible de critiques par le passé." #, fuzzy #~| msgid "The copyright file must contain information about the authors of the documents included in the package, and the related license. In our case, these are internal documents and their use is restricted to within the Falcot Corp company. The default changelog file is generally appropriate; replacing the “Initial release” with a more verbose explanation and changing the distribution from unstable to internal is enough. The control file was also updated: the Section field has been changed to misc and the Homepage, Vcs-Git and Vcs-Browser fields were removed. The Depends fields was completed with iceweasel | www-browser so as to ensure the availability of a web browser able to display the documents in the package." #~ msgid "The copyright file must contain information about the authors of the documents included in the package, and the related license. In our case, these are internal documents and their use is restricted to within the Falcot Corp company. The default changelog file is generally appropriate; replacing the “Initial release” with a more verbose explanation and changing the distribution from unstable to internal is enough. The control file was also updated: the Section field has been changed to misc and the Homepage, Vcs-Git and Vcs-Browser fields were removed. The Depends fields was completed with firefox-esr | www-browser so as to ensure the availability of a web browser able to display the documents in the package." #~ msgstr "Il faut mentionner dans le fichier copyright les auteurs des documents inclus dans le paquet et la licence logicielle associée. En l'occurrence, il s'agit de documents internes dont l'usage est limité à la société Falcot. Le fichier changelog par défaut convient relativement bien, et l'administrateur s'est contenté d'écrire une explication un peu plus longue que Initial release (« version initiale ») et de modifier la distribution unstable en internal. Le fichier control a lui aussi changé : le champ Section a désormais pour valeur misc et les champs Homepage, Vcs-Git et Vcs-Browser ont été supprimés. Le champ Depends a été complété par iceweasel | www-browser pour garantir la présence d'un navigateur web capable de consulter les documents ainsi diffusés." #~ msgid "package archive" #~ msgstr "archive de paquets" #~ msgid "Debian Developer's Reference" #~ msgstr "référence du développeur Debian" #~ msgid "QUICK LOOK pbuilder" #~ msgstr "DÉCOUVERTE pbuilder" #~ msgid "" #~ "\n" #~ "This work was packaged for Debian by Raphael Hertzog <hertzog@debian.org>\n" #~ "on Mon, 11 Apr 2011 20:46:33 +0200\n" #~ "\n" #~ "Copyright:\n" #~ "\n" #~ " Copyright (C) 2004-2011 Falcot Corp\n" #~ "\n" #~ "License:\n" #~ "\n" #~ " All rights reserved." #~ msgstr "" #~ "\n" #~ "This work was packaged for Debian by:\n" #~ "\n" #~ " Raphael Hertzog <hertzog@debian.org> on Mon, 11 Apr 2011 20:46:33 +0200\n" #~ "\n" #~ "Copyright:\n" #~ "\n" #~ " Copyright (C) 2004-2011 Falcot SA\n" #~ "\n" #~ "License:\n" #~ "\n" #~ " All rights reserved.\n" #~ msgid "The menu file" #~ msgstr "Le fichier menu" #~ msgid "" #~ "\n" #~ "?package(falcot-data):needs=X11|wm section=Help\\\n" #~ " title=\"Internal Falcot Corp Documentation\" \\\n" #~ " command=\"/usr/bin/x-www-browser /usr/share/falcot-data/index.html\"\n" #~ "?package(falcot-data):needs=text section=Help\\\n" #~ " title=\"Internal Falcot Corp Documentation\" \\\n" #~ " command=\"/usr/bin/www-browser /usr/share/falcot-data/index.html\"" #~ msgstr "" #~ "\n" #~ "?package(falcot-data):needs=X11|wm section=Help\\\n" #~ " title=\"Documentation interne à Falcot SA\" \\\n" #~ " command=\"/usr/bin/x-www-browser /usr/share/falcot-data/index.html\"\n" #~ "?package(falcot-data):needs=text section=Help\\\n" #~ " title=\"Documentation interne à Falcot SA\" \\\n" #~ " command=\"/usr/bin/www-browser /usr/share/falcot-data/index.html\"\n" #~ msgid "The needs field, when set to X11|wm indicates that this entry only makes sense in a graphical interface. It will therefore only be integrated into the menus of the graphical (X11) applications and window managers (hence the wm). The section field states where in the menu the entry should be displayed. In our case, the entry will be in the Help menu. The title field contains the text that will be displayed in the menu. Finally, the command field describes the command to run when the user selects the menu entry." #~ msgstr "Le champ needs positionné à X11|wm indique que cette entrée de menu n'a de sens que dans l'interface graphique. Elle sera donc intégrée uniquement dans les menus des applications graphiques (ou X11) et les gestionnaires de fenêtres (wm est en effet l'abréviation de window manager). Le champ section précise l'emplacement de l'entrée dans le menu. Dans notre cas, elle sera intégrée au sous-menu d'aide Help. Le champ title (titre) est le texte que les utilisateurs verront dans le menu. Enfin, le champ command décrit la commande à exécuter lorsqu'un utilisateur sélectionne cet élément de menu." #~ msgid "The second entry matches the first one, with slight adaptations adapted to the Linux console text mode." #~ msgstr "La deuxième entrée est le pendant de la première, mais adaptée au mode texte d'une console Linux." #~ msgid "DEBIAN POLICY Menu organization" #~ msgstr "CHARTE DEBIAN L'organisation des menus" #~ msgid "The Debian menus are organized in a formal structure, documented in the following text: " #~ msgstr "L'organisation des menus Debian suit une structure précise, documentée dans le texte suivant : " #~ msgid "The section in a menu file should be picked from the list mentioned in this document." #~ msgstr "Il est recommandé de choisir une section listée dans ce document pour remplir le champ section d'un fichier menu." #~ msgid "Simply creating the debian/menu file is enough to enable the menu in the package, since the dh_installmenu command is automatically invoked by dh during the package build process." #~ msgstr "La simple création du fichier debian/menu est suffisante pour activer le menu dans le paquet généré car le programme dh_installmenu est automatiquement appelé par dh au cours de la fabrication du paquet." #~ msgid "Hess, Joey" #~ msgstr "Hess, Joey" #~ msgid "ALTERNATIVE CDBS" #~ msgstr "ALTERNATIVE CDBS" #~ msgid "cdbs is another approach to Debian packaging, based exclusively on an inheritance system across Makefile files." #~ msgstr "cdbs offre une autre approche de la réalisation des paquets Debian, entièrement basée sur un système d'héritage entre fichiers Makefile." #~ msgid "That tool has its advocates, since it avoids duplicating the same list of dh_* commands in the debian/rules file. However, Debhelper version 7 introduced the dh command, which itself automates the appropriate sequence of calls to all the individual commands in the correct order, and CDBS has lost most of its appeal since then." #~ msgstr "L'outil a conquis bon nombre de mainteneurs car il évitait de dupliquer toujours la même liste de commande dh_* dans debian/rules. Cependant, la version 7 de debhelper a introduit la commande dh, qui automatise l'appel en séquence (et dans le bon ordre) de toutes les commandes individuelles, et CDBS a depuis perdu son principal attrait."