-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
rhel-9.6
-
None
-
No
-
None
-
rhel-pt-llvm-rust
-
3
-
False
-
False
-
-
No
-
None
-
None
-
None
-
Unspecified Release Note Type - Unknown
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
Wanted to remove dependency in my layered product (RHDH) container image on these RPMs, so as to be ready for the EOL of Python 3.9 in Oct 2025 (see https://devguide.python.org/versions/ ).
However installing cmake for RHEL 9 brings in these deps:
$ microdnf install cmake ... cmake-3.26.5-2.el9.x86_64 ubi-9-appstream-rpms 9.2 MB cmake-data-3.26.5-2.el9.noarch ubi-9-appstream-rpms 2.5 MB cmake-filesystem-3.26.5-2.el9.x86_64 ubi-9-appstream-rpms 23.4 kB cmake-rpm-macros-3.26.5-2.el9.noarch ubi-9-appstream-rpms 12.2 kB ... make-1:4.3-8.el9.x86_64 ubi-9-baseos-rpms 553.9 kB python-unversioned-command-3.9.21-2.el9_6.1.noarch ubi-9-appstream-rpms 10.2 kB python3-3.9.21-2.el9_6.1.x86_64 ubi-9-baseos-rpms 27.3 kB python3-libs-3.9.21-2.el9_6.1.x86_64 ubi-9-baseos-rpms 8.5 MB python3-pip-wheel-21.3.1-1.el9.noarch ubi-9-baseos-rpms 1.2 MB python3-setuptools-wheel-53.0.0-13.el9_6.1.noarch ubi-9-baseos-rpms 479.1 kB
Meanwhile in the ubi10 minimal image:
[root@95798d6822e3 /]# microdnf install cmake Package Repository Size Installing: cmake-3.30.5-3.el10_0.x86_64 ubi-10-appstream-rpms 12.6 MB cmake-data-3.30.5-3.el10_0.noarch ubi-10-appstream-rpms 2.7 MB cmake-filesystem-3.30.5-3.el10_0.x86_64 ubi-10-appstream-rpms 24.1 kB emacs-filesystem-1:29.4-10.el10_0.noarch ubi-10-appstream-rpms 11.0 kB expat-2.7.1-1.el10_0.x86_64 ubi-10-baseos-rpms 123.0 kB libuv-1:1.49.2-2.el10.x86_64 ubi-10-appstream-rpms 270.0 kB make-1:4.4.1-9.el10.x86_64 ubi-10-baseos-rpms 605.3 kB vim-filesystem-2:9.1.083-5.el10.noarch ubi-10-baseos-rpms 23.3 kB
What is the impact of this issue to you?
I have to keep fixing Python 3.9 CVEs instead of just dropping that from the container.
Please provide the package NVR for which the bug is seen:
cmake-3.26.5-2.el9.x86_64
How reproducible is this bug?:
Always
Steps to reproduce
- observe which rpms are installed for a ubi9-minimal container when you try toi install cmake
- podman run -it --rm --entrypoint /bin/bash --user root registry.access.redhat.com/ubi9-minimal:latest -c "microdnf install cmake"
- repeat for ubi10
- podman run -it --rm --entrypoint /bin/bash --user root registry.access.redhat.com/ubi10-minimal:latest -c "microdnf install cmake"
Expected results
On both ubi9 and ubi10, cmake should be able to be installed against python 3.11 or 3.12; it should not insist on installing python-unversioned-command-3.9 and python3-3.9
Actual results
On both ubi9 (but not ubi10), cmake install requires python-unversioned-command-3.9 and python3-3.9
- is depended on by
-
RHIDP-8062 Spike: can we use cmake via pip instead of rpm, or find a version of cmake without Python 3.9 dependency?
-
- New
-
