From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pylast/
Date: Mon, 28 Sep 2020 17:41:05 +0000 (UTC) [thread overview]
Message-ID: <1601314848.36b819cee5d1e813c72f04b0f1a77c8465126260.slyfox@gentoo> (raw)
commit: 36b819cee5d1e813c72f04b0f1a77c8465126260
Author: Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Mon Sep 28 16:46:38 2020 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Mon Sep 28 17:40:48 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=36b819ce
dev-python/pylast: keyworded 3.3.0 for hppa, bug #736519
Package-Manager: Portage-3.0.4, Repoman-3.0.1
RepoMan-Options: --include-arches="hppa"
Signed-off-by: Rolf Eike Beer <eike <AT> sf-mail.de>
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
dev-python/pylast/pylast-3.3.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/pylast/pylast-3.3.0.ebuild b/dev-python/pylast/pylast-3.3.0.ebuild
index 1e952dd430f..18789b6de11 100644
--- a/dev-python/pylast/pylast-3.3.0.ebuild
+++ b/dev-python/pylast/pylast-3.3.0.ebuild
@@ -13,7 +13,7 @@ SRC_URI="https://github.com/${PN}/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="Apache-2.0"
SLOT="0"
-KEYWORDS="amd64 ~arm ~ia64 ~ppc ~ppc64 ~sparc x86"
+KEYWORDS="amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc x86"
RDEPEND="dev-python/six[${PYTHON_USEDEP}]"
BDEPEND="
next reply other threads:[~2020-09-28 17:41 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 17:41 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-08 9:02 [gentoo-commits] repo/gentoo:master commit in: dev-python/pylast/ Michał Górny
2024-06-08 6:24 Arthur Zamarin
2024-05-23 2:11 Michał Górny
2024-05-18 7:47 Michał Górny
2023-11-24 15:13 Arthur Zamarin
2023-07-10 1:47 Michał Górny
2023-07-09 16:51 Arthur Zamarin
2023-06-07 5:09 Michał Górny
2023-06-02 1:49 Sam James
2022-11-25 14:04 Michał Górny
2022-11-25 13:54 Arthur Zamarin
2022-10-25 20:30 Arthur Zamarin
2022-05-28 18:35 Arthur Zamarin
2022-05-15 10:41 Michał Górny
2022-05-15 8:19 Jakov Smolić
2022-04-09 19:36 Arthur Zamarin
2022-04-08 8:56 Michał Górny
2022-03-16 7:56 Michał Górny
2022-01-31 23:47 Michał Górny
2021-12-30 21:30 Michał Górny
2021-12-30 20:10 Arthur Zamarin
2021-12-09 22:51 Michał Górny
2021-12-09 22:01 Arthur Zamarin
2021-11-30 18:46 Michał Górny
2021-11-04 17:09 Sam James
2021-10-05 8:27 Michał Górny
2021-08-24 14:33 Marek Szuba
2021-06-05 21:18 Michał Górny
2021-06-05 20:35 Sam James
2021-05-25 16:05 Michał Górny
2021-05-01 7:45 Michał Górny
2021-04-18 7:05 Michał Górny
2021-04-18 1:41 Sam James
2021-03-14 22:10 Michał Górny
2021-03-02 8:53 Michał Górny
2021-03-02 4:37 Sam James
2021-01-12 12:04 Sam James
2021-01-07 12:47 Sam James
2021-01-05 9:17 Michał Górny
2020-11-23 16:39 Sergei Trofimovich
2020-11-15 7:54 Michał Górny
2020-11-15 7:54 Michał Górny
2020-11-15 5:28 Sam James
2020-11-12 15:29 Sam James
2020-11-04 10:42 Sergei Trofimovich
2020-10-07 18:37 Michał Górny
2020-09-18 15:30 Michał Górny
2020-09-13 9:19 Sam James
2020-09-08 19:11 Michał Górny
2020-08-31 4:52 Sam James
2020-08-30 5:32 Sam James
2020-08-14 8:16 Sergei Trofimovich
2020-08-10 19:25 Sergei Trofimovich
2020-08-09 16:56 Sergei Trofimovich
2020-08-09 13:10 Michał Górny
2020-08-09 13:10 Michał Górny
2020-08-01 21:23 Michał Górny
2020-05-09 7:48 Agostino Sarubbo
2020-05-09 7:40 Agostino Sarubbo
2020-05-02 0:08 Patrick McLean
2020-04-26 6:49 Michał Górny
2017-12-02 15:37 Mike Gilbert
2017-12-02 15:37 Mike Gilbert
2017-09-21 6:41 Tim Harder
2017-09-21 6:41 Tim Harder
2017-02-02 12:29 Manuel Rüger
2017-01-19 10:59 Agostino Sarubbo
2017-01-18 16:52 Agostino Sarubbo
2016-10-11 7:41 David Seifert
2016-05-29 19:03 Dirkjan Ochtman
2016-05-29 14:19 Pacho Ramos
2016-05-29 14:19 Pacho Ramos
2015-10-25 22:41 Michał Górny
2015-09-01 19:25 Tobias Klausmann
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=1601314848.36b819cee5d1e813c72f04b0f1a77c8465126260.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