Jonathan Lebon

> We already do that today We're only checking for `OSTREE_REPO_COMMIT_STATE_PARTIAL` in that path, right? I meant actually traversing the commit in the non-partial case to make sure it really...

> I’d be much more in favour of something magical, which doesn’t require manually retrying the operation. OK yeah, that makes sense to me, regardless of whatever implementation we settle...

This oddly works now in a locally built FCOS live ISO and PXE artifacts: ``` [root@localhost ~]# rpm-ostree status State: idle Deployments: ● ostree://fedora:fedora/x86_64/coreos/testing-devel Version: 31.20200526.dev.0 (2020-05-26T19:18:19Z) Commit: f1bbe310d7ec3ac03e1dba2c819f43daf3c7f6c88c000b20892d7d4a25881f2e GPGSignature:...

Repurposing this card now to just generalize it to having ostree be "live system-aware".

That sounds fine to me overall, but that seems like more of a follow-up to this? I'd be happy if we can just drop the `/proc/cmdline` hacks to start.

> This oddly works now in a locally built FCOS live ISO and PXE artifacts: Ahh, I think the reason this works now is that we're literally shipping a `/boot`...

Don't fetch and build in `--strict` mode. Alternatively, see the steps in https://github.com/coreos/fedora-coreos-config?tab=readme-ov-file#adding-packages-to-the-os. Another alternative is to build a custom container image instead. See the examples at https://github.com/coreos/layering-examples.

Still interested in this.

Still interested in this.

Still interested in this.