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 change: libhibernate3-java sisu-guice spock 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. Comments? -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9 "Faith means not wanting to know what is true." -- Nietzsche
Description: Digital signature
__ This is the maintainer address of Debian's Java team <http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use debian-j...@lists.debian.org for discussions and questions.