Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 252979 - RPM missing a Requires:, fails on too-old glibc
RPM missing a Requires:, fails on too-old glibc
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Paul Nasrat
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-08-16 09:07 EDT by Valdis Kletnieks
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-08-20 03:36:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Valdis Kletnieks 2007-08-16 09:07:31 EDT
Description of problem:
RPM and yum loop with an error message:
rpmdb: unable to lock mutex: Invalid argument

I have glibc-2.6.90-8 installed, apparently rpm-libs is trying to use the futex
support added in 2.6.90-9.

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

How reproducible:
Install this release of RPM and a glibc older than 2.6.90-9.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Valdis Kletnieks 2007-08-16 10:20:52 EDT
Something else is obviously squirrelly - I managed to get back to an older RPM
with 'rpm2cpio rpm- | cpio -ivudm' and it's still doing it.
Comment 2 Valdis Kletnieks 2007-08-16 10:40:57 EDT
Whatever it was, seems to be gone after applying glibc-2.6.90-10.  Also, it only
seems to trigger if /var/lib/rpm/__db.00* files are present (hand-removing them
make it shut up).
Comment 3 Panu Matilainen 2007-08-20 03:36:53 EDT
Looks like temporary glibc brokenness, rpm mostly just cares about having
working and compatible NPTL used for locking (the __db* files). glibc 2.6.90 is
most certainly new enough, too new if anything... :)

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