Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
First Last Prev Next    This bug is not in your last search results.
Bug 12491 - rpm 4.0.32 lock message is wrong
rpm 4.0.32 lock message is wrong
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
6.2
All Linux
medium Severity high
: ---
: ---
Assigned To: Jeff Johnson
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2000-06-18 20:28 EDT by R P Herrold
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-06-20 21:43:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description R P Herrold 2000-06-18 20:28:30 EDT 
Running a query while a package install is running in another window yields
this lock message:

cannot get shared lock on /var/lib/rpm/Packages
 
failed to open /var/lib/rpm/packages.rpm: No such file or directory
  

dbiOpen: cannot open Packages index   

-------------------

The CORRECT name of this package is:    Packages            
and NOT   packages.rpm 

... is this an error message problem, or a filename issue?
Comment 1 Jeff Johnson 2000-06-20 21:43:26 EDT 
This is largely a problem with aging and misleading error messages rather
than a real problem. The current algorithm, when the desired db3 open fails,
is to attempt a db1 open, which of course also fails. A more precise return
from the db3 open will permit skipping the futile db1 open attempt.
Comment 2 Jeff Johnson 2000-07-20 14:05:12 EDT 
This should be fixed in rpm-4.0-0.56. Please reopen if not.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.