After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 791614 - The state dir is not on the same filesystem as the target dir
The state dir is not on the same filesystem as the target dir
Status: RESOLVED OBSOLETE
Product: gnome-builder
Classification: Other
Component: general
3.26.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Builder Maintainers
GNOME Builder Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-12-14 13:37 UTC by Dag Odenhall
Modified: 2018-01-11 10:51 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dag Odenhall 2017-12-14 13:37:22 UTC
When trying to build any flatpak, Builder says,

The state dir (/home/.../Projects/.../.flatpak-builder) is not on the same filesystem as the target dir (/home/.../.cache/gnome-builder/flatpak/staging/...)

This seems to have started after an update to flatpak-builder, so it could be a flatpak issue rather than a Builder issue but Builder is where I'm seeing it and it seems to come about as a result of where Builder runs builds. I could report this against flatpak-builder as well or instead if you think that's more appropriate.

My ~/.cache is a separate Btrfs subvolume, because I'm using snapper to create snapshots of $HOME regularly and caches aren't important but tend to hold a lot of unique and changing data that would grow snapshots out of control, but it's all a single Btrfs filesystem.

As a result I'm effectively locked out of using Builder because I can't build any projects and there's no obvious workaround except moving ~/Projects to ~/.cache, and that's just silly.
Comment 1 Dag Odenhall 2017-12-14 19:46:02 UTC
Also reported against flatpak-builder: https://github.com/flatpak/flatpak-builder/issues/84
Comment 2 Christian Hergert 2017-12-14 22:36:36 UTC
I can see how this is a frustrating situation for you.

The reason this *probably* became an issue, is that we moved away from using a .flatpak-builder directory placed in the source tree (~/Projects/foo/.flatpak-builder) to a shared directory (~/.cache/gnome-builder/flatpak-builder/) to increase the chances we can reuse existing source and build data between projects.

Maybe we should move back to the old way of doing things (but that also increases the amount of churn we're doing on your $HOME partition too, which is not exactly btrfs's strong point).
Comment 3 Dag Odenhall 2017-12-15 11:50:51 UTC
Hmm, I would think that putting everything in ~/.cache would actually *solve* this issue for me, not cause it. The problem seems to be that Builder is *not* putting everything in the same subvolume, because for me it *is* putting the state directory in the ~/Project subdirectory. I'm on gnome-builder-3.26.2-1.fc27.x86_64, is that supposed to have the new shared directory?
Comment 4 Christian Hergert 2017-12-16 02:36:24 UTC
3.26 does not have the code to use --state-dir, that is only in Nightly.
Comment 5 GNOME Infrastructure Team 2018-01-11 10:51:03 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-builder/issues/331.