Bug 23118
Summary: | up2date core dumps... | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Brad Kittredge <bmk> |
Component: | up2date | Assignee: | Preston Brown <pbrown> |
Status: | CLOSED DUPLICATE | QA Contact: | Aaron Brown <abrown> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | brad.kittredge |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-02-08 06:31:35 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Brad Kittredge
2001-01-02 01:03:07 UTC
Sorry, but bmk is a dead mail account ;-) The rpm version is: rpm-4.0.2-0.7 With default version of rpm I got an identical result as bug # 22974. Hope this helps. This appears to be a bug with rpm version 4.0.2-0.7. This should be fixed in the next release of rpm. In the meantime, this shouldnt happen with the original rpm 4.0-4 from 7.0. I'm not sure why you would be having the error reported in #22974. I havent been able to reproduce that behaviour here. Can you verify with rpm, and rpm-python were reinstalled with the original versions? I reverted to the version of rpm that ships with RH 7.0 and executed the following: rpm --rebuilddb Below is the output from up2date after I did this: Retrieving list of all available packages... Removing installed packages from list of updates... 0.077% <snip> Removing packages marked to skip from list... 0.202% <snip> Getting headers for available packages... 0.202% <snip> Removing packages with files marked to skip from list... 0.202% <snip> 3.651% There was a fatal RPM error. The message was: error reading from database |