Bug#687694: bouncycastle: 1.44 and 1.46 are not binary compatible

[Emmanuel Bourg]

I reviewed the reverse dependencies of bouncycastle and here is the
current status:

ivy                       OK
                          2.3.0-2 uploaded on 2013-05-16

jakarta-jmeter            PATCHED, applied upstream
                          2.8-1 uploaded on 2013-07-05

jenkins-instance-identity PENDING, waiting for jenkins/1.480.3+dfsg-1


libcommons-openpgp-java   OK
                          0+svn533492-4 uploaded on 2013-07-09

libitext-java             PATCHED
                          2.1.7-6 uploaded on 2013-05-31

libitext5-java            OK
                          5.4.1-1 uploaded on 2013-05-18

libj2ssh-java             OK, dependency removed
                          0.2.9-4 uploaded on 2013-05-02

libjgroups-java           OK, dependency removed
                          2.12.2.Final-3 uploaded on 2013-07-03

libjgroups2.6-java        OK, optional runtime dependency


libpdfbox-java            PATCHED, applied upstream
                          1:1.8.2+dfsg-1 uploaded on 2013-06-02

red5                      OK, but FTBFS for another reason
                          1.0~svn4374-2 uploaded on 2012-08-16

voms-api-java             FTBFS #713204
                          Patch forwarded upstream, maintainer contacted

wagon2                    OK, not a build dependency
                          2.4-1 uploaded on 2013-06-25

wss4j                     OK, use BC with reflection


Most packages have been fixed and/or uploaded after bouncycastle 1.46
reached unstable. jenkins-instance-identity has been fixed on Alioth but
can't be uploaded until the new version of jenkins is in unstable.
voms-api-java is the last package that has to be updated.


Emmanuel Bourg