@adamwill we've been ignoring the toolbox tests for a while now.

cc @rishi is there anyone willing to maintain toolbox tests or should we remove it?

revoked for now because we're not building v4.7.0 podman for f37 yet.

dont need the gvforwarder split for f37, so no need for this bodhi update.

disabling auto-request stable for RC builds. But no worries if it has to be pushed to stable for any reason.

disabling auto-request stable for RC builds. But no worries if it has to be pushed to stable for any reason.

disabling autostable until we decide how to deal with selinux failures.

disabling autostable until we decide how to deal with selinux failures.

will conflict with selinux-policy-doc on container_selinux.8 manpage ownership

https://bugzilla.redhat.com/show_bug.cgi?id=2209120

This update has been unpushed.

@kparal can you please retry with an upgrade from the version in stable, v2.209.0 to this one?

This update has been unpushed.

reverted this in favor of v2.211.1 . This one seems to run a time consuming relabel for a lot of people

@mhjacks ugh that was my bad. I'll check if the test failures are ok to be waived. If not, If I can't waive them yet, I'll do a new build while i'm at it.

@mhjacks doesn't sound quite right. I have added an obsoletes on the older podman-quadlet so it should get automatically removed. Did you actually need to remove the older podman-quadlet ? Might be a packaging error on my part in that case.

@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

ah yeah. my bad. we can karma this up after containers-common goes to stable.

addresses https://github.com/containers/podman/issues/13924

@gotmax23 was the rebuild of podman for f38 blocked because of this issue? Just trying to understand why an f38 mass rebuild would be blocked on f37. The rawhide build of the podman rc was already moved to stable.