From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libsecp256k1/
Date: Sat, 7 Jan 2023 07:41:13 +0000 (UTC) [thread overview]
Message-ID: <1673077186.c90d32f8feb067c03bbda772629e87f07c4ebef2.sam@gentoo> (raw)
commit: c90d32f8feb067c03bbda772629e87f07c4ebef2
Author: Matt Whitlock <gentoo <AT> mattwhitlock <DOT> name>
AuthorDate: Fri Jan 6 22:20:21 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Jan 7 07:39:46 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c90d32f8
dev-libs/libsecp256k1: drop BDEPEND on dev-libs/openssl
OpenSSL testing was removed upstream in October 2021.
See: https://github.com/bitcoin-core/secp256k1/commit/bc08599e776aff33c834ef829843ec5f629d1f39
Signed-off-by: Matt Whitlock <gentoo <AT> mattwhitlock.name>
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-libs/libsecp256k1/libsecp256k1-0.2.0-r1.ebuild | 1 -
1 file changed, 1 deletion(-)
diff --git a/dev-libs/libsecp256k1/libsecp256k1-0.2.0-r1.ebuild b/dev-libs/libsecp256k1/libsecp256k1-0.2.0-r1.ebuild
index 6af45ef9aab1..ecfe9afbe402 100644
--- a/dev-libs/libsecp256k1/libsecp256k1-0.2.0-r1.ebuild
+++ b/dev-libs/libsecp256k1/libsecp256k1-0.2.0-r1.ebuild
@@ -23,7 +23,6 @@ REQUIRED_USE="
"
BDEPEND="
virtual/pkgconfig
- test? ( dev-libs/openssl )
valgrind? ( dev-util/valgrind )
"
next reply other threads:[~2023-01-07 7:41 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 7:41 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-10 15:25 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libsecp256k1/ Sam James
2024-12-10 15:22 Sam James
2024-12-10 15:22 Sam James
2024-12-10 14:37 Arthur Zamarin
2024-12-01 11:51 Sam James
2024-11-09 13:24 Arthur Zamarin
2024-11-09 13:24 Arthur Zamarin
2024-11-09 9:58 Arthur Zamarin
2024-11-09 9:02 Arthur Zamarin
2024-11-07 13:27 Sam James
2024-11-07 13:27 Sam James
2024-11-07 13:27 Sam James
2024-11-07 13:27 Sam James
2024-11-07 13:06 Sam James
2024-11-07 7:46 Sam James
2024-11-06 14:28 Sam James
2024-11-06 14:28 Sam James
2024-11-06 10:57 Sam James
2024-10-12 7:52 Michał Górny
2024-10-11 0:24 Sam James
2024-10-10 6:54 Arthur Zamarin
2024-08-25 15:24 Andreas K. Hüttel
2024-08-13 7:36 Joonas Niilola
2024-08-13 7:36 Joonas Niilola
2024-05-08 20:48 Florian Schmaus
2024-05-08 20:48 Florian Schmaus
2024-01-21 17:09 Sam James
2023-10-24 9:14 Joonas Niilola
2023-10-24 9:14 Joonas Niilola
2023-09-18 9:01 Sam James
2023-05-14 17:11 Sam James
2023-05-14 7:51 Sam James
2023-04-11 4:07 Sam James
2023-03-13 18:07 Sam James
2023-03-13 18:07 Sam James
2023-01-07 7:41 Sam James
2023-01-07 7:41 Sam James
2023-01-07 7:41 Sam James
2023-01-06 12:43 Sam James
2021-05-28 3:17 Sam James
2021-05-28 2:27 Sam James
2021-02-07 9:03 Joonas Niilola
2021-02-07 9:03 Joonas Niilola
2021-01-21 23:41 Sam James
2020-08-30 17:14 Thomas Deutschmann
2020-08-29 13:23 Sam James
2020-05-01 15:09 Joonas Niilola
2019-10-13 11:22 Joonas Niilola
2019-10-13 11:22 Joonas Niilola
2019-10-13 11:22 Joonas Niilola
2019-01-11 21:38 Craig Andrews
2017-01-05 14:12 Anthony G. Basile
2016-12-20 9:08 Agostino Sarubbo
2016-12-19 19:56 Tobias Klausmann
2016-06-26 0:09 Anthony G. Basile
2016-03-20 15:42 Anthony G. Basile
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=1673077186.c90d32f8feb067c03bbda772629e87f07c4ebef2.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