Package: mysql-server-5.0 Severity: normal Tags: patch Hi,
I am recently upgrading one of the slaves of a master-slave replication to etch, for 2 reasons: 1. attempt to fix http://bugs.mysql.com/bug.php?id=20188 which claims to be fixed since 5.0.24 2. reherse migration to testing; since we can affort zero downtime, we can only first migrate slave to new version, switch it to a master, and then upgrate the original master with a reversed replication Then I begin to be hit by http://bugs.mysql.com/bug.php?id=24432 . To repeat the details in the 2 bug reports, the fix of 20188 has introduced another bug which make any version newer than 5.0.24 give a wrong auto_increment behavior (irrepective to replication). This behavior is finally fixed by 24432 in the recent 5.0.38 version. The wrong auto_increment behavior in its own is a bit mild (it skips some usable auto_increment values) but it causes replication problems with other master/slave without this bug. This bug is serious because any of the master or the slave with version between 5.0.24 and 5.0.36 inclusive will make replication fail, although it will work if both master and slave are within this range of versions. See the chart in the bug report for more details. If etch ships with an unpatched version of 5.0.32, then people will have a hard time upgrading to etch, and also upgrading to lenny later. Since the bug is only fixed in upstream in 5.0.38, which is very unlikely to be uploaded to etch, I propose to backport the patch. Here is the patch: http://lists.mysql.com/commits/19547 Backporting the patch will be a bit tricky, since upstream has inserted some code to detect version numbers to determine whether a certain replication will fail or survive. If debian make their 5.0.32-7etch2 free of this bug, then the logic there has to be altered. Maybe it is safe for us to drop the checking, but this may cause problem if some people run a replication between debian and another distro. -- Regards, Alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
