Well, one part of it is that Flatpak pulls data over the network, and sometimes data sent over a network doesn’t arrive in the exact same shape as when it left the original system, which results in that same data being sent in multiple copies - until one manages to arrive correctly.
Hence why Fedora Linux actually recently removed delta updates for DNF. Turns out it used more data in retries than just downloading a whole package again.
I am learning flatpak. Can someone explain why is like that???
Well, one part of it is that Flatpak pulls data over the network, and sometimes data sent over a network doesn’t arrive in the exact same shape as when it left the original system, which results in that same data being sent in multiple copies - until one manages to arrive correctly.
Hence why Fedora Linux actually recently removed delta updates for DNF. Turns out it used more data in retries than just downloading a whole package again.
Interesting, didnt know that! That sounds like a fixable issue though…
I think they have moved from trying to fix it in DNF, to using the capabilities found in BTRFS for Copy on write. Can’t quite remember exactly.
Could also be that the HTTP server lied about the content length.
something something ostree and how complicated the stuff it does actually is
I mean ostree is just git for binaries, isnt it?
But it will likely be the issue here.