From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/johntheripper/
Date: Sat, 15 Feb 2025 09:29:28 +0000 (UTC) [thread overview]
Message-ID: <1739611601.6dd29a88ae4851c8725da25cdb09f16b2772f9ac.ulm@gentoo> (raw)
commit: 6dd29a88ae4851c8725da25cdb09f16b2772f9ac
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Fri Feb 14 16:16:32 2025 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sat Feb 15 09:26:41 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6dd29a88
app-crypt/johntheripper: Fix incorrect REPLACING_VERSIONS usage
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
app-crypt/johntheripper/johntheripper-1.9.0.ebuild | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/app-crypt/johntheripper/johntheripper-1.9.0.ebuild b/app-crypt/johntheripper/johntheripper-1.9.0.ebuild
index 158f6df061c2..bca43f8eb9f7 100644
--- a/app-crypt/johntheripper/johntheripper-1.9.0.ebuild
+++ b/app-crypt/johntheripper/johntheripper-1.9.0.ebuild
@@ -1,9 +1,9 @@
-# Copyright 1999-2024 Gentoo Authors
+# Copyright 1999-2025 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
-inherit flag-o-matic toolchain-funcs
+inherit eapi9-ver flag-o-matic toolchain-funcs
MY_PN="john"
MY_P="${MY_PN}-${PV}"
@@ -131,7 +131,7 @@ src_install() {
}
pkg_postinst() {
- if [ -n "${REPLACING_VERSIONS}" ] && [ "${REPLACING_VERSIONS}" != "1.8.0" ]; then
+ if ver_replacing -lt 1.8.0; then
ewarn "This package no longer includes jumbo. If you want jumbo please install app-crypt/johntheripper-jumbo instead."
fi
}
next reply other threads:[~2025-02-15 9:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 9:29 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-24 5:00 [gentoo-commits] repo/gentoo:master commit in: app-crypt/johntheripper/ Sam James
2024-12-01 22:36 Jakov Smolić
2024-12-01 19:06 Arthur Zamarin
2024-12-01 19:03 Arthur Zamarin
2023-08-21 20:56 Rick Farina
2023-08-21 20:56 Rick Farina
2023-08-21 20:56 Rick Farina
2023-08-19 22:40 Rick Farina
2023-08-19 22:40 Rick Farina
2022-05-14 21:30 David Seifert
2022-01-05 10:01 David Seifert
2021-11-19 11:33 Sam James
2021-04-03 23:07 Sam James
2021-01-07 8:20 Fabian Groffen
2019-06-05 21:19 Andreas Sturmlechner
2019-05-15 15:17 Mikle Kolyada
2019-05-15 15:17 Mikle Kolyada
2019-05-13 17:02 Mikle Kolyada
2019-05-12 22:03 Sergei Trofimovich
2019-05-12 21:57 Sergei Trofimovich
2019-05-08 14:38 Tobias Klausmann
2019-05-08 6:25 Sergei Trofimovich
2019-05-07 6:26 Sergei Trofimovich
2018-12-18 21:40 Rick Farina
2018-12-18 21:40 Rick Farina
2018-12-13 15:34 Rick Farina
2018-11-27 17:52 Rick Farina
2018-11-02 20:24 Craig Andrews
2018-11-02 20:24 Craig Andrews
2016-06-03 11:03 Anthony G. Basile
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1739611601.6dd29a88ae4851c8725da25cdb09f16b2772f9ac.ulm@gentoo \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox