https://bugs.kde.org/show_bug.cgi?id=513220
--- Comment #2 from John <[email protected]> --- (In reply to Nate Graham from comment #1) > Can reproduce on KDE Linux too (which has git master of everything); looks > like it's not backend-specific. I was also a bit "lucky" a few minutes ago for a few moments, with something being slower than usual (the servers or the networks) an I could see that it's doing something like these steps: Refreshing Debian / GNU Linux forky/sid Refreshing Flatpak Refreshing Debian / GNU Linux forky/sid Refreshing Debian / GNU Linux forky/sid But it's still very fast and confusing on what exactly is doing and in what order. And why the output is: 1 line 2 lines 1 line Plus I wish it would be consistent with the names like: Refreshing the (stable|testing|unstabe) repository of APT Refreshing the (stable|beta) repository Flatpak OR: Refreshing the (stable|testing|unstabe) repository of Debian Refreshing the (stable|beta) repository of Flathub So either show the packaging formats' names or the repositories' names! I'm more interested in which repositories are contacted and which branch of them than for which packaging format. And for APT, I am interested to see also which mirror has been contacted as we can put multiple ones in the configuration. Especially if we use Nala that makes finding and using the fastest mirrors really easy with the fetch command. https://github.com/volitank/nala?tab=readme-ov-file#fetch IF APT term is shown, it must be written exactly like that as it's an acronym: https://en.wikipedia.org/wiki/APT_(software) Thanks and good luck with whatever you can fix / improve here! -- You are receiving this mail because: You are watching all bug changes.
