[04:33] <dhallett> i am new to snappy ubuntu and wondering if i can setup my own snappy repo to host updates and also snappy images for raspberry pi 2?
[04:35] <dhallett> i am currently using snappy ubuntu core 16.04 on my rpi2 right now. just to let you know.
[04:36] <dhallett> i have been a ubuntu user since Ubuntu 9.04 came out.
[04:38] <dhallett> any help is appreciated
[04:40] <dhallett> i would like to start contributing back to the ubuntu community as both as a dev and a fellow ubuntu user.
[04:52] <dhallett> anyone able to help me with my problem? i also have a webdm on snappy ubuntu problem as when i go to my localip of my raspberry pi 2 it doesn't show on 16.04LTS snappy core
[04:55] <dhallett> i  thought using this irc channel would provide faster answers after searching the internet for approx 24 hours i find the forums are a tad bit slow at answering than on irc
[08:05] <dholbach> good morning
[08:11] <didrocks> good morning dholbach!
[08:11] <dholbach> salut didrocks
[09:59] <JamesTait> Good morning all!  Happy Thursday, and happy Battery Day! 😃
[10:28] <popey> When I upload a snap to the store, I have to add a release. rolling-personal, rolling-core and 15.04-core. i made the snap on 16.04. which is that?
[10:30] <longsleep> Good morning snappy, what is the best way to get snapcraft and start building a snap for 16.04?
[10:30] <longsleep> is there a ppa or should i clone from Git?
[10:34] <popey> there's a ppa longsleep
[10:35] <longsleep> popey: that one looks good: https://launchpad.net/~snappy-dev/+archive/ubuntu/snapcraft-daily
[10:56] <zyga> longsleep: get xenial or the snapcraft ppa
[10:56] <zyga> longsleep: install snapcraft and look at snapcraft examples
[10:56] <ogra_> i think you need xenial in any case, dont you ?
[10:56] <zyga> longsleep: the examples are in snapcraft source tree, you can just clone that from github as a start
[10:56] <zyga> ogra_: oh, good point
[10:57] <zyga> longsleep: so you do want to use xenial for 16.04, 16.04 requires 16.04 to develop
[10:57] <ogra_> so use a chroot (or the traditional ubuntu-core tarball)
[10:58] <longsleep> ogra_: well i got the vagrant image but ran into bug #1546108
[10:58] <longsleep> i can chroot as well but that requires root which i would like to avoid
[10:59] <noizer> ogra_ HI i will use your application to start with lighttpd but do you have an conf file?
[11:01] <ogra_> noizer, i use a script to generate both configs (config.sh) out of the default.yaml file
[11:02] <ogra_> and indeed the startup wrapper script
[11:08] <longsleep> zyga: All right, i have 16.04 now gbarbieru/xenial Vagrant box seems to work
[11:09] <longsleep> ogra_: can i still rely that python3 and openssl binaries are available in 16.04 base snappy system?
[11:10] <longsleep> ok ready to go root@vagrant:~# snapcraft -v
[11:10] <longsleep> 2.2.2
[11:11] <noizer> ogra_ is it possible to use an conf file?
[11:12] <ogra_> noizer, sure, just ship it and point the binary to it
[11:12] <ogra_> longsleep, you could never rely on that .... though the new snapcraft makes it trivial to ship your interpreter
[11:12] <noizer> ok I will first make my conf file and then try it.
[11:12] <longsleep> ogra_: ok thanks - i will check it out
[11:13] <noizer> thx ogra_
[11:14] <ogra_> longsleep, thats for snapcraft 2.1 (so, outdated atm) http://paste.ubuntu.com/15106152/ but that should give you an idea
[11:14] <ogra_> the last three lines simply pull in the py2 interpreter
[11:14] <ogra_> (it allows indeed more complex things too)
[11:14] <longsleep> yeah i guess it does
[11:15] <longsleep> thanks - i need to find a suitable version of Go first - is it in the repositories nowadays?
[11:15] <ogra_> not a go user, so i dont know :)
[11:16] <ogra_> https://launchpad.net/ubuntu/+source/golang/2:1.6~rc2-0ubuntu1
[11:16] <ogra_> looks like that is in the archive
[11:16]  * longsleep looks
[11:17] <longsleep> well apt-cache search golang-go-linux-amd64 gave nothing, lets try golang-go and see what that installs
[11:18] <ogra_> https://launchpad.net/ubuntu/+source/golang/2:1.6~rc2-0ubuntu1/+build/8984117
[11:18] <ogra_> looks like it is just "golang"
[11:19] <longsleep> probably packaging has changed, does not look too bad
[11:23] <longsleep> ogra_: looks really good vagrant@vagrant:/vagrant/Dev/spreed-webrtc$ file bin/spreed-webrtc-server
[11:23] <longsleep> bin/spreed-webrtc-server: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, not stripped
[11:23] <longsleep> hooray!
[11:24] <ogra_> yay
[11:24] <ogra_> ricmm, ^^^ !
[11:33] <ricmm> longsleep: excellent :)
[11:42] <zyga> 19:41 -!- magizian [pan@162-202-67-158.lightspeed.livnmi.sbcglobal.net] has quit [Client Quit]
[11:42] <zyga> 19:41 -!- magizian [pan@162-202-67-158.lightspeed.livnmi.sbcglobal.net] has quit [Client Quit]
[11:43] <zyga> hmm
[11:43] <zyga> sorry :)
[11:43] <ogra_> zyga, yes ?
[11:44] <ogra_> hah
[11:44]  * ogra_ was wondering what you wanted to tell us :)
[11:45] <zyga> "where has my focus gone to"
[12:06]  * zyga digs into cgroups
[12:06] <zyga> whee
[12:08] <longsleep> mhm snapcraft does not work when used on the /vagrant mount - not really a problem but it would be nice if it would work :)
[12:08] <longsleep> [Errno 1] Operation not permitted: '/vagrant/Dev/spreed-webrtc-snap/parts/glue/install/ssleay.cnf' -> '/vagrant/Dev/spreed-webrtc-snap/stage/ssleay.cnf'
[12:13] <longsleep> ogra_: do you know if the make plugin for snapcraft can run a script after clone? like ./autogen.sh
[12:14] <zyga> jdstrand: I'd like to make some modification to ubuntu-core-launcher, I'll ping you later about that
[12:14] <longsleep> ogra_: ah seems i have to ue the autotools plugin
[12:14] <zyga> jdstrand: I'd like to sync with you as soon as you are around, it's important and related to the sprint
[12:23] <longsleep> ricmm: Are you there? I got the problem that snapcraft passes a bunch of LDFLAGS in a format which seems to be wrong for the go toolchain
[12:25] <ogra_> did you use the go plugin actually ?
[12:27] <longsleep> ogra_: no, the autotools plugin, but i can fix it in the Makefile.am
[12:27] <longsleep> ogra_: i guess it is our fault and not snapcraft to blame :)
[12:28] <ogra_> or sergiuens ;)
[12:28] <longsleep> Staging spreed worked now
[12:32] <zyga> jdstrand: so (in case you read the backlog), hw-assign doesn't work with /dev/i2c-1 for the same reason it didn't work with skills, still no permission to /dev/i2c-1 -- it's in the control group, but it's just not writable and the app doesn't run as root
[12:33] <zyga> jdstrand: unless there's a logic hole somewhere I think we have to accept to chmod devices
[12:33] <zyga> jdstrand: what confuses me is that other people make similar stuff and for them it works but they were always background commands, running as root, so getting the permission
[12:35] <longsleep> ogra_: btw, snappy-tools where do i get it from for xenial?
[12:36] <longsleep> (i have ppa:snappy-dev/tools)
[12:36] <ogra_> longsleep, hmm, they should be in the archive ... if not, they are definitely in https://launchpad.net/~snappy-dev/+archive/ubuntu/image
[12:37] <ogra_> oh, wait ... -tools isnt in there
[12:37] <ogra_> i guess the above is correct
[12:38] <longsleep> what exactly? /tools has not much builds for xenial yet
[12:38] <longsleep> and /image does not seem to have it either
[12:38]  * ogra_ has honsetly not used -tools since he switched to xenial and snapcraft 2.x )
[12:38] <longsleep> how do you sideload?
[12:39] <longsleep> manually?
[12:39] <longsleep> i wanted to use snappy-remote or something
[12:39] <kyrofa> Good morning
[12:41] <longsleep> ogra_: seems i accidently created an app instead of a service :/
[12:41]  * longsleep searches for a service example
[12:42] <ogra_> longsleep, see my mycroft examplle from above
[12:42] <longsleep> ah just add the daemon key?
[12:42] <ogra_> yeah, services are dead .... they are all apps now
[12:43] <ogra_> binary vs daemon is the difference
[12:43] <longsleep> ok got it
[12:46] <longsleep> ogra_: what about the caps? Seems like snapcraft 2.2 does not like it like it is in your example
[12:46] <longsleep> probably the uses key from the examples
[12:46] <longsleep> i think i get it from the example
[12:46]  * longsleep tries it
[12:47] <ogra_> longsleep, thats the new skills system i'm completely unfamiliar with
[12:47] <ogra_> zyga might be able to point you to something perhaps
[12:47] <longsleep> https://github.com/ubuntu-core/snapcraft/blob/master/examples/mosquitto/snapcraft.yaml
[12:47] <longsleep> using that example
[12:47] <ogra_> (caps are gone with 2.2+ )
[12:47] <ogra_> yeah, that looks about right
[12:48] <zyga> longsleep: no caps
[12:48] <zyga> longsleep: use the migration-skill please
[12:48] <zyga> longsleep: and tell me about the permissions your snap needs please
[12:48]  * zyga -> lunch
[12:50] <longsleep> zyga: i now use [network-listener, network-service], as the snap only listens in a bunch of ports and reads/writes to its own directories
[12:51] <longsleep> ogra_: ok i have a service now, only the config hook needs fixing and then i think i might have it
[12:52] <ogra_> wow, that was fast
[12:52] <ogra_> you rock :)
[12:52] <longsleep> well, KeyError app in the config hook still to resolve :)
[13:03] <longsleep> ah it is not even a problem in the config hook, i am just missing the config.in file in the snap
[13:08] <zyga> longsleep: nice!
[13:33] <ogra_> hmm
[13:34] <ogra_> does anyone have an idea why we ship Qt libs in our rootfs ? http://people.canonical.com/~ogra/core-image-stats/20160218.changes
[13:35] <asac> hehe
[13:35] <asac> ogra_: yes i know
[13:35] <asac> i lokoed it it just yesterday
[13:35] <asac> i think it can be fixed by seed
[13:35] <asac> we have the ubuntu-download-manager still in
[13:35] <asac> or somethign along that line used qt
[13:36] <ogra_> eek
[13:36] <ogra_> yeah, that shoul drally go
[13:36] <asac> just unseed it and see if world explodes :)
[13:36] <zyga> hmm, how do I start a background service in a snappy way?
[13:36] <ogra_> *should really
[13:36] <asac> sure it should
[13:36] <asac> dont think we want to remove it though before next week :)
[13:36] <ogra_> does snappy do the download on its own for snaps ?
[13:36] <asac> yes i think thats all old
[13:37] <zyga> ogra_: yes
[13:37] <ogra_> cool then
[13:37] <asac> just leftover from old world
[13:37] <asac> feel free to double check if you find any other rdepend
[13:37] <asac> so we are safe
[13:37] <ogra_> yeah, there is more system-image stuff still seeded i think
[13:37] <ogra_> (and hacks in the build system to set that up)
[13:37] <ogra_> sudo reboot
[13:38] <ogra_> damn ... EFOCUS :P
[13:38]  * ogra_ blames zyga ... he started that :P
[13:40] <zyga> Feb 18 13:40:23 localhost.localdomain ubuntu-core-launcher[3888]: failed to create user data directory. errmsg: Permission denied
[13:40] <zyga> hehe
[13:40] <zyga> so it seems we still have the permission denied issue, this time for services
[13:40] <zyga> so yay, more stuff to debug
[13:41] <zyga> (this is with the applied workaround)
[13:44] <zyga> kyrofa: ^^ any chance you know how to work around this?
[13:44]  * kyrofa reads scrollback
[13:44] <longsleep> ogra_: after i have fixed a bug in the config hook totally unrelated to snappy it actually works on 16.04
[13:45] <kyrofa> zyga, did jdstrand get that new profile out?
[13:45] <ogra_> longsleep, whee, awesome !
[13:45] <kyrofa> zyga, as for working around it, the same workaround he suggested before should work
[13:45] <kyrofa> Oh wait.. you said you're using that workaround
[13:46] <kyrofa> zyga, it was /** r or something, wasn't it?
[13:47] <kyrofa> zyga, check for apparmor denials?
[13:47] <kyrofa> (make sure this is the same issue)
[13:48] <kyrofa> zyga, also, you haven't rebooted since loading in that temporary profile, right? Or you've loaded it again?
[13:49] <kyrofa> zyga, alright, I will now take you up on making an edge image for me, if you have a minute. Let me take it for a spin, see what's going on
[13:50] <zyga> kyrofa: yes (I don't know if new image was built) but note I did apply the same workaround myself
[13:51] <zyga> kyrofa: how do I check apparmor denials?
[13:51] <kyrofa> zyga, either with snappy-debug or just the syslog
[13:51] <zyga> kyrofa: previously I manually straced everything, I don't know how to do that when systemd does activation
[13:51] <zyga> ok, I'll check
[13:51] <kyrofa> zyga, yeah you don't need to-- it's not that complicated
[13:52] <noizer> ogra_ how does I make some rewrite in lighttpd. it does not work from me
[13:54] <zyga> noizer: rewrite/
[13:55] <noizer> zyga do you know something about nginx on snappy?
[13:57] <zyga> noizer: no, I was just wondering what you were asking about
[13:58] <zyga> Feb 18 13:57:55 localhost.localdomain ubuntu-core-launcher[4831]: failed to create user data directory. errmsg: Permission denied
[13:58] <zyga> Feb 18 13:57:55 localhost.localdomain kernel: audit: type=1400 audit(1455803875.084:81): apparmor="DENIED" operation="mkdir" profile="/usr/bin/ubuntu-core-launcher" name="/root/snaps/" pid=4831 comm="ubuntu-core-lau" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
[13:58] <zyga> kyrofa: ^^
[13:58] <zyga> seems like the same old problem
[13:58] <zyga> just root instead of $HOME
[13:58] <zyga> I'll apply the same workaround
[13:58] <zyga> kyrofa: it'd be good to check if jdstrand fixed both root and $HOME
[13:59] <noizer> lighttpd is a webserver but ogra_ worked with it before and i thought he could help me out with some problems
[13:59] <ogra_> noizer, you likely need to enable the module first
[13:59] <kyrofa> zyga, I thought the workaround was /** r though, no?
[13:59] <ogra_> somewhere in the config
[13:59] <kyrofa> zyga, oh, the write though
[13:59] <kyrofa> zyga, yeah you can take a peek inside the profile real quick if you want
[14:00] <zyga> kyrofa: I only have the workaround
[14:00]  * zyga looks at vanilla profiles
[14:00] <noizer> mod_rewrite is enabled ogra_
[14:00] <ogra_> http://redmine.lighttpd.net/projects/1/wiki/Docs_ModRewrite#Description
[14:02] <kyrofa> zyga, /etc/apparmor.d/usr.bin.ubuntu-core-launcher
[14:03]  * ogra_ grumbles about systemd log output 
[14:03] <ogra_> ..."Failed with result 'exit-code'."
[14:03] <kyrofa> zyga, though have you built another image since that was released? (or is it included in the OS snap...)
[14:03] <ogra_> why cant it actually write the exit code in there
[14:03]  * ogra_ shakes head
[14:08] <kyrofa> zyga, yeah the apparmor profile uses HOME, which should be set correctly to /root. So I suspect you simply don't have the update
[14:08] <zyga> kyrofa: I have the workaround for sure so something else might be broken
[14:08]  * zyga returns to checking what
[14:09] <kyrofa> zyga, if you can upload an image somewhere I'd be happy to check it out
[14:09] <zyga> kyrofa: it's the stock image I built before, I don't want to re-flash it because I use classic dimension heavly for skill development
[14:10] <zyga> kyrofa: looking at u-c-l profile, where does it have access to $HOME/snaps?
[14:10] <kyrofa> zyga, makes sense
[14:10] <zyga> 14:58 < zyga> Feb 18 13:57:55 localhost.localdomain kernel: audit: type=1400 audit(1455803875.084:81): apparmor="DENIED" operation="mkdir" profile="/usr/bin/ubuntu-core-launcher" name="/root/snaps/" pid=4831 comm="ubuntu-core-lau" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
[14:11] <kyrofa> zyga, check the last few lines of the profile (83 and on)
[14:12] <zyga> kyrofa: I don't see anything that affects $HOME in the profile
[14:12] <zyga> kyrofa: http://paste.ubuntu.com/15109503/
[14:12] <zyga> kyrofa: that's my hacked copy
[14:12] <kyrofa> zyga, yeah you don't have the update then. Here, use this:
[14:12] <zyga> kyrofa: ah, perfect, thanks
[14:12]  * zyga wonders if he can just update snappy then
[14:13] <zyga> update is not released?
[14:13] <zyga> ubuntu-core         2016-02-12 16.04.0-8.armhf canonical
[14:13] <kyrofa> zyga, http://paste.ubuntu.com/15109578/
[14:13] <zyga> trying
[14:13] <kyrofa> zyga, I think that's the OS snap... right? Which needs it needs to be rebuilt before the update is actually distributed?
[14:14] <ogra_> i'll try to get to that today and bump all os snaps ...
[14:14] <kyrofa> which means it needs*
[14:14] <ogra_> (prob iis that mvo didnt pick the same version for all of them so its all manual hackery )
[14:14]  * kyrofa is still a little fuzzy on the kernel/os/magic snaps
[14:15] <zyga> kyrofa: all good, thanks
[14:15] <kyrofa> zyga, yeah? Working now?
[14:15] <zyga> kyrofa: I found unrelated bugs in snappy (it seems that "snappy service" blindly tries to run crazy stuff that's not a service
[14:16] <zyga> kyrofa: ) but starting the systemd unit manually makes things go
[14:16] <zyga> kyrofa: so I have a skill-based service in operation :-)
[14:16] <kyrofa> zyga, ooo, that's fun. What type of crazy stuff?
[14:16] <zyga> kyrofa: background piglow
[14:16] <kyrofa> (make sure you log those!)
[14:16] <zyga> kyrofa: Feb 18 14:14:07 localhost.localdomain ./snappy[5012]: main.go:50: DEBUG: [./snappy service start] failed: unable to start pi2-piglow's service foreground: [start pi2-piglow_foreground_INANbBEQgddX.service] failed with exit status 6: Failed to start pi2-piglow_foreground_INANbBEQgddX.service: Unit pi2-piglow_foreground_INANbBEQgddX.service failed to load: No such file or directory.
[14:16] <zyga> kyrofa: note: foreground is _not_ a background command/service
[14:17] <zyga> kyrofa: the source for this snap is at github.com/zyga/snappy-pi2-piglow
[14:17]  * zyga pushes new stuff
[14:17] <zyga> done
[14:18] <zyga> (now done)
[14:18] <kyrofa> zyga, haha, I was gonna say...
[14:18] <zyga> Feb 18 14:14:07 localhost.localdomain ./snappy[5012]: main.go:50: DEBUG: [./snappy service start] failed: unable to start pi2-piglow's service foreground: [start pi2-piglow_foreground_INANbBEQgddX.service] failed with exit status 6: Failed to start pi2-piglow_foreground_INANbBEQgddX.service: Unit pi2-piglow_foreground_INANbBEQgddX.service failed to load: No such file or directory.
[14:18] <kyrofa> zyga, yeah, how does foreground turn into a service?
[14:18] <zyga> er, damn paste
[14:18] <zyga> kyrofa: it doesn't-- there is no .service file for it
[14:19] <zyga> I don't know the service generation code by heart, maybe something is wrong there
[14:19] <kyrofa> zyga, huh... but the snap.yaml looks okay?
[14:20] <zyga> kyrofa: let's see
[14:20] <zyga> kyrofa: yes
[14:21] <zyga> kyrofa: I wouldn't worry yet, this might be some old/new snappy combination
[14:21] <zyga> I may have used old (non trunk) version of snappy to instal the snap perhaps
[14:21] <kyrofa> zyga, probably-- I was through all that code recently and it seemed okay
[14:21] <zyga> kyrofa: if it happens after clean reproduction I'll start chasing it
[14:21] <kyrofa> zyga, sounds good!
[14:25] <zyga> who can I poke to review / approve squashfs app in the store?
[14:25] <zyga> pi2-piglow.zygoon revision 2
[14:26] <longsleep> ricmm, ogra_ https://github.com/strukturag/spreed-webrtc-snap - works fine for me and should build fine on arm64 as well if you run snapcraft there
[14:27] <longsleep> ricmm, ogra_ it currently get the code from develop branch as i had to fix a variable conflict in the Makefile
[14:27]  * zyga must say that the piglow executable, stripped, is comparable in size to the side of .yaml/changelog ;)
[14:48]  * jdstrand reads backscroll and sees it is resolved
[14:48] <jdstrand> yes, ubuntu-core-launcher is part of the os snap. if an os snap hasn't been generated in a while, the fix won't be there
[14:49] <jdstrand> kyrofa: and the workaround rule was '/**/ rw,' - the trailing '/' is important :) ( though /** rw certainly would've worked too, but basically invalidated confinement :)
[14:50] <jdstrand> as workarounds go, it would've been effective though :)
[14:50] <kyrofa> jdstrand, heh. Yeah, all resolved :)
[14:51] <kyrofa> jdstrand, good morning by the way!
[14:51] <jdstrand> zyga: as for chmod-- this needs architects input. sure, a chmod will make it 'just work' for the ubuntu user, but there are a lot of implications in that
[14:51] <jdstrand> kyrofa: hi!
[14:52] <jdstrand> zyga: my gut feeling is that a chmod for the device for the user and a skills assignment to the snap are conflating two different things
[14:54] <jdstrand> we don't have a strong story of users and groups on snappy yet and that probably needs to be discussed
[14:54] <zyga> jdstrand: yep, I think this needs proper design
[14:54] <jdstrand> cool
[14:54] <zyga> jdstrand: hmm, perhaps in this case we could cheat by putting that device in the cgroup (as we do) and chmodding it *there*
[14:54] <zyga> so the user doesn't get it
[14:54] <zyga> but the app does
[14:54] <jdstrand> I'm happy to be part of that conversation, but I think tyhicks should also be a part of it
[14:55] <zyga> jdstrand: ok, let's do it
[14:56] <jdstrand> zyga: I think we want pitti to have input too
[14:56] <zyga> jdstrand: shall I open a bug on this to track it?
[14:57] <jdstrand> I think that makes sense. something about requiring sudo for certain devices after skills assignment
[15:09] <ogra_> longsleep, thanks, i'll try it out before EOD
[15:15] <longsleep> ogra_: For comparison, this is the full output for snapcraft snap for me: http://paste.ubuntu.com/15111240/
[15:15] <ogra_> thx
[15:15] <longsleep> ogra_: i am not sure about the dependencies, i added some but might have missed autoconf or something else
[15:16] <ogra_> k
[15:34] <zyga> kyrofa: can you do a sanity check please
[15:34] <zyga> kyrofa: install v2 of the p2-piglow.zygoon snap from the github url I mentined earlier
[15:34] <zyga> kyrofa: and see what services you have
[15:34] <zyga> ubuntu@localhost:~$ sudo ./snappy service status
[15:34] <zyga> Snap            Service         State
[15:34] <zyga> pi2-piglow      background      enabled; loaded; failed (failed)
[15:34] <zyga> pi2-piglow      foreground      ; not-found; inactive (dead)
[15:34] <zyga> !?
[15:35] <kyrofa> zyga, I don't actually have an image where that stuff will work :P
[15:37] <zyga> kyrofa: looking at the service code
[15:37] <zyga> kyrofa: the condition to see if something is a service is bogus IMHO
[15:37] <zyga>             if serviceName != "" && serviceName != name {
[15:37] <zyga>                 continue
[15:37] <zyga>             }
[15:37] <zyga> everything else is a service
[15:37] <zyga> what?
[15:38] <kyrofa> zyga, wait... shouldn't that be using the daemon keyword?
[15:38] <zyga> in other words _everything_ is a service
[15:38] <zyga> kyrofa: exactly
[15:38] <zyga> kyrofa: I'll fix that
[15:45] <zyga> https://github.com/ubuntu-core/snappy/pull/495/files
[15:51] <zyga> revoke works
[15:51] <longsleep> ogra_: What would i select to upload a snap to the store for 16.04? rolling-core?
[15:51] <zyga> now I only want to know which signal does systemd send to stop an app
[15:51] <zyga> (a service)
[15:52] <zyga> so that piglow can react to it by shutting down the lights before it goes
[15:52] <ogra_> longsleep, yeah
[15:55] <zyga> ah, that's SIGTERM
[15:55] <zyga> nice
[15:58] <longsleep> ogra_: mhm automated review failed, (NEEDS REVIEW) squashfs pkg lint_is_squashfs
[15:58] <longsleep> and one warning: unknown entries in package.yaml: 'apps,description,summary,uses' lint_snappy_unknown
[15:59] <ogra_> longsleep, sounds like a false positive ... beuno ^^^ ?
[16:00] <ogra_> Snapping spreed-webrtc_0.24.11-1_arm64.snap
[16:00] <ogra_> FATAL ERROR:Mksquashfs requires more physical memory than is available!
[16:00]  * ogra_ cries
[16:00] <longsleep> lol
[16:01] <longsleep> how much memory did you give that box?
[16:01]  * ogra_ hopes a swapfile will be respected
[16:01] <kyrofa> ogra_, it will
[16:01] <ogra_> cool !
[16:01] <ogra_> longsleep, its real HW with 1GB
[16:01] <longsleep> ah
[16:01] <kyrofa> ogra_, it's the only way my snaps build on the arms I have here-- a 16GB swapfile :P
[16:02] <ogra_> wow, thats bad
[16:02] <longsleep> my vagrant box has 758352 memory and the same as swap and it worked to build
[16:03] <kyrofa> ogra_, and that's a slight lie. I could make with no -j parameter and it would need less, but then it would take days
[16:04] <longsleep> ogra_: what hardware do you actually use?
[16:04] <ogra_> longsleep, dragonboard
[16:04] <longsleep> ah ok cool
[16:04] <beuno> ogra_, longsleep, it is false positives, will ve fixed soon
[16:05] <beuno> kyrofa, ogra_, you can build snaps on Launchpad!
[16:05] <kyrofa> beuno, indeed, and I plan on figuring that all out very soon
[16:05] <kyrofa> beuno, but we're doing arm64
[16:05] <kyrofa> beuno, launchpad only has 32-bit arms, no?
[16:05] <ogra_> kyrofa, hmm, do you use chroots when building ?
[16:06] <kyrofa> ogra_, no, why?
[16:06] <ogra_> kyrofa, no, LP builds our rootfses :)
[16:06] <ogra_> so there are also arm64 machines
[16:06] <kyrofa> ogra_, ah, excellent!
[16:06] <ogra_> kyrofa, because i just noticed 1GB is fine ... i just forgot to mount /proc and /sys
[16:06] <kyrofa> Ah!
[16:06] <beuno> kyrofa, it as arm64 for snaps  :)
[16:13] <ogra_> longsleep, works great !
[16:13] <longsleep> ogra_: fantastic!
[16:13] <longsleep> ogra_: thans for testing
[16:13] <longsleep> +k
[16:13] <ogra_> thansk for building !
[16:17] <ogra_> so sad the ubuntu phone browser doesnt work with it :(
[16:18] <longsleep> what html/javascript engine does that browser use?
[16:18] <ogra_> not sure ... popey ^^^ do you know ?
[16:19] <ogra_> not v8 afaik
[16:19] <popey> it's chromium, so blink.
[16:19] <ogra_> blink is the renderer
[16:20] <ogra_> and that all we use from chromium afaik ... the js engine was something different
[16:20] <longsleep> if its chromium including v8 and the media enginges in the back then it could work with if recent enough
[16:20] <ogra_> i'm pretty sure it is neither
[16:21] <longsleep> currently we support Chromium 38 or newer
[16:21] <longsleep> it might somewhat down to Chromium 30
[16:22] <longsleep> work somewhat
[16:22]  * ogra_ asked in #ubuntu-touch 
[16:22] <ogra_> we onyl use blink (and even re-work it for Qt)
[16:23] <popey> "Mozilla/5.0 (Linux; Ubuntu 14.04 like Android 4.4) AppleWebKit/537.36 Chromium/35.0.1870.2 Mobile Safari/537.36"
[16:23] <popey> thats OTA-9
[16:23] <popey> so chromium 35
[16:23] <ogra_> right, doesnt talk about js
[16:23] <longsleep> well, Chromium 35 would be too old in any case to connect to any recent browser
[16:24] <ogra_> nor is it chromium beyond the renderer ... thats like using gecko with all your own stiff and showing firefox in the UA :P
[16:24] <ogra_> ok, seems i was wrong, it is actually v8
[16:25] <longsleep> question is if all the media extensions are compiled in including the capture code
[16:25] <longsleep> webrtc for that matter
[16:25] <ogra_> no
[16:25] <longsleep> dtls
[16:25] <longsleep> srtp :)
[16:25] <ogra_> neither of them because they would have to be hooked into the toolkit
[16:25] <ogra_> whicfh isnt dont yet
[16:25] <ogra_> (my webrtc bug is open since 2.5y ... eventually it will come though :) )
[16:26] <ogra_> *isnt done
[16:27] <ogra_> we have basic camera and mic access working i think ... just no webrtc integration yet
[16:28] <ogra_> i wonder how much would work if we cheated inthe UA though
[16:35] <longsleep> ogra_: what do you mean cheating in the UA?
[16:35] <longsleep> ogra_: we are doing feature detection for pretty much everything, so the UA would not help
[16:35] <ogra_> longsleep, telling the server it is chromium 38
[16:35] <ogra_> ah, k
[17:16] <gregburd> I just tried Snappy for the first time on a NUC.  I like where the project is headed, the integration of a stable upgrade image A->B (and back) is a great step forward.  It takes the best part of CoreOS and grafts it into a Ubuntu world.  Thanks!  The "snappy" package manager is headed in the right direction as well, but I have to wonder (and I'm sure I'm
[17:16] <gregburd> not the first to ask this) why not simply adopt the Nix package manager format?  Why invent yet another thing when Nix seems to have all the bases covered that snappy would like to address (and more)?
[17:17] <ogra_> does nic integrate with apparmor and seccomp ?
[17:17] <ogra_> *nix
[17:17] <ogra_> does it use squashfs files as readonly filesystems of its packages ?
[17:18] <ogra_> (i never heard of Nix, just curious)
[17:18] <gregburd> http://nixos.org/nix/
[17:19] <ogra_> seems to onyl be a package manager though ... you should take a look at snapcraft too if you look at snappy :)
[17:19] <gregburd> http://sandervanderburg.blogspot.com/2015/04/an-evaluation-and-comparison-of-snappy.html is a good evaluation by a Nix maintainer of Snappy
[17:20] <ogra_> snappy (the package manager) is very deeply integrated with the OS too ... it was essentially built around all the things we learned from the phone OS
[17:21] <gregburd> So, I'm not saying "ditch all of Snappy" I'm saying "steal liberally the ideas from Nix and integrate them into Snappy" especially the way that Nix versions and inter-relates package dependencies (sim-link tree with a hash rather than version number used to separate packages).
[17:23] <gregburd> I used to work at Amazon/AWS and there we had a similar (to Nix) way of managing package dependencies in deployment (called Brazil) with versioned trees of inter-dependent packages.
[17:23] <gregburd> I like that deep integration ogra_ that makes sense.
[17:23] <gregburd> If my mom or some other non-technical person is ever going to experience Ubuntu Desktop then we'll need that level of integration.
[17:24] <gregburd> I'm sure that the phone project pushed the developers hard in the direction of super simple/reliable package distribution.
[17:25] <ogra_> well, snappy does effectivbely not have any dependencies
[17:25] <ogra_> you bundle everything
[17:27] <ogra_> (you can have library snaps, but only within your own namespace)
[17:27] <gregburd> ogra_ isn't that going to hammer memory as each different process brings its own copy of glibc along with it?
[17:27] <ogra_> well, glibc is on the system. as long as you dont differ too much you dont really need to ship it (but you can indeed)
[17:28] <ogra_> but yeah, there is surely some duplication that will eat some diskspce at least
[17:28] <gregburd> my point is more generally related to shared libraries that will, in a snappy world, be duplicated and not shared
[17:28] <gregburd> and RAM and cache lines
[17:29] <gregburd> and that's power and performance lost
[17:29] <gregburd> no?
[17:29] <ogra_> right, yxou should just build static binaries if you can :)
[17:29] <gregburd> er, I disagree
[17:29] <ogra_> you prefer shared libs that arent shared ?
[17:29] <gregburd> how is that not going to introduce the same problem?
[17:29] <gregburd> no :)
[17:30] <ogra_> either way, the confinement wont allow apps to share resources on that level
[17:31] <ogra_> (unless the libs come from your own namespace ... i.e. libreoffice.ogra wouldnt have to ship boost but could consume libboost.ogra)
[17:31] <gregburd> In the Nix (and Brazil) world a shared lib can indeed be shared by many other packages iff those packages all required the same version/config/build/dependencies that went into building glibc
[17:31] <gregburd> So, where there is overlap the shared libraries are indeed shared
[17:31] <ogra_> right, then we are back at dpkg :)
[17:31] <gregburd> not really.
[17:31] <ogra_> you ahve deps ... you have the same old probs
[17:32] <ogra_> while bundling works just fine in the Mac and Windows world since ages
[17:32] <ogra_> and yes, there might be some penalty ... but obviously neither of the other systems is hit by that to hard
[17:33] <gregburd> So, here again we'll disagree (and as a former NeXT engineer I might have some knowledge on this topic)
[17:33] <ogra_> (well, for some value of "fine" regarding windows :P )
[17:33] <gregburd> But hey, I'm not here to start a fight
[17:33] <gregburd> Please just consider reviewing the differences between Nix and Snappy with an open mind.
[17:33] <ogra_> the point is that theoretically the snap should be completely independent from the OS
[17:33] <ogra_> and be used standalone
[17:34] <gregburd> Okay, fair point and I'm certain I don't fully get how Snappy is supposed to work as yet.
[17:34] <ogra_> so that you can upgrade/rolback both of them completely independent ...
[17:34] <ogra_> if you have deps you will hit massive probs with that rollback mechanism for example
[17:35] <gregburd> Nix can do that as well (if "them" means "various applications and their package dependencies")
[17:35] <ogra_> the typical focus is your home router where you install a NAS snap and attch disks, plug in a WLAN stick and can install an AP snap to manage your WIFI ... etc ... also robots where you can install different types of autopilots ...
[17:36] <ogra_> while the vision of snappy doesnt stop there and will go towards desktops and phones over time, IoT, small devices, cloud instances and such are the current focus
[17:37] <ogra_> i.e. at the current state it is rather unlikely you will see firefox or libreoffice snaps for such devices :)
[17:37] <gregburd> So, here's the thing.  I would have put Ubuntu into deployment today for a rollout of a large number of NUCs that have to be managed as remote Kiosks if it had: 1) an opensource Omaha-esque centralized management setup, 2) a more Nix-like structure for inter-package dependency management and 3) a way to bridge the apt/dpkg world into the Snappy world until
[17:37] <gregburd> the Snappy world is as rich as the existing apt/dpkg world is today (so a way to deal with the practicalities of an incomplete new system).
[17:37] <ogra_> but rather the small samba server with a web interface ... or a upnp server or some such
[17:38] <ogra_> while you cant bridge it, you can use snappy in classic mode
[17:38] <gregburd> I get that, but don't preclude the future use cases with decisions that focus on today.
[17:38] <ogra_> (in 16.04 that is)
[17:39] <ogra_> snappy enable-classic: snappy shell classic ... and you are in an environment with full apt support ...
[17:39] <ogra_> you will not be able to run services in there (they wouldnt survive a reboot) but you can use snapcraft in there to just rapidly snap up wnat you need and turn it into a snap package immediately
[17:40] <gregburd> so that's the model for moving existing packages forward?
[17:41] <ogra_> that the model for ... well, enabling you to turn anything into a snap quickly
[17:42] <ogra_> so there is no need to use dpkg/apt ... its just a small yaml file away to turn anything you need into a snap
[17:42] <gregburd> ok, that's promising
[17:42] <gregburd> anything like the Omaha server/service available yet?
[17:43] <ogra_> if you invest a bit more you can also write a config hook for any deb you use that can be accessed through snappys REST api
[17:43] <ogra_> never heard of omaha ... is that like puppet/chef ?
[17:44]  * longsleep has heard of Omaha beach
[17:44] <ogra_> drinks and sun !
[17:44] <gregburd> https://github.com/google/omaha
[17:45] <gregburd> https://omaha.googlecode.com/svn/wiki/OmahaOverview.html
[17:45] <ogra_> ah, no need for that :)
[17:45] <ogra_> snappy cares
[17:45] <gregburd> https://coreos.com/docs/coreupdate/custom-apps/coreupdate-protocol/
[17:45] <ogra_> there is a builtin auto-update service that queries the sotre regulary
[17:45] <ogra_> *store
[17:46] <gregburd> so, that's great but sometimes services will need to have centralized control of the rollout of new software - limit the damage, etc.
[17:46] <ogra_> if you update your snap in the store it gets pushed out
[17:46] <ogra_> the store has staging areas
[17:47] <gregburd> how are end devices assigned to various channels?
[17:47] <ogra_> so you can push stuff to the edge channel and have your QA people pull that first ... once they give green light you can switchj it over to stable
[17:47] <ogra_> thats a good question someone from the architects needs to answer :)
[17:48] <ogra_> i havent played with that yet beyond ... well snappy install <packagename>/edge  ... which is the manual variant
[17:49] <ogra_> i assume you can define it image wide via your gadget snap (which effectively defines the whole system of an image)
[17:50] <gregburd> I'll have to review that part of Snappy, but I'm not sure it provides the level of control and flexibility I needed for a service that I used to run at Amazon/AWS.
[17:50] <gregburd> interesting discussion, thanks for the time
[17:50]  * gregburd back to work!
[17:50] <ogra_> :)
[19:13] <popey> ogra_: do you have an example of a snap that needs network access?
[19:13] <popey> (I assume network is blocked by default unless specified)
[19:13] <ogra_> i think client is always allowed ... (not sure about the snapcraft 2.0 world though)
[19:15] <popey> yeah, 2.x
[19:15] <ogra_> popey, https://github.com/strukturag/spreed-webrtc-snap/blob/master/snapcraft.yaml  see the "uses" thing between line 13 and 16 ... then see line 11 how the binary/service  uses it
[19:15] <popey> I'm getting odd network errors so assume not
[19:15] <popey> thanks
[20:10] <zyga> ogra_: there ware some back and forth but I think we'll see snaps *not* getting network access in 16.04 unless they asked for it
[20:10] <zyga> popey: ^^
[20:10] <zyga> popey: so do ask for the migration-skill and for the network-client cap
[20:10] <zyga> or something
[20:11]  * zyga really EODs
[20:33] <kyrofa> ogra_, hey does classic dimension not work on the dragon image?
[20:34] <kyrofa> zyga, ah, good to know!
[20:34] <kyrofa> zyga, I think that's smart
[20:34] <kyrofa> zyga, oh you're gone
[20:35] <kyrofa> ogra_, I get 'needle "ubuntu;xenial;arm64;default;" not found
[20:37] <kyrofa> elopio, you may know something about that ^^  too, perhaps?
[20:38] <elopio> needle? no, I don't know about that. I still have to find some time to resume my dragonboard testing.
[21:12] <plars> elopio: some output from the checkbox-ized version of the tests... there are a few permission problems, possibly because we are running them from a snap? http://paste.ubuntu.com/15122636/
[22:02] <robert_ancell> elopio, can you give me some pointers on a user test for https://github.com/ubuntu-core/snappy/pull/409?
[23:05] <elopio> robert_ancell: from your comment, I suppose we could write a test that installs and remove a snap without sudo. I know nothing about polkit, so I'm not sure how we could set up the configuration for that user.
[23:06] <robert_ancell> elopio, You'd probably want to to run a mock polkit service, but there's no mocked d-bus services in snappy currently are there?
[23:06] <elopio> robert_ancell: basically this: https://github.com/ubuntu-core/snappy/blob/master/integration-tests/tests/installApp_test.go#L58
[23:06] <elopio> without sudo with polkit.
[23:08] <elopio> robert_ancell: no, there is not. But running the tests we have sudo, so we could get it working, I guess.
[23:08] <elopio> but before exploring the mock option, is there a reason we can't use the real service?
[23:21] <robert_ancell> elopio, I'm just don't know what environment you are running in. You probably want to test the two cases with PolicyKit (accepted / declined)
[23:23] <elopio> robert_ancell: We are running this in a snappy system in scalingstack, bbb and raspberry pi. In my ignorance, I imagine that there's a way to tell polkit that the ubuntu user can install apps. And then there's a way to tell it to revoke that permission.
[23:23] <elopio> then we just run snappy install and check the result.
[23:24] <robert_ancell> elopio, is that ubuntu-core?
[23:24] <robert_ancell> Because then we wont have polkit
[23:24] <robert_ancell> If we can write the polkit config, we can configure both cases
[23:25] <elopio> robert_ancell: so, how are you going to install polkit on your system?
[23:26] <robert_ancell> That's a challenge...
[23:59] <elopio> robert_ancell: ok, I would say that's the first step. In the ideal scenario, we will be able to install it just as you install it, and then we can run a test to make sure that we will never break your system.