From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pkginfo/
Date: Thu, 6 Feb 2020 21:11:26 +0000 (UTC) [thread overview]
Message-ID: <1581023467.bc84ea209745e7011538cde0d529eb53cef8981c.slyfox@gentoo> (raw)
commit: bc84ea209745e7011538cde0d529eb53cef8981c
Author: Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Thu Feb 6 20:26:28 2020 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Thu Feb 6 21:11:07 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bc84ea20
dev-python/pkginfo: keyworded 1.5.0.1 for hppa/sparc, bug #700918
Package-Manager: Portage-2.3.84, Repoman-2.3.20
RepoMan-Options: --include-arches="hppa sparc"
Signed-off-by: Rolf Eike Beer <eike <AT> sf-mail.de>
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
dev-python/pkginfo/pkginfo-1.5.0.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/pkginfo/pkginfo-1.5.0.1.ebuild b/dev-python/pkginfo/pkginfo-1.5.0.1.ebuild
index 185725f2577..d7bd3378bd4 100644
--- a/dev-python/pkginfo/pkginfo-1.5.0.1.ebuild
+++ b/dev-python/pkginfo/pkginfo-1.5.0.1.ebuild
@@ -13,7 +13,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
LICENSE="MIT"
SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 ~ppc ~ppc64 x86"
+KEYWORDS="amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~sparc x86"
IUSE="doc"
RDEPEND="dev-python/setuptools[${PYTHON_USEDEP}]"
next reply other threads:[~2020-02-06 21:11 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 21:11 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-21 11:30 [gentoo-commits] repo/gentoo:master commit in: dev-python/pkginfo/ Michał Górny
2024-12-21 11:17 Michał Górny
2024-12-03 4:26 Michał Górny
2024-12-03 4:26 Michał Górny
2024-10-26 13:36 Michał Górny
2024-10-26 13:28 Arthur Zamarin
2024-10-10 18:25 Michał Górny
2024-06-29 16:58 Michał Górny
2024-06-29 7:57 Arthur Zamarin
2024-06-09 3:17 Michał Górny
2024-06-01 3:57 Michał Górny
2024-05-29 19:47 Petr Vaněk
2024-03-22 4:38 Michał Górny
2024-03-21 18:22 Arthur Zamarin
2024-03-04 6:31 Michał Górny
2023-06-01 4:13 Michał Górny
2023-02-16 20:26 Michał Górny
2023-01-09 8:09 Michał Górny
2023-01-07 4:54 Michał Górny
2023-01-06 5:35 Michał Górny
2023-01-04 14:15 Michał Górny
2022-12-31 10:55 Michał Górny
2022-12-31 10:41 Arthur Zamarin
2022-12-01 7:09 Michał Górny
2022-11-29 19:46 Arthur Zamarin
2022-11-29 19:46 Arthur Zamarin
2022-06-24 10:21 Michał Górny
2022-06-24 9:00 Arthur Zamarin
2022-06-08 19:40 Michał Górny
2022-05-24 6:16 Michał Górny
2022-05-24 6:16 Michał Górny
2022-04-25 16:50 Sam James
2022-01-01 18:48 Michał Górny
2022-01-01 17:51 Arthur Zamarin
2021-12-02 8:12 Michał Górny
2021-12-02 8:12 Michał Górny
2021-12-01 22:24 Michał Górny
2021-12-01 19:14 Michał Górny
2021-08-16 6:13 Michał Górny
2021-07-12 23:53 Marek Szuba
2021-07-10 7:34 Michał Górny
2021-05-07 11:58 Michał Górny
2021-02-19 8:58 Michał Górny
2021-02-19 2:54 Sam James
2021-01-17 9:02 Michał Górny
2020-12-31 6:07 Sam James
2020-11-28 13:41 Sam James
2020-09-20 9:36 Michał Górny
2020-07-05 9:27 Sergei Trofimovich
2020-07-02 17:05 Sergei Trofimovich
2020-05-31 10:04 Sergei Trofimovich
2020-05-26 20:03 Michał Górny
2020-03-28 11:59 Michał Górny
2020-03-28 11:59 Michał Górny
2020-03-28 11:59 Michał Górny
2020-03-28 11:59 Michał Górny
2020-03-20 9:58 David Seifert
2020-03-17 2:09 Matt Turner
2020-02-03 11:31 Agostino Sarubbo
2020-01-31 13:45 Agostino Sarubbo
2019-12-10 19:25 Sergei Trofimovich
2019-12-09 20:06 Sergei Trofimovich
2019-12-04 22:28 Patrick McLean
2018-03-24 7:58 Tim Harder
2017-08-15 5:41 Alexis Ballier
2017-07-09 12:06 Benda XU
2017-05-16 12:02 Manuel Rüger
2017-03-10 7:05 Zac Medico
2016-05-29 14:19 Pacho Ramos
2015-10-27 15:20 Agostino Sarubbo
2015-10-19 16:29 Justin Lecher
2015-10-15 12:01 Justin Lecher
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=1581023467.bc84ea209745e7011538cde0d529eb53cef8981c.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