Dan Nicholson

@Jan200101 Thanks for all that info. I'm starting to suspect the error is actually in the system helper that pulls the objects from the user's temporary repo used for downloading...

Can you run the system helper directly with `sudo /usr/libexec/flatpak-system-helper --replace --no-idle-exit --verbose --ostree-verbose` and see if there are any errors?

> `FH: CancelPull default 1 /var/lib/flatpak/repo/tmp/flatpak-cache-7DC461` seems fishy in there. If the pulls were prematurely canceled this would explain why various compressions functions report incomplete data. I actually think that's...

@dvzrv From [your arch change](https://gitlab.archlinux.org/archlinux/packaging/packages/ostree/-/commit/726c0da3d4f40e7dae93174ba2e590aea3156c90), it appears reverting f7f6f87c513c9f35bc24f35e909779c19cb49d3a fixes the problem, right? If so, care to turn it into a PR? I think that's the wise thing to do...

> Having only looked at this for 3 minutes so far, one immediate likely thing that jumps out to me here is the interaction with `revokefs-fuse`. Oh yeah, `revokefs-fuse`. I...

> I think we should try just linking prepare-root to glib, and then include in the required headers and c files from libostree/ directly into the binary. Seems least work...

Definitely was always something I planned to implement. In fact, #1292 has some of that including a `--lock-timeout` option added to all the CLIs, although the current locking implementation is...

``` PASS: tests/test-repo-finder-config 1 /repo-finder-config/init ERROR: tests/test-repo-finder-config - Bail out! PASS: tests/test-repo-finder-mount 1 /repo-finder-mount/init ERROR: tests/test-repo-finder-mount - Bail out! ERROR: tests/test-symbols.sh - missing test plan tap-driver.sh: internal error getting exit...

> ## UEFI only > We'll need to add a UEFI backend to ostree, which explicitly controls the UEFI boot ordering via e.g. `efibootmgr` instead of using the `/boot/loader/entries` stuff....

Also, if you're building a UKI, the initramfs is part of it and there's no need for ostree to find it. Are you suggesting the ostree take the separate kernel...