Description of problem: This is a request, a IMHO suggest. Please add to "dnf list" a sign (es. "@" ) to identify the package installed. The actual solution (first installed, then available package) is not useful in some case It's sufficient to re-enable the "@" before the repo to a full "dnf list" command without options. Or a new option "--old-style"? Or any way they deem most appropriate. Version-Release number of selected component (if applicable): Last version How reproducible: With old "dnf list" format it was possible to see which packages were installed (with "@") and which (without "@") is missing and can be installed This is an example [1] and [2]: If "dnf list" provide on line the package state (Installed or Available, example [2]) you can see which packages are not installed, then install it, if it's necessary. Having in the full list first the installed packages and then the available packages not help, then sometimes makes it necessary to reprocess the output with a script. See also this tread: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/KK46GRBHBPW73QXW2TN2MDPIKXVEXSQE/ [1] current "dnf list" output: lesca@dodo:~$ dnf list|grep ^NetworkManager Updating and loading repositories: Repositories loaded. NetworkManager.x86_64 1:1.54.3-2.fc43 updates NetworkManager-adsl.x86_64 1:1.54.3-2.fc43 updates NetworkManager-bluetooth.x86_64 1:1.54.3-2.fc43 updates NetworkManager-config-connectivity-fedora.noarch 1:1.54.3-2.fc43 updates NetworkManager-libnm.x86_64 1:1.54.3-2.fc43 updates NetworkManager-libnm-devel.x86_64 1:1.54.3-2.fc43 updates NetworkManager-openconnect.x86_64 1.2.10-9.fc43 fedora NetworkManager-openconnect-gnome.x86_64 1.2.10-9.fc43 fedora NetworkManager-openvpn.x86_64 1:1.12.5-1.fc43 updates NetworkManager-openvpn-gnome.x86_64 1:1.12.5-1.fc43 updates NetworkManager-ppp.x86_64 1:1.54.3-2.fc43 updates NetworkManager-pptp.x86_64 1:1.2.12-10.fc43 fedora NetworkManager-pptp-gnome.x86_64 1:1.2.12-10.fc43 fedora NetworkManager-ssh.x86_64 1.4.2-1.fc43 updates NetworkManager-ssh-gnome.x86_64 1.4.2-1.fc43 updates NetworkManager-ssh-selinux.x86_64 1.4.2-1.fc43 updates NetworkManager-sstp.x86_64 1:1.3.1-12.fc43 fedora NetworkManager-sstp-gnome.x86_64 1:1.3.1-12.fc43 fedora NetworkManager-tui.x86_64 1:1.54.3-2.fc43 updates NetworkManager-vpnc.x86_64 1:1.4.0-4.fc43 fedora NetworkManager-vpnc-gnome.x86_64 1:1.4.0-4.fc43 fedora NetworkManager-wifi.x86_64 1:1.54.3-2.fc43 updates NetworkManager-wwan.x86_64 1:1.54.3-2.fc43 updates NetworkManager-cloud-setup.x86_64 1:1.54.3-2.fc43 updates NetworkManager-config-server.noarch 1:1.54.3-2.fc43 updates NetworkManager-fortisslvpn.x86_64 1.4.1-10.20231021gite201da5.fc43 fedora NetworkManager-fortisslvpn-gnome.x86_64 1.4.1-10.20231021gite201da5.fc43 fedora NetworkManager-iodine.x86_64 1.2.0-25.fc43 fedora NetworkManager-iodine-gnome.x86_64 1.2.0-25.fc43 fedora NetworkManager-l2tp.x86_64 1.52.0-1.fc43 updates NetworkManager-l2tp-gnome.x86_64 1.52.0-1.fc43 updates NetworkManager-libnm.i686 1:1.54.3-2.fc43 updates NetworkManager-libnm-devel.i686 1:1.54.3-2.fc43 updates NetworkManager-libreswan.x86_64 1.2.30-1.fc43 updates NetworkManager-libreswan-gnome.x86_64 1.2.30-1.fc43 updates NetworkManager-ovs.x86_64 1:1.54.3-2.fc43 updates NetworkManager-strongswan.x86_64 1.6.0-10.fc43 fedora NetworkManager-strongswan-gnome.x86_64 1.6.0-10.fc43 fedora NetworkManager-team.x86_64 1:1.54.3-2.fc43 updates In this example[1] you cannot know what package are installed and what not [2] old style similar output lesca@dodo:~$ dnf list|awk 'BEGIN{p=" (Installed)"} $0~/^$/{p=""} NF==3{print $0 p}'|grep ^NetworkManager Updating and loading repositories: Repositories loaded. NetworkManager.x86_64 1:1.54.3-2.fc43 updates (Installed) NetworkManager-adsl.x86_64 1:1.54.3-2.fc43 updates (Installed) NetworkManager-bluetooth.x86_64 1:1.54.3-2.fc43 updates (Installed) NetworkManager-config-connectivity-fedora.noarch 1:1.54.3-2.fc43 updates (Installed) NetworkManager-libnm.x86_64 1:1.54.3-2.fc43 updates (Installed) NetworkManager-libnm-devel.x86_64 1:1.54.3-2.fc43 updates (Installed) NetworkManager-openconnect.x86_64 1.2.10-9.fc43 fedora (Installed) NetworkManager-openconnect-gnome.x86_64 1.2.10-9.fc43 fedora (Installed) NetworkManager-openvpn.x86_64 1:1.12.5-1.fc43 updates (Installed) NetworkManager-openvpn-gnome.x86_64 1:1.12.5-1.fc43 updates (Installed) NetworkManager-ppp.x86_64 1:1.54.3-2.fc43 updates (Installed) NetworkManager-pptp.x86_64 1:1.2.12-10.fc43 fedora (Installed) NetworkManager-pptp-gnome.x86_64 1:1.2.12-10.fc43 fedora (Installed) NetworkManager-ssh.x86_64 1.4.2-1.fc43 updates (Installed) NetworkManager-ssh-gnome.x86_64 1.4.2-1.fc43 updates (Installed) NetworkManager-ssh-selinux.x86_64 1.4.2-1.fc43 updates (Installed) NetworkManager-sstp.x86_64 1:1.3.1-12.fc43 fedora (Installed) NetworkManager-sstp-gnome.x86_64 1:1.3.1-12.fc43 fedora (Installed) NetworkManager-tui.x86_64 1:1.54.3-2.fc43 updates (Installed) NetworkManager-vpnc.x86_64 1:1.4.0-4.fc43 fedora (Installed) NetworkManager-vpnc-gnome.x86_64 1:1.4.0-4.fc43 fedora (Installed) NetworkManager-wifi.x86_64 1:1.54.3-2.fc43 updates (Installed) NetworkManager-wwan.x86_64 1:1.54.3-2.fc43 updates (Installed) NetworkManager-cloud-setup.x86_64 1:1.54.3-2.fc43 updates NetworkManager-config-server.noarch 1:1.54.3-2.fc43 updates NetworkManager-fortisslvpn.x86_64 1.4.1-10.20231021gite201da5.fc43 fedora NetworkManager-fortisslvpn-gnome.x86_64 1.4.1-10.20231021gite201da5.fc43 fedora NetworkManager-iodine.x86_64 1.2.0-25.fc43 fedora NetworkManager-iodine-gnome.x86_64 1.2.0-25.fc43 fedora NetworkManager-l2tp.x86_64 1.52.0-1.fc43 updates NetworkManager-l2tp-gnome.x86_64 1.52.0-1.fc43 updates NetworkManager-libnm.i686 1:1.54.3-2.fc43 updates NetworkManager-libnm-devel.i686 1:1.54.3-2.fc43 updates NetworkManager-libreswan.x86_64 1.2.30-1.fc43 updates NetworkManager-libreswan-gnome.x86_64 1.2.30-1.fc43 updates NetworkManager-ovs.x86_64 1:1.54.3-2.fc43 updates NetworkManager-strongswan.x86_64 1.6.0-10.fc43 fedora NetworkManager-strongswan-gnome.x86_64 1.6.0-10.fc43 fedora NetworkManager-team.x86_64 1:1.54.3-2.fc43 updates In this example[2] you can see which package are installed and which are missing and can install it
Do I understand that your want all information on a single line because you grep the output? That sounds like a desire for machine-parsable output. For that case DNF5 adds JSON output and that should be the way instead of making the human-readable output more complicated. Though "dnf5 list" does not yet implements --json option. However, I recommend you other approach: Use --installed or --available options if you want list of installed or a list of available packages. This you don't have to guess.
Upstream issue for the machine-parsable output for the list command: https://github.com/rpm-software-management/dnf5/issues/2551 Also, you can use globs for the list argument to filter specified packages instead of listing all packages and grepping the output. E.g. `dnf list NetworkManager*`