Please stop this ping pong, is useless for fixing this bug :) (and I get many mails because of this).
While trying to understand the root of this bug I found this: Get:424 http://debian.netcologne.de/debian/ unstable/main ecj kfreebsd-amd64 3.10.0-1 [13.2 kB] Get:425 http://debian.netcologne.de/debian/ unstable/main libecj-java-gcj kfreebsd-amd64 3.10.0-1 [1916 kB] Get:426 http://debian.netcologne.de/debian/ unstable/main ecj-gcj kfreebsd-amd64 3.10.0-1 [1653 kB] Get:540 http://incoming.debian.org/debian-buildd/ buildd-unstable/main libecj-java all 3.10.0+3.9.0-1 [1356 kB] this is the build log I'm referring to https://buildd.debian.org/status/fetch.php?pkg=gdcm&arch=kfreebsd-amd64&ver=2.4.2-1.1&stamp=1404597221 (the same happened for kfreebsd-i386) so maybe the problem is just that the buildd picked up various and probably non compatible binaries in that architecture? I hope a simple rebuild will fix this bug. For hurd I have no clue, seems a different issue. cheers, Gianfranco -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
