From: "Alfredo Tupone" <tupone@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/caffe2/
Date: Sun, 26 Jun 2022 17:30:05 +0000 (UTC) [thread overview]
Message-ID: <1656264593.e47bc4e8204e32b66568bbaf12e0a5fbcf31b1a1.tupone@gentoo> (raw)
commit: e47bc4e8204e32b66568bbaf12e0a5fbcf31b1a1
Author: Alfredo Tupone <tupone <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 26 17:29:53 2022 +0000
Commit: Alfredo Tupone <tupone <AT> gentoo <DOT> org>
CommitDate: Sun Jun 26 17:29:53 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e47bc4e8
sci-libs/caffe2: fix deps
Closes: https://bugs.gentoo.org/854408
Package-Manager: Portage-3.0.30, Repoman-3.0.3
Signed-off-by: Alfredo Tupone <tupone <AT> gentoo.org>
sci-libs/caffe2/caffe2-1.11.0.ebuild | 1 +
1 file changed, 1 insertion(+)
diff --git a/sci-libs/caffe2/caffe2-1.11.0.ebuild b/sci-libs/caffe2/caffe2-1.11.0.ebuild
index f8e9483bf74a..74e51e18a3ea 100644
--- a/sci-libs/caffe2/caffe2-1.11.0.ebuild
+++ b/sci-libs/caffe2/caffe2-1.11.0.ebuild
@@ -34,6 +34,7 @@ DEPEND="${RDEPEND}
dev-libs/FP16
dev-libs/pocketfft
dev-libs/flatbuffers
+ dev-python/pyyaml[${PYTHON_USEDEP}]
"
S="${WORKDIR}"/${MYP}
next reply other threads:[~2022-06-26 17:30 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 17:30 Alfredo Tupone [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-26 18:03 [gentoo-commits] repo/gentoo:master commit in: sci-libs/caffe2/ Alfredo Tupone
2022-06-26 20:24 Alfredo Tupone
2022-07-02 16:20 Alfredo Tupone
2022-07-03 10:45 Alfredo Tupone
2022-08-04 8:00 Alfredo Tupone
2022-08-29 6:42 Alfredo Tupone
2022-09-14 20:52 Alfredo Tupone
2022-11-10 16:51 Alfredo Tupone
2022-11-30 18:20 Alfredo Tupone
2022-12-16 15:56 Alfredo Tupone
2023-01-03 6:22 Alfredo Tupone
2023-02-12 9:09 Alfredo Tupone
2023-02-15 7:18 Alfredo Tupone
2023-02-15 7:36 Sam James
2023-02-15 19:40 Alfredo Tupone
2023-02-20 21:22 Alfredo Tupone
2023-02-27 7:23 Alfredo Tupone
2023-02-27 14:16 Alfredo Tupone
2023-02-28 7:12 Alfredo Tupone
2023-02-28 7:12 Alfredo Tupone
2023-03-17 18:47 Alfredo Tupone
2023-03-26 18:10 Alfredo Tupone
2023-04-06 19:46 Alfredo Tupone
2023-04-08 14:29 Alfredo Tupone
2023-04-23 13:24 Alfredo Tupone
2023-04-23 17:25 Alfredo Tupone
2023-05-05 6:00 Alfredo Tupone
2023-05-08 21:00 Alfredo Tupone
2023-05-14 7:59 Alfredo Tupone
2023-05-15 6:27 Alfredo Tupone
2023-06-17 14:02 Alfredo Tupone
2023-08-01 7:30 Alfredo Tupone
2023-08-11 7:31 Alfredo Tupone
2023-08-11 8:40 Alfredo Tupone
2023-12-01 5:54 Alfredo Tupone
2023-12-06 19:49 Alfredo Tupone
2023-12-10 10:31 Alfredo Tupone
2023-12-14 18:30 Alfredo Tupone
2023-12-17 9:30 Alfredo Tupone
2023-12-22 22:27 Alfredo Tupone
2023-12-23 8:24 Alfredo Tupone
2023-12-23 16:05 Alfredo Tupone
2023-12-26 22:14 Alfredo Tupone
2023-12-29 9:53 Alfredo Tupone
2024-01-03 18:23 Alfredo Tupone
2024-01-09 7:17 Alfredo Tupone
2024-01-10 21:15 Alfredo Tupone
2024-01-28 22:53 Jonas Stein
2024-02-03 7:22 Michał Górny
2024-02-17 22:21 Alfredo Tupone
2024-02-24 21:57 Alfredo Tupone
2024-03-01 18:54 Alfredo Tupone
2024-03-08 7:26 Alfredo Tupone
2024-03-11 19:28 Alfredo Tupone
2024-03-30 19:36 Alfredo Tupone
2024-03-30 19:40 Alfredo Tupone
2024-04-04 9:20 Alfredo Tupone
2024-04-04 9:23 Alfredo Tupone
2024-04-04 16:28 Alfredo Tupone
2024-04-20 19:31 Alfredo Tupone
2024-05-05 14:15 Alfredo Tupone
2024-05-07 6:06 Alfredo Tupone
2024-05-07 20:48 Alfredo Tupone
2024-05-09 18:46 Alfredo Tupone
2024-06-06 19:07 Alfredo Tupone
2024-06-07 8:32 Alfredo Tupone
2024-07-22 17:14 Alfredo Tupone
2024-09-15 17:36 Alfredo Tupone
2024-09-15 18:43 Alfredo Tupone
2024-09-16 17:42 Alfredo Tupone
2024-09-24 12:41 Alfredo Tupone
2024-10-11 6:49 Alfredo Tupone
2024-10-26 20:43 Alfredo Tupone
2024-10-27 14:13 Alfredo Tupone
2024-11-01 17:14 Alfredo Tupone
2024-11-15 7:39 Alfredo Tupone
2024-11-18 6:59 Alfredo Tupone
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=1656264593.e47bc4e8204e32b66568bbaf12e0a5fbcf31b1a1.tupone@gentoo \
--to=tupone@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