On 8/15/21 1:41 AM, L A Walsh wrote:
On 2021/08/12 12:34, Carlos E. R. wrote:
Well, try to remove glibc-32bit and see who complains.
Haven't reached the end yet, but so far, this is disturbing. Wrote a script (attached), that generates a list of all rpms with '32bit-' in the name (had 138). Try to remove 1st item on list, + capture errors of type: xxxx is needed by (installed) xxxyy
Then add xxxyy to the list and try "rpm -e" on the new list.
So far, it has taken 2-3 runs for each batch, with 1st run giving me some other rpm, and 2nd run a longer list. Then I ran through and deleted all of them that had no dependencies and am now down to 10 rpms (from 138).
Ok, lilo, which hasn't been updated since 2019 depends on these 32bit packages:
The maintainer decided to drop lilo last year so unfortunately we can't help you much with that [1]
I.e. 133 32bit packages were installed as "suggestions", while none of the same-version 64bit ones were installed...
I checked and my /etc/zypp/zypp.conf didn't have related files set to off. I thought it was set to that, but it has been set to pull in related since Mar 02,2016. Maybe since I usually have used rpm, I didn't notice how gratuitously it made "suggestions"...
This area has been cleaned up a lot for new installs in the last few years (well certainly since 2016), but if you had one package that needed 32 bit libs rather then 64bit ones it used to pull in alot of other libs as well. But this is largely fixed now that 32bit apps are much less common. 1. https://build.opensuse.org/request/show/811842 -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B