Your message dated Sun, 30 Dec 2018 18:22:53 +0100
with message-id <20181230172253.ga20...@aurel32.net>
and subject line Re: pacemaker is linked to both libcfg6 and libcfg7 causing it 
to fail to start
has caused the Debian Bug report #917801,
regarding pacemaker is linked to both libcfg6 and libcfg7 causing it to fail to 
start
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 ow...@bugs.debian.org
immediately.)


-- 
917801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pacemaker
Version: 1.1.18-2
Severity: grave
Tags: buster
Justification: renders package unusable

pacemaker in buster hasn't been rebuilt against corosync 3.0.0, so it
ends up to be dynamically linked to both libcfg6 and libcfg7. In turns
this causes it to fail to start with a configuration validation error.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message ---
Version: 1.1.19-1

On 2018-12-30 15:02, Aurelien Jarno wrote:
> Source: pacemaker
> Version: 1.1.18-2
> Severity: grave
> Tags: buster
> Justification: renders package unusable
> 
> pacemaker in buster hasn't been rebuilt against corosync 3.0.0, so it
> ends up to be dynamically linked to both libcfg6 and libcfg7. In turns
> this causes it to fail to start with a configuration validation error.

pacemaker version 1.1.19 has just migrated to buster. I am therefore
closing the bug.

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurel...@aurel32.net                 http://www.aurel32.net

--- End Message ---

Reply via email to