Timothée Ravier

I'm currently testing this change in this repo: https://github.com/travier/cosign-test This needs a newer podman version than the one currently available in Ubuntu 22.04 (`ubuntu-latest`), thus I'm installing it from https://podman.io/docs/installation#ubuntu

``` Error: initializing private key: decrypt: encrypted: unexpected kdf parameters ``` 🤔 Filed as https://github.com/containers/podman/issues/20771.

I now have a working setup with https://github.com/travier/podman-action & https://github.com/travier/cosign-test which works with this PR. Example multi-arch, podman signed build in https://github.com/travier/cosign-test/blob/main/.github/workflows/nginx.yml.

Another option would be to make another "podman only" action.

There is not much rpm-ostree can do here. This is inherent to the repos being built on two different infras, etc.

Do you mean that the mesa version is effectively downgraded and does not pick the latest build from the RPM Fusion repos? This is unexpected.

Isn't the idea that you remove mesa and replace it with mesa-freeworld as well?

Another option is to teach pungi to directly modify `automatic_version_prefix`/`automatic-version-prefix` to the corresponding version.

OK, I did that in pungi in https://pagure.io/pungi/pull-request/1726 -> https://pagure.io/pungi/pull-request/1731. Not sure which path is better here. Should we add the option here instead?

https://pagure.io/pungi/pull-request/1731 got merged so I'll close this one.