[05:39] I would guess it depends on the license it is released under [05:48] ogra_: how does snappy know where to mount the /writeable partition and what to do with it? === dr1337_ is now known as dr1337 [06:22] dr1337, from the initrd (and the filesystem label) [06:27] ogra_ nah I mean the snap command [06:27] on snapcraft.io it's /snap [06:27] well, that doesnt mount the writable partition [06:28] snaps are just squashfses and the /snap path is hardcoded [06:29] for more details, i guess zyga might be able to point you to the right code snippets [06:29] and what's the gadget snap for? [06:31] it describes the image (defining what kernel, bootloader and partitioning is used) === King_InuYasha is now known as Son_Goku === Mirv_ is now known as Mirv [07:52] is it normal that my confined snap does not have access to /tmp? [07:55] xnox, no ... it should spin up its own /tmp dir [07:55] e.g. i would have expected for mkdtemp() calls to work, as they do with e.g. PrivateTmp= in [07:55] it doesnt have access to the systems /tmp though [07:56] my code calls mkdtemp() [07:56] and i hoped that it would just work(tm) [07:57] ogra_, as in the execution envrionment should set-up per exec $tmpdir and set envrionemnt variables that would make mkdtemp() to work. [07:57] well, that should work ... on a per-snap base though [07:57] apps within the same snap should use the same /tmp ... if thats not the case, it is a bug [07:59] D$HmMo100709_ubu [08:00] someone needs to change their p4ssw0rd === tbr_ is now known as tbr [08:24] ogra_, right. I will experiment more and probably will open a bug report [08:24] jdstrand: is there a plan to update click-reviewers-tools in xenial? I am getting different results in snap-review on my laptop than the store gives. e.g. results on this app gives me bug 1618123 locally, https://myapps.developer.ubuntu.com/dev/click-apps/6141/rev/1/ [08:24] Bug #1618123: Add a build grade attribute to snaps [08:35] I'm trying to implement an interface for download manager, and I'm wondering what the snappy equivalent of APP_PKGNAME and APP_ID_DBUS are for app armor rules; I managed to bodge something with SNAP_NAME, but that doesn't seem like a reliable approach === chihchun_afk is now known as chihchun [08:37] popey: eventually, yes. I'm working on a big update for snap declarations and figured I'd update it after [08:53] jdstrand: ok, thanks. [08:53] PR snapd#2155 opened: HACKING.md: fix spread command for reusing servers [08:55] morphis, ogra_: do we care about any wlan drivers that do *not* support nl80211? [08:56] uuh, thats probably a kernel team question [08:56] (but i'd guess wwe should care about all possible drivers) [08:58] i have a half-assed version of 'ip monitor' now [08:58] now to hack up something like what 'iw monitor' would be if that existed === tinwood_ is now known as tinwood === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [10:15] PR snapd#2156 opened: many: move from flags as ints to flags as structs-of-bools [10:25] Bug #1634088 opened: Cannot activate Chinese input method for Qt app [10:25] Bug #1634089 opened: Cannot activate Chinese input method for Qt app [10:50] PR snapd#2157 opened: read/write boot variables in a single operation [11:19] hey does anyone know of a commercial product that's currently on sale that uses snappy core? [11:43] Hi, I've created snapcraft.yaml for application which uses tesseract. Snap package is done, but application crashes because cannot access the files in /usr/share/tesseract-ocr/tessdata. Did I miss something in sanpcraft.yaml? (permissions) === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === ara is now known as Guest69211 [12:41] PR snapd#2158 opened: many: remove unnecessary snap name parameter from buying endpoint === chihchun_afk is now known as chihchun [13:07] PR snapd#2159 opened: spread.yaml: dump apparmor denials on spread failure === chihchun is now known as chihchun_afk [13:28] PR snapd#2160 opened: image: tweak the cloud-init configuration === coreycb` is now known as coreycb === josepht` is now known as josepht [14:54] PR snapd#2161 opened: interfaces/builtin: add dcdbas_control interface [15:07] PR snapd#2091 closed: interfaces: tweak wording and comment [15:07] PR snapd#2159 closed: spread.yaml: dump apparmor denials on spread failure [15:43] I edited the origin on https://wiki.ubuntu.com/snapcraft/parts but https://parts.snapcraft.io/v1/parts.yaml wont edit [15:44] oh! nevermind, that's the git for the source right! sorry about that [15:55] how can i access .ssh with plugs? [16:38] PR snapd#2162 opened: interfaces: add system-power-control interface [18:23] PR snapd#2155 closed: HACKING.md: fix spread command for reusing servers [19:23] PR snapd#2163 opened: update dependency of ubuntu-core-launcher to snap-confine [19:34] PR snapd#2164 opened: many: add supports for keeping and finding assertions with different format iterations [20:09] PR snapd#2165 opened: snap: stop using ubuntu-core-launcher, use snap-confine [20:48] qengho, any idea what might cause a system to attempt looking for /var/lib/snapd/snaps/_x1.snap instead of the installed proper version "12" from the snap store. [20:49] qengho, x1 seems to be a placeholder/indicator for locally installed snaps, which mine wasn't [20:49] could it have something to do with intermittent network connectivity somehow? like validating w/ an unavilable snap store? [20:51] I'm getting occasional errors from ureadahead as the system is starting up trying to access *_x1 files that don't exist [22:57] PR snapd#2148 closed: many: introduce an assertion format iteration concept, refuse to add unsupported assertion