From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-auth/oath-toolkit/
Date: Fri, 07 Mar 2025 05:52:23 +0000 (UTC) [thread overview]
Message-ID: <1741326705.a5bdc610e63cac3fd4f72ce1050e60a730b60d6d.sam@gentoo> (raw)
commit: a5bdc610e63cac3fd4f72ce1050e60a730b60d6d
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 7 05:51:20 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Mar 7 05:51:45 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a5bdc610
sys-auth/oath-toolkit: drop bogus ICU dep
The real issue was fixed by bf230e0ecd0f96ae77b582be69b3adbde1b128af
which fixes as-needed in libtool w/ elibtoolize.
Bug: https://bugs.gentoo.org/719314
Bug: https://bugs.gentoo.org/833850
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../{oath-toolkit-2.6.12.ebuild => oath-toolkit-2.6.12-r1.ebuild} | 1 -
1 file changed, 1 deletion(-)
diff --git a/sys-auth/oath-toolkit/oath-toolkit-2.6.12.ebuild b/sys-auth/oath-toolkit/oath-toolkit-2.6.12-r1.ebuild
similarity index 99%
rename from sys-auth/oath-toolkit/oath-toolkit-2.6.12.ebuild
rename to sys-auth/oath-toolkit/oath-toolkit-2.6.12-r1.ebuild
index 74bd6fafabb5..a2d357e1055a 100644
--- a/sys-auth/oath-toolkit/oath-toolkit-2.6.12.ebuild
+++ b/sys-auth/oath-toolkit/oath-toolkit-2.6.12-r1.ebuild
@@ -16,7 +16,6 @@ IUSE="pam static-libs test"
RESTRICT="!test? ( test )"
DEPEND="
- dev-libs/icu:=
dev-libs/libxml2
dev-libs/xmlsec:=
pam? ( sys-libs/pam )
next reply other threads:[~2025-03-07 5:52 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 5:52 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-07 5:44 [gentoo-commits] repo/gentoo:master commit in: sys-auth/oath-toolkit/ Sam James
2024-10-05 16:52 Arthur Zamarin
2024-10-05 14:33 Arthur Zamarin
2024-10-05 14:17 Sam James
2024-10-05 12:58 Arthur Zamarin
2024-10-05 8:46 Arthur Zamarin
2024-10-05 8:19 Arthur Zamarin
2024-10-05 7:50 Arthur Zamarin
2024-10-05 7:28 Sam James
2024-10-05 7:22 Sam James
2024-10-05 7:22 Sam James
2024-08-31 13:50 Michael Orlitzky
2024-01-14 2:30 Sam James
2024-01-03 9:27 Sam James
2023-11-18 16:46 Sam James
2023-09-18 19:59 Arthur Zamarin
2023-09-07 23:03 Sam James
2023-09-07 23:03 Sam James
2023-09-07 20:16 Sam James
2023-07-20 0:08 Sam James
2023-04-29 7:52 Arthur Zamarin
2023-04-22 16:36 Arthur Zamarin
2023-04-18 5:30 Sam James
2023-04-16 5:07 Sam James
2023-04-15 5:40 Sam James
2023-04-09 18:54 Arthur Zamarin
2023-04-09 18:53 Arthur Zamarin
2023-04-09 18:53 Arthur Zamarin
2023-03-05 12:37 Sam James
2023-03-05 12:37 Sam James
2022-11-29 18:06 WANG Xuerui
2022-02-21 22:11 Sam James
2021-10-20 17:17 Mike Gilbert
2021-07-24 23:02 Marek Szuba
2020-12-13 15:15 Mikle Kolyada
2020-06-08 6:41 Michał Górny
2020-05-13 17:14 Agostino Sarubbo
2020-05-09 8:47 Mart Raudsepp
2020-05-07 16:35 Mikle Kolyada
2019-10-12 20:39 Mikle Kolyada
2019-08-21 2:14 Matt Turner
2019-06-21 8:03 Agostino Sarubbo
2019-04-17 18:07 Aaron Bauman
2019-02-03 18:54 Sergei Trofimovich
2019-02-02 11:58 Sergei Trofimovich
2018-02-05 22:19 Robin H. Johnson
2017-11-25 14:39 Patrick Lauer
2017-02-01 22:49 Robin H. Johnson
2016-11-27 22:39 Aaron Bauman
2015-10-26 20:19 Sven Wegener
2015-10-26 20:19 Sven Wegener
2015-10-26 20:06 Sven Wegener
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=1741326705.a5bdc610e63cac3fd4f72ce1050e60a730b60d6d.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