[Bug 1743904] [NEW] Please merge with Debian unstable 57

[Nish Aravamudan]

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 `./debian/rules debian/control`

 -- Nishanth Aravamudan   Wed, 17 Jan
2018 15:55:22 -0800

** Affects: php-defaults (Ubuntu)
 Importance: Undecided
 Assignee: Nish Aravamudan (nacc)
 Status: In Progress

** Changed in: php-defaults (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Changed in: php-defaults (Ubuntu)
   Status: New => In Progress

** Description changed:

- TBD
+ 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 `./debian/rules debian/control`
+ 
+  -- Nishanth Aravamudan   Wed, 17 Jan
+ 2018 15:55:22 -0800

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1743904

Title:
  Please merge with Debian unstable 57

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-defaults/+bug/1743904/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

[Nish Aravamudan]

** 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 because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1740892

Title:
  corosync upgrade on 2018-01-02 caused pacemaker to fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1740892/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

[Nish Aravamudan]

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 1927) is running...

Add PPA and upgrade corosync:

# add-apt-repository ppa:nacc/lp1740892
# apt-get update; apt-get install corosync

# service corosync status; service pacemaker status
 * corosync is running
pacemakerd is stopped

So what is in my PPA is not yet a fix and I think I see why:

Preparing to unpack .../corosync_2.3.3-1ubuntu4.1~ppa3_amd64.deb ...
 * Stopping corosync daemon corosync  
...
Setting up corosync (2.3.3-1ubuntu4.1~ppa3) ...
Installing new version of config file /etc/init.d/corosync ...
 * Restarting corosync daemon corosync  

   warning [MAIN  ] Could not 
lock memory of service to avoid page faults: Cannot allocate memory (12)

So the postinst change is correct and we now restart corosync instead of
start it. However, because the old package's prerm is run, that leads to
a stop of corosync which in turn causes pacemaker to exit. When we run
our updated init-script, it does not detect that pacemaker is running
and so does not restart it.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1740892

Title:
  corosync upgrade on 2018-01-02 caused pacemaker to fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1740892/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1532608] Re: Files moved around in clamav without appropriate Breaks/Replaces, causing upgrade failures

[Andreas Hasenack]

** 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.
https://bugs.launchpad.net/bugs/1532608

Title:
  Files moved around in clamav without appropriate Breaks/Replaces,
  causing upgrade failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1532608/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

[Nish Aravamudan]

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 both cases, but requires different changes in each release.

I will propose similar MPs for bionic as are in xenial.

The corresponding packages are building in the PPA currentlly.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1740892

Title:
  corosync upgrade on 2018-01-02 caused pacemaker to fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1740892/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs