Bug#757575: transition: libgcrypt20

[Andreas Metzler]

On 2014-08-10 Emilio Pozuelo Monfort <pochu at debian.org> wrote:
[...]
> > 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.

Hello,

Results of trying to rebuild all (about 90) packages build-depending
on libgcrypt11-dev (or the virtual package libgcrypt-dev) are quite
encouraging:

I have seen only 8 failing builds

These need source updates:
758997 anytun_0.3.4-2
758993 libcrypt-gcrypt-perl_1.26-1
758995 uswsusp_1.0+20120915-5
gnutls26_2.12.23-17 (Not really relevant since it will not be shipped
in jessie, however Werner Koch has pointed out a patch which I am
trying in experimental.)

The other packages are not broken by newer libgcrypt specifically but
simply FTBFS in current sid, I have filed bugs if they were missing.
chromium-browser_35.0.1916.153-2
758999 gjiten_2.6-2.2
openvas-libnasl_2.0.2-2.1
759000 remmina_1.0.0-6

OTOH out of the packages build-depending on the virtual
libgcrypt-dev package[1] (and not just as an alternative secondary
dependency as in "libgcrypt11-dev | libgcrypt-dev") only single one
(gjiten) failed. I plan NMU this one and later let libgcrypt20-dev
provide libgcrypt-dev.

cu Andreas

[1] dar, gjiten, goldencheetah, grive, libktorrent, libmicrohttpd,
openldap, pam-pgsql, percona-xtrabackup, seccure, wireshark,
xorg-server, zabbix
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'