Bug#717669: nmu: grive_0.2.0-1 tarantool_1.4.9+20130611.2012-1 tulip_3.7.0dfsg-4 ggcov_0.8.4-2 (rebuild against new binutils)

["Adam D. Barratt" <adam@adam-barratt.org.uk>]

On 2013-07-23 17:27, Axel Beckert wrote:
> Adam D. Barratt wrote:
> > > http://bugs.debian.org/714801, http://bugs.debian.org/714809 and
> > > http://bugs.debian.org/714810. Again, grive, tarantool and tulip
> > > prevent updating gcc-4.8, binutils and friends on my amd64 box. 
> > ggcov
> > > is 32-bit only, but hasn't had a sourceful upload since the 
> > previous
> > > binNMU either.
> >
> > tarantool needs #715358 fixing before it can migrate (or be usefully
> > binNMUed on !amd64).
>
> I guess you mean !linux.

Yes, sorry.

> 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.

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 (which is was what I was attempting to indicate in my 
earlier message).

Regards,

Adam