From: "Agostino Sarubbo (ago)" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-python/pyspf: pyspf-2.0.10.ebuild ChangeLog
Date: Fri, 27 Mar 2015 16:26:31 +0000 (UTC) [thread overview]
Message-ID: <20150327162631.DC9F614A84@oystercatcher.gentoo.org> (raw)
ago 15/03/27 16:26:31
Modified: pyspf-2.0.10.ebuild ChangeLog
Log:
Stable for amd64, wrt bug #537634
(Portage version: 2.2.14/cvs/Linux x86_64, RepoMan options: --include-arches="amd64", signed Manifest commit with key 7194459F)
Revision Changes Path
1.2 dev-python/pyspf/pyspf-2.0.10.ebuild
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/pyspf/pyspf-2.0.10.ebuild?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/pyspf/pyspf-2.0.10.ebuild?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/pyspf/pyspf-2.0.10.ebuild?r1=1.1&r2=1.2
Index: pyspf-2.0.10.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-python/pyspf/pyspf-2.0.10.ebuild,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- pyspf-2.0.10.ebuild 29 Sep 2014 04:14:37 -0000 1.1
+++ pyspf-2.0.10.ebuild 27 Mar 2015 16:26:31 -0000 1.2
@@ -1,6 +1,6 @@
-# Copyright 1999-2014 Gentoo Foundation
+# Copyright 1999-2015 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/dev-python/pyspf/pyspf-2.0.10.ebuild,v 1.1 2014/09/29 04:14:37 idella4 Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-python/pyspf/pyspf-2.0.10.ebuild,v 1.2 2015/03/27 16:26:31 ago Exp $
EAPI="5"
@@ -14,7 +14,7 @@
LICENSE="PSF-2"
SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 ~x86"
IUSE="ipv6 test"
# >=python-3.3 comes with the built-in ipaddress module
1.30 dev-python/pyspf/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/pyspf/ChangeLog?rev=1.30&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/pyspf/ChangeLog?rev=1.30&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/pyspf/ChangeLog?r1=1.29&r2=1.30
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-python/pyspf/ChangeLog,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- ChangeLog 25 Jan 2015 09:31:11 -0000 1.29
+++ ChangeLog 27 Mar 2015 16:26:31 -0000 1.30
@@ -1,6 +1,9 @@
# ChangeLog for dev-python/pyspf
# Copyright 1999-2015 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-python/pyspf/ChangeLog,v 1.29 2015/01/25 09:31:11 idella4 Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-python/pyspf/ChangeLog,v 1.30 2015/03/27 16:26:31 ago Exp $
+
+ 27 Mar 2015; Agostino Sarubbo <ago@gentoo.org> pyspf-2.0.10.ebuild:
+ Stable for amd64, wrt bug #537634
*pyspf-2.0.11 (25 Jan 2015)
next reply other threads:[~2015-03-27 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 16:26 Agostino Sarubbo (ago) [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-28 11:33 [gentoo-commits] gentoo-x86 commit in dev-python/pyspf: pyspf-2.0.10.ebuild ChangeLog Mikle Kolyada (zlogene)
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=20150327162631.DC9F614A84@oystercatcher.gentoo.org \
--to=ago@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