From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/resolvelib/
Date: Sat, 16 Nov 2024 11:28:02 +0000 (UTC) [thread overview]
Message-ID: <1731756478.66d76caf4b0c989dea3bc9efa0217f8f941d0c54.arthurzam@gentoo> (raw)
commit: 66d76caf4b0c989dea3bc9efa0217f8f941d0c54
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 16 11:27:58 2024 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Nov 16 11:27:58 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=66d76caf
dev-python/resolvelib: Stabilize 1.1.0 ppc64, #943571
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
dev-python/resolvelib/resolvelib-1.1.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/resolvelib/resolvelib-1.1.0.ebuild b/dev-python/resolvelib/resolvelib-1.1.0.ebuild
index 82543f1d1301..1470b41f7286 100644
--- a/dev-python/resolvelib/resolvelib-1.1.0.ebuild
+++ b/dev-python/resolvelib/resolvelib-1.1.0.ebuild
@@ -21,7 +21,7 @@ SRC_URI="
LICENSE="ISC"
SLOT="0"
-KEYWORDS="~alpha amd64 arm arm64 ~hppa ~m68k ppc ~ppc64 ~riscv ~s390 ~sparc x86"
+KEYWORDS="~alpha amd64 arm arm64 ~hppa ~m68k ppc ppc64 ~riscv ~s390 ~sparc x86"
BDEPEND="
test? (
next reply other threads:[~2024-11-16 11:28 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 11:28 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-01 19:01 [gentoo-commits] repo/gentoo:master commit in: dev-python/resolvelib/ Arthur Zamarin
2025-02-16 20:33 Michał Górny
2025-01-06 3:47 WANG Xuerui
2025-01-04 17:30 Sam James
2024-11-30 19:29 Michał Górny
2024-11-16 10:41 Jakov Smolić
2024-11-16 9:47 Arthur Zamarin
2024-11-16 8:48 Arthur Zamarin
2024-11-16 8:09 Michał Górny
2024-11-16 8:09 Michał Górny
2024-10-31 5:24 Michał Górny
2024-10-25 12:09 Arthur Zamarin
2024-08-12 17:18 Arthur Zamarin
2024-07-27 11:58 Sam James
2024-07-27 9:28 Arthur Zamarin
2024-07-27 6:00 Michał Górny
2024-07-11 20:55 James Le Cuirot
2024-07-07 1:02 Ionen Wolkens
2024-07-05 19:41 Viorel Munteanu
2024-07-05 19:41 Viorel Munteanu
2024-06-24 0:13 Sam James
2024-06-23 16:20 Michał Górny
2023-10-27 18:20 Michał Górny
2023-07-24 12:49 Michał Górny
2023-04-08 12:29 Michał Górny
2023-04-08 11:13 Arthur Zamarin
2023-04-08 10:47 Arthur Zamarin
2023-04-08 8:01 Arthur Zamarin
2023-03-09 17:00 Michał Górny
2023-03-08 17:02 Michał Górny
2023-02-24 17:42 Michał Górny
2022-12-25 17:03 Sam James
2022-12-25 16:42 Sam James
2022-12-25 16:42 Sam James
2022-11-17 6:15 Michał Górny
2022-08-09 11:38 Marek Szuba
2022-03-15 9:41 Jakov Smolić
2022-01-31 22:27 Michał Górny
2021-11-17 7:30 Michał Górny
2021-11-17 2:16 Sam James
2021-11-13 21:09 Jakov Smolić
2021-11-13 12:51 Jakov Smolić
2021-10-12 6:18 Michał Górny
2021-10-08 19:47 Michał Górny
2021-09-09 0:16 Marek Szuba
2021-09-04 21:57 Michał Górny
2021-08-09 22:42 Louis Sautier
2021-08-09 22:42 Louis Sautier
2021-08-01 23:49 Sam James
2021-07-24 20:26 Matthew Thode
2021-07-08 7:11 Sergei Trofimovich
2021-07-06 17:59 Sam James
2021-07-06 17:59 Sam James
2021-06-25 7:10 Michał Górny
2021-06-25 7:10 Michał Górny
2021-06-15 15:18 Matthew Thode
2021-06-15 15:18 Matthew Thode
2021-06-14 14:36 Matthew Thode
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=1731756478.66d76caf4b0c989dea3bc9efa0217f8f941d0c54.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