[08:24] <dholbach> good morning
[08:30] <morphis> sergiusens: ping
[08:31] <sergiusens> morphis, pong?
[08:31] <sergiusens> morning
[08:31] <morphis> sergiusens: morning :-)
[08:31] <sergiusens> 5:30am here :-)
[08:31] <morphis> quite early
[08:31] <sergiusens> but wide awake due to jetlag
[08:31] <sergiusens> 11 hour time jumps can do that
[08:31] <morphis> even better ;)
[08:32] <morphis> sergiusens: with snapcraft on xenial I am currently getting: https://paste.ubuntu.com/15413380/
[08:32] <morphis> sergiusens: nothing in snapcraft seem to create those two directories during the stage process
[08:32] <morphis> so I am wondering what goes wrong
[08:32] <morphis> loosk like snapcraft is adding them statically to CFLAGS
[08:33] <morphis> just creating both fixes the problem
[08:33] <sergiusens> morphis, interesting; this seems to be a snapcraft bug; it declares that include path (just in case)
[08:33] <sergiusens> thanks for pointing me out that inherited legacy code again :-)
[08:33] <sergiusens> morphis, can you file a bug?
[08:33] <morphis> sergiusens: sure, on github or launchpad?
[08:34] <sergiusens> and include your snapcraft.yaml
[08:34] <sergiusens> morphis, https://bugs.launchpad.net/snapcraft/+filebug
[08:34] <morphis> sergiusens: aye
[08:45] <dholbach> ogra_, mvo: do you know who's responsible for the Mt7623 snap?
[08:46] <dholbach> or who has access rights for it?
[08:46] <dholbach> we received a request to change the logo
[08:53] <morphis> sergiusens: https://bugs.launchpad.net/snapcraft/+bug/1558965
[08:58] <mvo> dholbach: I have no idea, probably best to ask in #u1-internal
[09:00] <dpm> dholbach, ogra_, if I'd want to create a snap from a .deb package, which is not on the archive, is there any snapcraft.yaml trick I can use to download the .deb from a URL, just as if it had been specified in 'stage-packages'?
[09:02] <dholbach> dpm, can you put it in a PPA and use either the launchpad build or the LOCAL SOURCES trick?
[09:02] <dpm> dholbach, I was trying to avoid that, as sergiusens mentioned that LOCAL_SOURCES was rather deprecated
[09:04] <dholbach> I think the official way we want to use is PPAs and LP builds
[09:04] <dholbach> but for local testing, while it's still available in the code, I'd recommend the local sources trick
[09:04] <dholbach> but maybe sergiusens has a different idea
[09:05] <ogra_> dholbach, havent heard of that snap
[09:05] <dpm> dholbach, right, but is not PPAs = LOCAL_SOURCES?
[09:05] <dpm> or do can the LP builds somehow use external PPAs?
[09:06] <dholbach> dpm, I have never used it yet, but I assume that it's like normal PPAs - you can make them depend on each other
[09:07] <sergiusens> dholbach, dpm just make sure it is in you local sources.list
[09:07] <dpm> I'm a bit confused now
[09:07] <dpm> so the package I'm trying to snap is both in a PPA and available as a downloadable .deb
[09:08] <dpm> so what's the recommended way to snap it if I just want to package the binaries, and not build them?
[09:10] <dholbach> ogra_,
[09:10] <dholbach>  Mt7623
[09:10] <dholbach> MT7623 support package MT7623 OEM snap for IoT demo purpose
[09:10] <dholbach> (https://developer.ubuntu.com/en/snappy/start/gadget-snaps/)
[09:10] <ogra_> dholbach, see PM :)
[09:10] <dholbach> gracias!
[09:24] <morphis> sergiusens: also looks a bit like snapcraft is not extracting all deb packages I put into stage-packages correctly
[09:25] <morphis> sergiusens: is there some condition around what gets extracted and what not?
[09:25] <morphis> sergiusens: https://paste.ubuntu.com/15413620/
[09:34] <sergiusens> morphis, can you check in parts/<part>/install ?
[09:35] <morphis> sergiusens: sure
[09:35] <morphis> sergiusens: hm there it is
[09:36] <sergiusens> morphis, do you have a stage or snap entry in your snapcraft.yaml?
[09:36] <morphis> sergiusens: ah .. my fault :-)
[09:36] <morphis> I strip it from the list of staged files
[09:36] <sergiusens> morphis, I'm fixing this in a pkg-config branch I have
[09:37] <morphis> sergiusens: but looks like the build is referencing to stage/ somehow
[09:37] <sergiusens> morphis, so you won't be hit by this again and what you did might as well be correct in the future
[09:37] <zyga> good morning
[09:37]  * sergiusens starts getting breakfast ready
[09:37] <morphis> zyga: morning
[09:38] <morphis> sergiusens: you mean stripping it from files being staged affects the build through pkg-config?
[09:40] <morphis> sergiusens: https://paste.ubuntu.com/15413661/ is still what I get during the build, shouldn't the build only point to parts/<current>/install?
[09:42] <sergiusens> morphis, the problem is pkg-config can only have one SYSROOT at a time
[09:42] <Chipaca> pitti: you around?
[09:42] <sergiusens> morphis, I've been fixing that; but not there yet (missing some corner cases)
[09:43] <morphis> sergiusens: ok, got it, thanks
[09:44] <sergiusens> morphis, and then yes, you would use 'install' for the part and not need to stage if not needed
[09:46] <morphis> sergiusens: ok
[11:27] <dpm> mvo, is there a way to query snapd for all the metadata of an app?
[11:31] <mvo> dpm: I don't think we have this right now, you can query the status if it is a service. why do you ask, what do you need here?
[11:37] <dpm> I think it's returning outdated metadata, and I wanted to check
[11:41] <kyrofa> Good morning
[12:05] <morphis> is there still a way with the new snappy stuff for 16.04 to let a snap being unconfined? like the security-template: unconfined switch we had with 15.04?
[12:06] <sergiusens> morphis, there is with old-security; look at the snapcraft examples
[12:06] <morphis> oh great
[12:07] <morphis> sergiusens: is that documented somewhere too?
[12:07] <sergiusens> morphis, that is an mvo question
[12:08] <morphis> sergiusens: basically I have a daemon I want to run unconfined
[12:10] <sergiusens> morphis, the only form of documentation I have on snapcraft's side are the examples and https://github.com/ubuntu-core/snapcraft/blob/master/schema/snapcraft.yaml#L57
[12:10] <morphis> sergiusens: I see
[12:10] <sergiusens> morphis, I don't want to write more until the snappy guys get some ticks on interfaces themselves
[12:11] <sergiusens> morphis, and that lands from here https://github.com/ubuntu-core/snapcraft/blob/master/schema/snapcraft.yaml#L248
[12:11] <sergiusens> morphis, which needs to ref'ed from `apps` in https://github.com/ubuntu-core/snapcraft/blob/master/schema/snapcraft.yaml#L185
[12:12] <morphis> I see, so defining a plug I then use in my app
[12:12] <sergiusens> morphis, this https://github.com/ubuntu-core/snapcraft/blob/master/examples/ros/snapcraft.yaml and this https://github.com/ubuntu-core/snapcraft/blob/master/examples/busybox/snapcraft.yaml should get you the gist of it
[12:15] <morphis> sergiusens: so something like https://paste.ubuntu.com/15414149/ should do the trick
[12:16] <sergiusens> morphis, yes
[12:16] <morphis> lets see
[12:16] <sergiusens> morphis, I hope we did a good job with the schema to detect incompatible options/combinations
[12:17] <morphis> sergiusens: I must say I like snapcraft more and more, got quite more solid then when I used it the last time back in november last year
[12:20] <morphis> sergiusens: but yeah, that trick works
[12:37] <morphis> mvo: ping
[12:46] <jospoortvliet> kyrofa: awesome! Sorry I only see it now - will push the blog in a few minutes OK :D
[12:46] <jospoortvliet> thanks a lot
[12:47] <kyrofa> jospoortvliet, no problem! Good afternoon :)
[12:47] <jospoortvliet> now for putting them on a stick, so I can demo it at Chemnitzer Linux Tage (conference happening this weekend) ;-)
[12:47] <kyrofa> Ooo, good luck!
[12:47] <jospoortvliet> will be fun, np
[12:48] <noizer> Hello guys
[12:49] <noizer> I have some trouble with changing my apparmor. I think an issue in Snappy. here is the following error that I have. :http://pastebin.com/t87eZpjz
[12:49] <noizer> error: http://pastebin.com/t87eZpjz
[12:49] <noizer> Does somebody got any idea how I can fix it?
[12:50] <jdstrand> we talked about this before
[12:50] <jdstrand> this is possibly a bug in the ubuntu-core-launcher
[12:50] <noizer> jdstrand: Yes but can it be fixed?
[12:51] <noizer> jdstrand: In some later version?
[12:51] <jdstrand> /home/ubuntu/snaps/ad.sideload/LTKVlHMSjhpm/snaps/ is not a valid path that the launcher should be looking at
[12:51] <noizer> Maybe i can make that path so ...
[12:51] <jdstrand> noizer: please file a bug at https://bugs.launchpad.net/snappy/+filebug with steps to reproduce if you're sure you are setting up everything correctly
[12:52] <mvo> morphis: pong
[12:54] <noizer> jdstrand: But you knows more about it what I'm trying to do and thats not in the filosofie of snappy
[13:03] <jdstrand> noizer: sure-- it might be you are not setting an env var correctly. you should look at how things are set in /snaps/bin to see why the last /snaps/ is being appended. only when you are sure that the launcher is doing the wrong thing, file the bug
[13:05] <kyrofa> noizer, yeah, check the $SNAP_USER_DATA variable
[13:05] <noizer> jdstrand: I will look into it and let you know for more advice
[13:06] <noizer> kyrofa: jdstrand Can i check it just over SSH to my raspi pi?
[13:07] <kyrofa> noizer, first off, I'm assuming this is a binary, not a daemon, right?
[13:08] <kyrofa> noizer, if yes, you can SSH in and check out the /snaps/bin/<binary> wrapper. If it's a daemon, you can SSH in and check out the /etc/systemd/system/<service>.service file
[13:16] <sergiusens> kyrofa, here's one for you https://github.com/ubuntu-core/snapcraft/pull/379 :-)
[13:17] <sergiusens> kyrofa, if you know of a stable snap on the staging server I can add an int test; I'm weary to add one otherwise
[13:17] <kyrofa> sergiusens, not really-- everything I've ever done on staging was temporary :P
[13:18] <kyrofa> sergiusens, though we have an upload test-- maybe couple them together a little?
[13:18] <sergiusens> jdstrand, hey, the sudo problem needs to be solved regardless of what dir we default to as one of the system components creates the dir layout and if it is the first run and sudo is involved we create a boo boo
[13:18]  * sergiusens speaks in loose terms since it is Friday after all
[13:19] <kyrofa> sergiusens has kids
[13:23] <sergiusens> just the one ;-)
[13:24] <sergiusens> nice coveralls is giving me nice messages now
[13:27] <kyrofa> sergiusens, explain this PR to me. How does the kernel needs snaps?
[13:28] <mvo> ogra_, kyrofa: you had issues with services not starting, i assume this is still the case? I am testing this right now
[13:28] <kyrofa> mvo, indeed-- they aren't activated on boot in 16.04 anymore
[13:29] <sergiusens> kyrofa, look at the kernel pr :-)
[13:29] <mvo> kyrofa: ok, let me try that
[13:29] <sergiusens> kyrofa, in summary, generic initrd
[13:29] <mvo> kyrofa: only when using u-d-f, right?
[13:29] <sergiusens> mvo, is there any other tool?
[13:29] <kyrofa> mvo, according to Chipaca and niemeyer I found out it isn't supposed to, though. Right, u-d-f
[13:30] <mvo> kyrofa: eh, wuut?
[13:30] <kyrofa> mvo, I learned that model assertions will be the way to do this
[13:30] <mvo> kyrofa: indeed and yet that should still activate them
[13:30] <mvo> kyrofa: plus we don't have them
[13:30] <kyrofa> mvo, so I ended up making a gadget snap with built-in to work for now (preinstalled doesn't work either)
[13:30] <mvo> sergiusens: I heard some talk about ubuntu-image ;)
[13:30] <kyrofa> mvo, indeed
[13:30] <mvo> kyrofa: but build-in does work?
[13:30] <sergiusens> mvo, blocked on generic initrd and model assertions ;-)
[13:31] <kyrofa> mvo, yeah, the gadget.go code parses that bit and activates on boot
[13:31] <mvo> kyrofa: ok
[13:32] <mvo> kyrofa: hm, hm, still awkward that we have --install in u-d-f and it does not work
[13:32] <mvo> kyrofa: I guess I kill that for now at least
[13:32] <kyrofa> mvo, yeah it's really hard to preinstall stuff now :P
[13:32] <kyrofa> mvo, I had to fork the entire rpi2 gadget
[13:32] <mvo> ogra_: you also had an issue with stuff not activated, was it the same?
[13:32] <mvo> kyrofa: that sucks (pardon my language)
[13:32] <sergiusens> mvo, btw, you may want to add StartLimitBurst= to the service units created; it would palliate the network requiring snaps a bit
[13:32] <mvo> kyrofa: actually I think we need to do something about this because webdm is something we want to preinstall
[13:33] <kyrofa> mvo, we could always add it to our gadgets if we don't want to support --install
[13:33] <sergiusens> mvo, right, the correct path for preinstalling is to define it in the model
[13:33] <sergiusens> mvo, but it is in a limbo state right now
[13:33] <mvo> sergiusens: no disagreement
[13:33] <mvo> sergiusens: I just don't like the limbo state, would be nice to be able to build images
[13:33] <mvo> sergiusens: so that people can use/test them
[13:33] <kyrofa> mvo, yeah, agreed
[13:34]  * mvo scratches head
[13:34] <sergiusens> mvo, of course; so many things have changed lately though that it is hard to unbreak everything :-)
[13:35] <mvo> sergiusens: yeah
[13:35] <mvo> sergiusens: I think we are very much in agreement :)
[13:35] <sergiusens> kyrofa, so the os.snap holds the generic initrd.img that ogra_ built; the intermediate plan is to compose a full initrd.img until snappy learns about N initrd's that can be chainloaded
[13:35] <noizer> jdstrand: kyrofa I got the following path
[13:35] <noizer> export SNAP_USER_DATA="$HOME/snaps/ad.sideload/LTKWTFRHRRWC"
[13:35] <jdstrand> kyrofa: did I hear correctly, model assertions are required for service start?
[13:35] <kyrofa> jdstrand, oh no, just pre-installing snaps in a generated image
[13:35] <sergiusens> mvo, I wish agreeing would magically fix things :-D
[13:36]  * sergiusens is in a very Friday mood
[13:36] <jdstrand> kyrofa: ok, I was going to say :)
[13:36] <kyrofa> jdstrand, starting to sweat?
[13:37] <jdstrand> noizer: I think what might be happening is when you call the scripts in /snaps/bin, your HOME is not /home/ubuntu, it is /home/ubuntu//snaps/ad.sideload/LTKWTFRHRRWC, so then the launcher looks at $HOME, tacks on /snaps and messes up
[13:38] <jdstrand> noizer: the fix is doing HOME=/home/`id -u` /snaps/bin/...
[13:38] <jdstrand> noizer: or similar (that won't work for root of course, but you get the idea)
[13:38] <kyrofa> sergiusens, ahh, okay I see now. So this is (hopefully) temporary, then?
[13:38] <jdstrand> err, id -un
[13:38] <kyrofa> sergiusens, the downloading, I mean
[13:39] <kyrofa> sergiusens, until we get them chained
[13:39] <sergiusens> kyrofa, yeah; but if we lived in a beatiful world this storeapi thing would be its separate project and we'd use it for ubuntu-image as well (to download snaps)
[13:39] <sergiusens> kyrofa, yes, until then
[13:39] <noizer> jdstrand: But I can't fix it right now?
[13:40] <kyrofa> sergiusens, that's not a bad idea. It might save us some work later, but it means facing the NEW queue
[13:40] <sergiusens> kyrofa, new queue is easy once you know the right people ;-)
[13:40] <kyrofa> sergiusens, ha!
[13:40] <kyrofa> sergiusens, what do you think then? Shall we extract it?
[13:41] <sergiusens> kyrofa, well now is not the time
[13:41] <kyrofa> Or even implement the API in ubuntu-image?
[13:41] <kyrofa> Okay
[13:41] <sergiusens> kyrofa, it's in snapcraft since you know what
[13:42] <kyrofa> Gotcha :)
[13:54] <jdstrand> noizer: this is in your code
[13:54] <jdstrand> noizer: you are calling /snaps/bin/... iirc
[14:00] <noizer> jdstrand: yes thats my code how can i fix it then?
[14:02] <roadmr> heya folks! I installed ubuntu-snappy-cli on a xenial system and there's no "snappy try". How can I try a locally built snap? I do have the snappy-dev ppa enabled
[14:02] <qengho> Is there any preferred idiom for restarting one's self after a config change? Just use local config program to kill or something? No systemd poking or anything?
[14:05] <jdstrand> noizer: I told you: you need to reset HOME to /home/ubuntu (or /home/`id -un` or something else smarter) before you call /snaps/bin/...
[14:05] <jdstrand> HOME=/home/`id -un` /snaps/bin/...
[14:06] <noizer> jdstrand: sorry i was a little confused :s
[14:07] <jdstrand> np
[14:19] <noizer> jdstrand: I set my HOME to /home/ubuntu and it won't help
[14:20] <jdstrand> noizer: otoh not sure. look at the env vars being set in /snaps/bin/... (they are just shell scripts) and try to figure out what you need to do
[14:22] <sergiusens> kyrofa, elopio I'm at a coffee shop that just got loud, mind if we start 10' late so I run home?
[14:22] <kyrofa> sergiusens, sure thing
[14:23] <kyrofa> sergiusens, no rush
[14:33] <ogra_> mvo, yeah, it was the same issue (webdm got unpacked in /snaps but no "current" link and no systemd services were created)
[14:36] <ogra_> mvo, we also used to be able to just build images without defining kernel and os (the oem snap used to define which ones it needs) ... that was very convenient, could we have that back ?
[14:38] <mvo> ogra_: I pushed a branch that activates the installed snaps now, the other one is probably simple too, I need to look at an example, can't remeber the syntax that the gadget defines kernel/os
[14:39] <ogra_> yeah, me neither, ricmm just pointed me to that yesterday, i'm alsready so used to define --os and --kernel :)
[14:39] <ogra_> mvo, also, when do you plan to land the udf changes so people dont need to pull your binary ?
[14:40] <ogra_> is there anything blocking ?
[14:40] <mvo> ogra_: well, ubuntu-image, but I suspect more and more that this is not going to happen before 16.04 so maybe we should go ahead. my branch was proposed ages ago
[14:40] <ogra_> (looks stable to me after using it for more than a month)
[14:40] <mvo> ogra_: my branch for u-d-f
[14:41] <ogra_> yeah, even if ubuntu-image happens we should have something that matches the current setup in the archive
[14:41] <kyrofa> mvo, +1 on landing
[14:41] <ogra_> until u-image is done
[14:42] <kyrofa> mvo, we're still waiting on a number of things to happen before ubuntu-image anyway
[14:42]  * ogra_ would like to disable tarballs on cdimage ... which will break the system-image setup, so u-d-f shouldnt use it for 16.04 anymore
[14:42] <mvo> ogra_: hm, did ricmm point to the agreed syntax for kernel/os snap in gadget.yaml :) ? I can't find that right now
[14:42] <ogra_> mvo, no, he just pointed out that it was possible with the old oem snaps ...
[14:42] <mvo> kyrofa: yeah, I think that makes sense
[14:42] <mvo> ogra_: right, well, hmmm
[14:43] <mvo> ogra_: we may need to wait until there is agreement on the syntax but in principle its a simple change I think
[14:43] <ogra_> probably nobody thought about that and it isnt in the spec
[14:43] <ogra_> (i personally hd completely forgotten about it :) )
[14:54] <morphis> mvo: nevermind, solved the problem already
[14:55] <ogra_> sergiusens, thanks for the cliffhanger btw ... looks like we might re-discuss merged initrds vs loop mounted modules :)
[14:56] <ogra_> (which in case we decide for the latter means changing the partitioning scheme )
[14:57]  * ogra_ will try to preapre a prototype
[15:07] <ogra_> sergiusens, so looking at https://github.com/ubuntu-core/snapcraft/pull/379 ... why not just pull the deb from the archive ... seems like overkill to use the whole os snap just to extract the img file
[15:12] <sergiusens> ogra_, we can't know which OS and deb relate
[15:12] <sergiusens> as in no traceability
[15:12] <sergiusens> ogra_, this is jus temporary though as you now know ;-)
[15:12] <ogra_> well, the generic initrd will have to come from somewhere
[15:12] <ogra_> even in the future
[15:13] <sergiusens> ogra_, yeah, but the kernel plugin won't need to pull it down
[15:13] <ogra_> how else would you get it then ?
[15:13] <kyrofa> ogra_, won't it be in the image?
[15:14] <ogra_> kyrofa, it currently is ... but that wont help you if you build your arm kernel via snapcraft on your PC
[15:15] <ogra_> then it would again need to pull the file from somewhere
[15:16] <ogra_> (unless you limit it to only building in the classic dimension)
[15:32] <roadmr> heya folks! I installed ubuntu-snappy-cli on a xenial system and there's no "snappy try". How can I try a locally built snap? I do have the snappy-dev ppa enabled
[15:33] <kyrofa> ogra_, I guess I'm not super clear on what the end goal is. I imagined the kernel snap having its own initrd and the OS having another one, and at boot they get chained together. Perhaps I've misunderstood?
[15:33] <elopio> mvo: ping. So, what should we use as the version of this deb we dput on changes to master?
[15:33] <elopio> I was thinking that the sha1 doesn't work because it's not increasing.
[15:34] <kyrofa> ogra_, i.e. they're independent
[15:35] <ogra_> kyrofa, well, the discussion about the implementation is still ongoing (or ongoing again since yesterday), but yes, the generic part in either scenarion can then come from the os on boot
[15:35] <ogra_> *scenario
[15:36] <ogra_> sorry, i'm judging by waht we currently have :)
[15:36] <ogra_> (which is "merge at build time")
[15:38] <dholbach> davidcalle, you can set SNAPCRAFT_LOCAL_SOURCES as an environment variable and use what's in your /etc/apt/sources.list*
[15:39] <kyrofa> ogra_, right, same page. I guess we're just assuming that the end goal will be to have them completely independent at build time, so we just have this temporary workaround for now
[15:39] <dholbach> davidcalle, that'd trump whatever snapcraft's using by default and you could work around the mirror which has a broken hashsum (or is in the middle of mirroring)
[15:40] <dholbach> at some stage, sergiusens will make me pay for every time I mention the local sources trick
[15:40] <ogra_> kyrofa, i learned to only trust end golas if the code exists ... i guess thats my prob :)
[15:40] <dholbach> it looks like a few people need this after all
[15:40] <ogra_> *goals
[15:40] <kyrofa> ogra_, heh
[15:41] <davidcalle> dholbach: perfect, thanks :)
[15:45] <mvo> elopio: ideally just whatever version we already have and we append ~ppaN (~ppa1, ~ppa2 etc)
[15:45] <mvo> elopio: the "~" is important to ensure the version is smaller
[15:57] <sergiusens> dholbach, I will make it default after I am done with this <josepht> jdstrand: I uploaded another revision
[15:57] <sergiusens> dholbach, err https://github.com/ubuntu-core/snapcraft/pull/335
[15:57] <sergiusens> not sure how that got copy/pasted ???
[15:57] <sergiusens> darn xchat
[15:57] <jdstrand> heh
[15:57] <dholbach> oooh, nice
[15:58] <dholbach> thanks sergiusens!
[15:58] <sergiusens> dholbach, which will allow you to also mostly use build packages instead of stage packages for most things again
[15:58] <dholbach> excellent
[16:00] <dholbach> all rightie... I call it a day - have a good one everyone!
[16:00]  * mvo hugs dholbach
[16:00] <kyrofa> Bye dholbach!
[16:00]  * dholbach hugs mvo and kyrofa 
[16:00] <dholbach> mvo, email! :-)
[16:01] <dholbach> see you!
[16:12] <ogra_> mvo, how about we target next week to do an all-snaps 16.04 alpha release on cdimiage.u.c/ubuntu-snappy (independent of u-d-f being merged or my autosubmit of snaps from cdimage to the store i think we should have some recent image we can point people at in an official space)?
[16:12] <mvo> ogra_: absolutely, this is why dholbach was bugging me about "send this mail"
[16:12] <ogra_> ah
[16:13] <roadmr> how can I try a locally-built snap?
[16:14]  * ogra_ always uses a kvm image or if i build for arm i actually use the target device to try it 
[16:14] <kyrofa> ogra_, yay for cdimage!
[16:15] <ogra_> roadmr, i'm not sure that "snappy try" is working yet
[16:15] <ogra_> s/that/if/
[16:15] <roadmr> ogra_: thanks! this is amd64 so a kvm image would work. I'm happy to be pointed to docs if there are any :)
[16:16] <ogra_> roadmr, http://people.canonical.com/~mvo/all-snaps/amd64-all-snap.img.xz ... unxz that ... then: kvm -m 512 -redir :8022::22 amd64-all-snap.img.
[16:17] <ogra_> (and you can ssh/scp to localhost at port 8022)
[16:17] <roadmr> ogra_: yay, thanks!
[16:25] <ogra_> kyrofa, did you consider giving your "split /writable to separate img" script snippets to zyga so he can include it in his ubuntu-image script ?
[16:26] <kyrofa> ogra_, no, but if you imagine it being more generally useful I totally can
[16:26] <ogra_> i think it is, yeah
[16:26] <ogra_> (for everyone wanting to have the payload on USB and boot on SD)
[16:27] <kyrofa> ogra_, yeah I have a custom version of his ubuntu-image as well, so I should upstream the whole thing
[16:27] <ogra_> yeah
[16:27] <kyrofa> ogra_, I'll make a few PRs, thanks for the poke :)
[16:27] <ogra_> thanks for the code :)
[16:29] <sergiusens> dpm, `snappy build` is going bye bye, might be better to say `snapcraft snap [DIR]`
[16:29] <kyrofa> sergiusens, https://github.com/ubuntu-core/snapcraft/pull/381
[16:30] <kyrofa> elopio, ^^
[16:30] <dpm> sergiusens, ah I've actually never used it, I've always used snapcraft so far. Any particular docs you've seen it mentioned?
[16:30] <sergiusens> dpm, the one you just shared in the call
[16:30] <dpm> sergiusens, ah, I see
[16:30] <dpm> updating it
[16:30] <sergiusens> dpm, you also mention 'clock' in there  ;-)
[16:30] <sergiusens> dpm, I only have View; else I would of commented/suggested inside the doc :-)
[16:31] <dpm> sergiusens, updated permissions, you should be able to edit/comment now :)
[16:31] <dpm> thanks!
[16:32] <ogra_> sergiusens, and now you own it !
[16:32] <sergiusens> thanks
[16:32] <sergiusens> ogra_, nah
[16:32] <ogra_> :)
[16:32] <dpm> dammit, it was worth a try :)
[16:38] <kyrofa> sergiusens, have any atom plugins to recommend?
[16:39] <sergiusens> kyrofa, you transitioned :-)
[16:40] <kyrofa> sergiusens, I'm taking it for a spin anyway
[16:40] <kyrofa> sergiusens, perhaps my combination of gedit vi and grep could be improved upon. Perhaps
[16:40] <ogra_> gedit and vi ?
[16:40] <ogra_> heh
[16:41] <sergiusens> kyrofa, atom-python-debugger, git-plus, linter (A Base Linter with Cow Powers), linter-flake8, linter-golinter, linter-gotype, linter-govet, linter-pep8 (although flake8 takes care of the same) and the best of all vim-mode
[16:41] <kyrofa> sergiusens, ah, it was watching your vim-mode that convinced me to try it out
[16:41] <sergiusens> kyrofa, I like "linter" most of all for the description
[16:42] <kyrofa> Hahaha
[16:42] <sergiusens> kyrofa, the reason I stopped using vscode was that its vim-mode wasn't that good
[16:43]  * kyrofa wonders how atom's ruby support is
[16:44] <kyrofa> sergiusens, what about python-tools?
[16:54] <dpm> davidcalle, I think the getting started doc is ready - if you want to have a quick review whenever you've got time, that'd be awesome
[16:56] <davidcalle> dpm, alright, on my end, I'm still trying to figure how to handle runtime deps
[16:57] <dpm> davidcalle, just put them all in :)
[16:57] <dpm> have you tried with "stage-packages"?
[16:57] <sergiusens> kyrofa, I just use the linter tools
[16:58] <sergiusens> kyrofa, btw https://owncloud.org/blog/wd-labs-raspberry-pi-owncloud-and-ubuntu/
[16:58] <davidcalle> dpm: that's the "all in" part I'm running after. Things build, but always choke on some missing lib when I try to run them. I'm tempted to add ubuntu-desktop ;)
[16:58] <dpm> davidcalle, ah, I had that issue too, it's a bit of trial and error :)
[16:59] <davidcalle> dpm: any way to not have to redownload anything when you change stage-packages?
[16:59] <kyrofa> sergiusens, hey thanks!
[17:00] <dpm> davidcalle, I haven't tried that yet, but the last comment on bug 1550679 might work
[17:04] <davidcalle> dpm: thanks, doesn't work (yet?), but nice to see it's planned
[17:06] <sergiusens> kyrofa, very nice
[17:06] <sergiusens> kyrofa, I'll start looking at your PR in a bit btw
[17:40] <joc_> sergiusens: hi, i've been trying to push this snapcraft PR along but keep hitting issues with the automated checks:
[17:40] <joc_> https://github.com/ubuntu-core/snapcraft/pull/364
[17:41] <kyrofa> Hey mvo do we have a bug for the unversioned data directory?
[17:42] <joc_> sergiusens: do you know if that is a problem with the tools or my PR?
[17:48] <sergiusens> joc_, given that other PRs are testing fine I'd guess with your PR; elopio mind checking?
[17:49] <sergiusens> joc_, if you have vpn access just click on details to see
[17:51] <joc_> sergiusens: ah thanks, didnt have vpn enabled
[17:55] <kyrofa> sergiusens, okay I admit. Atom is an improvement
[17:56] <sergiusens> kyrofa, it is nice; I downloaded it for a test run and here I am still 8 months in
[17:57] <kyrofa> sergiusens, and it's light and fast. That's why I was using my previous solution-- everything was so slow
[17:57] <kyrofa> everything else, rather
[17:58] <sergiusens> kyrofa, what other things were you using?
[17:59] <sergiusens> vim wouldn't be slow, but package management and the packages can get slow/flaky
[17:59] <kyrofa> sergiusens, no that's what I mean-- vi and gedit are both super light. But like, eclipse for instance
[18:08] <elopio> joc_: http://paste.ubuntu.com/15416550/
[18:17] <joc_> elopio: thanks, where did you get that output from?
[18:18] <joc_> elopio: i.e. can i get to it myself from the PR?
[18:20] <elopio> joc_: yes, just enable the vpn and go to the details link
[18:20] <elopio> http://162.213.35.179:8080/job/github-snapcraft-autopkgtest-cloud/176/console
[18:25] <ogra_> kyrofa, hahahaha (reading the blog article you linked)
[18:25] <ogra_> "This brings a very familiar operating system to the device"
[18:25] <ogra_> :D
[18:25] <kyrofa> ogra_, yeah I noticed that myself
[18:26] <kyrofa> Some people might be surprised
[18:26] <ogra_> yeah
[18:26] <ogra_> well, we need to promote the classic dimension more ... there we are actually a familiar choice ;)
[18:26]  * ogra_ wishes we had a "snappy enable-classic-with-snapcraft" 
[18:27] <ogra_> kyrofa, nontheless, awesome !!!!
[18:28] <kyrofa> ogra_, thanks! :)
[18:30] <wililupy> Question: In Xenial, how do we run snappy-remote?
[18:31] <ogra_> is it broken ?
[18:31]  * ogra_ never uses it 
[18:32] <ogra_> (being just a wrapper around two scp and ssh commands)
[18:32] <wililupy> I try to install snappy-tools from the ppa, but it says unable to locate package.
[18:32] <wililupy> This is on a xenial workstation.
[18:33] <ogra_> there might not be a xenial build for it indeed ... since "snappy try" is actually supposed to replace it (but i think thats not complete yet)
[18:33] <wililupy> I guess I could always just scp the .snap to the device and locally run snappy install, but I was hoping to do everything remote.
[18:34] <wililupy> Heh, I tried snappy try on xenail and it said, "Unknown command `try', did you mean `activate'?"
[18:34] <ogra_> sergiusens, ^^ any chance we could have a xenial build of snappy-tools (at least til snapcraft try works)
[18:35] <wililupy> There's room for a Star Wars Easter egg there ;)
[18:35] <sergiusens> ogra_, just copy_package it into xenial if you want
[20:00] <verterok> Hi, used snapcraft to build a snap of a python CLI app, but when I try to install it (kvm) but fails with: "failed to install: Signature verification failed with exit status 14"
[20:01] <verterok> couldn't find anything regariding the exit status 14, any ideas what might be going on?
[20:02] <kyrofa> verterok, you need --allow-unauthenticated when installing
[20:02] <kyrofa> snappy install <snap> --allow-unauthenticated
[20:03] <kyrofa> verterok, only snaps in the store are signed
[20:03] <verterok> kyrofa: I'm using --allow-unauthenticated
[20:03] <kyrofa> verterok, oh
[20:03] <kyrofa> verterok, 15.04 or 16.04?
[20:03] <verterok> kyrofa: ubuntu-core/15.04/stable
[20:04] <verterok> kyrofa: following the docs on both: 1) how to build a snap and 2) get snappy running on kvm
[20:04] <kyrofa> verterok, is it a large snap?
[20:04] <verterok> kyrofa: 48M
[20:05] <verterok> I can upload it somewhere if it helps, but will take a bit with my current connection
[20:05] <kyrofa> verterok, how much RAM do you have in the VM?
[20:06] <verterok> kyrofa: 512
[20:06] <verterok> should I bump it?
[20:08] <kyrofa> verterok, can you run  debsig-verify -d on the snap manually?
[20:09] <kyrofa> It sounds like the code checks for a signature and then decides whether or not to ignore it
[20:09] <verterok> kyrofa: http://paste.ubuntu.com/15417537/
[20:09] <kyrofa> verterok, how did you create the snap?
[20:09] <verterok> kyrofa: snapcraft
[20:09] <kyrofa> verterok, which version?
[20:10] <verterok> kyrofa: 2.4
[20:10] <verterok> I'm in xenial
[20:10] <kyrofa> verterok, ah, you are a victim of the currently terrible documentation situation
[20:10] <verterok> kyrofa: :)
[20:10] <kyrofa> verterok, if you're targeting pre-16.04, you must use Snapcraft 1.x (available pre-xenial back to trusty)
[20:11] <kyrofa> Snapcraft 2.x packages totally differently
[20:11] <verterok> kyrofa: oh, ok.
[20:11] <verterok> kyrofa: will add the ppa and install 1.0
[20:11] <verterok> kyrofa: thanks for the help
[20:12] <kyrofa> verterok, no problem! Note that you still may run into issues running Snapcraft 1.x on xenial, as the generated snap may end up wanting a newer libc than snappy 15.04 offers
[20:12] <kyrofa> verterok, we recommend running snapcraft on the same version of ubuntu you're targeting
[20:12] <verterok> kyrofa: got it, will create a trusty lxd ;-)
[20:12] <kyrofa> verterok, that's what I do as well :)
[20:13] <verterok> or just create a 16.04 snap vm
[20:13] <kyrofa> verterok, good luck, and I'm sorry about that! We're trying to clean up the docs now
[20:13] <verterok> np, just trying to get my first snap working
[20:13] <kyrofa> verterok, that works too, images here: http://people.canonical.com/~mvo/all-snaps/
[20:14] <verterok> thanks
[21:30] <sergiusens> ogra_, is this a correct path /usr/aarch64-linux-gnu/lib/ld-linux-aarch64.so.1 ? fwiw I can't x-compile upstream busybox :-)
[21:30] <sergiusens> or asked differently, is this sort of the same issue you saw when doing the generic initrd work?
[22:37] <kyrofa> sergiusens, strip cleaning: https://github.com/ubuntu-core/snapcraft/pull/382
[23:07] <leftyfb> will snappy run on the rpi3?
[23:18] <sergiusens> kyrofa, looking
[23:20] <sergiusens> leftyfb, not yet
[23:20] <leftyfb> sergiusens: will it run on it or is it just "unsupported"? Is it the kernel that lacks something for the new arm8?
[23:21] <sergiusens> leftyfb, it will not run yet; afaik we are waiting on broadcom to release their bootloader bits
[23:21] <sergiusens> but I haven't been paying attention
[23:21] <sergiusens> it's all about the dragonboard for me now :-)
[23:23] <sergiusens> kyrofa, do you know how to regenerate the PR view? I don't want to see code I already saw :-)
[23:24] <leftyfb> sergiusens: https://mailman.owncloud.org/pipermail/devel/2016-March/002273.html ?
[23:25] <leftyfb> https://mailman.owncloud.org/pipermail/devel/2016-March/002273.html
[23:25] <leftyfb> oh, pi2
[23:25] <leftyfb> nevermind :)
[23:26] <leftyfb> though according to this https://owncloud.org/blog/wd-labs-raspberry-pi-owncloud-and-ubuntu/ it looks like you can build your own 16.04 snap
[23:26] <sergiusens> leftyfb, still pi2