Re: RFS: anox
Sébastien Bertrand thedamoc...@gmail.com writes: - It probably does not handle whitespace in command names or directories. It handles complex command without problem. How? anonx does app = ' '.join(sys.argv[1:]) # Pick all arguments, but calling foo bar x is not the same as calling foo bar x. Similar for directories: if the current work directory is something like /foo/bar foo, then f.write(cd + directory + \n) will not work. (Everything except \0 can appear in a path.) - From the documentation on Popen.wait[1]: Warning: This will deadlock when using stdout=PIPE and/or stderr=PIPE and the child process generates enough output to a pipe such that it blocks waiting for the OS pipe buffer to accept more data. Ok, I'm not sure to understand how to write the code, but I'll check that point. You could just not redirect stdout (same as stderr). 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/87mxb2hzzq@deep-thought.43-1.org
Re: NMU done but unresponsive maintainer
Hi! Am 08.12.2011 21:03, schrieb Emilien Klein: Is there anyone available to sponsor my NMU from 2011-10-27? I'm sorry, but personally I don't like to sponsor your NMU. Some of the reasons are: * Only fixing a wishlist bug, nothing else * The wishlisht bug is a new version not detailing why the new version is needed * No apparent consent of the maintainer for the NMU * Not a minimal NMU, changing other stuff, too * Python package, I'm not really familiar with However, given that: a) There was only _one_ maintainer upload b) This upload was 9 month ago c) The upload was at that point already outdated (as 0.8 was released in February according to the homepage) d) Your (wishlist) bug was without answer for over three month e) You say the maintainer is unresponsive f) You seem to have an interest in the package Have you considered taking over maintenance of the package, probably in the python packaging team (which might help you find new sponsors)? Best regards, Alexander -- 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/4ee1dbbc.8030...@debian.org
Re: RFS: anox
Le 9 déc. 2011 10:27, Ansgar Burchardt ans...@debian.org a écrit : Sébastien Bertrand thedamoc...@gmail.com writes: - It probably does not handle whitespace in command names or directories. It handles complex command without problem. How? anonx does app = ' '.join(sys.argv[1:]) # Pick all arguments, but calling foo bar x is not the same as calling foo bar x. From the point of view of anoX, these two commands are the same. Similar for directories: if the current work directory is something like /foo/bar foo, then f.write(cd + directory + \n) will not work. (Everything except \0 can appear in a path.) - From the documentation on Popen.wait[1]: Warning: This will deadlock when using stdout=PIPE and/or stderr=PIPE and the child process generates enough output to a pipe such that it blocks waiting for the OS pipe buffer to accept more data. Ok, I'm not sure to understand how to write the code, but I'll check that point. You could just not redirect stdout (same as stderr). Thanks, that's managed in the 2.1 with Popon.communicate(). Regards, Sébastien.
Re: Using /lib/init/vars.sh and its VERBOSE variable in init.d scripts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Thomas, On 09.12.2011 06:50, Thomas Goirand wrote: # Load the VERBOSE setting and other rcS variables . /lib/init/vars.sh [...] case $1 in start) [ $VERBOSE != no ] log_daemon_msg Starting $DESC $NAME but in Debian, /lib/init/vars.sh contains VERBOSE=no by default, so the init.d script isn't producing outputs when I call it. That's all right. The default is no, so you won't see such daemon messages when implemented properly, but that's no problem. By sourcing /lib/init/vars.sh you not only get these variables in a predictable manner, but also proper site-local settings, as the script you mentioned also sources: # Source conffile if [ -f /etc/default/rcS ]; then . /etc/default/rcS fi Thus, in /etc/default/rcS you can make init scripts more verbose if you want to. - -- 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/ iQIcBAEBAgAGBQJO4ff+AAoJEMcrUe6dgPNtDGMP/jrOU9fpwEbqVzqRKCvgCQCV r/sVA21X5z72rXNbHX+SL2CmBAmh7P6Xr4NkJIffhOa9qcpQH6RoQ3VmOWea8ikS rMQT+a9ZHL1wykvgoHAeNHl0FS2oP5cKgPaLdU23hWmX9aiR2FjPQnOPZCa+1d7s oYt4Ex1wXIspMnkzUpMPa5UXFQjPy+nSiGD8bVXjSqE2lVMQC8atM7zXabiSX66i PBNDAVXpyeoMBaEYVrbHkBNOZJZJB/W2ll0RrIQdKKNxrAYh2onjt3GgZ8FOaCEJ pe9skPYqrNh+NCSlC/JslA4iHrS5MhGAqheyC9/R7zhc5iOGbsO+avoMVVTW6LvD fXf7Jt0P7G6g4ZiqZEdBZP7C9mZvxtcJj53VvuMCO1mUpB+leqS1VtFCpzYmvdaz se6Z6APldpyHyNE4C2BPJTpJWCkSXJvRJ/+P3a6lkD7d5VmM95LRnvcDb32vHzb2 o0j+Prdglxc9JgVAiQ57iBZx8WXDA+NEXEKCEvhrseyn1q3uknpoX0WDx9tPt9cA IkAVxsv42YqShhpG+VNVXdVU0IR3p2V2xbkMNXKYpuBoI3hADuRso7rMR4tBaxwv ytkY2Oo1NzhfDFhp7a0Y/w6i0GPwRkiUjF20seEnVXrxTfwLvCc7gkHD5dl9nzeC COMoasvl/VHVzpg1Xivd =1nrv -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/4ee1f7fe.1010...@toell.net
Re: NMU done but unresponsive maintainer
On Fri, 09 Dec 2011 10:58:20 +0100, Alexander Reichle-Schmehl toli...@debian.org wrote: I'm sorry, but personally I don't like to sponsor your NMU. Some of the reasons are: * Only fixing a wishlist bug, nothing else * The wishlisht bug is a new version not detailing why the new version is needed * No apparent consent of the maintainer for the NMU I agree with the first two points. But I think the third is OK, according to Emilien's previous message, the maintainer did bless the NMU. d -- 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/871useuefk.fsf@zancas.localnet
Re: RFS: php-xml-beautifier
Hi! On Thursday, December 08, 2011 09:05:16 PM Thomas Goirand wrote: Please use pkg-php-tools for your package, so that it can use variable substitutions, so that you can later use: ... Done. The new package on mentors and on the VCS: https://git.fsinf.at/apt/php-xml-beautifier ... now uses pkg-php-tools. I didn't update the debian version, I hope thats fine that way. Also, it'd be great if you were trying to have your package team-maintained. Please join the PHP PKG team and help, rather than working on your side only, and have your PEAR package sent to the Git repository on Alioth (in /git/pkg-php there's already quite a bunch of PEAR modules...). I already joined the mailinglist there and enjoy the spam that comes in there every day ;-). I did however file a join-request on their Alioth homepage. I can only hope they approve the request. Besides that, I don't think you need debian/dirs, and debian/README.Debian doesn't document anything useful. They were leftovers and are now removed. Last, why did you choose GPL-3+ for your packaging work, when upstream has chosen a more relaxed BSD 2 clause? Because I think its a good license. Is that a problem? I am happy to choose something different or the same as the package, if there are any customs or conventions I am not aware about. That being said, I still look for a sponsor for that package! ;-) greetings, Mati -- me on twitter: @mathiasertl | soup: http://soup.er.tl I only read plain-text mail! I prefer signed/encrypted mail! signature.asc Description: This is a digitally signed message part.
Re: NMU done but unresponsive maintainer
Hi! Am 09.12.2011 13:17, schrieb David Bremner: * Only fixing a wishlist bug, nothing else * The wishlisht bug is a new version not detailing why the new version is needed * No apparent consent of the maintainer for the NMU I agree with the first two points. But I think the third is OK, according to Emilien's previous message, the maintainer did bless the NMU. Ah, right. Missed that. However, his mail seems to underline my point: This package should have at least a new co-maintainer, or even better: Be team maintained :) Best regards, Alexander -- 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/4ee20592.9090...@debian.org
Re: NMU done but unresponsive maintainer
Hi Alexander, 2011/12/9 Alexander Reichle-Schmehl toli...@debian.org: I'm sorry, but personally I don't like to sponsor your NMU. Makes me sad ;) (joking) Some of the reasons are: * Only fixing a wishlist bug, nothing else * The wishlisht bug is a new version not detailing why the new version is needed I maintain the nautilus-image-manipulator package, which uses python-poster to upload files to a website. However there was a bug in python-poster 0.7.0 which I reported and which got fixed in 0.8.0. N I M's source code currently contains a hard copy of python-poster 0.8.0, and would like to get rid of it and use the dedicated Debian package as a dependency instead (reducing duplication of code/bugs/etc). See [minor] bug 648030 [0] * No apparent consent of the maintainer for the NMU As pointed to by David, maintainer suggests NMU. * Not a minimal NMU, changing other stuff, too This package only has the latest version and addresses the Lintian helper-templates-in-copyright error and the out-of-date-standards-version warning. * Python package, I'm not really familiar with I get that ;) Have you considered taking over maintenance of the package, probably in the python packaging team (which might help you find new sponsors)? I'm not fundamentally against taking over maintenance of the package, but I'm still very new to Debian packaging (not a DM or DD). Would that be a problem? Also, how is the taking over maintenance part done in a diplomatic way with regards to the current maintainer? Thanks, +Emilien [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648030 -- 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/CANqxmqGXv5TWaXGqA6aHTR1tt8=-QZDZPC=5n+rwrfimre6...@mail.gmail.com
Re: NMU done but unresponsive maintainer
* Alexander Reichle-Schmehl toli...@debian.org, 2011-12-09, 13:56: * Only fixing a wishlist bug, nothing else * The wishlisht bug is a new version not detailing why the new version is needed * No apparent consent of the maintainer for the NMU I agree with the first two points. But I think the third is OK, according to Emilien's previous message, the maintainer did bless the NMU. Ah, right. Missed that. However, his mail seems to underline my point: This package should have at least a new co-maintainer, Eh, why? Because the maintainer failed to respond to a wishlist bug? -- 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/20111209143941.ga7...@jwilk.net
RFS: python-poster (was: NMU done but unresponsive maintainer)
* Emilien Klein emilien+deb...@klein.st, 2011-11-25, 15:37: I am thus looking for someone to sponsor my NMU. It can be found at http://mentors.debian.net/package/python-poster. I gave it a quick look: + * debian/control: +- Bump Standards-Version to 3.9.2 This is not appropriate for an NMU. +- Added Vcs-Browser and Vcs-Hg, removed Vcs-Bzr Uh? This is incorrect. Vcs-* fields are supposed to point to Debian packaging repository, not upstream repository. + * debian/copyright: +- Conform to DEP-5: Machine-readable debian/copyright This is not appropriate for an NMU. + * debian/watch: +- Add `debian uupdate` after the URL Heavens forbid! +- Remove comments from helper tool This is not appropriate for an NMU. -- 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/20111209144938.ga7...@jwilk.net
Re: NMU done but unresponsive maintainer
Hi! Am 09.12.2011 15:39, schrieb Jakub Wilk: Ah, right. Missed that. However, his mail seems to underline my point: This package should have at least a new co-maintainer, Eh, why? Because the maintainer failed to respond to a wishlist bug? No, because he seems to be busy with his baby, while there's someone else interested in helping with the package. Best regards, Alexander PS: Note that with at least a new co-maintainer I meant: Either that or team maintained. -- 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/4ee222a7.5010...@schmehl.info
Re: RFS: python-poster (was: NMU done but unresponsive maintainer)
Hi Jakub, If I understand it correctly none of the changes I've made are acceptable for an NMU. That's fine by me, as l'm just trying to get a newer version that is free of the bug due to which I have to duplicate code. If fixing part of the Lintian warnings are not fit for a NMU, I'll gladly not do it ;) Just a question though: + * debian/watch: + - Add `debian uupdate` after the URL Heavens forbid! Could you please elaborate? Do you mean that this is not appropriate for a NMU, or in general? Motivation for this change: footnote 83 [0] of the Debian New Maintainers' Guide: If the uscan command downloads the updated source but it does not run the uupdate command, you should correct the debian/watch file to have debian uupdate at the end of the URL. Thanks for looking at it, though! +Emilien [0] http://www.debian.org/doc/manuals/maint-guide/update.en.html#ftn.id486282 -- 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/canqxmqgsyt2tuhsqaeadmdtfscubsyrbpz10oxlpwob+z+h...@mail.gmail.com
Re: NMU done but unresponsive maintainer
2011/12/9 Jakub Wilk jw...@debian.org: * Alexander Reichle-Schmehl toli...@debian.org, 2011-12-09, 13:56: This package should have at least a new co-maintainer, Eh, why? Because the maintainer failed to respond to a wishlist bug? It's actually failing to respond to 6 direct emails and 4 posts on the bug report [0], after having had the message from him that doing a NMU was fine (due to having a new baby), and this over the course of several months: my first direct message to Robert asking about updating the package is from April 14, 2011. But I do agree that it doesn't feel that diplomatic a move... But maybe I'm just not enough aware of the politics side ;) +Emilien [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638707 -- 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/canqxmqewyjpppv3gz+hdywupsjyrvhd8gs+1hqa-4erzr4r...@mail.gmail.com
Re: RFS: nuitka (2nd try)
Hello everybody, it's been silent, but I would appreciate more review or even sponsoring. So, anybody? :-) In the meantime, there have been upstream updates, so the version is no longer the current, but I upload them silently; I assume that these don't go unnoticed due to http://mentors.debian.net/package/nuitka anyway? Thanks in advance, Kay Am 05.12.2011 23:01, schrieb Kay Hayen: Dear mentors, after a first review round, the package is now lintian --pedantic clean. I am looking for a sponsor for my package nuitka. * Package name : nuitka Version : 0.3.16pre3-1 Upstream Author : Kay Hayen kayha...@gmx.de * URL : http://nuitka.net * License : GPLv3 Section : python It builds those binary packages: nuitka - Python compiler with full language support and CPython compatible To access further information about this package, please visit the following URL: http://mentors.debian.net/package/nuitka Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/n/nuitka/nuitka_0.3.16pre3-1.dsc I would be glad if someone uploaded this package for me. I believe it relatively is simple package. No real compile time dependencies. Pure Python. At run time, it uses g++ and Scons, without the user noticing. There is a inline copy of Scons, which is removed from the binary build, and it has been reviewed on Debian Python list somewhat and here already in a first round. I am willing to be a good upstream, and have so far made all known modifications to fit better into Debian. Thanks in advance, Kay Hayen -- 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/4ee22d92.6010...@gmx.de
Re: RFS: python-poster
Thanks Arno for your detailed explanation, makes complete sense. +Emilien -- 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/canqxmqhdgq5jjltybvgoh8-jwzmqe9vwpjrczvl34tyajzc...@mail.gmail.com
Re: RFS: python-poster (was: NMU done but unresponsive maintainer)
* Emilien Klein emilien+deb...@klein.st, 2011-12-09, 16:22: If I understand it correctly none of the changes I've made are acceptable for an NMU. That's fine by me, as l'm just trying to get a newer version that is free of the bug due to which I have to duplicate code. I'd happy to sponsor the NMU if it fixed this one thing. If fixing part of the Lintian warnings are not fit for a NMU, I'll gladly not do it ;) Fixing lintian *errors* would be probably OK if done in a minimal way. Just a question though: + * debian/watch: + - Add `debian uupdate` after the URL Heavens forbid! Could you please elaborate? Do you mean that this is not appropriate for a NMU, Yes. or in general? IMO[0] yes, too. I expect that if I call uscan, it'll download upstream source, and that's it, not run some arbitrary commands. [0] The rest of Debian community might not necessarily agree. -- 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/20111209165421.gb7...@jwilk.net
Re: RFS: python-poster (was: NMU done but unresponsive maintainer)
2011/12/9 Jakub Wilk jw...@debian.org: I'd happy to sponsor the NMU if it fixed this one thing. Great! One more question: For my initial NMU on 2011-10-27 I used version number 0.8.1-0.1. Should I use the same (since it hasn't been uploaded to unstable) and just pretend nothing else happened, or bump that number up and leave the junk modifications in debian/changelog? I'd thing the former is better, but you tell me! +Emilien -- 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/canqxmqgmwfqx5kp6oi2xzmqyonrvcwvckzpylgdmk7syjyr...@mail.gmail.com
Re: NMU done but unresponsive maintainer
On Sat, Dec 10, 2011 at 4:42 AM, Emilien Klein emilien+deb...@klein.st wrote: 2011/12/9 Jakub Wilk jw...@debian.org: * Alexander Reichle-Schmehl toli...@debian.org, 2011-12-09, 13:56: This package should have at least a new co-maintainer, Eh, why? Because the maintainer failed to respond to a wishlist bug? It's actually failing to respond to 6 direct emails and 4 posts on the bug report [0], after having had the message from him that doing a NMU was fine (due to having a new baby), and this over the course of several months: my first direct message to Robert asking about updating the package is from April 14, 2011. But I do agree that it doesn't feel that diplomatic a move... But maybe I'm just not enough aware of the politics side ;) politics aside, I'm happy if you want to add yourself to uploaders or even take over the package. Cynthia (our child) has GERD, and - well, if you have been through that, you'll know, and if you haven't there is no possible description that will communicate it. I'm sorry that the minor release has been blocking a significant fix in another package. 'nuff said. -Rob -- 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/CAJ3HoZ19VZtj255oJKYQJ8+Z=fmfhs3hn_k0rok91v5w_q1...@mail.gmail.com
Re: RFS: python-poster (was: NMU done but unresponsive maintainer)
* Emilien Klein emilien+deb...@klein.st, 2011-12-09, 18:36: One more question: For my initial NMU on 2011-10-27 I used version number 0.8.1-0.1. Should I use the same Yes, please use the same. -- 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/20111209174642.ga...@jwilk.net
Re: NMU done but unresponsive maintainer
Hi Robert, 2011/12/9 Robert Collins robe...@robertcollins.net: politics aside, I'm happy if you want to add yourself to uploaders or even take over the package. Thanks for you response. I'll make this upload a NMU, and will work to get that maintained within the Python group (still need to figure out how, though) Cynthia (our child) has GERD, and - well, if you have been through that, you'll know, and if you haven't there is no possible description that will communicate it. I'm sorry to hear that. We've already been through 2 normal baby sicknesses and a 7 weeks long skin condition with our 20-month old, but I can't imagine what you must be going through. Hope she gets better. I'm sorry that the minor release has been blocking a significant fix in another package. No big deal ;) ++ +Emilien -- 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/canqxmqhvhy4i7m_lbmxcab6p3g8l1gew0yrqs_vpqj0hhj8...@mail.gmail.com
Re: RFS: php-xml-beautifier
On 12/09/2011 08:46 PM, Mathias Ertl wrote: I already joined the mailinglist there and enjoy the spam that comes in there every day ;-). I did however file a join-request on their Alioth homepage. I can only hope they approve the request. I'd suggest sending a private mail to the admins of the project. Last, why did you choose GPL-3+ for your packaging work, when upstream has chosen a more relaxed BSD 2 clause? Because I think its a good license. Is that a problem? I am happy to choose something different or the same as the package, if there are any customs or conventions I am not aware about. There's no problems per say, I believe everyone is free to release the work it does in Debian in the license of its choice if it's DFSG free, but I just feel weird to have just a few files needed for the packaging to be more restrictive than the ones from the original authors itself. Said in another way: your choice of licensing is legally valid inside Debian, but it wouldn't be mine. I'd adopt the license of upstream, especially if it's the BSD license. IMHO, software with multiple licenses are a pain when writing debian/copyright files. That being said, I still look for a sponsor for that package! ;-) Please ping me in few days if I didn't get time to review again and nobody else stood up (I'm going to sleep now, I'm too tired to start packaging reviews ...). Thomas -- 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/4ee26c7a.8070...@goirand.fr
Re: RFS: python-poster (was: NMU done but unresponsive maintainer)
Hi Jakub, 2011/12/9 Jakub Wilk jw...@debian.org: * Emilien Klein emilien+deb...@klein.st, 2011-12-09, 16:22: If I understand it correctly none of the changes I've made are acceptable for an NMU. That's fine by me, as l'm just trying to get a newer version that is free of the bug due to which I have to duplicate code. I'd happy to sponsor the NMU if it fixed this one thing. I've restarted the NMU from scratch, this time only changing debian/changelog. It's uploaded to mentors: http://mentors.debian.net/package/python-poster It would be great if you could have a look at it. FYI I've tested it by removing the hard copy of poster in nautilus-image-manipulator and changing the import of poster like this: from poster.encode import multipart_encode from poster.streaminghttp import register_openers instead of: from nautilus_image_manipulator.upload.poster.encode import multipart_encode from nautilus_image_manipulator.upload.poster.streaminghttp import register_openers and all works fine. Thanks for your time and comments, +Emilien -- 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/CANqxmqGPQARzmqSbCsmFCKu8H7u4--D1auY2qDC3Z=-whu1...@mail.gmail.com
Re: RFS: python-poster
* Emilien Klein emilien+deb...@klein.st, 2011-12-09, 22:36: If I understand it correctly none of the changes I've made are acceptable for an NMU. That's fine by me, as l'm just trying to get a newer version that is free of the bug due to which I have to duplicate code. I'd happy to sponsor the NMU if it fixed this one thing. I've restarted the NMU from scratch, this time only changing debian/changelog. It's uploaded to mentors: http://mentors.debian.net/package/python-poster It would be great if you could have a look at it. Your *.diff.gz modifies files it shouldn't: $ lsdiff -z python-poster_0.8.1-0.1.diff.gz | grep -v /debian python-poster-0.8.1/poster.egg-info/PKG-INFO But, since it was caused by a latent bug in the existing package (not removing files that are modified at build time), I'll leave it that way. I uploaded the package to DELAYED/2. Please post full debdiff between 0.7.0-1.1 and 0.8.1-0.1 to the bug log. -- 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/20111209220814.ga2...@jwilk.net
Re: RFS: python-poster
2011/12/9 Jakub Wilk jw...@debian.org: I uploaded the package to DELAYED/2. Please post full debdiff between 0.7.0-1.1 and 0.8.1-0.1 to the bug log. Thanks Jakub for the upload. Full debdiff is to be found here: http://paste.debian.net/148759/ Please let me know if using the paste service isn't appropriate (I've set it to never expire) +Emilien -- 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/canqxmqfxdufk1nz5m0yg8dzlszz+q37ibyvtpktgf9zmc4j...@mail.gmail.com
Re: RFS: openssn (2nd try)
On Sun, Sep 18, 2011 at 9:27 PM, Vincent Cheng vincentc1...@gmail.com wrote: Dear mentors, I am looking for a sponsor for my package openssn. * Package name : openssn Version : 0.8-1 Upstream Author : Jesse Smith jessefrgsm...@yahoo.ca * URL : http://openssn.sourceforge.net/ * License : GPL2 (code), CC0 (data) Section : games Description: modern submarine tactical simulator OpenSSN is a submarine simulation (subsim) which tries to emulate the behaviour of modern submarines. The player is placed in command of a submarine and is able to move about in a deep ocean environment. It builds those binary packages (which are lintian and pbuilder clean): openssn - modern submarine tactical simulator openssn-data - modern submarine tactical simulator (data) openssn-dbg - modern submarine tactical simulator (debug) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/openssn Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/o/openssn/openssn_0.8-1.dsc I would be glad if someone uploaded this package for me. Kind regards, Vincent Cheng Just giving this a ping after 3 months. I'm still looking for a sponsor for openssn; an updated package is accessible with: $ dget http://mentors.debian.net/debian/pool/main/o/openssn/openssn_1.1-1.dsc Thanks in advance! Vincent -- 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/caczd_tctwoddxf4krpn8+aftitydxowuucne7sc2h3wdq6l...@mail.gmail.com
Re: RFS: python-poster
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Emilien, On 09.12.2011 23:22, Emilien Klein wrote: Full debdiff is to be found here: http://paste.debian.net/148759/ Please let me know if using the paste service isn't appropriate (I've set it to never expire) no it is not. Jakub meant to file a bug denoting your NMU to the BTS. You can use the nmudiff to get the idea. #610114 [1] is a random example of what we mean too. In your case you shouldn't be filing a new bug though, but reply to the existing one you are closing. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610114 - -- 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/ iQIcBAEBAgAGBQJO4o3JAAoJEMcrUe6dgPNtTs4QAKUmVBzUkR5s81YuV/Cz8bGk dx3wuC3yjBDC2uRMx6lUggLLsQYSyRmTw98WSYrMfPNDh2533H936Cj3cU9GIGNo e+4/SpIGY78hSUYSTRAQVDAZnB4aJRFVQh+b6A4FMOircDtpkonySsQv9KP/b7V0 UEwePZG2enzfxFFdN7h3XbhtfDlpyuFVtXNBRiZbvWXO8V6I2qAjTzlOiOju+aMX yPPDz3gsq6PNGyKA9w/2AkDlOTBDBxXyuOAXqiqEm/Tqpgkbf+Vd80jBB6T6QpV5 fAqS/XPpYy5m8RtvY/txrwKyjKuQimCq0Aa53zKVhGwnyy7fEPlcEzaz6QzsxBlQ 7Xws3GJ00gucr7UAHo8D6jyiwD1UYAw4y6FMpVCFWIyKOMBuRwb0/jqh9dbtbzXx 7FRMjFPIzlaBlOGKS93WRoKP3sfJjnxsjdS5J9yUreYb0sS7Odn3YJkqzTLarJTL Kt+ZFxkjOoy9WUWjZK3jeGd9q5i9vo6Q5+tUcYLfFbt35+N3N/E/g024LyhS5DWz Ubdg2WY90uEKN1tCQ5hkKaVlpFs6ogthMb/sPz7gX62EwVUEYxVgEN+PPAbTT1Vb LkBjSe35ArWEQG97uJLj9ApXsx8OBsT42mGOG4jc+5+A5ngGdZCTJz9C8cUL29cq 6vQK+L28jUeX/ks5ggdb =85e8 -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/4ee28dc9.9080...@toell.net
Re: RFS: anox
On Fri, Dec 09, 2011 at 11:30:38AM +0100, Sébastien Bertrand wrote: calling foo bar x is not the same as calling foo bar x. From the point of view of anoX, these two commands are the same. From the UNIX point of view, they are not. -- Andrea Bolognani e...@kiyuko.org Resistance is futile, you will be garbage collected. signature.asc Description: Digital signature
Re: RFS: python-poster
Hi Arno, 2011/12/9 Arno Töll deb...@toell.net: no it is not. Jakub meant to file a bug denoting your NMU to the BTS. You can use the nmudiff to get the idea. #610114 [1] is a random example of what we mean too. In your case you shouldn't be filing a new bug though, but reply to the existing one you are closing. Just to make sure we're on the same page: the message you replied to was sent to both the mailing list *and* the bug report [0]. Do you mean that I need to physically attach that diff to the bug report, instead of just linking to the paste? IMHO the coloring of the paste eases the reading, but there is also a download link at the bottom if someone needs a physical copy on it's computer. This is my first NMU, so I want to make sure I'm doing this right! +Emilien [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638707#30 -- 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/CANqxmqE-LcCTnVLZBwV+7rNrLswz-+Qg-5i�yswngkjmx...@mail.gmail.com
Re: RFS: python-poster
On Sat, Dec 10, 2011 at 00:25, Emilien Klein emilien+deb...@klein.st wrote: Hi Arno, 2011/12/9 Arno Töll deb...@toell.net: no it is not. Jakub meant to file a bug denoting your NMU to the BTS. You can use the nmudiff to get the idea. #610114 [1] is a random example of what we mean too. In your case you shouldn't be filing a new bug though, but reply to the existing one you are closing. Just to make sure we're on the same page: the message you replied to was sent to both the mailing list *and* the bug report [0]. Do you mean that I need to physically attach that diff to the bug report, instead of just linking to the paste? IMHO the coloring of the paste eases the reading, but there is also a download link at the bottom if someone needs a physical copy on it's computer. Except that posting the actual debdiff is required by policy, pastes on p.d.n are removed after some time (I think you can choose it at creation time), so please post the diff on the bug report (using nmudiff as suggested by Arno, f.e.). If someone need colored diff, there's always colordiff :) 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/capdtaj2ytbxx5qapscnxg3flxeu7jw0zohmo9pt69ywhdsr...@mail.gmail.com
Re: RFS: nuitka (2nd try)
On Fri, Dec 9, 2011 at 11:47 PM, Kay Hayen wrote: In the meantime, there have been upstream updates, so the version is no longer the current, but I upload them silently; I assume that these don't go unnoticed due to http://mentors.debian.net/package/nuitka anyway? There is currently zero automatic integration between debian-mentors and mentors.d.n. People reading your old RFS mails will probably download the old .dsc file unless you update the thread. -- 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/CAKTje6E0FF0NxSh68YyLP3pZ60cNycwF0htA500iK2MW=nj...@mail.gmail.com
