On 09/07/17 22:51, Dominique Leuenberger / DimStar wrote:
On Sun, 2017-07-09 at 11:33 +0200, Christian Boltz wrote:
Hello,
I don't want/need any *-32bit packages - but zypper dup always wants to pull in lots of them (see below). Therefore I had *-32bit locked in zypper for quite a while.
Today I finally had some time to track this down [1] and found out that the root cause is
# rpm -q --recommends patterns-base-enhanced_base |grep 32 glibc-32bit glibc-locale-32bit
zypper al glibc-32bit is enough to keep the *-32bit packages out.
Is there a good reason for the Recommends: glibc-32bit and glibc-locale-32bit? I doubt - if a package needs a *-32bit package, it can/should require it.
I'm in favor of such a change, as in most cases -32bit stuff is not needed (exceptions strat when you install wine / steam
In plus, I know of fun side effects at least on the live images, IF any of the 32bit stuff is being dragged in later on - as this happens to mess up the pam stack very quickly
(e.g. if you have a single pam=bit, the stack is getting very fragile)
See also bugs https://bugzilla.opensuse.org/show_bug.cgi?id=544314 and https://bugzilla.opensuse.org/show_bug.cgi?id=537343 (I hope the refs are correct, boo is currently not answering)
Cheers, Dominique
PS: there is actually also a bug which I assigned to myself, to get rid of -32bit on default installs
I also agree with the change, but when you do it can you add that recommends to the x86 pattern so it doesn't break so badly. It has also got me curious about the 32bit and 64bit patterns which also seem to do very little unless yast uses them, the 32bit pattern isn't visible at all and on this 64 bit machine the 64bit pattern is visible but not installed. Can we remove them? or should they both still be present but hidden? -- 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