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 779896 - Builder fails to run flatpak if some directory contains flatpak build-init dir inside the source directory
Builder fails to run flatpak if some directory contains flatpak build-init di...
Status: RESOLVED INCOMPLETE
Product: gnome-builder
Classification: Other
Component: general
Flatpak Nightly Channel
Other Linux
: Normal normal
: ---
Assigned To: GNOME Builder Maintainers
GNOME Builder Maintainers
Depends on:
Blocks: 781010
 
 
Reported: 2017-03-11 12:40 UTC by Carlos Soriano
Modified: 2017-04-08 18:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Carlos Soriano 2017-03-11 12:40:56 UTC 
I was debugging Polari build with manually doing flatpak-builder test (blah)json and then when I tried on builder to play build/run I get

13:36:59.0550                                  GLib-GIO[12967]: CRITICAL: g_file_enumerator_next_file: assertion 'G_IS_FILE_ENUMERATOR (enumerator)' failed
13:36:59.0550                                  GLib-GIO[12967]: CRITICAL: g_file_enumerator_close: assertion 'G_IS_FILE_ENUMERATOR (enumerator)' failed
13:36:59.0552                                       Ide[12829]:  WARNING: Error opening directory '/home/csoriano/Projects/polari/test/var/run/systemd/inaccessible': Permission denied

I though builder was running/building in a owned directory on ~/.cache. So this shouldn't happen.
Comment 1 Christian Hergert 2017-03-12 05:14:47 UTC 
I'm not sure I understand what you mean from the summary/description.

We don't do in-tree builds unless we detected you already configured in-tree (so basically if Makefile exists). But flatpak-builder does place a .flatpak-builder directory in the source tree so that we can reuse OSTree cache-points between different build configurations.
Comment 2 Matthew Leeds 2017-03-13 04:28:43 UTC 
I'm not able to reproduce this. I created the template app and ran flatpak-builder manually in the source directory so it has that var/run/systemd/inaccessible file, but builds still work using the flatpak manifest configuration. There are some warnings printed by the vala plugin about not being able to access that file, but I don't think that affects much.
Comment 3 Carlos Soriano 2017-03-13 08:31:52 UTC 
(In reply to Christian Hergert from comment #1)
> I'm not sure I understand what you mean from the summary/description.
> 
> We don't do in-tree builds unless we detected you already configured in-tree
> (so basically if Makefile exists). But flatpak-builder does place a
> .flatpak-builder directory in the source tree so that we can reuse OSTree
> cache-points between different build configurations.

Hm to clarify, I just did these steps:
Clone polari in builder
Go command line and do manually flatpak-builder test org.gnome.Polari.json
It builds
Go to builder and click the play button
It fails with the message in comment 0

Maybe I can try to debug further this.
Comment 4 Matthew Leeds 2017-04-08 18:33:23 UTC 
I've tried to reproduce this both using a Builder version from when the bug was filed and using the most recent Builder and haven't been able to. Maybe we should close the bug?
Comment 5 Carlos Soriano 2017-04-08 18:57:25 UTC 
I can reopen if I get further instructions, yes.