Would it perhaps be better to use COPR for testing so that people need to opt-in to these RCs (also on rawhide where it seems we're using Fedora as a CI system with a new build every 2 hours? https://bodhi.fedoraproject.org/updates/?packages=podman)
At the moment, even if these updates do not make it to the stable updates repositories (some of the broken ones like the skopeo update made it there even: https://bodhi.fedoraproject.org/updates/FEDORA-2020-cd7e382e0c). us folks that test the updates-testing repos are still getting them and seeing broken systems. The function of the updates-testing repositories is to test stable updates before they get to users, not to test rcs which are not intended for users in the first place, right?
A much better system would be to use copr (which has excellent scm integration) for all of these snapshots and only push stable versions of these tools to Fedora. That allows people to opt-in as opposed to the current system where I need to modify my repo files to opt out from these rcs. The other option is that I stop testing updates.
This update has been submitted for testing by lsm5.
This update's test gating status has been changed to 'waiting'.
This update has obsoleted podman-2.0.0-rc4.1.fc32, and has inherited its bugs and notes.
This update's test gating status has been changed to 'failed'.
This update has been pushed to testing.
This update's test gating status has been changed to 'ignored'.
I am going to give this negative karma just to make sure it does not get released, since this is a release candidate.
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.
dwalsh edited this update.
LGTM - passes gating tests (manually invoked, since Fedora CI seems to be down). -1 karma is for reasons explained above.
When I try to start container, it errors out with:
Error: error setting up OCI Hooks: parsing hook "/usr/share/containers/oci/hooks.d/oci-umount.json": unrecognized hook version: "": parsing hook "/usr/share/containers/oci/hooks.d/oci-systemd-hook.json": unrecognized hook version: "": parsing hook "/usr/share/containers/oci/hooks.d/oci-register-machine.json": unrecognized hook version: ""
Confirmed. With
oci-umount-2:2.5-4.gitc3cda1f.fc32, podman fails as follows:This is a regression:
podman-2:1.9.3-1.fc32succeeds with and withoutoci-umountinstalled.dnf remove oci-umountmakes podman work again.@jimtahu I've filed podman issue 6629. Thank you for reporting this.
Would it perhaps be better to use COPR for testing so that people need to opt-in to these RCs (also on rawhide where it seems we're using Fedora as a CI system with a new build every 2 hours? https://bodhi.fedoraproject.org/updates/?packages=podman)
At the moment, even if these updates do not make it to the stable updates repositories (some of the broken ones like the skopeo update made it there even: https://bodhi.fedoraproject.org/updates/FEDORA-2020-cd7e382e0c). us folks that test the updates-testing repos are still getting them and seeing broken systems. The function of the updates-testing repositories is to test stable updates before they get to users, not to test rcs which are not intended for users in the first place, right?
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#stable-releases
A much better system would be to use copr (which has excellent scm integration) for all of these snapshots and only push stable versions of these tools to Fedora. That allows people to opt-in as opposed to the current system where I need to modify my repo files to opt out from these rcs. The other option is that I stop testing updates.
This update has been obsoleted by podman-2.0.0-0.3.rc7.fc32.