The bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=320869
shows that MySQL is not able to start up with its default configuration
file on unstable(sid) + testing(etch)!
This has been a known bug since Aug 2, and according to the bug report
this has been fixed on sunday, 14 Aug, but the fix has not yet made it
to testing and apparently not even to unstable either.
It seems to me that a MySQL that won't even start up is a very serious
issue. When can we expect this fixed bug to propagate through to
testing/etch, after 3 weeks of broken-ness?
Where am I wrong when I assume that something this serious should have
been caught in unstable/sid and not make it through to testing at all?
And that if it *is* found in testing, I expected it to get fixed ASAP.
I'm not complaining that it didn't, because I have no right to, I'm only
wondering where I went wrong in my expectations...
The problem is that mysql-server installs version 4.0.24-10 and requires
mysql-common which is present in version 5.0.7beta-1 (etch) or
5.0.11beta-3 (sid). In both versions, mysql-common's my.cnf contains a
"old_passwords = 1" setting, not understood by mysql-server 4.0.24-10.
Using a default CD install, the first thing I do is simply:
apt-get install mysql-server
This yields:
.....
Setting up mysql-server (4.0.24-10) ...
Stopping MySQL database server: mysqld.
Starting MySQL database server: mysqld...failed.
Please take a look at the syslog.
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2)'
Check that mysqld is running and that the socket:
'/var/run/mysqld/mysqld.sock' exists!
MySQL on testing/etch can not even start up!
Peter
--
Peter Valdemar Mørch
http://www.morch.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
