From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-admin/ansible-core/
Date: Mon, 16 Dec 2024 21:12:46 +0000 (UTC) [thread overview]
Message-ID: <1734383536.c794b742ee70bb74745229ac62a3e67ea84bf5f1.sam@gentoo> (raw)
commit: c794b742ee70bb74745229ac62a3e67ea84bf5f1
Author: idealseal <realidealseal <AT> protonmail <DOT> com>
AuthorDate: Mon Dec 16 17:34:52 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Dec 16 21:12:16 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c794b742
app-admin/ansible-core: fix resolvelib dependency requirement
With the 2.18.1 version bump I increased the upper version bound for
dev-python/resolvelib from <1.1.0 to <2.0.0, which was present in the
upstream devel branch but not in the 2.18.1 tag.
Closes: https://bugs.gentoo.org/946316
Signed-off-by: idealseal <realidealseal <AT> protonmail.com>
Closes: https://github.com/gentoo/gentoo/pull/39733
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../{ansible-core-2.18.1.ebuild => ansible-core-2.18.1-r1.ebuild} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-admin/ansible-core/ansible-core-2.18.1.ebuild b/app-admin/ansible-core/ansible-core-2.18.1-r1.ebuild
similarity index 96%
rename from app-admin/ansible-core/ansible-core-2.18.1.ebuild
rename to app-admin/ansible-core/ansible-core-2.18.1-r1.ebuild
index 85f243ef58dc..59a4cb8c1778 100644
--- a/app-admin/ansible-core/ansible-core-2.18.1.ebuild
+++ b/app-admin/ansible-core/ansible-core-2.18.1-r1.ebuild
@@ -38,7 +38,7 @@ RDEPEND="
dev-python/netaddr[${PYTHON_USEDEP}]
dev-python/pexpect[${PYTHON_USEDEP}]
>=dev-python/resolvelib-0.5.3[${PYTHON_USEDEP}]
- <dev-python/resolvelib-2.0.0[${PYTHON_USEDEP}]
+ <dev-python/resolvelib-1.1.0[${PYTHON_USEDEP}]
net-misc/sshpass
virtual/ssh
"
next reply other threads:[~2024-12-16 21:12 UTC|newest]
Thread overview: 129+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 21:12 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-04 20:23 [gentoo-commits] repo/gentoo:master commit in: app-admin/ansible-core/ Sam James
2025-04-26 2:36 Sam James
2025-04-26 1:57 Sam James
2025-03-25 4:36 Sam James
2025-03-25 4:36 Sam James
2025-03-25 4:36 Sam James
2025-03-25 4:36 Sam James
2025-01-11 11:25 Sam James
2025-01-11 11:25 Sam James
2025-01-11 8:51 Arthur Zamarin
2024-12-22 1:30 Sam James
2024-12-22 1:30 Sam James
2024-12-12 5:12 Sam James
2024-11-20 3:20 Matthew Thode
2024-10-12 11:22 Michał Górny
2024-07-20 19:22 Matthew Thode
2024-06-20 17:39 Matthew Thode
2024-05-26 15:03 Matthew Thode
2024-05-20 18:01 Matthew Thode
2024-04-26 14:01 Matthew Thode
2024-04-20 14:19 Matthew Thode
2024-03-26 19:08 Matthew Thode
2024-03-12 5:16 Sam James
2024-03-08 4:29 Matthew Thode
2024-02-28 1:01 Matthew Thode
2024-02-28 1:01 Matthew Thode
2024-02-28 1:01 Matthew Thode
2024-02-04 16:39 Matthew Thode
2024-02-04 16:39 Matthew Thode
2024-02-04 16:39 Matthew Thode
2024-01-13 0:17 Matthew Thode
2024-01-13 0:17 Matthew Thode
2024-01-13 0:17 Matthew Thode
2024-01-07 18:49 Matthew Thode
2024-01-07 18:49 Matthew Thode
2024-01-07 18:49 Matthew Thode
2024-01-04 20:58 Matthew Thode
2024-01-04 20:58 Matthew Thode
2024-01-04 20:58 Matthew Thode
2023-12-12 19:19 Matthew Thode
2023-12-12 19:19 Matthew Thode
2023-12-12 19:19 Matthew Thode
2023-12-10 16:24 Matthew Thode
2023-12-07 23:59 Matthew Thode
2023-12-07 23:59 Matthew Thode
2023-12-05 2:09 Matthew Thode
2023-12-05 2:09 Matthew Thode
2023-12-05 2:09 Matthew Thode
2023-11-13 21:42 Matthew Thode
2023-11-10 19:31 Matthew Thode
2023-11-10 19:31 Matthew Thode
2023-11-10 19:31 Matthew Thode
2023-11-10 19:31 Matthew Thode
2023-11-07 23:44 Matthew Thode
2023-10-13 19:51 Matthew Thode
2023-10-13 19:51 Matthew Thode
2023-10-13 19:51 Matthew Thode
2023-10-10 2:00 Matthew Thode
2023-10-10 2:00 Matthew Thode
2023-09-15 21:54 Matthew Thode
2023-09-15 21:54 Matthew Thode
2023-09-15 21:54 Matthew Thode
2023-09-15 21:54 Matthew Thode
2023-09-15 21:54 Matthew Thode
2023-09-13 2:12 Matthew Thode
2023-09-13 2:12 Matthew Thode
2023-08-18 18:02 Matthew Thode
2023-08-18 18:02 Matthew Thode
2023-08-15 16:25 Matthew Thode
2023-08-15 16:25 Matthew Thode
2023-07-24 12:49 Michał Górny
2023-07-18 18:11 Matthew Thode
2023-07-18 18:11 Matthew Thode
2023-07-16 15:54 Matthew Thode
2023-06-22 3:16 Matthew Thode
2023-06-22 3:16 Matthew Thode
2023-06-16 21:21 Matthew Thode
2023-05-29 20:27 Matthew Thode
2023-05-26 2:55 Matthew Thode
2023-05-23 18:13 Matthew Thode
2023-05-20 6:22 Michał Górny
2023-05-16 22:31 Matthew Thode
2023-04-28 17:11 Matthew Thode
2023-04-28 17:11 Matthew Thode
2023-04-25 18:24 Matthew Thode
2023-04-09 2:56 Matthew Thode
2023-04-08 12:29 Michał Górny
2023-03-28 21:17 Matthew Thode
2023-03-28 21:17 Matthew Thode
2023-03-28 21:15 Matthew Thode
2023-03-28 21:15 Matthew Thode
2023-03-28 21:15 Matthew Thode
2023-03-17 15:29 Michał Górny
2023-02-28 16:35 Matthew Thode
2023-02-07 9:29 Marek Szuba
2023-02-06 23:50 Matthew Thode
2023-02-06 22:50 Matthew Thode
2023-01-31 16:53 Matthew Thode
2023-01-10 14:50 Michał Górny
2023-01-10 14:50 Michał Górny
2023-01-07 19:34 Matthew Thode
2023-01-06 16:55 Matthew Thode
2023-01-06 16:38 Matthew Thode
2022-12-13 17:07 Matthew Thode
2022-12-07 19:19 Matthew Thode
2022-12-07 19:19 Matthew Thode
2022-12-07 19:17 Matthew Thode
2022-12-06 21:02 Matthew Thode
2022-11-18 21:58 Matthew Thode
2022-11-14 15:55 Matthew Thode
2022-11-14 15:55 Matthew Thode
2022-11-14 14:30 Matthew Thode
2022-11-14 14:30 Matthew Thode
2022-11-13 21:25 Matthew Thode
2022-11-13 21:25 Matthew Thode
2022-11-08 16:57 Matthew Thode
2022-11-08 16:57 Matthew Thode
2022-10-16 22:19 Matthew Thode
2022-10-16 22:19 Matthew Thode
2022-10-14 23:29 Matthew Thode
2022-10-14 23:29 Matthew Thode
2022-10-14 23:29 Matthew Thode
2022-09-23 19:19 Matthew Thode
2022-09-23 19:19 Matthew Thode
2022-09-16 16:22 Matthew Thode
2022-09-13 16:36 Matthew Thode
2022-09-02 10:52 Marek Szuba
2022-09-02 10:52 Marek Szuba
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=1734383536.c794b742ee70bb74745229ac62a3e67ea84bf5f1.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