Bug 505351
Summary: | rpmfcHelper: Zusicherung »EVR != ((void *)0)« nicht erfüllt. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Robert Scheck <redhat-bugzilla> |
Component: | rpm | Assignee: | Panu Matilainen <pmatilai> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 10 | CC: | ffesti, jnovy, pmatilai |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 4.6.1-2.fc10 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-10-09 03:45:05 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: | |||
Bug Depends On: | |||
Bug Blocks: | 504882 |
Description
Robert Scheck
2009-06-11 15:18:57 UTC
I would assume the cause is, that "Version:" tag is empty. And rpm5.org solves this problem by doing then only a "Provides: pkgconfig(bitlbee)" rather then failing... ;-) Right, this has already been fixed for quite some time in rpm.org HEAD + 4.7.x branch, just not in 4.6.x. Panu, why is this bug report still not fixed at Fedora 10? It still prevents me from pushing an update of bitlbee there. rpm-4.6.1-2.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/rpm-4.6.1-2.fc10 rpm-4.6.1-2.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update rpm'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-9654 rpm-4.6.1-2.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report. |