Re: RFS: Several packages waiting sponsor
Hi Sven! Thank you very much for your attention! - Three orphaned packages: and gentoo (http://mentors.debian.net/debian/pool/main/g/gentoo). Had a short look at this one aswell. - There are now two patch files with de.po fixes, I'd like to see them consolidated to one file and passed on to the upstream dev if that hasn't already happened. The de.po is partially resolved in the new version. I have adapted this patch (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314096) to the new version. I have already sent the patch to the upstream author. - Why did you add the .desktop file via a patch? I usually just add them to the /debian/ dir and install them from there. OK.I did not know you can do this. Solved. - IMO the debian/copyright file still needs some polish. If you egrep -ri for 'copyright' you'll find some parts from the FSF and Drepper. Yo he cambiado un poco el archivo. Espero que este mejor. - The path to the icon listed in the menu file misses a leading / OK. Solved (...works well without the initial / !). Please rename the icon to something speaking for itself - icon_iconify.xpm is awful. Is the original file name of the upstream author. I've changed the name on the back. I have updated the package now in mentors. Regards! I. De Marchi -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlkti=gbawynyq5rvoox+nshm1gh8pk30q5d3lfz...@mail.gmail.com
Re: RFS: Several packages waiting sponsor
Hi Sven and Sven Hoexter s...@timegate.de wrote: - peg-solitarie (http://mentors.debian.net/debian/pool/main/p/peg-solitaire) a small game with pegs. I am the upstream autor and mantainer. Looks ok. Though I'm not so keen of sponsoring that. Partly because we've the GTK game (with a lot less features) called pegsolitaire (very, similar name though I've no good idea how to avoid that) and partly because I'm not into games. Maybe you can check with the games people if they'd like to have both or consolidate on your version. I'd prefer some consens on that topic with people who care about packages in that area before uploading that. Paul Wise p...@debian.org wrote: There is also peg-e. Yes, two other programs of this game. My program is different from the other two. Has a complete collection of problems alone. My program includes an algorithm to obtain different solutions for each problem (I think there is any program that does this) and save the solutions. Also, my program allows the user to pose new problems. I think there is no duplication of programs in this case. Regards! I. De Marchi -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimwc4lxc+q7ycxvyixnkccz4n5tclofohpd_...@mail.gmail.com
Re: RFS: logtop a realtime log line rate analyzer
Hi Julien On Mon, Dec 20, 2010 at 07:44:25PM +0100, Julien Palard wrote: I rebuilt it from scratch for the moment cause I can't undertand how to rebuild it properly without a debian/patches/debian-changes-0.1-1. So you have a new version to review today. The problem was that the CHANGELOG was not present in the upstream's orig.tar.gz, thus when building the package this was always a debian-change and thus the debian-changes-0.1-1 created. I had now time to review the package, sorry for the log delay! - debian/copyright: missing space inbetween first stanza and first Files: stanza. - debian/watch: -- Scanning for watchfiles in . -- Found watchfile in ./debian -- In debian/watch, processing watchfile line: http://githubredir.debian.net/github/JulienPalard/logtop/ (.*).tar.gz -- Found the following matching hrefs: /github/JulienPalard/logtop/0~master.tar.gz /github/JulienPalard/logtop/v0.1.tar.gz Newest version on remote site is v0.1, local version is 0.1 = Newer version available from http://githubredir.debian.net/github/JulienPalard/logtop/v0.1.tar.gz -- Downloading updated package v0.1.tar.gz -- Successfully downloaded updated package v0.1.tar.gz and symlinked logtop_v0.1.orig.tar.gz to it -- Scan finished -- v0.1 != 0.1 ... Either change the experession to v(.*) so that the 0.1 is extracted as version. Question: is it possible to release upstream's source tar.gz as logtop-$version.tar.gz? - lintian: N: Processing binary package logtop (version 0.1-1) ... W: logtop: manpage-has-bad-whatis-entry usr/share/man/man1/logtop.1.gz N: N:Each manual page should start with a NAME section, which lists the N:name and a brief description of the page separated by \-. The NAME N:section is parsed by lexgrog and used to generate a database that's N:queried by commands like apropos and whatis. This tag indicates that N:lexgrog was unable to parse the NAME section of this manual page. N: N:For manual pages that document multiple programs, functions, files, or N:other things, the part before \- should list each separated by a comma N:and a space. Each thing listed must not contain spaces; a man page for a N:two-part command like fs listacl must use something like fs_listacl N:in the NAME section so that it can be parsed by lexgrog. N: N:Refer to the lexgrog(1) manual page, the groff_man(7) manual page, and N:the groff_mdoc(7) manual page for details. N: N:Severity: normal, Certainty: certain N: W: logtop: manpage-section-mismatch usr/share/man/man1/logtop.1.gz:5 1 != SECTION N: N:A man page usually should contain a .TH header, specifying the section. N:The section in this manpage doesn't match with the section in the N:filename. N: N:Refer to the groff_man(7) manual page and the man(1) manual page for N:details. N: N:Severity: normal, Certainty: certain N: I: logtop: hyphen-used-as-minus-sign usr/share/man/man1/logtop.1.gz:28 N: N:This manual page seems to contain a hyphen where a minus sign was N:intended. By default, - chars are interpreted as hyphens (U+2010) by N:groff, not as minus signs (U+002D). Since options to programs use minus N:signs (U+002D), this means for example in UTF-8 locales that you cannot N:cut and paste options, nor search for them easily. The Debian groff N:package currently forces - to be interpreted as a minus sign due to N:the number of manual pages with this problem, but this is a N:Debian-specific modification and hopefully eventually can be removed. N: N:- must be escaped (\-) to be interpreted as minus. If you really N:intend a hyphen (normally you don't), write it as \(hy to emphasise N:that fact. See groff(7) and especially groff_char(7) for details, and N:also the thread starting with N:http://lists.debian.org/debian-devel/2003/debian-devel-200303/msg01481.h N:tml N: N:If you use some tool that converts your documentation to groff format, N:this tag may indicate a bug in the tool. Some tools convert dashes of N:any kind to hyphens. The safe way of converting dashes is to convert N:them to \-. N: N:Because this error can occur very often, Lintian shows only the first 10 N:occurrences for each man page and give the number of suppressed N:occurrences. If you want to see all warnings, run Lintian with the N:-d/--debug option. N: N:Refer to the groff_char(7) manual page for details. N: N:Severity: wishlist, Certainty: possible N: I: logtop: hyphen-used-as-minus-sign usr/share/man/man1/logtop.1.gz:46 I: logtop: hyphen-used-as-minus-sign usr/share/man/man1/logtop.1.gz:50 I: logtop: hyphen-used-as-minus-sign usr/share/man/man1/logtop.1.gz:54 I: logtop: hyphen-used-as-minus-sign usr/share/man/man1/logtop.1.gz:58 Bests Salvatore signature.asc Description: Digital signature
Building and uploading package, depending on experimental
Dear mentors, I want to upload a package to http://mentors.debian.net, which I am working on (https://launchpad.net/yade). Now I am trying to build the package with pbuilder. The problem is, that the software depends on package from experimental branch (python-sphinx0.99). I have 2 questions: 1) How can I build the package in pbuilder (--othermirror option did not work)? 2) May I upload such package to mentors.debian.net? I would appreciate any comments or links, where I can find a solution for the problem. Thank you. Anton Gladky
Re: Building and uploading package, depending on experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2010-12-26 14:18, Anton Gladky wrote: Dear mentors, I want to upload a package to http://mentors.debian.net, which I am working on (https://launchpad.net/yade). Now I am trying to build the package with pbuilder. The problem is, that the software depends on package from experimental branch (python-sphinx0.99). Hey I have 2 questions: 1) How can I build the package in pbuilder (--othermirror option did not work)? You want to create a --distribution experimental chroot for this (man pbuilder for more information). Note you should not use the experimental chroot except when you build packages targeted for experimental. 2) May I upload such package to mentors.debian.net? Yes, if you target the package for experimental (instead of unstable). I would appreciate any comments or links, where I can find a solution for the problem. Thank you. Anton Gladky ~Niels -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJNF0GgAAoJEAVLu599gGRCD3YP/iSluG1MMn/Q7Piq/5vtV7Th AgH03O5QBCK8FH1o6mqTni5SYPLGAaxCsifxa4o6LZgzxbnBD3mn5XVQ284V/u2H y+fYeslKXuF2oW9U8fee/6Ki3484rhv5KjEVFshpCkOD2cAEAyvUvqJmLVcTHJmO fI+iBSSMlcu76m0I0Kr6tODy4ubTchV13b0d8NibZiVcipT8D5Jjpb7ne6L/Jysr SPxPh8qA1pLHvO0Yfs0o7jzRwhVaWPVmAOPQ5uyrsxtfa6MUY+dg540F55CPULTP D2PDQ3PS7/cKkfIGb5P92wI5kkMBdkNY9iDdEzj10F/jhlRZnMD/Aw+PQQzuN8C8 KPcEpxIF4NnkQDkfp9Rg4dgIpGDD2Ss9xT9WsEwWOTRgtVHpm4oxYGI9brvxJrG2 MdYIuIFR/tNj7KPAMmjLhAZBfsoDcHLVVL0GyjKv7xDbXwvawiExBjr2RvJ2TaQ1 5KfdBUUUuKqqOlmPyt5W/n1bL8OcyP1jKoTWBUtpQrUyWq9QK83RltaR6IxYB4rj xbBM9zlUkEVFGhNS9/JDCNTG4Bfq0qj28eJ8AlFRLKNRptum/e9957EekiBbi399 8OUsuOW6UpGhdofGbS50bNitZJhJZc4Ve4R4rYCTL8dYFy2RocYUvdIYCOD63pX3 wAn8yEpvmYsEInUWrm7S =Ik6y -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d1741a2.40...@thykier.net
Re: Building and uploading package, depending on experimental
On Sun, Dec 26, 2010 at 02:22:42PM +0100, Niels Thykier wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2010-12-26 14:18, Anton Gladky wrote: Dear mentors, I want to upload a package to http://mentors.debian.net, which I am working on (https://launchpad.net/yade). Now I am trying to build the package with pbuilder. The problem is, that the software depends on package from experimental branch (python-sphinx0.99). Hey I have 2 questions: 1) How can I build the package in pbuilder (--othermirror option did not work)? You want to create a --distribution experimental chroot for this (man pbuilder for more information). Note you should not use the experimental chroot except when you build packages targeted for experimental. ...or you could use your existing pbuilder chroot (or copy it), then login into it (pbuilder --login --save-after-login), add the experimental lines to /etc/apt/sources.list and use /etc/apt/preferences to specify that python-sphinx should be fetched from experimental. Of course, if you want to use that chroot for other purposes (building other packages that do not need the newer python-sphinx version), you'd better copy it instead of just modifying it. That's not too hard - copy the base.tgz file under another name, create a new directory for the result, and copy the pbuilderrc, specifying the new basetgz and result directory. And then again, since the pbuilder manual page says that experimenal is special-cased in pbuilder, it just might turn out that all this is already implemented in pbuilder itself and I'm just wasting everyone's time :) (I have to admit I'm pretty good at that sometimes...) 2) May I upload such package to mentors.debian.net? Yes, if you target the package for experimental (instead of unstable). I would appreciate any comments or links, where I can find a solution for the problem. Thank you. Anton Gladky ~Niels G'luck, Peter -- Peter Pentchev r...@space.bgr...@ringlet.netr...@freebsd.org PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 This sentence claims to be an Epimenides paradox, but it is lying. signature.asc Description: Digital signature
Re: RFS: Several packages waiting sponsor
On Sun, Dec 26, 2010 at 09:29:00AM +0100, Innocent De Marchi wrote: Hi, - There are now two patch files with de.po fixes, I'd like to see them consolidated to one file and passed on to the upstream dev if that hasn't already happened. The de.po is partially resolved in the new version. I have adapted this patch (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314096) to the new version. I have already sent the patch to the upstream author. Ok, but I'd still like to see that merged into one patch and preferably add a nice header. Currently the fix-de-po-corrections.patch has a note refering to the bug id and the auto generated debian-changes-0.19.7-1 has the full default header with the complete changelog. My compromise would be to have both changes auto-generated in one patch by dpkg. Beside that quilt is the tool of choice to edit such things. You just have to set QUILT_PATCHES=debian/patches. - IMO the debian/copyright file still needs some polish. If you egrep -ri for 'copyright' you'll find some parts from the FSF and Drepper. Yo he cambiado un poco el archivo. Espero que este mejor. I think you missed my point here, I guess I wasn't clear. As a start please read http://lists.debian.org/debian-devel-announce/2006/03/msg00023.html The debian/copyright format was ok, I just wanted you to note that most of the files in the m4 directory have a copyright by the FSF. And there are other files aswell with different copyright holders. E.g. the file 'missing' states: # Copyright (C) 1996, 1997, 1999, 2000, 2002 Free Software Foundation, Inc. # Originally by Fran,cois Pinard pin...@iro.umontreal.ca, 1996. or po/Makefile.in.in: # Copyright (C) 1995-1997, 2000-2007 by Ulrich Drepper drep...@gnu.ai.mit.edu and some more in src/. You'll catch most of them with a 'egrep -ri copyright *' in the package source directory. I know that it's hard sometimes but even for packages which don't have to be reviewed by the ftp-masters I'd like to see a copyright file which at least states the obvious things. This is the best way to avoid any trouble and in the past I've seen some very dubious copyright claims in open source software. It's always good to review such things even if you and the current maintainer believe it's all free and ok. And thanks for catching up with upstream on the other bugs. :) Cheers, Sven -- And I don't know much, but I do know this: With a golden heart comes a rebel fist. [ Streetlight Manifesto - Here's To Life ] -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101226192738.ga2...@marvin
Re: RFS: Several packages waiting sponsor
On Sun, Dec 26, 2010 at 09:29:00AM +0100, Innocent De Marchi wrote: Thank you very much for your attention! And one more issue, and that's something I see frequently with newcomers, so I hope that some other new maintainers may read this mail too and avoid it in the future: Please don't alter the original released tar file from your upstream. Just rename it. Before sponsoring something I always download the original upstream release and check provided checksums and signatures if possible. Why is this important? Take a look at the recent mirror compromise of the Proftpd project. In this case sadly upstream doesn't provide any checksums or signatures which is not ideal and something one should ask for. But still the checksum of the upstream released tarball and the .orig. file on mentors differ. Please fix this and only build with the original, renamed upstream tarball. Thanks. Cheers, Sven -- And I don't know much, but I do know this: With a golden heart comes a rebel fist. [ Streetlight Manifesto - Here's To Life ] -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101226194048.gb1...@marvin
Re: Building and uploading package, depending on experimental
Thanks all for suggestions, I have done it! So, if the package requires even 1 depending from experimental it should be targeted as experimental? Anton Gladky On Sun, Dec 26, 2010 at 2:44 PM, Peter Pentchev r...@ringlet.net wrote: On Sun, Dec 26, 2010 at 02:22:42PM +0100, Niels Thykier wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2010-12-26 14:18, Anton Gladky wrote: Dear mentors, I want to upload a package to http://mentors.debian.net, which I am working on (https://launchpad.net/yade). Now I am trying to build the package with pbuilder. The problem is, that the software depends on package from experimental branch (python-sphinx0.99). Hey I have 2 questions: 1) How can I build the package in pbuilder (--othermirror option did not work)? You want to create a --distribution experimental chroot for this (man pbuilder for more information). Note you should not use the experimental chroot except when you build packages targeted for experimental. ...or you could use your existing pbuilder chroot (or copy it), then login into it (pbuilder --login --save-after-login), add the experimental lines to /etc/apt/sources.list and use /etc/apt/preferences to specify that python-sphinx should be fetched from experimental. Of course, if you want to use that chroot for other purposes (building other packages that do not need the newer python-sphinx version), you'd better copy it instead of just modifying it. That's not too hard - copy the base.tgz file under another name, create a new directory for the result, and copy the pbuilderrc, specifying the new basetgz and result directory. And then again, since the pbuilder manual page says that experimenal is special-cased in pbuilder, it just might turn out that all this is already implemented in pbuilder itself and I'm just wasting everyone's time :) (I have to admit I'm pretty good at that sometimes...) 2) May I upload such package to mentors.debian.net? Yes, if you target the package for experimental (instead of unstable). I would appreciate any comments or links, where I can find a solution for the problem. Thank you. Anton Gladky ~Niels G'luck, Peter -- Peter Pentchev r...@space.bgr...@ringlet.netr...@freebsd.org PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 This sentence claims to be an Epimenides paradox, but it is lying. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJNF0a3AAoJEGUe77AlJ98TJdUQAKGEdsTysgzoVjbUq9PgTRac R473pPQAhxxfca6f1EdsM2EyBzW8QQIPezGQJIs5iniIxmXms56J67AjyFV4VQBN QKUMVoKZf+gVV8Thv8rZgJvpSRs0c4p4/w3YHGx1bD9Oc8rhepPCX1WzCLyomLs4 U8w2OIh8d4UQH+A08aYI1aRG5gddAMlWj00dTF9lZDAkCU+/UMK1fWV067PnViwl /hmLtTd7LMPLvYQXvpVteE6euC8omm5QHwG7eDgEHoCe0ohD0sB9yyRJh+pDNuAq 1MKwPycJpaMTS8vM0cnG8NBzd0C+QGb9JMnUAJeUskUqQC9VnlCakf39tqH7bJYe uDB/LUnDtNR66hbYJXsUldNNrisZWYhrrHsxvFfNlnz0tmDEvorQzpV/KyxKwN8Z e+65ed558FKILUtxg+090rfCG+ZLE/Sg3MR1c1a0JH2cATlQBc9xTIfQHIyInZL0 m5G810qkYJ5RqY18pJUkv9nB+25l+uVq3QHLcIUpXBejXUqi0iEqqx3uD2S0Xf6+ eELd9F6nV7OUelJ5MlY7R/LyaZ6xJ6bcXQzuMIa7ywfQI1rRXYLJRLnqswmVVCid n3w7DDDdfFl6B9yai3DDbgIRUcCn/g/xOL9rl/3D5eThn5zPwip1ydoZLjrhFr1S j5ZwWxRNTsltCx9uAlAE =Dg82 -END PGP SIGNATURE-
Re: Building and uploading package, depending on experimental
On Sun, Dec 26, 2010 at 09:24:46PM +0100, Anton Gladky wrote: Thanks all for suggestions, I have done it! So, if the package requires even 1 depending from experimental it should be targeted as experimental? Anton Gladky Yes, as it won't be buildable/usable for someone that is just using unstable. -- Etienne Millon signature.asc Description: Digital signature
Re: RFS: klatexformula
Dear all, I fixed the issues mentioned below and uploaded the latest packages to the mentors server at http://mentors.debian.net/debian/pool/main/k/klatexformula Hopefully these have been the last issues and the package is ready to be sponsored. Best regards, Tobias On Sunday 05 December 2010 Michael Tautschnig wrote: I just looked at your RFS and intended to sponsor your package. But before doing so I did another round of reviewing and this resulted in a number of comments which need to be addressed before the package can be uploaded: - Upstream has released 3.2.2. - debian/changelog: Initial package is generally worded as Initial upload - debian/control: All binary packages share the same description. You should at least append one sentence describing the peculiarities of each package. And please use a consistent uppercase/lowercase version of KLatexFormula. - debian/copyright: It would be nice if it were formatted according to DEP-5 (http://dep.debian.net/deps/dep5/); especially as this is already almost the case. - No need for debian/README.source if your package is v3/quilt anyway. - debian/rules: It says rm debian/klatexformula.1, but you ship klatexformula.1 in the *source* package!? - debian/patches/debian-changes-3.2.1-1: This patch contains a number of auto-generated files. Couldn't you just have the debian build process generate those files? Even more so as your home-directory name occurs several times... Well, and I tried to build your package: ... -- [KDE4 SETTINGS (for kate plugin)] *** NOTE *** KDE4 is required to build KTextEditor plugin. Since KDE4 could not be found, the KLatexFormula KTextEditor plugin will not be built (KLF_BUILD_KTEXTEDITORPLUGIN). KLatexFormula itself does not need KDE4 and will be compiled normally. Please re-run cmake to proceed. CMake Error at src/klfkateplugin/CMakeLists.txt:30 (message): KDE4 not found. Call Stack (most recent call first): src/klfkateplugin/CMakeLists.txt:36 (klf_nokde4) It seems that your dependencies are incomplete. Please fix these issues and ping the list once again, then your package should get sponsored soon. Hope this helps, Michael -- Tobias Winchen III. Physikalisches Institut A RWTH Aachen University +49 (0)241 80 27326 signature.asc Description: This is a digitally signed message part.
Re: Building and uploading package, depending on experimental
Thanks all for your valuable answers! I have successfully uploaded a package. Anton Gladky On Sun, Dec 26, 2010 at 9:36 PM, Etienne Millon etienne.mil...@gmail.comwrote: On Sun, Dec 26, 2010 at 09:24:46PM +0100, Anton Gladky wrote: Thanks all for suggestions, I have done it! So, if the package requires even 1 depending from experimental it should be targeted as experimental? Anton Gladky Yes, as it won't be buildable/usable for someone that is just using unstable. -- Etienne Millon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJNF6dXAAoJEObsMVOU5V5V2bsIAJna8fcp9ClVLuUpWjKpNnPy SFWtwD+iI4tEO4b+hVS7LnminrKpd8vRvyRkU1VMOLZtRBzH4iNDKC1Oe2rBuu7B AmoRbOSEqWZqKKWgtFSyjiznxAtatqL0Binsh7okVpbWH3T/3obwChI0jizrFxJK vgTkpJPAb/yvHXkHURVojyF4lPr5RdXkKIm2JNSq0gWPs0mShhfBPNqg/Sv6iGQ/ uJhHqKxVRBrYbLfX4tr2XT3Ka2TZF90PXSRxJ+YSWIl6iEyVHhjMIFRt7mJXWWTe bJqxknJwp3zphA2+MjCaydJoPhckQDvDf9mAMNR0SL6SG4ItFuCGyWa1ov+zsxc= =fq9z -END PGP SIGNATURE-
Re: RFS: logtop a realtime log line rate analyzer
Hi Salvatore On Sun, Dec 26, 2010 at 1:42 PM, Salvatore Bonaccorso car...@debian.org wrote: I had now time to review the package, sorry for the log delay! Don't worry for this ! - debian/copyright: missing space inbetween first stanza and first Files: stanza. Done - debian/watch: -- v0.1 != 0.1 ... Either change the experession to v(.*) so Done by renaming the tag Question: is it possible to release upstream's source tar.gz as logtop-$version.tar.gz? So logtop-0.1.tar.gz ? as done here ? - lintian: Checked with --pedantic ! I'll be away from keyboard for one week, so don't worry about your speed at reviewing my package ! Kind regards. -- Julien Palard -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktims4q9qxzpuswcspbet8mewamlvÎtzeqol...@mail.gmail.com
