Bug 250885

Summary:	Error while loading shared libraries: libperl.so: cannot open shared object file: No such file or directory
Product:	[Fedora] Fedora	Reporter:	Greg Douglas <gregory.douglas>
Component:	perl	Assignee:	Robin Norwood <robin.norwood>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	7
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:	2007-08-06 02:44:47 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 Greg Douglas 2007-08-04 11:35:12 UTC

Description of problem:

After upgrading from FC6 to Fedora 7, perl no longer works.  Any application
that needs perl displays the following error message:

perl: error while loading shared libraries: libperl.so: cannot open shared
object file: No such file or directory

OR

/usr/bin/perl: error while loading shared libraries: libperl.so: cannot open
shared object file: No such file or directory


I have checked ldd, and there are no dynamic links for perl.

rpm -V perl gives:

prelink: /usr/bin/a2p: at least one of file's dependencies has changed since
prelinking
S.?.....   /usr/bin/a2p




Version-Release number of selected component (if applicable): perl-5.8.8-18.fc7


How reproducible: Every time.


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:
worked fin in FC6

Additional info:

Comment 1 Greg Douglas 2007-08-05 16:32:37 UTC

The update from FC6 to Fedora 7 resulted in yum not applying the dependency of
perl-libs.  This package was never installed.  I have manually added this
package, and the other applications appear to work now.  

Is this dependency missing from the rpms file?

Comment 2 Robin Norwood 2007-08-06 02:44:47 UTC

Greg - this is one we're blaming on yum.  See bug #240540

*** This bug has been marked as a duplicate of 240540 ***

Comment 3 Greg Douglas 2007-08-06 12:02:22 UTC

Indeed, thanks Robin.