From: "Pacho Ramos (pacho)" <pacho@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-python/blaze: blaze-0.7.1.ebuild ChangeLog
Date: Sun, 8 Mar 2015 23:40:35 +0000 (UTC) [thread overview]
Message-ID: <20150308234035.7308C1356E@oystercatcher.gentoo.org> (raw)
pacho 15/03/08 23:40:35
Modified: blaze-0.7.1.ebuild ChangeLog
Log:
x86 stable, bug 540290
(Portage version: 2.2.17/cvs/Linux x86_64, RepoMan options: --include-arches="x86", signed Manifest commit with key A188FBD4)
Revision Changes Path
1.3 dev-python/blaze/blaze-0.7.1.ebuild
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/blaze/blaze-0.7.1.ebuild?rev=1.3&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/blaze/blaze-0.7.1.ebuild?rev=1.3&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/blaze/blaze-0.7.1.ebuild?r1=1.2&r2=1.3
Index: blaze-0.7.1.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-python/blaze/blaze-0.7.1.ebuild,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- blaze-0.7.1.ebuild 6 Mar 2015 22:09:48 -0000 1.2
+++ blaze-0.7.1.ebuild 8 Mar 2015 23:40:35 -0000 1.3
@@ -1,6 +1,6 @@
# Copyright 1999-2015 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/dev-python/blaze/blaze-0.7.1.ebuild,v 1.2 2015/03/06 22:09:48 pacho Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-python/blaze/blaze-0.7.1.ebuild,v 1.3 2015/03/08 23:40:35 pacho Exp $
EAPI=5
@@ -17,7 +17,7 @@
LICENSE="BSD"
SLOT="0"
-KEYWORDS="amd64 ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 x86 ~amd64-linux ~x86-linux"
# Currently doc build fails, reason unclear but appears it's tied to use of
# redhat's anaconda installer, seemingly hostile to gentoo.
1.17 dev-python/blaze/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/blaze/ChangeLog?rev=1.17&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/blaze/ChangeLog?rev=1.17&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/blaze/ChangeLog?r1=1.16&r2=1.17
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-python/blaze/ChangeLog,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- ChangeLog 6 Mar 2015 22:09:48 -0000 1.16
+++ ChangeLog 8 Mar 2015 23:40:35 -0000 1.17
@@ -1,6 +1,9 @@
# ChangeLog for dev-python/blaze
# Copyright 1999-2015 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-python/blaze/ChangeLog,v 1.16 2015/03/06 22:09:48 pacho Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-python/blaze/ChangeLog,v 1.17 2015/03/08 23:40:35 pacho Exp $
+
+ 08 Mar 2015; Pacho Ramos <pacho@gentoo.org> blaze-0.7.1.ebuild:
+ x86 stable, bug 540290
06 Mar 2015; Pacho Ramos <pacho@gentoo.org> blaze-0.7.1.ebuild:
amd64 stable, bug 540290
next reply other threads:[~2015-03-08 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 23:40 Pacho Ramos (pacho) [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-06 22:09 [gentoo-commits] gentoo-x86 commit in dev-python/blaze: blaze-0.7.1.ebuild ChangeLog Pacho Ramos (pacho)
2015-01-26 5:28 Patrick Lauer (patrick)
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=20150308234035.7308C1356E@oystercatcher.gentoo.org \
--to=pacho@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