Re: putting bouncycastle 1.49 into backports?
- To: debian-java@lists.debian.org
- Cc: 'Jitsi Developers' <dev@jitsi.org>
- Subject: Re: putting bouncycastle 1.49 into backports?
- From: Daniel Pocock <daniel@pocock.com.au>
- Date: Tue, 21 Jan 2014 11:51:53 +0100
- Message-id: <[π] 52DE5149.2010602@pocock.com.au>
- In-reply-to: <[π] 52DE4BA9.2020907@apache.org>
- References: <[π] 52DD0D54.6050404@pocock.com.au> <[π] 52DD1316.4060700@apache.org> <[π] 52DE4761.3080901@pocock.com.au> <[π] 52DE4BA9.2020907@apache.org>
On 21/01/14 11:27, Emmanuel Bourg wrote: > Le 21/01/2014 11:09, Daniel Pocock a Γ©crit : > >> When you say creating separate binary packages, do you mean creating >> packages that have the version in the name such as >> >> libbcprov1.49-java.deb (1.49) >> >> libbcprov-java.deb (existing 1.44 in wheezy) > Yes exactly. And the package would have to be slightly modified to not > conflict with libbcprov-java (by renaming the jars in /usr/share/java > and changing the version of the Maven artifacts in /usr/share/maven-repo). > Based on Ingo's reply, I think this is what we would have to do because they definitely need that version in wheezy-backports if Jitsi is to be backported
Reply to:
- References:
- putting bouncycastle 1.49 into backports?
- From: Daniel Pocock <daniel@pocock.com.au>
- Re: putting bouncycastle 1.49 into backports?
- From: Emmanuel Bourg <ebourg@apache.org>
- Re: putting bouncycastle 1.49 into backports?
- From: Daniel Pocock <daniel@pocock.com.au>
- Re: putting bouncycastle 1.49 into backports?
- From: Emmanuel Bourg <ebourg@apache.org>
- putting bouncycastle 1.49 into backports?
- Prev by Date: RE: [jitsi-dev] putting bouncycastle 1.49 into backports?
- Next by Date: RFS: plexus-compiler/1.9.2-2
- Previous by thread: Re: putting bouncycastle 1.49 into backports?
- Next by thread: RE: [jitsi-dev] putting bouncycastle 1.49 into backports?
- Index(es):