Bug 86092 - Can't install/update rpm packages
Summary: Can't install/update rpm packages
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rpm
Version: 8.0
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Paul Nasrat
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-03-13 20:49 UTC by Todd Bailey
Modified: 2007-04-18 16:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-04-19 18:46:07 UTC


Attachments (Terms of Use)

Description Todd Bailey 2003-03-13 20:49:39 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
system crached during package install, can no longer install, remove, manage 
rpm packages, via command line, gui and package applet.

tried to rebuild via rpm -v --rebuilddb with out success.
gui gets to reading system state then quits.

Version-Release number of selected component (if applicable):
rpm-4.1.1-0.1.8.x

How reproducible:
Always

Steps to Reproduce:
1. 2x click on any rpm package to install
2. or 2x click on package manager gui appl
3. manually trying to install via cmd line
    

Actual Results:  gui status/progress bas, reading headers, reading system state
then gui appl shuts down

Expected Results:  dialog requesting confirmation that you want to install this 
package

Additional info:

provided on demand

Comment 1 Todd Bailey 2003-03-13 20:52:05 UTC
removing lock dbs __db* and rpm --rebuild did not fix the package db file


Is there a way to regenerate this file with out reinstall ?

Comment 2 Jeff Johnson 2003-03-14 20:46:05 UTC
Give me a pointer (i.e. URL, attachments won't work)
to a tarball of your database
   cd /var/lib
    tar czvf /tmp/rpmdb-86092.tar.gz rpm
and I'll try to fix.

Comment 3 Jeremy Katz 2005-04-19 18:46:07 UTC
Closing due to inactivity.  If this issue still occurs with current releases,
please reopen and set the release in which you've encountered the problem.


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