On dim., 2014-05-11 at 18:45 +0200, David Suárez wrote: > Source: strongswan > Version: 5.1.3-2 > Severity: serious > Tags: jessie sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20140510 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. > > Relevant part (hopefully): > > checking for main in -lcrypto... yes > > checking openssl/evp.h usability... yes > > checking openssl/evp.h presence... yes > > checking for openssl/evp.h... yes > > checking for main in -lgcrypt... no > > configure: error: gcrypt library not found > > The full build log is available from: > > http://aws-logs.debian.net/ftbfs-logs/2014/05/10/strongswan_5.1.3-2_unstable.log >
Hi GnuTLS maintainers. It seems that strongSwan (wrongly) missed a build-dep on libgcrypt*-dev, and started to FTBFS just recently. I'm unsure why it happened just know, I guess some -dev package was depending on the libgcrypt11-dev package. Now, an easy fix would be to add either libgcrypt*-dev package to build-deps, but now I'm a bit unsure which version to add. Would it be possible to summarize the reasons we have both in the archive and if there's a reason not the use the most recent one? Thanks in advance, and regards, -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part
