public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sebastien Fabbro" <bicatali@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/naima/
Date: Thu, 29 Dec 2016 19:56:40 +0000 (UTC)	[thread overview]
Message-ID: <1483041361.1716512bc179c748c3bbc75b9fec4e1aceee2f6c.bicatali@gentoo> (raw)

commit:     1716512bc179c748c3bbc75b9fec4e1aceee2f6c
Author:     Sébastien Fabbro <bicatali <AT> gentoo <DOT> org>
AuthorDate: Thu Dec 29 18:05:40 2016 +0000
Commit:     Sebastien Fabbro <bicatali <AT> gentoo <DOT> org>
CommitDate: Thu Dec 29 19:56:01 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1716512b

dev-python/naima: add addpredict workaround during install
Bug hard to reproduce.
Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=604012

Package-Manager: Portage-2.3.3, Repoman-2.3.1

 dev-python/naima/metadata.xml                              |  1 +
 dev-python/naima/{naima-0.8.ebuild => naima-0.8-r1.ebuild} | 12 ++++++++----
 2 files changed, 9 insertions(+), 4 deletions(-)

diff --git a/dev-python/naima/metadata.xml b/dev-python/naima/metadata.xml
index 4744569..a8f7917 100644
--- a/dev-python/naima/metadata.xml
+++ b/dev-python/naima/metadata.xml
@@ -13,6 +13,7 @@
     Markov Chain Monte Carlo.
   </longdescription>
   <upstream>
+    <remote-id type="github">zblz/naima</remote-id>
     <remote-id type="pypi">naima</remote-id>
   </upstream>
 </pkgmetadata>

diff --git a/dev-python/naima/naima-0.8.ebuild b/dev-python/naima/naima-0.8-r1.ebuild
similarity index 80%
rename from dev-python/naima/naima-0.8.ebuild
rename to dev-python/naima/naima-0.8-r1.ebuild
index 6052c8e..749dafc 100644
--- a/dev-python/naima/naima-0.8.ebuild
+++ b/dev-python/naima/naima-0.8-r1.ebuild
@@ -20,22 +20,26 @@ DOCS=( README.rst )
 
 RDEPEND="
 	dev-python/astropy[${PYTHON_USEDEP}]
+	dev-python/corner[${PYTHON_USEDEP}]
 	dev-python/emcee[${PYTHON_USEDEP}]
-	>=dev-python/numpy-1.10[${PYTHON_USEDEP}]"
+	dev-python/h5py[${PYTHON_USEDEP}]
+	dev-python/numpy[${PYTHON_USEDEP}]
+	sci-libs/scipy[${PYTHON_USEDEP}]"
 
 DEPEND="${RDEPEND}
 	dev-python/astropy-helpers[${PYTHON_USEDEP}]
 	dev-python/setuptools[${PYTHON_USEDEP}]
 	doc? ( dev-python/sphinx[${PYTHON_USEDEP}] )
-	test? (
-		dev-python/h5py[${PYTHON_USEDEP}]
-		dev-python/pytest[${PYTHON_USEDEP}] )"
+	test? (	dev-python/pytest[${PYTHON_USEDEP}] )"
 
 DOCS=( README.rst CHANGES.rst )
 
 python_prepare_all() {
 	sed -e '/auto_use/s/True/False/' -i setup.cfg || die
 	xdg_environment_reset
+	# issues during install time (bug #604012)
+	addpredict /proc/mtrr
+	addpredict /sys/devices/system/cpu/
 	distutils-r1_python_prepare_all
 }
 


             reply	other threads:[~2016-12-29 19:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-29 19:56 Sebastien Fabbro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-12-28 16:52 [gentoo-commits] repo/gentoo:master commit in: dev-python/naima/ Mikle Kolyada
2017-06-28 18:21 Sebastien Fabbro
2016-12-29  7:02 Sebastien Fabbro
2016-09-01 17:01 Sebastien Fabbro
2016-06-09 17:24 Sebastien Fabbro
2016-03-22 16:52 Sebastien Fabbro
2016-03-21 23:08 Sebastien Fabbro

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=1483041361.1716512bc179c748c3bbc75b9fec4e1aceee2f6c.bicatali@gentoo \
    --to=bicatali@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