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