From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/libscrypt/
Date: Wed, 27 Nov 2024 05:33:24 +0000 (UTC) [thread overview]
Message-ID: <1732685591.a82c9394d366236109e9e3761d4a3e057c8a9854.sam@gentoo> (raw)
commit: a82c9394d366236109e9e3761d4a3e057c8a9854
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 27 05:33:11 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Nov 27 05:33:11 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a82c9394
app-crypt/libscrypt: Stabilize 1.22-r3 ppc64, #945078
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-crypt/libscrypt/libscrypt-1.22-r3.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-crypt/libscrypt/libscrypt-1.22-r3.ebuild b/app-crypt/libscrypt/libscrypt-1.22-r3.ebuild
index 6d1f7224a014..28d0cedf8f8d 100644
--- a/app-crypt/libscrypt/libscrypt-1.22-r3.ebuild
+++ b/app-crypt/libscrypt/libscrypt-1.22-r3.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/technion/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="BSD-2"
SLOT="0"
-KEYWORDS="~amd64 arm ~arm64 ~hppa ~mips ppc ~ppc64 ~riscv ~sparc ~x86"
+KEYWORDS="~amd64 arm ~arm64 ~hppa ~mips ppc ppc64 ~riscv ~sparc ~x86"
PATCHES=(
"${FILESDIR}"/${PN}-1.22-no-clobber-fortify-source.patch
next reply other threads:[~2024-11-27 5:33 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 5:33 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-23 12:15 [gentoo-commits] repo/gentoo:master commit in: app-crypt/libscrypt/ Petr Vaněk
2024-11-27 7:12 Sam James
2024-11-27 7:12 Sam James
2024-11-27 5:33 Sam James
2024-11-27 5:33 Sam James
2024-11-27 5:33 Sam James
2024-11-27 5:33 Sam James
2024-11-25 21:01 Michał Górny
2024-11-23 20:15 Arthur Zamarin
2024-11-23 18:02 Arthur Zamarin
2024-03-23 8:37 Sam James
2024-01-07 0:20 Conrad Kostecki
2023-12-08 11:08 Sam James
2023-12-08 10:22 Arthur Zamarin
2023-12-08 9:02 Arthur Zamarin
2023-12-08 8:48 Arthur Zamarin
2023-12-08 8:48 Arthur Zamarin
2023-12-08 8:48 Arthur Zamarin
2023-12-08 8:45 Arthur Zamarin
2022-08-29 19:16 Jakov Smolić
2022-08-29 19:16 Jakov Smolić
2022-08-29 18:45 Agostino Sarubbo
2022-08-28 18:20 Arthur Zamarin
2022-08-28 18:03 Arthur Zamarin
2022-08-28 16:32 Arthur Zamarin
2022-05-14 12:13 Anthony G. Basile
2022-03-19 23:17 David Seifert
2022-03-16 15:18 Sam James
2021-07-23 11:05 Marek Szuba
2020-02-02 20:37 Anthony G. Basile
2019-05-10 4:16 Aaron Bauman
2017-11-14 19:56 Alon Bar-Lev
2017-11-04 22:05 Sergei Trofimovich
2017-10-28 23:59 Sergei Trofimovich
2017-10-14 20:33 Sergei Trofimovich
2017-09-26 22:48 Manuel Rüger
2017-09-26 22:47 Manuel Rüger
2017-08-28 4:42 Markus Meier
2017-07-01 20:31 Alon Bar-Lev
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=1732685591.a82c9394d366236109e9e3761d4a3e057c8a9854.sam@gentoo \
--to=sam@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