From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-localserver/
Date: Tue, 21 Jun 2022 18:35:36 +0000 (UTC) [thread overview]
Message-ID: <1655836526.885b09f0daa013edaa29c13f18c4e189d1e24172.arthurzam@gentoo> (raw)
commit: 885b09f0daa013edaa29c13f18c4e189d1e24172
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Tue Jun 21 18:35:26 2022 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Tue Jun 21 18:35:26 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=885b09f0
dev-python/pytest-localserver: Stabilize 0.6.0-r1 ALLARCHES, #853433
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
dev-python/pytest-localserver/pytest-localserver-0.6.0-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/pytest-localserver/pytest-localserver-0.6.0-r1.ebuild b/dev-python/pytest-localserver/pytest-localserver-0.6.0-r1.ebuild
index 443ad40828f9..87ee974827cc 100644
--- a/dev-python/pytest-localserver/pytest-localserver-0.6.0-r1.ebuild
+++ b/dev-python/pytest-localserver/pytest-localserver-0.6.0-r1.ebuild
@@ -14,7 +14,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
LICENSE="MIT"
SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~x64-macos"
+KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~m68k ppc ppc64 ~riscv ~s390 sparc x86 ~x64-macos"
RDEPEND="
>=dev-python/werkzeug-0.10[${PYTHON_USEDEP}]
next reply other threads:[~2022-06-21 18:35 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 18:35 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-26 13:07 [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-localserver/ Michał Górny
2024-10-26 12:48 Arthur Zamarin
2024-10-07 4:43 Michał Górny
2024-09-07 11:12 Michał Górny
2024-09-07 10:58 Michał Górny
2024-08-18 6:04 Michał Górny
2024-05-28 9:41 Michał Górny
2023-11-11 20:36 Michał Górny
2023-11-11 20:02 Sam James
2023-10-12 4:39 Michał Górny
2023-08-19 18:19 Michał Górny
2023-08-19 17:53 Arthur Zamarin
2023-07-16 2:55 Michał Górny
2023-06-01 17:20 Michał Górny
2023-03-03 17:48 Michał Górny
2023-03-03 17:48 Michał Górny
2023-03-03 17:37 Arthur Zamarin
2023-01-30 6:59 Michał Górny
2022-10-03 6:36 Michał Górny
2022-10-02 19:22 Arthur Zamarin
2022-09-01 19:42 Arthur Zamarin
2022-09-01 19:42 Arthur Zamarin
2022-06-21 18:48 Arthur Zamarin
2022-05-21 7:36 Michał Górny
2022-05-14 3:16 Sam James
2022-05-06 8:18 Michał Górny
2022-04-25 19:00 Sam James
2021-12-19 21:05 Arthur Zamarin
2021-11-19 9:03 Michał Górny
2021-09-21 22:29 James Le Cuirot
2020-11-28 14:21 Sam James
2020-09-21 16:06 Michał Górny
2020-07-25 8:31 Michał Górny
2020-07-14 15:57 Sam James
2020-07-14 13:19 Sam James
2020-07-11 7:51 Michał Górny
2020-07-11 7:51 Michał Górny
2020-07-09 8:59 Agostino Sarubbo
2020-07-09 7:06 Sergei Trofimovich
2020-07-05 9:27 Sergei Trofimovich
2020-07-02 17:05 Sergei Trofimovich
2020-07-01 12:21 Michał Górny
2020-05-31 10:04 Sergei Trofimovich
2020-05-31 10:04 Sergei Trofimovich
2020-05-30 14:37 Michał Górny
2020-05-30 14:37 Michał Górny
2020-05-30 11:51 Michał Górny
2020-05-30 11:51 Michał Górny
2020-05-27 20:45 Michał Górny
2020-05-04 11:44 Michał Górny
2020-04-26 15:29 Agostino Sarubbo
2020-04-26 14:16 Agostino Sarubbo
2020-04-26 10:17 Michał Górny
2020-03-17 2:09 Matt Turner
2020-03-14 16:33 Michał Górny
2020-02-05 21:22 Sergei Trofimovich
2019-12-04 3:14 Patrick McLean
2019-12-04 1:36 Patrick McLean
2019-11-21 2:02 Patrick McLean
2017-09-30 0:31 Matt Thode
2017-07-23 11:40 Manuel Rüger
2017-06-26 11:04 Alexis Ballier
2017-05-13 6:31 Markus Meier
2017-05-04 2:34 Zac Medico
2017-05-02 16:41 Michał Górny
2017-05-01 14:56 Michał Górny
2017-05-01 14:56 Michał Górny
2017-04-04 17:24 Manuel Rüger
2016-08-31 13:25 Manuel Rüger
2016-01-23 12:23 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=1655836526.885b09f0daa013edaa29c13f18c4e189d1e24172.arthurzam@gentoo \
--to=arthurzam@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