From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-vcs/git-crypt/
Date: Wed, 2 Nov 2022 20:06:11 +0000 (UTC) [thread overview]
Message-ID: <1667419562.96aabb34b436d4cd0e5bec4367c457f44756b1e0.sam@gentoo> (raw)
commit: 96aabb34b436d4cd0e5bec4367c457f44756b1e0
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 2 20:06:02 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Nov 2 20:06:02 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=96aabb34
dev-vcs/git-crypt: fix build w/ OpenSSL 1.1.x
Closes: https://bugs.gentoo.org/879095
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-vcs/git-crypt/git-crypt-0.7.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-vcs/git-crypt/git-crypt-0.7.0.ebuild b/dev-vcs/git-crypt/git-crypt-0.7.0.ebuild
index d9424c732212..9df1724c5b16 100644
--- a/dev-vcs/git-crypt/git-crypt-0.7.0.ebuild
+++ b/dev-vcs/git-crypt/git-crypt-0.7.0.ebuild
@@ -22,7 +22,7 @@ BDEPEND="dev-libs/libxslt"
src_configure() {
# bug #805545, https://github.com/AGWA/git-crypt/issues/232
- append-cppflags -DOPENSSL_API_COMPAT=0x30000000L
+ append-cppflags -DOPENSSL_API_COMPAT=10101
tc-export CXX
# bug #689180
next reply other threads:[~2022-11-02 20:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 20:06 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-11 6:52 [gentoo-commits] repo/gentoo:master commit in: dev-vcs/git-crypt/ Petr Vaněk
2022-12-01 15:52 Jakov Smolić
2022-11-01 23:32 Sam James
2022-11-01 23:32 Sam James
2022-11-01 23:21 Sam James
2022-11-01 23:21 Sam James
2022-11-01 23:21 Sam James
2021-04-03 21:58 Sam James
2019-03-26 13:19 Lars Wendler
2017-12-24 15:23 Patrick Lauer
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=1667419562.96aabb34b436d4cd0e5bec4367c457f44756b1e0.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