]>
Commit | Line | Data |
---|---|---|
1 | corosync (3.0.3-pve1) pve; urgency=medium | |
2 | ||
3 | * update to Corosync 3.0.3 | |
4 | ||
5 | -- Proxmox Support Team <support@proxmox.com> Mon, 25 Nov 2019 15:38:52 +0100 | |
6 | ||
7 | corosync (3.0.2-pve4) pve; urgency=medium | |
8 | ||
9 | * backport a fix ensuring that the messages during recovery (retransmission) | |
10 | do not exceed the maximum possible KNET package size. | |
11 | ||
12 | -- Proxmox Support Team <support@proxmox.com> Thu, 10 Oct 2019 18:16:02 +0200 | |
13 | ||
14 | corosync (3.0.2-pve3) pve; urgency=medium | |
15 | ||
16 | * totemknet: Disable forwarding on shutdown to make knet flush all messages | |
17 | (especially LEAVE one) | |
18 | ||
19 | * totemknet: Add locking for log call to ensure no log message is lost from | |
20 | different threads | |
21 | ||
22 | * totempg: Check sanity (length) of received message | |
23 | ||
24 | -- Proxmox Support Team <support@proxmox.com> Thu, 03 Oct 2019 16:13:54 +0200 | |
25 | ||
26 | corosync (3.0.2-pve2) pve; urgency=medium | |
27 | ||
28 | * cherry pick totem config patches to improve compatibillity with setups | |
29 | without a (currently) configured link0 | |
30 | ||
31 | -- Proxmox Support Team <support@proxmox.com> Fri, 21 Jun 2019 14:26:28 +0200 | |
32 | ||
33 | corosync (3.0.2-pve1) pve; urgency=medium | |
34 | ||
35 | * update to Corosync 3.0.2 | |
36 | ||
37 | -- Proxmox Support Team <support@proxmox.com> Wed, 19 Jun 2019 13:47:17 +0200 | |
38 | ||
39 | corosync (3.0.1-pve1) pve; urgency=medium | |
40 | ||
41 | * update to Corosync 3.0.1-2 | |
42 | ||
43 | * cherry-pick crypto changes for upgrade compatibility | |
44 | ||
45 | * cherry-pick CPG callback joinlist merging (PR 468) | |
46 | ||
47 | * drop transitional corosync-pve/libcorosync4-pve packages | |
48 | ||
49 | * corosync-qdevice/corosync-qnetd are now shipped separately | |
50 | ||
51 | * drop discontinued libtotem-pq library packages | |
52 | ||
53 | -- Proxmox Support Team <support@proxmox.com> Wed, 22 May 2019 12:40:27 +0200 | |
54 | ||
55 | corosync (2.4.4-pve1) unstable; urgency=medium | |
56 | ||
57 | * update to corosync 2.4.4 | |
58 | ||
59 | -- Proxmox Support Team <support@proxmox.com> Wed, 24 Oct 2018 12:48:36 +0200 | |
60 | ||
61 | corosync (2.4.2-pve5) unstable; urgency=medium | |
62 | ||
63 | * cpg: Inform clients about left nodes during pause | |
64 | ||
65 | -- Proxmox Support Team <support@proxmox.com> Wed, 25 Apr 2018 10:26:48 +0200 | |
66 | ||
67 | corosync (2.4.2-pve4) unstable; urgency=medium | |
68 | ||
69 | * fix CVE-2018-1084 | |
70 | ||
71 | -- Proxmox Support Team <support@proxmox.com> Fri, 13 Apr 2018 10:29:34 +0200 | |
72 | ||
73 | corosync (2.4.2-pve3) unstable; urgency=medium | |
74 | ||
75 | * don't install corosync-qdevice init script | |
76 | ||
77 | -- Proxmox Support Team <support@proxmox.com> Thu, 8 Jun 2017 14:13:22 +0200 | |
78 | ||
79 | corosync (2.4.2-pve2) unstable; urgency=medium | |
80 | ||
81 | * add libcorosync4-pve transitional package | |
82 | ||
83 | * only start corosync service if config exists | |
84 | ||
85 | -- Proxmox Support Team <support@proxmox.com> Mon, 13 Mar 2017 13:31:34 +0100 | |
86 | ||
87 | corosync (2.4.2-pve1) unstable; urgency=medium | |
88 | ||
89 | * switch to Debian's corosync package as base | |
90 | ||
91 | -- Proxmox Support Team <support@proxmox.com> Wed, 8 Mar 2017 14:16:58 +0100 | |
92 | ||
93 | corosync-pve (2.4.2-2) unstable; urgency=medium | |
94 | ||
95 | * rebuild for PVE 5.0 / Debian Stretch | |
96 | ||
97 | -- Proxmox Support Team <support@proxmox.com> Mon, 6 Mar 2017 09:30:57 +0100 | |
98 | ||
99 | corosync-pve (2.4.2-1) unstable; urgency=medium | |
100 | ||
101 | * update to corosync 2.4.2 | |
102 | ||
103 | -- Proxmox Support Team <support@proxmox.com> Wed, 08 Feb 2017 14:08:49 +0100 | |
104 | ||
105 | corosync-pve (2.4.0-1) unstable; urgency=medium | |
106 | ||
107 | * update to v2.4.0 | |
108 | ||
109 | -- Proxmox Support Team <support@proxmox.com> Sat, 16 Jul 2016 10:27:49 +0200 | |
110 | ||
111 | corosync-pve (2.3.5-2) unstable; urgency=medium | |
112 | ||
113 | * update to latest versions from branch needle | |
114 | (commit e2b6b25126a3e8f2caefcb8ccde67788c63fbeb5) | |
115 | ||
116 | * remove patch 0001-totem-swap-unicast-and-multicast-bind-order.patch (upstream) | |
117 | ||
118 | -- Proxmox Support Team <support@proxmox.com> Thu, 03 Dec 2015 14:49:43 +0100 | |
119 | ||
120 | corosync-pve (2.3.5-1) unstable; urgency=medium | |
121 | ||
122 | * update to v2.3.5 | |
123 | ||
124 | -- Proxmox Support Team <support@proxmox.com> Mon, 21 Sep 2015 12:02:49 +0200 | |
125 | ||
126 | corosync-pve (2.3.4-2) unstable; urgency=medium | |
127 | ||
128 | * update to latest upstream (commit 82526d2fe9137e8b604f1bbae6d6e39ba41377f9) | |
129 | ||
130 | -- Proxmox Support Team <support@proxmox.com> Mon, 30 Mar 2015 19:10:35 +0200 | |
131 | ||
132 | corosync-pve (2.3.4-1) unstable; urgency=medium | |
133 | ||
134 | * update to 2.3.4 | |
135 | ||
136 | * recompile for Debian Jessie | |
137 | ||
138 | -- Proxmox Support Team <support@proxmox.com> Mon, 23 Feb 2015 08:20:52 +0100 | |
139 | ||
140 | corosync-pve (1.4.7-1) unstable; urgency=low | |
141 | ||
142 | * update to 1.4.7 | |
143 | ||
144 | -- Proxmox Support Team <support@proxmox.com> Tue, 22 Jul 2014 06:17:13 +0200 | |
145 | ||
146 | corosync-pve (1.4.6-1) unstable; urgency=low | |
147 | ||
148 | * update to 1.4.6 | |
149 | ||
150 | -- Proxmox Support Team <support@proxmox.com> Fri, 09 May 2014 07:14:06 +0200 | |
151 | ||
152 | corosync-pve (1.4.5-1) unstable; urgency=low | |
153 | ||
154 | * update to 1.4.5 | |
155 | ||
156 | -- Proxmox Support Team <support@proxmox.com> Fri, 15 Mar 2013 06:35:02 +0100 | |
157 | ||
158 | corosync-pve (1.4.4-3) unstable; urgency=low | |
159 | ||
160 | * run at high priority using setpriority(-20) | |
161 | ||
162 | -- Proxmox Support Team <support@proxmox.com> Tue, 15 Jan 2013 12:54:02 +0100 | |
163 | ||
164 | corosync-pve (1.4.4-2) unstable; urgency=low | |
165 | ||
166 | * disable SCHED_RR (RT_GROUP_SCHED was disabled in our kernel | |
167 | anyways). In newer kernels this is enabled, but causes corosync to | |
168 | crash. | |
169 | ||
170 | -- Proxmox Support Team <support@proxmox.com> Fri, 11 Jan 2013 15:39:40 +0100 | |
171 | ||
172 | corosync-pve (1.4.4-1) unstable; urgency=low | |
173 | ||
174 | * update to 1.4.4 | |
175 | ||
176 | -- Proxmox Support Team <support@proxmox.com> Tue, 02 Oct 2012 09:41:59 +0200 | |
177 | ||
178 | corosync-pve (1.4.3-1) unstable; urgency=low | |
179 | ||
180 | * update to 1.4.3 | |
181 | ||
182 | -- Proxmox Support Team <support@proxmox.com> Thu, 12 Apr 2012 12:54:10 +0200 | |
183 | ||
184 | corosync-pve (1.4.1-1) unstable; urgency=low | |
185 | ||
186 | * update to 1.4.1 | |
187 | ||
188 | -- Proxmox Support Team <support@proxmox.com> Tue, 26 Jul 2011 11:49:17 +0200 | |
189 | ||
190 | corosync-pve (1.4.0-1) unstable; urgency=low | |
191 | ||
192 | * update to 1.4.0 | |
193 | ||
194 | * remove fix-schedrr-warning.patch (alread in 1.4.0) | |
195 | ||
196 | -- Proxmox Support Team <support@proxmox.com> Tue, 19 Jul 2011 12:36:54 +0200 | |
197 | ||
198 | corosync-pve (1.3.1-1) unstable; urgency=low | |
199 | ||
200 | * update to latest stable | |
201 | ||
202 | -- Proxmox Support Team <support@proxmox.com> Thu, 23 Jun 2011 06:52:20 +0200 | |
203 | ||
204 | corosync-pve (1.3.0-1) unstable; urgency=low | |
205 | ||
206 | * update to latest stable | |
207 | ||
208 | -- Proxmox Support Team <support@proxmox.com> Thu, 02 Dec 2010 07:11:10 +0100 | |
209 | ||
210 | corosync-pve (1.2.8-1) unstable; urgency=low | |
211 | ||
212 | * update to latest stable | |
213 | ||
214 | -- Proxmox Support Team <support@proxmox.com> Wed, 06 Oct 2010 13:24:24 +0200 | |
215 | ||
216 | corosync-pve (1.2.0-1) unstable; urgency=low | |
217 | ||
218 | * add patches/cpg-join-fix.diff, see | |
219 | https://bugzilla.redhat.com/show_bug.cgi?id=568356 | |
220 | ||
221 | * update to latest stable | |
222 | ||
223 | * do not create/installe /etc/corosync/* - we use cman instead | |
224 | ||
225 | * delete init.d script - we use cman instead | |
226 | ||
227 | -- Proxmox Support Team <support@proxmox.com> Thu, 21 Jan 2010 13:50:43 +0100 | |
228 | ||
229 | corosync-pve (1.1.2-1) unstable; urgency=low | |
230 | ||
231 | * update to latest stable | |
232 | ||
233 | -- Proxmox Support Team <support@proxmox.com> Fri, 23 Oct 2009 11:41:04 +0200 | |
234 | ||
235 | corosync-pve (1.1.1-1) unstable; urgency=low | |
236 | ||
237 | * update to latest stable | |
238 | ||
239 | -- Proxmox Support Team <support@proxmox.com> Thu, 22 Oct 2009 12:46:53 +0200 | |
240 | ||
241 | corosync-pve (1.0-1) unstable; urgency=low | |
242 | ||
243 | * update to latest trunc | |
244 | ||
245 | * use quilt instead of dpatch | |
246 | ||
247 | * use /dev/urandom instead of /dev/random for key generation | |
248 | ||
249 | * new config file localtion: /etc/corosync/corosync.conf | |
250 | ||
251 | * new key location: /etc/corosync/authkey | |
252 | ||
253 | * new default configuration: secauth = on | |
254 | ||
255 | * auto-generate authkey in postinst script if it does not exist | |
256 | ||
257 | -- Proxmox Support Team <support@proxmox.com> Mon, 08 Jun 2009 03:28:34 -0400 | |
258 | ||
259 | corosync-pve (0.95-1) unstable; urgency=low | |
260 | ||
261 | * update to 0.95 | |
262 | ||
263 | -- Proxmox Support Team <support@proxmox.com> Wed, 01 Apr 2009 10:07:13 -0400 | |
264 | ||
265 | corosync-pve (0.94-1) unstable; urgency=low | |
266 | ||
267 | * Initial release. | |
268 | ||
269 | -- Proxmox Support Team <support@proxmox.com> Mon, 30 Mar 2009 06:55:24 -0400 | |
270 |