I have added a work around (new packages at the same URL), where I do
(effectively):
fastjar xf $jar
rm -f $jar
fastjar ufm $jar newmanifest *
I can't use any other jar and have it in main still.
This works fine now! :-)
You can close bug #489432 as well.
I have already updated my j
On Sat Jul 12 18:18, Florian Grandel wrote:
> Hi Matthew,
>
>> Can you please try these fixed packages, I've put them up at:
>>
>> http://mjj29.matthew.ath.cx/debian-upload/java-tools/
>
> The jar filesearch is now correct. IMO you may close bug #489214.
Cool
> Anyway: jh_manifest still produces
Hi Matthew,
Can you please try these fixed packages, I've put them up at:
http://mjj29.matthew.ath.cx/debian-upload/java-tools/
The jar filesearch is now correct. IMO you may close bug #489214.
Anyway: jh_manifest still produces an invalid jar due to a bug in
fastjar -u option (see fastjar
On Wed Jul 09 13:39, Florian Grandel wrote:
> parseManifest('debian/jaranalyzer.manifest',
> 'debian/jaranalyzer/usr/bin/jaranalyzer', {'top': {}})
>
> This is probably wrong, is it?
>
> No idea what's wrong with your ffind call however. :-( Don't know
> scriptutil.
Yup, that's wrong.
shellgl
Hi Matthew,
I think I found the problem. I ran your script in the python debugger
and found out that in line 99
scriptutil.ffind(path, shellglobs=('*.jar')) returns the following:
['debian/jaran...n/jaranalyzer', 'debian/jaran...README.Debian',
'debian/jaran...zer/copyright', 'debian/jaran..
Matthew Johnson schrieb:
I shall try building it and reproducing that error, but in order to test
the rest of the program, can you try applying this diff:
--- jh_manifest.orig 2008-07-08 15:13:23.970424750 +
+++ jh_manifest 2008-07-08 15:14:02.756848750 +
@@ -73,8 +73,9 @@
manif
On Mon Jul 07 20:03, Florian Grandel wrote:
> I have tried. I installed the packages you indicated but now got the
> following error:
>
> Ick! 0x622f2123
> Traceback (most recent call last):
> File "/usr/bin/jh_manifest", line 247, in
> updatejar(j, tempmanifest, args)
> File "/usr/bin/jh
Hi Matthew,
Hi, please can you try out this new version I have just written in
python. Hopefully it should fix all these bugs.
Packages at:
http://mjj29.matthew.ath.cx/debian-upload/java-tools/
You will also need this package which I will upload to NEW, but you can
get from me:
http://
On Fri Jul 04 01:52, Florian Grandel wrote:
> Package: javahelper
> Version: 0.7
> Severity: normal
>
> jh_manifest may produce a MANIFEST.MF that does not conform to the jar
> specification. See http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html.
Hi, please can you try out this new version I h
Matthew Johnson schrieb:
Why should Debian-Java-Home not be in the main section? it applies to
the jar as a whole?
You are completely right. I was confused about this point. Sure, any
attribute applying to the jar as a whole should be in the main section.
Sorry about that.
--
To UNSUBSCRI
On Fri Jul 04 01:52, Florian Grandel wrote:
> jh_manifest may produce a MANIFEST.MF that does not conform to the jar
> specification. See http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html.
>
> The following problems may occur:
>
> Blank lines are significant. They separate sections within the
Package: javahelper
Version: 0.7
Severity: normal
jh_manifest may produce a MANIFEST.MF that does not conform to the jar
specification. See http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html.
The following problems may occur:
Blank lines are significant. They separate sections within the manif
12 matches
Mail list logo
