Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (). If you're a Red Hat customer, please continue to file support cases via the . If you're not, please head to the "" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult . That failing, please send an e-mail to the RH Jira admins at to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1786335

Summary: dnf history command output is trimmed because of hardcoded 79 cols limit
Product: Red Hat Enterprise Linux 8 Reporter: Ivan Pesin <ivan.pesin>
Component: dnfAssignee: Nicola Sella <nsella>
Status: CLOSED ERRATA QA Contact: Eva Mrakova <emrakova>
Severity: unspecified Docs Contact:
Priority: medium
Version: 8.4CC: james.antill
Target Milestone: rcKeywords: Triaged
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: Unspecified
OS: Unspecified
Whiteboard:
dnf-4.2.23-1.el8 If docs needed, set a value
---
2020-11-04 01:52:25 UTC Bug
--- ---
---
---
--- RHEL 7.3 requirements from Atomic Host:
---

Description Ivan Pesin 2019-12-24 13:51:48 UTC
Description of problem:

`dnf history` command's output is limited to 79 columns regardless of the actual terminal width. This often results in the commands column being trimmed, and makes it impossible to see the complete history information.

How reproducible:

Execute dnf install/update/remove command with parameters string longer than 24 characters. For example:

 dnf install less vim-enhanced tree bind-utils

Actual results:

[root@localhost cli]# dnf history
ID | Command line | Date and time | Action(s) | Altered
-------------------------------------------------------------------------------
 4 | install patch | 2019-12-24 13:27 | Install | 1
 3 | install tmux iputils mc | 2019-12-24 13:25 | Install | 48
 2 | install less vim-enhance | 2019-12-24 13:19 | Install | 10
 1 | | 2019-12-24 13:12 | Install | 394 EE

Expected results:

[root@localhost cli]# dnf history
ID | Command line | Date and time | Action(s) | Altered
---------------------------------------------------------------------------------------------------------------------------------------------------------
 4 | install patch | 2019-12-24 13:27 | Install | 1
 3 | install tmux iputils mc golang | 2019-12-24 13:25 | Install | 48
 2 | install less vim-enhanced tree bind-utils | 2019-12-24 13:19 | Install | 10
 1 | | 2019-12-24 13:12 | Install | 394 EE

Comment 1 Nicola Sella 2020-01-13 15:53:51 UTC
PR: https://github.com/rpm-software-management/dnf/pull/1567

Comment 2 Nicola Sella 2020-02-06 16:18:15 UTC
(In reply to nsella from comment #1)
> PR: https://github.com/rpm-software-management/dnf/pull/1567

Edit:
A PR that fixes the bug for terminal output was merged. [1]
For redirecting stdout to file there is an enhancement of the previous. [2]

[1] https://github.com/rpm-software-management/dnf/pull/1559
[2] https://github.com/rpm-software-management/dnf/pull/1587

Comment 10 errata-xmlrpc 2020-11-04 01:52:25 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (yum bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:4510