From: "David Seifert" <soap@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/graph-tool/
Date: Sat, 16 Apr 2022 17:59:21 +0000 (UTC) [thread overview]
Message-ID: <1650131950.f2329ac2fe1b4c6d854c785e6974f8a869548a68.soap@gentoo> (raw)
commit: f2329ac2fe1b4c6d854c785e6974f8a869548a68
Author: David Seifert <soap <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 16 17:59:10 2022 +0000
Commit: David Seifert <soap <AT> gentoo <DOT> org>
CommitDate: Sat Apr 16 17:59:10 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f2329ac2
dev-python/graph-tool: pull in x11-libs/cairo[X]
Closes: https://bugs.gentoo.org/829851
Signed-off-by: David Seifert <soap <AT> gentoo.org>
dev-python/graph-tool/graph-tool-2.44.ebuild | 1 +
dev-python/graph-tool/graph-tool-9999.ebuild | 1 +
2 files changed, 2 insertions(+)
diff --git a/dev-python/graph-tool/graph-tool-2.44.ebuild b/dev-python/graph-tool/graph-tool-2.44.ebuild
index 5078373af0e5..f45d24d4fbfe 100644
--- a/dev-python/graph-tool/graph-tool-2.44.ebuild
+++ b/dev-python/graph-tool/graph-tool-2.44.ebuild
@@ -34,6 +34,7 @@ RDEPEND="
cairo? (
dev-cpp/cairomm:0
dev-python/pycairo[${PYTHON_USEDEP}]
+ x11-libs/cairo[X]
)"
DEPEND="${RDEPEND}
dev-cpp/sparsehash"
diff --git a/dev-python/graph-tool/graph-tool-9999.ebuild b/dev-python/graph-tool/graph-tool-9999.ebuild
index 5078373af0e5..f45d24d4fbfe 100644
--- a/dev-python/graph-tool/graph-tool-9999.ebuild
+++ b/dev-python/graph-tool/graph-tool-9999.ebuild
@@ -34,6 +34,7 @@ RDEPEND="
cairo? (
dev-cpp/cairomm:0
dev-python/pycairo[${PYTHON_USEDEP}]
+ x11-libs/cairo[X]
)"
DEPEND="${RDEPEND}
dev-cpp/sparsehash"
next reply other threads:[~2022-04-16 17:59 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 17:59 David Seifert [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-28 20:07 [gentoo-commits] repo/gentoo:master commit in: dev-python/graph-tool/ David Seifert
2024-08-03 13:19 David Seifert
2024-08-03 13:19 David Seifert
2024-07-22 19:47 David Seifert
2024-07-04 10:41 David Seifert
2024-04-19 10:38 Sam James
2023-10-29 13:15 David Seifert
2023-10-11 12:18 David Seifert
2023-07-30 11:40 David Seifert
2023-07-30 11:40 David Seifert
2023-06-24 14:55 David Seifert
2023-06-19 17:13 David Seifert
2023-06-19 17:13 David Seifert
2023-03-14 11:40 David Seifert
2023-03-14 11:40 David Seifert
2023-03-14 11:40 David Seifert
2022-07-02 13:16 David Seifert
2022-06-19 14:14 David Seifert
2022-06-05 19:44 Michał Górny
2022-06-05 14:27 Michał Górny
2022-04-16 18:04 David Seifert
2022-01-26 12:03 David Seifert
2022-01-07 15:01 David Seifert
2022-01-07 15:01 David Seifert
2021-10-24 11:20 David Seifert
2021-07-08 10:39 David Seifert
2021-07-08 10:39 David Seifert
2021-07-04 14:04 David Seifert
2021-07-04 14:04 David Seifert
2021-07-04 14:04 David Seifert
2021-02-16 2:12 Matt Turner
2020-09-27 22:32 David Seifert
2020-09-21 23:16 David Seifert
2020-09-21 23:16 David Seifert
2020-09-21 23:16 David Seifert
2019-10-07 8:02 David Seifert
2019-10-07 8:02 David Seifert
2019-10-07 8:02 David Seifert
2019-06-30 16:14 David Seifert
2019-06-30 16:14 David Seifert
2019-05-30 16:51 David Seifert
2018-06-26 15:50 Tim Harder
2018-06-25 9:53 Jason Zaman
2018-01-04 20:35 Michał Górny
2017-09-30 6:08 Patrick Lauer
2017-09-05 7:14 David Seifert
2017-09-05 7:14 David Seifert
2017-05-17 18:13 David Seifert
2017-05-17 18:13 David Seifert
2017-05-16 12:57 Agostino Sarubbo
2017-05-15 14:17 Agostino Sarubbo
2017-05-13 8:44 David Seifert
2017-05-10 14:41 Agostino Sarubbo
2017-05-10 9:32 Agostino Sarubbo
2017-05-02 11:58 Michał Górny
2016-12-27 12:48 David Seifert
2016-12-27 11:47 David Seifert
2016-12-27 11:47 David Seifert
2016-11-18 22:17 Patrice Clement
2016-11-05 22:39 Patrice Clement
2016-08-06 16:51 Michał Górny
2016-05-03 21:24 David Seifert
2015-08-28 7:20 Tim Harder
2015-08-28 7:20 Tim Harder
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=1650131950.f2329ac2fe1b4c6d854c785e6974f8a869548a68.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