On 05. 10. 23 21:52, Ken Dreyer wrote:
Hi folks,
I have some Python apps that "import dnf". I wanted to run these on
the parallel Python versions in RHEL 8 and 9, but there's no
python311-dnf library available.
I haven't looked into this yet. Has anyone else looked at it?
I think I'll need something like
https://src.fedoraproject.org/rpms/python3-rpm/c/966f38637a7f51376e57b7aeb19a872986a39b8a
, but for a "python3-dnf" package?
(By the way, thanks Python team for python3.11 in RHEL 8 and 9. That
is helpful for moving workloads across RHEL versions and helping the
Python ecosystem move forward. And thank you Miro for python311-rpm!)
Hello.
Packaging python3.11-dnf for EPEL 8 and 9 should be trivial,
but it's not a single package.
$ repoquery -q --repo=c9s-baseos --requires python3-dnf --latest=1 | grep python
/usr/bin/python3.9
python(abi) = 3.9
python3-gpg
python3-hawkey >= 0.66.0
python3-libcomps >= 0.1.8
python3-libdnf
python3-libdnf >= 0.66.0
python3-rpm >= 4.14.0
We would need to package (at least) 4 packages:
python3.11-gpg (gpgme)
python3.11-hawkey and python3.11-libdnf (libdnf)
python3.11-libcomps (libcomps)
python3.11-dnf (dnf)
There's also a possible usage of the gi.Modulemd module from libmodulemd , but
I've only been able to grep that in tests :/
Reproducing the approach from python3-rpm should work, but I haven't tried it.
I am not able to commit myself to maintaining the dnf stack in EPEL for couple
years.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
