[debian-mysql] Bug#416145: marked as done (Replication failure with auto-increment and on duplicate key update)

[Debian Bug Tracking System]

Your message dated Tue, 10 Apr 2012 19:32:28 +0100
with message-id <4F847CBC.5030302 at periapt.co.uk>
and subject line closing
has caused the Debian Bug report #416145,
regarding Replication failure with auto-increment and on duplicate key update
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 owner at bugs.debian.org
immediately.)


-- 
416145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416145
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Alan Tam <Tam at SiuLung.com>
Subject: Replication failure with auto-increment and on duplicate key update
Date: Sun, 25 Mar 2007 16:51:04 +0800
Size: 3066
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20120410/fb039025/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Nicholas Bamber <nicholas at periapt.co.uk>
Subject: closing
Date: Tue, 10 Apr 2012 19:32:28 +0100
Size: 1705
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20120410/fb039025/attachment-0003.mht>