On 11.09.2009 13:31, Laurent Fousse wrote:
Hello,
* Matthias Klose [Fri, Sep 11, 2009 at 11:48:06AM +0200]:
libmpc1 is used as a dependency for GCC (>= 4.5). Uploading a new
mpclib with a changed soname built from the same source package
makes GCC uninstallable, because the old libmpc1 package is not
available anymore in the archive. And GCC needs GCC to build ... To
avoid this situation, please upload mpclib with a new soname if the
soversion of the library changes. Currently this is only seen with
the gcc-snapshot package, but once gcc-4.5 is in the archive (and
the sonmae changes again), this becomes a serious problem, which can
be avoid by the changed packaging.
I thought I did the right thing wrt soname and package name change,
yes.
but if I understand correctly we are in a special situation because of
the GCC -> GCC self-dependancy loop (GCC needs GCC, and libmpc1, to
build a new version of itself which would then depend on libmpc2).
yes.
The fix is then to revert the source package mpclib to provide libmpc1
again, and upload a new source package mpclib2 with the new version.
no, nothing is needed now, because the default compiler doesn't have the
dependency on libmpc1, and gcc-snapshot can be rebuilt using a compiler without
a dependency on libmpc1.
I assume the situation would be the same for gmp and mpfr, should a
soname change occur.
exactly. same for ppl and cloog.
Thanks for the report and sorry about the breakage.
no, the compiler isn't broken, I'll care about the gcc-snapshot update myself.
Just a reminder for the next soname change.
Matthias
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
