From: Charles Plessy Date: Tue, 28 Jun 2011 23:11:31 +0000 (+0900) Subject: Traduction mise à jour. X-Git-Url: https://source.charles.plessy.org/?a=commitdiff_plain;h=ecc99fb3f0dbdc35a49007d3fe0875f982a8ab24;p=source%2F.git Traduction mise à jour. --- diff --git "a/Debian/debi\303\242neries/bioperl-et-tests.en.po" "b/Debian/debi\303\242neries/bioperl-et-tests.en.po" index 308c3ce9..9dc69249 100644 --- "a/Debian/debi\303\242neries/bioperl-et-tests.en.po" +++ "b/Debian/debi\303\242neries/bioperl-et-tests.en.po" @@ -2,11 +2,12 @@ # Copyright (C) YEAR Free Software Foundation, Inc. # This file is distributed under the same license as the PACKAGE package. # Charles Plessy , 2011. +# Charles Plessy , 2011. msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "POT-Creation-Date: 2011-06-29 07:37+0900\n" -"PO-Revision-Date: 2011-06-28 23:06+0900\n" +"PO-Revision-Date: 2011-06-29 08:11+0900\n" "Last-Translator: Charles Plessy \n" "Language-Team: Hopla\n" "Language: en\n" @@ -37,7 +38,6 @@ msgid "[[!meta title=\"BioPerl et tests de régression\"]]\n" msgstr "[[!meta title=\"BioPerl and regression tests\"]]\n" #. type: Plain text -#, fuzzy #| msgid "" #| "Il y a deux semaines, j'ai mis à jour les paquets contentant les modules " #| "BioPerl [[!debpkg bioperl]] et [[!debpkg bioperl-run]], ce qui a permis " @@ -65,19 +65,19 @@ msgid "" "(http://lists.debian.org/debian-perl/2009/09/msg00044.html) quand le paquet " "est construit localement." msgstr "" -"Two weeks ago, I updated the packages containing the BioPerl modules [[!" -"debpkg bioperl]] and [[!debpkg bioperl-run]], which allowed to resume the " -"work done on [!debpkg gbrowse]], one of the [[genome browsers|gbrowse]] " -"available in Debian. As many Perl modules, BioPerl has extensive " -"[regression tests](http://www.bioperl.org/wiki/HOWTO:" -"Writing_BioPerl_Tests). Some of them need access to external services, and " -"are disabled by default as the Internet is not available in our [build farm]" -"(http://buildd.debian.org). Nevertheless, they can be triggered through the " -"environment variable [DEB_MAINTAINER_MODE](http://lists.debian.org/debian-" +"Two weeks ago, I updated the packages containing the BioPerl modules " +"[[!debpkg bioperl]] and [[!debpkg bioperl-run]], which allowed to resume the " +"work done on [!debpkg gbrowse desc=\"GBrowse\"]], one of the [[genome " +"browsers|gbrowse]] available in Debian. As many Perl modules, BioPerl has " +"extensive [regression " +"tests](http://www.bioperl.org/wiki/HOWTO:Writing_BioPerl_Tests). Some of " +"them need access to external services, and are disabled by default as the " +"Internet is not available in our [build farm](http://buildd.debian.org). " +"Nevertheless, they can be triggered through the environment variable " +"[DEB_MAINTAINER_MODE](http://lists.debian.org/debian-" "perl/2009/09/msg00044.html) when building the package locally." #. type: Plain text -#, fuzzy #| msgid "" #| "BioPerl passe avec succès tous les tests hors-ligne, et une partie des " #| "erreurs en ligne est déjà corrigée dans la [branche de dévelopment]" @@ -98,16 +98,16 @@ msgid "" "difficile de déterminer de quel côté est le problème." msgstr "" "Bioperl sucessfully passes all off-line tests, and a part of the on-line " -"errors is already corrected in teh [development branch](https://github.com/" -"bioperl/bioperl-live/tree/HEAD/t). In contrary, BioPerl-Run fail the tests " -"for Bowtie, DBA, EMBOSS, Genewise, Hmmer, PAML, SABlastPlus, TCoffee and " -"gmap-run. In some cases, like EMBOSS, it is because a command has been " -"renamed in Debian. In other cases, in particular [[!debpkg wise desc=\"DBA " -"et Genewise\"]], it is much more difficult to figure out on which side is " -"the problem." +"tests is already corrected its [development " +"branch](https://github.com/bioperl/bioperl-live/tree/HEAD/t). In contrary, " +"BioPerl-Run fail the tests for Bowtie, DBA, EMBOSS, Genewise, Hmmer, PAML, " +"SABlastPlus, T-Coffee and gmap-run. In some cases, like EMBOSS, it is " +"because a command has been renamed in Debian. In other cases, in particular " +"[[!debpkg wise desc=\"DBA et Genewise\"]], it is much more difficult to " +"figure out on which side is the problem." #. type: Plain text -#, fuzzy, no-wrap +#, no-wrap #| msgid "Les tests de régression sont essentiels pour déterminer si un paquet fonctionne ou non sur les plates-formes autres que celles utilisées par l'empaqueteur (amd64 dans mon cas). Même les plus simples peuvent être utiles. Dans le cas de [[!debpkg t-coffee desc=\"T-Coffee\"]], qui fournit un test très simple que j'ai activé récemment, cela a montré que les paquets distribués actuellement pour armel [[!debbugs 631249 desc=\"ne fonctionnent pas du tout\"]." msgid "" "Les tests de régression sont essentiels pour déterminer si un paquet fonctionne\n" @@ -117,10 +117,15 @@ msgid "" "fournit un test rudimentaire que j'ai activé récemment, cela a montré que les\n" "paquets distribués actuellement pour armel [[!debbug 631249 desc=\"ne\n" "fonctionnent pas du tout\"]].\n" -msgstr "Regression tests are essential to determine if a package works or not on other architectures that the one used by the packager (amd64 in my case). Even simple ones can be useful. In the case of [[!debpkg t-coffee desc=\"T-Coffee\"]], that has a rudimentary test that I have activated recently, it showed that the packages distributed on armel are [[!debbugs 631249 desc=\"not working at all\"]." +msgstr "" +"Regression tests are essential to determine if a package works or not on " +"[ports](http://www.debian.org/ports/) others than the one used by the " +"packager (amd64 in my case). Even simple ones can be useful. In the case " +"of [[!debpkg t-coffee desc=\"T-Coffee\"]], that has a rudimentary test that I " +"have activated recently, it showed that the packages distributed on armel " +"are [[!debbugs 631249 desc=\"not working at all\"]]." #. type: Plain text -#, fuzzy #| msgid "" #| "Exécuter les tests de régression durant la construction du paquet " #| "comporte des avantages, comme d'avoir le résultat automatiquement publié " @@ -143,16 +148,15 @@ msgid "" "sur le portage armel tant que t-coffee y défectueux sur armel." msgstr "" "Running regression tests when building packages have advantages, in " -"particular to have the results published automatically as part of the [build " +"particular to have the results published for each port automatically as part " +"of the [build " "logs](https://buildd.debian.org/status/logs.php?pkg=t-coffee&ver=8.99-1). " -"But is also cause problems. First, it can necessitate to lengthen the list " -"of build dependancies. For instance, bioperl-run has to build-depend on " -"each program for which it provides a wrapper in order to make comprehensive " -"tests. And in this particular case, as long as t-coffee is broken on armel, " -"bioperl-run can not be built on this platform." +"But is also cause problems. First, a package would need to build-depend on " +"every software it can interact with, in order to test it comprehensively. " +"In the example of bioperl-run, it makes it impossible to build on armel as " +"long as t-coffee is broken there." #. type: Plain text -#, fuzzy #| msgid "" #| "Deuxièmement, cela ne fournit pas un moyen simple à l'utilisateur de " #| "tester un paquet installé sur son système. La proposition [DEP 8](http://" @@ -179,13 +183,11 @@ msgid "" "qu'un seul programme manquant n'invalide complètement un paquet qui ne s'en " "sert que de manière optionnelle." msgstr "" -"Second, this does not help users to test the binary packages installed on " -"their systems. The [Debian Enhancement Proposal 8](http://dep.debian.net/" -"deps/dep8/) takes a different way, as its goal is to test at build time the " -"softwares, not as they have been built but as they are being packaged. This " -"is a step in a good direction. Perhaps it will be possible to build on this " -"project, in order to allow to test binary packages by themselves. This " -"would allow to perform the tests not during the build, but just after, and " -"introduce more flexibility in the build dependancies, so that the absence of " -"one program does not prevent the build of a packaegs that can use it on a " -"completely optionnal manner." +"Second, this does not allow testing on the user side. The [Debian " +"Enhancement Proposal 8](http://dep.debian.net/deps/dep8/) whose goal is to " +"test programs as they are packaged, is a step in a good direction. Perhaps " +"will it be possible to extend this project, for testing binary packages by " +"themselves. This would allow to perform the tests not during the build but " +"just after, and take advantage of the flexible levels of dependency between " +"binary packages, so that the unavailability of one program does not prevent " +"the build of a packages that can use it on a completely optional manner."