Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Output aesthetics #1901

Open
birdie-github opened this issue Nov 25, 2024 · 6 comments
Open

Output aesthetics #1901

birdie-github opened this issue Nov 25, 2024 · 6 comments

Comments

@birdie-github
Copy link

When you run dnf update in F41 you see:

Updating and loading repositories:
 google-chrome
 Fedora 41 - x86_64 - Updates
 google-chrome
 Fedora 41 - x86_64 - Updates

The first two lines refer to the repos metadata, the second two lines are the repos actual content.

Would be nice if DNF actually spelled it out. Otherwise people may think it does something twice unnecessarily.

Something akin to:

Updating repositories metadata:
 google-chrome
 Fedora 41 - x86_64 - Updates
Loading repositories:
 google-chrome
 Fedora 41 - x86_64 - Updates
@kontura
Copy link
Contributor

kontura commented Nov 26, 2024

We will probably need additional information because this doesn't happen for me.
I get:

user@toolbox ~ $ sudo dnf5 update --refresh
Updating and loading repositories:
 Fedora 41 - x86_64 - Updates                                                                    100% | 100.9 KiB/s |  27.1 KiB |  00m00s
 RPM Fusion for Fedora 41 - Free - Updates                                                       100% |  44.3 KiB/s |   6.8 KiB |  00m00s
 Fedora 41 - x86_64                                                                              100% | 135.6 KiB/s |  23.3 KiB |  00m00s
Repositories loaded.
Nothing to do.

The same repo shouldn't show up twice.
Can you share your repository and dnf configuration?

@birdie-github
Copy link
Author

birdie-github commented Nov 26, 2024

dnf.conf
# see `man dnf.conf` for defaults and possible options

[main]
gpgcheck=True
installonly_limit=3
clean_requirements_on_remove=True
best=False
skip_if_unavailable=True
deltarpm=false
max_parallel_downloads=20

Repos:

rpm -qf /etc/yum.repos.d/*
fedora-repos-41-1.noarch
fedora-repos-41-1.noarch
fedora-repos-41-1.noarch
fedora-repos-41-1.noarch
file /etc/yum.repos.d/google-chrome.repo is not owned by any package

All files by default. rpm -V fedora-repos-41-1.noarch; echo $?; 0

@kontura
Copy link
Contributor

kontura commented Nov 26, 2024

Ok, I still cannot reproduce it.
I am trying this in a container:

$ podman run -ti fedora:41
[root@89d43705870b /]# dnf update
Updating and loading repositories:
 Fedora 41 - x86_64                                                                              100% |   2.9 MiB/s |  35.4 MiB |  00m12s
 Fedora 41 openh264 (From Cisco) - x86_64                                                        100% |   8.2 KiB/s |   4.8 KiB |  00m01s
 Fedora 41 - x86_64 - Updates                                                                    100% |   1.6 MiB/s |   5.5 MiB |  00m03s
Repositories loaded.
Nothing to do.

Does this work for you?
Can you create a reproducer?

@birdie-github
Copy link
Author

birdie-github commented Nov 26, 2024

This must be absolutely happening for you as well:

Updating and loading repositories:
 Fedora 41 - x86_64 - Updates  100% |  12.4 KiB/s |  27.1 KiB |  00m02s
 Fedora 41 - x86_64 - Updates  100% | 238.9 KiB/s |   1.2 MiB |  00m05s

27.1 KiB vs 1.2 MiB - definitely the first line indicates the repo metadata being updated.

I can upload strace -f output if you need it. But darn, it's huge and very difficult to read.

@kontura
Copy link
Contributor

kontura commented Nov 26, 2024

I see, there must be something wrong when updating the lines in your terminal emulator.
There is supposed to be only one line per repo that gets updated.

Can you share what terminal emulator are you using and potentially try with something else?

@birdie-github
Copy link
Author

I'm using xfce4-terminal 1.1.3.

Maybe you're right but then I've never had any issues with it before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants