Bug 613010
Summary: | Strange error message from rpmbuild | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Richard W.M. Jones <rjones> |
Component: | rpm | Assignee: | Jindrich Novy <jnovy> |
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | ffesti, jnovy, n3npq, pknirsch, pmatilai |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-07-13 12:10:32 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
Richard W.M. Jones
2010-07-09 14:16:11 UTC
The message is rather cryptic but makes perfect sense. Note that you have Version: %{version} at line 2 in the spec file what leads macro evaluator to infinite loop when evaluating Source0 at line 9 in spec: Source0: http://people.redhat.com/~rjones/guestfs-browser/files/guestfs-browser-%{version}.tar.gz Please fix your spec file. I'm not an idiot. I understand there is a problem with the spec file, but the error message doesn't say anything useful such as "you shouldn't use symbol %{version} recursively". All macro processors do not have sufficient context to provide useful errot messages in situ, largely because there are multiple contexts associated. But sure a better error message could/should/would help. So would better input to the macro expansion. Fixed upstream. The new error message now looks like: error: Too many levels of recursion in macro expansion. It is likely caused by recursive macro declaration. error: line 10: Source0: http://people.redhat.com/~rjones/guestfs-browser/files/guestfs-browser- and the macro stack backtrace is now redirected to debug log in order to avoid user confusion. Much better, thanks. |