Bug#757575: transition: libgcrypt20

[Emilio Pozuelo Monfort <pochu@debian.org>]

Control: forwarded -1 https://release.debian.org/transitions/html/libgcrypt20.html
Control: tags -1 confirmed pending

On 09/08/14 15:48, Andreas Metzler wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: transition
> 
> Hello,
> 
> I would like to make sure that we only ship one gcrypt version in
> jessie and am therefore opening the transition tracker now.
> 
> libgcrypt20 is mostly API compatible to libgcrypt11. The main reason
> why we have versioned -dev packages is that libgnutls26 is one of the
> packages which cannot work with the old API. libgnutls26 should not be
> shipped in jessie so I envision that it should be possible to make
> major parts of this transition by bin-NMUs since I will be able to
> make libgcrypt11-dev a dummy package depending on libgcrypt20-dev
> after libgnutls26 has been dropped.
> 
> libgcrypt11's upstream support will end on 2016-12-31.
> 
> I will do some test builds to find out more.
> 
> Ben file:
> 
> title = "libgcrypt20";
> is_affected = .depends ~ "libgcrypt11" | .depends ~ "libgcrypt20" | .depends ~ "libgcrypt11-dev" | .depends ~ "libgcrypt20-dev" | .depends ~ "libgcrypt-dev";
> is_good = .depends ~ "libgcrypt20";
> is_bad = .depends ~ "libgcrypt11";

I have added a tracker for this (with minor tweaks). Let us know
when you have more information on this.

Emilio