[ubuntu/cosmic-proposed] pacemaker 1.1.18-2ubuntu1 (Accepted)

Wed Jul 25 05:42:16 UTC 2018

pacemaker (1.1.18-2ubuntu1) cosmic; urgency=medium

  * Merge with Debian. Remaining changes:
    - d/control: Demote fence-agents to Suggests, avoiding main
      inclusion.
    - debian/patches/pacemaker_is_partof_corosync.patch: Default systemd
      unit hard-requires corosync.
      + Debian disagrees in Debian bug 887563 message 36. We could revert back
        to Debian's behaviour, but keeping the patch in this merge maintains
        existing behaviour for Ubuntu users pending any separate future
        decision.
  * Drop changes:
    - Drop upstreamed patches (dropped in Debian now instead).
    - Refresh d/p/portability-define-EKEYREJECTED-if-necessary.patch: no longer
      needed; dropped in Debian.
    - d/pacemaker.{pre,post}inst flag for corosync: upgrade path no longer
      needed post-Bionic.

pacemaker (1.1.18-2) unstable; urgency=medium

  * [812cda7] Fixup symbols files.
    The Hurd architecture looks strangely irregular.
  * [38d49fe] Simplify autopkgtest script
  * [87f237c] Remove trailing empty line from debian/changelog

pacemaker (1.1.18-1) unstable; urgency=medium

  * [da58a7f] Some overlooked libqb vs new binutils symbol flux
  * [c6b8c8a] New upstream release (1.1.18)
  * [871dcfa] Delete upstreamed patches, refresh the rest
  * [7c9e795] Add post-1.1.18 regression fixes
    https://lists.clusterlabs.org/pipermail/users/2017-December/014227.html
    * 1.1.18 improved scalability by eliminating redundant node attribute
    write-outs. This proved to be too aggressive in one case: when a
    cluster is configured with only IP addresses (no node names) in
    corosync.conf, attribute write-outs can be incorrectly delayed; in the
    worst case, this prevents a node from shutting down due to the shutdown
    attribute not being written.
    * 1.1.18 overhauled unfencing in order to support it on remote nodes.
    (Unfencing is for devices such as fence_scsi that require a fenced node
    to be explicitly re-admitted to the cluster.) This made the faulty
    assumption that the fence devices themselves could operate before
    unfencing happened. As a result, a cluster with unfencing could see
    unnecessary fence device monitoring failures (these do not harm the
    cluster's ability to fence or unfence).
    * 1.1.18 implemented ordering constraints for the new bundle resource
    type. This had a corner case that could lead to an invalid transition.
    As part of the fix for this, we have included a fix for an issue
    discussed in an earlier thread on this list ("pcmk_remote evaluation"),
    so the cluster will always prefer the newest Pacemaker Remote
    connection to a remote node, even if an older (dead) connection has not
    yet timed out.
  * [4d9e29c] Update Standards-Version to 4.1.4 (no changes required)
  * [c77cdf4] Migrate to salsa.debian.org/ha-team
  * [269dcb6] Switch to HTTPS in the Homepage and Source URLs
  * [371288b] Switch to Debhelper compat level 11
  * [c58d652] Replace hand-made control substitution with stock dpkg method.
    Remove the superfluous check_header_deps call as well.
  * [eb76cbd] Update symbols files

Date: Tue, 24 Jul 2018 14:12:03 +0100
Changed-By: Robie Basak <robie.basak at ubuntu.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/+source/pacemaker/1.1.18-2ubuntu1
-------------- next part --------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 24 Jul 2018 14:12:03 +0100
Source: pacemaker
Binary: pacemaker-common pacemaker-resource-agents pacemaker pacemaker-cli-utils pacemaker-remote pacemaker-doc libcib4 libcib-dev libcrmcluster4 libcrmcluster-dev libcrmcommon3 libcrmcommon-dev libcrmservice3 libcrmservice-dev liblrmd1 liblrmd-dev libpe-rules2 libpe-status10 libpengine10 libpengine-dev libstonithd2 libstonithd-dev libtransitioner2
Architecture: source
Version: 1.1.18-2ubuntu1
Distribution: cosmic
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Robie Basak <robie.basak at ubuntu.com>
Description:
 libcib-dev - cluster resource manager CIB library development
 libcib4    - cluster resource manager CIB library
 libcrmcluster-dev - cluster resource manager cluster library development
 libcrmcluster4 - cluster resource manager cluster library
 libcrmcommon-dev - cluster resource manager common library development
 libcrmcommon3 - cluster resource manager common library
 libcrmservice-dev - cluster resource manager service library development
 libcrmservice3 - cluster resource manager service library
 liblrmd-dev - cluster resource manager LRMD library development
 liblrmd1   - cluster resource manager LRMD library
 libpe-rules2 - cluster resource manager Policy Engine rules library
 libpe-status10 - cluster resource manager Policy Engine status library
 libpengine-dev - cluster resource manager Policy Engine library development
 libpengine10 - cluster resource manager Policy Engine library
 libstonithd-dev - cluster resource manager STONITH daemon library development
 libstonithd2 - cluster resource manager STONITH daemon library
 libtransitioner2 - cluster resource manager transitioner library
 pacemaker  - cluster resource manager
 pacemaker-cli-utils - cluster resource manager command line utilities
 pacemaker-common - cluster resource manager common files
 pacemaker-doc - cluster resource manager HTML documentation
 pacemaker-remote - cluster resource manager proxy daemon for remote nodes
 pacemaker-resource-agents - cluster resource manager general resource agents
Changes:
 pacemaker (1.1.18-2ubuntu1) cosmic; urgency=medium
 .
   * Merge with Debian. Remaining changes:
     - d/control: Demote fence-agents to Suggests, avoiding main
       inclusion.
     - debian/patches/pacemaker_is_partof_corosync.patch: Default systemd
       unit hard-requires corosync.
       + Debian disagrees in Debian bug 887563 message 36. We could revert back
         to Debian's behaviour, but keeping the patch in this merge maintains
         existing behaviour for Ubuntu users pending any separate future
         decision.
   * Drop changes:
     - Drop upstreamed patches (dropped in Debian now instead).
     - Refresh d/p/portability-define-EKEYREJECTED-if-necessary.patch: no longer
       needed; dropped in Debian.
     - d/pacemaker.{pre,post}inst flag for corosync: upgrade path no longer
       needed post-Bionic.
 .
 pacemaker (1.1.18-2) unstable; urgency=medium
 .
   * [812cda7] Fixup symbols files.
     The Hurd architecture looks strangely irregular.
   * [38d49fe] Simplify autopkgtest script
   * [87f237c] Remove trailing empty line from debian/changelog
 .
 pacemaker (1.1.18-1) unstable; urgency=medium
 .
   * [da58a7f] Some overlooked libqb vs new binutils symbol flux
   * [c6b8c8a] New upstream release (1.1.18)
   * [871dcfa] Delete upstreamed patches, refresh the rest
   * [7c9e795] Add post-1.1.18 regression fixes
     https://lists.clusterlabs.org/pipermail/users/2017-December/014227.html
     * 1.1.18 improved scalability by eliminating redundant node attribute
     write-outs. This proved to be too aggressive in one case: when a
     cluster is configured with only IP addresses (no node names) in
     corosync.conf, attribute write-outs can be incorrectly delayed; in the
     worst case, this prevents a node from shutting down due to the shutdown
     attribute not being written.
     * 1.1.18 overhauled unfencing in order to support it on remote nodes.
     (Unfencing is for devices such as fence_scsi that require a fenced node
     to be explicitly re-admitted to the cluster.) This made the faulty
     assumption that the fence devices themselves could operate before
     unfencing happened. As a result, a cluster with unfencing could see
     unnecessary fence device monitoring failures (these do not harm the
     cluster's ability to fence or unfence).
     * 1.1.18 implemented ordering constraints for the new bundle resource
     type. This had a corner case that could lead to an invalid transition.
     As part of the fix for this, we have included a fix for an issue
     discussed in an earlier thread on this list ("pcmk_remote evaluation"),
     so the cluster will always prefer the newest Pacemaker Remote
     connection to a remote node, even if an older (dead) connection has not
     yet timed out.
   * [4d9e29c] Update Standards-Version to 4.1.4 (no changes required)
   * [c77cdf4] Migrate to salsa.debian.org/ha-team
   * [269dcb6] Switch to HTTPS in the Homepage and Source URLs
   * [371288b] Switch to Debhelper compat level 11
   * [c58d652] Replace hand-made control substitution with stock dpkg method.
     Remove the superfluous check_header_deps call as well.
   * [eb76cbd] Update symbols files
Checksums-Sha1:
 e6d5fa3559f1722679622c5f8b05b328511053ba 3922 pacemaker_1.1.18-2ubuntu1.dsc
 2fc2a74bb13917e44189dc330f8104fd27c5ec79 5321212 pacemaker_1.1.18.orig.tar.gz
 012cfbb5649f71bbb03941258fb08667d45d78fc 81268 pacemaker_1.1.18-2ubuntu1.debian.tar.xz
Checksums-Sha256:
 62c145a2b100229ab255d8efaf96084727188bfc257fb12ac27c9fb0679558ab 3922 pacemaker_1.1.18-2ubuntu1.dsc
 a71921c1e2a93c5bed6199fb41464a1cff887be515f4a0ffbc2c92bc98d233af 5321212 pacemaker_1.1.18.orig.tar.gz
 4dd53939261f50cf35a614332e3ac133b74a37578a802b4c35dfa21bab1f970a 81268 pacemaker_1.1.18-2ubuntu1.debian.tar.xz
Files:
 2e60680f96a37a499e514db8b753ab46 3922 admin optional pacemaker_1.1.18-2ubuntu1.dsc
 d9edfa9eeba87fd3480690fad3af6049 5321212 admin optional pacemaker_1.1.18.orig.tar.gz
 64a50994f1b5676cea784e87fb500049 81268 admin optional pacemaker_1.1.18-2ubuntu1.debian.tar.xz
Original-Maintainer: Debian HA Maintainers <debian-ha-maintainers at lists.alioth.debian.org>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJbWA2jAAoJEOVkucJ1vdUuFr4QAKIIQc0pEOdApc+oyM5KYacd
7T25MWInK7UAhZvNv43k2jAAe1CsM15b5Aac0rUfFVoMMEhSEz/hY2evG6VjH9r+
LI2cnFkiz42I8NtoCqKdrxL6BLHJ2lA7L9tAV+Jzt5pUcEhka6jiCROwN8421Fqo
v20tyQPNAsIsAfirc7swUQDfh9PE5Pnkv5Pel8N08woQijdfVioptcHFhPhGHZmZ
EzHgZrrGLQTrJKChgZU+0kqko2CvQkk+B43KYlV1vEOB463+nVzPWIAlcHfWfPxx
c9HL/+Pr6mVJJ5naqXa8jXEZVBoZpvscu27fNrKGMSKi2ZgoswgGic5VX0FQM80r
1dSldQFyzgIG7C10hOMF7jpwYmDj6mMpo/pwX3YYt3jnfgywdCqwRd7DPDX+7j44
ppUyj7mAqNbV/g5ULw/WNqaJGz2QoSVbWGIPvlskr7SNHvMZL04TSDdkAQUexGsB
SIxWg3i9Wyqam8/putz4sp8n9rsGzcAYj5f+OU/1TJ6UbL1JPltWLSbylUNVb26B
5YLMOfQaa+8pMQpZzhnjxZIjRNaj7iBhqHH/AhnpcW/Iinl2HyncwiyRI/mjPBAB
pzHSLqfKENriR+g6l5IWVKUurj0U8qFRxlu6yUkT7RfTt4lTD/LsakIs4DaH1zBB
9LovCUD6Wt0oZ4eiua1a
=5UtA
-----END PGP SIGNATURE-----