This bug was fixed in the package pacemaker - 1.1.17+really1.1.16-1ubuntu2
--------------- pacemaker (1.1.17+really1.1.16-1ubuntu2) artful; urgency=medium
* Rebuilding with a version greater than 1.1.17: - pacemaker 1.1.17 was pushed to Artful at one point and then got deleted.
pacemaker (1.1.16-1ubuntu2) artful; urgency=high
* Fix FBTFS situations - d/p/crm-mon-protect-against-non-standard-or-failing-asctime.patch: Fix: crm_mon: protect against non-standard or failing asctime.
- d/libcrmservice3.symbols: Mark symbols optional to avoid FTBFS with newer toolchains and make it cleanly backportable to older toolchains.
* Properly restart corosync and pacemaker together (LP: #1740892) - d/pacemaker.preinst: flag corosync to restart pacemaker on upgrade.
-- Eric Desrochers <email address hidden> Mon, 26 Feb 2018 12:36:37 -0500
This bug was fixed in the package pacemaker - 1.1.17+ really1. 1.16-1ubuntu2
--------------- really1. 1.16-1ubuntu2) artful; urgency=medium
pacemaker (1.1.17+
* Rebuilding with a version greater than 1.1.17:
- pacemaker 1.1.17 was pushed to Artful at one point and then got deleted.
pacemaker (1.1.16-1ubuntu2) artful; urgency=high
* Fix FBTFS situations mon-protect- against- non-standard- or-failing- asctime. patch:
- d/p/crm-
Fix: crm_mon: protect against non-standard or failing asctime.
- d/libcrmservice 3.symbols: Mark symbols optional to avoid FTBFS
with newer toolchains and make it cleanly backportable to older toolchains.
* Properly restart corosync and pacemaker together (LP: #1740892) preinst: flag corosync to restart pacemaker on upgrade.
- d/pacemaker.
-- Eric Desrochers <email address hidden> Mon, 26 Feb 2018 12:36:37 -0500