2023-02-02T08:52:07-0500 WARNING
Problem: cannot install the best candidate for the job
- nothing provides containers-common-extra >= 4:1-66 needed by podman-5:4.4.0-1.fc36.x86_64
unfortunately, no, it's just not possible with how bodhi works currently. builds can only be in one update and updates cannot be deleted; an unpushed update still 'counts'. you either have to rebuild, or wait for containers-common to go stable. it has stable-by-time set to 7 days and it was pushed 6 days ago, so shouldn't take much longer.
For help debugging failed Fedora CI tests (fedora-ci.*), contact the Fedora CI team.
For help debugging failed Fedora CoreOS tests (coreos.*), contact the Fedora CoreOS team.
For help debugging failed openQA tests (update.*), contact the Fedora Quality team, who will usually investigate and diagnose all failures within 24 hours.
This update has been submitted for testing by lsm5.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This seems to have a dependency problem:
2023-02-02T08:52:07-0500 WARNING Problem: cannot install the best candidate for the job - nothing provides containers-common-extra >= 4:1-66 needed by podman-5:4.4.0-1.fc36.x86_64
I think that depends on FEDORA-2023-041092cd8f which should hit stable before podman does
This update has been pushed to testing.
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.
they should've been submitted together, or this one should only have been submitted after that was stable, then.
ah yeah. my bad. we can karma this up after containers-common goes to stable.
@adamwill hmm, do you know if I can unpush this and add the same build to the containers-common bodhi? I really don't wanna do a new build
unfortunately, no, it's just not possible with how bodhi works currently. builds can only be in one update and updates cannot be deleted; an unpushed update still 'counts'. you either have to rebuild, or wait for containers-common to go stable. it has stable-by-time set to 7 days and it was pushed 6 days ago, so shouldn't take much longer.
note, once containers-common goes stable, you should be able to re-run the test with the 're-trigger tests' button and it should pass.
This update has been obsoleted by podman-4.4.1-2.fc36.