New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFE: useful lua errors #545
Comments
Agree. The error message does not help a lot. Some additional info containing whole %anotherluamacro can improve the situation. |
The top macro name you're seeing is simply the line in the spec. Try --trace (or in older versions that don't support it, --eval '%trace') for more advanced macro debugging. |
Thanks for the pointer! However that does not help a lot when you are mass building in mock (the general case nowadays), and the only debugging help are mock logs, and mock has already cleaned up all rpm temporary files |
Nod. Makes me think that perhaps we should default to macro tracing on when building packages, at least in non-quiet mode. |
This is broader than just Lua, rpm should really print out a "traceback" on macro errors. There's even some code to do that but I guess its not working as it should (shock horror) |
Should make macro debugging a little saner, including but not limited to Lua. Fixes: rpm-software-management#545
Right now rpm prints out lua syntax errors with line numbers, but forgets to print the macro in which those lines can be found
When several lua macros call each other finding the one which is erroring becomes quite tricky. rpm only points out the top macro name
For example
rpm will notify there is an error in %luamacro if %anotherluamacro has a syntax error, instead of notifying the error is in line x of %anotherluamacro
The text was updated successfully, but these errors were encountered: