Bug 1888216

Summary: "dnf history" output has table formatting broken
Product: [Fedora] Fedora Reporter: Kamil Páral <kparal>
Component: dnfAssignee: Nicola Sella <nsella>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: low    
Version: 33CC: dmach, geraldo.simiao.kutz, jmracek, jrohel, mblaha, mhatina, nsella, packaging-team-maint, pkratoch, rpm-software-management, vmukhame
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 09:34:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
80x24.png
none
reasonable-size.png
none
maximized.png none

Description Kamil Páral 2020-10-14 12:31:02 UTC 
"dnf history" used to print in a nicely-formatted table (according to the terminal width). But some new dnf version broke it and now it doesn't respect the terminal width and instead prints in a maximum width. The result is that I can't use "dnf history" output in any reasonable way, even if I enlarge my terminal to a maximum size.

See screenshots.
Comment 1 Kamil Páral 2020-10-14 12:31:32 UTC 
Created attachment 1721456 [details]
80x24.png
Comment 2 Kamil Páral 2020-10-14 12:31:38 UTC 
Created attachment 1721457 [details]
reasonable-size.png
Comment 3 Kamil Páral 2020-10-14 12:31:43 UTC 
Created attachment 1721458 [details]
maximized.png
Comment 4 Kamil Páral 2020-10-14 12:32:39 UTC 
dnf-4.4.0-2.fc33.noarch
Comment 5 Geraldo Simião 2020-10-22 13:14:14 UTC 
Kamil, I didn't see that on F33KDE

Shell: bash 5.0.17 
Resolution: 1366x768 
DE: Plasma 5.19.5
Terminal: konsole
Comment 6 Nicola Sella 2020-10-27 09:34:58 UTC 
There is a f32 bug tracking the same issue, so I would mark this as a duplicate.
The PR [1,2] should address the issue and deliver the fix as soon as it merged
in the next fedora release. Feel free to reopen if the fix does not fit.
The wrong behaviour was introduced in dnf-4.2.23.

[1] dnf:  https://github.com/rpm-software-management/dnf/pull/1636
[2] test: https://github.com/rpm-software-management/ci-dnf-stack/pull/902

*** This bug has been marked as a duplicate of bug 1852577 ***