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