Description of problem: podman 4.6.0-3.el9 has been built against podman main branch and commit 144098587706ac3fd4e257ea03c75aaf4ee29064 which is 4.7.0-dev and has been delivered in CentOS stream, causing all issues in systems running podman. For example, it prevents other tools like gitlab runner from starting services using podman. https://gitlab.com/redhat/centos-stream/rpms/podman/-/commit/d265b78198fdabd6ec7508a5a61b2d7f46405e55 The build was changed to be done against branch "main" (perhaps it should be tag v4.6.0), and specifically commit 144098587706ac3fd4e257ea03c75aaf4ee29064. ``` $ git tag --contains "144098587706ac3fd4e257ea03c75aaf4ee29064" ## nothing $ git checkout 144098587706ac3fd4e257ea03c75aaf4ee29064 $ cat version/rawversion/version.go package rawversion // RawVersion is the raw version string. // // This indirection is needed to prevent semver packages from bloating // Quadlet's binary size. // // NOTE: remember to bump the version at the top of the top-level README.md // file when this is bumped. const RawVersion = "4.7.0-dev" ``` Version-Release number of selected component (if applicable): 4.6.0-3 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This is now fixed by podman-4.6.1-1.el9: $ podman --version podman version 4.6.1