Bug#589359: Non-coordinated transition leading some packages to FTBFS

[Mehdi Dogguy <mehdi@dogguy.org>]

On  0, Laurent Fousse <laurent@komite.net> wrote:
> Hello,
> 
> * Mehdi Dogguy [Sat, Jul 17, 2010 at 01:48:39AM +0200]:
> > According to [1], mpfr_random was removed in 3.0 and that's causing apron
> > to FTBFS.
> > 
> > [1]
> > http://www.pubbs.net/201005/gcc/43610-gnu-mpfr-300-release-candidate.html
> > 
> > It would have been so nice if mpfr maintainers tested correctly their
> > r-deps, spot failures and file bugs against affected packages.
> 
> You're right. I should have made a more systematic testing, I merely
> tested the r-depends I knew about (talked with Matthias Klose for gcc,
> mpfi and mpclib I can take care of). I'll do better next time...
> 

No problem. Please don't hesitate to contact the Release Team before
you upgrade a package with a big number of r-deps. Even if the library
is advertised to be binary compatible with the old one, it allows us
to follow the migration and try to ease its migration.

BTW, what's your plan regarding src:mpfr? The libmpfr-dev package has
been dominated out. I guess, packages will progressively pick out
libmpfr4. And relatively soon after, mpfr will become useless (Well,
it's already the case).

Regards,

> 
> I'll try to provide a patch monday for apron.
> 

Thanks!

Regards,

-- 
Mehdi Dogguy