Update snapshots to 20260816

[schutzbot]

Results of the snapshot jobs:
Job(s) succeeded: 243
Job(s) failed: 3

If these are false, rebuild the enumerate cache manually:
Enumerate cache job succeeded: true
Check snapshot succeeded:

Workflow run: https://github.com/osbuild/rpmrepo/actions/runs/31921654228

---

update_schutzfile.py output

[achilleas-k]

The problem with the container resolver is that the podman run call is failing in github actions with

running registry.access.redhat.com/ubi9-micro:latest container failed: exit status 126
stderr:
[conmon:e]: Include journald in compilation path to log to systemd journal
Error: conmon failed: exit status 1

I can't reproduce the failure locally, neither on a Fedora host nor in an Ubuntu 24.04 container, which I used to try to replicate the CI environment.

[achilleas-k]

Merged the container resolver tests into the unit tests that run in Fedora containers. They're no longer separate jobs so they wont be reported separately in the statuses.

[achilleas-k]

The test explicitly refuses to run in a container and fails when forced. Let's see if I can change that.

[achilleas-k]

I think I'm just going to remove these tests. They're covered by integration tests in GitLab. It's not worth the effort to get them fixed to run in GHA. It'd be a different story if they were quick unit tests that can easily be run locally, which would catch problems before people push and open PRs, but they're not.

[croissanne]

thanks!

[achilleas-k]

Didn't drop the test. Instead changed it to be a simple error check without message matching.

[achilleas-k]

The other test failed now (╯°□°)╯︵ ┻━┻

[achilleas-k]

I'll check on it in a bit

[achilleas-k]

The other test failed now (╯°□°)╯︵ ┻━┻

So the failure in this case was a timeout, which I foolishly assumed was a problem with our test, possibly related to the previous failure that I worked around. Given how GitHub is currently having a day again, I'm going to assume it's just regular old GH-borkage until proven otherwise.