Bug 178540 - no selected packages, after boot rpm fails / missing shared libraries
Summary: no selected packages, after boot rpm fails / missing shared libraries
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 5
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-01-21 15:54 UTC by David Timms
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-01-23 18:51:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Timms 2006-01-21 15:54:12 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 Fedora/1.7.12-1.5.1

Description of problem:
The nothing selected minimal install ends up with a non-working rpm, and rpm-libs is not installed.

Version-Release number of selected component (if applicable):
anaconda from fc5t2 installer (boot.iso?)

How reproducible:
Always

Steps to Reproduce:
1. fc5t2 boot.iso, network install: ftp
2. at package selection unselect everything.
3. next etc.
4. once complete, try: rpm
  

Actual Results:  #rpm -qa
rpm: error while loading shared libraries: librpm-4.4.so: cannot open shared object file: No such file or directory

Expected Results:  should see the minimal installed package list.

Additional info:

#ls -l /usr/lib/librp*
  No such file or directory.
#ls -l /bin/rpm
-rwxr-xr-x 1 rpm rpm 83732 Jan 10 02:20 /bin/rpm

manually copying on librpm-4.4.so, then librpmdb-4.4.so, then librpmio-4.4.so, then librpmbuild-4.4.so from a FC4 system has got rpm operating.

#rpm -qa|grep rpm
rpm-4.4.2-12
but
doesn't rpm need rpm-libs ?

Without a working rpm, much harder to put the other particular packages you need onto the freshly installed system.

see also:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=132682


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