From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/iniparser/
Date: Wed, 12 Mar 2025 17:56:44 +0000 (UTC) [thread overview]
Message-ID: <1741802120.5cf8aba799b81705d37a485396dc7dbcf9e4445a.sam@gentoo> (raw)
commit: 5cf8aba799b81705d37a485396dc7dbcf9e4445a
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 12 17:55:20 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Mar 12 17:55:20 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5cf8aba7
dev-libs/iniparser: Stabilize 4.2.6 amd64, #951195
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-libs/iniparser/iniparser-4.2.6.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/iniparser/iniparser-4.2.6.ebuild b/dev-libs/iniparser/iniparser-4.2.6.ebuild
index f951201b5e81..c170252c3088 100644
--- a/dev-libs/iniparser/iniparser-4.2.6.ebuild
+++ b/dev-libs/iniparser/iniparser-4.2.6.ebuild
@@ -12,7 +12,7 @@ S=${WORKDIR}/${PN}-v${PV}
LICENSE="MIT"
SLOT="0/4"
-KEYWORDS="~alpha ~amd64 ~arm arm64 ~hppa ~loong ~m68k ppc ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
+KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ~loong ~m68k ppc ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
IUSE="doc examples"
# tests need work, uses ruby + fetchcontent
RESTRICT="test"
next reply other threads:[~2025-03-12 17:57 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 17:56 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-12 17:56 [gentoo-commits] repo/gentoo:master commit in: dev-libs/iniparser/ Sam James
2025-03-12 17:56 Sam James
2025-03-12 17:56 Sam James
2025-03-12 17:56 Sam James
2025-03-12 17:56 Sam James
2025-03-12 17:56 Sam James
2025-03-02 8:21 Sam James
2025-02-27 13:01 Sam James
2025-02-16 14:42 Ionen Wolkens
2025-01-24 7:35 Sam James
2025-01-24 7:35 Sam James
2025-01-24 6:29 Arthur Zamarin
2025-01-24 6:08 Sam James
2025-01-24 6:08 Sam James
2025-01-07 5:20 Ionen Wolkens
2025-01-07 5:20 Ionen Wolkens
2025-01-07 5:20 Ionen Wolkens
2025-01-07 5:20 Ionen Wolkens
2024-08-25 15:24 Andreas K. Hüttel
2024-06-05 14:53 Ben Kohler
2024-06-04 12:16 Ben Kohler
2024-04-05 14:23 Ben Kohler
2024-04-05 14:23 Ben Kohler
2023-10-13 20:18 Arthur Zamarin
2023-10-13 15:21 Sam James
2023-10-13 15:21 Sam James
2023-10-13 15:21 Sam James
2023-10-13 15:21 Sam James
2023-10-13 15:21 Sam James
2023-10-13 15:21 Sam James
2020-09-05 1:18 Sam James
2020-09-01 1:44 Sam James
2020-08-31 23:40 Sam James
2020-08-31 23:38 Sam James
2020-08-31 20:44 Thomas Deutschmann
2020-08-29 16:32 David Seifert
2020-07-18 0:01 Sam James
2020-06-22 18:35 Sergei Trofimovich
2020-06-07 8:48 Agostino Sarubbo
2020-06-07 8:44 Agostino Sarubbo
2020-06-06 21:46 Mart Raudsepp
2020-06-06 20:13 Agostino Sarubbo
2020-06-06 17:36 Agostino Sarubbo
2020-06-06 17:32 Agostino Sarubbo
2020-06-06 17:29 Agostino Sarubbo
2020-06-06 12:57 Sergei Trofimovich
2019-11-13 2:10 Aaron Bauman
2019-05-04 14:53 Andreas K. Hüttel
2019-05-04 11:02 Mikle Kolyada
2019-03-27 18:45 Fabian Groffen
2017-01-29 16:08 Fabian Groffen
2016-03-07 18:51 Mike Frysinger
2016-03-07 18:51 Mike Frysinger
2015-08-16 15:10 Justin Lecher
2015-08-10 20:58 Sebastian Pipping
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=1741802120.5cf8aba799b81705d37a485396dc7dbcf9e4445a.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