[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#917803: marked as done (nmu: pacemaker_1.1.18-2)



Your message dated Sun, 30 Dec 2018 15:46:07 +0100
with message-id <20181230144605.xasn2aanmaklji7o@debian.org>
and subject line Re: nmu: pacemaker_1.1.18-2
has caused the Debian Bug report #917803,
regarding nmu: pacemaker_1.1.18-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@bugs.debian.org
immediately.)


-- 
917803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917803
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: binnmu

pacemaker in buster hasn't been rebuilt in buster for the corosync
transition, causing it to fail to start. In turns it causes the
pacemaker autopkgtests to fail, which is considered as a glibc
regression.

The following binNMU should fix the issue:

nmu pacemaker_1.1.18-2 . ANY . buster . -m "Rebuild against libcfg7 (Closes: #917801)"

-- 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 ---
On Sun, Dec 30, 2018 at 03:07:09PM +0100, Aurelien Jarno wrote:
> pacemaker in buster hasn't been rebuilt in buster for the corosync
> transition, causing it to fail to start. In turns it causes the
> pacemaker autopkgtests to fail, which is considered as a glibc
> regression.
> 
> The following binNMU should fix the issue:
> 
> nmu pacemaker_1.1.18-2 . ANY . buster . -m "Rebuild against libcfg7 (Closes: #917801)"

As discussed on irc:

There is a newer version in unstable, which will probably migrate soon and
hopefully fix the issue.

Also binNMUs from t-p-u are currently (temporarily) disabled in britney, so
this wouldn't work anyway.

Closing.

Cheers,

Ivo

--- End Message ---

Reply to: