Bug 1947256

Summary:	glibc: multilib objects should be marked %missingok in RPM spec
Product:	Red Hat Enterprise Linux 8	Reporter:	Florian Weimer <fweimer>
Component:	glibc	Assignee:	glibc team <glibc-bugzilla>
Status:	CLOSED WORKSFORME	QA Contact:	qe-baseos-tools-bugs
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.5	CC:	ashankar, codonell, dj, fweimer, mnewsome, pfrankli, sipoyare, skolosov
Target Milestone:	beta	Keywords:	FutureFeature, Patch, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-09-16 12:26:10 UTC	Type:	Enhancement
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1889978

Description Florian Weimer 2021-04-08 05:30:35 UTC

Without %missingok, RPM will print confusing errors during in-place upgrades to Red Hat Enterprise Linux 9, like this:

warning: file /lib64/power9/libthread_db.so.1: remove failed: No such file or directory
warning: file /lib64/power9/libthread_db-1.0.so: remove failed: No such file or directory
warning: file /lib64/power9/librt.so.1: remove failed: No such file or directory
warning: file /lib64/power9/librt-2.33.so: remove failed: No such file or directory
warning: file /lib64/power9/libpthread.so.0: remove failed: No such file or directory
warning: file /lib64/power9/libpthread-2.33.so: remove failed: No such file or directory
warning: file /lib64/power9/libm.so.6: remove failed: No such file or directory
warning: file /lib64/power9/libm-2.33.so: remove failed: No such file or directory
warning: file /lib64/power9/libc.so.6: remove failed: No such file or directory
warning: file /lib64/power9/libc-2.33.so: remove failed: No such file or directory

I reviewed the RPM source code and %missingok is the only way to suppress this warning.

Comment 2 Florian Weimer 2021-06-18 08:31:40 UTC

I'm no longer sure if this worthwhile to do. We will likely have ldconfig warnings during in-place upgrades from Red Hat Enterprise Linux 8 to 9 if we install glibc's DSOs under their sonames, not versioned files (see Fedora bug 1652867). That warning won't go away because it makes sense for ldconfig in general. And if we cannot get down to zero warnings, we still need to document something, and documenting another warning isn't too much trouble.

Comment 3 Florian Weimer 2021-09-16 12:26:10 UTC

Closing as per comment 2.