Antheas Kapenekakis
Antheas Kapenekakis
Figured it out. Happens during checking out `/etc`. Has 2 `checkout_tree_at_recurse` They have these args: ``` (gdb) info args self = 0x55f9912ccb20 options = 0x7ffd811fab10 state = 0x7ffd811faa80 destination_parent_fd =...
I tried to do that. But unfortunately compiling ostree on a system without dev packages is not particularly easy... I have a command you can use to reproduce it though:...
Hi Eric, As I wrote above, we have not deployed the change yet as we would need to fork ostree. But we have made the change to os-release. I do...
Seems like `PRETTY_NAME` is only used in the place I sent and in the rpm-ostree backend code that implements `mutate-os-release` and is unrelated.
Looking at my deployment I can confirm. Both files are the same though. Your images appear to have the same issue. `PRETTY_NAME` is pinned so you cant tell different versions...
I cannot find that piece of code. The only reference to that is `mutate_os_release_contents` in rpm-ostree which is part of the backend code.
In universal blue, we are using an OCI based workflow, so most images cannot modify the commit metadata. They can do OCI tags or os-release. Also, this metadata fact escaped...
Switched to draft as something has to be done about `deployment_version` first.
Dan also brought up the valid point of (ostree:0). I personally think that the deployment ID needs to be in the bootloader somewhere, but I will concede that (ostree:X) is...
We already use that tag for the images. But I will review it again.