[00:53] <Swami_> sure thanks kyrofa. if you are around
[00:53] <Swami_> will get back and look through it
[03:53] <stgraber> beuno, jdstrand: Just uploaded a tiny fix for LXD 2.0.0 to the store (use the old lxcbr0 bridge as we don't have lxdbr0 on snappy yet)
[03:53] <stgraber> folks upgrading didn't have any issue with rc9 or 2.0 final, but folks doing a clean install would have got broken networking, this will fix new installs
[03:53] <stgraber> cyphermox: ^
[05:09] <cyphermox> stgraber: thanks
[09:31] <davidcalle> Hi snappers, when using the snap find command, I don't see the fully qualified app name, how can I install apps without it?
[09:59] <davidcalle> Anyone, zyga maybe? ^
[09:59] <davidcalle> "when using the snap find command, I don't see the fully qualified app name, how can I install apps without it?"
[10:00] <zyga> davidcalle: store bug
[10:00] <zyga> davidcalle: and it's snaps, not apps
[10:04] <davidcalle> zyga =) ty
[10:13] <mvo> davidcalle: beuno mentioned the other day they are working on automating this, for now we may need to set aliases for the store apps (worst case manually until this is automated). but I'm not sure what the status is, maybe its fixed already, beuno will know
[10:16] <ogra_> ubuntu@localhost:~$ snap install webdm
[10:16] <ogra_> error: access denied
[10:16] <ogra_> mvo, can we make that message a bit more user friendly ?
[10:17] <ogra_> (it used to tell me i should use sudo etc)
[10:17] <oparoz> Any idea why this doesn't compile on arm? https://github.com/kyrofa/mdns-publisher/blob/master/main.go
[10:18] <davidcalle> mvo: thanks
[10:18] <oparoz> Actually, that's wrong, it compiles, but fails in the stripping phase
[10:27] <mvo> ogra_: yes, I think we should
[10:29] <ogra_> Building dependency tree...
[10:29] <ogra_> E: Unable to locate package ubuntu-core-libs
[10:29] <ogra_> P: Begin unmounting filesystems...
[10:30] <ogra_> mvo, s390x and ppc64el fail with that ^^^
[10:30] <ogra_> do we not build that package there ?
[10:35] <oparoz> https://bugs.launchpad.net/snappy/+bug/1569280
[10:36] <mvo> ogra_: I'm surprised by that, I think that worked before :/
[10:36] <ogra_> mvo, did we ever buikld images for them ?
[10:36] <ogra_> (i just added both arches and started a testbuild)
[10:38] <ogra_> OH !
[10:38]  * ogra_ wasnt aware it is a meta package :P
[10:40] <mvo> ogra_: I don't think we did images for them
[10:40] <ogra_> right
[10:44] <ogra_> where the heck do the seeds live for that package ?
[10:46] <ogra_> ah, found them
[10:51] <daker> kyrofa: hi sorry for the noise, store question : if i have rev1 of v1.0 of my snap that's have been automatically rejected, i need to upload v1.0.1(for ex) ?
[11:25] <attente> is there a reason the names of the binaries in /snaps/bin don't match the ones in the snaps themselves?
[11:27] <ogra_> attente, got an example ?
[11:27] <attente> ogra_: ubuntu-calculator-app for example
[11:27]  * ogra_ never used that 
[11:28] <ogra_> i meant an example of the binary names :)
[11:28] <ogra_> vs what you expect
[11:28] <attente> ogra_: maybe a better question is what is the canonical way of launching a snap
[11:28] <ogra_> packagename.binary-name
[11:28] <ogra_> i.e. in my nethack snap i defined "run" ... to start my game i now need to exec nethack.run
[11:29] <attente> ogra_: so in ubuntu-calculator-app, i think the Exec line of the desktop file is incorrect possibly
[11:29] <ogra_> well, i thought dpm has tested that
[11:30] <attente> ogra_: it just has the line 'Exec=ubuntu-calculator-app
[11:31] <ogra_> and there is no binary of that name in the snap ?
[11:31] <ogra_> (not sure if .desktop files are simply handled differently)
[11:31] <ogra_> i never used them :)
[11:32] <attente> ogra_: no, there's only /snaps/ubuntu-calculator-app.ubuntucoredev/current/usr/bin/ubuntu-calculator-app
[11:32] <ogra_> then thats fine i guess
[11:32] <attente> ogra_: but /snaps/*/current/usr/bin isn't in the user's path
[11:32] <attente> only /snaps/bin is
[11:33] <attente> so it finds /snaps/bin/ubuntu-calculator-app.calculator instead
[11:33] <ogra_> well, i dont exactly know how ,.desktop files are operated in snappy ... but i guess it is only run inside the confined env ... where that path will be exported by the launcher
[11:34]  * ogra_ assumes /snaps/bin/ubuntu-calculator-app.calculator is a script
[11:34] <attente> yes
[11:35] <ogra_> then it will likely set the path correctly
[11:37] <attente> ogra_: so i should probably not be using the desktop file at all and just using the script in /snaps/bin directly?
[11:37] <attente> since it seems like the desktop file refers to the binary in the snap itself and not /snaps/bin
[11:38] <ogra_> you should use the ,.desktop files from GUIs obviously ... :)
[11:39] <ogra_> no idea how the integration works with that though
[11:39] <ogra_> from commandline you shoudl always just run ubuntu-calculator-app.calculator
[11:58] <tsimonq2> ogra_: can you make metapackages with Snappy or does it have to all be in the package?
[11:59] <tsimonq2> whoops, snap, not package :)
[11:59] <ogra_> tsimonq2, whats the difference ?
[11:59] <ogra_> :)
[11:59] <tsimonq2> heheheh
[11:59] <ogra_> a snap *is* essentially a metapackage :)
[11:59] <tsimonq2> well
[11:59] <tsimonq2> oh I see
[11:59] <ogra_> containing all the bits and pieces
[12:00] <tsimonq2> so let's say I want to make the bob metapackage, and include like 20 deb dependencies, would that work smoothly?
[12:00] <tsimonq2> ooh, could I get it from upstream instead if I wanted to?
[12:01] <ogra_> sure, you would just define all the debs in your snapcraft.yaml and snapcraft would include them
[12:01] <ogra_> and yes, you could as well use the upstream source
[12:01] <tsimonq2> are the debs only from Ubuntu or can they be from Debian as well?
[12:01] <ogra_> for one or even for all your deps
[12:01] <ogra_> only from ubuntu
[12:01] <tsimonq2> oic
[12:01] <tsimonq2> is there a tutorial I could follow to do this?
[12:02] <tsimonq2> or is it really simple?
[12:02] <ogra_> there are examples in the snapcraft-examples package
[12:02] <tsimonq2> is that a deb package that I could install now, or a snappy package? :D
[12:02] <ogra_> snapcraft is a deb package ... note though that you need xenial if you build for xenial snappy
[12:03] <tsimonq2> I'm on Xenial :)
[12:03] <ogra_> good
[12:03] <ogra_> well, "sudo apt install snapcraft"
[12:03] <ogra_> ;)
[12:03]  * tsimonq2 does sudo apt update && sudo apt -y install snapcraft snapcraft-examples
[12:04] <tsimonq2> :)
[12:04] <ogra_> create a workdir ... create a snapcraft.yaml file ... run "snapcraft" in the workdir and if your yasml file is correct you get a working snap ;)
[12:04] <ogra_> *yaml
[12:04] <tsimonq2> where are the examples then? :)
[12:04] <ogra_> i guess in /usr/share7doc
[12:05] <tsimonq2> also, can I upload snaps to PPAs?
[12:05] <ogra_> dpkg -L snapcraft-examples will tell you as usual ;)
[12:05] <ogra_> no
[12:05] <tsimonq2> that would be an awesome feature
[12:05] <ogra_> you can use launchpad to build snaps from a snapcraft.aml in a bzr branch
[12:05] <ogra_> and you can upload them to the store
[12:06] <ogra_> snaps *are* PPAs ... like they are metapackages ;)
[12:06] <tsimonq2> oh okay :)
[12:06] <tsimonq2> so let's say I have my snap built and all ready to go, how do I test it?
[12:07] <ogra_> in xenial you shoudl actually be able to install it directly on your system ...
[12:07] <ogra_> at least after release, not sure what bugs are still there
[12:07] <tsimonq2> it would replace packages and cause a big huge mess, I would prefer a VM :)
[12:07] <ogra_> alternatively you can run a complete snappy in kvm or on i.e. a raspberry pi
[12:07] <ogra_> no, it wouldnt cause any mess
[12:08] <tsimonq2> KVM? I thought there was a guide somewhere for that...
[12:08] <ogra_> snappy on classic installs is a feature of xenial :)
[12:08] <ogra_> installing a snap will "just work" ... snaps live in their own filesystem space, they wont mess up anything
[12:09] <ogra_> (it shoudl already work if your xenial system is up to date, ubuntu-snappy-cli should be installed)
[12:10] <oparoz> ogra_: What's the strategy when we need to ship a firewall, log rotater, etc. It's not really efficient to add it to every single snap part of a solution
[12:11] <ogra_> you would creater a library snap that all your other snaps (only yours though) can consume
[12:11] <oparoz> ogra_: Ah, good. Is there doc on that already?
[12:11] <ogra_> not sure
[12:13] <tsimonq2> ogra_: if I create a snappy package from upstream, will it automatically pull in updates from there?
[12:13] <tsimonq2> for example GitHub
[12:13] <ogra_> if you re-build it
[12:15] <tsimonq2> that seems a bit tedious :|
[12:15] <tsimonq2> is it easy to rebuild and reupload?
[12:16] <ogra_> if your snapcraft.yaml is correct it should be one click in launchpad
[12:16] <ogra_> (modulo build failures that the upstream changes introduce indeed ...)
[12:16] <tsimonq2> can you set up daily builds?
[12:17] <ogra_> i think launchpad receipes are supported ... not sure though
[12:18] <tsimonq2> I'll try later today :)
[12:18] <tsimonq2> then to update everything is sudo snappy update?
[12:19] <ogra_> sudo snap update
[12:19] <ogra_> the "snappy" command is dead
[12:19] <tsimonq2> why?
[12:19] <tsimonq2> 2 extra letters? :P
[12:19] <ogra_> dunno
[12:20]  * ogra_ wasnt involved in that discussion :)
[12:21] <tsimonq2> alright, thank you ogra_, I'm off for a few hours, have a nice day. :)
[12:21] <ogra_> you too
[12:36] <dholbach> kyrofa, sergiusens: can you maybe advise on https://bugs.launchpad.net/click-reviewers-tools/+bug/1569226?
[12:36] <dholbach> I don't know what the right fields and stuff are
[12:36] <kyrofa> Hey dholbach!
[12:36] <dholbach> hey hey - how are things?
[12:37] <sergiusens> morning
[12:53] <ogra_> eeek !
[12:53] <ogra_> sergiusens, !
[12:54] <ogra_> sergiusens, all our initrds use lzma now ... seems the kernel plugin has no check about the compression method and just assumes gzip
[12:58] <sergiusens> ogra_, well, not really; it said we only supported that for now
[12:58] <sergiusens> lzma or lzma2 or xz?
[12:58] <ogra_> bug 1569337
[12:59] <sergiusens> ogra_, thanks
[12:59] <sergiusens> ogra_, probably an EOW thing
[13:00] <ogra_> yeah
[13:07] <kyrofa> dholbach, things are frantic, haha
[13:07] <kyrofa> dholbach, any chance that bug relates to the removal of old-security from snappy?
[13:07] <dholbach> kyrofa, I don't know which fields are current and which old fiels should still be allowed
[13:07] <dholbach> but this breaks store reviews right now
[13:08] <kyrofa> dholbach, join the club, things are changing fast :(
[13:08] <kyrofa> dholbach, I believe old-security is gone and one needs to use the actual interface names now. But then I heard maybe that would come back
[13:08] <kyrofa> dholbach, zyga would know more on that one
[13:09] <zyga> old-security is gone now
[13:09] <zyga> but we'll probably bring it back later, for now use real interfaces
[13:09] <zyga> they are listed in docs/interfaces.md
[13:09] <zyga> note that only auto-connecting interfaces really work as connection/disconnection commands are not wired to the backend yet
[13:09] <zyga> that will land today though so all the interfaces will be fully functional
[13:09] <dholbach> ok... I guess I need to talk to jdstrand to find out what policy should be in this case... reject snaps which don't have proper interface names?
[13:10] <kyrofa> dholbach, I guess so. I thought we had old-security as a migration plan, but I guess not?
[13:11] <zyga> dholbach: snappy validates that internally
[13:11] <zyga> kyrofa: it's all crazy :)
[13:12] <kyrofa> zyga, I've noticed :)
[13:12] <zyga> kyrofa: I want to add old-security back but that's not top-priority
[13:12] <zyga> top priority is fully functional REST api for managing interfaces
[13:12] <kyrofa> zyga, I'm not sure it's necessary since everyone is broken now-- everyone will have to move to interfaces if they want stuff to work
[13:12] <zyga> kyrofa: true
[13:13] <zyga> kyrofa: but some edge cases need old security
[13:13] <dholbach> zyga, right... but the store needs to check it too
[13:13] <zyga> sergiusens: can you release snapcraft that allows something other than old security today?
[13:13] <zyga> dholbach: no
[13:13] <zyga> dholbach: the store doesn't have to check it in any way
[13:13] <oparoz> zyga there is no docs/interfaces.md in snapcraft
[13:13] <zyga> dholbach: we'll add some checks via assertions but that's not today
[13:13] <kyrofa> oparoz, that's snappy
[13:13] <sergiusens> ppisati, fwiw ogra_ logged a bug about the gzip issue
[13:13] <zyga> oparoz: sorry, look at snappy
[13:13] <zyga> oparoz: github.com/ubuntu-core/snappy/ docs/interfaces.md
[13:13] <dholbach> zyga, what if somebody uploads an old style app to the store
[13:14] <sergiusens> zyga, today? wow
[13:14] <oparoz> Thanks guys
[13:14] <dholbach> zyga, with no plugs defined
[13:14] <zyga> dholbach: nothing
[13:14] <zyga> dholbach: it will just run without any extra permissions, fully confined
[13:14] <zyga> dholbach: snappy ignores unknown or invalid interfaces
[13:14] <sergiusens> zyga, we can, but we need old-security replacements for our examples
[13:15] <zyga> sergiusens: I'd be fine with a half-broken release that lets people snapcraft non-broken snaps without old-security
[13:15] <zyga> sergiusens: I suspect that most of those can just use normal interfaces but I didn't check
[13:15] <sergiusens> zyga, right, but we won't be able to know if snapcraft itself is working
[13:15] <sergiusens> or doing the right thing
[13:16] <zyga> sergiusens: ideas welcome, right now you cannot build a snap that uses unity7 + x11 plugs
[13:16] <zyga> sergiusens: I don't know snapcraft as well as you do, what would be the best way forward?
[13:16] <sergiusens> zyga, 1st; is there an os image in edge that works already?
[13:17] <zyga> sergiusens: mvo built a package, the image is soon after that I bet
[13:17] <sergiusens> zyga, 2nd; do we have replacements for everything in `examples` wrt interfaces?
[13:17] <zyga> sergiusens: I don't know what's in all the examples
[13:17] <sergiusens> zyga, 3rd; is old-security coming back or gone forever?
[13:18] <sergiusens> if it is gone, I'd rather have it gone forever
[13:18] <zyga> sergiusens: 3 not sure, I can implement it but if powers that be demand it gone, what can we do?
[13:18] <zyga> sergiusens: https://github.com/ubuntu-core/snappy/blob/master/docs/interfaces.md
[13:18] <zyga> sergiusens: that is what we have today
[13:18] <dholbach> thanks... I'll just catch the error if no plug is defined
[13:18] <dholbach> think that should be fine
[13:19] <sergiusens> zyga, create a snapcraft bug and I'll work on a branch; kyrofa heads up, we might release today
[13:20] <kyrofa> sergiusens, thanks for the heads up
[13:20] <kyrofa> sergiusens, though that probably means we need to do the examples as well
[13:27] <zyga> sergiusens: sure; I'll open the bug in a moment
[13:28] <attente> has something changed with the /run/snapd.socket api in the past day? i seem to only be getting 404 errors now
[13:28] <zyga> attente: many things were removed
[13:28] <zyga> attente: look at docs/rest.md (it has been updated AFAIK)
[13:29] <zyga> attente: which endpoints were you calling
[13:30] <attente> zyga: for example GET /2.0/snaps?sources=local
[13:31] <attente> zyga: docs/rest.md was removed too?
[13:32] <attente> zyga: ok, i'll take a look, thanks for the pointer
[13:33] <zyga> attente: no, it is still there?
[13:33] <zyga> https://github.com/ubuntu-core/snappy/blob/master/docs/rest.md#v2snaps
[13:33] <zyga> attente: the prefix changed so you just have to update your client code
[13:35] <attente> zyga: ok, thanks. is the api going to be frozen at some point?
[13:35] <zyga> attente: when we release 1.0 I suspect
[13:35] <zyga> attente: though there will be less changes made now
[13:35] <zyga> attente: you can expect additions rather than changes
[13:39] <jdstrand> zyga: fyi, there are checks that the review tools need to do in the absence of assertions
[13:40] <zyga> jdstrand: perhaps but I don't know what the plan is for that
[13:40] <jdstrand> zyga: I will handle the review tools
[13:40] <jdstrand> dholbach: ^
[13:40] <zyga> jdstrand: thank you!
[13:41] <jdstrand> but there is no point in changing them atm until we have a working system
[13:41] <jdstrand> so, perhaps later this week
[13:41] <zyga> jdstrand: do you know where we are today?
[13:41] <jdstrand> not yet
[13:42] <zyga> jdstrand: we got auto-connection feature landed, also for x11 and unity7
[13:42] <zyga> jdstrand: I'm working on some tweaks to connection control so that it persistst properly and that users are in control
[13:43] <jdstrand> zyga: x and unity7 are autoconnecting? can you explain what you mean by autocontrol?
[13:43] <zyga> jdstrand: x11 (it was renamed)
[13:43] <zyga> jdstrand: it gets connected to os snap on install
[13:43] <jdstrand> I understand what that means
[13:44] <jdstrand> that also is a security hole
[13:44] <jdstrand> so we had the idea that there would be some sort of prompting
[13:44] <jdstrand> what happened with that?
[13:44] <jdstrand> beuno: ^ ?
[13:46] <zyga> jdstrand: there's no propmpting for that as there's no UI for install
[13:46] <jdstrand> I didn't mean an install prompt
[13:46] <zyga> jdstrand: oh?
[13:47] <jdstrand> what I suggested was no autoconnect on install. then on first use, prompt the user somehow, letting them know the app wants privileged access to the user's session. the user says yes or no. if yes, there is an interface connect
[13:47] <jdstrand> this prompt could be done via zenity, or anything really. mvo was in agreement on the approach
[13:47] <jdstrand> there is a card on the idea, but I think beuno was shopping it around
[13:48] <zyga> jdstrand: that's not realistic today
[13:48] <zyga> jdstrand: we'll improve it with SRUs
[13:48] <jdstrand> maybe not 'today' but interface connect is surely something for 16.04 release?
[13:48] <zyga> jdstrand: yes
[13:49] <mvo> jdstrand: quick question, we don't need ubuntu-core-security-{apparmor,seccomp,utils} anymore, correct?
[13:49] <jdstrand> so it should be realistic for 16.04 release
[13:49] <jdstrand> mvo: correct
[13:49] <mvo> ta
[13:49] <jdstrand> mvo: they should be removed from the archive too
[13:49] <zyga> jdstrand: there will be no prompting for 16.04
[13:49] <zyga> jdstrand: we can explore that after the release
[13:50] <jdstrand> zyga: why? who decided that? we are making announcements for this. where was this discussion?
[13:50] <zyga> jdstrand, mvo: FYI we only run apparmor_parser but templates seem to refer to included files
[13:50] <jdstrand> zyga: the prompt can be as simple as updated the shell script
[13:50] <jdstrand> zyga: the includes don't come from ubuntu-core-security. they come from apparmor
[13:50] <zyga> jdstrand: there are no APIs to implement the prompt
[13:50] <jdstrand> we don't need it
[13:51] <zyga> jdstrand: it's not just the UI
[13:51] <jdstrand> all we need is interface connect foo unity7
[13:51] <jdstrand> or whatever the api is
[13:52] <zyga> jdstrand: yes and that's not ready yet
[13:52] <zyga> jdstrand: I'm trying to get it ready
[13:52] <jdstrand> zyga: but you said a moment ago it would be for 16.04 release
[13:52] <zyga> jdstrand: auto connect is internal
[13:52] <zyga> jdstrand: connect/disconnect requires an API
[13:52] <jdstrand> I don't care about *today* so much as when someone tries to use this thing on release day, people see the choice
[13:53] <zyga> jdstrand: I'm trying to implement the API so that we can use it but it's not working as of this second yet
[13:53] <zyga> jdstrand: the goal is to get it working today (API) but I don't think we can manage a GUI at this stage
[13:59] <jdstrand> a gui is a zenity prompt
[13:59] <jdstrand> snappy sees if x11 or unity7 interface (or home) is requested. oh, it is, insert this zenity prompt in the shell script
[13:59] <zyga> jdstrand: can you implement one quickly? perhaps we can manage that?
[14:00] <zyga> jdstrand: note that there's a REST API there
[14:00] <jdstrand> I need beuno to confirm it is ok
[14:00] <zyga> jdstrand: so it's not a simple sequential client
[14:00] <jdstrand> zyga: where is the rest api?
[14:00] <zyga> jdstrand: you'd have to install the snap, inspect available plugs
[14:00] <zyga> jdstrand: deamon/api.go, the docs are in docs/rest.md
[14:01] <zyga> jdstrand: then see if your new snap has x11 or unity7 plug
[14:01] <zyga> jdstrand: and then offer a quick prompt (even without zenity, just a simple stdin prompt)
[14:01] <zyga> jdstrand: and then call .Connect()
[14:01] <zyga> jdstrand: note that there are GO bindings for the api (look at client/interfaces.go)
[14:01] <zyga> jdstrand: I think someone could look at doing that but I need to finish connect/disconnect first
[14:04] <zyga> jdstrand: also note that you need to work with cmd/snap/cmd_ops.go (AFAIR) because that's where install is
[14:04] <zyga> jdstrand, mvo: can tell you more
[14:04] <jdstrand> when I spoke to mvo before he said that he thought this was all managable. that was a few weeks ago
[14:05] <zyga> jdstrand: I thnk that explains it
[14:05] <zyga> jdstrand: there were many things that got us busy
[14:06] <jdstrand> sure, I understand
[14:06] <jdstrand> I'm not upset about that or anything-- I just want to make sure this is handled in some way
[14:08] <zyga> jdstrand: I understand, I'm sorry if I seem defensive :-) I'm just tired and we're all racing to get bits in place
[14:08] <jdstrand> no worries
[14:28] <jdstrand> mvo: can you ping me when you adjust the seeds for ubuntu-core-security?
[14:34] <dholbach> jdstrand, thanks
[14:34] <beuno> jdstrand, I'll follow up on the notify-when-x
[14:34] <jdstrand> thanks!
[15:06] <elopio> ogra_: any news about the new archs? I'm digging all the emails from yesterday but haven't seen anything.
[15:08] <ogra_> elopio, well i got no mails (probably olli forgot to forward something) ... but i have the rootfs snaps building (sadly they arent published yet because i still need to teach livecd-rootfs to not try to build kernel snaps for them)
[15:09] <ogra_> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/xenial/ubuntu-core-system-image/ both fail right after creating the ubuntu-core os snap
[15:17] <elopio> the image PPA is still not building for s390x. mvo: can you enable that? or do you know who can?
[15:21] <elopio> noise][: can you help me with spi? I'm getting 401 checking for the results of the run I launched. https://paste.ubuntu.com/15793410/
[15:28] <mvo> cjwatson: who should I talk to about s390x builds for https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+packages ? is that something you could enable or do I need to ask IS? or can I do it myself if I find the right knob :) ?
[15:28] <mvo> elopio: I ask someone who knows everything ;)
[15:29] <mvo> elopio: I think I can not do it myself
[15:29] <noise][> elopio: hey.. that's odd
[15:29] <cjwatson> you can't do it yourself because s390x has no virtualised builders yet, so it lacks sandboxing
[15:30] <cjwatson> but I see that PPA is already devirtualised
[15:30] <cjwatson> mvo: done
[15:30]  * ogra_ cureses about livecd-rootfs code ....
[15:31] <cjwatson> mvo: new builds aren't auto-created, but if you want to create new builds of an existing source in that PPA without reuploading, you can copy the source over itself including existing binaries and that has the side-effect of creating missing builds
[15:31] <ogra_> feels like i painted myself into a corner, skipping kernel creation for one arch is really hard now :/
[15:31] <cjwatson> mvo: (also obviously only xenial, since s390x didn't exist before that)
[15:32] <mvo> cjwatson: \o/
[15:32] <mvo> cjwatson: thanks a bunch
[15:34] <cjwatson> np
[15:34] <elopio> cjwatson: mvo: thanks!
[15:35] <ppisati> sergiusens: saw it
[15:35] <elopio> noise][: here in the dragonboard section is all I did, in case it helps: http://pad.ubuntu.com/spi
[15:35] <ppisati> sergiusens: i'm a bit nervous about the 'snappy login' step, i bet there's no way to skip it
[15:36] <zyga> ppisati: snap login, snappy is gone
[15:36] <ppisati> zyga: snapcraft login i mean
[15:36] <zyga> ah
[15:36] <ppisati> zyga: what does it do btw?
[15:36] <zyga> ppisati: I'm not quite sure
[15:36] <ppisati> sergiusens: ^
[15:41]  * ogra_ guesses it logs you in
[15:42] <ogra_> :P
[15:43] <ppisati> ogra_: ok, but why it needs to log me into UU build a kernel/snap?
[15:43] <ogra_> heh, no idea ... i was just stating the obvious :P
[15:44]  * ogra_ doesnt even know where to it logs you in
[15:44] <ppisati> ah ok
[15:45] <ogra_> i assume "snapcraft snap" should still work without login though
[15:45] <ogra_> (it does on the livefs builders ... and we wouldnt be able to use any kind of login there(
[15:46] <noise][> elopio: can you try to query the results w/o the test opp query param?
[15:47] <noise][> just https://spi.canonical.com/products/$PRODUCT_ID/tests/events
[15:47] <ppisati> ogra_: nope, it requires the login
[15:47] <ppisati> http://pastebin.ubuntu.com/15794106/
[15:47] <ppisati> btw i thought 'snap' was the default target
[15:47] <ogra_> ppisati, well, it has to be skippable, else we cant build images
[15:48] <ogra_> zyga, sergiusens ^^^
[15:48] <ogra_> there is no way we can add credentials on the image builders, nor can they see the store
[15:49] <sergiusens> ogra_, ppisati the login is to download the os.snap. I wasn't sure it was possible to download without being logged in
[15:49] <ogra_> sergiusens, just grab it from cdimage :P
[15:49]  * zyga doesn't know what login is for in the long term, cannot comment
[15:50] <ppisati> sergiusens: does it store my credentials somewhere?
[15:51] <sergiusens> ppisati, yes, in the form of oauth; not the password
[15:52] <sergiusens> ppisati, ~/.config/snapcraft/snapcraft.cfg
[15:52] <ogra_> sergiusens, how would that work for i.e. a launchpad based build ?
[15:52] <sergiusens> it is only the kernel plugin
[15:52] <ogra_> where you simply dont have these credentials
[15:52] <sergiusens> ogra_, ^
[15:53] <sergiusens> only the kernel plugin
[15:53] <sergiusens> kernel plugin is experimental
[15:53] <ogra_> sure, but what stops me from using the kernel plugin ibn an LP build
[15:53] <sergiusens> nothing is set on stone
[15:53] <sergiusens> and as I said multiple multiple multiple multiple times
[15:53] <sergiusens> this download thing goes away as soon as snappy does the initrd dance the correct way
[15:54] <sergiusens> ogra_, ^ what stops you is the fact that you need to login
[15:54] <ogra_> (i doubt that will happen before next LTS :P )
[15:54]  * ogra_ is obviously very pessimistic wrt the SRU process of massive architectural changes :)
[15:58] <elopio> noise][: same result.
[16:00] <noise][> elopio: hmm, and is that repeatable? starting w/a new product?
[16:26] <elopio> noise][: let me try that.
[16:33] <elopio> noise][: I can't create it anymore. Now I get 401 on the first step.
[16:33] <elopio> oh, wait, no there was a typo.
[16:33] <elopio> going on...
[16:35] <sergiusens> zyga, I logged https://bugs.launchpad.net/snapcraft/+bug/1569452 since I am impatient
[16:36] <elopio> noise][: reproduced again, I created everything from scratch, made a POST on the images endpoint and got 201. But when I query the tests/events, I get 401.
[16:46] <noise][> elopio: ok, I don't have time to dig at the moment, but can try to repro later this afternoon
[17:16] <sergiusens> jdstrand, zyga can you check if I made as "an accurate as possible" translation of things here https://github.com/ubuntu-core/snapcraft/pull/441/files
[17:16] <sergiusens> I am aware some things will just not work
[17:17] <sergiusens> like busybox which would need a read_path of / at least
[17:17] <zyga> looking
[17:18] <sergiusens> not sure what `network-management` was for, I hope it was covered by `network-bind` and also not sure I need `network` if I have `network-bind`
[17:18] <kyrofa> sergiusens, I was just about to ask that question :P
[17:18] <sergiusens> nor if `network-service` is covered in any way
[17:19] <kyrofa> network-service is now network-bind, I believe
[17:19] <sergiusens> my gut says it would
[17:19] <sergiusens> or anything needing network-bind would need network
[17:20]  * sergiusens is sad for removing all those tests though
[17:20] <zyga> sergiusens: network-management is more like "I want to be network-manager"
[17:20] <zyga> network == client; network-bind == server)
[17:21] <sergiusens> zyga, ok, so for something that listens on a port and also talks to the network I need both?
[17:21] <zyga> it won't hurt
[17:21] <zyga> but I suspect network-bind gives you network
[17:21] <zyga> jdstrand: can clarify
[17:21] <sergiusens> zyga, I'll wait for your first pass
[17:21] <zyga> we should add those kind of FAQs to the docs :/
[17:21] <zyga> sergiusens: I reviewed it already
[17:22] <sergiusens> oh; yeah, the docs aren't really all that complete ;-)
[17:23] <sergiusens> zyga, the mosquitto one, elopio can you look ^
[17:23] <sergiusens> zyga, if you look at how the listener plug is defined it seems to indicate it needs `network` and not `network-bind`
[17:23] <zyga> sergiusens: sorry, I'm so drained today I feel like I'm about to fall asleep right here;
[17:24] <zyga> my comments were based purely on the names
[17:29] <jdstrand> sergiusens: network-management was network-admin on 15.04
[17:29] <jdstrand> sergiusens: it is network-control now
[17:30] <jdstrand> sergiusens: network-bind and network client are not the same. network-bind currently gives you all of network, but there is no guarantee that will always be the case
[17:35] <kyrofa> jdstrand, good to know, thank you
[17:36] <sergiusens> jdstrand, ok, so my shout client I should add network and network-bind (basically a web irc bouncer)
[17:36] <sergiusens> shout app (not client)
[17:37] <jdstrand> sergiusens: gopaste technically would need network-control for a 1-1 mapping, but I think gopaste is suffereing from bug #1465724
[17:38] <jdstrand> sergiusens: I would, yes
[17:38] <sergiusens> jdstrand, yeah, most likely the case for gopaste
[17:38] <jdstrand> sergiusens: it is safe to leave network-control out for gopaste and just live with the denial until we can fix the kernel
[17:38] <sergiusens> jdstrand, what is your suggestion for it?
[17:38] <sergiusens> ok
[17:38] <jdstrand> tyhicks: iirc, that is the current recommendation, right? ^
[17:38] <tyhicks> jdstrand: yes
[17:39] <tyhicks> I think I know the proper fix for the denial now
[17:40] <tyhicks> I'll have another look at it soon
[17:40] <jdstrand> tyhicks: oh nice :)
[18:02] <dholbach> elopio, thanks for the update on bug 1569478 and everything
[18:11] <attente> are there any plans to add some api for extracting the metadata out of a snap that isn't yet installed?
[18:12] <kyrofa> attente, a store API already exists. Are you talking about a local snap, though?
[18:12] <attente> kyrofa: yeah, for sideloading
[18:13] <kyrofa> attente, not that I know of, but feel free to log a wishlist bug for it
[18:13] <attente> kyrofa: sure, thanks
[18:13] <ogra_> You can mount the snap or use unsquashfs to get the snap.yaml
[18:15] <ogra_> (it is just a squashfs file after all)
[18:15] <kyrofa> ogra_, hardly an API, but yeah
[18:16] <kyrofa> attente, if you're just scripting something, that may be a good direction
[18:16] <ogra_> Well, yaml iis kind of an api :P
[18:16] <kyrofa> ogra_, hahaha
[18:17] <kyrofa> attente, may I specifically call your attention to `unsquashfs -e`
[18:18] <kyrofa> attente, even more specifically: `unsquashfs -e meta/snap.yaml`
[18:18] <attente> yeah, i was just wondering if maybe there should be some friendlier tooling for it
[18:18] <attente> kyrofa: cool
[18:18] <kyrofa> attente, can you explain your use-case?
[18:18] <kyrofa> attente, though I guess you should do that in the bug anyway-- no need to make you repeat yourself :)
[18:19] <attente> heh
[18:36] <oparoz> Is it possible to merge unsquashed snaps and resquash the result?
[18:37] <beuno> oparoz, you'd have to unpack them, and re-pack them
[18:37] <beuno> what are you trying to do?
[18:37] <oparoz> beuno build parts on different machines
[18:47] <sergiusens> zyga, seems even after changing to interfaces I still have failing tests
[21:07] <jdstrand> meh, the security policy is messed up for the path renames
[21:07] <jdstrand> $ focuswriter.run
[21:07] <jdstrand> mkdir: cannot create directory ‘/home/jamie/snap/focuswriter’: Permission denied
[21:07]  * jdstrand takes a look
[21:07] <tsimonq2> can I make a snap part that just consists of a package from the Ubuntu archives?
[21:07] <tsimonq2> or does it *have* to be from source?
[21:11] <jdstrand> oh no, that wasn't hit. I hit the old ~/snap owned by root bug
[21:11] <jdstrand> sigh
[21:11] <jdstrand> but the path rename broke the apparmor system unit
[21:12] <jdstrand> tyhicks: hey, have you uploaded already?
[21:12] <jdstrand> we need better integration tests
[21:13] <tyhicks> jdstrand: I haven't yet
[21:14] <jdstrand> tyhicks: ok, can you add a super-quick change? just need to update a path. let me get you a bug and details
[21:14] <tyhicks> jdstrand: yes, this is good timing
[21:19] <jdstrand> tyhicks: https://bugs.launchpad.net/snappy/+bug/1569573
[22:16] <oparoz> Is SNAP_FULLNAME going away?
[23:01] <tyhicks> jdstrand: uploaded
[23:48] <sergiusens> jdstrand, tyhicks is that also the reaosn for what I pastebined not working?
 zyga, jdstrand it seems that with these new interfaces I can't create files in SNAP_DATA http://paste.ubuntu.com/15800694/
[23:48] <sergiusens> that just in case ^
[23:49] <zyga> sergiusens: thanks for noticing this. I don't recall us removing this explicitly. I will look at the apparmor template we use
[23:50] <zyga> I see
[23:50] <zyga> looks like another victinm of moving files around
[23:54] <zyga> sergiusens: https://github.com/ubuntu-core/snappy/pull/910
[23:55] <zyga> after the dust settles we should use ... variables for that :P