Zst:chunked FAQ

  1. Does the implementation of zst:chunked in Universal Blue images require additional maintenance from the zst:chunked implementation in Fedora 41 (or else, it brings added bandwidth performance “for free”) ?
  2. Will every Universal Blue images (Bazzite, Bluefin, Aurora, uCore, …) and channels (gts, stable, latest, …) will have zstd:chucked in the future, or only some of them due to limitations ?
  3. Would zst:chunked mitigate the current “major caveats using rpm-ostree” (if not all nor none, which ?) ?

I switched to stable, where I am currently, because of how big the updates were every day

See

If the latest channel updates size gets reduced (due to zstd:chuncked) I would switch back to it

  1. No, that’s for Fedora, we’ll be compressing our images with it when bootc lands support for it.

  2. Yes, all the images will have it once we implement it.

  3. No, layering doesn’t change.

2 Likes

Understood, thanks !

Hey, will Bluefin reinstall required when Zst:chunked arrives?

No it’s all done on the github side, no action will be necessary on your part.

It seems to have been rejected on 2024-08-19 ??

Also see

Edit

Apparently, the correct phrasing should probably be “postponned”

See my comment right bellow

zst:chunked is postponed (ideally v42)

See

https://pagure.io/cloud-image-uploader/issue/34

from