public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-httpserver/
Date: Sun, 25 Dec 2022 16:42:19 +0000 (UTC)	[thread overview]
Message-ID: <1671986465.13057e2f4468a3a3c48054698d4e451f351d120e.sam@gentoo> (raw)

commit:     13057e2f4468a3a3c48054698d4e451f351d120e
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Dec 25 16:41:05 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Dec 25 16:41:05 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=13057e2f

dev-python/pytest-httpserver: Stabilize 1.0.6 ppc64, #888395

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-python/pytest-httpserver/pytest-httpserver-1.0.6.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/pytest-httpserver/pytest-httpserver-1.0.6.ebuild b/dev-python/pytest-httpserver/pytest-httpserver-1.0.6.ebuild
index 7150db56970c..c3ad62932109 100644
--- a/dev-python/pytest-httpserver/pytest-httpserver-1.0.6.ebuild
+++ b/dev-python/pytest-httpserver/pytest-httpserver-1.0.6.ebuild
@@ -20,7 +20,7 @@ SRC_URI="
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~m68k ~ppc ~ppc64 ~riscv ~s390 ~sparc x86"
+KEYWORDS="amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~m68k ~ppc ppc64 ~riscv ~s390 ~sparc x86"
 
 RDEPEND="
 	dev-python/werkzeug[${PYTHON_USEDEP}]


             reply	other threads:[~2022-12-25 16:42 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-25 16:42 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-31  9:21 [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-httpserver/ Michał Górny
2024-08-31  8:00 Arthur Zamarin
2024-08-12  2:50 Michał Górny
2024-08-10  7:31 Michał Górny
2024-08-03  6:37 Michał Górny
2024-08-03  6:24 Michał Górny
2024-07-22  1:47 Michał Górny
2024-07-20  5:09 Michał Górny
2024-07-06  9:42 Arthur Zamarin
2024-05-28  9:41 Michał Górny
2024-03-13 15:02 Michał Górny
2024-03-13 13:50 Arthur Zamarin
2024-02-25  4:07 Michał Górny
2024-02-14  7:26 Michał Górny
2023-06-18 17:13 Michał Górny
2023-06-18 14:47 Sam James
2023-05-29 12:00 Michał Górny
2023-05-23  5:07 Michał Górny
2023-05-17  3:40 Michał Górny
2023-02-13  3:25 Matt Turner
2022-12-25 20:20 Arthur Zamarin
2022-12-25 17:11 Arthur Zamarin
2022-12-25 17:03 Sam James
2022-12-25 17:03 Sam James
2022-12-25 16:50 Sam James
2022-11-30 10:18 WANG Xuerui
2022-11-27 14:48 James Le Cuirot
2022-11-18 12:01 Arthur Zamarin
2022-10-25 10:31 Michał Górny
2022-10-25  9:49 Sam James
2022-10-14  4:20 Arthur Zamarin
2022-10-14  4:20 Arthur Zamarin
2022-10-14  4:20 Arthur Zamarin
2022-10-14  4:19 Arthur Zamarin
2022-10-13  0:50 Yixun Lan
2022-10-12 18:56 Arthur Zamarin
2022-10-12 18:56 Arthur Zamarin
2022-10-12 18:56 Arthur Zamarin
2022-09-22 18:23 Michał Górny
2022-09-22 12:15 Michał Górny
2022-08-30 18:53 Michał Górny
2022-08-30 17:08 Jakov Smolić
2022-07-30 12:35 Arthur Zamarin
2022-07-29 18:02 Michał Górny
2022-06-07  9:39 Sam James
2022-06-07  9:39 Sam James
2022-06-01 12:04 Jakov Smolić
2022-05-31 21:59 Sam James
2022-05-31 11:20 Sam James

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=1671986465.13057e2f4468a3a3c48054698d4e451f351d120e.sam@gentoo \
    --to=sam@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