=== LiX is now known as Guest33445 [05:09] jdstrand, mhall119: about KDE dbus usage... org.kde.$name-$pid is used when the application can have multiple instances running at the same time. they all claim their own address on the bus due to their pid, but you can still find them all due to the basename. applications where multiple instances make no sense do simply not use the pid extension. that being said we do generally know which of the two forms an application will use and we do generally [05:09] know the basename [07:47] hey hey [07:58] PR snapd#2366 closed: interfaces: apparmor support for classic confinement [08:00] Bug #1645605 opened: No alsa module on ubuntu core image [08:03] PR snapd#2361 closed: snap: fix try command when daemon linie is added [08:09] renato__: hey! Did you open a bug for snap connect not working after the first run of a snap using the content interface? If not, do you mind opening one? [08:09] Bug #1645606 opened: Default ubuntu core Pi2 configuration doesn't allow to use fullscreen browser === chihchun_afk is now known as chihchun [08:30] ogra_: hey, I was thinking about simplifying the various repos on https://code.launchpad.net/snappy-hub [08:30] ogra_: specifically I'd like to move the gadget snaps for reference platforms over to github.com/snapcore/ [08:31] and to give them their proper projects on launchpad so that they can have bugs associated with them === JanC is now known as Guest13710 === JanC_ is now known as JanC [09:08] zyga, well, i'd like to start auto-builds for the gadgets before end of year ... i dont think we have that for github projects yet (ICBW though) [09:09] i'd prefer to wait with the move til github is fully supported [09:12] ogra_: my idea is to mirror them to launchpad [09:12] ogra_: but use git in both places [09:12] ogra_: and to really make the reference code discoverable [09:13] ogra_: can you show me which of the 50 branches on snappy-hub contains the published pi2 and pi3 gadgets? I'd like to start with those [09:13] dunno, do we have auto-buiollds for that in place (i.e. you can bump the version and out comes a snap ) [09:13] huh ? 50 branches ? [09:13] ogra_: github -> (git mirror) -> launchpad project -> (snapcraft.yaml auto build to edge) -> store [09:13] https://code.launchpad.net/snappy-hub [09:14] doesnt open here [09:15] http://bazaar.launchpad.net/~snappy-dev/snappy-hub/snappy-systems/files [09:15] odd, this works here: https://code.launchpad.net/snappy-hub [09:15] thats the master branch we always used [09:15] ok [09:15] thanks, I'll use that [09:15] i didnt even know that there was anything else under snappy-hub :P [09:15] how does it auto build [09:16] but i had plabnned to re-work it comp,ltely to use archive packages for the bootloader binaries etc [09:16] and for auto builds [09:16] (we dont have that yet ... this move kind of trashes my plans then) [09:16] ogra_: hmm, why? [09:16] why what ? [09:16] ogra_: (it's not a plan, I want to make the sources for gadgets discoverable) [09:16] why does it trash that plan? [09:17] I want people to be able to find them, report bugs against them and fork them for local tinkering [09:17] well, it adds complexity, it doesnt "trash"them ... sorry :) [09:17] ah [09:17] I hope you just use git [09:17] and that's it [09:17] the rest should be automatic [09:17] ogra_: later on we should be able to build them with snapcraft as well [09:17] ogra_: right now I'll just add a readme file and we can work from there [09:18] ogra_: does that sound good to you? anything I'm missing" [09:18] well, i'd like to sdo the snapcraft (and first of all the deb part) first [09:18] we dont have sources for some of the uboot builds etc [09:18] and foundations insists these should all be deb based in the archive [09:19] i think it would make sense to have a meeting before we change the world [09:19] hmm [09:20] i.e. we need all the binaries in these trees packaged and reviewed (which is partially their responsibiliry) [09:20] the archive part is interesting, I suspect we're going to use archives but everyone building their own won't care about that [09:20] exactly [09:20] right now it's pretty hard to find our gadgets and even harder to make sense of this all and how to tweak e.g. the pi2 one [09:20] apart from BBB these are all official bits that need a classic image equivalent [09:20] I think the git move is separate and should not wait on this [09:20] which means they need to have debs for the bootloader [09:21] so to not do the work twice we should start with the debs [09:21] I think I'm still missing something [09:21] If all I do is move the current branch to git and publish it on snapcore/* [09:21] turning on auto-builds and have snapcraft builds is indeed a side job but moving away from LP adds a lot of complexity [09:21] then everyone working on this can continue to do what they do there [09:21] and it's easier to find [09:22] no [09:22] i'd prefer to have everything ready and done and*then*Ü do the move) [09:22] remember: lp can mirror git! [09:22] we can do the move in 3 hours and then all git commits on github show up in launchpad (as git) and can be acted upon [09:22] without any intervention now ? [09:22] yes, I think so [09:22] last i chercked you needed to manually do that first every time [09:23] manually do the git mirrors? [09:23] I can check, give me a sec [09:23] yes [09:23] ogra_: btw, I also feel this should be a repo-per-gadget [09:24] we should have a reference repo for porters ... but i like to have all bits in one place for the official images [09:24] though if you insist ... [09:24] ogra_: this means no snapcraft builds [09:24] ogra_: one repo per snapcraft.yaml I think [09:24] (makes everything harder imho) [09:24] ogra_: and also, bbb is not officially supported so it'd have to be somewhere else [09:25] ogra_: I understand the transition is difficult but current situation is very bad for everyone trying to figure out how this works and fork something to expeirment [09:25] well, irt is the only one that can use unpartitioned bootloader paertitions ... which makes it a good example [09:26] but well, go ahead and rip it apart ... it will take me a lot longer to sort everything then though [09:26] ogra_: that's all fair, we need to just find a spot for all the (large) number of non-officially supported devices [09:26] ogra_: don't get me wrong, I don't want to make your life harder [09:26] ogra_: I hope we can all benefit from this [09:26] ogra_: please help me help everyone [09:26] (kind of trashes my planning ... but it wasnt high on my TODO (i.e. notz before EOY) anyway) [09:27] mvo, hi, I re-pushed https://github.com/snapcore/snapd/pull/2252 to re-run the tests, most of them worked this time. The few that did not seem to be due to infrastructure: "cannot connect to linode:..." etc [09:27] PR snapd#2252: interfaces: add unconfined access to modem-manager [09:27] ogra_: can you still execute your plan the way you want when this is on git on github in snapcrore? [09:27] sure, i just need more time to adapt to the new stuff first [09:28] ogra_: to git vs bzr or is there something else? [09:28] to a completely new setup and all the possible (and unplanned) differences in that [09:29] ogra_: but all I want to do is to move the repository, is that what you mean? [09:29] my plan was simply a different order and not to sit down and find out how/if auto-builds work, to re-arrange the world etc etc as the first step [09:29] i.e. make things work first and *then* do the chasnges [09:30] ogra_: I see, if we waited till next year would that make it eaier for you? [09:30] but as i said, i only have two weeks before EOY ... i wont finish that stuff in that time anyway [09:31] and we need to coordinate with foundations somehow for everything but BBB [09:31] since they will want a central place for the binaries that also the debs can use [09:32] (uboot, blobs etc) [09:32] ogra_: can that be the git repo perhaps? [09:32] no [09:32] zyga: on alsa: if I'm correct, there are multiple sound modules and they have different names depending on the card [09:32] ogra_: why not? [09:32] not if the git repo has not been completely changed from what the LP one contains today [09:33] ogra_: do you know if this is correct? ^ [09:33] didrocks: interesting, how does it work on classic? [09:33] the repo will end up to only have a snapcraft.yaml in the end [09:33] zyga: it's a very good question, I never dive into this part, pulseaudio worked for me :p [09:33] ogra_: interesting, and where will all the source code be? [09:33] zyga, preferably debs in the archive [09:33] so the classic images can use them [09:34] ogra_: hmm, I see [09:34] ogra_: I think this is somewhat difficult for others (poor reference) because they will start with uboot tree [09:34] ogra_: not with any debss [09:34] ogra_: but perhaps we can find a way to accomodate that somehow [09:34] zyga: can you try to lsmod | grep snd on your machine? [09:34] I do have: [09:34] snd 81920 18 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_seq_device [09:34] (notice the thinkpad_acpi) [09:34] zyga, the only arch that can use a uboot tree only is the BBB [09:35] zyga, all others need additional blobs [09:35] ogra_: that's fine but my point is that the snapcraft.yaml that is deb based is not aligned with people that want to create a gadget for their board that uses some bootloader and they build it from sources [09:35] zyga: ah, the machine-dependant one for me is: cat /proc/asound/modules [09:35] 0 snd_hda_intel [09:35] didrocks, there are /usr/share/alsa/cards and /usr/share/alsa/ucm [09:36] didrocks: I'm on a VM here, on my thinkpad natively I'd probably get the same thing [09:36] they have the default configs for certain cards [09:36] zyga, yes, so using our official gadget trees as reference is perhaops the wrong thing altogether [09:36] zyga: and look at /etc/modprobe.d/alsa-base.conf [09:36] those are the rules [09:36] zyga, like our kernel snaps are not even remotely related to what the kernel snapcraft plugin gives you [09:37] abeato: aha, I have a look, thank you [09:37] great, np [09:37] ogra_: context is bug #1645605 [09:37] Bug #1645605: No alsa module on ubuntu core image === chihchun is now known as chihchun_afk [09:38] zyga, anyway, do what you feel you need to do ... [09:38] didrocks: hey, thanks for the additional info in the download bug \o/ I'm going through it now and try to make sense of it [09:39] didrocks, BSPs usually have their sound bits builtin ... also arm boards usually use UCM [09:39] mvo: thanks! If there is anything else I can do to help debugging, I have my setup started here === chihchun_afk is now known as chihchun [09:46] didrocks, anyway ... your alsa bug is a kernbel bug in the first place [09:47] (if you dont find a soundcard there is either the UCM setup or the module missing in the kernel) [09:47] i thought we had that enabled but /proc/asound/cards is empty on all boards here [09:48] so first of all the kernel needs the bits enabled to turn on UCM ... and it should ship the right UCM config [09:51] re [09:51] ogra_: that's true [09:51] ogra_: I guess we have to decide what to do then [09:51] ogra_: perhaps we need "both" to the point where those are identical (long term plan) [09:51] ogra_: perhaps something else entirely [09:52] well, rolling a gadget isnt "have that ubioot tree and drop a snbapcraft.yaml in" [09:52] it is sadly a lot more complex [09:53] ogra_: indeed [09:53] ogra_: do you think it can be, eventually, a snapcraft.yaml in a tree of sources (and blobs if there's no source for them) that builds all the way? [09:53] anyway, if you feel it is urgent to do that github move and split of trees right now, go ahead [09:53] no [09:54] you need a lot of manual work, tinkering and testing to find the right setup before being able to build your first gadget if it is a completely new arch [09:54] ogra_: oh, sure, I mean our references [09:54] we should have a reference tree for every bigger setup imho [09:54] ogra_: do you think we can eventually build them from source all the way? [09:55] (i.e. we dont have anything for sunxi boards ... proting to that will be a pain for users) [09:55] we can surely build parts opf them from source ... really depends on the board [09:55] ogra_: I see, thanks for the input [09:55] ogra_: I'm not going to do anything right now, I've added a card to track this [09:55] the only arches where booting does nto depend on binary blobs are x86 and BBB thogh [09:56] *not [09:56] ogra_: I'd like to improve the visibility of the gadgets [09:56] ogra_: and perhaps de-mystify them a little [09:56] +1 [09:56] ogra_: but it's a complex topic and I don't want to just break more than I improve [09:57] is there any documentation about the dump plugin? [09:57] well, i think forst of all we should have a meeting or so with foundations [09:57] http://snapcraft.io/docs/reference/plugins/dump is virtually empty [09:57] to clearly line out a plan ... [09:57] ogra_: that's a good idea [09:57] the "examples" also sends you to an empty page [09:57] ogra_: preferably early so that everyone can think about this over xmas [09:57] i had hoped to do that in the hague ... but there was not much foundations there [09:58] (i want steve and adam in that meeting) [10:01] ogra_: so slangasek and ... (slipped my head) [10:01] (and looking at /names doesn't help) [10:01] the infinite one ;) [10:02] infinity in case that wasnt clear :) [10:15] PR snapd#2369 opened: snap: disable support for socket activation [10:29] does adt-buildvm-ubuntu-cloud on xenial not work to build yakkety images? [10:30] Chipaca: you need the version from xenial-backports iirc [10:31] Chipaca: apt install autopkgtest/xenial-backports [10:32] mvo, ah! thanks [10:33] that works, indeed [10:33] PR snapd#2363 closed: snap: support "daemon: notify" in snap.yaml [10:49] ogra_: right, that was clear, thanks :) [10:50] :) [11:05] PR snapd#2370 opened: i18n: use github.com/ojii/gettext.go (pure go) for i18n to avoid cgo === chihchun is now known as chihchun_afk [11:23] snappy-debug suggestion "* adjust program to not require 'CAP_DAC_OVERRIDE' (see 'man 7 capabilities')" anybody have any idea how to do this? [11:26] Bug #1402536 changed: snappy install should support version/hash to get specific version from the store [11:26] Bug #1413185 changed: Snappy remote install requires password three times [11:35] Bug #1457491 changed: Upgrade from r41 to r55 on BBB failed to boot and also to failover (drops into rescue systemd mode) [11:35] Bug #1459642 changed: If a gadget install fails, udev is not cleaned up [11:50] Bug #1464944 changed: no way to configure keyboard layout [11:50] Bug #1466682 changed: Docker unix socket permission issue on ubuntu-core update [11:50] ogra_: invinte sent, let me know if that's that's too late for you [11:53] Bug #1468958 changed: selftests print "no such file or directory" on error [11:53] didrocks, hey, I saw someone complaining about that on the ml, I think there is a bug already. Let me find it [11:54] zyga, hmm, its ok ... are you sure that short of a notice works for the others though ? [11:56] Bug #1472721 changed: snappy update shows no message when there are no updates [11:57] PR snapd#2371 opened: daemon, store: let snap info find things in any channel [11:59] Bug #1472802 changed: ubuntu-core timezone config has no effect [12:01] ogra_: if not we can move [12:02] Bug #1474125 changed: Image got in a broken state after update -> rollback -> update (wrong kernel) [12:03] didrocks, ohh, just saw that you replied the e-mail asking to open the bug, but did not get reply. Let me open it [12:08] Bug #1479027 changed: package.yaml docs missing releases OR frameworks fields [12:08] Bug #1481086 changed: Need API/cli method to know if "is_snappy" [12:11] Bug #1484982 changed: service description whitelist unnecessarily strict === hikiko is now known as hikiko|ln [12:14] Bug #1495059 changed: cannot add new sudo users [12:17] Bug #1495452 changed: auto upgrade unintentionally updates /etc/udev/rules.d/70-persistent-net.rules [12:17] Bug #1495662 changed: Services and binaries allow _ # [12:20] hi I have this suggestion by snappy-debug: "* adjust program to not require 'CAP_DAC_OVERRIDE' (see 'man 7 capabilities')" anybody have experience of this? [12:20] Bug #1496319 changed: Could not create symlink to hw device with udev rules [12:20] Bug #1499109 changed: hw-assign and oem assign are inconsistent [12:23] Bug #1499478 changed: snappy install failure if service doesn't start does not cleanup [12:23] Bug #1499662 changed: boot partition size should be configurable [12:26] Bug #1499993 changed: U-d-f uses hardcoded names for kernel and initrd instead of the ones defined in hardware.yaml [12:26] Bug #1500020 changed: /var/lib/opencryptoki needs to be in /etc/system-image/writable-paths [12:29] bonjello [12:29] Bug #1502810 changed: Implement "snappy try" [12:44] zyga: i tried snap-confine from the use-aa-support branch but it segfaults : http://paste.ubuntu.com/23553160/ - do you have any suggestion? [12:47] longsleep: looking [12:48] longsleep: any chance to get a backtrace? [12:48] zyga: yeah let me install gdb [12:54] Bug #1504649 changed: dns-nameserver, dns-nameservers and dns-search not documented for snappy config for static ip addresses [12:55] PR snapd#2372 opened: interfaces/seccomp: add support for classic confinement [12:55] zyga: here you go: http://paste.ubuntu.com/23553195/ [12:55] longsleep: checking [12:55] not much in there :/ [12:55] longsleep: oh, nice [12:56] longsleep: up [12:56] longsleep: (one sec, switching branches) [12:56] longsleep: print label [12:57] Bug #1504938 changed: invalid character '<' looking for beginning of value [12:57] Bug #1505696 changed: SquashfsTestSuite.TestRunCommandUgly fails if you have a non-english locale [12:57] Bug #1505717 changed: prefer vmlinuz-*.efi.signed over vmlinuz in device tarball [12:57] longsleep: print mode [12:57] longsleep: perhaps something I dind't account for, I can fix that quickly [12:58] zyga: http://paste.ubuntu.com/23553198/ [12:58] longsleep: let me cook a patch === hikiko|ln is now known as hikiko [12:58] longsleep: nice, thanks [12:58] zyga: let me see if i can resolve the not found [12:58] longsleep: nah, that's all good [12:58] longsleep: I know what the bug is already [12:58] longsleep: thank you!!! :) [12:58] zyga: awesome :) [13:00] Bug #1507607 changed: move boot-ok to before sessions [13:01] zyga: fixed the not-found - see here http://paste.ubuntu.com/23553206/ [13:02] longsleep: I just pushed a fix [13:02] zyga: rebuilding [13:02] longsleep: feel free to comment on the pull request as well once you get this working [13:03] Bug #1511435 changed: ubuntu-snappy.firstboot fails when oem snap contains preinstalled snap [13:04] zyga: looks better now [13:04] /root/xenial/root/snap-confine/src/snap-confine snap.hello-world.env /snap/hello-world/27/bin/env [13:04] SNAP_NAME is not set [13:04] zyga: so do you have a suggestion how i could fully test this now? [13:05] zyga: still does not seem to work though [13:05] SNAP_NAME=hello-world /root/xenial/root/snap-confine/src/snap-confine snap.hello-world.env /snap/hello-world/27/bin/env [13:05] cannot change apparmor hat. errmsg: Operation not permitted [13:05] support process for mount namespace capture exited abnormally [13:05] [157896.731125] type=1400 audit(1480424709.523:33): apparmor="DENIED" operation="change_hat" info="unconfined" error=-1 profile="unconfined" pid=17652 comm="snap-confine" [13:09] longsleep: (just in a call now, I'll be with you in 15 minutes0 [13:09] zyga: all right thanks - take your time and just ping me when you are available [13:09] PR snapcraft#918 closed: create the deltas package/class with xdetal generation implementation [13:16] longsleep: nice [13:16] longsleep: you now need snapd and snap-run to get this to work [13:16] longsleep: oh, that's super odd, let me check why this happens (the hat thing which is what this was supposed to fix) [13:18] zyga: is there a way i can make snapd/snap-run use my custom snap-confine? [13:18] longsleep: fixed again [13:18] zyga: you are awesome, rebuilding [13:19] longsleep: yes, do a bind mount so it shows up in /usr/lib/snapd [13:19] longsleep: sudo mount --bind some/custom/snap-confine /usr/lib/snapd/snap-confine [13:19] longsleep: and make sure it's stuid root [13:19] setuid* [13:19] longsleep: (no wonder this doens't work, there's no spread test for it yet) [13:19] longsleep: thank you for trying this [13:20] zyga: seems to work now [13:21] longsleep: great! [13:21] zyga: http://paste.ubuntu.com/23553265/ so what does that tell us now? [13:21] longsleep: thank you! [13:21] Bug #1511447 changed: snapcraft stage does not work with Go and Launchpad [13:21] zyga: that branch will get merged into release eventually and it wont matter that my kernel does what it does? [13:21] longsleep: that it should be good [13:21] longsleep: you can set SNAP_CONFINE_DEBUG=yes [13:21] longsleep: to see what's going on [13:21] longsleep: yes [13:22] longsleep: I plan to merge it as soon as I get a review from security [13:22] longsleep: well.. [13:22] longsleep: if your snap-confine is unconfined it won't try to switch hat [13:22] longsleep: there are other places that care about apparmor [13:22] longsleep: (in snapd) [13:22] longsleep: but some of the work I'm doing will make that more flexible [13:22] longsleep: I want to know one more thing [13:22] longsleep: can you run [13:23] longsleep: apparmor_parser -r /etc/apparmor.d/usr.lib.snapd.snap-confine [13:23] longsleep: that probalbly crashes but I want to see why [13:23] zyga: sure, this is the debug output http://paste.ubuntu.com/23553270/ [13:24] Bug #1511448 changed: ubuntu-snappy.firstboot fails when oem snap contains config for snaps not preinstalled, built-in [13:24] zyga: the apparmor_parser -r does not print anything [13:24] longsleep: odd [13:24] longsleep: hmmm [13:24] longsleep: I'll get back to you [13:34] anyone had any success in allowing a confined snap to manage network namespaces? [13:39] jamespage: hey [13:39] zyga, hello [13:39] jamespage: jdstrand is working on supporting it, the current idea is that /run/something-used-by-ip-netns will be like /media today [13:39] I was just reading https://bugs.launchpad.net/snappy/+bug/1624675 [13:39] Bug #1624675: Please add network-namespace interface [13:39] jamespage: and then you can use ip setns [13:39] jamespage: I'll try to sync with jamie today, adding that directory should be trivial [13:40] jamespage: would that be sufficient for you? [13:40] zyga, it might be - the neutron agents do a load of things with namespaces to support overlapping ip address ranges and alike [13:40] jamespage: note that as of today, you can use devmode to create network namespaces via 'ip netns' that will work for that snap [13:40] jdstrand: hey! [13:41] jdstrand, yeah - have my snaps working ok with the hypervisor snap in devmode [13:41] jdstrand: I sent you an invite for a call today (if you can get there please let me know) [13:41] zyga: hi! [13:41] I think that this netns bit is the last part that means I still need devmode [13:41] (looking at the kernel log at least) [13:42] well for now [13:42] jamespage: do you have a wiki page for testing this? I've never gotten very far with neutron/etc in the past. ideally this would be to run in a vm [13:42] jdstrand, yeah - we do [13:42] jdstrand: I replied to your question on https://github.com/snapcore/snap-confine/pull/193 -- I'd love to know if I can merge that and if my explanation is correct, I'm working on addressing the remaining things in a new pull request [13:42] PR snap-confine#193: Replace mkpath with sc_nonfatal_mkpath [13:42] jamespage: do you know otoh if these things are using 'ip netns' or are they doing something else? [13:42] jdstrand, https://github.com/openstack-snaps/snap-test [13:43] I need to add in the bit for the nova-hypervisor snap - however that is a little dependent on some of the interface work I have inflight atm [13:43] jdstrand, they all use ip netns [13:44] jamespage: ok, I'll be poking at this soon (ie, this week) [13:44] but I guess using in devmode would be supportable [13:44] I'll need to drop the newer interface bits from the snap for now [13:45] I can deal with interface bits fine [13:45] so don't do anything extra on my account [13:46] jdstrand, ack [13:46] zyga: re the meeting later, I'll talk to tyhicks and one of us will join [13:47] tbh most of my time in the last few days was burnt on trying to get libvirt to work from within a snap [13:47] I parked that for now [13:47] eek [13:48] jdstrand: perfect, that's exactly what I suggested in the meeting notes [13:48] jamespage: definitely start with devmode. libvirt as a snap is going to need to be super-privileged like docker-support and lxd-support [13:49] jdstrand, most of my pain was due to the amount of build time detection and path encoding that libvirt does [13:49] yeah, I can imagine [13:49] anyway I'm aiming for on host os libvirt and ovs for now [13:50] I have another interface to propose - openvswitch in the style of libvirt - just allows access to the ovs db socket on the host [13:51] Bug #1516351 changed: Consider changing release id [13:56] tedg: do you know what's keeping inkscape from being published to the stable channel? [13:57] Bug #1520093 changed: ugly error when trying to set config without sudo [13:57] Bug #1521927 changed: Package operations are not atomic. [14:00] Bug #1563737 changed: Bootloader type detection ignores the actual bootloader in use [14:06] Bug #1564316 changed: classic dist-upgrade fails on sudo and tzdata... [14:08] renato__: hey, did you file it? I would like a link I can reference :) [14:09] Bug #1569577 changed: please remove var/lib/snapd/apparmor/additional from debian/snapd.dirs [14:10] didrocks, https://bugs.launchpad.net/ubuntu-app-platform/+bug/1645731 [14:10] Bug #1645731: Fail to access the shared content if app starts before connect interface [14:11] renato__: thanks! :) [14:11] renato__: hum, no snappy ref? [14:12] renato__: didn't Mirv said this was a snappy bug? mind adding this task? [14:12] Bug #1570280 changed: snap and snappy man pages incomplete [14:12] didrocks, this is a snapd bug I think [14:13] renato__: please add an upstream snappy task then [14:13] didrocks, renato__: I just assigned that bug to mysel [14:13] f [14:14] zyga, ok thanks [14:14] zyga: thanks :) [14:15] Bug #1570261 changed: Snappy does not deal well with non-existing/non-working daemon command [14:15] Bug #1645731 opened: Fail to access the shared content if app starts before connect interface [14:24] mhall119: Yes [14:24] Bug # changed: 1570618, 1571710, 1571721, 1572151, 1572463 [14:25] mhall119: It's based on a pre-release version that hasn't been released yet. Will be pushed to stable once 0.92 is released. [14:26] ah, cool, ok [14:27] is that happening soon? If not, would they snap up the current stable? [14:30] PR snapd#2373 opened: debian: remove unneeded conflict against the "snappy" package [14:33] Bug #1574526 changed: x11 plug doesn't allow getsockname, breaks xeyes [14:33] Bug #1574556 changed: apparmor denials reported for encrypted HOME [14:36] Bug #1574829 changed: snappy install requires root or login, but doesn't tell you so [14:36] Bug #1575399 changed: Half installation for a snap [14:39] Bug #1576263 changed: Installing a non-existent app from the store results in core being downloaded but not installed [14:42] Bug #1577228 changed: "Ubuntu Core Snappy AutoUpdate" service failed with "error: the required argument `` was not provided" [14:45] Bug #1577441 changed: No way to rollback a snap since the move to snap command [14:46] interesting [14:46] oops wrong channel [14:46] sheesh [14:46] is there a snappy core channel? === pbek_ is now known as pbek [14:52] Bug #1577439 changed: No more -u/-v options for "list" [14:52] Bug #1579932 changed: The user acceptance test suite is called integration-tests [14:52] Bug #1580403 changed: snap tries to manage bootloader in snappy-on-ubuntu-classic mode [14:54] wxl: this is this one [14:55] Bug #1583259 changed: Snappy needs to influence environment variables in applications (Ubuntu):Fix Released> [14:56] didrocks: great. is there a prepared snappy image i could use in virtualbox or do i just need to go ahead and install one? [14:58] wxl: hum, there is a qemu image, I don't think there is one for virtualbox [14:58] Trevinho: hey! I would need the bug reference for the snapcraft parser now please :) [14:58] didrocks: great thanks [14:59] didrocks: I already subscribed to you there... [14:59] Trevinho: oh? [14:59] didrocks: see https://github.com/snapcore/snapcraft/pull/930 [14:59] PR snapcraft#930: Parser support remote dependencies [14:59] didrocks: https://bugs.launchpad.net/snapcraft/+bug/1645350 [14:59] Bug #1645350: Parts depending on other remote parts aren't properly added [14:59] Trevinho: thanks! [14:59] Trevinho: you didn't subscribe me to the bug [15:00] didrocks: I did... https://usercontent.irccloud-cdn.com/file/sJNTn1yT/ [15:01] * Trevinho has to fix the branch now... :-/ [15:01] Trevinho: I only see Joe and you on my launchpad bug [15:01] weird [15:02] you are talking about #1645350, right? [15:02] Bug #1645350: Parts depending on other remote parts aren't properly added [15:02] yes [15:02] this is weird, I definitively have only you two in this section :/ [15:02] who knows.... maybe you filter out something... but I did subscribe you just after filing it [15:03] zyga: 193 approved [15:04] Trevinho: well, my filter wouldn't change launchpad page :p [15:04] Bug #1584586 changed: First snap install should fail fast rather than download OS snap [15:04] didrocks: yeah I mean... Something related to lp project options? [15:04] Trevinho: could be… I don't think, first time I see that [15:05] jdstrand: thanks! [15:05] zyga: thanks for the cleanups :) [15:05] jdstrand: I'm taking a different approach for mode/uid/gid mkdir, that will be easier to verify I hope [15:06] hi I get this output when I try to run my program as sudo "* adjust program to not require 'CAP_DAC_OVERRIDE' (see 'man 7 capabilities')" could anyone advise me how to deal with this please? [15:07] sorry meant to say while running snappy-debug [15:09] gerry_: if you get it while running sudo, it sounds like the unix permissions are being ignored because you are root. eg, perhaps a user owned directory that is 755 that root is writing to, a file that is 644 that isn't root owned, etc [15:09] that is usually what triggers that sort of thing [15:10] ok so I change the permissions of my file? [15:10] if that is the issue, that would fix it, yes. change perms or owner [15:12] jdstrand : thank you for your help I will try [15:14] PR snapd#2374 opened: snap: tweak snap install output as designed by Mark [15:18] jdstrand: no I still have the same problem my program run when installed in devmode but crashes with "No protocol specified Exception in thread "main" java.awt.AWTError: Can't connect to X11 window server" when I try to run it with sudo, while installed in dangerous mode [15:19] Bug # changed: 1586248, 1587175, 1587445, 1587676 [15:26] um, so is ubuntu core (http://cdimage.ubuntu.com/ubuntu-core/16/stable/) and ubuntu snappy core different??? [15:31] Bug #1596243 changed: snap gets stuck removing snap [15:31] Bug #1597417 changed: Doesn't use "update-desktop-database" which is needed for mime handlers [15:31] wxl: no, it's the same, ubuntu core is the official name [15:31] (yeah, naming was bad, sorry) [15:34] Bug #1597948 changed: github.com/snapcore/snapd/cmd/snap TestSnapRunSnapExecEnv fails if HOME is set in environment [15:37] Bug #1599919 changed: SnapOpSuite unit tests interfere with the user's $HOME/.snap directory [15:38] didrocks: ok. well when i boot that image, it asks me to configure networking. it doesn't seem to give me an option for wifi, which is understandable, i guess. is there a workaround besides building a custom image? also, is there official documentation that goes over things like this? === palasso_ is now known as palasso [15:39] wxl: you are in a VM, correct? This is why you don't have wifi option [15:39] but your VM should share connexions [15:40] Bug #1600260 changed: Support paravirtualization [15:41] didrocks: omg. derp. [15:43] Bug #1600719 changed: The camera interface only grants access to /dev/video0 [15:44] didrocks: the "store" refers to where exactly? [15:46] Bug #1603018 changed: snap create-user gets bad username [15:46] wxl: ubuntu snap store (which is the same than click store) [15:46] I thought there was a link to register, correct? [15:46] PR snapd#2375 opened: store: retry tweaks and logging [15:47] not that i saw [15:47] is that apps.ubuntu.com? [15:48] or maybe myapps.developer.ubuntu.com? [15:48] yeah, the latter [15:49] sorry for all the noob questions but i'm not really finding any great docs anywhere and the answers aren't immediately obvious [15:49] Bug #1603610 changed: Snaps have no screenshots Yakkety):Fix Released by robert-ancell> [15:49] so does it create a login based on that account? if so, given i got in via SSO, what's my password? [15:50] wxl: yeah, there is few starting guide [15:50] create an account for myapps [15:51] jdstrand is bug #1603879 something straightforward ? or very tricky? [15:51] Bug #1603879: Requesting additions to optical-drive interface for cdparanoia. [15:51] wooot, it looks like the snappy team is triaging their bugs ;-) [15:51] seb128: *cough* [15:52] :-) [15:52] seb128: did I ever mention how much I hate bug triage? [15:52] haha [15:52] you might :p [15:52] Bug #1604016 changed: Snap requires sudo if not logged in [15:53] but yeah, it's borring but useful! [15:53] slangasek, ogra_: will you be able to make the call/hangout on gagets later today? [15:53] speaking of bugs, where does one report issues about the snapcraft.io documentation bugs? [15:53] didrocks: ok got the account. it accepted my email. now i'm confronted with a request for credentials and have no clue what they are. [15:54] well, it's just your email address, correct? [15:54] the "store account" [15:54] yep, but there's no password given SSO [15:54] you don't know password [15:54] unless i'm meant to use my launchpad password [15:55] on the ubuntu core image vm [15:55] just the email address is asked [15:55] s/know/need any/ [15:55] Bug #1604880 changed: Missing inhibit interface [15:55] Bug #1604885 changed: Access to mounted USB drives [15:55] i already gave it that, which is accepted [15:55] so now i'm beyond that [15:56] ah, I see what you mean [15:56] did you read the last line? [15:56] now i'm presented with a localhost login [15:56] zyga: yes, though I'm surprised this needs a hangout. I had talked with sergiusens at the last sprint about the fact that we needed pointers to sources from binary snaps, and that it should preferably be done officially in snapcraft - since we don't have any way to add arbitrary things to meta if we're using snapcraft [15:56] you can ssh to your vm now [15:56] better to ssh [15:56] oic [15:56] your ssh key was copied over to it [15:56] seb128: yeah [15:56] seb128: snapcraft.io bugs, not sure, dholbach probably knows [15:57] slangasek: this is an informal call driven mainly by me; I want gadgets to be easier to find and (eventually) serve as a reference [15:57] seb128: https://github.com/ubuntudesign/snapcraft.io/issues/new [15:57] see bottom of the page :) [15:57] thanks didrocks [15:57] slangasek: since I don't own then I cannot decide by myself and I want to share my (simple) plan/idea with you to get feedback and see if you like the idea [15:57] slangasek: right now it's hard to find where each gadget comes from and harder to report bugs against them [15:58] didrocks, right, I was unsure if the content for the plugins section is coming from the site or autogenerated from the code [15:58] slangasek: I talked to ogra about this in the morning and he suggested that I add you and adam to the mix [15:58] seb128: long long discussion… [15:58] seb128: in summary, file them there, and normally davidcalle retargets, fixes [15:58] zyga: ok. do you have a proposed layout under github for them? How will I have commit access to them once moved there? [15:58] didrocks, lol, let's not reboot it then, thanks for the url [15:58] Bug #1604964 changed: huge download for nothing - snap does not exist [15:58] Bug #1605216 changed: cups-control interface doesn't allow printing [15:58] thanks [15:59] slangasek: my layout idea is super simple, either move them as-is (perhaps not ideal, see below) and start making them nicer (commit rights are super easy to manage) [15:59] slangasek, the question was also about the uboot sources (deb sources shared with classic images) etc ... [15:59] slangasek: or split them so that later on launchpad can import separate repos and do github->launchpad->(Snapcraft)->store pipeline [15:59] slangasek: but even the split can be step two [15:59] slangasek: correspodning to this I'd like to have a place to file bug against each specific reference gadget (all 4 of them) [16:00] hi snappy debug has this output "* adjust program to not require 'CAP_DAC_OVERRIDE' (see 'man 7 capabilities')" when I try to start my program with sudo any help gratefully received [16:00] seb128: didrocks: "fixes"? that's debatable :p [16:00] slangasek, my assumption is that the github "tree" is in the end just a snapcraft.yaml and that we can have the gadgets auto-built if someone bumps a version in the tree [16:00] slangasek: and lastly, not sure what to do with bbb, it's not the same support status but we should find some way to have it live (as a community gadget) somewhere and perhaps share the benefits [16:00] at least that was the plan with lsunchpad [16:00] i think github is a little further from that automation plan atm [16:01] seb128: this location is fine, lp:snappy with snap-docs tag works as well if you prefer your bug mail on lp [16:01] zyga, i'm the maintainer of BBB ... i'lll keep it in LP if you dont mind [16:01] slangasek: perhaps we can do a project for gadgets/kernels that are not officially supported [16:01] (BBB is community supported ... ) [16:02] zyga: as it's not supported by us, but by ogra, you should ask ogra what works for that :) [16:02] zyga, kernels are a totally different story [16:02] ogra_: no, I don't mind but if you can use bbb as a way to show how to build an ecosystem (if we agree on how that would look like) [16:02] slangasek: my main goal is to make the gadgets easier to find, easier to fork and more of a reference [16:02] slangasek: all I want to do is take a first step [16:02] i wont go my own path here but i prefer to have things easier maintainable ... gihub is a pain i'd like to avoid for my own projects [16:02] slangasek: and move them out of the rather hard-to-find project on launchpad branch [16:03] (until LP stops to support bzr completely :) ) [16:03] davidcalle, ok, thanks [16:03] ogra_: that's okay, let's not complicate this over with bbb, focus just on the reference platforms [16:03] davidcalle, in any case the bug as been fixed it seems, so for next time [16:03] seb128: best kind of bugs [16:03] davidcalle, the "examples" at the bottom of the plugins descriptions was giving a github page stating that queries needs a project or user specified [16:04] but seems to work now [16:04] slangasek: apart from what we have there in the lp branches now I'd like to add a readme to each repository so that it explains what the content is, how it can be built and how it ends up in the store [16:04] slangasek: as well as a link to launchpad for bug tracking [16:05] zyga, regarding kernels, the stuff is already moving to kernel.ubuntu.com (sadly) and will be 100% in the kernel team hands ... apart from the builds for the edge chaynnel where we need group mgmt from LP [16:05] slangasek: and anything else we can come up that's useful over time [16:05] ogra_: interesting [16:05] the kernel team will take ovber everything [16:05] ogra_: I think that's fine, my focus is on gadgets today :) for kernels there will be another day (maybe) to look at how people can do their own kenrel easily with snapcraft / store [16:06] (but we need edge in a state that everyone can make changes to the non-kernel components in the kernel snap) [16:06] zyga, well, such people should use the snapcraft plugin ... but that will make you end up with something completely different indeed [16:07] ogra_: step by step, let's work on gadgets first, set up git trees, lp mirrors etc [16:07] ogra_: sergiusens made a pull request that snapcraftifies one of the gadgets [16:07] ogra_: that's a great first step and IMHO the way to go with all of them [16:08] zyga, yes, i have sergiusens commit open here because i planned to look into it before EOY [16:08] is there a juju snap? i'm not immediately finding one and i'm surprised [16:08] ogra_: +1 thank you [16:09] slangasek: so that's the rough idea, the call is there just so that we can all share concerns and plans and align [16:10] PR snapd#2376 opened: docs: document SNAP_DEBUG_HTTP in HACKING.md [16:11] correction: i find https://uappexplorer.com/app/juju-nskaggs.nskaggs but i cannot for whatever reason find it with snap [16:11] wxl, probably not in the stable channel or perhaps it uses devmode [16:12] ogra_: oh, you know what. it's amd64 only. [16:13] :) [16:13] sergiusens, hey, what do you mean by "allowing" in "we agreed on allowing /snap//current"? That's its a stable interface garanty that it's not going to change/go away and that any snap can rely on the dir to be there for ever? [16:13] awww fooey [16:18] PR snapd#2377 opened: snap: provide friendlier `snap find` message when no snaps are found [16:20] zyga: hey, tyhicks was wondering if the meeting re snap-confine and snapd merging just to convince the security team it is ok, or is it something else? [16:20] s/just/was just/ [16:20] hey zyga :) [16:20] well, I was wondering too after he mentioned it :) [16:21] jdstrand: I want do convince you that it is better to merge it into snapd [16:21] tyhicks: hey, how are you :) [16:21] doing well :) [16:22] tyhicks: I discovered that a gamy my son likes has a special easter egg for thanksgiving :) [16:22] tyhicks: (too bad we cannot do those in snap-confine) ;) [16:22] hehe [16:22] zyga: well, if that is all the meeting is about, we can probably cancel it-- tyhicks and I don't have strong objections [16:22] jdstrand: ah, in that case +1 [16:22] Bug # changed: 1606813, 1606815, 1606893, 1606932, 1606961 [16:22] jdstrand: do you want to have the security label that requires a security +1 on pull requests? [16:22] zyga: I don't know that we need a meeting for that. We understand the positives and only have a preference for keeping it a seperate project (no hard blockers against it) [16:23] jdstrand: or some other way to track this? [16:23] * zyga nod [16:23] * zyga nods [16:23] zyga, jdstrand: I'll leave a +0 comment in the bug [16:24] thank you [16:24] zyga: we probably need a way to track things better that need security team awareness/review, yes [16:25] we will need that [16:25] zyga's idea for labels is probably the best that we'll get [16:25] zyga: it was easy before to see the changes to snap-confine [16:25] is there a way to auto-label? [16:25] like, if it is in this dir, then it gets a label? [16:25] Bug # changed: 1607121, 1607129, 1607344, 1607604 [16:26] oh, that's a nice idea [16:26] jdstrand: not that I know of, it will require some though on our end [16:27] jdstrand: maybe with a bot later (it can do this in pull requests) [16:27] thought* [16:27] zyga: having it separate in github meant that there was a mental separation that snap-confine was special and needed special attention. I'm not sure how to achieve that once it is merged [16:27] sometimes the smallest changes can result in disaster in a setuid executable [16:28] Bug #1608608 changed: Snapweb avahi service is still called webdm.local [16:28] Bug #1608807 changed: create-user fails on classic [16:28] Bug #1586248 opened: 96boards-kernel need change name [16:29] I don't see a way to automatically tag PRs like that [16:29] a bot is likely needed === greyback is now known as greyback|afk [16:31] Bug #1609930 changed: Support license acceptance [16:34] seb128 it will be a stable interface yes; if it changes we burn zyga's place down [16:34] sergiusens, good! :-) [16:34] :-) [16:34] Bug #1611063 changed: can't mkdir SNAP_USER_COMMON directory [16:37] jdstrand: note that many things in snapd are already special (all interface reviews) [16:37] Bug #1611384 changed: Change detection not working, have to "snapcraft clean" between builds when modifying snap contents [16:38] Bug #1616006 changed: clean remove of snapd [16:38] jdstrand: how do you manage those currently? [16:38] sergiusens, seb128: AFAIK we're not changing the current symlink in 16 series (it will stay as-is) [16:38] zyga, I'm glad to read that! [16:39] timothy: hey, you reported bug 1604346 a while ago [16:39] Bug #1604346: snapd apparmor tests fail on ArchLinux [16:39] timothy: can you check if that still happens with latest snapd? [16:48] zyga: I had to reboot with apparmor kernel [16:48] sergiusens: is there a way to make an exception for a snapcraft integration test to allow network access? [16:52] timothy: no rush, if you can please add this to the bug report [16:52] timothy: how is arch btw? [16:52] where can one find detailed descriptions of interfaces? [16:53] http://snapcraft.io/docs/reference/interfaces is a good list [16:53] timothy: I didn't do much cross distro work lately and when I did I was stuck on fedora and selinux [16:53] but it has no details/example of how to use those [16:54] seb128: only in the code for now, I've added one page to the wiki to describe the content interface, I want to do this for all interfaces: https://github.com/snapcore/snapd/wiki/Content-Interface [16:54] seb128: (I actually didn't link it from the main list of interfaces yet) [16:55] seb128: it's a wiki though so editors welcome, if you have a specific interface we could work on documenting it [16:56] tyhicks, jdstrand: could you guys have a look at https://github.com/snapcore/snap-confine/pull/188 [16:56] PR snap-confine#188: Add apparmor support module [16:56] zyga, wooot, the content interface was the one I was after so thanks for that ;-) [16:56] seb128: :D my pleasure, feedback welcome, this is my first edit on the wiki [16:56] k, will do [16:56] how does one add a new group on snappy? [16:57] wxl: you mean system group? [16:57] wxl: that's not supported yet [16:57] fooey [16:57] i found an lxd beta snap but it doesn't seem to add the lxd group [16:57] wxl: but we have some plans to do that, many daemons would like that [16:57] mvo: ^ did we add lxd hack to snapd? [16:59] hack ? i thought the hacks were gone [16:59] :P [16:59] iirc you need to manually call addgroup if you use the snap on a core image [16:59] zyga: I see Fedora uses /var/ directory instead of /snap, did you create a migrate procedure? [16:59] (with the --extrausers option) [17:00] timothy: no, we decided not to, [17:00] timothy: we didn't publish any packages that use that yet either because of confinement issues [17:00] * zyga jumps into a call [17:01] zyga: usually someone manually pings me are adds @jdstrand. this is not great and I'd want to tie changes to interfaces/ (for example) to be tagged in some way [17:01] ogra_: --extrausers is a snap option? [17:01] wxl, nope ... passwd/adduser etc [17:01] zyga: ie, do for interfaces what we do for snap-confine [17:01] oh right, so you're talking about building the snap then [17:02] nope about the core image [17:02] oh [17:02] even worse XD [17:03] zyga, it's a bit confusing in the examples to have the same word used for slots/plugs names and as an attribute [17:05] slangasek: hey, do you have the time to attend the gadget call now? [17:05] seb128: aha, thanks, I'll see if I can change that or make it more obviou [17:05] ogra_: i was sure hoping that core→snap juju/lxd→juju deploy mysql/wordpress would do the trick, but i guess i'm still a bit ahead of my time [17:05] zyga, yw :-) [17:12] zyga, hum, also is it required to have a "interface: content"? your example doesn't have it [17:23] Bug #1639952 opened: When running in unity8 desktop snap, snap application icons aren't found in app scope [17:26] attente integration tests do have network access, unit tests do not (those are also run on package build which is networkless) [17:31] slangasek: can you point me to the official branch? [17:34] slangasek: there were some more commits on the vorlon one AFAIK [17:39] seb128: interface: content? [17:39] * zyga looks [17:39] zyga (cc jdstrand): I'm in the middle of reviewing snap-confine PR 188 [17:40] tyhicks: thanks! [17:41] zyga, well other examples I found have an "interface: content" line, I guess it needs to know what interface to use? [17:41] Bug # changed: 1617250, 1617251, 1617264, 1617278 [17:42] seb128: is "interface" there an attribute? [17:42] seb128: of a plug or a slot? [17:42] seb128: that attribute doesn't mean anything, we only look at "content" [17:42] * zyga triple checks [17:43] zyga, I don't know, that thing is undocumented, I'm basing my comment on the read of http://askubuntu.com/questions/841004/cannot-get-basic-content-interface-example-working-with-snapcraft [17:44] ah [17:44] seb128: "interface: content" is required when the interface itself is not named "content" [17:44] oh [17:44] seb128: the plug / slot name can be anything [17:44] k [17:44] Bug #1617770 changed: Snap cannot exec tput [17:44] seb128: but we create an implicit "interface: $PLUG_OR_SLOT_NAME" [17:44] some more magic ;-) [17:44] seb128: so when things all match is shorter and more magic [17:44] good to know [17:44] thanks zyga [17:45] seb128: I'll document that, thanks for pointing that out! [17:47] ogra_, slangasek: can you confirm that [17:47] http://bazaar.launchpad.net/~snappy-dev/snappy-hub/snappy-systems [17:48] is the place that has all the commits [17:48] yep [17:48] thanks! [17:49] PR snapd#2356 closed: cmd/snap: have some completers [17:50] zyga, thanks! [17:50] Bug #1619455 changed: classic does not work with connsole-conf created user [17:55] ogra_: the latest commit there is [17:55] timestamp: Fri 2016-10-28 13:06:29 +0200 [17:55] ah, 2016, I read that like 2015 [17:55] sorry :) [17:55] heh [17:55] no, i bumped the dragonboard last ... right before release [17:55] adding a second console= kernel option like on all other arches [17:59] Bug #1617232 changed: subiquity goes into endless configuration loop, no way to get out [18:05] jdstrand, zyga: are you ok with me proposing pull requests with stacked commits? or do you want me todo them as standalone commits? [18:05] happy todo either [18:05] jamespage: to snap-confine? [18:05] to snapd [18:06] jamespage: in snapd we don't do squashing, so more commits is fine [18:06] ogra_: this is the first one [18:06] slangasek: ^^ [18:06] https://github.com/snapcore/pi2 [18:07] looks good [18:07] ogra_: no tags? [18:07] PR snapd#2378 opened: Openvswitch interface [18:07] nope [18:07] ah, no tags in bzr either, ok [18:09] dunno if we want to start to have two branches (one for edge, one that migrates through beta->canididate->stable, for the second one i'd use tags [18:10] slangasek: master == edge [18:10] er [18:10] ogra_: ^^ [18:10] ogra_: I think the rest is up to you [18:10] yeah, thats what we did in the past [18:11] ogra_: you can also work with QA on this [18:11] i just dont know if we want to kkeep that setup [18:11] i'd actually like to have a "go wild" branch for edge [18:11] where you can try out the evil stuff without harming the branch that gos later into stable [18:11] *goes [18:12] ogra_: I think those are pull requests [18:12] ogra_: if we set this right, pull requests can even go to named channels [18:12] PR snapcraft#933 opened: _filedir takes an extension, not a glob [18:13] you mean a PR would land in edge so you can trigger an img build from it ? [18:18] PR snapd#2376 closed: docs: document SNAP_DEBUG_HTTP in HACKING.md [18:19] ogra_, no, a PR would land in its own custom channel [18:19] "here, try this bugfix" [18:19] kyrofa, right ... not what i want [18:20] kyrofa, i want to land a fix and have it show up in tomorrows daily img without me doing anything [18:20] (or land "the test of a fix" ... this is edge ... that is what it is for) [18:21] ogra_: that's edge [18:21] right [18:21] ogra_: but even before you land someone's PR you can use a branch channel [18:21] ogra_: and try that out [18:21] why would i ? [18:22] sounds like we'd have a lot fragementation then [18:22] ogra_: you see a pull request, you do code review, you check that on a real device with a channel switch [18:22] ogra_, right, reading more backlog your use-case isn't the custom channels thing. You just want a branch essentially assigned to edge [18:22] That doesn't necessarily get merged into anything more stable [18:23] zyga, how does a channel switch help me with some initial boot stuff (i.e. gadget) [18:23] ogra_: you switch and reboot [18:23] i need an imag to dd [18:23] ogra_: no [18:23] ogra_: you switch and reboot :) [18:23] ogra_: maybe with a helper to wipe first-boot logic [18:23] gadgets very very rarely have anything that helps via a channel switch [18:24] ogra_: if that doesn't do enough it's a bug in snapd, eventually that should be enough [18:24] usually fixes are in the firstboot area etc [18:25] anyway ... whatever works ... [18:34] jdstrand, tyhicks: https://github.com/snapcore/snap-confine/pull/195/files [18:34] PR snap-confine#195: Fix creation of $XDG_RUNTIME_DIR and $SNAP_USER_DATA [18:35] I'm still going to add more unit tests and spread tests for this [18:35] for $SNAP_USER_DATA [18:35] and for chown logic (unit tests) [18:35] and for the hint callback [18:35] but have a look please for the overall aproach [18:35] approach* [18:48] slangasek: I did all the repos, look at github please [18:48] slangasek: I'll do all the launchpad repos next (I did pi2 as launchpad.net/snap-pi2) [18:48] slangasek: and I'll work on snapcraft.yaml's [18:48] slangasek: and publication to edge [18:49] but now, some time for my son, ttyl [19:13] jdstrand: were you the person that pmcgowan talked to about policykit in the unity8-session snap? I wanted to discuss that a bit [19:14] Specifically the suggestion to just bundle polkitd. One problem with that is that we'd need to patch policykit to get rid of the setuid requirement for the libpolkit agent helper. Which you security folks might not be thrilled with [19:15] mterry: I'm working on a response to that bug. it is quite a complicated prospect overall [19:15] jdstrand: ok cool we can talk in the bug [19:15] mterry: as for the setuid bit, why is it setuid? [19:16] jdstrand: I don't know? /usr/lib/policykit-1/polkit-agent-helper-1 is setuid and last time I looked, I think it verifies that setuid is set? Maybe I'm wrong that it verifies, and we could try faking it... [19:17] mterry: also, it is possible to ship a snap with a setuid binary. it will fail review, but there is a way to override that [19:17] jdstrand: not my favorite path but sure :) [19:20] mterry: from the security team notes: http://paste.ubuntu.com/23554639/ [19:22] seems it is only needed for password prompts. since iirc Touch didn't have any of those, you could probably skip it. But you'd need to be sure to undo this once you added password prompts [19:23] jdstrand: well we only don't have password prompts in Touch because we added a lot of polkit policy files that said "don't ask for a password if the phablet user makes this call" [19:23] I'm not sure we want to go down that route again [19:27] mterry: that's a fair observation. I commented in the bug [19:38] mterry: you might refresh-- I made two more comments [19:40] jdstrand: guh I don't like supporting both classic and all-snap in one :( [19:40] I would imagine you wouldn't [19:40] :) [19:40] :) [19:41] jdstrand: it might be a better use of eng resources on my side to not implement any of the workarounds until a bit more guidance comes from you snappy folks -- u8 isn't broken without this, we just can't install more snaps through the ui. But I'll leave that to product folks to decide [19:42] let me put that in the bug [19:43] mterry: note, I'm not tasked with this. like you, would need product folks to bubble that up. it probably isn't on the snappy team's radar either, so that stakeholder meeting would need to include Ja mieBennett, rat liff and whoever from your side and product [19:44] jdstrand: got it. Thanks for the comments! [19:44] np! [19:45] Bug #1645841 opened: Separate Signature Keys topic from Image Building flow [20:07] zyga: fyi, https://github.com/snapcore/snapd/pull/2366#discussion_r90101320 [20:07] PR snapd#2366: interfaces: apparmor support for classic confinement [20:39] Bug #1559248 changed: Support unversioned data directory (i.e. data shared between versions) [21:54] PR snapcraft#934 opened: Migrate from xdelta to xdelta3 [22:01] jdstrand: thanks, checking === greyback|afk is now known as greyback [22:03] PR snapcraft#935 opened: Utilize MakePlugin build logic within CMakePlugin. (LP: #1645853) === IznogooD is now known as izzno