Bug#801321: commons-javaflow: depends on obsolete libasm2-java library

[Markus Koschany]

Control: severity -1 serious

This is now the last package that blocks the removal of libasm2-java and
the old substance and liblaf-* src packages. I'm raising the severity to
serious because we should either fix this bug or request the removal of
commons-javaflow before the next freeze to avoid shipping libasm2-java
in Stretch.

Markus



signature.asc
Description: OpenPGP digital signature
__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Processed: Re: Bug#801321: commons-javaflow: depends on obsolete libasm2-java library

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #801321 [commons-javaflow] commons-javaflow: depends on obsolete 
libasm2-java library
Severity set to 'serious' from 'important'

-- 
801321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

Bug#801321: commons-javaflow: depends on obsolete libasm2-java library

[Markus Koschany]

Control: tags -1 patch

I have updated commons-javaflow to the latest svn snapshot.
Unfortunately there are no releases and tags is another mysterious word
for this project.

I think the package works but jasperreports, the only
reverse-dependency, fails to build from source.

If I remove the dstdir and mode attribut in line 122 of build.xml, ant
is able to execute the javaflow task for jasperreports. However then the
build FTBFS again with this error message:

BUILD FAILED
/build/jasperreports-6.1.1+dfsg/build.xml:122:
java.lang.IllegalStateException: Undefined label used
at org.objectweb.asm.util.CheckMethodAdapter.visitMaxs(Unknown Source)
at
org.apache.commons.javaflow.bytecode.transformation.asm.ContinuationMethodAdapter.visitMaxs(ContinuationMethodAdapter.java:313)

etc.

This bug is known upstream at:

https://issues.apache.org/jira/browse/SANDBOX-476

There is no solution so far hence I am stuck at this point.

The updated debian directory is attached to this bug report. Just run
"debian/rules get-orig-source" to retrieve the sources.

Markus


commons_javaflow_debian.tar.gz
Description: application/gzip


signature.asc
Description: OpenPGP digital signature
__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#801321: commons-javaflow: depends on obsolete libasm2-java library

[Emmanuel Bourg]

Le 01/11/2015 23:59, Markus Koschany a écrit :

> I have updated commons-javaflow to the latest svn snapshot.
> Unfortunately there are no releases and tags is another mysterious word
> for this project.

javaflow is still a sandbox project at Apache Commons. This means it has
never been officially released and thus never tagged.

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

Bug#801321: commons-javaflow: depends on obsolete libasm2-java library

[Markus Koschany]

Package: commons-javaflow
Severity: important
User: pkg-java-maintainers@lists.alioth.debian.org
Usertags: oldlibs libasm2-java

Hi,

commons-javaflow depends on libasm2-java, which is obsolete and was replaced by
libasm4-java. commons-javaflow should be ported to the new libasm4-java
version, so that we can remove the old, unmaintained one.

There are only four packages in Debian which depend on libasm2-java:

 - substance
 - liblaf-widget-java
 - jasperreports
 - commons-javaflow

substance and liblaf-widget-java are both five years old and there is no
indication of upstream development. substance is a build-dependency of
jajuk which is still actively developed but the Debian package is outdated.
jasperreports is also severely outdated. commons-javaflow has no
reverse-dependencies and a very low popcon value.

It would be great to "save" the first three packages, commons-javaflow should
probably be removed.


Regards,

Markus

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