bump version to 2.4.2-2~pve4+2

[corosync-pve.git] / debian / changelog

diff --git a/debian/changelog b/debian/changelog
index f4a2790641fe2046b258e4c89971ae96c4ec9847..f58204f456488d00af2eb65dc8f8361ae7a853a0 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,33 @@
+corosync-pve (2.4.2-2~pve4+2) unstable; urgency=medium
+
+  * fix CVE-2018-1084
+
+ -- Proxmox Support Team <support@proxmox.com>  Fri, 13 Apr 2018 11:15:45 +0200
+
+corosync-pve (2.4.2-2~pve4+1) unstable; urgency=medium
+
+  * also restart when switching from old to new upgrade behaviour
+
+ -- Proxmox Support Team <support@proxmox.com>  Wed, 8 Mar 2017 11:25:48 +0100
+
+corosync-pve (2.4.2-2~pve4) unstable; urgency=medium
+
+  * restart corosync.service on upgrades instead of stop-wait-start
+
+ -- Proxmox Support Team <support@proxmox.com>  Tue, 7 Mar 2017 15:22:47 +0100
+
+corosync-pve (2.4.2-1) unstable; urgency=medium
+
+  * update to corosync 2.4.2
+
+ -- Proxmox Support Team <support@proxmox.com>  Wed, 08 Feb 2017 14:08:49 +0100
+
+corosync-pve (2.4.0-1) unstable; urgency=medium
+
+  * update to v2.4.0
+
+ -- Proxmox Support Team <support@proxmox.com>  Sat, 16 Jul 2016 10:27:49 +0200
+
 corosync-pve (2.3.5-2) unstable; urgency=medium
 
   * update to latest versions from branch needle