libarchive 3.2.0 testsuite failure causes FTBFS on kfreebsd
Hello kfreebsd porters!
I've recently uploaded a new upstream release of libarchive (3.2.0) to
experimental. Apparently there's a regression on kfreebsd where one of
the tests now fails and we thus get FTBFS on kfreebsd-*.
Unfortunately the details of the failing test is not available in
the build log (only which files to look at), so a local build is needed
to be able to investigate it. eg:
| FAIL: bsdtar_test
| =================
|
|
| If tests fail or crash, details will be in:
| /tmp/bsdtar_test.2016-05-06T11.18.44-000
(above snippet from:
https://buildd.debian.org/status/fetch.php?pkg=libarchive&arch=kfreebsd-amd64&ver=3.2.0-1&stamp=1462533614
)
To make the matter worse we also have Bug#823893 (CVE-2016-1541) which
is fixed in 3.2.0 and I'd thus like to upload it to unstable ASAP.
Do you think there's any chance you will find time to help out with
looking into the cause of the regression any time soon?
Do you think uploading libarchive 3.2.0 to unstable would cause you much
problems?
Do you think we should delay (and for how long) the upload given the
above mentioned circumstances?
Regards,
Andreas Henriksson
Reply to: