public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/brython/
Date: Sun, 29 Oct 2017 17:29:38 +0000 (UTC)	[thread overview]
Message-ID: <1509298173.6756f97d289f9e2145a61760b7d09e10d095545e.slyfox@gentoo> (raw)

commit:     6756f97d289f9e2145a61760b7d09e10d095545e
Author:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 29 17:29:23 2017 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sun Oct 29 17:29:33 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6756f97d

dev-python/brython: stable 3.3.3 for ppc64, bug #634758

Package-Manager: Portage-2.3.13, Repoman-2.3.4
RepoMan-Options: --include-arches="ppc64"

 dev-python/brython/brython-3.3.3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/brython/brython-3.3.3.ebuild b/dev-python/brython/brython-3.3.3.ebuild
index c57083445a1..2ce53f2f211 100644
--- a/dev-python/brython/brython-3.3.3.ebuild
+++ b/dev-python/brython/brython-3.3.3.ebuild
@@ -12,7 +12,7 @@ HOMEPAGE="http://www.brython.info"
 SRC_URI="https://github.com/${PN}-dev/${PN}/archive/${PV}.zip -> ${P}.zip"
 
 LICENSE="BSD"
-KEYWORDS="~amd64 ppc ~ppc64 x86"
+KEYWORDS="~amd64 ppc ppc64 x86"
 
 REQUIRED_USE="${PYTHON_REQUIRED_USE}"
 


             reply	other threads:[~2017-10-29 17:29 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-29 17:29 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-08 10:20 [gentoo-commits] repo/gentoo:master commit in: dev-python/brython/ Pacho Ramos
2023-01-27 13:35 Arthur Zamarin
2022-10-24 19:10 Arthur Zamarin
2022-03-09 18:26 Arthur Zamarin
2021-05-17  7:49 Patrice Clement
2021-05-17  7:49 Patrice Clement
2020-07-01  6:17 Patrice Clement
2020-06-27 20:34 Patrice Clement
2020-06-27 20:34 Patrice Clement
2020-06-19 16:18 Patrice Clement
2019-08-10 18:06 Patrice Clement
2019-08-10 18:06 Patrice Clement
2019-08-10 18:06 Patrice Clement
2019-08-10 18:06 Patrice Clement
2019-06-01 21:56 Patrice Clement
2019-06-01 21:56 Patrice Clement
2019-06-01 21:56 Patrice Clement
2019-05-18 21:21 Patrice Clement
2019-04-16 15:35 Patrice Clement
2019-04-16 15:35 Patrice Clement
2019-04-16 15:35 Patrice Clement
2018-06-23 21:57 Patrice Clement
2018-06-12  8:46 Patrice Clement
2018-04-20 22:45 Patrice Clement
2018-04-20 22:45 Patrice Clement
2018-03-26 21:37 Patrice Clement
2018-03-14 22:08 Patrice Clement
2018-02-09 10:55 Patrice Clement
2018-02-01 23:08 Patrice Clement
2018-01-04 21:08 Patrice Clement
2017-12-04 22:12 Patrice Clement
2017-10-29 10:45 Sergei Trofimovich
2017-10-26 18:54 Thomas Deutschmann
2017-09-27 18:48 Patrice Clement
2017-09-27 18:48 Patrice Clement
2017-09-27 18:48 Patrice Clement
2017-05-25  8:44 Patrice Clement
2017-02-19 22:43 Patrice Clement
2017-02-19 22:43 Patrice Clement
2017-02-11 23:25 Patrice Clement
2016-12-04  0:47 Patrice Clement
2016-12-04  0:47 Patrice Clement
2016-12-04  0:47 Patrice Clement
2016-11-15 22:47 Patrice Clement
2016-07-17 15:44 Patrick Lauer
2016-06-13 18:44 Patrice Clement

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=1509298173.6756f97d289f9e2145a61760b7d09e10d095545e.slyfox@gentoo \
    --to=slyfox@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