[EPEL-devel] Re: python311-dnf for el8 and el9
Thanks for the replies. I studied the implementation in python3.11-rpm, and I used that same technique to package python3.11-dnf for EPEL 8 and 9. https://copr.fedorainfracloud.org/coprs/ktdreyer/python3.11/ There's a tight dependency on libdnf in RHEL 8.8 and 9.2. I'll have to see how difficult this is to keep in sync with those RHEL packages. Also, thanks Troy for recently packaging python3.11-gpg for EPEL 9. I'd originally ported the python3-gpg 1.15.1 version from RHEL 9, but yours is newer (1.22.0), so I deleted my version. - Ken On Sun, Oct 8, 2023 at 11:01 AM Miro Hrončok wrote: > > 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@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Re: python311-dnf for el8 and el9
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@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Re: python311-dnf for el8 and el9
On Thu, Oct 5, 2023 at 3:52 PM 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!) Not recently. I looked at it way back in the EPEL 7 Python 3 stack days... I don't think it'd be too difficult to actually do, based on what Miro did for the python3-rpm package for EPEL. -- 真実はいつも一つ！/ Always, there's only one truth! ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
