Bug#789518: wagon2: FTBFS in sid

Hans Joachim Desserud debian at desserud.org
Fri Jul 24 18:28:25 UTC 2015


I took a look at this issue, and while I haven't solved the problems
I've found some clues which might be useful for the next person.

One of the things I found was an Ubuntu build log [1] from when it
built successfully. I know some packages have Ubuntu-deltas, but
for the most part its the same set of packages as Debian had at
the time.

> adding libxbean-java to Build-Depends makes
no difference.

Looking at the build log, it looks it was already pulled in due
to some dependency or another. I tried looking at whether the
missing class in question had changed in any obvious way in the
meantime, but didn't find anything suspicious.

I also briefly experimented with replacing libxbean-java and a
couple of other packages with .debs from stable, but didn't
see any difference.

What I believe is happening is that some test is run, which
happens to extend PlexusTestCase from plexus-container-default [2]
which again ends up in libxbean-java, does some reflection magic (?)
and fails to find a class. And it looks like the problem is that
something in this chain has changed since the package was built.

What I find really interesting is that I found another RC bug [3]
which has a strangely similar (but not identical!) stacktrace
and ends up complaining about not finding the same class. And
this also goes through PlexusTestCase and the rest of the chain.
So while I don't know what's going on, I'm fairly sure these two
are connected in some way.

[1] 
https://launchpadlibrarian.net/188300331/buildlog_ubuntu-vivid-amd64.wagon2_2.7-1_UPLOADING.txt.gz
[2] https://tracker.debian.org/pkg/plexus-container-default
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788980

-- 
mvh / best regards
Hans Joachim Desserud
http://desserud.org



More information about the pkg-java-maintainers mailing list