From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/patchelf/
Date: Wed, 2 Aug 2023 04:27:33 +0000 (UTC) [thread overview]
Message-ID: <1690950386.61d1d40e71fd2bbc82345c85ec1c95bbd0de0a76.sam@gentoo> (raw)
commit: 61d1d40e71fd2bbc82345c85ec1c95bbd0de0a76
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Aug 2 04:26:26 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Aug 2 04:26:26 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=61d1d40e
dev-util/patchelf: Stabilize 0.18.0 hppa, #911028
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-util/patchelf/patchelf-0.18.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-util/patchelf/patchelf-0.18.0.ebuild b/dev-util/patchelf/patchelf-0.18.0.ebuild
index b4fbaa1c8439..e00b1f7629dd 100644
--- a/dev-util/patchelf/patchelf-0.18.0.ebuild
+++ b/dev-util/patchelf/patchelf-0.18.0.ebuild
@@ -9,7 +9,7 @@ DESCRIPTION="Small utility to modify the dynamic linker and RPATH of ELF executa
HOMEPAGE="https://github.com/NixOS/patchelf"
SRC_URI="https://github.com/NixOS/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
SLOT="0"
-KEYWORDS="amd64 arm arm64 ~hppa ~ia64 ~loong ppc ppc64 ~riscv ~s390 ~sparc x86 ~amd64-linux ~riscv-linux ~x86-linux"
+KEYWORDS="amd64 arm arm64 hppa ~ia64 ~loong ppc ppc64 ~riscv ~s390 ~sparc x86 ~amd64-linux ~riscv-linux ~x86-linux"
LICENSE="GPL-3"
PATCHES=(
next reply other threads:[~2023-08-02 4:27 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 4:27 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-26 20:17 [gentoo-commits] repo/gentoo:master commit in: dev-util/patchelf/ Ionen Wolkens
2023-11-10 5:47 Viorel Munteanu
2023-08-24 21:42 James Le Cuirot
2023-08-24 21:42 James Le Cuirot
2023-08-24 21:42 James Le Cuirot
2023-08-24 18:09 Arthur Zamarin
2023-06-18 22:17 James Le Cuirot
2023-06-17 22:48 Sam James
2023-06-17 3:55 Sam James
2023-06-17 3:55 Sam James
2023-06-17 2:49 Sam James
2023-06-17 2:49 Sam James
2023-06-17 2:49 Sam James
2023-06-16 13:47 Arthur Zamarin
2023-04-23 18:37 James Le Cuirot
2023-04-23 18:21 James Le Cuirot
2023-01-13 23:33 James Le Cuirot
2022-12-24 17:21 James Le Cuirot
2022-12-24 2:01 Sam James
2022-12-24 1:46 Sam James
2022-12-24 1:46 Sam James
2022-12-24 1:46 Sam James
2022-12-24 1:46 Sam James
2022-12-24 1:46 Sam James
2022-12-24 1:46 Sam James
2022-11-14 9:24 Arthur Zamarin
2022-11-08 22:52 James Le Cuirot
2022-10-29 13:32 James Le Cuirot
2022-10-29 13:32 James Le Cuirot
2022-10-25 8:07 Sam James
2022-10-25 8:07 Sam James
2022-10-24 6:37 Agostino Sarubbo
2022-10-23 7:52 Agostino Sarubbo
2022-10-23 7:52 Agostino Sarubbo
2022-10-23 7:51 Agostino Sarubbo
2022-10-09 16:10 Sam James
2022-10-09 0:04 Sam James
2022-07-22 7:31 James Le Cuirot
2022-07-16 22:43 James Le Cuirot
2022-07-16 22:42 James Le Cuirot
2022-03-21 21:48 James Le Cuirot
2022-03-21 9:18 Jakov Smolić
2022-03-21 7:50 Agostino Sarubbo
2022-03-21 7:48 Agostino Sarubbo
2022-03-21 7:48 Agostino Sarubbo
2022-03-21 7:47 Agostino Sarubbo
2022-02-26 23:30 James Le Cuirot
2022-02-26 23:30 James Le Cuirot
2021-12-16 23:19 James Le Cuirot
2021-12-16 23:19 James Le Cuirot
2021-08-22 9:43 James Le Cuirot
2021-08-22 9:43 James Le Cuirot
2020-08-29 19:57 James Le Cuirot
2020-08-18 22:31 James Le Cuirot
2019-11-22 21:29 Aaron Bauman
2019-11-20 13:23 Agostino Sarubbo
2019-11-20 13:21 Agostino Sarubbo
2019-11-20 11:27 Agostino Sarubbo
2019-11-20 11:21 Agostino Sarubbo
2019-07-29 13:04 Aaron Bauman
2019-05-03 20:45 James Le Cuirot
2019-03-30 0:06 James Le Cuirot
2019-03-30 0:06 James Le Cuirot
2019-01-21 22:57 James Le Cuirot
2018-03-26 21:01 James Le Cuirot
2017-12-20 21:53 Sergei Trofimovich
2016-03-17 22:41 James Le Cuirot
2016-03-15 7:06 James Le Cuirot
2016-01-08 9:42 James Le Cuirot
2015-11-22 15:16 James Le Cuirot
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=1690950386.61d1d40e71fd2bbc82345c85ec1c95bbd0de0a76.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