Re: [Popcon-developers] Encrypted popcon submissions
On Sun, Aug 04, 2013 at 03:54:25PM +0200, Bill Allombert wrote: > Well I have fixed this problem in popcon 1.59 by using a temporary GPGHOME > that I remove afterward. > > If no more problem are found, I will release 1.60 in September with > ENCRYPT=maybe > by default (i.e. encrypt if gpg is available). > Thanks for your tests! I just released popularity-contest 1.60 with encryption enabled by default. Cheers, -- Bill. Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130907121617.GA8237@yellowpig
buildd could run "make -i" twice on failure
After a build fails on the buildd, it would be really useful to have the build run again twice with "make -i" and log the output of the second retry Obviously I could hack something like this into debian/rules: make || make -i ; make -i ; exit 1 but it would be nice to have a centrally managed approach The output would then provide a more complete set of feedback about whether a package just has 1 error or 500 errors, this would provide greater visibility of potential effort required for porting Some packages don't compile their test cases without running "make check", so it would also be useful to force the test cases to be compiled (with -i) to check for compile errors -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/522b9a7f@pocock.com.au
Re: buildd could run "make -i" twice on failure
On Sat, Sep 07, 2013 at 11:28:31PM +0200, Daniel Pocock wrote: > After a build fails on the buildd, it would be really useful to have the > build run again twice with "make -i" and log the output of the second retry What's the main advantage of doing so? To log further errors not seen due to the first failure? Why not just use "-k" to begin with? > Obviously I could hack something like this into debian/rules: > > > make || make -i ; make -i ; exit 1 > > but it would be nice to have a centrally managed approach There's no guarantee that "make" is being used for building, and it's non-trivial to determine if it is or is not in use, nor how to invoke it appropriately. If we want to do it centrally, it would be more reliable to add a new target which sbuild or other build tools could invoke on error, and which package maintainers could add to support their specific requirements. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. signature.asc Description: Digital signature
Bug#722123: ITP: puppet-module-puppetlabs-apache -- Puppet module for Apache webserver
Package: wnpp Severity: wishlist Owner: Thomas Bechtold * Package name: puppet-module-puppetlabs-apache Version : 0.9.0 Upstream Author : Puppet Labs * URL : http://forge.puppetlabs.com/puppetlabs/apache * License : Apache 2 Programming Lang: Ruby Description : Puppet module for Apache webserver The Apache module allows you to set up virtual hosts and manage web services with minimal effort. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130908062611.9434.64331.reportbug@steinpilz
Bug#722124: ITP: python-dogpile.core -- dogpile lock, typically used as a component of a larger caching solution
Package: wnpp Severity: wishlist Owner: Thomas Goirand * Package name: python-dogpile.core Version : 0.4.1 Upstream Author : Mike Bayer * URL : https://pypi.python.org/pypi/dogpile.core * License : BSD Programming Lang: Python Description : dogpile lock, typically used as a component of a larger caching solution Python dogpile.core lock allows a single thread to generate an expensive resource while other threads use the old value, until the new"value is ready. . Dogpile is basically the locking code extracted from the Beaker package, for simple and generic usage. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130908063956.22553.72298.report...@buzig.gplhost.com
