1 corosync-pve (2.3.5-2) unstable; urgency=medium
3 * update to latest versions from branch needle
4 (commit e2b6b25126a3e8f2caefcb8ccde67788c63fbeb5)
6 * remove patch 0001-totem-swap-unicast-and-multicast-bind-order.patch (upstream)
8 -- Proxmox Support Team <support@proxmox.com> Thu, 03 Dec 2015 14:49:43 +0100
10 corosync-pve (2.3.5-1) unstable; urgency=medium
14 -- Proxmox Support Team <support@proxmox.com> Mon, 21 Sep 2015 12:02:49 +0200
16 corosync-pve (2.3.4-2) unstable; urgency=medium
18 * update to latest upstream (commit 82526d2fe9137e8b604f1bbae6d6e39ba41377f9)
20 -- Proxmox Support Team <support@proxmox.com> Mon, 30 Mar 2015 19:10:35 +0200
22 corosync-pve (2.3.4-1) unstable; urgency=medium
26 * recompile for Debian Jessie
28 -- Proxmox Support Team <support@proxmox.com> Mon, 23 Feb 2015 08:20:52 +0100
30 corosync-pve (1.4.7-1) unstable; urgency=low
34 -- Proxmox Support Team <support@proxmox.com> Tue, 22 Jul 2014 06:17:13 +0200
36 corosync-pve (1.4.6-1) unstable; urgency=low
40 -- Proxmox Support Team <support@proxmox.com> Fri, 09 May 2014 07:14:06 +0200
42 corosync-pve (1.4.5-1) unstable; urgency=low
46 -- Proxmox Support Team <support@proxmox.com> Fri, 15 Mar 2013 06:35:02 +0100
48 corosync-pve (1.4.4-3) unstable; urgency=low
50 * run at high priority using setpriority(-20)
52 -- Proxmox Support Team <support@proxmox.com> Tue, 15 Jan 2013 12:54:02 +0100
54 corosync-pve (1.4.4-2) unstable; urgency=low
56 * disable SCHED_RR (RT_GROUP_SCHED was disabled in our kernel
57 anyways). In newer kernels this is enabled, but causes corosync to
60 -- Proxmox Support Team <support@proxmox.com> Fri, 11 Jan 2013 15:39:40 +0100
62 corosync-pve (1.4.4-1) unstable; urgency=low
66 -- Proxmox Support Team <support@proxmox.com> Tue, 02 Oct 2012 09:41:59 +0200
68 corosync-pve (1.4.3-1) unstable; urgency=low
72 -- Proxmox Support Team <support@proxmox.com> Thu, 12 Apr 2012 12:54:10 +0200
74 corosync-pve (1.4.1-1) unstable; urgency=low
78 -- Proxmox Support Team <support@proxmox.com> Tue, 26 Jul 2011 11:49:17 +0200
80 corosync-pve (1.4.0-1) unstable; urgency=low
84 * remove fix-schedrr-warning.patch (alread in 1.4.0)
86 -- Proxmox Support Team <support@proxmox.com> Tue, 19 Jul 2011 12:36:54 +0200
88 corosync-pve (1.3.1-1) unstable; urgency=low
90 * update to latest stable
92 -- Proxmox Support Team <support@proxmox.com> Thu, 23 Jun 2011 06:52:20 +0200
94 corosync-pve (1.3.0-1) unstable; urgency=low
96 * update to latest stable
98 -- Proxmox Support Team <support@proxmox.com> Thu, 02 Dec 2010 07:11:10 +0100
100 corosync-pve (1.2.8-1) unstable; urgency=low
102 * update to latest stable
104 -- Proxmox Support Team <support@proxmox.com> Wed, 06 Oct 2010 13:24:24 +0200
106 corosync-pve (1.2.0-1) unstable; urgency=low
108 * add patches/cpg-join-fix.diff, see
109 https://bugzilla.redhat.com/show_bug.cgi?id=568356
111 * update to latest stable
113 * do not create/installe /etc/corosync/* - we use cman instead
115 * delete init.d script - we use cman instead
117 -- Proxmox Support Team <support@proxmox.com> Thu, 21 Jan 2010 13:50:43 +0100
119 corosync-pve (1.1.2-1) unstable; urgency=low
121 * update to latest stable
123 -- Proxmox Support Team <support@proxmox.com> Fri, 23 Oct 2009 11:41:04 +0200
125 corosync-pve (1.1.1-1) unstable; urgency=low
127 * update to latest stable
129 -- Proxmox Support Team <support@proxmox.com> Thu, 22 Oct 2009 12:46:53 +0200
131 corosync-pve (1.0-1) unstable; urgency=low
133 * update to latest trunc
135 * use quilt instead of dpatch
137 * use /dev/urandom instead of /dev/random for key generation
139 * new config file localtion: /etc/corosync/corosync.conf
141 * new key location: /etc/corosync/authkey
143 * new default configuration: secauth = on
145 * auto-generate authkey in postinst script if it does not exist
147 -- Proxmox Support Team <support@proxmox.com> Mon, 08 Jun 2009 03:28:34 -0400
149 corosync-pve (0.95-1) unstable; urgency=low
153 -- Proxmox Support Team <support@proxmox.com> Wed, 01 Apr 2009 10:07:13 -0400
155 corosync-pve (0.94-1) unstable; urgency=low
159 -- Proxmox Support Team <support@proxmox.com> Mon, 30 Mar 2009 06:55:24 -0400