From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/zope-component/
Date: Sat, 28 May 2022 06:58:04 +0000 (UTC) [thread overview]
Message-ID: <1653721078.e79f5114ece01387b6dbafe8b9ff68e931c0f38a.ago@gentoo> (raw)
commit: e79f5114ece01387b6dbafe8b9ff68e931c0f38a
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Sat May 28 06:57:58 2022 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Sat May 28 06:57:58 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e79f5114
dev-python/zope-component: arm64 stable wrt bug #847775
Package-Manager: Portage-3.0.30, Repoman-3.0.3
RepoMan-Options: --include-arches="arm64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
dev-python/zope-component/zope-component-5.0.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/zope-component/zope-component-5.0.1.ebuild b/dev-python/zope-component/zope-component-5.0.1.ebuild
index 8b0a285c9213..09ddc2bc5776 100644
--- a/dev-python/zope-component/zope-component-5.0.1.ebuild
+++ b/dev-python/zope-component/zope-component-5.0.1.ebuild
@@ -20,7 +20,7 @@ S=${WORKDIR}/${MY_P}
LICENSE="ZPL"
SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 ~ppc64 ~riscv"
+KEYWORDS="amd64 ~arm arm64 ~ppc64 ~riscv"
RDEPEND="
dev-python/zope-event[${PYTHON_USEDEP}]
next reply other threads:[~2022-05-28 6:58 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 6:58 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-18 15:56 [gentoo-commits] repo/gentoo:master commit in: dev-python/zope-component/ Michał Górny
2023-06-06 6:13 Michał Górny
2023-05-04 17:44 Michał Górny
2023-05-04 17:22 Arthur Zamarin
2023-04-15 8:23 Michał Górny
2023-03-21 6:49 Michał Górny
2023-03-17 18:28 Michał Górny
2023-02-17 6:21 Michał Górny
2023-02-16 22:50 Sam James
2023-01-04 14:15 Michał Górny
2023-01-04 12:24 Michał Górny
2023-01-04 6:24 Sam James
2022-11-09 6:53 Sam James
2022-06-07 23:12 Sam James
2022-05-27 9:12 Jakov Smolić
2022-05-13 10:49 Jakov Smolić
2022-05-13 8:55 Jakov Smolić
2022-04-25 6:29 Jakov Smolić
2022-04-24 17:47 Arthur Zamarin
2022-04-23 19:07 Michał Górny
2022-04-22 15:35 Michał Górny
2022-04-22 15:35 Michał Górny
2022-04-22 15:11 Arthur Zamarin
2022-04-22 15:11 Arthur Zamarin
2022-04-22 15:11 Arthur Zamarin
2022-04-11 19:58 Michał Górny
2022-04-09 21:47 Jakov Smolić
2022-04-09 20:23 Michał Górny
2022-04-09 18:56 Michał Górny
2021-06-22 17:02 Marek Szuba
2021-05-31 12:09 Michał Górny
2021-03-02 8:40 Sam James
2020-12-04 12:38 Michał Górny
2020-12-03 17:31 Michał Górny
2020-10-09 7:15 Michał Górny
2020-08-02 9:33 Michał Górny
2020-05-04 12:34 Michał Górny
2020-03-08 14:29 Michał Górny
2019-06-16 6:59 Matthew Thode
2019-05-16 16:00 Matthew Thode
2018-03-17 21:41 Michał Górny
2018-01-06 13:39 Michał Górny
2017-09-30 0:01 Tim Harder
2017-09-17 21:09 Matt Turner
2017-09-13 15:05 Fabian Groffen
2017-08-28 20:44 Alexis Ballier
2017-08-20 4:06 Tim Harder
2017-07-23 11:40 Manuel Rüger
2017-07-15 17:25 Tobias Klausmann
2017-05-07 18:43 Michał Górny
2017-05-02 17:43 Michał Górny
2017-04-28 18:32 Manuel Rüger
2016-08-31 12:35 Manuel Rüger
2015-12-01 20:52 Manuel Rüger
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=1653721078.e79f5114ece01387b6dbafe8b9ff68e931c0f38a.ago@gentoo \
--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