Le 22/04/2010 12:35, Norbert Tretkowski a écrit :
Am Donnerstag, den 22.04.2010, 11:53 +0200 schrieb Julien Bernard:
Le 22/04/2010 10:55, Norbert Tretkowski a écrit :
Am Donnerstag, den 22.04.2010, 10:13 +0200 schrieb Julien Bernard:
I think this is a real packaging bug. mysql-server-core-5.1 needs a file
(/usr/bin/mysqld_safe) that is in mysql-server-5.1 so
mysql-server-core-5.1 should depend on mysql-server-5.1 or this file
should be in mysql-server-core-5.1.
Please take a look at bug #548419, it explains why we introduced the
mysql-server-core-5.1 package, and why it's intended that it doesn't
depend on the mysql-server-5.1 package.
Just install mysql-server-5.1 (or mysql-server) instead.
The point is not to merge mysql-server-5.1 and mysql-server-core-5.1,
but to solve this real bug. As I understand #548419, there is no need to
start a mysql server with mysql-server-core-5.1, so the init script
should disappear (or rather go in mysql-server-5.1) and it would solve
the problem.
The init script is not part of mysql-server-core-5.1 package:
# dpkg -L mysql-server-core-5.1 | grep init
#
It's in the mysql-server-5.1 package instead:
# dpkg -L mysql-server-5.1 | grep init
/etc/init.d
/etc/init.d/mysql
So the problem comes from the upgrade from the old server to the new
server/server-core. Aptitude told me that I had some config files left
from server, so I purged them and all is correct now.
Thanks for your patience.
Julien
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
