Re: RFS: clipit
On Fri, 12 Nov 2010, Cristian Henzel wrote: dpkg-shlibdeps: warning: dependency on libpthread.so.0 could be avoided if debian/clipit/usr/bin/clipit were not uselessly linked against it (they use none of its symbols). but this last one is unnecessary, because my program actually uses functions from libpthread.so (pthread_exit), so it needs that library... Hum, libc.so.6 also has that symbol (and dpkg-shlibdeps finds it there first), that's why dpkg-shlibdeps thinks it's not necessary. But I hear those symbols on libc6 are weak and thus the one provided by libpthread are used. Thus this warning is rather bogus apparently. Would you please file a bug report against dpkg-dev for this? Cheers, -- Raphaël Hertzog ◈ Debian Developer ◈ [Flattr=20693] Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- 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/20101112091608.ge22...@rivendell.home.ouaza.com
Re: RFS: kstars-data-extra-tycho2 (third try)
On 11/10/2010 01:06 PM, Noel David Torres Taño wrote: On Sábado 18 Septiembre 2010 22:38:23 Noel David Torres Taño escribió: Dear mentors, I am looking for a sponsor for my package kstars-data-extra-tycho2. * Package name: kstars-data-extra-tycho2 Version : 1.1r1-1 Upstream Author : Akarsh Simha, Jason Harris kstars-de...@kde.org * URL : http://edu.kde.org/kstars/downloads/tycho2_mag_12.5-1.1.tar.bz2 * License : GPL Section : science It builds these binary packages: kstars-data-extra-tycho2 - Contains the Tycho2 star catalog for centralized (avoiding per-user) install The package appears to be lintian clean. Totally clean in source and 4 overrides in binary (two -I and two --pedantic) The upload would fix these bugs: 597202 and is a step in fixing 596007 My motivation for maintaining this package is: I collaborate in maintaining Astronomy classrooms in which several students per computer need to download each one the same files. I think that a centralized install is better if possible. I discussed this in KDE forum in http://forum.kde.org/viewtopic.php?f=21t=90166 and want to create Debian packages for the other 8 downloadable kstars' extras. we have a similar problem for bioinformatics, and so the bioinformatics community has come up with the getData (wiki.debian.org/getData) tool to help with the maintenance of public data resources. It would be lovely if you could give that a review with the hindsight of your particular demands. Tycho2 is already part of that, btw, it was my first test case :) Our strategy was to have applications add instructions to /etc/getdata.d on how to retrieve and pre/post-process the data that they work on. Have many thanks Steffen -- 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/4cdd08a0.6050...@gmx.de
RFS: sima (autoqueue MPD client, find similar artists to queue)
Dear mentors, I am looking for a sponsor for my package sima. * Package name: sima Version : 0.6.0-1 Upstream Author : Kaliko Jack ef...@azylum.org * URL : http://codingteam.net/project/sima * License : GPLv3 Section : sound It builds these binary packages: sima - Automagically add title to mpd playlist The package appears to be lintian clean. The upload would fix this bug: 594085 My motivation for maintaining this package is: As the upstream Author I would be glad to distribute my soft within official Debian repository, first because it is a way to contribute and learn about python packaging within Debian, second it would benefit the popularity hence quality of the soft to be distributed in such a popular distribution. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/sima - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/sima/sima_0.6.0-1.dsc I would be glad if someone uploaded^Wreview this package for me. Kind regards Geoffroy Youri Berret signature.asc Description: OpenPGP digital signature
Re: RFS: clipit
Hello, thanks for your reply! I have also tried removing the reference to pthread.h in my program, hoping that it would take the symbols from libc, but I still got the same warning from dpkg-shlibdeps. So, should I put the reference to pthread back in and leave it like that (with the warning) and submit the bug against dpkg-dev? Best regards, Mit freundlichen Grüßen, Henzel Cristian On 11/12/2010 11:16 AM, Raphael Hertzog wrote: On Fri, 12 Nov 2010, Cristian Henzel wrote: dpkg-shlibdeps: warning: dependency on libpthread.so.0 could be avoided if debian/clipit/usr/bin/clipit were not uselessly linked against it (they use none of its symbols). but this last one is unnecessary, because my program actually uses functions from libpthread.so (pthread_exit), so it needs that library... Hum, libc.so.6 also has that symbol (and dpkg-shlibdeps finds it there first), that's why dpkg-shlibdeps thinks it's not necessary. But I hear those symbols on libc6 are weak and thus the one provided by libpthread are used. Thus this warning is rather bogus apparently. Would you please file a bug report against dpkg-dev for this? Cheers, -- 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/4cdd0812.8010...@web-tm.com
Re: RFS: sima (autoqueue MPD client, find similar artists to queue)
Hello. I am not DM or DD but you should fix a spelling error in manpage: spelling-error-in-manpage usr/share/man/man1/simadb_cli.1.gz completly completely Cheers Iker 2010/11/12 Geoffroy Youri Berret ef...@azylum.org Dear mentors, I am looking for a sponsor for my package sima. * Package name: sima Version : 0.6.0-1 Upstream Author : Kaliko Jack ef...@azylum.org * URL : http://codingteam.net/project/sima * License : GPLv3 Section : sound It builds these binary packages: sima - Automagically add title to mpd playlist The package appears to be lintian clean. The upload would fix this bug: 594085 My motivation for maintaining this package is: As the upstream Author I would be glad to distribute my soft within official Debian repository, first because it is a way to contribute and learn about python packaging within Debian, second it would benefit the popularity hence quality of the soft to be distributed in such a popular distribution. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/sima - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/sima/sima_0.6.0-1.dsc I would be glad if someone uploaded^Wreview this package for me. Kind regards Geoffroy Youri Berret
Re: RFS: clipit
Hi, On Fri, 12 Nov 2010, Cristian Henzel wrote: thanks for your reply! I have also tried removing the reference to pthread.h in my program, hoping that it would take the symbols from libc, but I still got the same warning from dpkg-shlibdeps. So, should I put the reference to pthread back in and leave it like that (with the warning) and submit the bug against dpkg-dev? Actually the problem is more complex apparently. You don't need to link it to libpthread unless you call pthread_create somewhere. So you need to fix the options passed to the linker to drop the -lpthread (the library linked are unrelated to the include you use, but if you can drop the include and it still builds it probably means you don't need the library for real and you can drop it from the linker command line). So it's not a bug on dpkg-shlibdeps as I first suspected. Cheers, -- Raphaël Hertzog ◈ Debian Developer ◈ [Flattr=20693] Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- 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/20101112095054.ga4...@rivendell.home.ouaza.com
Re: RFS: sima (autoqueue MPD client, find similar artists to queue)
Hi Dne Fri, 12 Nov 2010 10:30:51 +0100 Geoffroy Youri Berret ef...@azylum.org napsal(a): The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/sima - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/sima/sima_0.6.0-1.dsc The upstream tarball name is mpd_sima, maybe you want to name source package same way? Why have you modified the source tarball? You shoudn't list debian/changelog.gz in debian/docs. You should install examples by dh_installexamples (or debian/examples) not by debian/docs. Why you manually compress changelog in debian/rules? You should rather use dh_installchangelogs for installing it. -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Re: RFS: ccbuild (updated package)
Am 11.11.2010 15:44, schrieb Williams Orellana: 2010/11/11 Markus Schölzelm-schoel...@web.de: Dear mentors, I am looking for a sponsor for the new version 2.0.1-0.1 of my package ccbuild. It builds these binary packages: ccbuild- A C++ source scanning build utility The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/c/ccbuild - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/c/ccbuild/ccbuild_2.0.1-0.1.dsc I would be glad if someone uploaded this package for me. Kind regards Markus Schölzel -- 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/4cdbf736.9030...@web.de Well, I'm not a DD, but here's my review for your package :) lintian show me this ccbuild source: quilt-patch-missing-description 10-ccbuild.1-fix-spelling.patch this is easy to solve, you just have to add a description of the changes you made to the original source In the control file you should split the Depends this should not be greater than 80 characters would be nice if the copyright was standardized format with the dep-5 [0] these are my remarks, I hope you serve something ;) [0] http://dep.debian.net/deps/dep5/ Thanks for your help! http://mentors.debian.net/debian/pool/main/c/ccbuild/ccbuild_2.0.1-0.2.dsc The new version fixes: - add headers to 10-ccbuild.1-fix-spelling.patch - fix length of Build-Depends in debian/control - rewrite of debian/copyright (dep-5 format) Hopefully these fixes are correct. Kind regards Markus Schölzel -- 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/4cdd10de.60...@web.de
Re: RFS: clipit
On Fri, Nov 12, 2010 at 10:16:08AM +0100, Raphael Hertzog wrote: On Fri, 12 Nov 2010, Cristian Henzel wrote: dpkg-shlibdeps: warning: dependency on libpthread.so.0 could be avoided if debian/clipit/usr/bin/clipit were not uselessly linked against it (they use none of its symbols). but this last one is unnecessary, because my program actually uses functions from libpthread.so (pthread_exit), so it needs that library... Hum, libc.so.6 also has that symbol (and dpkg-shlibdeps finds it there first), that's why dpkg-shlibdeps thinks it's not necessary. But I hear those symbols on libc6 are weak and thus the one provided by libpthread are used. Thus this warning is rather bogus apparently. Would you please file a bug report against dpkg-dev for this? If you don't actually use threads, the stubs provided by glibc will be used (they are mostly no-ops). This is done to avoid the need for every library to come in a single-threaded and a multi-threaded version and yet pay the performance costs of threading only when they are actually needed. The only such function you use is pthread_exit(), so dpkg-shlibdeps is correct here. -- 1KB // Microsoft corollary to Hanlon's razor: // Never attribute to stupidity what can be // adequately explained by malice. signature.asc Description: Digital signature
Re: RFS: clipit
Hello, I have updated the package now and removed all of the references to pthread.h, but it still includes it, and I have no idea why (any help on this would be appreciated). P.S. I find it odd that it includes the package even if there's no referece to it and I also use -Wl,--as-needed... Best regards, Mit freundlichen Grüßen, Henzel Cristian On 11/12/2010 11:50 AM, Raphael Hertzog wrote: Hi, On Fri, 12 Nov 2010, Cristian Henzel wrote: thanks for your reply! I have also tried removing the reference to pthread.h in my program, hoping that it would take the symbols from libc, but I still got the same warning from dpkg-shlibdeps. So, should I put the reference to pthread back in and leave it like that (with the warning) and submit the bug against dpkg-dev? Actually the problem is more complex apparently. You don't need to link it to libpthread unless you call pthread_create somewhere. So you need to fix the options passed to the linker to drop the -lpthread (the library linked are unrelated to the include you use, but if you can drop the include and it still builds it probably means you don't need the library for real and you can drop it from the linker command line). So it's not a bug on dpkg-shlibdeps as I first suspected. Cheers, -- 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/4cdd1301.6060...@web-tm.com
Re: RFS: ccbuild (updated package)
Hi, Markus Schölzel m-schoel...@web.de writes: I am looking for a sponsor for the new version 2.0.1-0.1 of my package ccbuild. Your NMU does not close any bugs so I don't understand why you want to upload the package. If you want a new upstream version, you should first file a bug and ask the maintainer to update the package. Please remember that Debian is currently frozen to prepare for the next release. The maintainer might not want to update the package in unstable for this reason. Regards, Ansgar -- 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/s2soc9uq1m4@pc-admin-01.mathi.uni-heidelberg.de
Re: RFS: sima (autoqueue MPD client, find similar artists to queue)
On Fri, Nov 12, 2010 at 10:30:51AM +0100, Geoffroy Youri Berret wrote: I would be glad if someone uploaded^Wreview this package for me. you don't need to override dh_install, you can just rely on debian/sima.install if you * rename debian/sima.sh to debian/wrappers/sima (can't rename it to debian/sima because that's going to be a directory in the build process) * change the sima /usr/bin line to debian/wrappers/sima /usr/bin in debian/sima.install * and likewise for simadb_cli still concerning the wrappers: using a shell script is not what i'd do in own packages, but i'm not sure about the pros and cons so i won't recommend against it, but you might want to * exec the python script instead of calling it, so that the sh process doesn't stay until the program quits * put the $@ in quotes so the arguments are not shell-unescaped again * (optionally) avoid changing the working directory, and finally use PYTHONPATH=/usr/share/sima/:$PYTHONPATH exec /usr/share/sima/mpd_sima.py $@ regards chrysn -- To use raw power is to make yourself infinitely vulnerable to greater powers. -- Bene Gesserit axiom signature.asc Description: Digital signature
Re: RFS: clipit
Hi, On Fri, 12 Nov 2010, Cristian Henzel wrote: P.S. I find it odd that it includes the package even if there's no referece to it and I also use -Wl,--as-needed... Maybe -Wl,--as-needed is not smart enough to cover this case. Entirely dropping the -lpthread is the only way to fix this apparently. That said the dpkg-shlibdeps warning is harmless and it's not a big deal if it stays in your build log. Cheers, -- Raphaël Hertzog ◈ Debian Developer ◈ [Flattr=20693] Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- 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/20101112124801.ga6...@rivendell.home.ouaza.com
Re: RFS: clipit
Hello, well, I'm not sure how I could drop -lpthread. Like I said, there is no reference to the pthread lib in any of my source files (beside the obvious call to pthread_exit), so this must come from some of the stuff that ./configure runs, and I am not sure how I could drop it from there. If it's a harmless warning and the rest of it is fine, could it get in the repos like this? Best regards, Mit freundlichen Grüßen, Henzel Cristian On 11/12/2010 02:48 PM, Raphael Hertzog wrote: Hi, On Fri, 12 Nov 2010, Cristian Henzel wrote: P.S. I find it odd that it includes the package even if there's no referece to it and I also use -Wl,--as-needed... Maybe -Wl,--as-needed is not smart enough to cover this case. Entirely dropping the -lpthread is the only way to fix this apparently. That said the dpkg-shlibdeps warning is harmless and it's not a big deal if it stays in your build log. Cheers, -- 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/4cdd38a6.90...@web-tm.com
Re: RFS: clipit
Le vendredi 12 nov. 2010 à 13:48:01 (+0100), Raphael Hertzog a écrit : Hi, On Fri, 12 Nov 2010, Cristian Henzel wrote: P.S. I find it odd that it includes the package even if there's no referece to it and I also use -Wl,--as-needed... Maybe -Wl,--as-needed is not smart enough to cover this case. Entirely dropping the -lpthread is the only way to fix this apparently. I haven't checked the package at all, but if it uses libtool, it might also be related to #347650 [0] which prevents -Wl,--as-needed to work as expected. Cheers, Julien [0] http://bugs.debian.org/347650 -- Julien Valroff jul...@kirya.net http://www.kirya.net GPG key: 4096R/258E26B1 E1D8 5796 8214 4687 E416 948C 859F EF67 258E 26B1 -- 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/20101112125138.gc24...@kirya.net
Re: RFS: clipit
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2010-11-12 13:51, Julien Valroff wrote: Le vendredi 12 nov. 2010 à 13:48:01 (+0100), Raphael Hertzog a écrit : Hi, On Fri, 12 Nov 2010, Cristian Henzel wrote: P.S. I find it odd that it includes the package even if there's no referece to it and I also use -Wl,--as-needed... Maybe -Wl,--as-needed is not smart enough to cover this case. Entirely dropping the -lpthread is the only way to fix this apparently. I haven't checked the package at all, but if it uses libtool, it might also be related to #347650 [0] which prevents -Wl,--as-needed to work as expected. Cheers, Julien [0] http://bugs.debian.org/347650 I noticed that --as-needed was one of the first arguments passed and is definitely passed before the libraries. I think the issue is that it picks up -pthread via pkg-config and - --as-needed does not handle -pthread, since it is not a -l, but it is a wild-guess. ~Niels -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJM3UDNAAoJEAVLu599gGRC6U8P/RApv10gubEdmmOMaY72p6ii EjBVx7X1q/HZ+W0S8vRDCj6EHnFRB3u/fmE+9qdfDGvKVmmj0sDmifCJfEWzFwDa oyovoMLqTNHpSfsMxRpzHXS186v2fwVl78094NBz7GAvQrUyCatDuu6l7gqjdDJ9 9nw6yazB4uoIlFqOdEpDcEJ2SUzJy1O3TBeOTAIXbnyMMViD4BK+Mtf6nSfYMl7v xxVXYBcBoWI5IJnglffCbf4OxO7oNru6WT/XhBcgWFIHgMZj1Q9SEMtun+39xHWf btmgfo+GVJZNEWDSaHHSjNbrJEM9dFcbrNfF0x9aYyVkvSSlfgodTepH5TDL3doc ZEmEMLOhVyF4D8wTfishZsnuWIfjE/naa9AqTc6ezIzsMMXWRKqU61ykUWyTyCqO gvwrPbUQ4fm9Eet3DSIgbGyD5kCd6+aSwIbav11yr9xEybViLB5bmrQub2xcnpJa lHQmde6gLiZfKdjwOy+cviKbWXy5E8Ny1b2NzmhtWOeOeBRW4+GVuy6iEVtc4BJh QMSDxZhI08mJ92uyaOwLvC9+gNNaIVceeuDWyX6/oXjTxTfAilpe5WXStbZuWBgQ h5wDrqEs91uIpa3NuJ15xbjedn7HF449eHmuVW0BGmoT8fIY8lEeULI2ZZVzs3iM fsbwKnzkTfwV+DkjWwuS =6bve -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/4cdd40ce.8040...@thykier.net
Re: RFS: clipit
On Fri, 12 Nov 2010, Cristian Henzel wrote: If it's a harmless warning and the rest of it is fine, could it get in the repos like this? Sure, this warning is not a reason to block an upload. Many packages in the archive have this kind of warnings. They are not bugs but things that can be improved. Cheers, -- Raphaël Hertzog ◈ Debian Developer ◈ [Flattr=20693] Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- 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/20101112134753.ga8...@rivendell.home.ouaza.com
Re: RFS: kstars-data-extra-tycho2 (third try)
On Miércoles 10 Noviembre 2010 21:01:22 Benoît Knecht escribió: Benoît Knecht wrote: [...] A few more comments: - Your debian/docs file is empty; did you mean to add something there, like README.source for instance? - I don't think you need a patch just to create a Makefile. You can achieve the same result with a debian/install file. - Your debian/rules contains a typo: %export DH_VERBOSE=1 instead of #export DH_VERBOSE=1; I'm also not sure why you're exporting DESTDIR. - You may want to rephrase the description in debian/control; the sentence Installing this package avoids the need for the users to each one download the catalog for itself sounds wrong (instead of itself, I would write themselves or him/herself). But something like Installing this package avoids the need for each user to individually download the whole catalog might be even clearer. I hope this helps. Cheers, Thanks for your comments. I was trying to get things on that way, but I've found no information at all in the Policy about debian/install . Where can I found info about it? I will try first to get the package done and in good shape and re-address the License thing here after that. Anyway, I'm doing that in parallel. Thanks Noel er Envite signature.asc Description: This is a digitally signed message part.
Re: RFS: kstars-data-extra-tycho2 (third try)
Hi Noel, Noel David Torres Taño wrote: On Miércoles 10 Noviembre 2010 21:01:22 Benoît Knecht escribió: Benoît Knecht wrote: [...] - I don't think you need a patch just to create a Makefile. You can achieve the same result with a debian/install file. [...] Thanks for your comments. I was trying to get things on that way, but I've found no information at all in the Policy about debian/install . Where can I found info about it? In the dh_install(1) man page, and in the Debian New Maintainers' Guide http://www.debian.org/doc/maint-guide/ch-dother.en.html#s-install. Cheers, -- Benoît Knecht -- 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/20101112141647.gb6...@debian.lan
RFS: python-ordereddict
Dear mentors, I am looking for a sponsor for my package python-ordereddict. * Package name: python-ordereddict Version : 1.1-1 Upstream Author : Raymond Hettinger * URL : http://pypi.python.org/pypi/ordereddict/ * License : MIT Section : python It builds these binary packages: python-ordereddict - drop-in substitute for Py2.7's new collections.OrderedDict The package appears to be lintian clean. The upload would fix these bugs: 603277 My motivation for maintaining this package is: some of the tools I use at work require this package. Plus, I've never packaged Python modules before, and this seems simple enough to start tackling them. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/python-ordereddict - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/python-ordereddict/python-ordereddict_1.1-1.dsc This is my first Python package, I'd appreciate reviews or comments on it. I would be glad if someone uploaded this package for me. I'm CCing fEnIo, who is my usual sponsor for the GeeXboX packages, and the debian-python list. Please CC me on replies as I'm not subscribed to the list. Kind regards Davide Cavalca -- 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/9198eee5747496c291a4f4c9f2883...@localhost
Re: RFS: python-ordereddict
On Fri, Nov 12, 2010 at 15:26, Davide Cavalca dav...@geexbox.org wrote: Dear mentors, I am looking for a sponsor for my package python-ordereddict. * Package name : python-ordereddict Version : 1.1-1 Upstream Author : Raymond Hettinger * URL : http://pypi.python.org/pypi/ordereddict/ * License : MIT Section : python It builds these binary packages: python-ordereddict - drop-in substitute for Py2.7's new collections.OrderedDict The package appears to be lintian clean. The upload would fix these bugs: 603277 My motivation for maintaining this package is: some of the tools I use at work require this package. Plus, I've never packaged Python modules before, and this seems simple enough to start tackling them. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/python-ordereddict - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/python-ordereddict/python-ordereddict_1.1-1.dsc This is my first Python package, I'd appreciate reviews or comments on it. I would be glad if someone uploaded this package for me. I'm CCing fEnIo, who is my usual sponsor for the GeeXboX packages, and the debian-python list. what about joining the DPMT and maintain this module with the team [1] ? [1] http://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin Please also consider that for squeeze (the current under-development stable release) this package won't be included, and also in the release after squeeze (called wheezy) it seems it will be available only python 2.7 (even if the python maintainer hadn't spoken about it yet, quite surprisingly ah) . Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- 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/aanlktin9cjebds5g8ekrk_du8wkgl+621cc5pvona...@mail.gmail.com
Re: RFS: sima (autoqueue MPD client, find similar artists to queue)
On Fri, Nov 12, 2010 at 6:12 PM, chrysn chr...@fsfe.org wrote:
PYTHONPATH=/usr/share/sima/:$PYTHONPATH exec /usr/share/sima/mpd_sima.py $@
Please use this instead to avoid security issues caused by allowing
python to load modules from the working directory (which may have
untrusted files in it):
PYTHONPATH=/usr/share/sima/${PYTHONPATH:+:$PYTHONPATH} exec
/usr/share/sima/mpd_sima.py $@
c.f. all the recent LD_LIBRARY_PATH vulnerabilities for the reasoning
behind this.
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
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/aanlktintcjxo7tbr5hvigplgwo52ja0v+pb5zctpf...@mail.gmail.com
Re: RFS: kstars-data-extra-tycho2 (third try)
On Viernes 12 Noviembre 2010 09:28:00 Steffen Möller escribió: [...] we have a similar problem for bioinformatics, and so the bioinformatics community has come up with the getData (wiki.debian.org/getData) tool to help with the maintenance of public data resources. It would be lovely if you could give that a review with the hindsight of your particular demands. Tycho2 is already part of that, btw, it was my first test case :) Our strategy was to have applications add instructions to /etc/getdata.d on how to retrieve and pre/post-process the data that they work on. Have many thanks Steffen I'm not interested (at the moment) in how these data are updated or maintained, since I want to have a bunch of packages in shape for kstars usage in wheezy. After having the packages as intended, I will try to put them in consonance with the stardata-common framework ( https://alioth.debian.org/scm/browser.php?group_id=30498 ). After that, I could consider using getData, but the Tycho catalog is sort of stable, so I do not think it is appropiate. Anyway, thanks Noel er Envite signature.asc Description: This is a digitally signed message part.
Re: RFS: clipit
Sure, this warning is not a reason to block an upload. Many packages in the archive have this kind of warnings. They are not bugs but things that can be improved. ok, so is there anything else that I need to do, or will you upload it? I have searched a bit on google, but I couldn't find any neat solution to this problem, so I guess that'll have to stay for now (unless you want me to do something hackerish like a sed on the configure file after it has been created, to remove all references to -pthread, or something like that, because else I don't see how this could be solved). Best regards, Mit freundlichen Grüßen, Henzel Cristian -- 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/4cdd59b4.6000...@web-tm.com
Re: RFS: clipit
Hi, On Fri, 12 Nov 2010, Cristian Henzel wrote: Sure, this warning is not a reason to block an upload. Many packages in the archive have this kind of warnings. They are not bugs but things that can be improved. ok, so is there anything else that I need to do, or will you upload it? I responded on a specific point (which concerns me since I'm maintaining dpkg-shlibdeps), I have not looked the rest of the package and I don't intend to do it, sorry. Someone else should be sponsoring it. Cheers, -- Raphaël Hertzog ◈ Debian Developer ◈ [Flattr=20693] Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- 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/20101112154455.ga23...@rivendell.home.ouaza.com
Re: RFS: kstars-data-extra-tycho2 (third try)
On Miércoles 10 Noviembre 2010 21:01:22 Benoît Knecht escribió: [...] A few more comments: - Your debian/docs file is empty; did you mean to add something there, like README.source for instance? - I don't think you need a patch just to create a Makefile. You can achieve the same result with a debian/install file. - Your debian/rules contains a typo: %export DH_VERBOSE=1 instead of #export DH_VERBOSE=1; I'm also not sure why you're exporting DESTDIR. - You may want to rephrase the description in debian/control; the sentence Installing this package avoids the need for the users to each one download the catalog for itself sounds wrong (instead of itself, I would write themselves or him/herself). But something like Installing this package avoids the need for each user to individually download the whole catalog might be even clearer. I hope this helps. Cheers, Done. New version uploaded. http://mentors.debian.net/cgi-bin/sponsor- pkglist?action=details;package=kstars-data-extra-tycho2 Is the package ready? I'm most interested in the postinst since it is the point I'm trying to achieve. Thanks Noel er Envite -- 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/201011121612.36255.env...@rolamasao.org
Re: RFS: kstars-data-extra-tycho2 (third try)
Hi Noel, Noel David Torres Taño wrote: On Miércoles 10 Noviembre 2010 21:01:22 Benoît Knecht escribió: [...] [...] - I don't think you need a patch just to create a Makefile. You can achieve the same result with a debian/install file. - Your debian/rules contains a typo: %export DH_VERBOSE=1 instead of #export DH_VERBOSE=1; I'm also not sure why you're exporting DESTDIR. [...] Done. New version uploaded. You still have a patch in debian/patches creating a Makefile, and you are exporting DESTDIR in debian/rules although it works without it just as well. Is the package ready? I'm most interested in the postinst since it is the point I'm trying to achieve. I'll try and have a look at postinst later, but I'm not very familiar with debconf or the kstarsrc syntax, so I'll be of little assistance I'm afraid. Cheers, -- Benoît Knecht -- 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/20101112164724.ge6...@debian.lan
Re: RFS: clipit
I responded on a specific point (which concerns me since I'm maintaining dpkg-shlibdeps), I have not looked the rest of the package and I don't intend to do it, sorry. Someone else should be sponsoring it. Ohh, ok then, I got you wrong. Sorry about that. :-) I'm still figuring out how all of this works (I mean the procedure for finding a sponsor)... Best regards, Mit freundlichen Grüßen, Henzel Cristian -- 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/4cdd7a12.4020...@web-tm.com
Re: RFS: kstars-data-extra-tycho2 (third try)
On Viernes 12 Noviembre 2010 16:47:24 usted escribió: [...] You still have a patch in debian/patches creating a Makefile, and you My fault, didn't clean are exporting DESTDIR in debian/rules although it works without it just as well. Yes. Commented out. Not worth to really delete (it helps me to learn that I do not need it there). Is the package ready? I'm most interested in the postinst since it is the point I'm trying to achieve. I'll try and have a look at postinst later, but I'm not very familiar with debconf or the kstarsrc syntax, so I'll be of little assistance I'm afraid. It's like any other KDE foorc file. I've no doubts with the kstarsrc file itself, but the postinst procedure (or if I need a preinst, or prerm and/or postrm) to create (and/or remove and maintain) it. Uploaded again (same URL and version number) Thanks Noel er Envite -- 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/201011121817.49376.env...@rolamasao.org
Re: RFS: libvdpau (updated package)
On Thu, 11 Nov 2010 18:37:39 -0800, Russ Allbery wrote: Michael Gilbert michael.s.gilb...@gmail.com writes: Would anyone be willing to sponsor another RC-fix upload? This new libvdpau package fixes bug #603220: http://mentors.debian.net/debian/pool/main/l/libvdpau Thank you very much for your enthusiasm for fixing bugs for the release! But for the future, could you please wait at least a day or so after filing an RC bug before requesting someone sponsor an NMU for it? Usually the maintainers will want to at least look at the bug first. Why delay? The debdiff is in the bug report, and an NMU will get uploaded to DELAYED, so the maintainer has plenty of time to act; that is if they are indeed going to act. If not then the NMU goes through. I don't see the problem. Personally I'd prefer to not have to context-switch back to the problem a day later when I can deal with it all at once. Mike -- 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/20101112151049.93351adb.michael.s.gilb...@gmail.com
Re: RFS: libvdpau (updated package)
Hi Michael, On Thu, 11 Nov 2010 18:37:39 -0800, Russ Allbery wrote: Michael Gilbert michael.s.gilb...@gmail.com writes: Would anyone be willing to sponsor another RC-fix upload? This new libvdpau package fixes bug #603220: http://mentors.debian.net/debian/pool/main/l/libvdpau Thank you very much for your enthusiasm for fixing bugs for the release! But for the future, could you please wait at least a day or so after filing an RC bug before requesting someone sponsor an NMU for it? Usually the maintainers will want to at least look at the bug first. Why delay? The debdiff is in the bug report, and an NMU will get uploaded to DELAYED, so the maintainer has plenty of time to act; that is if they are indeed going to act. If not then the NMU goes through. I don't see the problem. I'm sure you are aware of [1]. The second item of Before doing an NMU states: Did you give enough time to the maintainer? Unless I got something wrong, there weren't more than a few hours between the bug report and the RFS. You'll surely understand that this wouldn't even allow people living in different time zones to _notice_ your bug report. Personally I'd prefer to not have to context-switch back to the problem a day later when I can deal with it all at once. While I do understand that your time is valuable and I do as well highly appreciate your contribution, please be aware that you are playing with other people's time. You'd need someone unfamiliar with the codebase review your changes and possibly do the sponsoring thereafter. Would you instead give the maintainer at least the chance to read it (by waiting for one day) you could possible avoid this. And, seriously, it's not too hard to keep an email in the draft folder for a day or so. Sending it out shouldn't require too much of a context to restore. Thanks a lot, Michael [1] http://www.debian.org/doc/developers-reference/pkgs.html#nmu pgpnyOeDf8J7S.pgp Description: PGP signature
Re: RFS: libvdpau (updated package)
On Fri, 12 Nov 2010 22:09:46 +0100, Michael Tautschnig wrote: Hi Michael, On Thu, 11 Nov 2010 18:37:39 -0800, Russ Allbery wrote: Michael Gilbert michael.s.gilb...@gmail.com writes: Would anyone be willing to sponsor another RC-fix upload? This new libvdpau package fixes bug #603220: http://mentors.debian.net/debian/pool/main/l/libvdpau Thank you very much for your enthusiasm for fixing bugs for the release! But for the future, could you please wait at least a day or so after filing an RC bug before requesting someone sponsor an NMU for it? Usually the maintainers will want to at least look at the bug first. Why delay? The debdiff is in the bug report, and an NMU will get uploaded to DELAYED, so the maintainer has plenty of time to act; that is if they are indeed going to act. If not then the NMU goes through. I don't see the problem. I'm sure you are aware of [1]. The second item of Before doing an NMU states: Did you give enough time to the maintainer? Unless I got something wrong, there weren't more than a few hours between the bug report and the RFS. You'll surely understand that this wouldn't even allow people living in different time zones to _notice_ your bug report. Michael, Thanks for your feedback. Does the Did you give enough time to the maintainer question have as much relevance toward the end of the freeze when timely RC bug fixes are paramount? Also, I wonder if those NMU guidelines are a bit antiquated nowadays since there is much broader acceptance of NMUs by maintainers? I can appreciate the make sure you don't break it and send the diff to the bug report guidelines, but is it really necessary to spend so much effort to contact the maintainer (bullets 2, 4, and 5)? Also, there is the Upload fixing only release-critical and important bugs: 5 days guideline which already gives the maintainer plenty of time to react. Also, there is the low threshold nmu list, which I had read some discussion where there was a push to make all packages low threshold. Not sure if that's gone anywhere though. Mike -- 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/20101112162604.e67bf0b9.michael.s.gilb...@gmail.com
Re: RFS: kstars-data-extra-tycho2 (third try)
Hi Noel, [...] I'm not interested (at the moment) in how these data are updated or maintained, since I want to have a bunch of packages in shape for kstars usage in wheezy. After having the packages as intended, I will try to put them in consonance with the stardata-common framework ( https://alioth.debian.org/scm/browser.php?group_id=30498 ). After that, I could consider using getData, but the Tycho catalog is sort of stable, so I do not think it is appropiate. [...] Would you mind to elaborate in what respect this is going to be more than your little pet package? Is kstars that often installed on true multi-user systems such that a quick hack is warranted? I find it very unfortunate that you refuse to integrate with existing Debian work right from the start. Given that your package is unlikely to make it into Squeeze anyway, IMHO there is no need to hurry. Why not prepare a nicely integrated package right away, what would you expect to gain from this first shot if you'll later plan to transition to stardata-common anyway? Please don't feel offended in any way, but I'm not going to sponsor such a package. Of course many others might have a very different attitude and will take it, so just don't count on me. Best regards, Michael pgpOsSQqqAvVD.pgp Description: PGP signature
Re: RFS: clipit
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2010-11-12 18:32, Cristian Henzel wrote: I responded on a specific point (which concerns me since I'm maintaining dpkg-shlibdeps), I have not looked the rest of the package and I don't intend to do it, sorry. Someone else should be sponsoring it. Ohh, ok then, I got you wrong. Sorry about that. :-) I'm still figuring out how all of this works (I mean the procedure for finding a sponsor)... You are in the middle of the process; it started when you sent the first RFS email. :) Anyhow, I had yet another look at your package; the copyright file does not Xyhthyx as the copyright holder of a lot of files. Even if he/she stopped developing on the project and you forked it, the original code is still (also) copyrighted by Xyhthyx. Which brings us to another interesting detail; parcellite (the forked project) has already been packaged for Debian by someone[1]. Have you talked to the current maintainer of parcellite? Andrew might be interested in replacing parcellite with clipit as well (with the upstream retiring). You got an perfect opportunity to get a co-maintainer and a sponsor here. :) There are a few bugs filed against parcellite; have you checked if clipit is affected by those? Fixing all of them is not a requirement for getting the package sponsored - I am just lazily forwarding bugs to upstream here ^^ Anyhow, once you fix the copyright issue I listed above and get in contact with Andrew about parcellite and clipit; I think this package is good to go. :) Best regards, Mit freundlichen Grüßen, Henzel Cristian ~Niels [1] http://packages.qa.debian.org/p/parcellite.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJM3bR1AAoJEAVLu599gGRCIYwP/i5wLQhRUliiV8OXgU69FPs4 svIPKl06/3fC60ThkmhDOntufpWeVp1K6JRIx58fcvC7NST2i5NG9BEzIycvG3yN Mt16i291gjY7y6yOxwr664a0QK4aXLQulYTcG4V1uC9LMLvM4LGp6/F49tKVl/fE pISXucvdcyA9QNE0ia75gImTUmRAGjRlutSCexmdLi8fWi8J71dUPFwLzaOPhhup jZ4h7jAM4SK7EjjZu/h1e+t8Dis3egDHubUU7k8pv9sRqBFAHz2KO9jdkCDSpnRp rjNi3lDL8QX8pH4mwb1Jj6P4FCczGdK2sJMtrt9/k2/NyoN2EUsp+8lvV4T8iTV4 HIdc0q7k+Q1o3W8PfZ9zSMT8lXXTTSHlFDOqHAL2anN5qJpKL70W1ir+WsD4Rnik BMJkJeDIVQqGpFEpm+pmci4zXHFMo9Tfad2PuVCPy1snKxmTqE4YVXQBA36LaBhH owGxBB/rH4AKzDN/FN1RO1w2GYnJnAIHZVO9HQ9fWVs/s8/Ot21OLiqG/6UWNzfa EQpgunzKSIYuBrdjDl2Rcmw+IjeY0+oCapFyXie9fNKK3YwVxDimHdnfVRs78T8k unhEl0bWDLm4lpzaMsy+zvkSo4F77mc0pWf69E/HQnkGqH0mIlHjG5sUdYzVWtbf +KtqNg3K2xMJ1mPp1Ryg =rRwR -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/4cddb476.7070...@thykier.net
Re: RFS: libvdpau (updated package)
On Thu, 11 Nov 2010 17:54:53 -0500, Michael Gilbert wrote: Hi, Would anyone be willing to sponsor another RC-fix upload? This new libvdpau package fixes bug #603220: http://mentors.debian.net/debian/pool/main/l/libvdpau Just FYI, I'm withdrawing this request since the maintainers are handling the issue. Thanks, Mike -- 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/20101112165254.49e0f791.michael.s.gilb...@gmail.com
Re: RFS: libvdpau (updated package)
Hi again, [...] I'm sure you are aware of [1]. The second item of Before doing an NMU states: Did you give enough time to the maintainer? Unless I got something wrong, there weren't more than a few hours between the bug report and the RFS. You'll surely understand that this wouldn't even allow people living in different time zones to _notice_ your bug report. Michael, Thanks for your feedback. Does the Did you give enough time to the maintainer question have as much relevance toward the end of the freeze when timely RC bug fixes are paramount? Also, I wonder if those NMU guidelines are a bit antiquated nowadays since there is much broader acceptance of NMUs by maintainers? I can appreciate the make sure you don't break it and send the diff to the bug report guidelines, but is it really necessary to spend so much effort to contact the maintainer (bullets 2, 4, and 5)? Also, there is the Upload fixing only release-critical and important bugs: 5 days guideline which already gives the maintainer plenty of time to react. Also, there is the low threshold nmu list, which I had read some discussion where there was a push to make all packages low threshold. Not sure if that's gone anywhere though. In my opinion, this case of yours has nothing whatsover got to do with NMUs, let alone the freeze. Technically, your approach is probably covered by policy, freeze, etc. But Debian is not a system of robots. I think this case is rather a matter of being polite. The BTS records a response from one of the maintainers within 2:37 hours. You could of course try to contact one of the maintainers on IRC, but other than that there's little chance you get a response in a project as global as Debian in less time. Best regards, Michael, who will go to bed and need more than 2:37 hours for another response :-) pgpzRjj9LMT5h.pgp Description: PGP signature
Re: RFS: libvdpau (updated package)
On Fri, 12 Nov 2010 22:58:23 +0100, Michael Tautschnig wrote: Hi again, [...] I'm sure you are aware of [1]. The second item of Before doing an NMU states: Did you give enough time to the maintainer? Unless I got something wrong, there weren't more than a few hours between the bug report and the RFS. You'll surely understand that this wouldn't even allow people living in different time zones to _notice_ your bug report. Michael, Thanks for your feedback. Does the Did you give enough time to the maintainer question have as much relevance toward the end of the freeze when timely RC bug fixes are paramount? Also, I wonder if those NMU guidelines are a bit antiquated nowadays since there is much broader acceptance of NMUs by maintainers? I can appreciate the make sure you don't break it and send the diff to the bug report guidelines, but is it really necessary to spend so much effort to contact the maintainer (bullets 2, 4, and 5)? Also, there is the Upload fixing only release-critical and important bugs: 5 days guideline which already gives the maintainer plenty of time to react. Also, there is the low threshold nmu list, which I had read some discussion where there was a push to make all packages low threshold. Not sure if that's gone anywhere though. In my opinion, this case of yours has nothing whatsover got to do with NMUs, let alone the freeze. Technically, your approach is probably covered by policy, freeze, etc. But Debian is not a system of robots. I think this case is rather a matter of being polite. The BTS records a response from one of the maintainers within 2:37 hours. You could of course try to contact one of the maintainers on IRC, but other than that there's little chance you get a response in a project as global as Debian in less time. OK, I'm going down the let the maintainer do his thing road right now since that is happening, but I don't see the harm from checking both roads first (the other road being fix it myself and get a sponsor). If the end goal is fixing bugs and getting the release out, I don't see how starting an RFS to achieve that goal was an impolite thing to do. In all actuality, any potential wasted time was stopped by the maintainer responding. The rest of the discussion has been my pondering of the current system and social norms, and whether those could be improved. Mike -- 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/20101112172227.ffc4a003.michael.s.gilb...@gmail.com
ClipIt -- Clipboard manager
Hello, I am working on a cliboard manager for GTK (the project is forked from parcellite) and have also packaged it for debian. Because you are the maintainer of the project I have forked my work from, I have been told by the debian mentors to contact you asking if you were interested in sponsoring/co-maintaining this program. I am not sure what details you'd need, but if you are interested please let me know and also tell me what exactly you want to know and I can provide any information. Thank you! -- Best regards, Mit freundlichen Grüßen, Henzel Cristian -- 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/4cddc259.8000...@web-tm.com
Re: RFS: clipit
Hello, Anyhow, I had yet another look at your package; the copyright file does not Xyhthyx as the copyright holder of a lot of files. Even if he/she stopped developing on the project and you forked it, the original code is still (also) copyrighted by Xyhthyx. I have fixed this in the changelog and uploaded another release. This was an omition on my part, no bad intentions. Thanks for pointing it out. Which brings us to another interesting detail; parcellite (the forked project) has already been packaged for Debian by someone[1]. Have you talked to the current maintainer of parcellite? Andrew might be interested in replacing parcellite with clipit as well (with the upstream retiring). You got an perfect opportunity to get a co-maintainer and a sponsor here. :) I have just sent him an e-mail about this and I'm awaiting his reply. There are a few bugs filed against parcellite; have you checked if clipit is affected by those? Fixing all of them is not a requirement for getting the package sponsored - I am just lazily forwarding bugs to upstream here ^^ Yeah, as far as I have seen, there are 2 bugs filed on parcellite in debian, and around 10-12 in ubuntu (from which half are actually feature requests). I have tackled the first bug filed in ubuntu, which I found pretty important (an OOM exception) in version 1.2.1, and the fix that I implemented, should also take care in part of the other bug (it was caused by the same big entries in the history). This fix is not perfect, but it should work in 99% of all cases and I will also think of a better way to do it in future (there also seem to be speed issues with such big entries in the GTK menus). (this fix should also take care of one or two of the bugs filed in ubuntu) Anyhow, once you fix the copyright issue I listed above and get in contact with Andrew about parcellite and clipit; I think this package is good to go. :) That's good news... :-) Thank you very much for your reply! Best regards, Mit freundlichen Grüßen, Henzel Cristian -- 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/4cddc8de.6070...@web-tm.com
Re: ClipIt -- Clipboard manager
Sorry, I have meant this to be in the same thread I have started earlier, namely RFS: clipit. If someone could move it there, I would be very thankful. -- Best regards, Mit freundlichen Grüßen, Henzel Cristian -- 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/4cddcab5.4000...@web-tm.com
Re: RFS: kstars-data-extra-tycho2 (third try)
On Viernes 12 Noviembre 2010 21:37:32 Michael Tautschnig escribió: Hi Noel, [...] I'm not interested (at the moment) in how these data are updated or maintained, since I want to have a bunch of packages in shape for kstars usage in wheezy. After having the packages as intended, I will try to put them in consonance with the stardata-common framework ( https://alioth.debian.org/scm/browser.php?group_id=30498 ). After that, I could consider using getData, but the Tycho catalog is sort of stable, so I do not think it is appropiate. [...] Would you mind to elaborate in what respect this is going to be more than your little pet package? Is kstars that often installed on true multi-user systems such that a quick hack is warranted? I do not want a quick hack but a truly good package that allows users to have their systems fully installed through Debian packaging systems. I do not know why one needs to download data from the network for a program that is packaged: kstars data is not a non-distributable PDF reader to need an installer outside the packaging system. Is it? I do not want these packages to be my pet packages, and I would very gladly leave them on hands of Debian Qt/KDE Maintainers but I think they're actually a bit overloaded. I would be happy to maintain these packages from inside that team, but I want to have them in shape before that. About how often is kstars installed in true multiuser systems, one system is enough for me to say that there is a problem, but I've been sysadmin at universitary computer rooms, and numbers are quite higher that one. But, To make a long story short: I saw a need, and I'm working towards a solution. It is up to you to be happy with it or not, but it works for me and can work for others. I find it very unfortunate that you refuse to integrate with existing Debian work right from the start. Given that your package is unlikely to make it into Squeeze anyway, IMHO there is no need to hurry. Why not prepare a nicely integrated package right away, what would you expect to gain from this first shot if you'll later plan to transition to stardata-common anyway? I agree that there is no hurry, but I'm working on the set to have it in shape for wheezy. Would you prefer for me to wait? About the transition to stardata-common, the problem with that is that I'm still not convinced that it is compatible with this package set. The source for this version of the Tycho2 package is not the original data as-is but a subset of it, but even the stardata-common concept may be not applicable to other packages of the set like ephemerides, DST rules, images or icons, as stardata-common is Common framework for handling stardata catalogues in Debian and not anything similar to Common framework for handling astronomical and related data in Debian. It may be that four of the nine packages in sight (two of them are not free, so actual number is two) can happen to be under the scope of stardata-common, the other five are not catalogs at all. I would be happy (again) of working them inside that framework, as I've discussed already with Javier, but it is still to be seen if it is possible. I still have to study the project and the kstars data format in order to decide if it is possible, and both things will require a lot of time. These packages, in turn, solve the problem and don't create new ones, so why not to have them? They will be integrated later, _if possible_. Why not start asking Debian Qt/KDE Maintainers to work with upstream in order to get Gliese and Yale catalogs out of actual kstars-data package? I would do that, but having the proposed packages in Debian in order to solve the actual problem is of higher importance to me than diving into stars.dat, namedstars.dat and unnamedstars.dat from that package to remove the stars tha are actually in the gliese and yale packages. Please don't feel offended in any way, but I'm not going to sponsor such a package. Of course many others might have a very different attitude and will take it, so just don't count on me. I'm not offended: I try to learn from everybody's comments, either constructive or not, but it seems to me (personal humble opinion) that you missed the point of these packages. I think that a good enough solution is better than an asimptotycally unreachable perfect one, moreover if it is later improvable, and even if the perfect solution is actually reachable but in a long term. Don't sponsor these packages, I hope others will have better sight on the problem I saw (which, by the way, has actually happened to have collateral benefits for the upstream KStars team out of Debian, as they have re-checked the License of their web-distributed Tycho2 and USNO Nomad files). Best regards, Michael Thanks for your comments, I've learned from them. Noel er Envite signature.asc Description: This is a digitally signed message part.
RFS: gallery-uploader 2.3-1
Dear mentors, I am looking for a sponsor for the new version 2.3-1 of my package gallery-uploader. It builds these binary packages: gallery-uploader - graphical tool to upload pictures and videos to Gallery The package appears to be lintian clean. The upload would fix these bugs: 576414 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/g/gallery-uploader - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/g/gallery-uploader/gallery-uploader_2.3-1.dsc I would be glad if someone uploaded this package for me. Out of template: Piotr Ożarowski sponsored past uploads of the package, but he's currently in quasi vacation. If anyone is interested in sponsoring/reviewing but has no access to a gallery instance to test, please contact me in private so I can provide him the credentials for a test account. Kind regards Pietro Battiston signature.asc Description: This is a digitally signed message part
RFS: pycam
Dear mentors, I am looking for a sponsor for my package pycam. * Package name: pycam Version : 0.4-1 Upstream Author : Lode Leroy, Lars Kruse (that's me) * URL : http://pycam.sourceforge.net * License : GPL3 Section : python It builds these binary packages: pycam - CAM program library written in Python PyCAM is a toolpath generator for 3-axis machines (e.g. mills). The package appears to be lintian clean. I am currently one of the maintainers of the clearsilver package in Debian. I would like to see PyCAM included in Debian, because: 1) it would be the first toolpath generating program in the repository (python-opencam is only a library and currently not usable) 2) I want to simplify the life of PyCAM's users :) 3) I want to get more involved in Debian development The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/pycam - Source repository: deb-src http://mentors.debian.net/debian unstable main - dget http://mentors.debian.net/debian/pool/main/p/pycam/pycam_0.4-1.dsc I would be glad if someone uploaded this package for me. cheers, Lars -- 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/20101113011649.38b54...@erker
RFS: 9menu (updated package, Second try)
Dear mentors, I am looking for a sponsor for the new version 1.8-4 of my package 9menu. It builds these binary packages: 9menu - Creates X menus from the shell The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/9/9menu - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/9/9menu/9menu_1.8-4.dsc I would be glad if someone uploaded this package for me. Kind regards daniel echeverry http://www.rinconinformatico.net
RFS: libgis - virtual globe library
Dear mentors, I am looking for a sponsor for my package libgis. * Package name: libgis Version : 0.4.1-1 Upstream Author : Andy Spencer (myself) * URL : http://lug.rose-hulman.edu/code/projects/libgis/wiki * License : GPL-3+ Section : science It builds these binary packages: libgis - A Virtual Globe library libgis-bin - Example programs for libgis libgis-dev - Development files for libgis libgis-doc - HTML documentation for libgis The package appears to be lintian clean. My motivation for maintaining this package is: I am the primary developer (upstream) for this package and would like to make it easier to non-technical users to install and use. libgis is a Virtual Globe library which uses OpenGL to render an image of the earth using satellite and terrain data from publicly accessible servers. This is similar in concept to Google Earth and NASA World Wind, except implemented as a library. I am also working on a program called AWeather which I plan on packaging as well. The development of AWeather and libgis is closely tied and, as far as I know, aweather is currently the only program that uses libgis. Note: I am new to Debian and Debian packaging. This is my first attempt at putting a package together for libgis so it will probably need some work before it's all ready, especially since it's a library. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/libgis - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libgis/libgis_0.4.1-1.dsc I would be glad if someone could review this package and provide advice on anything that needs to be improved, and eventually uploaded it for me as well. Kind regards Andy Spencer pgpYiUNmjW3Xo.pgp Description: PGP signature
