Drop replacing lines from the table when they are exact replacements

[jan-kolarik]

Exclude replacing lines from the transaction table output when replacing a single package with the same name.

For #326.

[jrohel]

I understand the motivation for this change - fewer rows in the table.
The problem is that useful information is being removed, not just duplicated as stated in the linked issue.

For example, I check from which version to which version the change is happening before approving the upgrade.
Occasionally it happens that a package is replaced by a package with a different architecture, an arch package for noarch and vice versa. Or a package from a different repository.

I understand that not everyone checks what is happening in the system during an upgrade. But I do use this information and it is one of the reasons for me why dnf5 is better than dnf.

I guess we'll have to figure out the "verbosity" of the output somehow, since everyone has different preferences. This PR will satisfy users who want a shorter output at the expense of information (or who have super memory and know exactly what versions and from where they have installed and thus don't need to display it). But it will annoy those who are interested in details. Especially when I manage several different computers I am interested in the exact state of the upgraded computer when upgrading.

[jan-kolarik]

There is an intent to have the verbosity configurable with a default level "not detailed". The verbose mode should be implemented by the #1518 after the discussion in #1191.

[jan-kolarik]

There isn't a consensus within the team on this approach. Let's wait until things settle around the verbose mode, and then we can decide. We can eventually merge it together when the verbose option is ready.

[ewoks]

Hi @jan-kolarik although there is no concensus about verbose mode, additional replacing line (even for exact replacements) became default way even without using --verbose.
If team really believe that this is necessary, let's please find a solution for many annoyed users and allow to turn this off (or make it simpler like with dnf4) by adding new flag --simple-out (or simial) even if it's default.

Would that be a compromise approach team can live with?

[ewoks]

@jan-kolarik can you please shine some light on the status? more and more tickets on this topic are open, it would be great to point users to one place with up-to-date info to manage expectations. Thanks :)

[jan-kolarik]

@jan-kolarik can you please shine some light on the status? more and more tickets on this topic are open, it would be great to point users to one place with up-to-date info to manage expectations. Thanks :)

As of now, I can't provide specific details about this. It's on our radar, and we plan to implement verbose mode and make some changes to the default output—though preferably minimal compared to the current state (mainly wrt "replacing" things). I see this as more of a Q1 2025 or later task, as we're currently overwhelmed with higher-priority work.

[ferdnyc]

As an in-betweening of this, in #785 (comment) I suggested changing the "replacing" line format for same-package replacements from:

<package_name>             <arch> <new_version>   <repo> <size>
  replacing <package_name> <arch> <old_version>   <repo> <size>

to:

<package_name>             <arch> <new_version>   <repo> <size>
  replacing                       <old_version>

Which would help with the line-wrapping issues frequently caused by the overly-long "␣␣replacing <package_name>" lines in the first column.

[ewoks]

@evan-goode failed and it looks like it contains more than you wanted to test