Bug 49800

Summary: glibc-common won't install on clean system
Product: [Retired] Red Hat Linux Reporter: Robert van den Aker <robert2>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED CURRENTRELEASE QA Contact: Aaron Brown <abrown>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: fweimer
Target Milestone: ---   
Target Release: ---   
Hardware: alpha   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-07-24 01:45:52 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 Robert van den Aker 2001-07-24 01:45:48 UTC
From Bugzilla Helper:

User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Mac_PowerPC)



Description of problem:

I updated my mirror of RH 7.0 for alpha with glibc-common-2.2-12 
and glibc-2.2-12. Tried to install from that updated mirror onto clean 
system. Error message in /tmp/install.log:

Installing glibc-common.

unpacking of archive failed: cpio: Missing hard link

Running rpm -i glibc-common will install the package after the install, 
but then I have to remove and reinstall all packages that couldn't 
install properly because they needed glibc-common. This includes 
all packages that are configured by a perl script, because perl can't 
set the locale. Very annoying. Could glibc-common be rebuilt so that 
it will install on a clean system?



How reproducible:

Always



Steps to Reproduce:

1. Mirror RH 7.0 for alpha

2. Incorporate updates from 'updates' tree into 'Redhat/RPMS' tree, 
including update to glibc-2.2-12 and glibc-common-2.2-12.

3. Try installation off the updated 'RedHat/RPMS' tree.

	



Actual Results:  glibc-common didn't install. Subsequent packages 
didn't install properly.



Expected Results:  glibc-common should install on clean system.



Additional info:

Comment 1 Jakub Jelinek 2001-07-25 10:56:58 UTC
It is a rpm issue when there are hardlinks where some of the links are
present in one %lang(), others in other %lang() and one of those languages
is not selected for install.
You can get around this by forcing %_install_langs all, or by using some
more recent glibc (such as the one from 7.1 distribution - highly recommended).