[debian-mysql] Bug#416145: Replication failure with auto-increment and on duplicate key update

[Christian Hammers]

tags 416145 + confirmed upstream wontfix
forwarded 416145 http://bugs.mysql.com/bug.php?id=24432
stop

Hi!

On 2007-03-25 Alan Tam wrote:
> 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.

So if I understand correctly, the version in etch is not buggy in a sense
that it causes trouble when people only use etch<->etch replication and
patching this minor bug would require some tricks?

In this case I would rather stay with the recommendation to only use the very
same version in replication and if people need a newer version they should
use backports.org on both sides.

I leave this bug open for reference though.

bye,

-christian-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20070502/91a7f674/signature.pgp