Felix Uhl

Notes: - current latest version of xcp (without the flag) is v0.21.3 - check at https://github.com/tarka/xcp/releases if a new version is available - submit upgrade PR to nixpkgs if necessary...

xcp 0.22.0 was released, nixpkgs PR opened: https://github.com/NixOS/nixpkgs/pull/355776

> we could even allow users to specify zfs and then we print out a helpful error message Ah yes that's a better option than the user simply seeing "value...

Ah, and we should probably make this change a two-step process by first issuing warnings when a user specifies a `format` that we don't know about, and encourage posting an...

Good example of why an inclusive list will be a breaking change: #840

I tried to implement the less controversial solution (assertions), but haven't succeeded yet. The obvious first thing to do was to add an assertion to `_config`: ```diff _config = lib.mkOption...

You can try to use `--mode format`, which shouldn't destroy anything, but also is not able to apply all changes automatically. If you don't have important data yet, you can...

Ahhh we released the update to the docs without releasing the change itself, that was dumb. Please use `--mode disko` for now.

It might be enough to implement this check by changing [the type definition of `start`](https://github.com/nix-community/disko/blob/51994df8ba24d5db5459ccf17b6494643301ad28/lib/types/gpt.nix#L98). A good example is [the type of `size` just a few lines above](https://github.com/nix-community/disko/blob/51994df8ba24d5db5459ccf17b6494643301ad28/lib/types/gpt.nix#L84).

Why? I feel like it's a very good thing that all our examples are tests. This means that no matter what's on master, all examples are always guaranteed to work,...