Bug 89741
Summary: | Building sword gives reference to an unexpected package "sword-debuginfo-1.5.5-1" | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Hugo van der Kooij <hugo> |
Component: | rpm-build | Assignee: | Elliot Lee <sopwith> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
URL: | http://hvdkooij.xs4all.nl/software/sword-1.5.5-1.i386.html | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-01-07 11:53:53 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
Hugo van der Kooij
2003-04-27 12:58:53 UTC
Try adding %define debug_package %{nil} to the spec file. Does that fix? It allows the package to be build. So I assume some more permanent fix is required. For the moment, %define debug_package %{nil} is the fix. A better fix would require the redhat-rpm-config package to interact more closely with rpmbuild, and that's exactly opposite to what was desired, building -debuginfo packages automagically w/o changing any existing specfile. But yes the configuration is a bit flimsy, can't be helped imho. I find it unacceptable that one has to install a source packae and then edit a spec file where a plain rpmbuild --rebuild should work. Editting individual SPEC files is NOT a workable option. Then do rpm -e redhat-rpm-config and be happy. Off to redhat-rpm-config for closure. I highly suspect that the 'exit 0' at the end of %install is the real cause of the problem. Please remove it instead of using the define. Is there a way to set thin in z central file? Like a .specrc file or something similar instead of changing hundreds of files? Took me a while to realise ~/.rpmmacros is the answer to this bug. If one put's in a line like: %debug_package %{nil} The whole issue is solved. |