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, 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). 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. I assume the situation would be the same for gmp and mpfr, should a soname change occur. I'll upload in the evening, my PGP key is not available at work. Thanks for the report and sorry about the breakage. Laurent. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
