commit: d2bd0ad359f6b217b1e8c1da7956eb54addfa355
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Tue May 5 21:46:02 2020 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Tue May 5 21:46:13 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d2bd0ad3
sys-cluster/corosync: drop invalid version check, bug #705276
'if [[ ${REPLACING_VERSIONS} < 2.0 ]]; then' uses lexicographical
version compare. That should be ver_cmp version compare or similar.
As it's a guard against non-existent version let's just drop the ewarn.
Closes: https://bugs.gentoo.org/705276
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
sys-cluster/corosync/corosync-2.3.5.ebuild | 11 -----------
sys-cluster/corosync/corosync-2.4.2.ebuild | 11 -----------
2 files changed, 22 deletions(-)
diff --git a/sys-cluster/corosync/corosync-2.3.5.ebuild
b/sys-cluster/corosync/corosync-2.3.5.ebuild
index 3e4bf6a0f56..3485dedb6bb 100644
--- a/sys-cluster/corosync/corosync-2.3.5.ebuild
+++ b/sys-cluster/corosync/corosync-2.3.5.ebuild
@@ -73,14 +73,3 @@ src_install() {
use static-libs || rm -rf "${D}"/usr/$(get_libdir)/*.{,l}a || die
}
-
-pkg_postinst() {
- if [[ ${REPLACING_VERSIONS} < 2.0 ]]; then
- ewarn "!! IMPORTANT !!"
- ewarn " "
- ewarn "Migrating from a previous version of corosync can be
dangerous !"
- ewarn " "
- ewarn "Make sure you backup your cluster configuration before
proceeding"
- ewarn " "
- fi
-}
diff --git a/sys-cluster/corosync/corosync-2.4.2.ebuild
b/sys-cluster/corosync/corosync-2.4.2.ebuild
index 49840bb0216..bdea670c8da 100644
--- a/sys-cluster/corosync/corosync-2.4.2.ebuild
+++ b/sys-cluster/corosync/corosync-2.4.2.ebuild
@@ -69,14 +69,3 @@ src_install() {
use static-libs || rm -rf "${D}"/usr/$(get_libdir)/*.{,l}a || die
}
-
-pkg_postinst() {
- if [[ ${REPLACING_VERSIONS} < 2.0 ]]; then
- ewarn "!! IMPORTANT !!"
- ewarn " "
- ewarn "Migrating from a previous version of corosync can be
dangerous !"
- ewarn " "
- ewarn "Make sure you backup your cluster configuration before
proceeding"
- ewarn " "
- fi
-}