Bug 2269779 - dnf5 info no color package name
Summary: dnf5 info no color package name
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf5
Version: 39
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: rpm-software-management
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-03-16 09:06 UTC by Vincent L
Modified: 2024-04-10 09:10 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)
Info output at dnf5-5.1.15-1.fc40.x86_64 (171.76 KB, image/jpeg)
2024-03-18 13:29 UTC, Geraldo Simião
no flags Details

Description Vincent L 2024-03-16 09:06:31 UTC
With 'dnf5 info <package>', The package name is not colored with certain packages. For example, does not work with httpd php python3.


NAME="Fedora Linux"
VERSION="39 (Container Image)"

dnf5 version 5.1.14
dnf5 plugin API version 1.0
libdnf5 version 5.1.14
libdnf5 plugin API version 1.0


Reproducible: Always

Steps to Reproduce:
1.run podman fedora-39 container
2.dnf install dnf5 dnf5-plugins
3.dnf5 info php
Actual Results:  
name package is not colored

Expected Results:  
name package green color

Comment 1 Geraldo Simião 2024-03-18 13:27:29 UTC
do you have php installed? I see here at F40 (dnf5-5.1.15-1.fc40.x86_64) that installed packages show with the name in green color, and only available packages (not installed) shows in white color.

Comment 2 Geraldo Simião 2024-03-18 13:29:26 UTC
Created attachment 2022336 [details]
Info output at dnf5-5.1.15-1.fc40.x86_64

Comment 3 Vincent L 2024-03-19 17:14:29 UTC
The package is not installed and therefore not colored. If I install the package, the name is colored.
The behavior is different in dnf4. I didn't see this change in the change log, so I thought it was bad behavior, but it looks OK.

Comment 4 Jan Kolarik 2024-04-10 09:10:27 UTC
Hi, thanks for the report. We should mention the change in behavior in the docs.


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