=== JanC is now known as Guest15956 === JanC_ is now known as JanC [04:29] Experimenting with snappy. I installed atom-cwayne but cannot find any way to launch it. [08:59] karlthane: happy weekend! Does your environment add /snap/bin to your shell's PATH? [10:35] morning everyone :) [12:52] How can I make files not read only? I cant run my snap after install because it converts the files to read only [12:56] Cavan: All snap files are immutable by design. By read-only, do you mean no executable bit? [12:57] "Read only" usually means not writable. It says nothing about executability. [12:58] Yeah thats what I mean sorry, the snap cant write the files which need to be written, the error is 'mkdir: cannot create directory ‘/snap/karaf/x9/data/log’: Read-only file system' [12:59] qengho [12:59] Cavan: You're writing to the wrong place. Write beneath $SNAP_DATA, not $SNAP. [13:01] I put 'export SNAP_DATA="$SNAP/data/log/"' in a wrapper, is that incorrect? [13:03] That is very much incorrect. You shouldn't assign anything starting with SNAP. [13:05] * qengho Zzz. [13:05] qengho, I'm very new to this as you can probably tell, is something like this better 'export KARAF_DATA="$SNAP_DATA/data/log/"'? [13:15] Cavan: You have a program. If it's expecting some environment variable, you should set it, and export it to subprocess's environments. If it's expecting some parameter, you should construct it. What you have there looks fine to me, but I don't know your program at all. You have to know why you're doing that, and then you might know what, better. [13:21] why is the qmake plugin staging my app binary at stage/home/ubuntu/snap/infodump/parts/infodump/build/build/infodump instead of something sensible like stage/bin/infodump? [15:41] Can anyone assist me with snapcraft and how it works and some basics about Ubuntu Snappy Core. I've been to all possible web pages, but it seems like I'm missing something. Thanks [16:35] ogra_ thanks for the bug, I suspect it is related to the way we migrate files from parts//install to stage and prime [16:36] sergiusens, yeah, there are also a few ldd issues at the very end of the build https://launchpadlibrarian.net/274817065/buildlog_snap_ubuntu_xenial_amd64_os-snap-test_BUILDING.txt.gz [16:36] * ogra_ spent the whole day uploading hacked snapcrafts to the image ppa :) [16:36] ogra_ yeah, you probably want to not elf crawl for type OS [16:37] right, actually it should just blindly copy everything over and call mksquashfs [16:38] * ogra_ learned a lot about snapcraft today (stage and prime are still a bit of a myth to me though) [16:39] the kernel snap build works fine btw https://code.launchpad.net/~ogra/+snap/kernel-test-snap :) [16:39] (i still need to set it up for other arches than amd64 though) [16:43] ogra_ yeah for an os snap we do, but for others, special attribs are not a good idea as we won't be able to easily support clean delta updates [16:43] indeed [16:48] ogra_ and now I understand where those PPA build failures come from too :-) [16:48] heh [16:49] sorry for spamming [16:50] PR snapcraft#681 closed: parser - Add handling for carriage returns in wiki [19:49] 'Still getting /snap/karaf/x14/data/log/karaf.log (Read-only file system)' How can I configure it to write the files? I've tried so many things and nothing has worked so far [19:51] Bug #1606053 opened: 'snap find ' output is a little agressive when '' results in no snaps [19:54] Cavan: don't you tell it to write to $SNAP_USER_DATA ? [20:00] magicaltrout, is it as simple as writing 'export KARAF_DATA="$SNAP_USER_DATA"'? It wont write the files it needs to from the karaf data [20:09] dunno how karaf is setup to write Cavan [20:09] but something like that [20:09] you need to write it somewhere [20:10] depends what its set to [20:10] you could also try [20:11] -Duser.home=$SNAP_USER_DATA [20:11] and see if it rewrites everything [20:11] it might [20:12] magicaltrout, where should I put that, in the wrapper I made with the other exports ect? [20:16] somewhere that takes java opts