v5.7.0 stable podman will be added here soon

@anotheruser Thanks for that link. I've forwarded it to the team, so someone should be responding to it soon. But it's just a warning and that warning is going to be there even when v5.7.0 releases. So, I don't see it being a problem with this particular build.

RE: build in copr, we're already doing bleeding-edge builds. But, realistically, how many people use or care about coprs? Is there some Fedora megaphone or some close-to-vanilla Fedora setup that will publicize/enable a copr as conveniently as updates-testing?

Again, wdyt about bumping karma and time to some absurdly high number?

@decathorpe Well, I PREFER NOT to push it to stable but it's no big deal if it lands in stable if it needs to be pushed there for any reason. It did pass tests fwiw. Is that still a problem?

If it is still a problem, would you be ok if I bump the required karma to over 9000 and required days to 365 for such builds?

I guess once this update gets unlocked, podman 5.6.0-rc2 will get automatically added here.

it was revoked already, so hopefully nothing broke except the tests here.

@adamwill this was mistakenly triggered by running packit create-update manually.

auto-request stable disabled until we have podman v5.5.0

auto-request stable disabled until we have podman v5.5.0

@adamwill All tests are passing here now with podman 5.4.2 already in rawhide. Could you please revert karma here?

podman 5.4.2 got added to https://bodhi.fedoraproject.org/updates/FEDORA-2025-ba88ddf062 so I'm just gonna wait until that lands in stable. It's f40 so not really high priority atm.

Never mind, we're gonna release podman 5.4.2 which will have the error messages fixed. That should fix things.

@adamwill I just checked with @gscrivano . The error messages are a podman problem and have been fixed upstream, should land in the upcoming 5.5.0. Not a crun issue. I'll waive the test failures after the rerun. Could you please revert karma as well?

autopush disabled until we have v5.4.0.

Thanks @adamwill

Ignore previous comment. It's not a downgrade from the previous build so it's all good. This build got triggered uninitentionally via a packit build in-koji and I wasn't aware it would do a tagged build. I was under the impression it'd be scratch. NVM.

This was a mistake

@adamwill looks like it overrode 1.13.1 on f42 https://bodhi.fedoraproject.org/updates/FEDORA-2024-5b11a69cb3 . I didn't know that was possible. The latest I see in src.fp.o is 1.13.0.