-
Notifications
You must be signed in to change notification settings - Fork 235
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
dnf5: Don't output to a PTY #1261
dnf5: Don't output to a PTY #1261
Conversation
Thank you for the patch!
Seems so. Look like pty was historically needed to get some more output from dnf. OTOH, with the patch applied the output isn't much better:
|
Yes, I should have linked this also: rpm-software-management/dnf5#1058 (I mentioned it in fedora-copr/copr#3040). It will hopefully be a quick fix. That issue comes up not just with mock, but in general when piping DNF 5's output. |
Otherwise LGTM |
It would be nice if you dropped a quick bugfix release-note entry into |
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?
df855a4
to
26e42d1
Compare
Looks good, thanks. |
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?