Timothée Ravier

Not sure how robust this would be in case of power failures as we would need to update two places at the same time every time we do a new...

We would have one UKI per boot entry in all cases, even if they are the same files as vfat has no hardlinks.

This part of the boot specification might be relevant too to avoid creating two different mechanisms: https://github.com/uapi-group/specifications/blob/main/specs/boot_loader_specification.md#boot-counting

FYI, discussion is in https://gitlab.gnome.org/GNOME/Incubator/Submission/-/issues/11

Given that we have https://gitlab.gnome.org/GNOME/Incubator/Submission/-/issues/11#note_2080742 (and the next message) as a decision, should we resubmit this app under a different name?

From "rpm-ostree": ``` error: Importing: Unencapsulating base: Unhandled layer type: application/vnd.oci.image.layer.v1.tar+zstd ```

Unfortunately https://github.com/ostreedev/ostree-rs-ext/pull/615 is for `zstd` only, not `zstd:chunked` which is not supported by the [oci_spec library](https://docs.rs/oci-spec/latest/oci_spec/image/enum.MediaType.html#variants) yet.

For reference: https://github.com/containers/storage/pull/775

~~Note for people coming to this issue: You should be able to overlay the RPM package from the COPR build on Silverblue.~~

My bad, it looks like the script directly writes to `/lib`: https://github.com/bayasdev/envycontrol/blob/main/envycontrol.py#L202 This is not recommended, on any distributions, not just Silverblue. Custom local udev rules should be installed in...