[ppa] FTBFS libarchive on launchpad

Looks like it's this bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659294
I quote the solution:
> The problem is that the test suite run (just like the whole package
> build) is done within fakeroot (which means fakeroot-tcp), triggering
> Debian's #534879. ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534879 )

It was fixed in 3.0.3-4 for debian and it worked: http://goo.gl/PMwjN (link to git diff)
I don't know why it doesn't work for ppa build daemon

http://code.google.com/p/libarchive/issues/detail?id=223 looks relevant. Can you try that patch?

https://launchpad.net/~medigeek/+archive/evince-xps/+build/3249143
It builds fine in pbuilder-dist with the patch applied.

I just noticed that the amd64 ~ppap1 was built: https://launchpad.net/~medigeek/+archive/evince-xps/+build/3245957
https://launchpad.net/~medigeek/+archive/evince-xps/+build/3245957/+files/buildlog_ubuntu-precise-amd64.libarchive_3.0.3-5%7Eppap1_BUILDING.txt.gz

~ppap4 failed to build again:
https://launchpad.net/~medigeek/+archive/evince-xps/+build/3249143
https://launchpadlibrarian.net/94776212/buildlog_ubuntu-precise-i386.libarchive_3.0.3-5~ppap4_FAILEDTOBUILD.txt.gz

I'll test with a pbuilder 32-bit (my pbuilder was 64-bit) and let you know.

Works with and without the patch (tried ~ppap1 and ~ppap4):

I suppressed the error from the tests (~ppap6 and ~ppap7), trying to get some more information out of the build daemon log:
https://launchpadlibrarian.net/94807629/buildlog_ubuntu-precise-i386.libarchive_3.0.3-5~ppap6_BUILDING.txt.gz

find command came out empty:
find /tmp/ -maxdepth 1 -iname "libarchive*" -type f -exec echo "DEBUG-TEST {}" \; -a -exec cat "{}" \;
find /tmp/ -maxdepth 1 -iname "bsd*" -type f -exec echo "DEBUG-TEST {}" \; -a -exec cat "{}" \;

I suppose I can't use the find or cat command in /tmp of a build daemon? :)

> ~ppap6 and ~ppap7
Pardon ~ppap6 only. I won't make a ~ppap7
However, I'm still interested why the tests fail on launchpad.

I made a mistake when I was trying to read the logs in /tmp (libarchive* and bsd* are folders, not files).
Here are the log files (~ppap7):
https://launchpadlibrarian.net/94867412/buildlog_ubuntu-precise-i386.libarchive_3.0.3-5~ppap7_BUILDING.txt.gz

I hope it helps debug the problem.

That shows the problem -- libarchive is trying to use FIEMAP, which was only introduced in Linux 2.6.28. The buildds mostly run Hardy (2.6.24) kernels.

http://code.google.com/p/libarchive/issues/detail?id=238 has a patch.

This bug was fixed in the package libarchive - 3.0.3-6ubuntu1

---------------
libarchive (3.0.3-6ubuntu1) precise; urgency=low

  * Add 03_ignore_fiemap_errors.patch: Ignore FIEMAP errors on linux < 2.6.28.
    This fixes a failing test case (and thus FTBFS) when building this on a
    hardy-based buildds. This can be dropped once the buildds get upgraded to
    something more modern. Thanks to Savvas Radevic for the patch!
    (LP: #942994)
 -- Martin Pitt <email address hidden> Fri, 16 Mar 2012 10:10:24 +0100