/srv/irclogs.ubuntu.com/2016/09/19/#snappy.txt

=== chihchun_afk is now known as chihchun
mwhudsonmcphail: according to the mailing list it's supposed to be $SNAP_USER_COMMON but it doesn't work right now01:47
mwhudsonmcphail: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/161106301:48
mupBug #1611063: can't mkdir SNAP_USER_COMMON directory <snapd-interface> <Snappy:Triaged> <snapd (Ubuntu):Triaged> <https://launchpad.net/bugs/1611063>01:48
notadeveloperis video acceleration available in snappy01:48
mupBug #1624963 opened: pulseaudio interface (still) missing permissions <Snappy:New> <https://launchpad.net/bugs/1624963>02:06
=== JanC is now known as Guest19696
=== JanC_ is now known as JanC
mupPR snapd#1939 opened: Update documentation on testing snapd <Created by robert-ancell> <https://github.com/snapcore/snapd/pull/1939>03:23
mupBug #1602752 changed: Add support for timezone-read interface <snapd-interface> <Snappy:Expired> <https://launchpad.net/bugs/1602752>04:19
mupPR snapd#1939 closed: Update documentation on testing snapd <Created by robert-ancell> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/1939>05:39
=== chihchun_afk is now known as chihchun
mupPR snapd#1937 closed: image: ensure local snaps are put last in seed.yaml  <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/1937>06:32
mcphailmwhudson: thanks!06:37
dholbachhey hey06:50
stubWhen I say 'Snap Store' in my documentation, what URL should I be linking to?06:58
mupPR snapd#1938 closed: asserts: check that validation assertions are signed by the publisher of the gating snap <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/1938>07:28
mupPR snapd#1940 opened: asserts: define a bit less terse Ref.String <Created by pedronis> <https://github.com/snapcore/snapd/pull/1940>07:36
zygamwhudson: hey :)07:48
zygamwhudson: I'll work on release today :) happy to finally reach this point07:48
mupPR snapd#1932 closed: add HACKING.md and move content from README.md over <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/1932>07:56
zygajdstrand, tyhicks: https://github.com/snapcore/snap-confine/pull/14708:17
mupPR snap-confine#147: Implement secure_getenv(3) if not provided by stdlib <Created by zyga> <https://github.com/snapcore/snap-confine/pull/147>08:17
zygalool: https://github.com/snapcore/snap-confine/pull/14708:19
mupPR snap-confine#147: Implement secure_getenv(3) if not provided by stdlib <Created by zyga> <https://github.com/snapcore/snap-confine/pull/147>08:19
mwhudsonzyga: oh yeah, you'll need to find a DD to do the thing that lets you upload the package08:22
zygamwhudson: I need to refresh my memory on the process08:23
zygamwhudson: I'll do a sdist release without tagging as soon as 147 lands and do a round of packaging and distro testing08:23
zygamwhudson: then officially tag and start pushing downstream08:24
mwhudsonzyga: https://wiki.debian.org/DebianMaintainer#Granting_Permissions08:24
mwhudsonzyga: sounds good08:24
zygathank you!08:24
mupPR snapd#1920 closed: --lazy is only available with -l in trusty <Created by vosst> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/1920>08:27
mupPR snapd#1873 closed: interfaces: disable auto-connect in libvirt interface <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/1873>08:39
mupPR snapd#1940 closed: asserts: define a bit less terse Ref.String <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/1940>08:39
=== seb128_ is now known as seb128
ogra_cjwatson, looks like LP tries to upload the .manifest files now (thanks for publishing them !) ... i got mails from tonights auto-builds: " __all__: The upload does not appear to be a valid package."08:53
ogra_mvo, could you approve https://myapps.developer.ubuntu.com/dev/click-apps/5912/rev/3/ ? and give me upload access to the beagleblack gadget (i have a working beagle image here)08:56
mvoogra_: we probably need to republish the beaglblack under a different publisher, e.g. beagleblack.ogra ? or just beagle.ogra or something08:59
ogra_mvo, ok, i can do that09:00
mvoogra_: great, thank you09:00
=== vrruiz_ is now known as rvr
loolzyga: thanks for adding secure_getenv; wanted to do it over the week-end but ended up debugging other things09:04
zygamatteo: hey09:13
matteohi zyga09:13
zygamatteo: would you mind doing a quick test build of snap-confine from this branch https://github.com/snapcore/snap-confine/pull/147/files09:13
mupPR snap-confine#147: Implement secure_getenv(3) if not provided by stdlib <Created by zyga> <https://github.com/snapcore/snap-confine/pull/147>09:13
zygamatteo: I will do a release shortly, I just want to make sure it works outside of glibc09:13
matteoyou mean with MUSL?09:14
zygayes09:15
matteoI'm using glibc on OpenWrt, but I can rebuild the toolchain09:19
zygamatteo: hmm, I thought that openwrt used musl09:21
zygalool: ^ where did you end up using musl?09:21
matteosure, by default09:21
loolzyga: I can do a build with musl09:21
matteobut I switched to glibc to be sure that it works09:21
loolafter lunch09:21
zygalool: thanks09:22
zygamatteo: I see, thanks09:22
zygamatteo: I guess lool will do the check09:22
matteozyga: I didn't want to add extra entropy to the system :D09:22
zygahehe :)09:22
zygais openwrt ususally using musl?09:22
timothyopenwrt can also use uclibc09:24
ogra_mwhudson, in bug 1624329 i dont want you to fix firstboot ... thats mvo's job i guess :) but i want the network device to work after i plugged in a cable (it doesnt, even if i cancel console-conf to have it start over from scratch)09:24
mupBug #1624329: snapd firstboot setup fails constantly when rebooting before console-conf has finished <Snappy:New> <snapd (Ubuntu):New> <subiquity (Ubuntu):New> <https://launchpad.net/bugs/1624329>09:24
mwhudsonogra_: that's super odd09:25
mwhudson(the device not appearing)09:25
matteotimothy: time ago, now it's dropped it for most architectures09:25
timothyyou can still choose it from make menuconfig09:25
matteoit's the default on archs unsupported by MUSL09:26
mwhudsonogra_: to get the devices it just does (roughly) pyudev.Context().list_devices(subsystem='net')09:26
ogra_it appears but i cant configure it09:26
mwhudsonogra_: there's nothing cached between invocations...09:26
matteoyes, you can choose it if you really like broken C libraries09:26
ogra_weird09:26
mwhudsonogra_: i finally dug my dragonboard out today so i can experience some of your pain more faithfully tomorrow :)09:26
ogra_hah, great09:27
ogra_i'm just playing with a beaglebone image here ... thats even more odd09:27
mwhudsoni have a pile of hardware that i think strictly speaking belongs to linaro09:27
mwhudsona panda, beagleboard xm, arndale09:27
ogra_(beautiful oopses on boot and no network device at all ... )09:27
ogra_(on second boot all is fine ... but then firstboot is already in a wonky state)09:28
mwhudsonogra_: how do you connect to dragonboard serial?09:29
mwhudsoni have a fdti thing but i never got it to work09:29
ogra_with the mezzanine board that got shipped along :P09:29
mwhudsonah heh clearly i bought mine too early09:29
ogra_well, the company bought mine09:30
mwhudsonwell yes, mine too09:30
mwhudsonbut it was before that sort of thing was available09:30
mwhudsonogra_: this one? https://www.seeedstudio.com/96Boards-UART-p-2525.html09:31
ogra_yep09:31
zygamwhudson: it's fiddly09:32
zygamwhudson: I had mine but it's easy to make it not work09:32
zygamwhudson: as a quick test, check if the daughter board works by itself09:32
zygamwhudson: I also found that the board has to be aligned properly vertically, it can easily bend back and forth and this makes the connection fail09:33
mwhudsonzyga: can't possibly be more fiddly than the http://www.digikey.co.nz/product-detail/en/ftdi-future-technology-devices-international-ltd/TTL-232RG-VIP-WE/768-1069-ND/2441358 i was trying to use before09:34
ogra_mvo, http://paste.ubuntu.com/23202066/ ... could we make the firstboot service run after console-conf somehow ?09:34
zygamwhudson: heh, well, you can always use those simple ftdi cables with female connectors09:35
mwhudsonogra_: that's netplan segfaulting?09:35
mwhudsonzyga: ?09:35
ogra_mwhudson, thats a kernel oops of the NIC ... my prob is that firstboot is from then on broken, even if i have a boot without oops09:38
zygamwhudson: a usb serial from ftdi where each connector is a separate cable with female connector, just plug those over and it should work09:38
zygamwhudson: (just make sure not to fry the board)09:38
mwhudsonzyga: huh i didn't see that one when i was looking ~15 months ago09:38
mwhudsonanyway i'll try the one i have and order a mezzanine if i can't make it work09:38
zygamwhudson: http://www.aliexpress.com/store/product/USB-to-TTL-Serial-Cable-Adapter-FTDI-Chipset-PL2303HX-USB-Cable-Computer-Cable/1180713_1889042442.html09:38
zygamwhudson: something like this09:38
mvoogra_: hm, that would make sense, this way we have ntp hopefully09:38
mwhudsonzyga: the dragonboards connectors are themselves female aren't they?09:38
zygahmmm, are they? sorry I don't have one in front of me09:38
zyga(there are male variants of the thing as well)09:38
ogra_mvo, well, i dont care that much about ntp ... more about having network at all09:38
ogra_ppisati_, http://paste.ubuntu.com/23202086/ ... beaglebone (with linux-generic xenial)09:39
ppisati_cking: ogra_ :O09:42
ppisati_ops09:42
ppisati_ogra_: :O09:42
ogra_yeah :/09:42
cking?!09:42
ogra_i blame pitti .... netplan tries to start the network :)09:42
ppisati_ogra_: yeah, put the blame on pitti09:42
ogra_hehe09:42
ogra_let me build a public image so you can tinker with it09:42
ppisati_ogra_: ta09:42
ogra_(gimme 10-15min)09:42
ppisati_ogra_: is that a beaglebone black?09:42
ogra_yep09:42
ppisati_k09:42
ogra_with 4.4.0-36-generic09:42
ogra_it works better on subsequent boots btw ... on first boot i always get the oops, reliably ... on subsequent ones it only happens very random09:43
ppisati_weird09:44
ogra_yep09:44
ogra_ppisati_, http://people.canonical.com/~ogra/snappy/all-snaps/daily/current/ has the beagle image now09:56
mupPR snapd#1941 opened: interfaces/builtin: allow mmaping pulseaudio buffers <Created by zyga> <https://github.com/snapcore/snapd/pull/1941>09:58
ppisati_ogra_: cool, i'll give it a spin10:00
ogra_mvo, hmm, looks like it would just help if firstboot.go wouldnt create an empty state.json file when there is no network ...10:03
ogra_mvo, if i do: "sudo rm /var/lib/snapd/state.json && sudo systemctl restart snapd.firstboot.service && sudo reboot" it works fine10:04
cjwatsonogra_: Hm, that exact message doesn't appear in the LP source tree.  URL to the failing build?10:04
ogra_i have four of them ... one sec ...10:05
ogra_https://launchpad.net/~snappy-dev/+snap/ubuntu-core/+build/510910:05
mvoogra_: yeah, three are some easy wins here10:05
ogra_equally 5107, 5108 and 511010:05
cjwatsonogra_: Ah, right.  Please file a bug against LP itself - we'll need to be more selective about which files we upload to the store10:07
ogra_cjwatson, yep ... it is blocking all upload apart from ppc64el and s390x now it seems ... i assume these two dont generate manifests10:10
ogra_*uploads10:10
cjwatsonogra_: Dropping the manifest temporarily will work around it.10:10
ogra_k10:10
cjwatsonogra_: But I should be able to fix it reasonably quickly.10:10
ogra_thats good enough :)10:11
ogra_ok10:11
ogra_cjwatson, Bug #1625117 for you10:26
mupBug #1625117: store uploads fail since os snaps publish manifest files <Launchpad itself:New> <https://launchpad.net/bugs/1625117>10:26
cjwatsonTa10:27
mupPR snapd#1942 opened: Initial support for download deltas (via SNAPPY_DELTA_DOWNLOAD_FORMATS) <Created by absoludity> <https://github.com/snapcore/snapd/pull/1942>10:33
=== hikiko is now known as hikiko|ln
mupPR snapd#1943 opened: wrappers: add new X-Snap-Exec=$snap.$app support to .desktop files <Created by mvo5> <https://github.com/snapcore/snapd/pull/1943>10:54
mvoseb128: https://github.com/snapcore/snapd/pull/1943 this is what you asked for last week, right?10:55
mupPR snapd#1943: wrappers: add new X-Snap-Exec=$snap.$app support to .desktop files <Created by mvo5> <https://github.com/snapcore/snapd/pull/1943>10:55
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
mectorshow do I use the content plug to allow a snap to read the directory /root/.certs/?11:42
ogra_you would need a snap that provides /root i guess (no, thats not possible)11:43
ogra_and i doubt you will have any access to "dot" dirs anyway ...11:43
mectorsogra: thanks11:52
=== hikiko|ln is now known as hikiko
mectorsogra: how do I execute a script to change a file so I can rewrite the directories?12:06
mectorsbasically execute a sed s/root/$SNAP_DATA/12:08
=== chihchun is now known as chihchun_afk
ogra_mectors, i'D use a wrapper script12:13
morphis_niemeyer: was about to try the spread snap, how is that supposed to work for local backends like kvm or lxd?12:35
morphis_getting errors like: 2016/09/19 14:33:36 Cannot allocate qemu:ubuntu-16.04: cannot launch qemu qemu:ubuntu-16.04: exec: "kvm": executable file not found in $PATH12:36
mectorsogra: how does a wrapper script work?12:37
tenaciousmvhi. I'm trying to get the nodejs-plugin-based shout demo working: https://github.com/snapcore/snapcraft/tree/master/demos/shout   when I build and install it locally, i don't see anything in /snap/bin afterward12:44
tenaciousmvbut when i run `snap install shout` instead it works12:44
tenaciousmvi used --force-dangerous for the local install12:45
tenaciousmvsnapcraft v 2.1712:45
ogra_mectors, https://github.com/ogra1/laidout ... look at snapcraft.yaml and wrapper.sh there ... thats a very simple wrapper script12:46
mectorsogra: thanks12:47
fearingfound this in my history just seeing what this is12:57
zygajdstrand: hello12:58
ogra_ppisati_, btw, bug 162517712:58
mupBug #1625177: OOPS on beaglebone on boot of 4.4.0-36-generic under snappy ubuntu core xenial <linux (Ubuntu):New> <https://launchpad.net/bugs/1625177>12:58
jdstrandzyga: hi!12:58
zygajdstrand: hey, I merged secure_getenv improvement, I noticed your NAK in the morning12:59
zygajdstrand: I'd appreciate a post-merge review of this 3 line function12:59
zygajdstrand: just to be on the safe side :)12:59
zygajdstrand: I'd like to file the bugs for apparmor issues we found last week13:00
zygajdstrand: do you have a preference? is launchpad oka?13:00
sergiusenscan't you just command do `command: desktop-launch $SNAP/usr/bin/laidout "$@"`?13:02
sergiusenserr, without the $@13:02
ogra_sergiusens, yeah, that snap is super old ... from a time where the desktop-launcher stuff was still in development13:03
ogra_and it was only a proof of concept to show someone that i can make a snap from an upstream binary in less than 10min13:03
jdstrandzyga: thanks for fixing that. I'll take a look. I filled the apparmor bug already13:03
* jdstrand looks for it13:03
ogra_sergiusens, effectively the wrapper is nonsense there ... at least nowadays (and i doubt with the new laucnehrs it wouldnt even build anymore)13:04
jdstrandzyga: https://bugs.launchpad.net/apparmor/+bug/162449713:04
mupBug #1624497: complain mode blocks access to nsfs (/proc/self/ns/*) without exec rule <AppArmor:Confirmed> <https://launchpad.net/bugs/1624497>13:04
sergiusenszyga are you aware of any missing interface work to get tray icons to work? My telegram snap has the forbidden icon since forever and I know that kyrofa has some snaps in that state too13:09
zygasergiusens: no, is there a bug report for this somewhere?13:10
zygasergiusens: I'll check out your snap later today so that I can perhaps see this myseld13:10
sergiusenszyga hmm, kyrofa or seb128 I guess would know13:11
seb128sergiusens, zyga, could be bug #160013613:13
mupBug #1600136: App indicator does not show icon for Qt apps <snap-desktop-issue> <Snappy:New> <snapd (Ubuntu):Confirmed> <https://launchpad.net/bugs/1600136>13:13
seb128it's trying to use /tmp to share the icon13:13
didrockssergiusens: that's what we discussed during the heidelberg sprint (and the bug seb128 referenced). Main issue is this /tmp thing in appmenu-qt13:14
zygajdstrand: one tiny unrelated issue, the base profile doesn't allow xdg-open13:17
zygajdstrand: and the executable in the core snap (which is probably out of date anyway) is in /usr/local13:17
zygajdstrand: I was thinking about adding it to the main template13:18
zygajdstrand: to /usr/bin/xdg-open xi,13:18
jdstrandzyga: I would think that the unity7 interface would make more sense. it is only for desktop applications, no?13:19
zygajdstrand: well, I don't know13:19
zygajdstrand: perhaps13:19
zygajdstrand: though at the same time, I don't know13:19
jdstrand"xdg-open is for use inside a desktop session only. It is not recommended to use xdg-open as root."13:19
jdstrandfrom it's man page13:20
zygajdstrand: in any case we need to have it somewhere and document it13:20
jdstrandplease use unity7 for now. we can move it to default if required, but I don't think we will13:20
jdstrandalso, yeah, moving out of /usr/local would be good too13:20
jdstrandI'm not sure how that would work on an actual desktop though...13:21
zygajdstrand: on the desktop there's snapd-xdg-open13:21
zygajdstrand: we need to keep things in sync as AFAIK they drifted apart now13:21
zygajdstrand: I'll try to untangle it13:21
jdstrandwell, now I'm confused13:21
jdstrandok, so snapd-xdg-open is what snapd provides, not xdg-open?13:22
didrocksjdstrand: snapd-xdg-open is the service on the desktop side answering to our fake xdg-open requests over dbus13:24
didrocks(and snapd-xdg-open calls the real xdg-open on the desktop)13:24
jdstrandso why is zyga requesting we add xdg-open to the policy?13:24
ogra_there is one xdg-open *inside* the ubuntu-core snap ... thats the one in /usr/local ... on the desktop side there is /usr/lib/x86_64-linux-gnu/snapd-xdg-open which (as i understand) is supposed to talk to the oone inside the snap13:24
ogra_and this is all along with the default xdg-open you have installed on a desktop anyway13:25
jdstrandshouldn't the one in /usr/local go away then?13:25
jdstrand(in the all snaps image)13:26
ogra_well, it should surely move to /usr/bin13:26
seb128that one is our small wrapper doing the dbus call13:26
zygajdstrand: yes13:26
jdstrandand people just use snapd-xdg-open?13:26
zygajdstrand: I don't know how it managed to get there TBH13:26
seb128snapd-xdg-open is on the host13:26
seb128not in the snap13:26
zygajdstrand: no, people use xdg-open13:26
jdstrandman, this is confusing13:26
ogra_ah, well, i dont know if snapd-xdg-open? doesnt need the one inside the snaps13:26
zygajdstrand: that talks to snapd-xdg-open in the distro13:26
seb128that's the service listening to the dbus call13:26
jdstrandso on all snaps, we call it xdg-open, but it is really a wrapper. on desktop it is snapd-xdg-open cause the real xdg-open is not snapd-xdg-open13:26
jdstrandlet's back up13:27
seb128can't parse that13:27
jdstrandwhat are snaps supposed to use?13:27
seb128define snaps?13:27
zygano, it works the same way everywhere13:27
zygaor actually13:27
zygano13:27
jdstranda snap of type: app13:27
seb128you mean what is a desktop snapped app supposed to use?13:27
didrocksjdstrand: you basically have: xdg-open (fake, in /usr/local), called by the snap app <------ dbus --------> snapd-xdg-open (service, activated by fake /usr/local) which execs real xdg-open13:27
zygaon classic the core snap has 'xdg-open' that talks over dbus to snapd-xdg-open13:27
didrocksthe first one is inside the snap/ubuntu-core13:27
didrocksthe second part of the array is on the destkop13:28
ogra_zyga, http://paste.ubuntu.com/23202842/  ... its a buuld time hack13:28
ogra_*build13:28
seb128didrocks, to be exact that uses gio and doesn't execs the real xdg-open ;-)13:28
jdstrandwith didrocks explanation, why do we need to add anything to the policy-- the xdg-open that talks to snapd-xdg-open is in the snap13:28
didrocksseb128: indeed, to keep the service running :) :p13:29
seb128well apparently snapd denies /usr/local/xdg-open to be exec13:29
jdstrandseb128: what is the system /usr/local/xdg-open supposed to be used by?13:29
seb128random code13:30
jdstrandto do what?13:30
seb128open an url13:30
ogra_/usr/local/bin/xdg-open FWIW :)13:30
jdstrandmeh13:30
seb128random admin script, desktop apps, command line apps do "xdg-open http:...."13:30
jdstrandI'm not trying to be obtuse, I'm trying to be very specific. there are several things called xdg-open. zyga wants to adjust the policy. I want to know how the pieces fit together13:31
seb128we also associate that wrapper with "http:"13:31
didrocksfor instance, Qt openUrl() is wrapping qtsubprocess.call("xdg-open url") (or whatever is the correct syntax)13:31
seb128jdstrand, http://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk/view/head:/live-build/ubuntu-core/hooks/500-create-xdg-wrapper.binary13:31
jdstrandseb128: so why wouldn't that snap ship xdg-open like snaps on classic do?13:31
seb128code might be easier than words13:31
jdstrandbut that is on classic13:31
ogra_that is why i posted it above :P13:31
=== petevg is now known as petevg_afk
seb128I don't understand that question13:31
seb128that wrapper is part of the ubuntu-core image13:31
seb128why would snap need to ship it?13:32
jdstrandlook13:32
didrocksseb128: I think jdstrand is asking, why aren't we asking every snap app using xdg-open to ship it as part of the code13:32
seb128because it's easier to have it in the base image?13:32
jdstrandI understnad what snappy's xdg-open is supposed to do. I'm trying to reconcile classic and all snaps13:32
didrocksjdstrand: am I right on your question? ^13:32
jdstranddidrocks: you are13:32
didrocksI think shipping it on runtime snaps might make sense13:33
jdstrandand if it is right to be in the base image, why are we doing things different between classic and all snaps?13:33
didrocksas the usage of xdg-open is often by the toolkit13:33
didrocksnot directly or in a awareness-way by the app13:33
seb128that's not true13:33
seb128if you look on codesearch.debian.net you can see it's used by stack of random command line tools13:33
seb128like mutt13:33
seb128or mc13:33
seb128or backup script things13:34
didrocksyeah, cli ones might do it…13:34
jdstrandwhat is interesting about xdg-open on all snaps is there is no desktop by default13:34
jdstrandso shipping it is kinda weird13:34
seb128doesn't need to be a desktop for it to work13:34
seb128it's just a wrapper to call the appropriate handle13:34
seb128that could be links13:34
jdstrandthe man page for xdg-open says it needs to run in a desktop session13:35
seb128we are not using xdg-open though13:35
jdstrandbut we are meant to replace it13:35
seb128we are diverting the command to call our handler that opens a browser13:35
jdstrandand a browser isn't on all snaps13:35
sergiusensdidrocks seb128 thanks13:36
seb128how is "open an url" supposed to work on all snaps?13:36
jdstrandthat's a great question13:36
jdstrandI don't think anyone defined that13:36
ogra_yeah, thats future work13:36
jdstrand(which is what I'm really getting at)13:36
seb128can we get the cheap trick we currently have to work then?13:37
seb128until that proper job is done13:37
jdstrandhow would it work?13:37
seb128on classic I mean13:37
jdstrandyou call xdg-open and nothing happens13:37
zygajdstrand: (offtopic): https://github.com/snapcore/snapd/pull/194113:37
mupPR snapd#1941: interfaces/builtin: allow mmaping pulseaudio buffers <Created by zyga> <https://github.com/snapcore/snapd/pull/1941>13:37
seb128well what we currently have would make urls work on classic13:37
seb128if snap-confine wasn't blocking the xdg-open exec13:37
jdstrandseb128: yes, of cousre we want it on classic. which is why I suggested unity7, but then didrocks said that snaps on classic should ship it13:38
zyga(that's snapd, snap-confine just does what it is told to do)13:38
jdstrandseb128: which brings us full circle-- why do we need to allow it in the policy if apps are meant to ship it13:38
zygajdstrand: we don't want snaps on classic to ship xdg-open13:38
seb128I disagree with having every app to ship it13:38
didrocksI didn't say that, I said if we don't want to ship it on ubuntu core snap, maybe having it as part of the toolkit makes sense13:38
zygajdstrand: because then we are stuck with the interface forever13:38
didrocksbut seb128 has some good arguments about cli apps13:39
* jdstrand doesn't care where it is shipped-- just trying to find the right place13:39
jdstrand/usr/local is not the right place btw13:39
jdstrandthat is for admins, not system installed software13:39
didrocksI think attente shipped it there because he didn't want to conflict in case we have a "personal snap" shipping the system version13:40
seb128that's also where we have you fake "apt" that tells you that apt is not supported13:40
didrocksbut my memory could be skewed :)13:40
didrocksand good point seb128 ;)13:40
seb128you->our13:40
jdstrandthat is an abuse of /usr/local13:40
seb128but the reason is probably what did said13:40
jdstrandanyway13:40
seb128I'm not going to discuss that, it was not my doing but mvo's13:41
seb128I'm happy for it to change location13:41
mvojdstrand: /usr/local/bin/{apt,xdg-open} should change location? sure13:42
jdstrandthat's kinda a side discussion, but it did add to my confusion13:43
seb128so summary is13:44
jdstrandfyi, nothing in snap-confine mounts /usr/local from the os for classic for that to work anyway (afaics)13:44
seb128well, that dir is part of ubuntu-core13:45
seb128I didn't try in recent weeks but the fake "apt" command was in the snaps last time I tried13:45
jdstrandit is. I'm thinking through what should be done13:45
seb128so the ubuntu-core /usr/local/bin was available inside the snaps13:45
ogra_but is it in PATH ?13:45
seb128yes13:45
jdstrandI guess it probably should be in the core snap, but since nothing in all snaps uses it, that makes me slightly uncomfortable, but I guess there is nothing better that can be done13:46
jdstrandespecially if there is defined future work for making it work on all snaps13:47
jdstrandso for now, leaving it in the core snap (but please move it to /usr/bin so we are using the correct locations and for avoiding confusion in the future) and add '/usr/bin/xdg-open ixr,' to the unity7 interface makes the most sense. at least that way if someone on all snaps tries to use it we are suggesting that it isn't supported yet13:48
jdstrandthat's my opinion. does that make sense to others? ^ (seb128, didrocks, zyga, mvo)13:49
seb128jdstrand, that wfm, though it's a crossdesktop thing and used by command line tools often so unsure unity7 is the right interface13:50
seb128jdstrand, like mutt would probably end up using it to open an url13:51
seb128unsure how much of a big hammer it is to recommend those to use unity713:51
jdstrandseb128: because today the thing it is replacing is documented as requiring a desktop session and because we haven't defined what it should look like without a desktop session13:51
seb128right, it should need one13:52
jdstrandwhen we do, it can be moved/added to somewhere else, perhaps the default policy13:52
seb128but unity7 give you quite some things13:52
seb128but I guess fair enough for now13:52
jdstrandit could be a separate interface13:52
jdstrandI'm uncomfortable adding it to the default policy because it requires dbus13:53
mupPR snapd#1941 closed: interfaces/builtin: allow mmaping pulseaudio buffers <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/1941>13:53
seb128I see13:53
didrocksjdstrand: wfm as well13:53
seb128well unity7 should do for now13:53
mupPR snapd#1944 opened: many: validate refreshes against validation assertions by gating snaps <Created by pedronis> <https://github.com/snapcore/snapd/pull/1944>13:54
jdstrandzyga: so, sounds like adding it to unity7 is the way to go for now since we only support it on classic desktop atm (a comment saying as much would be good). it sounds like mvo may move it from /usr/local. not sure if that is something you would want to do as part of this13:56
zygajdstrand: OK13:57
zygajdstrand: will do13:57
jdstrandzyga: if it would help, I could do it. I always have a list of miscellaneous updates :)13:57
zygajdstrand: if you want to, sure go ahead :)13:59
zygajdstrand: I'm looking at snap-confine SRU paperwork now13:59
mvojdstrand: I can look into the move to /usr/bin later, probably tomorrow morning14:01
jdstrandmvo: ok, I'll just add the access to /usr/local and mention in the PR it should be adjusted when it is moved14:02
mvojdstrand: great, thank you14:06
tenaciousmvsergiusens: do you know of a nodejs-based snap that works when locally built and installed? See my comment above about shout working only when installed from snapcraft store14:18
sergiusenstenaciousmv see your comment where?14:19
sergiusensand yes, it works, our tests make sure of that (shout is in demos)14:20
kyrofasergiusens, zyga I'm not sure where was ever a bug filed since we never really got to the point where we knew what was causing the bug. didrocks said it needed some love from the desktop team. I was planning on starting an email thread once I had enough spare brainpower for it14:20
tenaciousmvsergiusens: repasting comment: hi. I'm trying to get the nodejs-plugin-based shout demo working: https://github.com/snapcore/snapcraft/tree/master/demos/shout  when I build and install it locally, i don't see anything in /snap/bin afterward14:24
tenaciousmvsergiusens: i'm glad the tests pass :) i wonder what i could be doing wrong. I just built, installed (with --force-dangerous) and shout is not in /snap/bin14:28
seb128mvo, sorry I forgot to reply to your ping earlier, unsure that's best, I would rather not have to modify the upstream .desktop, what sergiusens suggested and sounded nicer was to have that snapcraft.yaml define the .desktop name and let you override the exec and do the sed-ing for you14:28
kyrofatenaciousmv, the app is a service, which means it generates a systemd unit file instead14:29
kyrofatenaciousmv, it won't put anything in /snap/bin/14:29
mvoseb128: works for me, just copy/paste this comment in the PR and I will close it14:29
tenaciousmvkyrofa: after snap install shout, i see it in /snap/bin14:30
tenaciousmvthough `which snap` return /usr/bin/snap14:31
tenaciousmvis the verion of shout in the store the one built from the snapcraft.yaml in demos?14:32
kyrofatenaciousmv, no idea. Who is the publisher?14:33
seb128mvo, k14:33
tenaciousmvkyrofa: sergiusens14:34
kyrofatenaciousmv, I'm not sure what he has there. All I know is that this: https://github.com/snapcore/snapcraft/blob/master/demos/shout/snapcraft.yaml will not put anything in /snap/bin/14:34
tenaciousmvkyrofa: right, exactly14:36
tenaciousmvkyrofa: so how would you run the shout from the demos after installing it?14:36
kyrofatenaciousmv, it should already be running-- it's a daemon14:37
kyrofa(once you install it, obviously)14:37
kyrofaI'm not sure about the port, though14:37
tenaciousmvkyrofa: so i should be able to see it in service --status-all then no?14:39
tenaciousmvkyrofa: thx for helping btw14:39
kyrofatenaciousmv, now sure what the `service` command does nowadays, but you should be able to see if with `systemctl status snap.shout.server.service` I think14:40
kyrofas/if/it/14:40
tenaciousmvkyrofa: indeed, i see it!14:41
tenaciousmvkyrofa: is there an example of a nodejs app (not a daemon)?14:44
kyrofatenaciousmv, not that I know of off the top of my head, but you could make the shout one an example if you simply remove the `daemon: simple` line14:45
tenaciousmvkyrofa: ah, duh. Thanks!14:45
mupPR snapd#1943 closed: wrappers: add new X-Snap-Exec=$snap.$app support to .desktop files <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/1943>14:48
sergiusenstenaciousmv that demo doesn't setup anything to be in snap/bin14:53
tenaciousmvsergiusens: yea, kyrofa explained it to me. I missed the daemon line in the snapcraft.yaml14:53
sergiusenstenaciousmv shout on the store is in my repo, not in the demos14:53
tenaciousmvsergiusens, ok will check it out14:54
mupPR snapd#1945 opened: Spread out to trusty <Created by vosst> <https://github.com/snapcore/snapd/pull/1945>14:59
mupPR snapcraft#811 opened: Support deb files as sources <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/811>15:00
sergiusensogra_ ^ for you15:01
sergiusensmorphis and maybe you too ;-) ^15:01
ogra_bug 160466915:01
mupBug #1604669: Support Installing a local deb package in the snapcraft <Snapcraft:In Progress by sergiusens> <https://launchpad.net/bugs/1604669>15:01
ogra_ah15:01
sergiusensogra_ ;-)15:02
ogra_:)15:02
jdstrandseb128: fyi, http://paste.ubuntu.com/23203145/. the all snaps one is more justification that this should still be in unity7 for the moment. the second is on my desktop with snapd 2.14.215:07
seb128k, makes sense15:08
seb128jdstrand, your desktop doesn't have snapd-xdg-open installed right?15:08
seb128(we don't depends/recommends it afaik)15:08
jdstrandno15:08
seb128that's something we should change15:08
jdstrandperhaps we should on classic?15:08
seb128yes15:09
seb128mvo, ^ would you be the right person to add snapd-xdg-open to the snapd recommends?15:09
jdstrandsnapd-xdg-open doesn't appear to be a package in xenial15:09
seb128it's in universe15:10
seb128https://launchpad.net/ubuntu/+source/snapd-xdg-open15:10
seb128oh, in xenial15:11
seb128it's in xenial-proposed only15:11
jdstrandI see15:11
seb128the SRU verification relies on having the wrapper in the ubuntu-core image and working15:11
mhall119lool: did you say there wouldbe RPi3 images of snappy ubuntu core today?15:12
tedgI'm trying to put a slot on a snap, but it doesn't seem to show up in "snap interfaces" list15:13
tedgDoes anyone have a snapcraft.yaml of putting a slot on a snap that I could crib from?15:13
loolmhall119: at least pi2; I'd hope pi3 as well15:14
loolzyga: FTBFS with musl: http://paste.ubuntu.com/23203170/15:15
loolzyga: missing include probably?15:16
loolI'll double check I have the right version pulled from the build15:16
jdstrandpcoca: hi!15:18
jdstrandpcoca: do you have a moment to talk about bug #1613572 ?15:18
mupBug #1613572: sandbox denials for snaps on BTLE device <snapd-interface> <Snappy:Triaged by jdstrand> <https://launchpad.net/bugs/1613572>15:18
mupPR snapcraft#805 closed: Refresh discharge macaroon if necessary <Created by cjwatson> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/805>15:19
mhall119lool: when and where will those be available?15:19
loolzyga: http://paste.ubuntu.com/23203191/15:20
tedgHuh, seems that mongo22 doesn't have a slot either.15:21
loolzyga: right, you missed #include secure-getenv.h in sc-main.c15:21
ogra_mhall119, dailies (built from the edge channel) are at  http://people.canonical.com/~ogra/snappy/all-snaps/daily/current/ .. and beta releases are just being announced by mvo15:22
ogra_http://cdimage.ubuntu.com/ubuntu-snappy/16.04/current/15:23
mhall119thanks ogra_15:23
tedgbluez does, cribbing from there15:24
loolzyga: adding the #include is enough to fix build http://paste.ubuntu.com/2320321615:28
loolit fails in other components later15:28
loolzyga: http://paste.ubuntu.com/23203233/15:31
popeymhall119: https://lists.ubuntu.com/archives/snapcraft/2016-September/001166.html :)15:32
mhall119literally 10 minutes ago, that's timing :)15:35
zygalool: looking15:37
zygalool: oh, indeed15:37
zygalool: thanks, I'll put that into the relase15:38
zygalool: pushed15:41
loolzyga: lovely, thanks15:42
loolupdated my openwrt feed to point at it15:43
loolmhall119: http://cdimage.ubuntu.com/ubuntu-snappy/16.04/current/15:44
loolah too late15:44
ogra_lool, yeah, and lame too ... http://people.canonical.com/~ogra/snappy/all-snaps/daily/current/ has so many more exciting bugs15:47
mhall119lol15:49
diddledanI've reordered the list on https://github.com/ubuntu/snappy-playpen/wiki/SandPit to be alphabetical (also added my attempt at corebird to the list)15:54
oparozHello, what's the difference between mvo's all-snaps images and the ones available at cdimage?16:07
ogra_oparoz, the cdimage ones are official beta images16:18
ogra_the mov all-snaps ones are obsolete16:18
ogra_*mvo16:19
oparozThanks ogra_ . Does that mean that zyga's script to built images can be updated to point to the beta images? https://github.com/zyga/devtools/blob/master/ubuntu-image16:19
ogra_oparoz, use http://cdimage.ubuntu.com/ubuntu-snappy/16.04/current/ or if you like to live on the edge use http://people.canonical.com/~ogra/snappy/all-snaps/daily/current/16:20
ogra_everything else is dead beef and not supported anymore16:20
oparoz:)16:20
ogra_since they would be using  the wrong creation tool16:20
oparozwrong creation tool?16:21
dduffeyhi, I've tried various snappy 16 pi3 images but they all hang at the 4-rasberry screen16:21
dduffeylool, ^^^ what image are you using/16:21
looldduffey: http://cdimage.ubuntu.com/ubuntu-snappy/16.04/current is latest16:22
looldduffey: you want serial console rather than console16:22
loolbut I suppose console should work16:22
ogra_yeah16:22
ogra_dont use embedded boards without serial16:22
ogra_general rule of thumb16:22
dduffeylool, okay16:23
tbr+1 for UART16:23
tbrthose things are dirt cheap16:23
ogra_yeah16:23
ogra_oparoz, sudo snap install ubuntu-image --devmode --edge ... then you need to create a signed model assertion and have a proper new gadget.yaml following the new format16:25
dduffeylool, thanks ... I am using that image ... normal for it not to hit the network until I plug in a serial console and setup networking, correct?16:26
ogra_dduffey, you need to run through the console-conf tool, yes16:26
ogra_else you dont have a user either16:26
looldduffey: yes16:26
oparozThanks ogra_ . I think I'll just wait for you guys to provide the pi2 gadget and updated partitioning script to use an external HD :)16:29
ogra_http://bazaar.launchpad.net/~snappy-dev/snappy-hub/snappy-systems/files/head:/ is up to date ... regarding the gadget :)16:29
* ogra_ calls it a day16:32
oparozThanks ogra_16:32
ogra_np16:32
mupPR snapcraft#812 opened: New plugin: jhbuild <Created by attente> <https://github.com/snapcore/snapcraft/pull/812>16:39
mupPR snapd#1926 closed: tests: add https_proxy into environment as well <Created by mvo5> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/1926>16:58
=== dames is now known as thedac
mupBug #1625279 opened: cmd_run.go:179: WARNING: cannot create user data directory: cannot create "/home/$USER/snap/$SNAP/$VERSION": mkdir /home/$USER/snap/$SNAP: permission-denied <Snappy:New> <https://launchpad.net/bugs/1625279>17:12
tyhickszyga: congrats on the release :)17:17
sergiusensso jdstrand or zyga is there a plan of action for LP #1600136 ?17:23
mupBug #1600136: App indicator does not show icon for Qt apps <snap-desktop-issue> <Snappy:New> <snapd (Ubuntu):Confirmed> <https://launchpad.net/bugs/1600136>17:23
jdstrandsergiusens: not from me. I gave several ideas on how the desktop team/someone familiar with the technologies could pursue17:27
jdstrandsergiusens: but no one responded17:27
jdstrandultimately, the snaps are putting things in /tmp and that isn't the same /tmp that the system would see17:28
sergiusensjdstrand oh really, it might be a communication breakdown problem then as I suspect the desktop folk were pointing the other way17:28
* sergiusens checks the bug report17:28
jdstrandwell, I'm happy to discuss ways forward, but this is basically the same as all the stuff going into the desktop part. trying to make traditional applications that aren't designed for application isolation work17:29
jdstrandI suspect upstreams would be interested in patches because this would affect any sandboxing mechanism that uses a private /tmp (which is all of them afaik)17:31
sergiusensjdstrand I am going to play with my preload part and see what I can do; but patching upstreams would be ideal ;-)17:31
sergiusensin the case of telegram they already fork and patch Qt so I will try and see if they can take one more patch17:32
mupBug #1625291 opened: ConnectedSlotSnippet not invoked when connecting two snaps <Snappy:New> <https://launchpad.net/bugs/1625291>17:33
kyrofasergiusens, jdstrand at the sprint we realized the applications were sending icon blobs17:36
kyrofasergiusens, jdstrand in dbus I mean17:36
kyrofaWe couldn't figure out why they weren't showing up17:36
=== chihchun_afk is now known as chihchun
jdstrandkyrofa: I thought they were sending icon urls that were in /tmp. so the app puts it in its /tmp, but the system sees a different /tmp17:45
mupBug #1623589 opened: No icons anymore <Snappy:New> <snapweb:Confirmed> <https://launchpad.net/bugs/1623589>17:45
sergiusenskyrofa wait, this isn't in the bug report18:12
sergiusensif it's blobs it should just work however inefficient that is18:12
sergiusensdoesn't surprise me given other uses of bus I've seen :-P18:13
tenaciousmvsergiusens: another q about the nodejs plugin18:23
tenaciousmvsergiusens: running npm install as root sometimes has issues18:23
kyrofajdstrand, sergiusens yeah that's what we all thought, but in heidelberg that didn't appear to be what was happening. I personally didn't update the bug because I was incredibly confused at that point :P18:24
tenaciousmvbecause of the way npm tries to downgrade privileges or sth18:24
tenaciousmvsergiusens: is there a way to run npm install not as root?18:24
tenaciousmvsergiusens: another technique people use is npm install -g --unsafe-perm <package>18:24
tenaciousmvsergiusens: to prevent user/group switching during the installation18:25
jdstrandkyrofa: ah, well, then perhaps more digging simply needs to be done then documented in the bug and we can go from there18:32
kyrofajdstrand, indeed18:35
mhall119zyga: is there a way to specify environment variables in snapcraft.yaml yet?18:46
tvossniemeyer: o/18:46
niemeyertvoss: Heya18:52
tvossniemeyer: hey, welcome back :)18:52
niemeyertvoss: Glad to see your PRs coming up :)18:52
niemeyertvoss: Thanks18:52
niemeyertvoss: A few comments in one of them.. also, would just like to highlight the fact we have a convention on the summary18:53
niemeyerPlease have a look at the list here to get an idea: https://github.com/snapcore/snapd/pulls18:53
tvossniemeyer: yeah, let me rename them18:53
dchI'm packaging couchdb via snappy. It's important we have a migration story for our 1.6.x debian-style packages to a snappy-based one, and often they have very large databases 500GB upwards, so we can't "just" copy files around.18:56
tvossniemeyer: working through your comments now18:56
niemeyertvoss: Thanks again18:56
dduffeyokay I have pi3 booting and visiable via usb serial ... it seems to be taking some time after "Stated update resolvconf for Networkd DNS." .. but no login prompt, etc.18:57
dchis it possible to allow a snap to access specific parts of the old existing filesystem, like /var/lib/couchdb or /etc/couchdb/*.ini ?18:57
dchI'm also interested in making the snap available for centos & redhat too, this looks very cool18:58
mhall119sergiusens: snapcraft is stripping quotes out of the "command:" parameter for my daemon, how can I stop that?19:06
sergiusenstenaciousmv don't run snapcraft as root19:06
sergiusensmhall119 it may just be a bug19:08
kgunnjdstrand: hey, so took strace of amd64 and arm64, they are strikingly similar...so i don't quite see why amd64 succeeds confined and arm64 gets a hard denial19:17
kgunnone of the few differences i see is that the system call signatures are similar but not same...e.g. amd64 open is openat on arm6419:18
kgunnand stat on amd64 is newfstatat on arm6419:18
kgunnlikewise access on amd64 is faccessat on arm6419:19
mupPR snapd#1879 closed: debian: adjust installation to account for deputy systemd on trusty <Created by vosst> <Closed by niemeyer> <https://github.com/snapcore/snapd/pull/1879>19:25
mupPR snapd#1927 closed: tests: account for different PWD handling on trusty <Created by vosst> <Closed by niemeyer> <https://github.com/snapcore/snapd/pull/1927>19:27
tenaciousmvsergiusens: good idea! thanks19:28
mupPR snapd#1923 closed: tests: replace realpath with readlink -f for trusty support <Created by vosst> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/1923>19:28
mupPR snapd#1913 closed: daemon,store: move store login user logic to store <Created by matiasb> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/1913>19:38
mupPR snapd#1946 opened: interfaces: allow xdg-open in unity7, unity7 cleanups <Created by jdstrand> <https://github.com/snapcore/snapd/pull/1946>19:38
jdstrandkgunn: syscall numbers are architecure-dependent19:40
kgunnjdstrand: yeah, these arent' the numbers, these are the names of the calls listed in the strace19:42
kgunnjdstrand: but i'm kinda lost on what to do next19:42
jdstrandglibc might implement things differently depending on the arch too19:43
kgunnjdstrand: so do i simply need to add "openat" in my list of mirPermanentSlotSecComp19:45
kgunn?19:45
kgunnin order to cover both archs?19:45
jdstrandkgunn: I suggest comparing /etc/passwd, /etc/group, /var/lib/extrausers, and compare the file and directory ownerships from / to SNAP_DATA, etc, etc19:45
jdstrandkgunn: do you have a seccomp denial? you shouldn't. openat is allowed19:46
jdstrandkgunn: ie, the policy should already cover both archs for common stuff like that19:46
kgunnjdstrand: lemme look again, i have to drag out all my dragonbaord and cables :)19:47
jdstrandkgunn: the 3 you mentioned are already allowed19:47
kgunnah k19:48
kgunni'll double check the exact denial again...i forgot to note it down19:49
dduffeyif I have xenial snappy installed, how do i search --edge19:49
dduffey'snap find --edge"19:49
zygare19:53
jdstrandkgunn: you are still talking about dac_override, no? or did you get new denials?19:53
* zyga gets back to work19:53
jdstrandmorphis: fyi, I approved udisks2, but I think you need to press the publish button19:53
mhall119sergiusens: this is my snapcraft.yaml: http://paste.ubuntu.com/23204318/20:41
mhall119but snapcraft snap turns the exec line into:20:42
mhall119exec "env" ERL_FLAGS="-couch_ini ${SNAP_DATA}/default.ini ${SNAP_DATA}/local.ini" ${SNAP}/bin/couchdb "$@"20:42
mhall119wait, that's my modified one20:42
mhall119exec "env" ERL_FLAGS=-couch_ini ${SNAP_DATA}/default.ini ${SNAP_DATA}/local.ini ${SNAP}/bin/couchdb "$@"20:42
mhall119^^ that's what it does20:42
mhall119so  ERL_FLAGS=-couch_ini and then it tries to execute  ${SNAP_DATA}/default.ini20:42
mhall119I think i found a way around it20:46
kgunnjdstrand: ok, interesting, i just rebuilt snapd with only the inclusion of the new20:51
kgunn /run/udev/data/c13:[0-9]* r,20:52
kgunn /run/udev/data/+input:input[0-9]* r,20:52
kgunn...and that seemed to cure the dac_override need20:52
kgunnjdstrand: only other thing i can think, is i got my dragon into a weird state that a reboot cured?20:52
kgunnat any rate... jdstrand you were ok with me adding those to the mir interface right ^?20:53
jdstrandkgunn: yes20:53
jdstrandkgunn: glad that doc_override went away20:54
kgunnwill clean up and submit a pr20:54
kgunnug... jdstrand getting denial now...this is odd... i'll ping back if i get some consistency....21:09
mwhudsonsnappy sure makes reading the output of mount to e.g. find your sdcard harder :-)21:13
mwhudson(lxd and schroot, too)21:14
mupPR snapd#1946 closed: interfaces: allow xdg-open in unity7, unity7 cleanups <Created by jdstrand> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/1946>21:17
mupPR snapcraft#813 opened: [WIP] "snapcraft validate" and "snapcraft gated" commands <Created by ralsina> <https://github.com/snapcore/snapcraft/pull/813>21:19
kgunnjdstrand: dang i just got it figured out! ... so i got tired of the screen blanking on dragon, so i added a setterm to my bash21:21
kgunnthat was screwing with it, so all good now...21:21
* kgunn makes note of setterm being a not good idea with mir testing21:21
kgunni had kinda forgotten i even added that....21:22
jdstrandhuh21:24
jdstrandnice find!21:24
mhall119is there any way to pre-populate $SNAP_DATA without resorting to a wrapper script?21:36
mhall119twice now I've had snaps that don't need a wrapper except for doing the initial $SNAP_DATA setup21:40
mupPR snapd#1858 closed: interfaces: add stub selinux backend <Reviewed> <Created by zyga> <Closed by niemeyer> <https://github.com/snapcore/snapd/pull/1858>21:44
mupPR snapd#1947 opened: interfaces/builtin: add initial docker interface <Created by jdstrand> <https://github.com/snapcore/snapd/pull/1947>22:03
mupPR snapd#1619 closed: interfaces/builtin: add initial docker interface <Blocked> <Created by tianon> <Closed by jdstrand> <https://github.com/snapcore/snapd/pull/1619>22:05
tianonjdstrand: would it be helpful to just put you directly on the collaborators list for https://github.com/docker-snap/docker ? :)23:32
=== chihchun_afk is now known as chihchun

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!