Static installation broken on older versions (<1.27) due to packages adding prefix crio- #7923
Labels
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
What happened?
Was not sure if this Issue should be opened here or in https://github.com/cri-o/packaging, please correct me if this is wrong place.
So recently some packages added crio- prefix in name due to conflict with redhat packages this causes the static installation to fail on older builds. I see updated packages are released in 1.28.4 and 1.29.2, but is there any plans for back-ports to 1.27 and 1.26? Otherwise is there a possibility to extend the packaging script to support these versions?
Also the README example suggest that the static installation would work on 1.21.0 which it won't so I think some disclaimer there would be very useful and an example that is actually working.
What did you expect to happen?
cri-o to be installed
How can we reproduce it (as minimally and precisely as possible)?
The example from the README can be used, but also more recent version such as v1.27.4
Anything else we need to know?
No response
CRI-O and Kubernetes version
Not applicable fails installation for versions below v1.28
OS version
Additional environment details (AWS, VirtualBox, physical, etc.)
Virtual machine, but should not affect the result
The text was updated successfully, but these errors were encountered: