From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-timeout/
Date: Wed, 4 Dec 2019 19:44:34 +0000 (UTC) [thread overview]
Message-ID: <1575488610.d2acca3042274af4ff2fdeb3b48e6d5707cc8591.slyfox@gentoo> (raw)
commit: d2acca3042274af4ff2fdeb3b48e6d5707cc8591
Author: Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Wed Dec 4 15:54:35 2019 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Wed Dec 4 19:43:30 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d2acca30
dev-python/pytest-timeout: keyworded 1.3.3 for hppa, bug #700918
Package-Manager: Portage-2.3.79, Repoman-2.3.16
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/pytest-timeout/pytest-timeout-1.3.3.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/pytest-timeout/pytest-timeout-1.3.3.ebuild b/dev-python/pytest-timeout/pytest-timeout-1.3.3.ebuild
index 36201824d5c..6f64383c972 100644
--- a/dev-python/pytest-timeout/pytest-timeout-1.3.3.ebuild
+++ b/dev-python/pytest-timeout/pytest-timeout-1.3.3.ebuild
@@ -13,7 +13,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
SLOT="0"
LICENSE="MIT"
-KEYWORDS="amd64 ~arm arm64 ~ppc ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 ~arm arm64 ~hppa ~ppc ~x86 ~amd64-linux ~x86-linux"
RDEPEND="dev-python/pytest[${PYTHON_USEDEP}]"
BDEPEND="dev-python/setuptools[${PYTHON_USEDEP}]"
next reply other threads:[~2019-12-04 19:44 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 19:44 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-15 11:30 [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-timeout/ Michał Górny
2024-05-09 16:48 Michał Górny
2024-03-23 10:45 Michał Górny
2024-03-23 10:41 Michał Górny
2024-03-08 5:40 Michał Górny
2023-11-11 20:36 Michał Górny
2023-11-11 19:21 Sam James
2023-10-10 7:13 Michał Górny
2023-10-10 7:13 Michał Górny
2023-10-08 17:48 Michał Górny
2023-05-23 18:36 Arthur Zamarin
2023-03-17 15:23 Michał Górny
2022-05-09 20:38 Michał Górny
2022-02-27 18:46 Michał Górny
2022-01-18 22:44 Michał Górny
2022-01-13 21:53 Michał Górny
2022-01-13 19:29 Arthur Zamarin
2021-12-14 10:21 Michał Górny
2021-11-13 9:26 Arthur Zamarin
2021-10-11 7:56 Michał Górny
2021-09-21 21:37 James Le Cuirot
2021-05-24 2:39 Joshua Kinard
2021-05-19 18:32 Michał Górny
2020-11-18 8:47 Michał Górny
2020-10-22 21:06 Michał Górny
2020-10-22 7:18 Sam James
2020-09-21 16:06 Michał Górny
2020-09-20 14:30 Michał Górny
2020-08-01 21:48 Michał Górny
2020-07-17 5:56 Michał Górny
2020-07-11 8:06 Michał Górny
2020-07-11 7:51 Michał Górny
2020-07-09 8:59 Agostino Sarubbo
2020-07-08 8:26 Michał Górny
2020-06-16 8:18 Michał Górny
2020-06-15 7:23 Michał Górny
2020-06-11 21:48 Sergei Trofimovich
2020-05-28 18:20 Sergei Trofimovich
2020-05-26 10:35 Michał Górny
2020-05-06 16:43 Mikle Kolyada
2020-05-05 22:13 Sergei Trofimovich
2020-04-29 11:03 Michał Górny
2020-04-18 14:25 Michał Górny
2020-04-08 14:01 Agostino Sarubbo
2020-04-07 7:03 Georgy Yakovlev
2020-03-28 18:49 Michał Górny
2020-03-16 5:54 Matt Turner
2020-03-14 16:33 Michał Górny
2020-03-08 10:46 Agostino Sarubbo
2020-03-08 10:37 Agostino Sarubbo
2020-03-08 10:25 Agostino Sarubbo
2020-02-06 21:11 Sergei Trofimovich
2019-12-02 21:13 Aaron Bauman
2019-04-28 8:15 Maxim Koltsov
2017-12-05 4:53 Tim Harder
2017-05-03 7:37 Michał Górny
2017-03-22 19:48 Markus Meier
2017-02-13 9:03 Zac Medico
2017-01-21 18:54 Agostino Sarubbo
2017-01-21 17:27 Agostino Sarubbo
2016-11-30 14:45 Lars Wendler
2016-06-29 18:49 Patrick Lauer
2015-10-15 9:21 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=1575488610.d2acca3042274af4ff2fdeb3b48e6d5707cc8591.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