Bug 219662 - install fails: libpython2.5.so.1.0 not found
install fails: libpython2.5.so.1.0 not found
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
rawhide
powerpc Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
:
: 219888 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-12-14 13:05 EST by John Reiser
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-12-15 09:48:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
The point where anaconda dies (8.41 KB, image/png)
2006-12-14 17:07 EST, Bas Mevissen
no flags Details

  None (edit)
Description John Reiser 2006-12-14 13:05:11 EST
Description of problem: Attempting to install using today's Rescue CD for
PowerPC, anaconda appears to start but fails immediately with the text message:
/urs/bin/python: error while loading shared libraries: libpython2.5.so.1.0:
cannot open shared object file: no such file or directory.


Version-Release number of selected component (if applicable):


How reproducible: always


Steps to Reproduce:
1. boot PowerPC Rescue CD with boot: linux
2. accept defauls for language and keyboard; specify HTTP, IP4 only, DHCP,
mirror, directory
3.
  
Actual results:
install terminated abnormally (very soon after "running anaconda, ..." because
libpythong2.5.so.1.0 cannot be found

Expected results:
install proceeds

Additional info:
Comment 1 Bas Mevissen 2006-12-14 17:07:19 EST
Created attachment 143706 [details]
The point where anaconda dies

Same problem on i386 architecture in Xen guest
Comment 2 Bas Mevissen 2006-12-14 17:27:50 EST
So problem seems arch independant.
Comment 3 Jeremy Katz 2006-12-15 09:48:55 EST
Fix for this is in CVS, but other things are breaking the build right now. 

I'll hopefully get those taken care of today.  Then there's just some other
python2.5 fallout that needs fixing (pyxf86config seems to play things a little
too fast and loose with refcounting)
Comment 4 Bas Mevissen 2006-12-15 10:01:23 EST
OK, thanks.
From the process point of view: why not first put it to resolved and then close
after you recieve confirmation of the original submitter?
Comment 5 Chris Lumens 2006-12-15 19:52:00 EST
*** Bug 219888 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.