Bug 1235901 - Add description to a dnf transaction
Summary: Add description to a dnf transaction
Keywords:
Status: CLOSED DUPLICATE of bug 1192684
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 22
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-26 04:25 UTC by Peter Tselios
Modified: 2015-06-26 11:25 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-26 11:25:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1218401 0 low CLOSED [doc] document history_list_view and set it to cmd by default 2021-02-22 00:41:40 UTC

Internal Links: 1218401

Description Peter Tselios 2015-06-26 04:25:22 UTC
Description of problem:
when you search the history, you can see the timestamp of the action, the action itself and the number of packages included in the transaction. However, you have no information about it. What was the original command, or why you installed that package. 

For example, it would be great to use dnf history list and have a list like the following:

ID     | Description          | Date a           | Action  | Altere  | User 
-------------------------------------------------------------------------------
...
4001   | Change Control #1233 | 2014-06-24 09:01 | Install |    8  < | Me
4000   | Install oVirt        | 2014-06-24 09:01 | Install |    8  < | Me
...

That could be implemented with a "--description" directive in the dnf [install
erase] action, like for example:

dnf install oVirt --description "Install oVirt"
dnf install package123 --description "Change Control #1233"

Comment 1 Honza Silhan 2015-06-26 11:25:51 UTC
I believe this is a duplicate. Now you are the second person requesting this feature. It could be handy in layered images too, to see what packages were installed in which image from running container. Maybe you want a little more helpful output of history list too (bug 1218401).

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


Note You need to log in before you can comment on or make changes to this bug.