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 jaranalyzer package and removed the workaround
for bugs #489432 and #489214. See [1].
The jaranalyzer package now build-depends on javahelper >= 0.13. As soon
as you upload your newest javahelper package, jaranalyzer should be
pbuilder-clean again.
Thanks for the quick resolution. :-)
[1]
http://mentors.debian.net/debian/pool/main/j/jaranalyzer/jaranalyzer_1.2-3.dsc
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
