Christian Hammers wrote: > On 2006-09-03 Charles Lepple wrote: >> Would you suggest enabling unstable as well, then upgrading >> mysql-server-5.0, and removing the dummy package if it doesn't get >> removed >> automatically? > Oh, hm, I have no experience with mixing stable/testing, I would rather > recommend using only stable and get mysql-server-5.0 from > www.backports.org. > Using testing/unstable might also work but stable+testing.. hmm..
On further inspection, it seems that there is a mysql-server non-virtual package in unstable (in addition to the virtual one provided by mysql-server-5.0): from http://packages.qa.debian.org/m/mysql-dfsg-5.0/news/20060903T223230Z.html Description: libmysqlclient15-dev - mysql database development files libmysqlclient15off - mysql database client library mysql-client - mysql database client (current version) mysql-client-5.0 - mysql database client binaries mysql-common - mysql database common files (e.g. /etc/mysql/my.cnf) mysql-server - mysql database server (current version) mysql-server-5.0 - mysql database server binaries So that may be confusing dpkg/apt as well. I can try going to testing-only if that will rule out any weirdness, but it looks like the problem is independent of that. Removing the non-virtual mysql-server did get rid of the cron job as expected, but that package probably needs to be removed from the archive if the mysql-server-<version> packages are providing it as well. It also seems like mysql-client is also both real and virtual in testing/unstable, although I have not run across any similar problems there. -- Charles Lepple
