public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "David Seifert" <soap@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/leveldb/
Date: Sun, 30 Jul 2017 14:30:52 +0000 (UTC)	[thread overview]
Message-ID: <1501425042.844cb5fa97a1ca85b6e83fb16f3e9e661f1e0e42.soap@gentoo> (raw)

commit:     844cb5fa97a1ca85b6e83fb16f3e9e661f1e0e42
Author:     Sergey Alirzaev <zl29ah <AT> gmail <DOT> com>
AuthorDate: Mon Jul 17 16:39:38 2017 +0000
Commit:     David Seifert <soap <AT> gentoo <DOT> org>
CommitDate: Sun Jul 30 14:30:42 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=844cb5fa

dev-libs/leveldb: := dep on app-arch/snappy

libsnappy.so.1.1.5: cannot open shared object file: No such file or directory
Closes: https://github.com/gentoo/gentoo/pull/5115

 dev-libs/leveldb/{leveldb-1.18-r1.ebuild => leveldb-1.18-r2.ebuild} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-libs/leveldb/leveldb-1.18-r1.ebuild b/dev-libs/leveldb/leveldb-1.18-r2.ebuild
similarity index 98%
rename from dev-libs/leveldb/leveldb-1.18-r1.ebuild
rename to dev-libs/leveldb/leveldb-1.18-r2.ebuild
index 198f75119f6..0afecb254ff 100644
--- a/dev-libs/leveldb/leveldb-1.18-r1.ebuild
+++ b/dev-libs/leveldb/leveldb-1.18-r2.ebuild
@@ -16,7 +16,7 @@ IUSE="+snappy static-libs +tcmalloc kernel_FreeBSD"
 
 DEPEND="tcmalloc? ( dev-util/google-perftools )
 	snappy? (
-		app-arch/snappy
+		app-arch/snappy:=
 		static-libs? ( app-arch/snappy[static-libs] )
 	)"
 RDEPEND="${DEPEND}"


             reply	other threads:[~2017-07-30 14:30 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-30 14:30 David Seifert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-12 19:23 [gentoo-commits] repo/gentoo:master commit in: dev-libs/leveldb/ Arthur Zamarin
2023-09-27 16:44 WANG Xuerui
2023-03-17  9:06 Arthur Zamarin
2023-03-17  9:05 Arthur Zamarin
2023-03-15 20:01 Arthur Zamarin
2023-03-15 20:01 Arthur Zamarin
2023-03-15 19:57 Arthur Zamarin
2023-03-15 19:57 Arthur Zamarin
2023-03-15 19:57 Arthur Zamarin
2023-02-09 14:52 Arthur Zamarin
2023-02-09 14:52 Arthur Zamarin
2022-10-10 15:25 Arthur Zamarin
2022-02-04 20:16 Arthur Zamarin
2022-02-02  0:08 Sam James
2022-02-01  7:36 Agostino Sarubbo
2022-02-01  7:30 Agostino Sarubbo
2022-02-01  5:57 Sam James
2022-01-31 20:11 Arthur Zamarin
2022-01-31 20:08 Arthur Zamarin
2022-01-17  8:13 Joshua Kinard
2022-01-04  3:29 Sam James
2021-12-31 16:13 Arthur Zamarin
2021-10-27 22:42 Sam James
2021-10-27 22:35 Sam James
2021-10-04 22:58 Sam James
2021-09-16  1:49 Sam James
2021-09-07  3:07 Sam James
2021-08-20 12:54 Arthur Zamarin
2021-08-15 17:50 Arthur Zamarin
2021-08-13 14:16 Marek Szuba
2020-01-15  7:20 Michał Górny
2019-12-31 18:08 Aaron Bauman
2019-11-13  2:10 Aaron Bauman
2019-11-13  2:10 Aaron Bauman
2019-08-30 18:39 Sergei Trofimovich
2019-06-04 10:59 Agostino Sarubbo
2019-05-26  7:21 Sergei Trofimovich
2019-03-20 11:23 Mikle Kolyada
2019-03-19  2:03 Thomas Deutschmann
2018-06-17 20:34 David Seifert
2018-06-17 20:34 David Seifert
2017-11-18 10:13 Sergei Trofimovich
2016-11-03 16:19 Göktürk Yüksek
2015-10-06 22:04 Chí-Thanh Christopher Nguyễn
2015-09-21  4:58 Jeroen Roovers

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=1501425042.844cb5fa97a1ca85b6e83fb16f3e9e661f1e0e42.soap@gentoo \
    --to=soap@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