RFS: anteater

2003-10-29 Thread Andrea Capriotti
I'm an applicant and I'm looking for a sponsor. http://nm.debian.org/nmstatus.php?email=a.capriotti%40nettuno.it Package: deb http://mentors.debian.net/debian unstable main deb src http://mentors.debian.net/debian unstable main Or: http://www.linux.it/~capriotti/debian/ Upstream: http://ante

RFS: anteater

2003-10-29 Thread Andrea Capriotti
I'm an applicant and I'm looking for a sponsor. http://nm.debian.org/nmstatus.php?email=a.capriotti%40nettuno.it Package: deb http://mentors.debian.net/debian unstable main deb src http://mentors.debian.net/debian unstable main Or: http://www.linux.it/~capriotti/debian/ Upstream: http://ante

Re: RFS (3): aap

2003-10-29 Thread Bas Zoetekouw
Hi Cory! You wrote: > A-A-P is an astoundingly powerful replacement for make that keeps the good > ideas, cleans up the syntax and adds important features like Python > scripting. > Upstream is Bram Moolenaar, whom you may know as the author of ViM. It: > * has autoconf/make features > * suppo

Re: RFS (3): aap

2003-10-29 Thread Pablo Lorenzzoni
Hello! I will take a look. If your packages are any good I'll sponsor'em. []s Pablo Em Qua, 29 Out 2003, Cory Dodt escreveu: | Still looking for a sponsor. Packages reside at: |deb http://mentors.debian.net/debian unstable main |deb src http://mentors.debian.net/debian unstable main |

Re: RFS (3): aap

2003-10-29 Thread Bas Zoetekouw
Hi Cory! You wrote: > A-A-P is an astoundingly powerful replacement for make that keeps the good > ideas, cleans up the syntax and adds important features like Python > scripting. > Upstream is Bram Moolenaar, whom you may know as the author of ViM. It: > * has autoconf/make features > * suppo

Re: RFS (3): aap

2003-10-29 Thread Pablo Lorenzzoni
Hello! I will take a look. If your packages are any good I'll sponsor'em. []s Pablo Em Qua, 29 Out 2003, Cory Dodt escreveu: | Still looking for a sponsor. Packages reside at: |deb http://mentors.debian.net/debian unstable main |deb src http://mentors.debian.net/debian unstable main |

Re: ITP Timeframe

2003-10-29 Thread Andreas Barth
* Martin List-Petersen ([EMAIL PROTECTED]) [031029 01:25]: > What would be an appropriate timeframe from the point, where you file an > ITP until the first package arrives in sid ? What is custom ? I would say it depends from which side you look at it. If looking at it as a ITPer, you should uplo

Re: ITP Timeframe

2003-10-29 Thread Andreas Barth
* Martin List-Petersen ([EMAIL PROTECTED]) [031029 01:25]: > What would be an appropriate timeframe from the point, where you file an > ITP until the first package arrives in sid ? What is custom ? I would say it depends from which side you look at it. If looking at it as a ITPer, you should uplo

RFS (3): aap

2003-10-29 Thread Cory Dodt
Still looking for a sponsor. Packages reside at: deb http://mentors.debian.net/debian unstable main deb src http://mentors.debian.net/debian unstable main Or direct link: http://mentors.debian.net/debian/dists/unstable/main/binary-all/aap/ There are two binary packages: aap, and aap-doc.

RFS (3): aap

2003-10-29 Thread Cory Dodt
Still looking for a sponsor. Packages reside at: deb http://mentors.debian.net/debian unstable main deb src http://mentors.debian.net/debian unstable main Or direct link: http://mentors.debian.net/debian/dists/unstable/main/binary-all/aap/ There are two binary packages: aap, and aap-doc.

Re: Fixing a b0rked NMU - How long do I have to wait?

2003-10-29 Thread Colin Watson
On Wed, Oct 29, 2003 at 02:36:48PM +0100, Andreas Metzler wrote: > I've made a broken NMU of libgpgme0.4, introducing a > /usr/share/info/dir.* rc-bug (218083). I've submitted a patch and tagged > the bug accordingly. How long do I have to wait before I can make an > upload fixing my own broken NMU

Re: Fixing a b0rked NMU - How long do I have to wait?

2003-10-29 Thread Andreas Metzler
On Wed, Oct 29, 2003 at 02:39:17PM +, Colin Watson wrote: > On Wed, Oct 29, 2003 at 02:36:48PM +0100, Andreas Metzler wrote: > > I've made a broken NMU of libgpgme0.4, introducing a > > /usr/share/info/dir.* rc-bug (218083). I've submitted a patch and tagged > > the bug accordingly. How long do

Re: Fixing a b0rked NMU - How long do I have to wait?

2003-10-29 Thread Colin Watson
On Wed, Oct 29, 2003 at 02:36:48PM +0100, Andreas Metzler wrote: > I've made a broken NMU of libgpgme0.4, introducing a > /usr/share/info/dir.* rc-bug (218083). I've submitted a patch and tagged > the bug accordingly. How long do I have to wait before I can make an > upload fixing my own broken NMU

Re: Fixing a b0rked NMU - How long do I have to wait?

2003-10-29 Thread Andreas Metzler
On Wed, Oct 29, 2003 at 02:39:17PM +, Colin Watson wrote: > On Wed, Oct 29, 2003 at 02:36:48PM +0100, Andreas Metzler wrote: > > I've made a broken NMU of libgpgme0.4, introducing a > > /usr/share/info/dir.* rc-bug (218083). I've submitted a patch and tagged > > the bug accordingly. How long do

Fixing a b0rked NMU - How long do I have to wait?

2003-10-29 Thread Andreas Metzler
Hello, I've made a broken NMU of libgpgme0.4, introducing a /usr/share/info/dir.* rc-bug (218083). I've submitted a patch and tagged the bug accordingly. How long do I have to wait before I can make an upload fixing my own broken NMU? Do I really have to wait again sometime + sometime + delayed-7da

Fixing a b0rked NMU - How long do I have to wait?

2003-10-29 Thread Andreas Metzler
Hello, I've made a broken NMU of libgpgme0.4, introducing a /usr/share/info/dir.* rc-bug (218083). I've submitted a patch and tagged the bug accordingly. How long do I have to wait before I can make an upload fixing my own broken NMU? Do I really have to wait again sometime + sometime + delayed-7da

Re: ITP Timeframe

2003-10-29 Thread Matthew Palmer
On Wed, Oct 29, 2003 at 12:40:12AM +0100, Martin List-Petersen wrote: > What would be an appropriate timeframe from the point, where you file an > ITP until the first package arrives in sid ? What is custom ? As soon as practicable. It's hard to put any hard limits on it - you should file the ITP