From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pycares/
Date: Mon, 06 Jan 2025 10:50:56 +0000 (UTC) [thread overview]
Message-ID: <1736160627.3b5021dd19379d2458a448e1e6bae2f43d9ff5b0.sam@gentoo> (raw)
commit: 3b5021dd19379d2458a448e1e6bae2f43d9ff5b0
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Jan 6 10:50:27 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Jan 6 10:50:27 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3b5021dd
dev-python/pycares: Stabilize 4.5.0 hppa, #946423
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/pycares/pycares-4.5.0.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-python/pycares/pycares-4.5.0.ebuild b/dev-python/pycares/pycares-4.5.0.ebuild
index 718bdd9bb397..d67ce305747d 100644
--- a/dev-python/pycares/pycares-4.5.0.ebuild
+++ b/dev-python/pycares/pycares-4.5.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2024 Gentoo Authors
+# Copyright 1999-2025 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
@@ -17,7 +17,7 @@ HOMEPAGE="
LICENSE="MIT"
SLOT="0"
-KEYWORDS="~alpha amd64 arm arm64 ~hppa ~loong ~mips ppc ppc64 ~riscv ~s390 sparc x86"
+KEYWORDS="~alpha amd64 arm arm64 hppa ~loong ~mips ppc ppc64 ~riscv ~s390 sparc x86"
IUSE="test"
# Tests fail with network-sandbox, since they try to resolve google.com
PROPERTIES="test_network"
next reply other threads:[~2025-01-06 10:51 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 10:50 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-06 11:46 [gentoo-commits] repo/gentoo:master commit in: dev-python/pycares/ Michał Górny
2024-12-16 7:51 Arthur Zamarin
2024-12-15 7:02 Sam James
2024-12-14 18:06 Zac Medico
2024-12-14 13:20 Arthur Zamarin
2024-12-14 12:47 Sam James
2024-12-14 11:49 Sam James
2024-12-14 11:49 Sam James
2024-12-14 10:58 Arthur Zamarin
2024-11-26 22:34 Zac Medico
2024-10-08 11:07 Sam James
2024-09-12 17:29 Arthur Zamarin
2024-09-12 8:01 Arthur Zamarin
2024-09-08 19:10 Arthur Zamarin
2024-09-07 14:16 Arthur Zamarin
2024-09-07 12:31 Jakov Smolić
2024-09-07 11:26 Jakov Smolić
2024-09-07 10:24 Arthur Zamarin
2024-08-29 14:28 Ionen Wolkens
2024-08-29 14:28 Ionen Wolkens
2024-08-29 14:28 Ionen Wolkens
2024-08-29 14:28 Ionen Wolkens
2024-08-24 6:41 Michał Górny
2024-08-05 10:36 Arthur Zamarin
2024-08-05 10:34 Jakov Smolić
2024-08-05 10:34 Jakov Smolić
2024-07-24 7:20 Sam James
2024-07-23 3:18 Michał Górny
2024-07-23 3:18 Michał Górny
2024-06-19 12:50 Petr Vaněk
2023-11-11 20:50 Michał Górny
2023-11-11 20:17 Arthur Zamarin
2023-10-07 4:43 Michał Górny
2023-05-29 6:23 Michał Górny
2023-05-29 6:23 Michał Górny
2023-05-04 16:22 Michał Górny
2023-01-12 6:14 Michał Górny
2023-01-11 21:40 Sam James
2022-12-12 15:33 Michał Górny
2022-09-11 5:31 Michał Górny
2022-09-10 22:57 Jakov Smolić
2022-08-09 17:58 Arthur Zamarin
2022-07-25 7:14 Michał Górny
2022-07-25 7:07 Agostino Sarubbo
2022-06-28 18:49 Arthur Zamarin
2022-06-22 7:50 Michał Górny
2022-04-24 18:44 Jakov Smolić
2021-11-21 20:11 Michał Górny
2021-11-21 19:28 Jakov Smolić
2021-10-18 20:40 Michał Górny
2021-06-15 5:40 Michał Górny
2021-06-15 5:25 Sam James
2021-05-19 8:12 Michał Górny
2021-05-15 20:48 Michał Górny
2021-05-14 8:14 Michał Górny
2021-05-11 19:23 Michał Górny
2021-05-11 19:23 Michał Górny
2021-01-03 9:12 Sam James
2020-07-20 0:22 Zac Medico
2020-05-30 19:48 Michał Górny
2020-03-28 17:21 Michał Górny
2020-01-10 6:19 Michał Górny
2020-01-10 6:19 Michał Górny
2019-12-14 8:44 Michał Górny
2019-10-18 6:17 Zac Medico
2019-07-15 13:56 Michał Górny
2019-07-15 13:36 Michał Górny
2019-07-15 13:36 Michał Górny
2018-01-15 0:16 Zac Medico
2018-01-14 23:53 Zac Medico
2017-02-13 8:22 Zac Medico
2016-11-07 18:34 Zac Medico
2016-09-18 22:40 Zac Medico
2016-09-18 22:34 Zac Medico
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=1736160627.3b5021dd19379d2458a448e1e6bae2f43d9ff5b0.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