[pkg-eucalyptus-maintainers] [Debian] Re: Possible FTBS?

[Rudy Godoy Guillén]

Hello,

2011/8/17 Rudy Godoy Guillén <rudy at stone-head.org>

<removing some bits>


> I've managed to isolate the problem. The error is related to the jar files
> on clc/lib. The Debian build uses debian/build-jars to make symlinks to
> installed Java libs, however the "normal" upstream ant build downloads from
> eucalyptus and builds them correctly.
>
> Currently I've the following version from sid:
> - groovy 1.8.1
>
> cloud-lib.tar.gz ships:
> - groovy 1.7.0
>
> The packaging build error, at the end, is related to Jar Index conflict.
> According it's definition there's a difference between what is expected and
> what is in the INDEX.LIST for that class in the jar file. I'm about to
> identify if this is related to the groovy version or to other class.
>
>
> Best regards,
> Rudy
>
>
> /home/rudy/debian/devel/soc-2011/eucalyptus/pkg-eucalyptus/build-area/eucalyptus-2.0.3/clc/modules/msgs/src/main/java/\
> org/apache/tools/ant/util/DateUtils.java
> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup
> failed:
> General error during conversion: Invalid index
>
> sun.misc.InvalidJarIndexException: Invalid index
>         at
> sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:870)
>         at
> sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:779)
>         at sun.misc.URLClassPath.getResource(URLClassPath.java:185)
>         at java.net.URLClassLoader$1.run(URLClassLoader.java:209)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
>         at
> groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:673)
>         at
> groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:540)
>         at
> org.codehaus.groovy.control.ResolveVisitor.resolveToClass(ResolveVisitor.java:663)
>         at
> org.codehaus.groovy.control.ResolveVisitor.resolve(ResolveVisitor.java:268)
>         at
> org.codehaus.groovy.control.ResolveVisitor.resolveFromStaticInnerClasses(ResolveVisitor.java:446)
>         at
> org.codehaus.groovy.control.ResolveVisitor.resolve(ResolveVisitor.java:268)
>         at
> org.codehaus.groovy.control.ResolveVisitor.visitClass(ResolveVisitor.java:1128)
>
>
> --
> Rudy Godoy
> http://stone-head.org
>
>

After some time trying to figure out what the problem is I did the simple
thing and told the build not to use the debian/build-jars file to link with
system-wide jars (installed by the dependencies). The build was successful
and I'm about to install it and test. I'll also commit this change to the
repo.

For this problem to be eliminated, given we want to use java package
dependencies for the build system, we need to figure which is the class
(jar) file that makes the JarIndex fail. There are ways to do it using
Eclipse, which seems to be the most accurate we can get so far according my
research on the subject.

Though this is not a definitive solution it seems to work. We now should
focus on upgrading the packaging system and tackle those remaining bits.

Have a nice weekend.

-- 
Rudy Godoy
http://stone-head.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-eucalyptus-maintainers/attachments/20110820/21d50e35/attachment.html>