On Sat, Apr 30, 2016 at 3:39 PM, Andreas Beckmann <a...@debian.org> wrote: > On Thu, 21 Apr 2016 07:45:34 -0500 (CDT) "Steve M. Robbins" <s...@debian.org> > wrote: >> Boost 1.55 has not built correctly since the GCC 5 introduction in July 2015 >> and I plan >> to ask for its removal from unstable very shortly. It has already been >> removed from >> testing. >> >> The package mongodb appeared on a list of reverse dependencies generated >> using 'dak rm -Rn boost1.55' (see below). This bug is to request an >> upload with updated boost dependencies. >> >> If your package build-depends on the default boost, then a simple rebuild >> will suffice. > > This package has stale binaries due to FTBFS on these two architectures: > >> mongodb: mongodb-clients [hurd-i386 kfreebsd-i386] >> mongodb-server [hurd-i386 kfreebsd-i386] > > I'd recommend this: > > Control: reassign -1 ftp.debian.org > Control: severity -1 normal > Control: retitle -1 RM: mongodb [hurd-i386 kfreebsd-i386] -- RoM; FTBFS, > depends on boost 1.55 Sorry for the slow reaction. The FTBFS reason is the package test case. It's threaded and the sequence is confused by the file timestamp resolution of Hurd and kFreeBSD architectures. It's one second only (Linux has millisecond resolution). Question is, how should it be handled? Disable self-tests, ignore the results or maybe remove mongodb from the mentioned architectures?
Regards, Laszlo/GCS
