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 sh
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...@bug
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
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 dstdi
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 t
5 matches
Mail list logo
