Bug#700155: ITP: silversearcher-ag -- very fast grep-like program. alternative ack-grep.

2013-02-08 Thread Hajime MIZUNO
Package: wnpp Owner: Hajime MIZUNO Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org * Package name: silversearcher-ag Version : currently not assigned version number by upstrearm. Upstream Author : Geoff Greer * URL or Web page : https://github.com/ggreer/the_silver

Bug#700154: ITP: firewalld -- dynamically managed firewall with support for network zones

2013-02-08 Thread Michael Biebl
Package: wnpp Severity: wishlist Owner: Michael Biebl * Package name: firewalld Version : 0.2.12 Upstream Author : Thomas Woerner * URL : https://fedorahosted.org/released/firewalld/ * License : GPL-2+ Programming Lang: Python Description : dynamically

Bug#700153: ITP: python-slip -- Miscellaneous convenience, extension and workaround code for Python

2013-02-08 Thread Michael Biebl
Package: wnpp Severity: wishlist Owner: Michael Biebl * Package name: python-slip Version : 0.2.24 Upstream Author : Nils Philippsen * URL : https://fedorahosted.org/python-slip * License : GPL-2+ Programming Lang: Python Description : Miscellaneous co

Re: RFC declarative built-using field generation

2013-02-08 Thread Joey Hess
Andreas Beckmann wrote: > Can't we just annotate the foo-source binary package in some way - it > should be pretty clear to the maintainer that he produces such a > "special" package. No, because it's not just foo-source packages. One example of a package that needs to use built-using is debian-

Re: RFC declarative built-using field generation

2013-02-08 Thread Andreas Beckmann
On 2013-02-09 01:38, Russ Allbery wrote: > Peter Samuelson writes: >> I'm a bit confused. Given that perhaps 99% of Built-Using would be for >> trivial things like crt1.o and libgcc.a, which are concentrated into a >> relatively tiny number of packages, it seems to make more sense to >> annotate

Re: RFC declarative built-using field generation

2013-02-08 Thread Russ Allbery
Peter Samuelson writes: > [Joachim Breitner] >> this seems to be a good disk-space for human-time trade to me as well: >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699333 > I'm a bit confused. Given that perhaps 99% of Built-Using would be for > trivial things like crt1.o and libgcc.a, w

Re: RFC declarative built-using field generation

2013-02-08 Thread Peter Samuelson
[Joachim Breitner] > this seems to be a good disk-space for human-time trade to me as well: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699333 I'm a bit confused. Given that perhaps 99% of Built-Using would be for trivial things like crt1.o and libgcc.a, which are concentrated into a rela

Bug#700106: ITP: libconfig-properties-perl -- Perl implementation of the java.util.Properties API

2013-02-08 Thread Taku YASUI
Package: wnpp Severity: wishlist Owner: Taku YASUI * Package name: libconfig-properties-perl Version : 1.75 Upstream Author : Salvador Fandin~o * URL : http://search.cpan.org/dist/Config-Properties/ * License : GPL, Artistic Programming Lang: Perl Descript

Bug#700103: ITP: libdata-uniqid-perl -- Perl extension for simple genrating of unique id's

2013-02-08 Thread Taku YASUI
Package: wnpp Severity: wishlist Owner: Taku YASUI * Package name: libdata-uniqid-perl Version : 0.12 Upstream Author : Mike Wesemann, * URL : http://search.cpan.org/dist/Data-Uniqueid/ * License : GPL, Artistic Programming Lang: Perl Description : Per

Re: avoiding execution of old-prerm during update

2013-02-08 Thread Marco Mariani
On 8 February 2013 18:27, Jakub Wilk wrote: https://lists.debian.org/debian-devel/2000/04/msg00298.html > Thanks, we'll go for pre-depend then. Regards, Marco

Re: avoiding execution of old-prerm during update

2013-02-08 Thread Jakub Wilk
* Marco Mariani , 2013-02-08, 14:46: I am about to release a new version of a .deb package. The main problem is a bug on the previous version's prerm script that has the effect of removing a configuration file. Is there a way to execute the new-prerm instead of old-prerm? In my understanding,

avoiding execution of old-prerm during update

2013-02-08 Thread Marco Mariani
Hi, I am about to release a new version of a .deb package. The main problem is a bug on the previous version's prerm script that has the effect of removing a configuration file. Is there a way to execute the new-prerm instead of old-prerm? In my understanding, the answer would be no, but maybe s

Bug#700084: ITP: python-cffi -- Foreign Function Interface for Python calling C code

2013-02-08 Thread Stefano Rivera
Package: wnpp Severity: wishlist Owner: Stefano Rivera * Package name: python-cffi Version : 0.5 Upstream Author : Armin Rigo * URL : http://pypi.python.org/pypi/cffi/ * License : Expat Programming Lang: Python, C Description : Foreign Function Interfac

Re: Bug#700031: ITP: libjreen -- A powerful Jabber/XMPP library implemented in Qt/C++

2013-02-08 Thread Andrey Ponomarenko
Jonas Erlandsson wrote: Package: wnpp Severity: wishlist Owner: rm * Package name: libjreen Version : 1.1.1 Upstream Author : Jonas Erlandsson * URL : http://qutim.org/jreen/ * License : GPL2 Programming Lang: C++/QT Description : A powerful Jabb

Re: RFC declarative built-using field generation

2013-02-08 Thread Joachim Breitner
Hi, Am Donnerstag, den 07.02.2013, 20:51 -0400 schrieb Joey Hess: > Did occur to me later that another option would be to just generate > Built-Using for all build dependnecies when the field is turned on in a > package. This would list too much, but perhaps that wouldn't matter. > OTOH, perhaps t

Re: RFC declarative built-using field generation

2013-02-08 Thread Russ Allbery
Johannes Schauer writes: > There are apparently currently 67 .*-source.* packages in Debian Sid: > $ grep-dctrl -P --pattern "-source" -c < Packages > 67 A bunch of those are kernel module source packages for module-assistant, so aren't as interesting for this particular purpose. Eyeballing th

Re: RFC declarative built-using field generation

2013-02-08 Thread Johannes Schauer
Hi, On Fri, Feb 08, 2013 at 08:36:56AM +0100, Raphael Hertzog wrote: > On Thu, 07 Feb 2013, Joey Hess wrote: > > Ben Hutchings wrote: > > > What I mean is that a changes file for a sourceful upload has > > > 'source' (and maybe some real architecture names) in the Architecture > > > field. Theref