public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-fs/cryfs/
Date: Sun,  2 May 2021 17:47:10 +0000 (UTC)	[thread overview]
Message-ID: <1619977381.ce22a67d0afd009b4fc09d3d0ab4cc7f6866a28e.zlogene@gentoo> (raw)

commit:     ce22a67d0afd009b4fc09d3d0ab4cc7f6866a28e
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sun May  2 17:43:01 2021 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sun May  2 17:43:01 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ce22a67d

sys-fs/cryfs: remove libressl support

Package-Manager: Portage-3.0.18, Repoman-3.0.2
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>

 sys-fs/cryfs/cryfs-0.10.2.ebuild | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/sys-fs/cryfs/cryfs-0.10.2.ebuild b/sys-fs/cryfs/cryfs-0.10.2.ebuild
index fb7866b6393..feb0b0eec32 100644
--- a/sys-fs/cryfs/cryfs-0.10.2.ebuild
+++ b/sys-fs/cryfs/cryfs-0.10.2.ebuild
@@ -20,7 +20,7 @@ HOMEPAGE="https://www.cryfs.org/"
 
 LICENSE="LGPL-3 MIT"
 SLOT="0"
-IUSE="custom-optimization debug libressl test"
+IUSE="custom-optimization debug test"
 RESTRICT="!test? ( test )"
 
 RDEPEND="
@@ -28,8 +28,7 @@ RDEPEND="
 	>=dev-libs/crypto++-8.2.0:=
 	net-misc/curl:=
 	>=sys-fs/fuse-2.8.6:0
-	!libressl? ( dev-libs/openssl:0= )
-	libressl? ( dev-libs/libressl:= )
+	dev-libs/openssl:0=
 "
 DEPEND="${RDEPEND}
 	${PYTHON_DEPS}


             reply	other threads:[~2021-05-02 17:47 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-02 17:47 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-15  9:29 [gentoo-commits] repo/gentoo:master commit in: sys-fs/cryfs/ Ulrich Müller
2025-01-24  8:14 Sam James
2024-09-01  2:39 Yixun Lan
2024-08-30 13:15 Arthur Zamarin
2024-06-03 11:15 Sam James
2024-03-03 17:33 Andreas K. Hüttel
2024-02-28 22:57 Sam James
2023-06-27  7:06 Sam James
2023-04-26  4:03 Sam James
2023-01-23  2:40 Sam James
2022-09-04 13:03 David Seifert
2022-06-28  4:18 WANG Xuerui
2022-04-18 18:56 Alexey Shvetsov
2021-10-14  6:38 Andreas Sturmlechner
2021-10-13 20:33 Sam James
2021-08-29 10:02 Agostino Sarubbo
2021-08-18  0:35 Yixun Lan
2021-08-13 18:33 Sam James
2021-08-13 18:33 Sam James
2021-05-10  9:45 Sam James
2021-01-18  8:55 Joonas Niilola
2020-11-05 12:32 Joonas Niilola
2020-11-05 12:32 Joonas Niilola
2020-10-16 11:12 Georgy Yakovlev
2020-06-04 20:57 Andreas Sturmlechner
2020-05-16  7:09 Joonas Niilola
2020-05-16  7:09 Joonas Niilola
2020-04-17 15:56 Andreas Sturmlechner
2020-02-10 13:26 Michał Górny
2020-01-18 23:09 Andreas Sturmlechner
2020-01-18 23:09 Andreas Sturmlechner
2020-01-18 23:09 Andreas Sturmlechner
2019-11-13  2:51 Aaron Bauman
2019-11-02  8:42 Agostino Sarubbo
2019-11-01 23:51 Thomas Deutschmann
2019-11-01  8:53 Andreas Sturmlechner
2019-10-26 21:14 Andreas Sturmlechner
2019-10-26 21:06 Andreas Sturmlechner
2019-10-26 20:15 Andreas Sturmlechner
2019-06-16 21:57 Andreas Sturmlechner
2019-06-16 21:57 Andreas Sturmlechner
2019-06-16 21:57 Andreas Sturmlechner
2019-06-16 21:57 Andreas Sturmlechner
2019-06-16 21:57 Andreas Sturmlechner
2019-06-16 21:57 Andreas Sturmlechner
2019-05-28  2:35 Aaron Bauman
2019-02-19 18:04 Andreas Sturmlechner
2018-09-24  1:50 Thomas Deutschmann
2018-09-16 17:51 Mikle Kolyada
2018-08-11 17:03 Mike Gilbert
2018-04-11 22:47 Patrice Clement
2018-03-15 20:17 Markus Meier
2018-01-21  5:03 Michael Palimaka
2018-01-18 16:07 Mikle Kolyada
2018-01-17 11:01 Andreas Sturmlechner
2017-10-11 19:15 Johannes Huber
2017-10-11 19:15 Johannes Huber
2017-10-11 19:15 Johannes Huber
2017-05-27 13:48 Michał Górny
2017-05-27 13:48 Michał Górny
2017-05-24 17:12 Michał Górny
2017-05-24 17:12 Michał Górny
2017-05-24 17:04 Michał Górny

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=1619977381.ce22a67d0afd009b4fc09d3d0ab4cc7f6866a28e.zlogene@gentoo \
    --to=zlogene@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