Re: RFS: ah

2009-06-23 Thread Harry Rickards
On 23 Jun 2009, at 00:27, Russ Allbery r...@debian.org wrote: Harry Rickards hricka...@l33tmyst.com writes: Even after removing the \, I still get: W: ah: manpage-has-bad-whatis-entry usr/share/man/man1/ah.1.gz ah.1.gz in the deb archive that you pointed to at the beginning of this

Re: RFS: ah

2009-06-23 Thread Harry Rickards
On 23 Jun 2009, at 00:27, Russ Allbery r...@debian.org wrote: Harry Rickards hricka...@l33tmyst.com writes: Even after removing the \, I still get: W: ah: manpage-has-bad-whatis-entry usr/share/man/man1/ah.1.gz ah.1.gz in the deb archive that you pointed to at the beginning of this

RFS: ah

2009-06-22 Thread Harry Rickards
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I am looking for a sponsor for my package ah. * Package name: ah Version : 0.02-1 Upstream Author : Zhaolei zhaole...@hotmail.com Maintainer : Harry Rickards hricka...@l33tmyst.com * URL :

Re: RFS: ah

2009-06-22 Thread Sandro Tosi
On Mon, Jun 22, 2009 at 19:39, Harry Rickardshricka...@l33tmyst.com wrote: The package appears to be lintian clean apart from a few warnings that I can't seem to correct (http://pastebin.com/f2ed86daf) please explain WHY you can't correct them. for example: W: ah: manpage-has-bad-whatis-entry

Re: RFS: ah

2009-06-22 Thread Harry Rickards
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/22/09 18:56, Sandro Tosi wrote: On Mon, Jun 22, 2009 at 19:39, Harry Rickardshricka...@l33tmyst.com wrote: The package appears to be lintian clean apart from a few warnings that I can't seem to correct (http://pastebin.com/f2ed86daf)

Re: RFS: ah

2009-06-22 Thread Alexander Toresson
On Mon, Jun 22, 2009 at 8:25 PM, Harry Rickardshricka...@l33tmyst.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/22/09 18:56, Sandro Tosi wrote: On Mon, Jun 22, 2009 at 19:39, Harry Rickardshricka...@l33tmyst.com wrote: The package appears to be lintian clean apart from a few

Re: RFS: ah

2009-06-22 Thread Neil Williams
On Mon, 22 Jun 2009 18:39:25 +0100 Harry Rickards hricka...@l33tmyst.com wrote: Dear mentors, I am looking for a sponsor for my package ah. Can't this use a better name, like antihex ? At least that tells me something about what the package can do. Or maybe something like hex2dec or

Re: RFS: ah

2009-06-22 Thread Harry Rickards
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/22/09 19:45, Neil Williams wrote: On Mon, 22 Jun 2009 18:39:25 +0100 Harry Rickards hricka...@l33tmyst.com wrote: Dear mentors, I am looking for a sponsor for my package ah. Can't this use a better name, like antihex ? At least that

Re: RFS: ah

2009-06-22 Thread Harry Rickards
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/22/09 19:39, Alexander Toresson wrote: On Mon, Jun 22, 2009 at 8:25 PM, Harry Rickardshricka...@l33tmyst.com wrote: ... Thanks for the advice. I've managed to get rid of all of the errors apart from two. They are:

Re: RFS: ah

2009-06-22 Thread Neil Williams
On Mon, 22 Jun 2009 20:41:07 +0100 Harry Rickards hricka...@l33tmyst.com wrote: I am looking for a sponsor for my package ah. Can't this use a better name, like antihex ? At least that tells me something about what the package can do. Or maybe something like hex2dec or similar.

Re: RFS: ah

2009-06-22 Thread Neil Williams
On Mon, 22 Jun 2009 21:19:07 +0100 Neil Williams codeh...@debian.org wrote: Make sure you document this change in the ITP - including retitling the ITP to use the changed package name. Just saw, you've already done that. #534242 - thanks. -- Neil Williams =

RFS: antihex (was RFS: ah)

2009-06-22 Thread Harry Rickards
On 22 Jun 2009, at 21:20, Neil Williams codeh...@debian.org wrote: On Mon, 22 Jun 2009 21:19:07 +0100 Neil Williams codeh...@debian.org wrote: Make sure you document this change in the ITP - including retitling the ITP to use the changed package name. Just saw, you've already done that.

Re: RFS: ah

2009-06-22 Thread Russ Allbery
Harry Rickards hricka...@l33tmyst.com writes: Even after removing the \, I still get: W: ah: manpage-has-bad-whatis-entry usr/share/man/man1/ah.1.gz ah.1.gz in the deb archive that you pointed to at the beginning of this thread is a pure text file that's just formatted vaguely like the output