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

2013-08-27 Thread Steffen Möller
> Gesendet: Dienstag, 27. August 2013 um 00:47 Uhr > Von: "Emmanuel Bourg" > An: 687...@bugs.debian.org, 687694-submit...@bugs.debian.org > Betreff: Bug#687694: bouncycastle: 1.44 and 1.46 are not binary compatible > > Quick update on the remaining package

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

2013-08-26 Thread Emmanuel Bourg
Quick update on the remaining packages affected by the transition: jenkins-instance-identity OK 1.3 uploaded on 2013-07-27 voms-api-java PATCHED 2.0.9-1.1 uploaded on 2013-07-16 jglobus PATCHED, patch app

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

2013-07-12 Thread gregor herrmann
On Fri, 12 Jul 2013 13:51:43 +0200, Emmanuel Bourg wrote: > voms-api-java FTBFS #713204 > Patch forwarded upstream, maintainer contacted This information is not visible in the bug report; could you add it there please? (By concidence I looked at this bug yes

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

2013-07-12 Thread 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-jmeterPATCHED, applied upstream 2.8-1 uploaded on 2013-07-05 jenkins-instance-id

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

2012-09-15 Thread Niels Thykier
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 wi