From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-arch/unshield/
Date: Sun, 14 May 2023 08:48:53 +0000 (UTC) [thread overview]
Message-ID: <1684054113.2536ea48ebf971d298b6dbf61a0ce5fdd66f84e8.sam@gentoo> (raw)
commit: 2536ea48ebf971d298b6dbf61a0ce5fdd66f84e8
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun May 14 08:48:33 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun May 14 08:48:33 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2536ea48
app-arch/unshield: Stabilize 1.5.1 amd64, #906316
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-arch/unshield/unshield-1.5.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-arch/unshield/unshield-1.5.1.ebuild b/app-arch/unshield/unshield-1.5.1.ebuild
index 0f72275ec6f7..a016bb33cdc4 100644
--- a/app-arch/unshield/unshield-1.5.1.ebuild
+++ b/app-arch/unshield/unshield-1.5.1.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/twogood/unshield/archive/${PV}.tar.gz -> ${P}.tar.gz
LICENSE="MIT"
SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~hppa ~ppc ~ppc64 ~riscv x86"
+KEYWORDS="amd64 ~arm64 ~hppa ~ppc ~ppc64 ~riscv x86"
# OpenSSL is detected at build time, and used to determine
# whether or not a hand-rolled md5 implementation is used. The build
next reply other threads:[~2023-05-14 8:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 8:48 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-02 21:32 [gentoo-commits] repo/gentoo:master commit in: app-arch/unshield/ Sam James
2025-06-01 16:59 Sam James
2023-05-14 8:48 Sam James
2023-04-28 7:44 Joonas Niilola
2022-11-22 13:46 Arthur Zamarin
2021-09-23 22:47 Marek Szuba
2021-04-30 17:10 Mikle Kolyada
2020-09-05 1:02 Sam James
2019-08-28 9:11 David Seifert
2019-06-05 6:56 Andreas Sturmlechner
2019-06-04 14:45 Thomas Deutschmann
2017-04-28 12:10 Lars Wendler
2016-12-29 10:45 Agostino Sarubbo
2016-12-29 3:03 Aaron Bauman
2016-12-26 23:28 Michael Orlitzky
2016-08-25 15:06 Michael Orlitzky
2016-03-21 22:03 Anthony G. Basile
2015-09-20 13:05 Julian Ospald
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=1684054113.2536ea48ebf971d298b6dbf61a0ce5fdd66f84e8.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