On 2014-05-17 Michael Biebl <em...@michaelbiebl.de> wrote:
> Am 26.04.2014 20:01, schrieb Andreas Metzler:
>> Package: network-manager
>> Version: 0.9.8.8-7
[...]
>> Usertags: gnutls3
>> network-manager uses gcrypt directly (not only as an indirect dependency
>> via gnutls) but does not build-depend on it.
> Hi Andreas,
> could you tell me what I'm supposed to fix here and how this relates to
> gnutls3?
Hello Michael,
I am sorry that report was too terse, let me give some background:
We want to transition to GnuTLS v3 ("gnutls28"). As part of this I have
tried building all reverse (build-)dependencies of GnuTLSv2
("gnutls26") against gnutls28 (I locally added a libgnutls-dev
packages which depends on libgnutls28-dev.) and submitted bugreports
against all failing ones.
network-manager uses both gnutls and gcrypt. However it does not
build-depend on libgcrypt11-dev or libgcrypt20-dev but instead relies
on libgnutls-dev depending on libgcrypt11-dev. Since gnutls28 uses
nettle instead of gcrypt as crypto backend this dependency is gone and
network-manager FTBFS.
---
How to fix this bug:
The quickest way would be to simply add a b-d on libgcrypt11-dev.
However what I would like to see is upgrading the b-d from
libgnutls-dev to "libgnutls28-dev, libgcrypt20-dev | libgcrypt11-dev".
Obviously it is less than optimal that network-manager then depends on
two crypto libraries (indirectly on nettle via gnutls, and gcrypt).
This could be fixed by using the GnuTLS crypto API instead of
gcrypt. It should not be very difficult for a programmer, but I cannot
provide a patch since I am not a programmer.
hth, cu Andreas
--
`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'
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
