Bug 117081
Summary: | rpm.headerLoad call causes segfault | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Sean Kasun <skasun> |
Component: | yum | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-02-29 22:47:24 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
Sean Kasun
2004-02-28 05:09:42 UTC
segfaults in rpmlib are invariably because of bad data is the general rule. otherwise, try -0.16, if segfault persists, then attach the hdr here. short *.py reproducer will expedite fix. Upgrading to -0.16 fixes it. After messing around with it, it seems that it was caused by rpm-python's dependances. rpm-python -0.14 doesn't require rpm -0.14. So when yum updated, it upgraded rpm-python from -0.9 to -0.14 before upgrading rpm. The result was that it segfaulted right afterwards, leaving rpm at -0.9. rpm-python deliberately does not depend on explcit release of rpm. |