-
Notifications
You must be signed in to change notification settings - Fork 102
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
Document that a transaction progress is printed to an error output instead of to a standard output #2116
Comments
This can be reproduced locally like so:
|
This is caused by this change: #1641 |
Neal, bare-bone reproducer please. I'm not going learn what Kiwi is, how to run it and investigate how Kiwi executed DNF. |
But yes, DNF5 prints transaction summary to stdout and transaction progress, as all progressbars, to stderr. According to that pull request it's a feature. I recommend you fixing Kiwi to capture stderr too. Otherwise, you will miss error messages. |
I will ask other teammates, but I'm keen rejecting this request as transaction progress is a "verbose debugging" output. |
It's straight up a regression from DNF4 that this output was moved to stderr.
Bare-bones reproducer is to just run dnf through subprocess without redirecting stderr into stdout. Please also endeavor to be courteous. I filed this issue while discussing it during the DNF community meeting. I provided the information that was asked. And you will have to know about kiwi anyway, since we use it for almost half of Fedora images now. |
We've decided to keep the status quo of which messages are printed on stdout vs stderr. I don't consider these changes a regression from DNF 4 since they did resolve #1361, and things like Kiwi should be logging stderr (and possibly capturing dnf5.log) anyway. But I realize the changes from #1641 are not documented on https://dnf5.readthedocs.io/en/latest/changes_from_dnf4.7.html, so we should update it. |
I noticed that DNF isn't printing out all the install step output when it is run inside of kiwi (essentially python subprocess piped to a python logger). It looks something like this:
Full log is available here: https://kojipkgs.fedoraproject.org//packages/Fedora-KDE-Desktop-Live/42_Beta/1.2/data/logs/image/x86_64/image-root.x86_64.log
I expect the output to look more like what it does in mock root.log where it shows the downloading and installing progress steps, like in this file: https://kojipkgs.fedoraproject.org//packages/Fedora-KDE-Desktop-Live/42_Beta/1.2/data/logs/image/x86_64/root.log
(This was discussed in the community meeting and filed as an issue accordingly.)
The text was updated successfully, but these errors were encountered: