Description of problem: Having run my Fedora 34 with libdrm and dependencies from Fedora 35, I noticed that Fedora 34 libdrm was updated to the level I was running. So I decided to replace the Fedora 35 components by the same Fedora 34 components. The result is a system that can no longer find the binaries. Version-Release number of selected component (if applicable): glibc-2.33-8.fc34.x86_64.rpm glibc-all-langpacks-2.33-8.fc34.x86_64.rpm glibc-common-2.33-8.fc34.x86_64.rpm glibc-devel-2.33-8.fc34.x86_64.rpm glibc-headers-x86-2.33-8.fc34.noarch.rpm glibc-static-2.33-8.fc34.x86_64.rpm glibc-utils-2.33-8.fc34.x86_64.rpm libnsl-2.33-8.fc34.x86_64.rpm nscd-2.33-8.fc34.x86_64.rpm How reproducible: Update to: glibc-2.33.9000-2.fc35.x86_64.rpm glibc-all-langpacks-2.33.9000-2.fc35.x86_64.rpm glibc-common-2.33.9000-2.fc35.x86_64.rpm glibc-devel-2.33.9000-2.fc35.x86_64.rpm glibc-headers-x86-2.33.9000-2.fc35.noarch.rpm glibc-langpack-en-2.33.9000-2.fc35.x86_64.rpm glibc-static-2.33.9000-2.fc35.x86_64.rpm glibc-utils-2.33.9000-2.fc35.x86_64.rpm libnsl-2.33.9000-2.fc35.x86_64.rpm nscd-2.33.9000-2.fc35.x86_64.rpm libdrm-2.4.105-1.fc35.x86_64.rpm libdrm-devel-2.4.105-1.fc35.x86_64.rpm drm-utils-2.4.105-1.fc35.x86_64.rpm This works. Then do a `rpm -Uvh --force` on: drm-utils-2.4.105-1.fc34.x86_64.rpm glibc-2.33-8.fc34.x86_64.rpm glibc-all-langpacks-2.33-8.fc34.x86_64.rpm glibc-common-2.33-8.fc34.x86_64.rpm glibc-devel-2.33-8.fc34.x86_64.rpm glibc-headers-x86-2.33-8.fc34.noarch.rpm glibc-static-2.33-8.fc34.x86_64.rpm glibc-utils-2.33-8.fc34.x86_64.rpm libdrm-2.4.105-1.fc34.x86_64.rpm libdrm-devel-2.4.105-1.fc34.x86_64.rpm libnsl-2.33-8.fc34.x86_64.rpm nscd-2.33-8.fc34.x86_64.rpm The drm-related rpms are not the problem. Actual results: Unsuable system. Expected results: Flawless move to Fedora 34 rpms. Additional info:
*** This bug has been marked as a duplicate of bug 1652867 ***