public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Horea Christian" <horea.christ@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: dev-python/fslpy/
Date: Fri,  8 Nov 2019 06:25:39 +0000 (UTC)	[thread overview]
Message-ID: <1573194321.9a4a50f96873b278d957248e4512ed64b52f7deb.chymera@gentoo> (raw)

commit:     9a4a50f96873b278d957248e4512ed64b52f7deb
Author:     Horea Christian <chr <AT> chymera <DOT> eu>
AuthorDate: Fri Nov  8 06:23:53 2019 +0000
Commit:     Horea Christian <horea.christ <AT> gmail <DOT> com>
CommitDate: Fri Nov  8 06:25:21 2019 +0000
URL:        https://gitweb.gentoo.org/proj/sci.git/commit/?id=9a4a50f9

dev-python/fslpy: corrected indenting

Package-Manager: Portage-2.3.77, Repoman-2.3.17
Signed-off-by: Horea Christian <chr <AT> chymera.eu>

 dev-python/fslpy/fslpy-2.6.2.ebuild | 4 ++--
 dev-python/fslpy/fslpy-2.7.0.ebuild | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/dev-python/fslpy/fslpy-2.6.2.ebuild b/dev-python/fslpy/fslpy-2.6.2.ebuild
index 31ea40ece..389ab8d42 100644
--- a/dev-python/fslpy/fslpy-2.6.2.ebuild
+++ b/dev-python/fslpy/fslpy-2.6.2.ebuild
@@ -22,7 +22,7 @@ DEPEND="
 		dev-python/pytest-cov[${PYTHON_USEDEP}]
 	)
 	dev-python/setuptools[${PYTHON_USEDEP}]
-	"
+"
 RDEPEND="
 	dev-python/deprecation[${PYTHON_USEDEP}]
 	dev-python/h5py[${PYTHON_USEDEP}]
@@ -34,7 +34,7 @@ RDEPEND="
 	=sci-libs/Rtree-0.8.3*[${PYTHON_USEDEP}]
 	sci-libs/scipy[${PYTHON_USEDEP}]
 	>=sci-libs/nibabel-2.3.1[${PYTHON_USEDEP}]
-	"
+"
 
 PATCHES=( "${FILESDIR}/${P}-exclude_tests.patch" )
 

diff --git a/dev-python/fslpy/fslpy-2.7.0.ebuild b/dev-python/fslpy/fslpy-2.7.0.ebuild
index a61c8b6d7..211ae6087 100644
--- a/dev-python/fslpy/fslpy-2.7.0.ebuild
+++ b/dev-python/fslpy/fslpy-2.7.0.ebuild
@@ -22,7 +22,7 @@ DEPEND="
 		dev-python/pytest-cov[${PYTHON_USEDEP}]
 	)
 	dev-python/setuptools[${PYTHON_USEDEP}]
-	"
+"
 RDEPEND="
 	dev-python/h5py[${PYTHON_USEDEP}]
 	dev-python/indexed_gzip[${PYTHON_USEDEP}]
@@ -34,7 +34,7 @@ RDEPEND="
 	=sci-libs/Rtree-0.8.3*[${PYTHON_USEDEP}]
 	>=sci-libs/nibabel-2.3.1[${PYTHON_USEDEP}]
 	sci-libs/scipy[${PYTHON_USEDEP}]
-	"
+"
 
 python_test() {
 	virtx pytest -m "not (dicomtest or fsltest)" --verbose || die


             reply	other threads:[~2019-11-08  6:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08  6:25 Horea Christian [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-23 14:22 [gentoo-commits] proj/sci:master commit in: dev-python/fslpy/ Andrew Ammerlaan
2024-09-23 14:22 Andrew Ammerlaan
2023-07-26 22:14 Alexander Puck Neuwirth
2023-05-03  0:14 Horea Christian
2023-02-16  7:38 Horea Christian
2022-10-11 19:20 Andrew Ammerlaan
2022-10-11 19:20 Andrew Ammerlaan
2022-07-07  4:54 Sam James
2022-01-23 13:06 Andrew Ammerlaan
2022-01-14 20:36 Andrew Ammerlaan
2021-10-10 22:05 Horea Christian
2021-09-30 10:59 Horea Christian
2021-03-15  8:30 Andrew Ammerlaan
2021-02-01  1:27 Horea Christian
2021-01-20 12:29 Andrew Ammerlaan
2020-12-23  8:38 Horea Christian
2020-10-22  6:11 Horea Christian
2020-10-22  6:11 Horea Christian
2020-10-19 21:55 Horea Christian
2020-03-16 20:05 Horea Christian
2019-11-08  6:17 Horea Christian

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=1573194321.9a4a50f96873b278d957248e4512ed64b52f7deb.chymera@gentoo \
    --to=horea.christ@gmail.com \
    --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