# Ultrabug <ultrabug@gentoo.org> (16 May 2012) # Masked for testing >=sys-cluster/corosync-2.0.0 This package .mask entry has been in place for a long time. Can you remove it and either let the affected versions go to ~arch or remove them? Thanks, William
+*corosync-2.3.3 (12 Aug 2014) +*corosync-1.4.7 (12 Aug 2014) + + 12 Aug 2014; Ultrabug <ultrabug@gentoo.org> -corosync-1.3.3-r1.ebuild, + -corosync-1.4.3-r1.ebuild, -corosync-1.4.4.ebuild, +corosync-1.4.7.ebuild, + -corosync-2.3.1.ebuild, -corosync-2.3.2.ebuild, +corosync-2.3.3.ebuild: + version bump, drop old ebuilds + Ok, first of all I've bumped and cleaned up corosync a bit. Now I'd like to have the ACK of one of my fellow cluster herd member before dropping the mask as migrating from corosync 1.4 to corosync 2.0 was known to cause some problems at the time of the mask. As a side note, I've bumped sys-cluster/libqb to version 0.17.0 fyi.
bumped today : + corosync-2.3.4 + libqb-0.17.1 I will drop the mask this week. Be advised that I do NOT intend to maintain corosync 1.3.x versions so I will drop them soon after.
Mask dropped, thx mate + 02 Dec 2014; Ultrabug <ultrabug@gentoo.org> package.mask: + drop sys-cluster/corosync-2.x mask wrt #518880 +
