On 2006-09-03 Charles Lepple wrote: > Christian Hammers wrote: > > Hello Charles > > > > On 2006-09-01 Charles Lepple wrote: > >> Here is a trace of /etc/cron.daily/mysql-server: > > > > It seems to me that you have an old script from MySQL 4.x > > laying around, the current 5.x packages do not have an > > /etc/cron.daily/ file as they use "expire_days" in /etc/mysql/my.cnf. > > > > Can you verify with "dpkg -S etc/cron.daily/mysql-server" if this skript > > still belongs to any package? If not, just delete it. > > $ dpkg -S /etc/cron.daily/mysql-server > mysql-server: /etc/cron.daily/mysql-server > > $ aptitude show mysql-server > Unable to find an archive "sarge" for the package "mysql-server" > Package: mysql-server > State: installed > Automatically installed: no > Version: 5.0.24-3 > Priority: optional > Section: misc > Maintainer: Christian Hammers <[EMAIL PROTECTED]> > Uncompressed Size: 69.6k > Depends: mysql-server-5.0 > Provided by: mysql-server-5.0, mysql-server-4.1 > [...] > > It looks like the non-virtual mysql-server is in testing, but so is the > mysql-server-5.0 which provides the virtual package. Hm, maybe that while upgrading from the real to the virtual mysql-server package, dpkg thought that it was not supposed to remove the leftover config files as the package name did not vanish. I will try this out and maybe add a explicit remove to the mysql-server-5.0 package.
You can safely do a "rm /etc/cron.daily/mysql-server" and are done. > Apparently, my pin file and sources.list are not in sync, because the > system is a stable/testing hybrid (instead of testing/unstable, as the pin > information may have indicated). > > 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.. bye, -christian- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
