Your message dated Wed, 14 Oct 2015 19:26:58 +0200
with message-id <>
and subject line Re: jasperreports: depends on obsolete libasm2-java library
has caused the Debian Bug report #801320,
regarding jasperreports: depends on obsolete libasm2-java library
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Package: jasperreports
Severity: important
Usertags: oldlibs libasm2-java


jasperreports depends on libasm2-java, which is obsolete and was replaced by
libasm4-java. jasperreports 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.



--- End Message ---
--- Begin Message ---
Version: 4.1.3+dfsg-4

This one was apparently fixed with the latest upload to unstable. Closing.


Attachment: signature.asc
Description: OpenPGP digital signature

--- End Message ---
This is the maintainer address of Debian's Java team
Please use for discussions and questions.

Reply via email to