public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Yixun Lan" <dlan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-proxy/shadowsocks-libev/
Date: Wed,  7 Sep 2016 01:48:19 +0000 (UTC)	[thread overview]
Message-ID: <1473212897.3c354bc282a1081ae4eef5cb6872f620cf8fbb98.dlan@gentoo> (raw)

commit:     3c354bc282a1081ae4eef5cb6872f620cf8fbb98
Author:     Yixun Lan <dlan <AT> gentoo <DOT> org>
AuthorDate: Wed Sep  7 01:47:02 2016 +0000
Commit:     Yixun Lan <dlan <AT> gentoo <DOT> org>
CommitDate: Wed Sep  7 01:48:17 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3c354bc2

net-proxy/shadowsocks-libev: fix libsodium dep

thanks aihuxiaoxiongmao at gmail dot com for reporting

Package-Manager: portage-2.3.0

 ...shadowsocks-libev-2.5.0.ebuild => shadowsocks-libev-2.5.0-r1.ebuild} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-proxy/shadowsocks-libev/shadowsocks-libev-2.5.0.ebuild b/net-proxy/shadowsocks-libev/shadowsocks-libev-2.5.0-r1.ebuild
similarity index 98%
rename from net-proxy/shadowsocks-libev/shadowsocks-libev-2.5.0.ebuild
rename to net-proxy/shadowsocks-libev/shadowsocks-libev-2.5.0-r1.ebuild
index 051af43..06e70f0 100644
--- a/net-proxy/shadowsocks-libev/shadowsocks-libev-2.5.0.ebuild
+++ b/net-proxy/shadowsocks-libev/shadowsocks-libev-2.5.0-r1.ebuild
@@ -20,7 +20,7 @@ IUSE="debug doc +openssl mbedtls +system-libs"
 RDEPEND="openssl? ( dev-libs/openssl:= )
 	mbedtls? ( net-libs/mbedtls )
 	system-libs? (
-		dev-libs/libsodium
+		>=dev-libs/libsodium-1.0.8
 		dev-libs/libev
 		net-libs/udns
 	)


             reply	other threads:[~2016-09-07  1:48 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07  1:48 Yixun Lan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-06  0:53 [gentoo-commits] repo/gentoo:master commit in: net-proxy/shadowsocks-libev/ Sam James
2021-12-03  1:23 Yixun Lan
2021-01-14  8:20 Yixun Lan
2021-01-13 23:09 Yixun Lan
2020-09-27  8:49 Yixun Lan
2020-02-15  7:21 Yixun Lan
2020-02-15  7:21 Yixun Lan
2020-01-22  6:22 Yixun Lan
2019-12-13  9:21 Yixun Lan
2019-11-16 10:29 Yixun Lan
2019-10-16  2:58 Yixun Lan
2019-10-16  2:58 Yixun Lan
2019-08-29  7:52 Yixun Lan
2019-06-24 22:06 Yixun Lan
2019-06-24 22:06 Yixun Lan
2019-03-20  1:44 Yixun Lan
2019-03-12  6:37 Yixun Lan
2019-03-07  3:24 Yixun Lan
2019-03-07  3:22 Yixun Lan
2019-01-24  9:17 Yixun Lan
2018-10-23 12:49 Benda XU
2018-05-31  5:53 Yixun Lan
2018-04-24 14:20 Yixun Lan
2018-03-13 22:04 Yixun Lan
2018-03-01 14:43 Yixun Lan
2018-03-01 10:40 Yixun Lan
2018-03-01 10:40 Yixun Lan
2017-11-26 23:23 David Seifert
2017-10-04  9:15 Michał Górny
2017-06-06 14:53 Yixun Lan
2017-01-19  9:49 Yixun Lan
2017-01-19  9:49 Yixun Lan
2016-11-24  2:40 Yixun Lan
2016-10-14 21:31 Yixun Lan
2016-10-14 21:31 Yixun Lan
2016-10-11  6:34 Yixun Lan
2016-09-05  7:46 Yixun Lan
2016-09-05  7:46 Yixun Lan
2016-09-01 10:23 Jeroen Roovers
2016-07-09 13:01 Patrick Lauer
2016-06-30 22:03 Yixun Lan
2016-06-30 21:41 Yixun Lan
2016-03-27 17:48 Yixun Lan
2016-03-27 17:48 Yixun Lan
2016-03-27 17:48 Yixun Lan
2015-12-21  7:47 Yixun Lan
2015-08-11 15:08 Yixun Lan

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=1473212897.3c354bc282a1081ae4eef5cb6872f620cf8fbb98.dlan@gentoo \
    --to=dlan@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