public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: sci-libs/nipy/
Date: Sun, 14 Aug 2016 19:24:25 +0000 (UTC)	[thread overview]
Message-ID: <1471202655.e42015ed624b0fea7cc44839bf6670aded6c7e96.jlec@gentoo> (raw)

commit:     e42015ed624b0fea7cc44839bf6670aded6c7e96
Author:     Justin Lecher <jlec <AT> gentoo <DOT> org>
AuthorDate: Sun Aug 14 19:23:49 2016 +0000
Commit:     Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Sun Aug 14 19:24:15 2016 +0000
URL:        https://gitweb.gentoo.org/proj/sci.git/commit/?id=e42015ed

sci-libs/nipy: Add missing dep

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=589312

Package-Manager: portage-2.3.0
Signed-off-by: Justin Lecher <jlec <AT> gentoo.org>

 sci-libs/nipy/nipy-0.4.0.ebuild | 3 ++-
 sci-libs/nipy/nipy-9999.ebuild  | 3 ++-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/sci-libs/nipy/nipy-0.4.0.ebuild b/sci-libs/nipy/nipy-0.4.0.ebuild
index ae7d99c..5cb4a33 100644
--- a/sci-libs/nipy/nipy-0.4.0.ebuild
+++ b/sci-libs/nipy/nipy-0.4.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2015 Gentoo Foundation
+# Copyright 1999-2016 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 # $Id$
 
@@ -18,6 +18,7 @@ KEYWORDS="~amd64 ~x86 ~amd64-linux ~x86-linux"
 IUSE=""
 
 RDEPEND="
+	dev-python/prov[${PYTHON_USEDEP}]
 	sci-libs/scipy[${PYTHON_USEDEP}]
 	dev-python/sympy[${PYTHON_USEDEP}]
 	>=sci-libs/nibabel-1.2[${PYTHON_USEDEP}]

diff --git a/sci-libs/nipy/nipy-9999.ebuild b/sci-libs/nipy/nipy-9999.ebuild
index 72f40e6..8e48a80 100644
--- a/sci-libs/nipy/nipy-9999.ebuild
+++ b/sci-libs/nipy/nipy-9999.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2014 Gentoo Foundation
+# Copyright 1999-2016 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 # $Id$
 
@@ -19,6 +19,7 @@ IUSE=""
 KEYWORDS=""
 
 DEPEND="
+	dev-python/prov[${PYTHON_USEDEP}]
 	dev-python/setuptools[${PYTHON_USEDEP}]
 	dev-python/numpy[${PYTHON_USEDEP}]"
 RDEPEND="${DEPEND}


             reply	other threads:[~2016-08-14 19:24 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-14 19:24 Justin Lecher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-21  1:17 [gentoo-commits] proj/sci:master commit in: sci-libs/nipy/ Horea Christian
2023-05-02 23:58 Horea Christian
2023-05-02 12:55 Andrew Ammerlaan
2023-01-30 10:41 Horea Christian
2023-01-30 10:41 Horea Christian
2023-01-26 21:16 Horea Christian
2022-07-11 14:39 Horea Christian
2022-07-11 14:39 Horea Christian
2021-12-16 10:57 Andrew Ammerlaan
2021-06-01  8:38 Andrew Ammerlaan
2021-01-30 15:20 Andrew Ammerlaan
2021-01-20  9:39 Andrew Ammerlaan
2021-01-13 21:06 Andrew Ammerlaan
2020-12-23  8:04 Horea Christian
2020-09-27  4:21 Horea Christian
2020-09-26 11:38 Horea Christian
2020-03-29  2:55 Horea Christian
2020-01-07 22:00 Horea Christian
2018-07-31 12:20 Horea Christian
2018-07-30 11:51 Horea Christian
2017-08-25  4:04 Benda XU
2015-11-17 15:46 Justin Lecher
2015-11-17 15:46 Justin Lecher
2015-11-17 15:46 Justin Lecher
2014-01-06 18:33 Justin Lecher

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=1471202655.e42015ed624b0fea7cc44839bf6670aded6c7e96.jlec@gentoo \
    --to=jlec@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