In the meantime, python3-wrapt was recently built/pushed to testing. This command testing 3 newly created EPEL 10 packages is working insid an x86_64 centos 10 container:
Note that the positive karma does not re-enable auto-push to stable after negative karma disabled it. This update will need to be manually pushed to stable, or auto-push by karma and/or time will need to be manually re-enabled by @mfocko.
Either way, please ensure this reaches stable slightly after python-wrapt, so it doesn’t fail to install even briefly.
Ideally these would have been a multi-build update created from a side tag to begin with. If you want to, you could unpush this update, and I could unpush the python-wrapt update, and then I could tag both builds into a new side tag and create a combined update from that. I have done that before, and it works well. Just let me know if this is what you want.
@music I guess that's up to you, I have a newer release (new upstream release and there were also some changes to specfile by @carlwgeorge) that will supersede this update, I think I should(?) be able to build it in your side tag, if you create it?
I wonder if we could get @kkeithle to do the same for FEDORA-EPEL-2024-ce568eaa56, which depends on python-deprecated. Let’s get python-wrapt and python-deprecated set up first.
I’ll unpush python-wrapt, create a side tag, tag in the python-wrapt build, and follow up here.
I unpushed FEDORA-EPEL-2024-4bbcbd6c6d, then I requested an EPEL10 side tag (epel10.0-build-side-101152) and ran
$ koji tag epel10.0-build-side-101152 python-wrapt-1.17.0-2.el10_0
$ koji wait-repo epel10.0-build-side-101152 --build=python-wrapt-1.17.0-2.el10_0 --request
so python-wrapt is now available for other builds in the side tag.
You can now either unpush this update and run
$ koji tag epel10.0-build-side-101152 python-deprecated-1.2.14-7.el10_0
$ koji wait-repo epel10.0-build-side-101152 --build=python-deprecated-1.2.14-7.el10_0 --request
or you can build a later NVR of python-deprecated with fedpkg build --target=epel10.0-build-side-101152. You or someone else will still need to run the koji wai-repo … command on the resulting build before it‘s available for any other builds to use, since side-tag repo regeneration isn’t automatic anymore. In this case, with a newer python-deprecated build, I think creating a new update from the side tag should obsolete this update – although unpushing it doesn’t hurt.
This update has been submitted for testing by mfocko.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
This does not install. I've commented on the request bug with additional details.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
In the meantime, python3-wrapt was recently built/pushed to testing. This command testing 3 newly created EPEL 10 packages is working insid an x86_64 centos 10 container:
dnf install -y https://kojipkgs.fedoraproject.org//packages/python-wrapt/1.16.0/6.el10_0/x86_64/python3-wrapt-1.16.0-6.el10_0.x86_64.rpm https://kojipkgs.fedoraproject.org//packages/python-pikepdf/8.8.0/4.el10_0/x86_64/python3-pikepdf-8.8.0-4.el10_0.x86_64.rpm https://kojipkgs.fedoraproject.org//packages/python-deprecated/1.2.14/7.el10_0/noarch/python3-deprecated-1.2.14-7.el10_0.noarch.rpm
So adding a positif karma (while indeed it was not working initially).
Note that the positive karma does not re-enable auto-push to stable after negative karma disabled it. This update will need to be manually pushed to stable, or auto-push by karma and/or time will need to be manually re-enabled by @mfocko.
Either way, please ensure this reaches stable slightly after
python-wrapt, so it doesn’t fail to install even briefly.Ideally these would have been a multi-build update created from a side tag to begin with. If you want to, you could unpush this update, and I could unpush the
python-wraptupdate, and then I could tag both builds into a new side tag and create a combined update from that. I have done that before, and it works well. Just let me know if this is what you want.@music I guess that's up to you, I have a newer release (new upstream release and there were also some changes to specfile by @carlwgeorge) that will supersede this update, I think I should(?) be able to build it in your side tag, if you create it?
Ok, let’s do it.
I wonder if we could get @kkeithle to do the same for FEDORA-EPEL-2024-ce568eaa56, which depends on
python-deprecated. Let’s getpython-wraptandpython-deprecatedset up first.I’ll unpush
python-wrapt, create a side tag, tag in thepython-wraptbuild, and follow up here.I unpushed FEDORA-EPEL-2024-4bbcbd6c6d, then I requested an EPEL10 side tag (
epel10.0-build-side-101152) and ranso
python-wraptis now available for other builds in the side tag.You can now either unpush this update and run
or you can build a later NVR of
python-deprecatedwithfedpkg build --target=epel10.0-build-side-101152. You or someone else will still need to run thekoji wai-repo …command on the resulting build before it‘s available for any other builds to use, since side-tag repo regeneration isn’t automatic anymore. In this case, with a newerpython-deprecatedbuild, I think creating a new update from the side tag should obsolete this update – although unpushing it doesn’t hurt.Should be done: https://koji.fedoraproject.org/koji/repoinfo?repoID=6534226
This update has been unpushed.
Here’s the replacement update: FEDORA-EPEL-2024-2ce4c21cfc
I’ll try to coordinate getting
python-pikepdfadded to it as well.Thanks!