Alex Băluț

I remember reading on https://snapcraft.io/universal-ctags about such a limitation, but I forgot about it, thinking I'll notice an error when I get to using it. Probably snap allows using `/tmp`...

If that is not accepted by snap, consider error-ing if the output file is in `/tmp` when running as ctags-snap.

I see "Committing stage" in `builder_cache_commit` in [builder-cache.c](https://github.com/flatpak/flatpak-builder/blob/09b2736693fb683dd5d32b368c2860195202cee2/src/builder-cache.c#L572). "fstatat(%s)" appears to be in [libglnx/glnx-fdio.h](https://github.com/search?q=org%3Aflatpak+%22error%3A+fstatat%22&type=Code) and in a few ostreedev/ostree/src/libostree/ [files](https://github.com/search?q=org%3Aostreedev+%22Error%3A+fstatat%22&type=Code): src/libostree/ostree-repo-static-delta-core.c - [_ostree_repo_static_delta_delete](https://github.com/ostreedev/ostree/blob/8d2e9b8f9e7a0bf112ace44a1b640b42c9d6b157/src/libostree/ostree-repo-static-delta-core.c#L671) src/libostree/ostree-sysroot-deploy.c - [get_kernel_from_tree_usrlib_modules](https://github.com/ostreedev/ostree/blob/632e4ebd60da3afa79cb259f6a1e827e33ab8f30/src/libostree/ostree-sysroot-deploy.c#L916) src/libostree/ostree-repo.c - [_ostree_repo_has_loose_object](https://github.com/ostreedev/ostree/blob/7661f3e80973cd7d02c43fc7ac6343df05242029/src/libostree/ostree-repo.c#L4141) Since...

I rebuilt the archlinux flatpak-builder package with some additional `g_print ("builder_cache_commit 1\n");` statements and now it built.

`rm -rf $(find . -name .flatpak-builder)`

I keep noticing this issue

Can you reproduce the error if you build `manifest.json`?

I rebuilt locally the [ostree](https://git.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/ostree) package and with the locally built ostree it runs fine. Seems to be an issue related to how ostree is built by archlinux. But no...

I added some debug output to flatpak-builder and to ostree: - flatpak-builder: https://github.com/aleb/flatpak-builder/commit/9339cb47e21e04644ae81f87440d3b8454d147e2 - ostree: https://github.com/aleb/ostree/commit/772bccb17f6db84a33a5618b1ce6b5efe9568c84 "Unfortunately" the build succeeded, but the previous failure printed this: ``` CALLING builder_cache_commit from...

The chain of calls is: - `builder_cache_commit` - `ostree_repo_write_directory_to_mtree` - `ostree_repo_write_dfd_to_mtree` - `write_dfd_iter_to_mtree_internal` - `write_dir_entry_to_mtree_internal` - ... - `write_dfd_iter_to_mtree_internal` (again) - `glnx_fstatat`: https://github.com/aleb/ostree/blob/ab566d29b98e2f00fe1bc3f9be43ec81de45aa51/src/libostree/ostree-repo-commit.c#L3988 ``` if (!glnx_fstatat (src_dfd_iter->fd, dent->d_name, &stbuf, AT_SYMLINK_NOFOLLOW,...