From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-admin/ansible-molecule/
Date: Thu, 25 Nov 2021 23:39:51 +0000 (UTC) [thread overview]
Message-ID: <1637883586.5bd606ba8960f63dd37bf058ab010979f07f16fe.marecki@gentoo> (raw)
commit: 5bd606ba8960f63dd37bf058ab010979f07f16fe
Author: Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Thu Nov 25 23:37:25 2021 +0000
Commit: Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Thu Nov 25 23:39:46 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5bd606ba
app-admin/ansible-molecule: support >=dev-python/pyyaml-6
All that upstream commit dcf82b067b0d4a1bfb5f1c478abd0d315b5e46e5,
(to be included in the next release) did was remove the version cap
in setup.cfg, and I have just confirmed that 3.5.2 builds, tests and
installs fine against pyyaml-6.0.
Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>
.../{ansible-molecule-3.5.2.ebuild => ansible-molecule-3.5.2-r1.ebuild} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-admin/ansible-molecule/ansible-molecule-3.5.2.ebuild b/app-admin/ansible-molecule/ansible-molecule-3.5.2-r1.ebuild
similarity index 98%
rename from app-admin/ansible-molecule/ansible-molecule-3.5.2.ebuild
rename to app-admin/ansible-molecule/ansible-molecule-3.5.2-r1.ebuild
index f55cd367c9ac..21dc93e1196d 100644
--- a/app-admin/ansible-molecule/ansible-molecule-3.5.2.ebuild
+++ b/app-admin/ansible-molecule/ansible-molecule-3.5.2-r1.ebuild
@@ -31,7 +31,7 @@ RDEPEND="$(python_gen_cond_dep '
dev-python/packaging[${PYTHON_USEDEP}]
<dev-python/paramiko-3[${PYTHON_USEDEP}]
<dev-python/pluggy-2.0[${PYTHON_USEDEP}]
- <dev-python/pyyaml-6[${PYTHON_USEDEP}]
+ >=dev-python/pyyaml-5.1[${PYTHON_USEDEP}]
>=dev-python/rich-9.5.1[${PYTHON_USEDEP}]
>=dev-python/subprocess-tee-0.3.5[${PYTHON_USEDEP}]
>=dev-util/cookiecutter-1.7.3[${PYTHON_USEDEP}]
next reply other threads:[~2021-11-25 23:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 23:39 Marek Szuba [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-03 5:07 [gentoo-commits] repo/gentoo:master commit in: app-admin/ansible-molecule/ Sam James
2025-09-16 13:32 Petr Vaněk
2025-08-26 15:26 Sam James
2025-07-30 7:38 Petr Vaněk
2025-07-04 20:00 Sam James
2025-06-08 12:13 Sam James
2025-06-08 12:13 Sam James
2025-03-25 4:36 Sam James
2025-03-25 4:36 Sam James
2025-03-01 7:54 Joonas Niilola
2025-02-22 9:20 Michał Górny
2024-12-12 5:12 Sam James
2024-04-30 1:35 Marek Szuba
2024-04-22 13:51 Marek Szuba
2023-10-23 21:03 Marek Szuba
2023-10-23 21:03 Marek Szuba
2023-08-21 13:46 Marek Szuba
2023-08-21 13:46 Marek Szuba
2023-07-08 0:52 Marek Szuba
2023-07-08 0:52 Marek Szuba
2023-05-11 21:44 Marek Szuba
2023-05-09 13:20 Marek Szuba
2023-04-10 10:39 Marek Szuba
2023-02-27 12:45 Marek Szuba
2023-02-24 21:19 Marek Szuba
2023-01-10 14:15 Michał Górny
2022-12-11 3:30 Michał Górny
2022-11-23 0:00 Marek Szuba
2022-10-28 17:59 Michał Górny
2022-09-21 12:18 Marek Szuba
2022-06-25 16:37 Jakov Smolić
2022-02-03 17:58 Marek Szuba
2021-11-26 10:20 Marek Szuba
2021-11-26 9:16 Marek Szuba
2021-11-25 23:39 Marek Szuba
2021-11-19 14:59 Marek Szuba
2021-06-14 12:39 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=1637883586.5bd606ba8960f63dd37bf058ab010979f07f16fe.marecki@gentoo \
--to=marecki@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