Re: RFS: mail-notification (updated package; NMU for RC bugs among others)
Hi Michael, On Wed, 07 Sep 2011 02:43:37 +0200, Michael Biebl bi...@debian.org wrote: Am 07.09.2011 00:57, schrieb Stephen Kitt: I am looking for a sponsor for the package mail-notification. This update would fix a couple of RC bugs (the usual Evolution updates, which also require a switch to GTK+ 3); Hm, the package still build-depends on libgtk2.0-dev, is that an oversight? It's only needed for gtk-builder-convert; I suppose I could just provide the .ui files in a patch, but I'd rather build everything from the original sources as far as possible. Also, the package seem to still use a lot of deprecated GNOME 2 libs, like libgnomeprintui2.2-dev, libgnomevfs2-dev and libgnome2-dev. Are they still required? If so, you should consider porting them to the newer interfaces, like GVFS. OK - do you have any pointers to migration documentation? The main intent of the NMU was to fix the FTBFS, not really overhaul the whole package, but it would indeed be better to avoid leaving predictable future FTBFSes... Thanks for looking at the package, Stephen -- 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/20110907081243.098fc...@sk2.org
Re: RFS: mail-notification (updated package; NMU for RC bugs among others)
On Wed, Sep 07, 2011 at 08:12:43AM +0200, Stephen Kitt wrote: On Wed, 07 Sep 2011 02:43:37 +0200, Michael Biebl bi...@debian.org wrote: Am 07.09.2011 00:57, schrieb Stephen Kitt: I am looking for a sponsor for the package mail-notification. This update would fix a couple of RC bugs (the usual Evolution updates, which also require a switch to GTK+ 3); [...] Also, the package seem to still use a lot of deprecated GNOME 2 libs Are they still required? If so, you should consider porting them to the newer interfaces, like GVFS. OK - do you have any pointers to migration documentation? The main intent of the NMU was to fix the FTBFS, not really overhaul the whole package, but it would indeed be better to avoid leaving predictable future FTBFSes... It seems strange to me to have changes of this scale in a NMU. Wouldn't you rather either hijack the package or talk to Liu Qi about adding yourself as a co-maintainer? Especially since it's your 5th NMU of this package in a row, you're kind of its official non-maintainer :p -- 1KB // Yo momma uses IPv4! -- 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/20110907083411.ga19...@angband.pl
dh_python2: error: no such option: --with
Dear mentors, I am trying to use the new dh for the gdcm package, as seen at: http://anonscm.debian.org/viewvc/debian-med/trunk/packages/gdcm/trunk/debian/rules?view=markup However this package fails to build with: Unknown option: with dh_icons: warning: ignored unknown options in DH_OPTIONS dh_perl -O--parallel Unknown option: with dh_perl: warning: ignored unknown options in DH_OPTIONS dh_python2 -O--parallel Usage: dh_python2 -p PACKAGE [-V [X.Y][-][A.B]] DIR [-X REGEXPR] dh_python2: error: no such option: --with make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 Has anyone seen this error before ? What do I need to do ? Thanks much, -- Mathieu -- 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/CA+7wUswb2cm7ZBRep=esxj4evioc3ju4tfg+dd7w9q9+mn-...@mail.gmail.com
Re: dh_python2: error: no such option: --with
On Wed, 7 Sep 2011 11:23:27 +0200, Mathieu Malaterre wrote: Dear mentors, I am trying to use the new dh for the gdcm package, as seen at: http://anonscm.debian.org/viewvc/debian-med/trunk/packages/gdcm/trunk/debian/rules?view=markup [..] dh $@ --parallel --with=cli --with=python2 --with options go right after the target -- and they can be grouped together. So either: dh $@ --with cli --with python2 --parallel or: dh $@ --with cli,python2 --parallel -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature
Re: dh_python2: error: no such option: --with
Le Wed, Sep 07, 2011 at 11:23:27AM +0200, Mathieu Malaterre a écrit : Dear mentors, I am trying to use the new dh for the gdcm package, as seen at: http://anonscm.debian.org/viewvc/debian-med/trunk/packages/gdcm/trunk/debian/rules?view=markup Hi Mathieu, shouldn't it be --with cli,python2 ? Cheers, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- 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/20110907093817.gc26...@merveille.plessy.net
Re: dh_python2: error: no such option: --with
On Wed, Sep 7, 2011 at 11:37 AM, David Paleino da...@debian.org wrote: --with options go right after the target -- and they can be grouped together. [...] dh $@ --with cli,python2 --parallel Exact same error, using: %: dh $@ --with cli,python2 --parallel Unknown option: with dh_icons: warning: ignored unknown options in DH_OPTIONS dh_perl -O--parallel Unknown option: with dh_perl: warning: ignored unknown options in DH_OPTIONS dh_python2 -O--parallel Usage: dh_python2 -p PACKAGE [-V [X.Y][-][A.B]] DIR [-X REGEXPR] dh_python2: error: no such option: --with make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 Let's move on to the next suggestion -- Mathieu -- 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/CA+7wUszu2OL2HN_WqmcvmprGyGfDU_P--Afo9ZpAAHBCGt=a...@mail.gmail.com
Re: RFS: mail-notification (updated package; NMU for RC bugs among others)
On Wed, Sep 07, 2011 at 10:34:11AM +0200, Adam Borowski wrote: Hi, OK - do you have any pointers to migration documentation? The main intent of the NMU was to fix the FTBFS, not really overhaul the whole package, but it would indeed be better to avoid leaving predictable future FTBFSes... It seems strange to me to have changes of this scale in a NMU. Wouldn't you rather either hijack the package or talk to Liu Qi about adding yourself as a co-maintainer? Especially since it's your 5th NMU of this package in a row, you're kind of its official non-maintainer :p I've uploaded one the NMUs in the past and last time Liu ACK'ed the NMU because he had not enough time to care at the time. I think I already proposed to Steve to take over the whole thing upstream because it's dead otherwise. Steve and some other people from other distros currently pass around patches and the mess is getting bigger every other month. :-/ Sven -- 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/20110907100857.gc2...@sho.bk.hosteurope.de
Re: dh_python2: error: no such option: --with
On Wed, 7 Sep 2011 12:04:59 +0200, Mathieu Malaterre wrote: %: dh $@ --with cli,python2 --parallel Unknown option: with dh_icons: warning: ignored unknown options in DH_OPTIONS dh_perl -O--parallel Unknown option: with dh_perl: warning: ignored unknown options in DH_OPTIONS dh_python2 -O--parallel Usage: dh_python2 -p PACKAGE [-V [X.Y][-][A.B]] DIR [-X REGEXPR] dh_python2: error: no such option: --with make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 Then it's (probably) a bug in dh_python2 in how it handles unknown options. This is a drawback of dh7, IIRC: the same options are passed to all dh_* helpers, and they should cope with them. See how dh_icons and dh_perl handle the unknown (for them) option --parallel. David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature
Re: dh_python2: error: no such option: --with
Hi, On Wed, Sep 7, 2011 at 12:16 PM, David Paleino da...@debian.org wrote: On Wed, 7 Sep 2011 12:04:59 +0200, Mathieu Malaterre wrote: %: dh $@ --with cli,python2 --parallel Unknown option: with dh_icons: warning: ignored unknown options in DH_OPTIONS dh_perl -O--parallel Unknown option: with dh_perl: warning: ignored unknown options in DH_OPTIONS dh_python2 -O--parallel Usage: dh_python2 -p PACKAGE [-V [X.Y][-][A.B]] DIR [-X REGEXPR] dh_python2: error: no such option: --with make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 Then it's (probably) a bug in dh_python2 in how it handles unknown options. This is a drawback of dh7, IIRC: the same options are passed to all dh_* helpers, and Looks like this has been reported: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638679 I did not understand at first the relation, now this is clear. they should cope with them. See how dh_icons and dh_perl handle the unknown (for them) option --parallel. I do not understand however your above suggestion. Do you want me to provide a patch for dh-python2 ? Thanks -- Mathieu -- 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/ca+7wusw50+aauvq5dwatr4g0aef9sd_12hybg4aeehv+tpx...@mail.gmail.com
Re: dh_python2: error: no such option: --with
Hi, you can remove this to workaround the dh_python2 issue: # require to get dh_clideps include /usr/share/cli-common/cli.make the values set in this include are default now so it is not needed anymore when you pass --with cli to dh. Best Regards, Julian Taylor signature.asc Description: OpenPGP digital signature
[solved] Re: Packaging php app/scripts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/09/11 19:12, Игорь Пашев wrote: # find . ./src ./src/index.php ./debian ./debian/control ./debian/rules ./debian/changelog ./debian/my-pkg.install ./debian/compat ./debian/copyright sic well, thx for your help with pointing me to mistake I made trying to go on shortcut btw thx to all who replied in this topic - -- |_|0|_| | |_|_|0| Heghlu'Meh QaQ jajVam | |0|0|0| kuLa - | gpg --keyserver pgp.mit.edu --recv-keys 0xC100B4CA -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOZ1RCAAoJEOqHloDBALTKQfEIAJHPuCRjSrF/oNTWs0mnmV81 SdOEkCQmenYkdJ1uQNpCCW4wEPvvpohV911lDYHrhbANG/b1oAxBCt09jLRbCUUN PTEWJIq5Zw0vQ8FGXulQBMzo2usPK6yr6vsWm/Udsi6nlEwafASSJbF8Fpzm00Om wscIJ/Lv8UWK4z83Wb5WAC15xLqUuWtbnvb+uK6wAf9GmTSfVwIyj6v+hUu/TZNI r4XcuytUENG1NyoA1xEOyV9Qd2D60gqldi59AHTt/mIv/YCCpl9czfa9KVKERpps 4k59V06tCGCJxOnG0QBhHYXXYKuNcaluJ9MnNsnqPgpQ/atxWVkaHmzrTgWaPB4= =8t+p -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/4e675442.5020...@kulisz.net
Re: dh_python2: error: no such option: --with
On Wed, Sep 7, 2011 at 12:32 PM, Julian Taylor jtaylor.deb...@googlemail.com wrote: Hi, you can remove this to workaround the dh_python2 issue: # require to get dh_clideps include /usr/share/cli-common/cli.make the values set in this include are default now so it is not needed anymore when you pass --with cli to dh. *much* better. Thanks for catching this ! -- Mathieu -- 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/ca+7wusxyjq-7fznwe6t7mhhze77gc2-lktbo3uhcwlh3xpd...@mail.gmail.com
Re: Tracking RFSs as bugs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Paul, On 06.09.2011 16:49, Paul Wise wrote: I'm concerned that this might turn out about as useful as filing an RFP bug against wnpp; not very useful at all. I am not sure, a mailing list is better suited. I was not thrilled to use the BTS when I heard about that idea first, but the more I think about, the more attractive it gets. To be honest, the current procedure does not work very well either. Some RFS mails are lost in space due to the high volume of requests. The same happens for some comments when the maintainer files a new RFS thread instead of replying to existing reviews and so on. Finally, nobody knows simple things as how many packages are out there which are seeking an uploader, or what's the status of a particular RFS, without digging mailing list archives. By using the BTS all those features come for free: * We can merge, retitle, reassign bugs. * We can tag and categorize bugs (pending, reviewed, ...) * We can easily see which packages are awaiting a sponsor (ok, that could be seen on Debexpo as well - but I don't think the Needs a sponsor flag ever helped to find one.) * You can finally close bugs with wontfix i.e. wontupload instead of politely hoping the requester goes away. * We can track the entire history of an upload easily at one sight. Just open the bug. * Its easy to tell Debexpo about the status of a package - it can just use SOAP to query the BTS, instead of guessing/parsing mails from mentors and devel-changes ... * No more broken/incomplete RFS mails anymore (reportbug could take care, or even Debexpo could be filing the bug) * Its convenient and controllable through a handy mail interface to sponsors * Having the debian-mentors mailing list as pseudo package owner still discloses every RFS mail to the public easily. I can live to keep things as is, but please let's decide NOW, BEFORE I spent a lot of time for writing interfaces in Debexpo to either solution. - -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJOZ3dDAAoJEMcrUe6dgPNtMnMP/3pqdRQb30iEfB3/vTBjPQXl B8ORKdRHGFs+5gEgXdeUBRBz6hTKGu62xIChcnsm3FadJiHmH9IgfKo12kBLtq/A nhutsFoONGW1hJKs45BzqWXKRMtMXqjP/c1Ek4Evq75T69KQ+dSIrU03dinUVEqg nyEgRs1tWnDoKl6klID3IEdtJZUS6oDnuiOQy7iF/Aodxq7OrMygLnaM5/P2MUOX 95cIsNAxA9LGrFi/Yw3uV3Xr0DVcqWkkZd/wdchaMvHJWX0EHn+tJKkoZk8HJOfU I8bOAyrWv15eSnn36e/0FIJkBGTKJkS/EsRGkaFIsV8kxPmKZIKpJHqWp7QKDimM 7/xp2v3kYsLs3AXt5P1uaHt90/IlKjj1wEbLSmg3/YkzvMEdU2jtFHMLAxfvL7Yb ee/1F84cvROxnv6xE1l+76pxI6rWEDGqzFtWznL3gi8uTzQA5UTk9lwRVXgtLla/ t3taet8jhhQMEfbkM7bJDxSXbMEUED+8yk0IbSKnLEh6XvkKDJaFyROFk332iMT2 AEjLRBGb8uq3We/GSpYc7q18kjGyLkC6F7Hjfpux86MYeHK5x/Nji75ViLH5l1/0 c4IiY3TvvBxo/RsZ7CFyK8qUzD9b/7fjxoy4UQEWh16GzWxkyAFb0yi/P3a09F/Z FRLT3JftDjmm1bEY2+/W =o+0W -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/4e677743.3090...@toell.net
adopting a package
I am adopting an orphaned package (ircii), I have changed the title to ITA, and I have also changed the owner using cont...@bugs.debian.org. As the last package built was from 2008, I have started work on building the 2011 version, patching the build system etc. I also have an account on mentors.debian.org. Do I have to find a sponsor for this package? How do I proceed? -- 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/20110907103714.GA26683@darkness
Re: adopting a package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Shaun, thanks for your interest to help Debian. On 07.09.2011 12:37, Shaun Silk wrote: Do I have to find a sponsor for this package? How do I proceed? Yes, you need a sponsor. Please read [1][2] to get the idea. You may also find the New Maintainer's Guide helpful [3]. [1] http://mentors.debian.net/intro-maintainers [2] http://wiki.debian.org/SponsoredMaintainer [3] http://www.debian.org/doc/manuals/maint-guide/ - -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJOZ36LAAoJEMcrUe6dgPNtwTgQALRIm4nE1wMHBpYC7TyAbOUl qAA9Qqhn+PIJL18VZ0vUm9TiVcsSxJBLZPVWTi1uW6N81kr5tlt9WO2MjaBPay9g V7lwO67yhbjfY5bLPCkreTfxVYCsTvkbWXldOsg8XjnY4BAbv0wsEI8FQFsYGM8b JXJHiJfurJ4VqC0E4QeLVMZSs5FuZj41meUkl1+jzP1m2dbOj5sZa2fAs2EERzRo b7QhGbr34+k3nydh9oaAuU346nRyI3lMKp/hif4ADuXBpdt4scQLLILnB2p+/er9 rn/yRbcgheMyZUkukLPdj7ZMg+A5cMGPPkfgxs4HQRJUllHqFFL3CB0qhjQK4uU9 PcWI5DohJinWO/0TOTor+qPQD5XjUBql4xAU9sWhFul8LipljluOyQlqSXBDHBiR hyNhh6HGHCfXyzW/tEmvb6QjlPmcl2apL+7dYsWnRg0Cj+Ss+CpH60XYWPWSusoP 54V6JkjWjpZpdHLJ1P7ccfqnjl2NNaNE1WWXz2LgQEaHthuMtGRyLGe3tyDka1al imR9N16ZUc3UNiLc36ZZXKmVp4jFJquHHPb6UdWdK2s47OLIw5UCp8wcIlQrJcoP zj6uQTmHXuKhR98a6yXU/1Z2mj06HbcR2M/HllCLtOVWMrogmP3NV0KsKY8BO1vz FPaPn4php+y2iFQU3PE/ =aqky -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/4e677e8c.6090...@toell.net
RFS: slurm 0.4.0-1
Dear mentors, I am looking for a sponsor for my package slurm. * Package name: slurm Version : 0.4.0-1 * License : GPL-2 Section : net It builds those binary packages: slurm - Realtime network interface monitor To access further information about this package, please visit the following URL: http://mentors.debian.net/package/slurm Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/s/slurm/slurm_0.4.0-1.dsc I would be glad if someone uploaded this package for me. This release adds support for GNU/kFreeBSD and fixes a ftbfs bug in Ubuntu Oneiric. Kind regards, Matthias Schmitz -- 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/20110907162105.7d7af...@localhost.aus.der.hoelle
Re: spotweb_0~20110903+gitab1d95b4-1_i386.changes REJECTED
Michael, others, Sorry for the delay after the NAK from ftp-masters. I've prepared a new version, but there is something I'm now quite sure about. Some of the compressed .js and .css files in the upstream source are not accompanied by their uncompressed originals. I've now put those in debian/extra_sources, to be able to generate the proper compressed files at package build time. Is that the proper way to handle this? Please have a look at the new version, the .dsc is at http://mentors.debian.net/debian/pool/main/s/spotweb/spotweb_0~20110903+gitab1d95b4+dfsg-1.dsc Regards Jan-Pascal -- 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/6f4e3d37d4b8c4ef8c094d365489d819.squir...@www.vanbest.eu
Re: spotweb_0~20110903+gitab1d95b4-1_i386.changes REJECTED
On Wed, Sep 7, 2011 at 4:42 PM, Jan-Pascal van Best wrote: Some of the compressed .js and .css files in the upstream source are not accompanied by their uncompressed originals. I've now put those in debian/extra_sources, to be able to generate the proper compressed files at package build time. Is that the proper way to handle this? That is a reasonable workaround for the case where upstream refuses to do the compression at build time. Much better would be to get upstream to remove the compressed versions from their source tarballs and VCS repository (if present) and generate them at build time while also providing compressed versions in a separate file for users of those. -- 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/CAKTje6GaxqsgV-CM3=cla5lvucabjldg+d8wbpotfbnkg5h...@mail.gmail.com
Re: RFS: sxiv
* Daniel Echeverry epsilo...@gmail.com, 2011-09-04, 17:14: To access further information about this package, please visit the following URL: http://mentors.debian.net/package/sxiv Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/s/sxiv/sxiv_0.9-1.dsc $ tar -tvvf sxiv_0.9.orig.tar.gz | grep '/debian/$' drwxr-xr-x epsilon/epsilon 0 2011-07-07 21:19 sxiv-0.9/debian/ Huh? -- Jakub Wilk -- 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/20110907170724.ga3...@jwilk.net
Re: Tracking RFSs as bugs
On 05/09/11 at 15:12 -0400, Michael Gilbert wrote: Hi, I've been thinking about how mentors works lately (after watching Asheesh's debconf11 talk). It seems like the 4 day response effort worked somewhat well for a while, but kind of tailed off, and I've been pondering what could be done instead that would have some staying power. I've noticed that the release team has a lot of success addressing their issues in a rather timely manner. I think that this success comes from the fact that they treat all of the items they need to accomplish as bugs [0]. So, as requests get old, they notice that and do something about it (or they just close it out if the submitter isn't responsive). Anyway, I think mentors could greatly benefit from a similar work flow. So, I was wondering if there were any thoughts on setting up a mentors.debian.net pseudo-package [1]? It seems like all of the existing ones are debian.org features, so I'm not sure if that would require mentors becoming an official .org service first or not? Anyway, I think this could be a really significant improvement to the mentors culture. The BTS provides a good way to track requests. But mentors.d.n does, too. On the other hand, the BTS doesn't have a useful interface to search, filter and sort RFSes based on various criterias, such as: - is the package already in Debian? (sponsoring a second upload is easier) - did I sponsor the previous upload? - is the package related to Ruby (easy to determine by grepping build-depends and depends) - ... all of this can easily be implemented on mentors.debian.net, but cannot be added to a BTS pseudo-package. So I don't see the point of using a BTS pseudo-package instead of mentors.d.n. (I also don't see the point of using mentors.d.n together with a BTS pseudo-package.) Additionally, it's very important to note that not all packages should eventually be uploaded, so the fact that some packages never get sponsored is a feature. Debian doesn't want to contain every piece of free software ever written, because some of them have better alternatives already in Debian, for example. How would you deal with that with a BTS pseudo-package? After some time, there will be a few hundred RFSes that should never ever be uploaded to Debian, but are still open. Who gets to decide that they can be closed? Lucas -- 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/20110907173901.ga23...@xanadu.blop.info
Re: Tracking RFSs as bugs
On Wednesday, September 07, 2011 09:53:07 AM, Arno Töll wrote: Hi Paul, On 06.09.2011 16:49, Paul Wise wrote: I'm concerned that this might turn out about as useful as filing an RFP bug against wnpp; not very useful at all. I am not sure, a mailing list is better suited. I was not thrilled to use the BTS when I heard about that idea first, but the more I think about, the more attractive it gets. To be honest, the current procedure does not work very well either. Some RFS mails are lost in space due to the high volume of requests. The same happens for some comments when the maintainer files a new RFS thread instead of replying to existing reviews and so on. Finally, nobody knows simple things as how many packages are out there which are seeking an uploader, or what's the status of a particular RFS, without digging mailing list archives. By using the BTS all those features come for free: * We can merge, retitle, reassign bugs. * We can tag and categorize bugs (pending, reviewed, ...) * We can easily see which packages are awaiting a sponsor (ok, that could be seen on Debexpo as well - but I don't think the Needs a sponsor flag ever helped to find one.) * You can finally close bugs with wontfix i.e. wontupload instead of politely hoping the requester goes away. * We can track the entire history of an upload easily at one sight. Just open the bug. * Its easy to tell Debexpo about the status of a package - it can just use SOAP to query the BTS, instead of guessing/parsing mails from mentors and devel-changes ... * No more broken/incomplete RFS mails anymore (reportbug could take care, or even Debexpo could be filing the bug) * Its convenient and controllable through a handy mail interface to sponsors * Having the debian-mentors mailing list as pseudo package owner still discloses every RFS mail to the public easily. I can live to keep things as is, but please let's decide NOW, BEFORE I spent a lot of time for writing interfaces in Debexpo to either solution. After reading all of the above I see that there are a lot of benefits to having RFS mails in the BTS. And it's interesting in that new packages already get started via ITP reports to the BTS, so this would basically be an extension of normal procedure. The only concern I have is BTS performance from all of the extra devel traffic, which I suspect would be more significant than for normal bug reports. So the logical thought is whether it would make sense to have a separate BTS for ITP/RFS/etc tracking rather than the normal BTS or not, since these wouldn't necessarily need to be handled in the same way that normal bug reports do. On the other hand setting up another BTS would be a lot of work and require infrastructure, so this then goes back to the expected performance hit of devel traffic using the standard BTS would cause. -- Chris -- Chris Knadle chris.kna...@coredump.us signature.asc Description: This is a digitally signed message part.
Re: RFS: slurm 0.4.0-1
Matthias Schmitz matth...@sigxcpu.org wrote on 2011-09-07 16:21: * Package name: slurm Version : 0.4.0-1 * License : GPL-2 Section : net Thanks for updating this package. It seems you have started as upstream by yourself, too - right? It would be very nice to see a home of the source package files. E.g. you could use Alioth for this. Because of this changes please update copyright file. E.g. the download link does not show the source package files. And you should change to DEP-5 format. It would also be nice if you update your git repository to 0.4.0-1. Thank for your work! --- Have a nice day. Joachim (Germany) -- 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/20110907201225.0bb6e...@jupiter.home
Re: RFS: django-autoslug
* Jocelyn Delalande deb...@hackriculture.fr, 2011-09-06, 01:46:
First of all, as it's my initial post here ; so I just wanted to say Hi
to you all, I hope we'll happy-hack together :-). I'll mainly work with
Python packaging, as it's a language I know well, love fairly. I use
some nice pieces of python software missing just the deb packaging to
hit the full awesomeness rank, sounds like a mission for me :-)
For future, debian-pyt...@lists.debian.org might a better place to ask
for sponsorship of packages like this.
To access further information about this package, please visit the
following URL:
http://mentors.debian.net/package/django-autoslug
Alternatively, one can download the package with dget using this command:
dget -x
http://mentors.debian.net/debian/pool/main/d/django-autoslug/django-autoslug_1.4.1-1.dsc
I would be glad if someone uploaded this package for me.
I tried to stick to naming used with other django apps in debian.
According to Python Policy 2.2, the binary package name should be
python-autoslug. (Now, you may say that's too generic and that the
package name should include django - but so should upstream module
name...)
debian/control:
- Remove XB-Python-Version, it servers no purpose.
- More importantly, remove Provides: ${python:Provides}. See
http://lists.debian.org/debian-python/2011/03/msg00139.html for
rationale.
- Short description is not a sentence, so it should not end with a dot.
See Developer's Reference 6.2.2.
debian/python-django-autoslug.preinst:
- It doesn't make sense. You package was never affected by #479852
(besides, the bug is already fixed in stable).
debian/rules:
- Please consider removing useless comments.
- Unexporting anything is not necessary, the *FLAGS don't affect your
package by any means.
debian/watch:
- Please write one. That shouldn't be hard, as the tarballs are available
at PyPI.
autoslug/__version.py:
- So is it 1.3.5 or 1.4.1 after all?
autoslug/tests.py:
- Please run them at build time.
You might want consider joining the Python Modules Packaging Team:
http://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin
--
Jakub Wilk
--
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/20110907182142.gb6...@jwilk.net
Re: Tracking RFSs as bugs
[...] The BTS provides a good way to track requests. But mentors.d.n does, too. On the other hand, the BTS doesn't have a useful interface to search, filter and sort RFSes based on various criterias, such as: - is the package already in Debian? (sponsoring a second upload is easier) - did I sponsor the previous upload? - is the package related to Ruby (easy to determine by grepping build-depends and depends) - ... What about usertags and usercategories? I believe the BTS could do a really good job here if used in the right way. all of this can easily be implemented on mentors.debian.net, but cannot be added to a BTS pseudo-package. So I don't see the point of using a BTS pseudo-package instead of mentors.d.n. (I also don't see the point of using mentors.d.n together with a BTS pseudo-package.) In my opinion the BTS and mentors.d.n could serve two somewhat distinct parts of the process: clearly we need a space that packages can be uploaded to. Indeed the BTS would do poor job if source packages got uploaded as attachments to the BTS. On the other hand, the BTS is an excellent platform to track sponsoring progress, making all the comments over time available in a single bug log. Additionally, it's very important to note that not all packages should eventually be uploaded, so the fact that some packages never get sponsored is a feature. Debian doesn't want to contain every piece of free software ever written, because some of them have better alternatives already in Debian, for example. How would you deal with that with a BTS pseudo-package? After some time, there will be a few hundred RFSes that should never ever be uploaded to Debian, but are still open. Who gets to decide that they can be closed? As Arno outlined before, all we would see here is an improvement (if any change) - who is it that gets to decide now? Its the community and the decision is communicated by not responding to (possibly repeated) RFS. With the BTS, this could be tagged as wontfix. In some earlier email I stated that we should probably come up with a dedicated sponsoring team that gets to handle the bureaucratic bits. It would, IMHO, then be this team's work to close such bugs from time to time. Best regards, Michael pgpQBxF11mPlr.pgp Description: PGP signature
Re: Becoming DM [was: Re: Tracking RFSs as bugs]
On 06/09/2011 23:47, Michael Tautschnig wrote: Hi Chris, [...] As said above: I for one would be perfectly fine to offer this kind of mentoring to you. I'm not sure whether you had ever had a negative answer to such a request for mentorship - have you ever asked for it (before)? I had a mentor for about a year when I first started packaging. His responses to my occasional emails were invaluable, but we lost touch last year when he moved jobs/email addresses. There is a huge difference between reading debian-policy (or the wiki, or whatever other resource), and having someone bring it to life applied to your own work. At the start of this year I asked for a new mentor, on both debian-mentors[1] and (after nobody replied) on debian-devel-games[2]. I have 'joined' the games team on IRC, and have been told that the way to get a sponsor is to do outstanding packaging tasks on other games. Since I'm not yet good enough at packaging to do this, I have tried to contribute to the wiki instead[3], though this has been stalled by RL over the summer. I would very much appreciate your help. May I email you? Regards, Chris -- [1]http://lists.debian.org/debian-mentors/2011/01/msg00249.html [2]http://lists.debian.org/debian-devel-games/2011/02/msg00053.html [3]http://wiki.debian.org/Games/IntoDebian -- 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/4e67d201.9040...@gmail.com
Re: Becoming DM [was: Re: Tracking RFSs as bugs]
Hi Chris, [...] I would very much appreciate your help. May I email you? I wouldn't claim I could answer all your questions, especially when it comes to games-specific ones, but at least I'll try my best to help. So yes, please go ahead. Best, Michael pgp6wMMNMscgR.pgp Description: PGP signature
Re: RFS: sxiv
Hi, $ tar -tvvf sxiv_0.9.orig.tar.gz | grep '/debian/$' drwxr-xr-x epsilon/epsilon 0 2011-07-07 21:19 sxiv-0.9/debian/ Huh? -- Jakub Wilk Fixed. Please checkout: http://mentors.debian.net/debian/pool/main/s/sxiv/sxiv_0.9-1.dsc Thank you! -- Epsilon http://www.rinconinformatico.net http://www.fitnessdeportes.com http://www.dragonjar.org Linux user: #477840 Debian user
Re: RFS: mail-notification (updated package; NMU for RC bugs among others)
On Wed, 7 Sep 2011 12:08:57 +0200, Sven Hoexter s...@timegate.de wrote: On Wed, Sep 07, 2011 at 10:34:11AM +0200, Adam Borowski wrote: OK - do you have any pointers to migration documentation? The main intent of the NMU was to fix the FTBFS, not really overhaul the whole package, but it would indeed be better to avoid leaving predictable future FTBFSes... It seems strange to me to have changes of this scale in a NMU. Wouldn't you rather either hijack the package or talk to Liu Qi about adding yourself as a co-maintainer? Especially since it's your 5th NMU of this package in a row, you're kind of its official non-maintainer :p I've uploaded one the NMUs in the past and last time Liu ACK'ed the NMU because he had not enough time to care at the time. I think I already proposed to Steve to take over the whole thing upstream because it's dead otherwise. Steve and some other people from other distros currently pass around patches and the mess is getting bigger every other month. :-/ I went for a large-scale NMU mainly because, compared to the work involved fixing the FTBFS bug (the patches adding support for Evolution 3 and switching to GTK+ 3), the rest was rather simple and addressed either nasty bugs (the eggtrayicon segfault and Polish crash), important missing functionality people have been waiting for for years (SSL) or a trivial text-formatting fix (b instead of span). Then I fixed some lintian warnings because I know some sponsors prefer a reasonably lintian-clean package! I have indeed ended up being the de facto maintainer, and Qi agreed in March that we should probably co-maintain it (well, strictly speaking the agreement was that I should have access to a repository used to maintain mail-notification). Since then though I haven't heard anything. I also attempted to get in touch with Jean-Yves Lefort but haven't heard anything from him either. In any case I don't mind either taking over upstream or taking over the Debian package (or both). I don't know if it's possible to take over a dead project on Savannah and Launchpad (where mail-notification are hosted), as used to be the case on SourceForge... In the meantime though, would any one like to sponsor the NMU? Regards, Stephen signature.asc Description: PGP signature
Re: RFS: sxiv
* Daniel Echeverry epsilo...@gmail.com, 2011-09-07, 16:15: http://mentors.debian.net/debian/pool/main/s/sxiv/sxiv_0.9-1.dsc I tried to build the package with DEB_BUILD_OPTIONS=noopt, but -O2 was used as optimization anyway. Could you please fix that? -- Jakub Wilk -- 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/20110907222105.ga8...@jwilk.net
Re: RFS: sxiv
Hi, 2011/9/7 Jakub Wilk jw...@debian.org * Daniel Echeverry epsilo...@gmail.com, 2011-09-07, 16:15: http://mentors.debian.net/**debian/pool/main/s/sxiv/sxiv_**0.9-1.dschttp://mentors.debian.net/debian/pool/main/s/sxiv/sxiv_0.9-1.dsc I tried to build the package with DEB_BUILD_OPTIONS=noopt, but -O2 was used as optimization anyway. Could you please fix that? -- Jakub Wilk Fixed. Please check out: http://mentors.debian.net/debian/pool/main/s/sxiv/sxiv_0.9-1.dsc Thank you! -- Epsilon http://www.rinconinformatico.net http://www.fitnessdeportes.com http://www.dragonjar.org Linux user: #477840 Debian user
