[debian-mysql] Bug#830976: marked as done (logrotate failures if mysql server is not running)

Mon Mar 20 09:21:03 UTC 2017

Your message dated Mon, 20 Mar 2017 09:19:09 +0000
with message-id <E1cptT3-0000fU-Hl at fasolo.debian.org>
and subject line Bug#830976: fixed in mariadb-10.1 10.1.22-1
has caused the Debian Bug report #830976,
regarding logrotate failures if mysql server is not running
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.)

-- 
830976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830976
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Biebl <biebl at debian.org>
Subject: logrotate failures if mysql server is not running
Date: Wed, 13 Jul 2016 15:21:11 +0200
Size: 4241
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20170320/f74b8694/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: =?utf-8?b?T25kxZllaiBTdXLDvQ==?= <ondrej at debian.org>
Subject: Bug#830976: fixed in mariadb-10.1 10.1.22-1
Date: Mon, 20 Mar 2017 09:19:09 +0000
Size: 8490
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20170320/f74b8694/attachment-0003.mht>