-
Notifications
You must be signed in to change notification settings - Fork 63
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
Verbose DNF5 logs in Fedora Copr #3040
Comments
evan-goode
added a commit
to evan-goode/mock
that referenced
this issue
Dec 1, 2023
If DNF 5 sees an "interactive" TTY on stdout, it will try to draw progress bars and cause the Mock logs to be garbled: fedora-copr/copr#3040. A simple fix is to have DNF 5 output to a pipe instead of a PTY. I'm not sure why output is collected via a PTY from yum/dnf (seems to start from commit 99ca2fa), but it's probably no longer needed for DNF 5?
This was referenced Dec 1, 2023
I think rpm-software-management/mock#1261 is the main problem here, but even after changing Mock to invoke DNF 5 with a pipe on stdout and not a PTY, the logs are still garbled due to rpm-software-management/dnf5#1058. |
praiskup
pushed a commit
to evan-goode/mock
that referenced
this issue
Dec 11, 2023
If DNF 5 sees an "interactive" TTY on stdout, it will try to draw progress bars and cause the Mock logs to be garbled: fedora-copr/copr#3040. A simple fix is to have DNF 5 output to a pipe instead of a PTY. I'm not sure why output is collected via a PTY from yum/dnf (seems to start from commit 99ca2fa), but it's probably no longer needed for DNF 5?
praiskup
pushed a commit
to rpm-software-management/mock
that referenced
this issue
Dec 12, 2023
If DNF 5 sees an "interactive" TTY on stdout, it will try to draw progress bars and cause the Mock logs to be garbled: fedora-copr/copr#3040. A simple fix is to have DNF 5 output to a pipe instead of a PTY. I'm not sure why output is collected via a PTY from yum/dnf (seems to start from commit 99ca2fa), but it's probably no longer needed for DNF 5?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So far I deployed
package_manager=dnf5
release only on our staging instance. But the DNF5 logs there are pretty ugly, snippet:It seems that we should either revisit the stdout/stderr filter installed in Mock, or the one we have in
copr-rpmbuild
. Not sure, or maybe there are some options in DNF5 to make the output more "logger" friendly? @evan-goodeThe text was updated successfully, but these errors were encountered: