reassign 331396 libmysqlclient15
severity 331396 serious
thanks

Florent Angebault wrote:

>The problem is that "mysql-server-5.0" requires the package
>"libmysqlclient15" and the 2 others require the package
>"libmysqlclient14".
>
>While updrading, I get this message :
># apt-get update ; apt-get dist-upgrade
>[...]
>dpkg : erreur de traitement de
>/var/cache/apt/archives/libmysqlclient15_5.0.12beta-2_i386.deb
>(--unpack) :
> tentative de remplacement de « /usr/lib/libndbclient.so.0.0.0 », qui
> appartient aussi au paquet libmysqlclient14
>[...]
>
>Sorry, it's in french but it means that "libmysqlclient15" can't be
>unpacked because it tries to overwrite the file
>"/usr/lib/libndbclient.so.0.0.0" which was installed before by
>"libmysqlclient14".
>

This is a problem with libmysqlclient15 package (as is currently in
sid). The package contains the same files as libmysqlclient14-dev which
makes libmysqlclient15 unusable if you want to use 14-dev.

Either libcdbclient.so should be a static only library and be in the
-dev packages
*or*
be split off to its own package and be properly versioned.

PACKAGE                          FOUND IN
==============================================================
usr/lib/libndbclient.so.0        
libdevel/libmysqlclient14-dev,libs/libmysqlclient15
usr/lib/libndbclient.so.0.0.0    
libdevel/libmysqlclient14-dev,libs/libmysqlclient15


The problem in Etch is even worse because libndbclient.so* are in the clients 
libraries only.

PACKAGE                          FOUND IN
==============================================================
usr/lib/libndbclient.so.0        libs/libmysqlclient14,libs/libmysqlclient15
usr/lib/libndbclient.so.0.0.0    libs/libmysqlclient14,libs/libmysqlclient15



The only current workaround is to install libmysqlclient14 from Unstable
at which point you should be able to install libmysqlclient15 even if it
is currently a little broken.

- Adam




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to