On 2014-04-27 Alberto Garcia <[email protected]> wrote: > On Sat, Apr 26, 2014 at 06:58:33PM +0200, Andreas Metzler wrote: >> event-dance uses gcrypt directly (not only as an indirect dependency >> via gnutls) but does not build-depend on it.
> There's libgcrypt11 and libgcrypt20 at the moment in the repository, > and I think event-dance doesn't care, but it should be the same as the > one required by gnutls, no? > I'm not sure what's the way to deal with this without having to > manually change the build dependency on gcrypt whenever gnutls > switches to a newer version. > It seems to me that we would be making the package more fragile just > for the sake of correctness with no other real benefit. Hello, that is not the case: * gnutls26 uses libgrypt11. gnutls26 is not developed anymore, libgcrypt20 drops some deprecated APIs, therefore gnutls26 cannot switch over. * gnutl28 does not use libgrypt at all. It uses nettle instead. I have stumbled over the issue when test-building all gnutls26 reverse dependencies against gnutls28. It is possible for event-dance to simply use whatever crypto backend gnutls uses, but a little bit more involved than adding a Build-Dependcy. It would need to stop using gcrypt directly and switch to the GnuTLS crypto API. On a sidenote: If event-dance can switch to libgnutl28-dev without breaking reverse depencies it should do so. 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 [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
