On Sun, Dec 15, 2013 at 07:55:06PM -0300, Miguel Landaeta wrote:
> On Sun, Dec 15, 2013 at 11:34:25PM +0100, Emmanuel Bourg wrote:
> > This is unlikely to be a simple upgrade. cglib 3 switched to asm 4
> > and there are many incompatibilities according to clirr:
> The advisable thing would be to introduce a cglib3 package, right?

I rebuilt all reverse build dependencies on libcglib-java against
CGLIB 3.1 and I found 3 packages with FTBFS errors related to this


I have a package cglib3 ready but I don't know if I just should update
cglib or introduce this new package. What's for sure, I don't want to
have packages broken in the archive for months while we wait for upstream
to port their software or for ourselves to patch those packages.

I would prefer to introduce cglib3 and migrate to it since that way
should be less intrusive.


Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at
"Faith means not wanting to know what is true." -- Nietzsche

Attachment: signature.asc
Description: Digital signature

This is the maintainer address of Debian's Java team
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to