public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Georgy Yakovlev" <gyakovlev@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/zc-lockfile/
Date: Thu, 12 Dec 2019 02:19:46 +0000 (UTC)	[thread overview]
Message-ID: <1576117162.8bed8cc291e583123befb9d1f8eab142552c1f39.gyakovlev@gentoo> (raw)

commit:     8bed8cc291e583123befb9d1f8eab142552c1f39
Author:     Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
AuthorDate: Thu Dec 12 01:32:57 2019 +0000
Commit:     Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
CommitDate: Thu Dec 12 02:19:22 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8bed8cc2

dev-python/zc-lockfile: keyword on ~ppc64

Package-Manager: Portage-2.3.81, Repoman-2.3.20
Signed-off-by: Georgy Yakovlev <gyakovlev <AT> gentoo.org>

 dev-python/zc-lockfile/zc-lockfile-2.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/zc-lockfile/zc-lockfile-2.0.ebuild b/dev-python/zc-lockfile/zc-lockfile-2.0.ebuild
index de837754651..44e20f6b9d0 100644
--- a/dev-python/zc-lockfile/zc-lockfile-2.0.ebuild
+++ b/dev-python/zc-lockfile/zc-lockfile-2.0.ebuild
@@ -15,7 +15,7 @@ SRC_URI="mirror://pypi/${MY_PN:0:1}/${MY_PN}/${MY_P}.tar.gz"
 
 LICENSE="ZPL"
 SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~hppa ~sparc"
+KEYWORDS="~amd64 ~arm64 ~hppa ~ppc64 ~sparc"
 IUSE="test"
 
 RDEPEND=">=dev-python/setuptools-3.3[${PYTHON_USEDEP}]"


             reply	other threads:[~2019-12-12  2:19 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12  2:19 Georgy Yakovlev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-01 19:01 [gentoo-commits] repo/gentoo:master commit in: dev-python/zc-lockfile/ Arthur Zamarin
2025-02-16 20:33 Michał Górny
2025-01-04 15:08 Sam James
2024-11-30 16:43 Michał Górny
2024-10-25 12:09 Arthur Zamarin
2024-07-11 20:55 James Le Cuirot
2024-06-15  4:22 Michał Górny
2023-10-20 14:49 Michał Górny
2023-03-28  4:26 Michał Górny
2023-03-27 19:31 Sam James
2023-03-27 19:31 Sam James
2023-03-27 17:58 Arthur Zamarin
2023-03-27 17:58 Arthur Zamarin
2023-03-27 17:58 Arthur Zamarin
2023-03-27 17:58 Arthur Zamarin
2023-03-21  6:49 Michał Górny
2023-03-01  6:16 Michał Górny
2023-03-01  6:16 Michał Górny
2023-02-24  6:00 Michał Górny
2023-01-03  2:53 WANG Xuerui
2022-10-22 14:54 Michał Górny
2022-06-22 12:01 Michał Górny
2022-06-22 10:16 Agostino Sarubbo
2022-06-22 10:13 Agostino Sarubbo
2022-06-22 10:10 Agostino Sarubbo
2022-06-21 19:26 Arthur Zamarin
2022-06-21 18:37 Arthur Zamarin
2022-05-22  9:25 Michał Górny
2022-05-22  9:25 Michał Górny
2021-09-02 22:57 Marek Szuba
2021-06-05 18:44 Michał Górny
2020-07-13 23:13 Sam James
2020-06-22 19:05 Mart Raudsepp
2020-06-21 11:18 Michał Górny
2020-06-21 11:18 Michał Górny
2020-06-20 14:20 Thomas Deutschmann
2020-05-30 20:33 Sergei Trofimovich
2020-05-30 16:20 Michał Górny
2020-05-16 11:25 Mikle Kolyada
2020-03-29 12:22 Michał Górny
2020-03-17  2:09 Matt Turner
2020-02-06  7:10 Michał Górny
2020-01-28 10:20 Agostino Sarubbo
2019-12-04 19:44 Sergei Trofimovich
2019-11-22  0:20 Patrick McLean
2019-04-17 18:07 Aaron Bauman
2019-03-10  2:38 William Hubbs
2019-03-08 22:05 William Hubbs

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=1576117162.8bed8cc291e583123befb9d1f8eab142552c1f39.gyakovlev@gentoo \
    --to=gyakovlev@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