Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: The recent update of glibc to version 2.29-12 (Bodhi: [0]) a missing package for glibc-headers.i686. Koji [1] indicates the package had successfully been built, but it hasn't been found in the updates repository for x86_64. This breaks dnf update on at least one of my machines with the following messages: Probleem 1: package glibc-headers-2.29-9.fc30.i686 requires glibc = 2.29-9.fc30, but none of the providers can be installed - cannot install both glibc-2.29-12.fc30.i686 and glibc-2.29-9.fc30.i686 - cannot install both glibc-2.29-9.fc30.i686 and glibc-2.29-12.fc30.i686 - cannot install both glibc-2.29-12.fc30.x86_64 and glibc-2.29-9.fc30.x86_64 - cannot install both glibc-2.29-9.fc30.x86_64 and glibc-2.29-12.fc30.x86_64 - cannot install the best update candidate for package glibc-headers-2.29-9.fc30.i686 - cannot install the best update candidate for package glibc-2.29-9.fc30.i686 - cannot install the best update candidate for package glibc-2.29-9.fc30.x86_64 Probleem 2: problem with installed package glibc-headers-2.29-9.fc30.i686 - glibc-headers-2.29-9.fc30.i686 has inferior architecture - cannot install both glibc-headers-2.29-12.fc30.x86_64 and glibc-headers-2.29-9.fc30.x86_64 - cannot install both glibc-headers-2.29-9.fc30.x86_64 and glibc-headers-2.29-12.fc30.x86_64 - cannot install the best update candidate for package glibc-headers-2.29-9.fc30.x86_64 Version-Release number of selected component (if applicable): 2.29-12 How reproducible: Try to update glibc-headers.i686 and dependencies to version 2.29-12. Steps to Reproduce: 1. Have an x86_64 machine with glibc-headers-2.29-9.fc30.i686 installed. 2. Run dnf update Actual results: No update Expected results: Update Additional info: [0] https://bodhi.fedoraproject.org/updates/FEDORA-2019-f82f6f0c87 [1] https://koji.fedoraproject.org/koji/buildinfo?buildID=1261638
This is a known issue which we cannot fix in the glibc package. The workaround is to remove the glibc-headers.i686 package manually, before the update. *** This bug has been marked as a duplicate of bug 1652872 ***