]> git.proxmox.com Git - corosync-pve.git/blob - debian/changelog
update to 1.4.5
[corosync-pve.git] / debian / changelog
1 corosync-pve (1.4.5-1) unstable; urgency=low
2
3 * update to 1.4.5
4
5 -- Proxmox Support Team <support@proxmox.com> Fri, 15 Mar 2013 06:35:02 +0100
6
7 corosync-pve (1.4.4-3) unstable; urgency=low
8
9 * run at high priority using setpriority(-20)
10
11 -- Proxmox Support Team <support@proxmox.com> Tue, 15 Jan 2013 12:54:02 +0100
12
13 corosync-pve (1.4.4-2) unstable; urgency=low
14
15 * disable SCHED_RR (RT_GROUP_SCHED was disabled in our kernel
16 anyways). In newer kernels this is enabled, but causes corosync to
17 crash.
18
19 -- Proxmox Support Team <support@proxmox.com> Fri, 11 Jan 2013 15:39:40 +0100
20
21 corosync-pve (1.4.4-1) unstable; urgency=low
22
23 * update to 1.4.4
24
25 -- Proxmox Support Team <support@proxmox.com> Tue, 02 Oct 2012 09:41:59 +0200
26
27 corosync-pve (1.4.3-1) unstable; urgency=low
28
29 * update to 1.4.3
30
31 -- Proxmox Support Team <support@proxmox.com> Thu, 12 Apr 2012 12:54:10 +0200
32
33 corosync-pve (1.4.1-1) unstable; urgency=low
34
35 * update to 1.4.1
36
37 -- Proxmox Support Team <support@proxmox.com> Tue, 26 Jul 2011 11:49:17 +0200
38
39 corosync-pve (1.4.0-1) unstable; urgency=low
40
41 * update to 1.4.0
42
43 * remove fix-schedrr-warning.patch (alread in 1.4.0)
44
45 -- Proxmox Support Team <support@proxmox.com> Tue, 19 Jul 2011 12:36:54 +0200
46
47 corosync-pve (1.3.1-1) unstable; urgency=low
48
49 * update to latest stable
50
51 -- Proxmox Support Team <support@proxmox.com> Thu, 23 Jun 2011 06:52:20 +0200
52
53 corosync-pve (1.3.0-1) unstable; urgency=low
54
55 * update to latest stable
56
57 -- Proxmox Support Team <support@proxmox.com> Thu, 02 Dec 2010 07:11:10 +0100
58
59 corosync-pve (1.2.8-1) unstable; urgency=low
60
61 * update to latest stable
62
63 -- Proxmox Support Team <support@proxmox.com> Wed, 06 Oct 2010 13:24:24 +0200
64
65 corosync-pve (1.2.0-1) unstable; urgency=low
66
67 * add patches/cpg-join-fix.diff, see
68 https://bugzilla.redhat.com/show_bug.cgi?id=568356
69
70 * update to latest stable
71
72 * do not create/installe /etc/corosync/* - we use cman instead
73
74 * delete init.d script - we use cman instead
75
76 -- Proxmox Support Team <support@proxmox.com> Thu, 21 Jan 2010 13:50:43 +0100
77
78 corosync-pve (1.1.2-1) unstable; urgency=low
79
80 * update to latest stable
81
82 -- Proxmox Support Team <support@proxmox.com> Fri, 23 Oct 2009 11:41:04 +0200
83
84 corosync-pve (1.1.1-1) unstable; urgency=low
85
86 * update to latest stable
87
88 -- Proxmox Support Team <support@proxmox.com> Thu, 22 Oct 2009 12:46:53 +0200
89
90 corosync-pve (1.0-1) unstable; urgency=low
91
92 * update to latest trunc
93
94 * use quilt instead of dpatch
95
96 * use /dev/urandom instead of /dev/random for key generation
97
98 * new config file localtion: /etc/corosync/corosync.conf
99
100 * new key location: /etc/corosync/authkey
101
102 * new default configuration: secauth = on
103
104 * auto-generate authkey in postinst script if it does not exist
105
106 -- Proxmox Support Team <support@proxmox.com> Mon, 08 Jun 2009 03:28:34 -0400
107
108 corosync-pve (0.95-1) unstable; urgency=low
109
110 * update to 0.95
111
112 -- Proxmox Support Team <support@proxmox.com> Wed, 01 Apr 2009 10:07:13 -0400
113
114 corosync-pve (0.94-1) unstable; urgency=low
115
116 * Initial release.
117
118 -- Proxmox Support Team <support@proxmox.com> Mon, 30 Mar 2009 06:55:24 -0400
119