Ok, I've put up MPs for Trusty (just corosync) and Xenial (corosync and
pacemaker). I think that's correct, and the underlying bug here (package
upgrade of corosync does not lead to pacemaker restarting) should be
resolved in both cases [1) in c#33]. Additionally, case 2) in c#33 is
resolved in
Testing on Trusty:
# apt-get install corosync pacemaker
# Make corosync start at boot
# sed -i 's/no/yes/' /etc/default/corosync
# Make pacemaker start at boot
# update-rc.d pacemaker defaults
# reboot
# service corosync status; service pacemaker status
* corosync is running
pacemakerd (pid
** Changed in: clamav (Ubuntu)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
** Changed in: clamav (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
** Bug watch added: Debian Bug tracker #887563
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887563
** Also affects: corosync (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887563
Importance: Unknown
Status: Unknown
--
You received this bug notification
Public bug reported:
php-defaults (57ubuntu1) bionic; urgency=medium
* Merge with Debian unstable (LP: #1743904). Remaining changes:
- d/control, d/rules: bump to php7.1 as the default.
+ Update text of d/control to refer to Ubuntu and 7.1 as well.
+ d/control generated by
