Bug#918029: marked as done (transition: corosync)
Your message dated Mon, 7 Jan 2019 18:06:58 +0100
with message-id <b01c66f8-470d-a6c2-340f-3d214c99edf0@debian.org>
and subject line Re: Bug#918029: transition: corosync
has caused the Debian Bug report #918029,
regarding transition: corosync
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@bugs.debian.org
immediately.)
--
918029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918029
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
Hi,
First of all, I'm sorry for inadvertently starting the Corosync
transition. It isn't a problematic one, though: please schedule a
rebuild of sheepdog and dlm on all relevant architectures, that should
finish it.
Thanks,
Feri.
Ben file (the auto-corosync tracker looks fine, though):
title = "corosync";
is_affected = .depends ~ "libcfg6" | .depends ~ "libcfg7";
is_good = .depends ~ "libcfg7";
is_bad = .depends ~ "libcfg6";
--- End Message ---
--- Begin Message ---
On 05/01/2019 09:11, Ferenc Wágner wrote:
> Emilio Pozuelo Monfort <pochu@debian.org> writes:
>
>> On 02/01/2019 15:21, Ferenc Wágner wrote:
>>
>>> please schedule a rebuild of sheepdog and dlm on all relevant
>>> architectures, that should finish it.
>>
>> Done.
>
> Thanks, the rebuilds went through just fine, I think we can close this
> transition. (I didn't with this message in case you still need to do
> some administration.)
Yes. Let's close this.
Emilio
--- End Message ---
Reply to: