From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libltdl/
Date: Sat, 4 Mar 2023 07:45:50 +0000 (UTC) [thread overview]
Message-ID: <1677915937.1bffc347e88f9d13d9bd3fe3f501c02a27c1736f.arthurzam@gentoo> (raw)
commit: 1bffc347e88f9d13d9bd3fe3f501c02a27c1736f
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 4 07:45:37 2023 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Mar 4 07:45:37 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1bffc347
dev-libs/libltdl: Stabilize 2.4.7-r1 amd64, #899300
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
dev-libs/libltdl/libltdl-2.4.7-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/libltdl/libltdl-2.4.7-r1.ebuild b/dev-libs/libltdl/libltdl-2.4.7-r1.ebuild
index a93034b3aad6..2bc43d774bc2 100644
--- a/dev-libs/libltdl/libltdl-2.4.7-r1.ebuild
+++ b/dev-libs/libltdl/libltdl-2.4.7-r1.ebuild
@@ -16,7 +16,7 @@ S="${WORKDIR}"/${MY_P}/libltdl
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="~alpha ~amd64 arm arm64 hppa ~ia64 ~loong ~m68k ~mips ppc ppc64 ~riscv ~s390 ~sparc ~x86 ~x64-cygwin ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~loong ~m68k ~mips ppc ppc64 ~riscv ~s390 ~sparc ~x86 ~x64-cygwin ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
IUSE="static-libs"
# libltdl doesn't have a testsuite.
next reply other threads:[~2023-03-04 7:45 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 7:45 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-31 23:48 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libltdl/ Sam James
2025-01-25 17:01 Sam James
2025-01-25 15:52 Matt Turner
2025-01-06 8:09 Sam James
2025-01-06 8:04 Sam James
2025-01-06 8:04 Sam James
2025-01-06 8:04 Sam James
2025-01-06 8:04 Sam James
2025-01-06 8:04 Sam James
2025-01-06 8:04 Sam James
2024-11-21 12:23 Sam James
2024-09-30 2:36 Sam James
2024-09-30 2:36 Sam James
2024-09-25 16:53 Sam James
2024-08-30 7:59 Sam James
2024-08-14 22:53 Sam James
2024-05-16 0:51 Sam James
2024-01-18 1:52 Mike Frysinger
2024-01-18 1:52 Mike Frysinger
2023-03-04 8:26 Arthur Zamarin
2023-03-04 7:54 Arthur Zamarin
2023-03-04 7:09 Arthur Zamarin
2023-03-04 6:20 Arthur Zamarin
2023-03-04 6:10 Arthur Zamarin
2023-03-04 5:57 Arthur Zamarin
2023-03-04 5:52 Arthur Zamarin
2023-01-28 0:06 Mike Frysinger
2022-12-10 2:15 Sam James
2022-06-16 23:05 Jakov Smolić
2022-06-14 7:16 Agostino Sarubbo
2022-06-14 7:11 Agostino Sarubbo
2022-06-14 7:11 Agostino Sarubbo
2022-06-13 21:23 Sam James
2022-06-13 21:14 Sam James
2022-06-13 21:14 Sam James
2022-06-13 21:00 Jakov Smolić
2022-03-25 3:10 Sam James
2022-03-25 3:10 Sam James
2022-03-17 21:30 Sam James
2022-03-17 21:24 Sam James
2020-12-27 14:21 Fabian Groffen
2020-02-18 19:11 David Seifert
2019-12-07 14:36 Michał Górny
2019-05-04 18:38 Andreas K. Hüttel
2017-03-14 9:02 Michael Haubenwallner
2017-01-29 16:19 Fabian Groffen
2016-12-09 13:53 Lars Wendler
2015-09-13 18:14 Fabian Groffen
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=1677915937.1bffc347e88f9d13d9bd3fe3f501c02a27c1736f.arthurzam@gentoo \
--to=arthurzam@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