[Rpm-maint] [rpm-software-management/rpm] RFE: log autodep/autoprov calls if something writes to stdout (#620)

[nim-nim]

I had to deal recently with an upstream, whose state caused one of the autodep commands to write to stderr (and not output  any of the the expected deps). I think the language the autodep binary is written in allows non-blocking errors. Traces are written to stderr, but processing tries to continue anyway, even though it is usually already doomed, pretty awful for robustness, but that's the language designer choice.

rpm build logs only showed this unhelpful low-level trace, with no indication on which autodep command was erroring, and what were the arguments passed to it. Debugging proved quite tricky.

Please enhance rpm so, when an autodep/autoprov writes to stderr, rpm also prints the command call that resulted in this stderr writing, with all the parameters rpm passed to it.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/620
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20190121/03b164f4/attachment.html>