Bug 51648

Summary:	Warning in /tmp/upgrade.log
Product:	[Retired] Red Hat Raw Hide	Reporter:	hjl
Component:	anonftp	Assignee:	Bernhard Rosenkraenzer <bero>
Status:	CLOSED RAWHIDE	QA Contact:	Aaron Brown <abrown>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0	CC:	jik
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-08-22 10:33:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description hjl 2001-08-13 15:41:55 UTC

I used glibc-2.2.4-5 to upgrade glibc in RedHat 7.1. I got

Upgrading glibc-common.
Upgrading glibc.
basename: too many arguments
Try `basename --help' for more information.
cp: cannot stat `/lib/ld-.so': No such file or directory
cp: cannot stat `/lib/libc-.so': No such file or directory
cp: cannot stat `/lib/libnsl-.so': No such file or directory
cp: cannot stat `/lib/libnss_files-.so': No such file or directory

in /tmp/upgrade.log

Comment 1 Jakub Jelinek 2001-08-13 15:47:35 UTC

This is a bug in anonftp (note to Bero, it is still there, it has not
been fixed).
The line
LIBCVER=`basename %{ROOT}/lib/libc-*.so .so | cut -f2- -d-`
is bogus, at the point of glibc upgrade where the version changes
(like 2.2.3-foo -> 2.2.4-bar) when the %trigger is run, there are
2 libc-*.so files so it becomes confused.
As I've mailed some long time ago, you should be using ldconfig output
to see what library you should copy, or at least run ldconfig and then look
what libc.so.6 symlink points to.

Comment 2 Bernhard Rosenkraenzer 2001-08-20 10:03:51 UTC

*** Bug 51943 has been marked as a duplicate of this bug. ***

Comment 3 Bernhard Rosenkraenzer 2001-08-20 10:09:01 UTC

Fixed in 4.0-8 (4.0-7 fixed the copy() script only, not the LIBCVER variable)

Comment 4 Jonathan Kamens 2001-08-21 13:47:57 UTC

I got these errors when upgrading from 4.0-7 to 4.0-8.  Does this means that
there's still a problem somewhere, or that the bugs were in a postuninstall
script from 4.0-7?

ls: /var/ftp/lib/libc-*.so: No such file or directory
ls: /lib/ld-.so.so: No such file or directory
cp: cannot stat `': No such file or directory
ls: /lib/libc-.so.so: No such file or directory
cp: cannot stat `': No such file or directory
ls: /lib/libnsl-.so.so: No such file or directory
cp: cannot stat `': No such file or directory
ls: /lib/libnss_files-.so.so: No such file or directory
cp: cannot stat `': No such file or directory

Comment 5 Jonathan Kamens 2001-08-22 10:33:29 UTC

After the error noted above, I get this when I run "rpm --verify anonftp" with
4.0-8:

root@jik:~/tmp/addresses/rwback!1# rpm --verify anonftp
md5sum: /var/ftp/lib/lib*-*.so: No such file or directory
5.......   /var/ftp/lib/lib*-*.so

Either this isn't actually fixed, or there's an issue with upgrading between
Rawhide versions of this package.  Since I'm not sure which of these is the
case, I'm reopening this bug so it doesn't get lost.

Comment 6 Bernhard Rosenkraenzer 2001-08-22 12:10:09 UTC

4.0-9 fixes it for good

Comment 7 Jakub Jelinek 2001-08-22 12:39:25 UTC

*** Bug 52212 has been marked as a duplicate of this bug. ***

Comment 8 Jakub Jelinek 2001-11-30 23:17:15 UTC

*** Bug 56950 has been marked as a duplicate of this bug. ***