I also noticed an or1k build on an unofficial archive with the same error
http://wannabuild.cmd.nu/fetch.php?pkg=pcmanfm&arch=or1k&ver=1.2.0-1&stamp=1401451299
Given that this seems to be happening on at least three mostly
independent architectures I doubt it's an architecture issue per-se, the
question is what is causing it? maybe contamination in some package?
some installation order related glitch?
I just tried and failed to reproduce this locally on amd64, i'll give it
a try in an arm64 qemu chroot sometime.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
