peter green wrote:
Still stumped as to why, the obvious cause for something like this
would be a directory called debian/tmp/usr/include/libfm already
existing at the time the symlink was created but I can't find any
evidence in the build log for the creation of such a directory at that
point. A race condition is possible I guess but I don't see any
evidence of paralell building.
I added some test code to debian/rules and did an arm64 build and the
package came out without the problem. So some sort of race condition
seems likely. Next step will be to see if any other architectures are
affected.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
