Bugzilla – Bug 1225884
Discover prompts for glibc-32bit update but fails
Last modified: 2024-06-03 23:36:50 UTC
Created attachment 875286 [details] Failure message in Discover After boot, the automatic system update prompted updates were available. After accepting the update in Discover the process immediately failed. The error given was as follows: Dependency resolution failed: the installed steam-1.0.0.79-1.4.x86_64 requires 'glibc-locale-base-32bit', but this requirement cannot be provided After going into the terminal to assess the situation I attempted the update manually and was given the following: Problem: 1: the installed steam-1.0.0.79-1.4.x86_64 requires 'glibc-locale-base-32bit', but this requirement cannot be provided deleted providers: glibc-locale-base-32bit-2.39-7.1.x86_64 Solution 1: deinstallation of steam-1.0.0.79-1.4.x86_64 Solution 2: keep obsolete glibc-locale-base-32bit-2.39-7.1.x86_64 Solution 3: break steam-1.0.0.79-1.4.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): It seemed the package was a requirement of "steam-1.0.0.79-1.4.x86_64" but the package missing (though verbage indicates its installed (2)) I tried to manually install the required "glibc-locale-base-32bit" which net the following error: solaris17@localhost:~> sudo zypper in glibc-locale-base-32bit Refreshing service 'NVIDIA'. Refreshing service 'openSUSE'. Loading repository data... Reading installed packages... 'glibc-locale-base-32bit' is already installed. Package 'glibc-locale-base-32bit' is not available in your repositories. Cannot reinstall, upgrade, or downgrade. Resolving package dependencies... Nothing to do. It seems the package "steam-1.0.0.79-1.4.x86_64" requires a package version not availible in the standard repos.
To provide further context. It appears that the version requested is not built for x86_64: https://www.rpmfind.net/linux/rpm2html/search.php?query=glibc
. *** This bug has been marked as a duplicate of bug 1225809 ***
(In reply to hui from comment #2) > . > > *** This bug has been marked as a duplicate of bug 1225809 *** Thanks for referencing the way forward!