From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/npth/
Date: Wed, 7 Aug 2024 02:55:46 +0000 (UTC) [thread overview]
Message-ID: <1722999329.e6a028b8d3a3a4989120a2a38f1a28f7f0cf921a.sam@gentoo> (raw)
commit: e6a028b8d3a3a4989120a2a38f1a28f7f0cf921a
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Aug 7 02:55:29 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Aug 7 02:55:29 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e6a028b8
dev-libs/npth: Stabilize 1.7-r1 ppc, #937455
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-libs/npth/npth-1.7-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/npth/npth-1.7-r1.ebuild b/dev-libs/npth/npth-1.7-r1.ebuild
index cb730c39aa88..3552bf08f80f 100644
--- a/dev-libs/npth/npth-1.7-r1.ebuild
+++ b/dev-libs/npth/npth-1.7-r1.ebuild
@@ -11,7 +11,7 @@ SRC_URI="mirror://gnupg/${PN}/${P}.tar.bz2"
LICENSE="LGPL-2.1+"
SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc x86 ~amd64-linux ~x86-linux ~arm64-macos ~ppc-macos ~x64-macos ~x64-solaris"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~m68k ~mips ppc ~ppc64 ~riscv ~s390 ~sparc x86 ~amd64-linux ~x86-linux ~arm64-macos ~ppc-macos ~x64-macos ~x64-solaris"
IUSE="test"
RESTRICT="!test? ( test )"
next reply other threads:[~2024-08-07 2:55 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 2:55 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-30 15:31 [gentoo-commits] repo/gentoo:master commit in: dev-libs/npth/ Jakov Smolić
2024-08-30 15:31 Jakov Smolić
2024-08-10 10:28 Michał Górny
2024-08-09 8:57 Sam James
2024-08-09 8:50 Jakov Smolić
2024-08-07 2:55 Sam James
2024-08-07 2:41 Sam James
2024-08-07 2:41 Sam James
2024-02-25 10:41 Jakov Smolić
2024-02-24 12:40 Jakov Smolić
2024-01-03 10:40 Sam James
2023-01-14 19:17 Sam James
2022-05-17 5:34 Sam James
2021-03-27 15:37 David Seifert
2021-01-06 19:34 Fabian Groffen
2020-10-07 0:31 Sam James
2020-10-07 0:31 Sam James
2020-10-07 0:31 Sam James
2020-09-03 23:57 Sam James
2020-09-01 0:17 Sam James
2020-08-18 15:36 Sam James
2020-08-17 14:07 Agostino Sarubbo
2020-08-17 14:07 Agostino Sarubbo
2020-08-17 14:06 Agostino Sarubbo
2020-08-17 14:06 Agostino Sarubbo
2020-01-10 14:21 Kristian Fiskerstrand
2019-05-04 18:38 Andreas K. Hüttel
2018-10-05 19:27 Alon Bar-Lev
2018-09-28 17:34 Tim Harder
2018-06-03 10:01 Mikle Kolyada
2017-12-24 13:21 Patrice Clement
2017-06-02 23:19 Tim Harder
2017-05-24 1:36 Tim Harder
2017-04-08 9:35 Alon Bar-Lev
2017-04-08 9:11 Jeroen Roovers
2017-03-21 14:34 Agostino Sarubbo
2017-03-21 11:31 Michael Weber
2017-03-20 12:28 Agostino Sarubbo
2017-03-20 6:17 Matt Turner
2017-03-20 6:17 Matt Turner
2017-03-20 6:17 Matt Turner
2017-03-20 6:17 Matt Turner
2017-03-20 1:05 Matt Turner
2017-03-17 11:12 Michael Haubenwallner
2017-03-07 16:34 Michael Haubenwallner
2017-02-24 4:16 Mike Frysinger
2017-02-10 10:50 Fabian Groffen
2017-01-26 10:22 Agostino Sarubbo
2017-01-24 9:57 Fabian Groffen
2017-01-18 14:52 Alon Bar-Lev
2016-11-28 23:06 Thomas Deutschmann
2016-11-27 23:57 Tim Harder
2016-09-29 4:06 Jeroen Roovers
2016-09-27 18:44 Markus Meier
2016-09-21 17:48 Tobias Klausmann
2016-08-07 7:12 Tim Harder
2016-06-08 18:55 Mike Frysinger
2016-02-22 0:55 Stephen Klimaszewski
2015-11-18 9:32 Agostino Sarubbo
2015-10-18 16:21 Mikle Kolyada
2015-10-11 13:06 Anthony G. Basile
2015-10-10 17:33 Mikle Kolyada
2015-10-03 8:59 Markus Meier
2015-09-15 6:57 Anthony G. Basile
2015-09-14 13:55 Tobias Klausmann
2015-09-14 3:24 Jeroen Roovers
2015-09-12 16:46 Anthony G. Basile
2015-08-25 4:31 Tim Harder
2015-08-25 4:31 Tim Harder
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=1722999329.e6a028b8d3a3a4989120a2a38f1a28f7f0cf921a.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