tomcat9 9.0.64-2 MIGRATED to testing

2022-06-26 Thread Debian testing watch
FYI: The status of the tomcat9 source package in Debian's testing distribution has changed. Previous version: 9.0.63-1 Current version: 9.0.64-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

Processed: owner 1013324

2022-06-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > owner 1013324 ! Bug #1013324 [lz4-java] Upgrade package to latest upstream version Owner recorded as tony mancill . > thanks Stopping processing here. Please contact me if you need assistance. -- 1013324:

hbci4java 3.1.60+dfsg-1 MIGRATED to testing

2022-06-26 Thread Debian testing watch
FYI: The status of the hbci4java source package in Debian's testing distribution has changed. Previous version: 3.1.59+dfsg-1 Current version: 3.1.60+dfsg-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day

hibiscus 2.10.7+dfsg-1 MIGRATED to testing

2022-06-26 Thread Debian testing watch
FYI: The status of the hibiscus source package in Debian's testing distribution has changed. Previous version: 2.10.6+dfsg-2 Current version: 2.10.7+dfsg-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day

Bug#1013565: libitext5-java: FTBFS: dh_auto_test: error:

2022-06-26 Thread Markus Koschany
Same here. Looks related to maven-resource-plugins / maven-filtering and #1013582 and #1013586 signature.asc Description: This is a digitally signed message part __ This is the maintainer address of Debian's Java team

Bug#1013586: Bug#1013595: plexus-io: FTBFS: Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.1.0:testResources

2022-06-26 Thread Markus Koschany
I believe this is related to a bug in maven-filtering or maven-resources- plugin. According to https://issues.apache.org/jira/browse/MRESOURCES-237 the behavior how symlinks are handled has changed between version 2.7 and 3.0.x of maven-resources-plugin. This is apparently fixed in