Hi, Adam D. Barratt wrote:
> > IIRC Julien binNMUed tarantool last time only on those > > architectures where it built successfully in the pastm namely amd64 > > and i386. > > It /has/ built successfully in the past on kfreebsd-*; it only > stopped doing so with the 1.4.9+20130608.2059-1 upload. Sorry, my fault this time. I meant "where it built successfully on the last upload". > Both testing and unstable contain tarantool packages on kfreebsd-* > with a dependency on "binutils (<< 2.23)". Whilst we can obviously > skip the binNMUs on those architectures, none of binutils or the > other packages will be able to migrate unless either tarantool gets > fixed or we remove it from testing Right. JFTR: #715358 was filed on 8-Jul-2013, the FTBFS was already on 11-Jun-2013. There's a new upstream snapshot of tarantool waiting[1] in NEW since 20-Jun-2013, i.e. was uploaded one week after the FTBFS. Of course no mention of #715358 due to the date, but also no mention of fixing a FTBFS. So I have no idea if that package would fix the FTBFS. [1] https://ftp-master.debian.org/new/tarantool_1.4.9+20130620.1443-1.html Regards, Axel -- ,''`. | Axel Beckert <[email protected]>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
