[Debian-ha-maintainers] Bug#868019: marked as done (corosync: Unexpected restart corosync during upgrade from 2.3.6 to 2.4.2)

[Debian Bug Tracking System]

Your message dated Tue, 11 Jul 2017 11:14:45 +0200
with message-id <20170711091445.4n5pqvlb3t4cudh3 at msg.df7cb.de>
and subject line Re: [Debian-ha-maintainers] Bug#868019: corosync: Unexpected restart corosync during upgrade from 2.3.6 to 2.4.2
has caused the Debian Bug report #868019,
regarding corosync: Unexpected restart corosync during upgrade from 2.3.6 to 2.4.2
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.)


-- 
868019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868019
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Azat Yakupov <azat_yakupov at inbox.ru>
Subject: corosync: Unexpected restart corosync during upgrade from 2.3.6 to 2.4.2
Date: Tue, 11 Jul 2017 11:59:28 +0300
Size: 2255
URL: <http://lists.alioth.debian.org/pipermail/debian-ha-maintainers/attachments/20170711/d8dee068/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Christoph Berg <myon at debian.org>
Subject: Re: [Debian-ha-maintainers] Bug#868019: corosync: Unexpected restart corosync during upgrade from 2.3.6 to 2.4.2
Date: Tue, 11 Jul 2017 11:14:45 +0200
Size: 2637
URL: <http://lists.alioth.debian.org/pipermail/debian-ha-maintainers/attachments/20170711/d8dee068/attachment-0001.mht>