Bug#727193: still unresolved?

2015-02-10 Thread Daniel Pocock
What is the status of this bug? The upstream discussion in bug 68376 talks about the technicalities of turning this on and off but it doesn't really give any insight into what people should do in practice For example, - Why does it skip that table and no other table? - Would it be better to

Bug#727193: [debian-mysql] Bug#727193: still unresolved?

2015-02-10 Thread Norvald H. Ryeng
On Tue, 10 Feb 2015 13:56:20 +0100, Daniel Pocock dan...@pocock.pro wrote: On 10/02/15 13:46, Norvald H. Ryeng wrote: On Tue, 10 Feb 2015 09:37:28 +0100, Daniel Pocock dan...@pocock.pro wrote: What is the status of this bug? The status is forwarded, which means it's been forwarded to

Bug#727193: [debian-mysql] Bug#727193: still unresolved?

2015-02-10 Thread Norvald H. Ryeng
On Tue, 10 Feb 2015 09:37:28 +0100, Daniel Pocock dan...@pocock.pro wrote: What is the status of this bug? The status is forwarded, which means it's been forwarded to upstream. Upstream has closed it as not a bug. I guess we should close it in Debian too. The upstream discussion in

Bug#727193: [debian-mysql] Bug#727193: still unresolved?

2015-02-10 Thread Daniel Pocock
On 10/02/15 13:46, Norvald H. Ryeng wrote: On Tue, 10 Feb 2015 09:37:28 +0100, Daniel Pocock dan...@pocock.pro wrote: What is the status of this bug? The status is forwarded, which means it's been forwarded to upstream. Upstream has closed it as not a bug. I guess we should close it in