Ok I was able to reproduce the issue in a local arm64 qemu chroot.
It appears the cause is a difference in filelists between architectures.
amd64 has
lrwxrwxrwx root/root 0 2014-07-04 06:55 ./usr/include/libfm ->
libfm-1.0
While i386 and arm64 have
drwxr-xr-x root/root 0 2014-07-04 11:02 ./usr/include/libfm/
lrwxrwxrwx root/root 0 2014-07-04 11:02
./usr/include/libfm/libfm-1.0 -> libfm-1.0
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.
It would be easy enough to write a hack to patch this up between running
the upstream install target and actually building the package but it
would really be preferable to know why this is happening.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
