On 04/07/14 12:24, Michael Biebl wrote: > Am 04.07.2014 10:10, schrieb Emilio Pozuelo Monfort: >> On 29/06/14 20:16, Michael Biebl wrote: >>> Source: sagan >>> Version: 0.2.1.r1-1 >>> Severity: serious >>> >>> Due to the latest updates in liblognorm, sagan now FTBFS >>> >>> configure:2701: checking whether the C compiler works >>> configure:2723: gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 >>> -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-z,relro >>> conftest.c -lm -lestr -lee >&5 >>> /usr/bin/ld: cannot find -lee >>> collect2: error: ld returned 1 exit status >>> >>> Full build log is attached. >>> >>> Due to the changes in liblognorm, the liblognorm-dev package no longer >>> depends on libee-dev. >>> >>> Simply adding libee-dev to Build-Depends was not sufficient, due to a >>> bug in libestmp [1] >> >> libestmp got fixed. Is adding libee-dev enough now? > > No, unfortunately not. > As I wrote in the bug report, sagan's configure needs to use pkg-config > proper to get all necessary compiler and linker flags. > Without them it will fail to find the json header files. > > Even when this is fixed, I don't know if sagan already works with > liblognorm. > > My suggestion would be to RM it from testing.
There are a few fixes upstream to fix these issues: https://github.com/beave/sagan/commits/master But yes, we can remove this package from testing is this bug doesn't get fixed. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
