From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/hyperframe/
Date: Thu, 1 Oct 2020 22:33:51 +0000 (UTC) [thread overview]
Message-ID: <1601591626.8aaf71ae2062d0a4a4f3c52b5df5e6e57f301070.slyfox@gentoo> (raw)
commit: 8aaf71ae2062d0a4a4f3c52b5df5e6e57f301070
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Thu Oct 1 22:31:51 2020 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Thu Oct 1 22:33:46 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8aaf71ae
dev-python/hyperframe: stable 6.0.0 for sparc
stable wrt bug #745972
Package-Manager: Portage-3.0.8, Repoman-3.0.1
RepoMan-Options: --include-arches="sparc"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
dev-python/hyperframe/hyperframe-6.0.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/hyperframe/hyperframe-6.0.0.ebuild b/dev-python/hyperframe/hyperframe-6.0.0.ebuild
index 7337c2d4dc4..f0fbcdb5b6a 100644
--- a/dev-python/hyperframe/hyperframe-6.0.0.ebuild
+++ b/dev-python/hyperframe/hyperframe-6.0.0.ebuild
@@ -14,6 +14,6 @@ SRC_URI="mirror://pypi/${P:0:1}/${PN}/${P}.tar.gz"
LICENSE="MIT"
SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~riscv ~s390 sparc ~x86"
distutils_enable_tests pytest
next reply other threads:[~2020-10-01 22:33 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 22:33 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-11 11:05 [gentoo-commits] repo/gentoo:master commit in: dev-python/hyperframe/ Michał Górny
2023-05-27 15:42 Sam James
2023-03-16 18:13 Michał Górny
2023-03-16 3:50 Michał Górny
2022-05-12 16:17 Michał Górny
2022-05-12 16:17 Michał Górny
2022-03-15 14:10 Michał Górny
2022-03-15 11:36 Jakov Smolić
2022-02-02 9:27 Michał Górny
2022-02-02 9:27 Michał Górny
2022-01-27 23:41 James Le Cuirot
2022-01-27 22:56 James Le Cuirot
2021-05-19 7:11 Michał Górny
2021-05-19 3:23 Sam James
2021-05-18 11:40 Michał Górny
2021-05-09 11:35 Michał Górny
2021-04-18 7:05 Michał Górny
2020-10-02 20:41 Sam James
2020-10-01 23:06 Sergei Trofimovich
2020-10-01 22:55 Sergei Trofimovich
2020-10-01 14:04 Michał Górny
2020-09-06 15:25 Michał Górny
2020-08-04 12:01 Michał Górny
2020-05-27 7:52 Michał Górny
2020-05-04 11:07 Michał Górny
2020-02-16 13:51 Sergei Trofimovich
2020-02-13 13:03 Agostino Sarubbo
2020-02-11 11:30 Agostino Sarubbo
2020-02-11 10:58 Agostino Sarubbo
2020-02-11 10:55 Agostino Sarubbo
2020-02-11 9:52 Agostino Sarubbo
2020-02-11 9:43 Agostino Sarubbo
2020-02-11 8:36 Agostino Sarubbo
2019-12-02 2:48 Aaron Bauman
2019-11-21 21:25 Michał Górny
2019-01-17 20:45 Mikle Kolyada
2019-01-05 17:19 Mikle Kolyada
2018-08-20 18:17 Sergei Trofimovich
2018-07-16 19:57 Michał Górny
2018-07-15 8:37 Michał Górny
2018-05-04 15:17 Mart Raudsepp
2018-04-06 5:23 Matt Turner
2018-03-30 18:08 Sergei Trofimovich
2018-02-22 17:02 Michał Górny
2018-01-04 20:35 Michał Górny
2017-12-13 22:15 Sergei Trofimovich
2017-12-13 22:15 Sergei Trofimovich
2017-10-28 22:34 Sergei Trofimovich
2017-09-28 13:42 Michael Palimaka
2017-07-02 15:02 Sergei Trofimovich
2017-07-02 15:02 Sergei Trofimovich
2017-06-28 13:19 Agostino Sarubbo
2017-06-26 20:18 Tobias Klausmann
2017-06-09 18:18 Brian Dolbec
2017-05-26 10:16 Tobias Klausmann
2017-03-29 1:43 Brian Dolbec
2017-03-22 19:48 Markus Meier
2017-03-12 12:30 Anthony G. Basile
2017-02-19 8:40 Markus Meier
2017-02-12 7:06 Zac Medico
2017-01-25 6:39 Jeroen Roovers
2016-10-22 1:26 Brian Dolbec
2016-10-07 18:11 Brian Dolbec
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=1601591626.8aaf71ae2062d0a4a4f3c52b5df5e6e57f301070.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