closest I could get was the output from sudo dnf repoinfo and then eyeballing by hand… err… eye and hoping it didn’t change for the actual pull of the repo itself.
Would be nice to see which server was supplying the repository information, however.
Yes, all the repos have metalinks, however I am using the dnf override .repo you showed me in another thread - which I have confirmed does work, but the repo I connect to not show in with dnf --dump-repo-config=*
So while I have verified that me last download came from the mirror specified in the override .repo - I still want to know proactively what repo I will connect to.
Excellent and very informative command. I highly recommend anyone interested in how dnf works to run it.
It is too long to post it all but here is a sample.
$ tail -n 10 -f /var/log/dnf5.log
2025-10-27T16:01:35+0000 [12713] DEBUG No modules metadata available for repo rpmfusion-free-updates
2025-10-27T16:01:35+0000 [12713] DEBUG Loading solv cache file: "/var/cache/libdnf5/rpmfusion-nonfree-updates-c00cb99192127d50/solv/rpmfusion-nonfree-updates.solv"
2025-10-27T16:01:35+0000 [12713] DEBUG No updateinfo metadata available for repo "rpmfusion-nonfree-updates"
2025-10-27T16:01:35+0000 [12713] DEBUG Loading solv cache file: "/var/cache/libdnf5/rpmfusion-nonfree-updates-c00cb99192127d50/solv/rpmfusion-nonfree-updates-group.solvx"
2025-10-27T16:01:35+0000 [12713] DEBUG No modules metadata available for repo rpmfusion-nonfree-updates
2025-10-27T16:01:35+0000 [12713] DEBUG Loading solv cache file: "/var/cache/libdnf5/rpmfusion-nonfree-a1eaa2e306b49749/solv/rpmfusion-nonfree.solv"
2025-10-27T16:01:35+0000 [12713] DEBUG No updateinfo metadata available for repo "rpmfusion-nonfree"
2025-10-27T16:01:35+0000 [12713] DEBUG Loading solv cache file: "/var/cache/libdnf5/rpmfusion-nonfree-a1eaa2e306b49749/solv/rpmfusion-nonfree-group.solvx"
2025-10-27T16:01:35+0000 [12713] DEBUG No modules metadata available for repo rpmfusion-nonfree
2025-10-27T16:01:35+0000 [12713] INFO DNF5 finished
2025-10-27T16:51:54+0000 [29725] INFO --- DNF5 launched with arguments: "dnf update --refresh" ---
2025-10-27T16:51:54+0000 [29725] DEBUG Loading plugin file="/usr/lib64/dnf5/plugins/builddep_cmd_plugin.so"
2025-10-27T16:51:54+0000 [29725] INFO Loaded dnf5 plugin "builddep" ("/usr/lib64/dnf5/plugins/builddep_cmd_plugin.so") version "1.0.0"
2025-10-27T16:51:54+0000 [29725] DEBUG Loading plugin file="/usr/lib64/dnf5/plugins/changelog_cmd_plugin.so"
2025-10-27T16:51:54+0000 [29725] INFO Loaded dnf5 plugin "changelog" ("/usr/lib64/dnf5/plugins/changelog_cmd_plugin.so") version "1.0.0"
2025-10-27T16:51:54+0000 [29725] DEBUG Loading plugin file="/usr/lib64/dnf5/plugins/config-manager_cmd_plugin.so"
2025-10-27T16:51:54+0000 [29725] INFO Loaded dnf5 plugin "config-manager" ("/usr/lib64/dnf5/plugins/config-manager_cmd_plugin.so") version "0.1.0"
2025-10-27T16:51:54+0000 [29725] DEBUG Loading plugin file="/usr/lib64/dnf5/plugins/copr_cmd_plugin.so"
2025-10-27T16:51:54+0000 [29725] INFO Loaded dnf5 plugin "copr" ("/usr/lib64/dnf5/plugins/copr_cmd_plugin.so") version "0.1.0"
2025-10-27T16:51:54+0000 [29725] DEBUG Loading plugin file="/usr/lib64/dnf5/plugins/needs_restarting_cmd_plugin.so"
2025-10-27T16:51:54+0000 [29725] INFO Loaded dnf5 plugin "needs_restarting" ("/usr/lib64/dnf5/plugins/needs_restarting_cmd_plugin.so") version "1.0.0"
2025-10-27T16:51:54+0000 [29725] DEBUG Loading plugin file="/usr/lib64/dnf5/plugins/repoclosure_cmd_plugin.so"
2025-10-27T16:51:54+0000 [29725] INFO Loaded dnf5 plugin "repoclosure" ("/usr/lib64/dnf5/plugins/repoclosure_cmd_plugin.so") version "1.0.0"
2025-10-27T16:51:54+0000 [29725] DEBUG Loading plugin file="/usr/lib64/dnf5/plugins/repomanage_cmd_plugin.so"
2025-10-27T16:51:54+0000 [29725] INFO Loaded dnf5 plugin "repomanage" ("/usr/lib64/dnf5/plugins/repomanage_cmd_plugin.so") version "1.0.0"
2025-10-27T16:51:54+0000 [29725] DEBUG Loading plugin file="/usr/lib64/dnf5/plugins/reposync_cmd_plugin.so"
2025-10-27T16:51:54+0000 [29725] INFO Loaded dnf5 plugin "reposync" ("/usr/lib64/dnf5/plugins/reposync_cmd_plugin.so") version "1.0.0"
2025-10-27T16:51:54+0000 [29725] DEBUG Loading plugin library file="/usr/lib64/libdnf5/plugins/expired-pgp-keys.so"
2025-10-27T16:51:54+0000 [29725] INFO Loaded libdnf plugin "expired-pgp-keys" ("/usr/lib64/libdnf5/plugins/expired-pgp-keys.so"), version="1.0.0"
and etc
However it does not show which mirror I will connect to.
On the upside I am learning a lot about how dnf mirror manager works.
Note also I am using an override file in /etc/dnf/repos.override.d/ which I believe I have confirmed will be respected during downloads and updates, but is not shown in tail while running dnf update
No. Good point, I was wondering how quickly the mirror from the mirror manager would change.
But as I want to use this command to verify if manually added mirrors or overrides are working, I think that it is good enough and I am satisfied.
That’s what I was trying to say up top - it shows the mirror currently being used, but not necessarily the one which will be used for the actual pull, as there’s every chance a load balancer or a VIP will kick in and route the actual update to another of the “(21 more)” referred to as an example.
You are correct, I had an error in my repo override so it did not click at the time.
In the upside I learnt a lot about DNF along the thread.
As you got the solution first I have reassigned it to you, thanks everyone for the fantastic help.