Hadmut <[EMAIL PROTECTED]> wrote:
Subject: ISAM trap in package upgrade
Date: Mon, 27 Feb 2006 10:51:44 +0100
ugly trap in mysql-server-package:
When the preinst script finds any .ISM files in /var/lib/mysql, it
denies the upgrade. But then, the old mysql-server-package is already
removed, and current debian distribution does not contain the old
mysql-server anymore. No chance to update the databases to a newer
file format anymore, no way to get a mysql-server running.
Christian Hammers <[EMAIL PROTECTED]> wrote:
tags 354544 + wontfix confirmed
Sadly this problem seems not to be solvable. I can abort the
installation of the mysql-server-5.0 but it is not possible to
tell apt-get not to continue and remove the conflicting mysql-server-4.1
package.
Lucky, after the apt-get run it should be no problem to just reinstall
the mysql-server-4.1 package, convert the table manually and then
try again.
Well, unfortunately this isn't true either. The user will *not* be able to
reinstall mysql-server-4.1 after an upgrade. The reason is that
mysql-server-5.0 depends on mysql-common => 5.0 which conflicts with
mysql-common-4.1.
Now there is a *lot* (let's say f.ex amaroc) of software that depends on
libmysqlclient. That means when upgrading we will have the following
scenario:
apt-get will:
* remove mysql-server-4.1, mysql-common-4.1 and old libmysqlclient
* unpack, preconfigure and set up a mysql-common => 5.0, libmysqlclient15
and a lot of software that depends on libmysqlclient15.
* setup of mysql-server-5.0 will fail due to an existing ISAM DB
Now the user will be left with a semi-updated system which will:
* not allow him to install mysql-server-4.1 since it depends on old
libmysqlclient because installing old libmysqlclient would oblige the
user to downgrade all installed packages the now depend on
libmysqlclient15 that conflicts through mysql-common > 5.0 with old
libmysqlclient.
Since downgrading is not supported in Debian, this means that the user
either can throw away his old data captured in his ISAM DBs or reinstall
sarge or a different distro somewhere or boot from Knoppix. Which is at
least painful and at most impossible depending on the skills of the user.
I'm not sure which severity to give this bug, but IMHO it's release critical.
*t
--
--------------------------------------------------------
Tomas Pospisek
http://sourcepole.com - Linux & Open Source Solutions
--------------------------------------------------------
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
