[debian-mysql] Bug#811443: mysql-5.6: Multiple security fixes from the January 2016 CPU

Salvatore Bonaccorso carnil at debian.org
Tue Jan 19 19:57:53 UTC 2016


Hi Robie,

On Tue, Jan 19, 2016 at 12:15:53PM +0000, Robie Basak wrote:
> Question for the security team.
> 
> On Mon, Jan 18, 2016 at 09:16:06PM +0100, Norvald H. Ryeng wrote:
> > Source: mysql-5.6
> > Version: 5.6.27-2
> > Severity: grave
> > Tags: security upstream fixed-upstream
> 
> 5.6.27-2 only exists in testing, and I uploaded 5.6.28-1 to unstable
> recently. It hasn't landed in testing yet, but when it does this bug
> will be fixed.
> 
> Is there anything we should do to accelerate this, given that it will be
> a security fix?

How fast (unless some RC bug is introduced) a package migrates from
unstable to testing is controlled by the urgency set. In this case it
will now happen in three days, which is fine.

See https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#testing-unstable

Regards,
Salvatore



More information about the pkg-mysql-maint mailing list