Package: libitext-java
Version: 2.1.7-3
Severity: serious
Tags: wheezy
Hi,
According to Julius Davies[1], libitext-java in testing is broken due
to an ABI change in libbcprov-java (bouncycastle). Allegedly a no
change rebuild against the testing version og libbcprov-java should
solve the issue.
Package: bouncycastle
Version: 1.46+dfsg-7
Severity: serious
Hi,
As reported by Julius Davies[1], packages built against
bouncycastle/1.46 breaks when run with bouncycastle/1.44.
The known issue is that some constants in bcprov changed type, but
there may be others. Using dak, I have come up
libitext-java_2.1.7-4_amd64.changes uploaded successfully to localhost
along with the files:
libitext-java_2.1.7-4.dsc
libitext-java_2.1.7-4.debian.tar.gz
libitext-java_2.1.7-4_all.deb
libitext-rtf-java_2.1.7-4_all.deb
libitext-rups-java_2.1.7-4_all.deb
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 15 Sep 2012 11:02:37 +0200
Source: libitext-java
Binary: libitext-java libitext-java-gcj libitext-rtf-java libitext-rups-java
Architecture: source all amd64
Version: 2.1.7-4
Distribution: unstable
Urgency: low
FYI: The status of the bouncycastle source package
in Debian's testing distribution has changed.
Previous version: 1.44+dfsg-2
Current version: 1.44+dfsg-3.1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day
Your message dated Sat, 15 Sep 2012 23:48:02 +
with message-id e1td25i-0003xg...@franck.debian.org
and subject line Bug#687539: fixed in plexus-interactivity-api 1.0-alpha-6-7
has caused the Debian Bug report #687539,
regarding plexus-interactivity-api: missing jar from /usr/share/java
to be
6 matches
Mail list logo