]>
Commit | Line | Data |
---|---|---|
013929b6 TL |
1 | corosync (2.4.2-pve5) unstable; urgency=medium |
2 | ||
3 | * cpg: Inform clients about left nodes during pause | |
4 | ||
5 | -- Proxmox Support Team <support@proxmox.com> Wed, 25 Apr 2018 10:26:48 +0200 | |
6 | ||
c01206f1 FG |
7 | corosync (2.4.2-pve4) unstable; urgency=medium |
8 | ||
9 | * fix CVE-2018-1084 | |
10 | ||
11 | -- Proxmox Support Team <support@proxmox.com> Fri, 13 Apr 2018 10:29:34 +0200 | |
12 | ||
e4647070 FG |
13 | corosync (2.4.2-pve3) unstable; urgency=medium |
14 | ||
15 | * don't install corosync-qdevice init script | |
16 | ||
17 | -- Proxmox Support Team <support@proxmox.com> Thu, 8 Jun 2017 14:13:22 +0200 | |
18 | ||
3dbd0db6 FG |
19 | corosync (2.4.2-pve2) unstable; urgency=medium |
20 | ||
21 | * add libcorosync4-pve transitional package | |
22 | ||
23 | * only start corosync service if config exists | |
24 | ||
25 | -- Proxmox Support Team <support@proxmox.com> Mon, 13 Mar 2017 13:31:34 +0100 | |
26 | ||
bcf18111 FG |
27 | corosync (2.4.2-pve1) unstable; urgency=medium |
28 | ||
29 | * switch to Debian's corosync package as base | |
30 | ||
31 | -- Proxmox Support Team <support@proxmox.com> Wed, 8 Mar 2017 14:16:58 +0100 | |
32 | ||
6f6e3e0d FG |
33 | corosync-pve (2.4.2-2) unstable; urgency=medium |
34 | ||
35 | * rebuild for PVE 5.0 / Debian Stretch | |
36 | ||
37 | -- Proxmox Support Team <support@proxmox.com> Mon, 6 Mar 2017 09:30:57 +0100 | |
38 | ||
63916ea1 TL |
39 | corosync-pve (2.4.2-1) unstable; urgency=medium |
40 | ||
41 | * update to corosync 2.4.2 | |
42 | ||
43 | -- Proxmox Support Team <support@proxmox.com> Wed, 08 Feb 2017 14:08:49 +0100 | |
44 | ||
275a2fbe DM |
45 | corosync-pve (2.4.0-1) unstable; urgency=medium |
46 | ||
47 | * update to v2.4.0 | |
48 | ||
49 | -- Proxmox Support Team <support@proxmox.com> Sat, 16 Jul 2016 10:27:49 +0200 | |
50 | ||
df03257c DM |
51 | corosync-pve (2.3.5-2) unstable; urgency=medium |
52 | ||
53 | * update to latest versions from branch needle | |
54 | (commit e2b6b25126a3e8f2caefcb8ccde67788c63fbeb5) | |
55 | ||
56 | * remove patch 0001-totem-swap-unicast-and-multicast-bind-order.patch (upstream) | |
57 | ||
58 | -- Proxmox Support Team <support@proxmox.com> Thu, 03 Dec 2015 14:49:43 +0100 | |
59 | ||
0a8764f4 DM |
60 | corosync-pve (2.3.5-1) unstable; urgency=medium |
61 | ||
62 | * update to v2.3.5 | |
63 | ||
64 | -- Proxmox Support Team <support@proxmox.com> Mon, 21 Sep 2015 12:02:49 +0200 | |
65 | ||
d05fb358 DM |
66 | corosync-pve (2.3.4-2) unstable; urgency=medium |
67 | ||
68 | * update to latest upstream (commit 82526d2fe9137e8b604f1bbae6d6e39ba41377f9) | |
69 | ||
70 | -- Proxmox Support Team <support@proxmox.com> Mon, 30 Mar 2015 19:10:35 +0200 | |
71 | ||
013101f0 DM |
72 | corosync-pve (2.3.4-1) unstable; urgency=medium |
73 | ||
74 | * update to 2.3.4 | |
75 | ||
76 | * recompile for Debian Jessie | |
77 | ||
78 | -- Proxmox Support Team <support@proxmox.com> Mon, 23 Feb 2015 08:20:52 +0100 | |
79 | ||
0320eacf DM |
80 | corosync-pve (1.4.7-1) unstable; urgency=low |
81 | ||
82 | * update to 1.4.7 | |
83 | ||
84 | -- Proxmox Support Team <support@proxmox.com> Tue, 22 Jul 2014 06:17:13 +0200 | |
85 | ||
728d91c3 DM |
86 | corosync-pve (1.4.6-1) unstable; urgency=low |
87 | ||
88 | * update to 1.4.6 | |
89 | ||
90 | -- Proxmox Support Team <support@proxmox.com> Fri, 09 May 2014 07:14:06 +0200 | |
91 | ||
1d458e36 DM |
92 | corosync-pve (1.4.5-1) unstable; urgency=low |
93 | ||
94 | * update to 1.4.5 | |
95 | ||
96 | -- Proxmox Support Team <support@proxmox.com> Fri, 15 Mar 2013 06:35:02 +0100 | |
97 | ||
af5eee0c DM |
98 | corosync-pve (1.4.4-3) unstable; urgency=low |
99 | ||
100 | * run at high priority using setpriority(-20) | |
101 | ||
102 | -- Proxmox Support Team <support@proxmox.com> Tue, 15 Jan 2013 12:54:02 +0100 | |
103 | ||
e0a6828c DM |
104 | corosync-pve (1.4.4-2) unstable; urgency=low |
105 | ||
106 | * disable SCHED_RR (RT_GROUP_SCHED was disabled in our kernel | |
107 | anyways). In newer kernels this is enabled, but causes corosync to | |
108 | crash. | |
109 | ||
110 | -- Proxmox Support Team <support@proxmox.com> Fri, 11 Jan 2013 15:39:40 +0100 | |
111 | ||
deb86d56 DM |
112 | corosync-pve (1.4.4-1) unstable; urgency=low |
113 | ||
114 | * update to 1.4.4 | |
115 | ||
116 | -- Proxmox Support Team <support@proxmox.com> Tue, 02 Oct 2012 09:41:59 +0200 | |
117 | ||
aeb347a9 DM |
118 | corosync-pve (1.4.3-1) unstable; urgency=low |
119 | ||
120 | * update to 1.4.3 | |
121 | ||
122 | -- Proxmox Support Team <support@proxmox.com> Thu, 12 Apr 2012 12:54:10 +0200 | |
123 | ||
930e051d DM |
124 | corosync-pve (1.4.1-1) unstable; urgency=low |
125 | ||
126 | * update to 1.4.1 | |
127 | ||
128 | -- Proxmox Support Team <support@proxmox.com> Tue, 26 Jul 2011 11:49:17 +0200 | |
129 | ||
130 | corosync-pve (1.4.0-1) unstable; urgency=low | |
131 | ||
132 | * update to 1.4.0 | |
133 | ||
134 | * remove fix-schedrr-warning.patch (alread in 1.4.0) | |
135 | ||
136 | -- Proxmox Support Team <support@proxmox.com> Tue, 19 Jul 2011 12:36:54 +0200 | |
137 | ||
138 | corosync-pve (1.3.1-1) unstable; urgency=low | |
139 | ||
140 | * update to latest stable | |
141 | ||
142 | -- Proxmox Support Team <support@proxmox.com> Thu, 23 Jun 2011 06:52:20 +0200 | |
143 | ||
144 | corosync-pve (1.3.0-1) unstable; urgency=low | |
145 | ||
146 | * update to latest stable | |
147 | ||
148 | -- Proxmox Support Team <support@proxmox.com> Thu, 02 Dec 2010 07:11:10 +0100 | |
149 | ||
150 | corosync-pve (1.2.8-1) unstable; urgency=low | |
151 | ||
152 | * update to latest stable | |
153 | ||
154 | -- Proxmox Support Team <support@proxmox.com> Wed, 06 Oct 2010 13:24:24 +0200 | |
155 | ||
156 | corosync-pve (1.2.0-1) unstable; urgency=low | |
157 | ||
158 | * add patches/cpg-join-fix.diff, see | |
159 | https://bugzilla.redhat.com/show_bug.cgi?id=568356 | |
160 | ||
161 | * update to latest stable | |
162 | ||
163 | * do not create/installe /etc/corosync/* - we use cman instead | |
164 | ||
165 | * delete init.d script - we use cman instead | |
166 | ||
167 | -- Proxmox Support Team <support@proxmox.com> Thu, 21 Jan 2010 13:50:43 +0100 | |
168 | ||
169 | corosync-pve (1.1.2-1) unstable; urgency=low | |
170 | ||
171 | * update to latest stable | |
172 | ||
173 | -- Proxmox Support Team <support@proxmox.com> Fri, 23 Oct 2009 11:41:04 +0200 | |
174 | ||
175 | corosync-pve (1.1.1-1) unstable; urgency=low | |
176 | ||
177 | * update to latest stable | |
178 | ||
179 | -- Proxmox Support Team <support@proxmox.com> Thu, 22 Oct 2009 12:46:53 +0200 | |
180 | ||
181 | corosync-pve (1.0-1) unstable; urgency=low | |
182 | ||
183 | * update to latest trunc | |
184 | ||
185 | * use quilt instead of dpatch | |
186 | ||
187 | * use /dev/urandom instead of /dev/random for key generation | |
188 | ||
189 | * new config file localtion: /etc/corosync/corosync.conf | |
190 | ||
191 | * new key location: /etc/corosync/authkey | |
192 | ||
193 | * new default configuration: secauth = on | |
194 | ||
195 | * auto-generate authkey in postinst script if it does not exist | |
196 | ||
197 | -- Proxmox Support Team <support@proxmox.com> Mon, 08 Jun 2009 03:28:34 -0400 | |
198 | ||
199 | corosync-pve (0.95-1) unstable; urgency=low | |
200 | ||
201 | * update to 0.95 | |
202 | ||
203 | -- Proxmox Support Team <support@proxmox.com> Wed, 01 Apr 2009 10:07:13 -0400 | |
204 | ||
205 | corosync-pve (0.94-1) unstable; urgency=low | |
206 | ||
207 | * Initial release. | |
208 | ||
209 | -- Proxmox Support Team <support@proxmox.com> Mon, 30 Mar 2009 06:55:24 -0400 | |
210 |