I am a Fedora user. When I receive updates of number of packages. Example in total :
The discover says that,
It is 1.5 GB while as dnf says that it is 552 MB. Why is this ?
It fetches updates from rpm repos, why not fetch the sizes too. The same case applies for flatpak too.
The update will be about 15MB or so for FreeDesktop runtimes but it will show full size of the package as if I downloading for the first time.
Is this the same in debian based ones too ?
I think this is being fixed in Plasma 6.3 if I follow the digest weekly in correct order. Am I right, @ngraham ?
Not sure, it doesn’t ring any bells. The way the size is calculated probably differs between the sources. One is likely not including all dependencies in its calculation.
Well, you seem to write that in every “This week in Plasma” post recently.
So, I hope it is.
On recent announcements, perhaps you might be thinking of the work to more accurately reflect progress for Flatpaks by accounting for the runtimes as well - 494781 – No progress on "tasks" section while downloading Flatpak runtimes - or the change to only show size estimates once the update checks are actually complete - updates: Don't show the total size until updates have been fetched (!949) · Merge requests · Plasma / Discover · GitLab ?
For Flatpaks, Discover can only show what Flatpak is aware of itself. Providing accurate size estimates for updates is an outstanding item for that upstream project:
For Fedora packages, that information is coming from PackageKit, via its dnf backend. That backend, at least from the examples I’ve looked at on my system, seems to be providing the end-state installed size of the updated programs, rather than the size of the packages to be downloaded - presumably because of Install size versus download size in PkDetails by mcrha · Pull Request #476 · PackageKit/PackageKit · GitHub - see my example here:
For Fedora 41 and beyond, there’s likely to be some more work needed to either adapt the dnf PackageKit backend to fully work with DNF5, or to develop another plugin path for Discover to interact with DNF5 directly outside of PackageKit entirely - some discussion about that so far was had here: 480525 – Custom backend for DNF5
Hope that helps,
