On 15/01/16 02:50, Andreas Beckmann wrote: > Control: reopen -1 > Control: tag 808401 unreproducible > > On Sun, 10 Jan 2016 16:15:50 +0100 Gert Wollny <gw.foss...@gmail.com> wrote: >>> That package failed to build last time it was uploaded (and >>> binNMUed): >>> >>> https://buildd.debian.org/status/package.php?p=plastimatch > >> That was in December, and the problem was (most likely) that at that >> time insighttoolkit4 was still build against gdcm-2.4 (and an older >> dcmtk) resulting in this mixup. This was discussed in [1], and blocked >> by the now resolved bug [2]. > >> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808401 >> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808491 > >> I just had the build tested in an actual sid-amd64 cowbuilder >> environment, there it worked. > > I can confirm that rebuilding plastimatch works fine on amd64, didn't > try any other platform. > >> That said, I've also seen that insighttoolkit4 4.8.2-3 failed to build >> on i386 because of an internal compiler error, > > Successfully built after being given back. > > > Given that -2 was only built on 2 platforms so far (but against > libgdcm2.4), I'd recommend to NMU it there and to give it back > everywhere else: > > nmu plastimatch_162+dfsg-2 . amd64 mips64el . -m 'Rebuild against libgdcm2.6' > gb plastimatch_162+dfsg-2 . ANY
Scheduled, let's see how that goes. Cheers, Emilio
