Re: RFS: Jampal (2nd try)
Many thanks for doing this.
I used rsync since cp -a was trying to copy the svn directories. For
some reason I am not sure of, it was failing with an error that it was
unable to create the svn directories in the destination directory. I did
not look further into why that was, but just changed to rsync. If you
think that is abuse I can investigate the svn issue again.
I put leading zeroes in my version number thinking that in future if I
went from 2.9 to 2.10 it would be considered as a lower version
somewhere. Perhaps my 3 part version number is a bit excessive.
I am not sure what is so bad about a relative classpath in a jar file. I
can get rid of the duplicate icon file.
On 7/22/2011 3:07 PM, Kilian Krause wrote:
> Hi Peter,
> On Fri, Jul 15, 2011 at 01:06:09PM -0400, Peter Bennett wrote:
>> Thank you Arno for your assistance.
>> I have uploaded a new version of jampal, 02.01.05-1
>> All problems previously noted have been fixed.
> Having a closer look I find the version number.. uhm... "interesting" ;-)
> Nevertheless there's nothing wrong with it, so nothing to complain here.
>> The lintian appears to be clean
>> lintian -I --pedantic jampal_02.01.05-1.dsc
>> gives no error.
> As you stress this I'm tempted to give you my output (including -X):
> W: tagbkup: manpage-has-errors-from-man usr/share/man/man1/tagbkup.1.gz Invalid or incomplete multibyte or wide character
> X: jampal: duplicate-files usr/share/doc/jampal/html/favicon.ico.gz usr/share/doc/jampal/html/images/jampal.ico.gz
> W: jampal: classpath-contains-relative-path usr/share/jampal/jampal.jar: ../freetts/lib/freetts.jar
> W: jampal: manpage-has-errors-from-man usr/share/man/man1/jampal.1.gz Invalid or incomplete multibyte or wide character
> none of which are truly harmful though. Especially the manpage errors are a
> quite frequent false positive.
>> I am looking for a sponsor for my package "jampal".
>> - dget
> What I did stumble upon is the build-depends against rsync. After closely
> checking that seems to be bordering abuse yet nothing that is formally
> wrong. I'm somewhat unsure though why "cp -a" wouldn't do the same thing
> here. Eventually the CVS exlude would require some extra rm lines but apart
> from that I don't really see the benfit.
> As a side note it seems the DEP-5 Format URL is broken even though it's
> verbatim the style DEP-5 demands for AFAICT. Still strange though.
> Anyway, built, signed, uploaded.