From: "Christoph Junghans" <ottxor@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: sci-libs/pydicom/
Date: Mon, 25 May 2015 23:02:34 +0000 (UTC) [thread overview]
Message-ID: <1430734410.0cba5b2ddee2f6c20e2b5088e724fc5ade3bd46d.ottxor@gentoo> (raw)
commit: 0cba5b2ddee2f6c20e2b5088e724fc5ade3bd46d
Author: Horea Christian <h.chr <AT> mail <DOT> ru>
AuthorDate: Mon May 4 10:13:30 2015 +0000
Commit: Christoph Junghans <ottxor <AT> gentoo <DOT> org>
CommitDate: Mon May 4 10:13:30 2015 +0000
URL: https://gitweb.gentoo.org/proj/sci.git/commit/?id=0cba5b2d
updated homepage
Package-Manager: portage-2.2.18
sci-libs/pydicom/ChangeLog | 3 +++
sci-libs/pydicom/pydicom-0.9.8.ebuild | 2 +-
sci-libs/pydicom/pydicom-9999.ebuild | 2 +-
3 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/sci-libs/pydicom/ChangeLog b/sci-libs/pydicom/ChangeLog
index dac4df3..b8014d9 100644
--- a/sci-libs/pydicom/ChangeLog
+++ b/sci-libs/pydicom/ChangeLog
@@ -2,6 +2,9 @@
# Copyright 1999-2015 Gentoo Foundation; Distributed under the GPL v2
# $Header: $
+ 04 May 2015; <chymera@gentoo.org> pydicom-0.9.8.ebuild, pydicom-9999.ebuild:
+ updated homepage
+
06 Apr 2015; <chymera@gentoo.org> pydicom-9999.ebuild:
no keywords in live ebuilds
diff --git a/sci-libs/pydicom/pydicom-0.9.8.ebuild b/sci-libs/pydicom/pydicom-0.9.8.ebuild
index c65f082..ad575a6 100644
--- a/sci-libs/pydicom/pydicom-0.9.8.ebuild
+++ b/sci-libs/pydicom/pydicom-0.9.8.ebuild
@@ -9,7 +9,7 @@ PYTHON_COMPAT=( python2_7 )
inherit distutils-r1
DESCRIPTION="A pure python package for parsing DICOM files"
-HOMEPAGE="https://code.google.com/p/pydicom/"
+HOMEPAGE="http://www.pydicom.org/"
SRC_URI="https://pydicom.googlecode.com/files/${P}.zip"
LICENSE="MIT"
diff --git a/sci-libs/pydicom/pydicom-9999.ebuild b/sci-libs/pydicom/pydicom-9999.ebuild
index fd90534..bc09e8c 100644
--- a/sci-libs/pydicom/pydicom-9999.ebuild
+++ b/sci-libs/pydicom/pydicom-9999.ebuild
@@ -9,7 +9,7 @@ PYTHON_COMPAT=( python2_7 python3_3 python3_4 )
inherit distutils-r1 git-r3
DESCRIPTION="A pure python package for parsing DICOM files"
-HOMEPAGE="https://code.google.com/p/pydicom/"
+HOMEPAGE="http://www.pydicom.org/"
SRC_URI=""
EGIT_REPO_URI="https://github.com/darcymason/pydicom"
next reply other threads:[~2015-05-25 23:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 23:02 Christoph Junghans [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-25 5:40 [gentoo-commits] proj/sci:master commit in: sci-libs/pydicom/ Horea Christian
2023-05-25 5:40 Horea Christian
2023-05-25 5:40 Horea Christian
2023-05-22 11:03 Horea Christian
2023-05-22 11:03 Horea Christian
2023-05-10 9:23 Horea Christian
2023-05-02 12:25 Andrew Ammerlaan
2023-05-02 12:15 Andrew Ammerlaan
2022-01-18 16:14 Horea Christian
2020-09-27 3:20 Horea Christian
2020-03-13 17:24 Horea Christian
2018-07-31 18:36 Horea Christian
2018-07-27 15:38 Horea Christian
2016-11-28 21:22 Marius Brehler
2015-09-07 6:49 Justin Lecher
2015-09-01 11:47 Justin Lecher
2015-05-25 23:02 Christoph Junghans
2015-05-25 23:02 Christoph Junghans
2015-05-25 23:02 Christoph Junghans
2015-05-25 23:02 Christoph Junghans
2015-05-25 23:02 Christoph Junghans
2015-05-25 23:02 Christoph Junghans
2014-01-06 19:58 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=1430734410.0cba5b2ddee2f6c20e2b5088e724fc5ade3bd46d.ottxor@gentoo \
--to=ottxor@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