]>
Commit | Line | Data |
---|---|---|
470255f1 TL |
1 | corosync (3.1.7-pve3) bookworm; urgency=medium |
2 | ||
3 | * d/control: do not depend on obsolete lsb-base | |
4 | ||
5 | -- Proxmox Support Team <support@proxmox.com> Sun, 07 May 2023 14:43:01 +0200 | |
6 | ||
37cb1baa TL |
7 | corosync (3.1.7-pve2) bookworm; urgency=medium |
8 | ||
9 | * re-build for Debian 12 Bullseye / Proxmox VE 8 | |
10 | ||
11 | -- Proxmox Support Team <support@proxmox.com> Tue, 02 May 2023 18:52:58 +0200 | |
12 | ||
e6b04e72 FG |
13 | corosync (3.1.7-pve1) bullseye; urgency=medium |
14 | ||
15 | * update to Corosync 3.1.7 | |
16 | ||
17 | -- Proxmox Support Team <support@proxmox.com> Wed, 16 Nov 2022 09:10:33 +0100 | |
18 | ||
11bf5fcf FG |
19 | corosync (3.1.5-pve2) bullseye; urgency=medium |
20 | ||
21 | * cherry-pick fix for high retransmit load | |
22 | ||
23 | * cherry-pick fix for CPG corruption during membership change bug | |
24 | ||
25 | -- Proxmox Support Team <support@proxmox.com> Tue, 9 Nov 2021 11:50:52 +0100 | |
26 | ||
5e4f0357 TL |
27 | corosync (3.1.5-pve1) bullseye; urgency=medium |
28 | ||
29 | * update to v3.1.5 upstream release | |
30 | ||
31 | -- Proxmox Support Team <support@proxmox.com> Fri, 10 Sep 2021 13:11:32 +0200 | |
32 | ||
7f65236f TL |
33 | corosync (3.1.2-pve2) bullseye; urgency=medium |
34 | ||
35 | * re-build for Debian 11 Bullseye / Proxmox VE 7 | |
36 | ||
37 | * package corosync-vqsim | |
38 | ||
39 | * enable kronosnet's nozzle support | |
40 | ||
41 | -- Proxmox Support Team <support@proxmox.com> Sun, 16 May 2021 17:53:59 +0200 | |
42 | ||
e72ec945 FG |
43 | corosync (3.1.2-pve1) pve; urgency=medium |
44 | ||
45 | * update to Corosync 3.1.2 | |
46 | ||
47 | -- Proxmox Support Team <support@proxmox.com> Tue, 6 Apr 2021 14:25:27 +0200 | |
48 | ||
7d368b0c TL |
49 | corosync (3.1.0-pve1) pve; urgency=medium |
50 | ||
51 | * update to Corosync 3.1.0 | |
52 | + Configuration system is rewritten and reload became atomic operation. | |
53 | + Quorum service got improved API with ability to register new totem | |
54 | members change callback. | |
55 | + Default token timeout was changed from 1 seconds to 3 seconds. | |
56 | + Support for changing crypto configuration during runtime. | |
57 | ||
58 | -- Proxmox Support Team <support@proxmox.com> Thu, 28 Jan 2021 11:39:25 +0100 | |
59 | ||
9e726e8b TL |
60 | corosync (3.0.4-pve1) pve; urgency=medium |
61 | ||
62 | * update to Corosync 3.0.4 | |
63 | ||
64 | -- Proxmox Support Team <support@proxmox.com> Thu, 25 Jun 2020 17:02:11 +0200 | |
65 | ||
b895e775 TL |
66 | corosync (3.0.3-pve1) pve; urgency=medium |
67 | ||
68 | * update to Corosync 3.0.3 | |
69 | ||
70 | -- Proxmox Support Team <support@proxmox.com> Mon, 25 Nov 2019 15:38:52 +0100 | |
71 | ||
8a4032e5 TL |
72 | corosync (3.0.2-pve4) pve; urgency=medium |
73 | ||
74 | * backport a fix ensuring that the messages during recovery (retransmission) | |
75 | do not exceed the maximum possible KNET package size. | |
76 | ||
77 | -- Proxmox Support Team <support@proxmox.com> Thu, 10 Oct 2019 18:16:02 +0200 | |
78 | ||
6282e6ca TL |
79 | corosync (3.0.2-pve3) pve; urgency=medium |
80 | ||
81 | * totemknet: Disable forwarding on shutdown to make knet flush all messages | |
82 | (especially LEAVE one) | |
83 | ||
84 | * totemknet: Add locking for log call to ensure no log message is lost from | |
85 | different threads | |
86 | ||
87 | * totempg: Check sanity (length) of received message | |
88 | ||
89 | -- Proxmox Support Team <support@proxmox.com> Thu, 03 Oct 2019 16:13:54 +0200 | |
90 | ||
fa960e0c TL |
91 | corosync (3.0.2-pve2) pve; urgency=medium |
92 | ||
93 | * cherry pick totem config patches to improve compatibillity with setups | |
94 | without a (currently) configured link0 | |
95 | ||
96 | -- Proxmox Support Team <support@proxmox.com> Fri, 21 Jun 2019 14:26:28 +0200 | |
97 | ||
4e762dd4 FG |
98 | corosync (3.0.2-pve1) pve; urgency=medium |
99 | ||
100 | * update to Corosync 3.0.2 | |
101 | ||
102 | -- Proxmox Support Team <support@proxmox.com> Wed, 19 Jun 2019 13:47:17 +0200 | |
103 | ||
06d5370e FG |
104 | corosync (3.0.1-pve1) pve; urgency=medium |
105 | ||
106 | * update to Corosync 3.0.1-2 | |
107 | ||
108 | * cherry-pick crypto changes for upgrade compatibility | |
109 | ||
110 | * cherry-pick CPG callback joinlist merging (PR 468) | |
111 | ||
112 | * drop transitional corosync-pve/libcorosync4-pve packages | |
113 | ||
114 | * corosync-qdevice/corosync-qnetd are now shipped separately | |
115 | ||
116 | * drop discontinued libtotem-pq library packages | |
117 | ||
118 | -- Proxmox Support Team <support@proxmox.com> Wed, 22 May 2019 12:40:27 +0200 | |
119 | ||
459f4daa FG |
120 | corosync (2.4.4-pve1) unstable; urgency=medium |
121 | ||
122 | * update to corosync 2.4.4 | |
123 | ||
124 | -- Proxmox Support Team <support@proxmox.com> Wed, 24 Oct 2018 12:48:36 +0200 | |
125 | ||
013929b6 TL |
126 | corosync (2.4.2-pve5) unstable; urgency=medium |
127 | ||
128 | * cpg: Inform clients about left nodes during pause | |
129 | ||
130 | -- Proxmox Support Team <support@proxmox.com> Wed, 25 Apr 2018 10:26:48 +0200 | |
131 | ||
c01206f1 FG |
132 | corosync (2.4.2-pve4) unstable; urgency=medium |
133 | ||
134 | * fix CVE-2018-1084 | |
135 | ||
136 | -- Proxmox Support Team <support@proxmox.com> Fri, 13 Apr 2018 10:29:34 +0200 | |
137 | ||
e4647070 FG |
138 | corosync (2.4.2-pve3) unstable; urgency=medium |
139 | ||
140 | * don't install corosync-qdevice init script | |
141 | ||
142 | -- Proxmox Support Team <support@proxmox.com> Thu, 8 Jun 2017 14:13:22 +0200 | |
143 | ||
3dbd0db6 FG |
144 | corosync (2.4.2-pve2) unstable; urgency=medium |
145 | ||
146 | * add libcorosync4-pve transitional package | |
147 | ||
148 | * only start corosync service if config exists | |
149 | ||
150 | -- Proxmox Support Team <support@proxmox.com> Mon, 13 Mar 2017 13:31:34 +0100 | |
151 | ||
bcf18111 FG |
152 | corosync (2.4.2-pve1) unstable; urgency=medium |
153 | ||
154 | * switch to Debian's corosync package as base | |
155 | ||
156 | -- Proxmox Support Team <support@proxmox.com> Wed, 8 Mar 2017 14:16:58 +0100 | |
157 | ||
6f6e3e0d FG |
158 | corosync-pve (2.4.2-2) unstable; urgency=medium |
159 | ||
160 | * rebuild for PVE 5.0 / Debian Stretch | |
161 | ||
162 | -- Proxmox Support Team <support@proxmox.com> Mon, 6 Mar 2017 09:30:57 +0100 | |
163 | ||
63916ea1 TL |
164 | corosync-pve (2.4.2-1) unstable; urgency=medium |
165 | ||
166 | * update to corosync 2.4.2 | |
167 | ||
168 | -- Proxmox Support Team <support@proxmox.com> Wed, 08 Feb 2017 14:08:49 +0100 | |
169 | ||
275a2fbe DM |
170 | corosync-pve (2.4.0-1) unstable; urgency=medium |
171 | ||
172 | * update to v2.4.0 | |
173 | ||
174 | -- Proxmox Support Team <support@proxmox.com> Sat, 16 Jul 2016 10:27:49 +0200 | |
175 | ||
df03257c DM |
176 | corosync-pve (2.3.5-2) unstable; urgency=medium |
177 | ||
178 | * update to latest versions from branch needle | |
179 | (commit e2b6b25126a3e8f2caefcb8ccde67788c63fbeb5) | |
180 | ||
181 | * remove patch 0001-totem-swap-unicast-and-multicast-bind-order.patch (upstream) | |
182 | ||
183 | -- Proxmox Support Team <support@proxmox.com> Thu, 03 Dec 2015 14:49:43 +0100 | |
184 | ||
0a8764f4 DM |
185 | corosync-pve (2.3.5-1) unstable; urgency=medium |
186 | ||
187 | * update to v2.3.5 | |
188 | ||
189 | -- Proxmox Support Team <support@proxmox.com> Mon, 21 Sep 2015 12:02:49 +0200 | |
190 | ||
d05fb358 DM |
191 | corosync-pve (2.3.4-2) unstable; urgency=medium |
192 | ||
193 | * update to latest upstream (commit 82526d2fe9137e8b604f1bbae6d6e39ba41377f9) | |
194 | ||
195 | -- Proxmox Support Team <support@proxmox.com> Mon, 30 Mar 2015 19:10:35 +0200 | |
196 | ||
013101f0 DM |
197 | corosync-pve (2.3.4-1) unstable; urgency=medium |
198 | ||
199 | * update to 2.3.4 | |
200 | ||
201 | * recompile for Debian Jessie | |
202 | ||
203 | -- Proxmox Support Team <support@proxmox.com> Mon, 23 Feb 2015 08:20:52 +0100 | |
204 | ||
0320eacf DM |
205 | corosync-pve (1.4.7-1) unstable; urgency=low |
206 | ||
207 | * update to 1.4.7 | |
208 | ||
209 | -- Proxmox Support Team <support@proxmox.com> Tue, 22 Jul 2014 06:17:13 +0200 | |
210 | ||
728d91c3 DM |
211 | corosync-pve (1.4.6-1) unstable; urgency=low |
212 | ||
213 | * update to 1.4.6 | |
214 | ||
215 | -- Proxmox Support Team <support@proxmox.com> Fri, 09 May 2014 07:14:06 +0200 | |
216 | ||
1d458e36 DM |
217 | corosync-pve (1.4.5-1) unstable; urgency=low |
218 | ||
219 | * update to 1.4.5 | |
220 | ||
221 | -- Proxmox Support Team <support@proxmox.com> Fri, 15 Mar 2013 06:35:02 +0100 | |
222 | ||
af5eee0c DM |
223 | corosync-pve (1.4.4-3) unstable; urgency=low |
224 | ||
225 | * run at high priority using setpriority(-20) | |
226 | ||
227 | -- Proxmox Support Team <support@proxmox.com> Tue, 15 Jan 2013 12:54:02 +0100 | |
228 | ||
e0a6828c DM |
229 | corosync-pve (1.4.4-2) unstable; urgency=low |
230 | ||
231 | * disable SCHED_RR (RT_GROUP_SCHED was disabled in our kernel | |
232 | anyways). In newer kernels this is enabled, but causes corosync to | |
233 | crash. | |
234 | ||
235 | -- Proxmox Support Team <support@proxmox.com> Fri, 11 Jan 2013 15:39:40 +0100 | |
236 | ||
deb86d56 DM |
237 | corosync-pve (1.4.4-1) unstable; urgency=low |
238 | ||
239 | * update to 1.4.4 | |
240 | ||
241 | -- Proxmox Support Team <support@proxmox.com> Tue, 02 Oct 2012 09:41:59 +0200 | |
242 | ||
aeb347a9 DM |
243 | corosync-pve (1.4.3-1) unstable; urgency=low |
244 | ||
245 | * update to 1.4.3 | |
246 | ||
247 | -- Proxmox Support Team <support@proxmox.com> Thu, 12 Apr 2012 12:54:10 +0200 | |
248 | ||
930e051d DM |
249 | corosync-pve (1.4.1-1) unstable; urgency=low |
250 | ||
251 | * update to 1.4.1 | |
252 | ||
253 | -- Proxmox Support Team <support@proxmox.com> Tue, 26 Jul 2011 11:49:17 +0200 | |
254 | ||
255 | corosync-pve (1.4.0-1) unstable; urgency=low | |
256 | ||
257 | * update to 1.4.0 | |
258 | ||
259 | * remove fix-schedrr-warning.patch (alread in 1.4.0) | |
260 | ||
261 | -- Proxmox Support Team <support@proxmox.com> Tue, 19 Jul 2011 12:36:54 +0200 | |
262 | ||
263 | corosync-pve (1.3.1-1) unstable; urgency=low | |
264 | ||
265 | * update to latest stable | |
266 | ||
267 | -- Proxmox Support Team <support@proxmox.com> Thu, 23 Jun 2011 06:52:20 +0200 | |
268 | ||
269 | corosync-pve (1.3.0-1) unstable; urgency=low | |
270 | ||
271 | * update to latest stable | |
272 | ||
273 | -- Proxmox Support Team <support@proxmox.com> Thu, 02 Dec 2010 07:11:10 +0100 | |
274 | ||
275 | corosync-pve (1.2.8-1) unstable; urgency=low | |
276 | ||
277 | * update to latest stable | |
278 | ||
279 | -- Proxmox Support Team <support@proxmox.com> Wed, 06 Oct 2010 13:24:24 +0200 | |
280 | ||
281 | corosync-pve (1.2.0-1) unstable; urgency=low | |
282 | ||
283 | * add patches/cpg-join-fix.diff, see | |
284 | https://bugzilla.redhat.com/show_bug.cgi?id=568356 | |
285 | ||
286 | * update to latest stable | |
287 | ||
288 | * do not create/installe /etc/corosync/* - we use cman instead | |
289 | ||
290 | * delete init.d script - we use cman instead | |
291 | ||
292 | -- Proxmox Support Team <support@proxmox.com> Thu, 21 Jan 2010 13:50:43 +0100 | |
293 | ||
294 | corosync-pve (1.1.2-1) unstable; urgency=low | |
295 | ||
296 | * update to latest stable | |
297 | ||
298 | -- Proxmox Support Team <support@proxmox.com> Fri, 23 Oct 2009 11:41:04 +0200 | |
299 | ||
300 | corosync-pve (1.1.1-1) unstable; urgency=low | |
301 | ||
302 | * update to latest stable | |
303 | ||
304 | -- Proxmox Support Team <support@proxmox.com> Thu, 22 Oct 2009 12:46:53 +0200 | |
305 | ||
306 | corosync-pve (1.0-1) unstable; urgency=low | |
307 | ||
308 | * update to latest trunc | |
309 | ||
310 | * use quilt instead of dpatch | |
311 | ||
312 | * use /dev/urandom instead of /dev/random for key generation | |
313 | ||
314 | * new config file localtion: /etc/corosync/corosync.conf | |
315 | ||
316 | * new key location: /etc/corosync/authkey | |
317 | ||
318 | * new default configuration: secauth = on | |
319 | ||
320 | * auto-generate authkey in postinst script if it does not exist | |
321 | ||
322 | -- Proxmox Support Team <support@proxmox.com> Mon, 08 Jun 2009 03:28:34 -0400 | |
323 | ||
324 | corosync-pve (0.95-1) unstable; urgency=low | |
325 | ||
326 | * update to 0.95 | |
327 | ||
328 | -- Proxmox Support Team <support@proxmox.com> Wed, 01 Apr 2009 10:07:13 -0400 | |
329 | ||
330 | corosync-pve (0.94-1) unstable; urgency=low | |
331 | ||
332 | * Initial release. | |
333 | ||
334 | -- Proxmox Support Team <support@proxmox.com> Mon, 30 Mar 2009 06:55:24 -0400 | |
335 |