Your message dated Tue, 01 May 2012 20:44:38 +0100
with message-id <[email protected]>
and subject line very old versions
has caused the Debian Bug report #416841,
regarding MySql 5.0.38 incompatible with linux kernel 2.4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
416841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416841
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mysql-server-5.0
Version: 5.0.38-1
As I just discovered the hard way (dist-upgrading a machine set to
'testing') that
it would appear somewhere between MySql 5.0.32 and 5.0.38, the newer
version of the server is not fully compatible with linux kernel 2.4.*
When apt was attempting to upgrade the package, it would start the
server and hang.
In my own debugging, I also ended up moving my /var/lib/mysql dir out
of the way, removing & purging all related mysql packages (server,
client, common, libs), making sure /etc/mysql was removed as well,
then performing a fresh reinstall. The server still would not start.
I downgraded to 5.0.32 from etch manually and pinned the package,
which seems to work fine on the 2.4 kernel.
Also, after 5.0.38 under the 2.4 kernel got ahold of the database
files, they were corrupted to the point of no longer directly working
with 5.0.32 either. A restore from backups was required.
It might be worth adding a dependency entry for the kernel in the next
update of this package.
To me, it seems a better option during an upgrade to see your kernel
will be replaced and cancel it, than to have apt simply upgrade to
5.0.38, not be able to start the server fully, and corrupt the
databases on disk.
Thanks -- Jon
--- End Message ---
--- Begin Message ---
--- End Message ---
