[02:08] <tsimonq2> Can I make a metapackage with my snapcraft.yaml file, and if so, how?
[13:02] <oparoz> Hello. How does one create a user using snapcraft?
[13:18] <jospoortvliet> tsimonq2: a metapackage? you mean something that pulls in other stuff? no, snaps don't do dependencies
[13:18] <jospoortvliet> you have to inclde everything
[13:19] <jospoortvliet> oparoz: with everything running as root (aparently) I guess you don't need to :D
[13:20] <oparoz> jospoortvliet: This worries me... You may want to have writable files for the sysadmin, but make sure PHP can't read or worse write to those files
[13:20] <jospoortvliet> well the way snaps work is that no, you don't have writable files for the sysadmin, the snap with the code is read-only
[13:20] <jospoortvliet> and only the actual datafiles are editable
[13:21] <jospoortvliet> and if you want to edit config you create a new snap
[13:21] <jospoortvliet> with your new config
[13:21] <jospoortvliet> correct me if I'm wrong kyrofa
[13:21] <jospoortvliet> oparoz: so all the config files we're fscking with like httpd.conf are read-only
[13:21] <jospoortvliet> config.php of ownCloud is an exception but that's, well, of course.
[13:21] <jospoortvliet> not different in any ownCloud installation
[13:22] <jospoortvliet> even root can't doo much in a snap so it is safe to run as root
[13:22] <jospoortvliet> *SOMEBODY TELL ME I'M WRONG* ;-)
[13:22] <tsimonq2> jospoortvliet: but it pulls in stuff from GitHub?
[13:22] <tsimonq2> and Ubuntu packages?
[13:22] <oparoz> just checking the owncloud folder
[13:22] <jospoortvliet> tsimonq2: aah ok, that is what you mean
[13:22] <jospoortvliet> yeah, when building
[13:22] <jospoortvliet> the snap
[13:22] <jospoortvliet> not when installing the snap
[13:22] <jospoortvliet> this will all be included in the snap
[13:22] <tsimonq2> mhhhhmmmm...
[13:22] <tsimonq2> yes
[13:23] <tsimonq2> :)
[13:23] <jospoortvliet> this is like a package build script
[13:23] <jospoortvliet> the snapcraft.yaml I mean
[13:23] <tsimonq2> *nod*
[13:23] <jospoortvliet> I'm writing a blog about it, will try and get that finished... will drop what I have in a wiki page, gimme some minutes
[13:23] <jospoortvliet> reading over that should help you get an idea of this weird stuff :D
[13:24] <jospoortvliet> oparoz: I'll work what I wrote into https://github.com/owncloud/pi-image/wiki/Building-your-own-images
[13:24] <jospoortvliet> good with you?
[13:25] <oparoz> OK
[13:26] <oparoz> It's now: Building your first image
[13:26] <oparoz> We need additional articles about the specific parts
[13:26] <qengho> oparoz: You can't create a user.
[13:27] <oparoz> Thanks qengho. Does it matter if a script has a non-existing user then or should we modify all generic scripts we use so that they use root or www-data?
[13:27] <qengho> oparoz: One package can't touch the files in another package or outside the system. As far as it's concerned, it is the only package installed on a whole simple machine that it has all to itself.
[13:29] <oparoz> qengho: The problem is that if in a web app you have a mix of read-only and regular files, then you need to write some complex vhosts to only place those writeable files to the writeable "side"
[13:29] <jospoortvliet> oparoz: I have turned the call you guys had Friday into a extensive how-to
[13:29] <jospoortvliet> also explaining the basics of snappy etc
[13:29] <oparoz> OK jospoortvliet
[13:30] <jospoortvliet> would love to hear from tsimonq2 what he thinks once I've formatted the thing :D
[13:30] <qengho> oparoz: it doesn't matter about the ownership, within reason. Don't use UIDs greather than 999 and you should be fine.
[13:30] <oparoz> Thanks qengho, I'll give it a go
[13:30] <jospoortvliet> oparoz: pls don't edit the file anymore
[13:30] <jospoortvliet> damn I just lost all my changes :(
[13:31] <oparoz> :(
[13:35] <qengho> oparoz: Doesn't seem hard, but perhaps the usual Apache url=filesystem mapping plugin doesn't fit. Check if the resource is in one place. If not, check in another. If not, 404
[13:39] <jospoortvliet> tsimonq2: here it is: https://github.com/owncloud/pi-image/wiki/Building-your-first-image
[13:40] <jospoortvliet> I sadly have to leave now, taking my wife out for a dinner & concert. Ok, that is far from sad but it means I won't be back here today ;-)
[13:40] <jospoortvliet> will work more on this tomorrow
[13:40] <jospoortvliet> kyrofa: oparoz: please, review, check that wiki page
[13:40] <jospoortvliet> it is based on pretty much the first half of your conversation friday
[13:40] <jospoortvliet> should be a newbie-introduction to snappy
[13:41] <oparoz> Thanks jospoortvliet! Enjoy the show!
[13:41] <jospoortvliet> I will. Just fixed a layout issue, now I'm really out of here :D
[13:42] <jospoortvliet> oparoz: there are some more layout issues with the page.
[13:43] <oparoz> jospoortvliet: yep...
[13:43] <oparoz> But I'm writing a daemon...
[13:44] <jospoortvliet> go write your evil spirit, I will be happy to fix the page tomorrow
[13:44] <jospoortvliet> or tsimonq2 fixes it while reading :D
[13:44] <jospoortvliet> tsimonq2: you have access there?
[13:44] <jospoortvliet> if not, pls email your github account name to frank@owncloud.com with jos@owncloud.com in cc, asking for access to the pi-image repo and you can edit as soon as F adds you!
[13:45] <tsimonq2> jospoortvliet: :) I'll take a look
[13:46] <tsimonq2> (not a Snappy dev by any means, just an Ubuntu enthusiast and member :) )
[13:46] <jospoortvliet> tsimonq2: thanks a billion times, believe me, right now any knowledge is super helpful :D
[13:46] <jospoortvliet> tsimonq2: and email me if you're interested in a Pi drive :P
[13:46] <jospoortvliet> https://owncloud.org/blog/pioneer-our-owncloud-pi-drives/
[15:58] <oparoz> kyrofa: Where are you telling Apache to load php7_module. It's not listed anywhere in snapcraft or the Apache plugin
[16:03] <oparoz> kyrofa: I'm guessing all modules are automatically loaded, so we have to prevent the build of mod_php
[16:26] <forker> Hello @here. Can someone help me to set forking type for service in package.yaml?
[16:26] <forker> - name: subutai-agent    type: forking    security-policy:       apparmor: meta/agent.profile       seccomp: meta/agent.seccomp    description: "agent service"    start: bin/agent-wrapper
[16:27] <forker> trying like this http://pastebin.com/EsvZyBru but it does not work :(
[16:59] <forker> hm, is there a way to configure forking service on 15.04 snappy or it work only in 16.04?
[17:02] <oparoz> How do you make a script executable in a snap?
[17:45] <oparoz> Why is this an invalid argument on Snappy, when used in a daemon? -> ulimit -HSn 32768
[19:32] <qengho> oparoz: "dmesg"
[19:33] <qengho> oparoz: ^ look for logged errors or warnings that the kernel facilities blocked.
[19:34] <qengho> oparoz: When you construct a snap, the execute bits that are set when you make the image are still on when you unpack and use the image.
[19:35] <oparoz> Thanks qengho. Regarding the execute bits. I'm worried that it's going to be lost when I'm going to push my changes via git
[19:35] <qengho> git preserves x bits.
[19:36] <qengho> ...pretty sure.
[19:36] <oparoz> qengho: If Windows keeps it...
[19:36] <qengho> Sorry, never heard of it.
[19:37] <oparoz> We'll see
[22:30] <oparoz> How do you compile mod_mpm_event on snappy 16.04?  No rule to make target 'server/mpm/event/libevent.la', needed by 'httpd'
[22:30] <oparoz> Neither libevent-dev or libev-dev work
[22:53] <oparoz> Is it normal for ldd to report all binaries in an installed sna as broken?
[23:00] <oparoz> Apparently it's normal  as the missing libs are in the snap