[debian-mysql] Bug#851234: marked as done (Security fixes from the January 2017 CPU)

Debian Bug Tracking System owner at bugs.debian.org
Fri Jan 20 15:09:15 UTC 2017


Your message dated Fri, 20 Jan 2017 15:07:26 +0000
with message-id <E1cUamk-0001yC-K4 at fasolo.debian.org>
and subject line Bug#851234: fixed in mysql-5.6 5.6.35-1
has caused the Debian Bug report #851234,
regarding Security fixes from the January 2017 CPU
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.)


-- 
851234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851234
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: "Norvald H. Ryeng" <norvald.ryeng at oracle.com>
Subject: Security fixes from the January 2017 CPU
Date: Fri, 13 Jan 2017 09:19:34 +0100
Size: 2778
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20170120/c97e0f63/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Lars Tangvald <lars.tangvald at oracle.com>
Subject: Bug#851234: fixed in mysql-5.6 5.6.35-1
Date: Fri, 20 Jan 2017 15:07:26 +0000
Size: 6560
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20170120/c97e0f63/attachment-0001.mht>


More information about the pkg-mysql-maint mailing list