[09:08] Good morning all; happy Friday, and happy Siblings Day! :-D === vrruiz_ is now known as rvr === erkules_ is now known as erkules [10:58] mvo: it's frameworks (list versus string) [10:58] mvo: I was going to fix last night but got distracted fixing other things [10:58] sergiusens: yeah, fixed [10:58] sergiusens: no worries [10:58] mvo: just removed the line a suppose [11:11] mvo: btw, mind looking at my latest u-d-f mps? [11:11] sergiusens: yeah, just removed it [11:11] sergiusens: sure, do you have a url? [11:11] sergiusens: I will need lunch first though [11:13] pitti: fwiw, was just trying to know the status on ntp, not sure you were on top of it or who was [11:14] mvo: https://code.launchpad.net/goget-ubuntu-touch/+activereviews [11:14] sergiusens: we have timesyncd enabled by default now, AFAIK that was the intended ntp client for snappy? [11:14] mvo: the ones from les that 24hrs ago :-) [11:14] pitti: oh, it is, great! === kickinz1 is now known as kickinz1|lunch === kickinz1|lunch is now known as kickinz1 [12:58] sergiusens: how do I use your new beaglebone snap straight from the store? [13:03] lool: call it by name [13:03] lool: e.g.; beagleboneblack.sergiusens [13:03] --oem beagleboneblack.sergiusens [13:08] sergiusens: sudo ubuntu-device-flash core \ --platform am335x-boneblack \ --size 4 \ --oem beagleboneblack.sergiusens --developer-mode --channel=ubuntu-core/devel-proposed -o bbb.img [13:09] lool: --size is 4 by default [13:10] lool: just sudo ubuntu-device-flash core --output bbb.img --channel edge --oem beagleboneblack.sergiusens is enough [13:10] lool: I tried to apply sane defaults everywhere to type less [13:22] sergiusens: what defines "edge" as a channel? [13:24] sergiusens: and how does it figure --platform am335x-boneblack? [13:25] (I'd like to do the same for pi) [13:25] ok, found channel maps [13:26] lool: platform is in the oem snap [13:26] lool: the channel maps is a shorthand, (and some form of consistency with the snappy tool) [13:27] it kind of feels bad to have this in the tool rather than as server side aliases, but I can see why it's handier for now [13:29] lool, sergiusens, started working on a spec: https://docs.google.com/document/d/1-BFwOcM7yq3feowdAL9SVW5UZkNHiE0q3duXBMUkkyY/edit [13:30] lool: I was waiting for the system image rename to happen to make this easier [13:31] beuno: I guess you've already seen the naming of the chrome release channels [13:31] https://www.chromium.org/getting-involved/dev-channel [13:31] it seems we have the same number of channels, but with different names [13:31] (that's fine of course) [13:33] lool, we have 1 more! :) [13:33] anyway, its subject to change, it captures the discussions we've had so far [13:35] (RaspberryPi2)ubuntu@localhost:~$ sudo snappy install docker_1.5.0.001_multi.snap [13:35] Installing docker_1.5.0.001_multi.snap [13:35] 2015/04/10 13:34:53 Signature check failed, but installing anyway as requested [13:35] mkdir /apps/docker/1.5.0.001/meta/framework-policy: permission denied [13:35] unpack docker_1.5.0.001_multi.snap to /apps/docker/1.5.0.001 failed with exit status 1 [13:35] kickinz1: ^ [13:35] mvo: ^ does the above sound familiar (snappy go version on image 220 on rpi2) [13:36] I'm trying to get docker to load a dockerfile on snappy but get the error `2015/04/10 13:32:38 open dockerfile.tar: permission denied` when I try to do it as the ubuntu user and get `sudo: docker: command not found` when I do it with sudo, anyone have any ideas what I could be doing wrong? [13:37] fionnan, you need to have your Dockerfile in /home/ubuntu/apps/docker/1.3.xxx/ [13:37] if anyone knows of any docs about using docker on snappy would be great too, I can't seem to find anything :( [13:38] kickinz1: cool, thanks! [13:38] then in this dir you run docker buid... [13:38] lool: I think Chipaca is dealing with this [13:38] sergiusens: with what? [13:39] Chipaca: see above error when installing docker [13:39] lool, hdstrand had this yesterday evening, but it was related to a bad docker-daemon.apparmor. [13:39] 15:35 < lool> mkdir /apps/docker/1.5.0.001/meta/framework-policy: permission denied [13:39] 15:35 < lool> unpack docker_1.5.0.001_multi.snap to /apps/docker/1.5.0.001 failed with exit status 1 [13:39] kickinz1: that fixed it! [13:39] kickinz1: I've built the rootfs minutes ago against devel-proposed; how do I get the fix? [13:39] lool: that does not look like something i'm doing, no [13:39] lool: why did you get permission denied on mkdir? [13:40] lool: I will upload a more recent one for you to test, but the one I sent to you was supposed to work [13:40] ooh, wait, that might be me [13:40] * Chipaca looks a bit deeper [13:40] mvo: jodh I got this weird problem when upgrading from d-p to devel-proposed http://paste.ubuntu.com/10791611/ [13:41] kickinz1: I have beagle up too [13:41] lool: so, that error itself is not me afaict, but i'd be interested in knowing how you got there [13:41] ubuntu-core 2015-04-10 220 [13:41] lool: are the permissions in the docker tar wrong? [13:41] Chipaca: I dont know, I can check [13:42] lool: please [13:42] Chipaca: look alright to me [13:42] Chipaca: http://paste.ubuntu.com/10791622/ [13:43] yep, those lok alright [13:43] look* [13:45] lool: do you have anything in dmesg? [13:45] Chipaca: remember that snappy calls unpack with reduced privs [13:46] sergiusens: but i don't see any reason for a mkdir at random to fail on unpack, which is what's reported here [13:48] sergiusens: it's an upgrader bug resulting from the recent rework. Fixing... [13:50] lool: so, i don't know where/how you're trying to make that work, but i just tested the docker thing locally and it installed without a hitch [13:50] lool: so i'd really like to know more :) [13:50] [ 64.460170] audit: type=1400 audit(1428673111.960:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="system-status.victor_system-status_1.0.3" pid=805 comm="apparmor_parser" [13:50] [ 66.848594] audit: type=1400 audit(1428673114.348:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="pastebinit.mvo_pastebinit_1.4.0.0.1" pid=805 comm="apparmor_parser" [13:51] [ 86.906565] audit: type=1400 audit(1428673134.408:8): apparmor="DENIED" operation="capable" profile="system-status.victor_system-status_1.0.3" pid=884 comm="system-status" capability=12 capname="net_admin" [13:51] are the only dmesg bits [13:51] lool: dmesg -T will give you saner timestamps, for next time :) [13:51] none of those seem relevant to docker [13:51] good to know [13:51] Chipaca: no [13:52] Chipaca: would also be surprized that snappy install would run confined [13:52] so mkdir failing is weird [13:52] Chipaca: I'll test on BBB in a few, with an updated snap [13:53] lool: what are you testing on, here? [13:53] Chipaca: oh sorry, dmesg is from wrong board [13:53] lool: is this the same vm that was saying "no space left on device"? [13:53] I actually reinstalled since [13:54] Chipaca: so yes, it is from same vm [13:54] Chipaca: and I think the issue is missing modules [13:54] [Fri Apr 10 13:00:10 2015] systemd-journald[458]: Failed to create new runtime journal: No space left on device [13:54] probably lack of tmpfs [13:54] right, lsmod is empty [13:54] the modules are there in rootfs, but not initrd [13:54] * lool goes updating [13:55] lool: so it looks like that vm is otherwise fubar'ed [13:56] yeah [13:56] lool: if you can reproduce the issue with a vm that is not already broken let me know :) [13:56] i really think we need a "sanity check" command in snappy [13:56] ... but there's so much more stuff we need :) [14:02] bah I foobarded the initrd [14:06] /sbin/udevadm: line 2: ��HL�F�k��@�� [14:06] somehow not good [14:06] /sbin/udevadm: line 1: ELF: not found [14:08] ppisati: sorry, mind reminding me how to properly repack initrd? I gunzip-ed | cpio -i, and am repacking with find . | cpio --quiet --dereference -o -H newc | lzma -7 > ../new-initrd.lz [14:08] well, I'll start with gzip [14:08] is it possible to develop/tinker on snappy core on raspberry pi without a second raspberry pi running ubuntu? [14:12] lool, abootimg-unpack-initrd ... abootimg-pack-initrd [14:12] we have helpers for this ;) [14:15] ok, managed to repack initrd [14:15] ogra_: thanks [14:15] it was actually my unpacking which was incorrect [14:15] (forgot -d to cpio) [14:15] I still get [ 50.591157] systemd-journald[399]: Failed to create new runtime journal: No space left on device [14:17] ppisati: so for some reason the modules dep were out of date [14:22] I still get the dreaded [ 50.525271] systemd-journald[332]: Failed to create new runtime journal: No space left on device [14:22] I don't see any information about "cross compiling" or porting applications to raspi/snappy, so maybe it isn't that easy [14:23] eltigre: http://hypernephelist.com/2015/03/09/cross-compilation-made-easy-on-ubuntu-with-sbuild.html [14:23] eltigre: it depends *what* you're cross-compiling though [14:23] eltigre: I typically did all the MWC snaps with cross-compilation [14:24] go / C / C++ ones mainly [14:24] but sometimes it can be a pain [14:24] I would be using python [14:24] eltigre: are there native bits? [14:24] I think I will go the raspbian route for the foreseeable future [14:24] maybe [14:25] eltigre: I'm not sure why it would be any easier with raspian [14:25] it's pretty easy to run into C extensions you didn't expect in Python nowadays [14:25] *raspbian [14:25] it compiles stuff [14:25] slowly, but it does [14:25] and it has a package manager, unlike snappy [14:25] we do have a package manage, it's snappy! :-) [14:26] no, that's an application manager [14:26] eltigre: right, we dont have snaps for a build environment [14:26] the difference being that you have to somehow get your dependencies in the app itself, as far as I understand it [14:26] that's right [14:27] kickinz1: ok, I managed to install docker on rpi2 now [14:27] which is on one hand a very good idea, but on the other... well... unfamiliar and currently much more work [14:27] eltigre: I think that's about right [14:28] it's less familiar and more work right now [14:28] but it pays off in the end [14:28] eltigre: you can have an Ubuntu chroot on a snappy install where you do the builds [14:28] lool: ok, I have a new package for you then. [14:28] or a qemu-arm schroot on your desktop (above blog post) or cross-build stuff [14:28] problem is, I'm not that familiar with the chrooting stuff... I hardly even grokked docker [14:28] eltigre: now specifically for python, you'd want to grab barry who's worked exactly on this topic [14:29] eltigre: https://lists.ubuntu.com/archives/snappy-devel/2015-April/000428.html [14:29] thanks [14:30] kickinz1: does it intentionally have the exact same name as the previous one? [14:31] 2015/04/10 14:31:01 Signature check failed, but installing anyway as requested [14:31] open /apps/docker/1.5.0.001/meta/docker-daemon.seccomp: permission denied [14:31] unpack docker_1.5.0.001_multi (1).snap to /apps/docker/1.5.0.001 failed with exit status 1 [14:31] that's weird [14:31] kickinz1, jdstrand: The older snap installs fine though [14:32] lool: this might be because you are installing the same version over other? [14:32] lool: on bbb? [14:32] kickinz1: both on rpi2 [14:32] jdstrand: maybe [14:32] jdstrand: I had snappy removed though [14:32] lool: what is ls -l /apps/docker/1.5.0.001/meta/ [14:33] right now after successful install of old snap: http://paste.ubuntu.com/10791980/ [14:33] * lool removes [14:33] that looks fine [14:33] now /apps/docker exists but is empty [14:33] lool: do ls -l after removal too [14:34] ok, that is what I've seen [14:34] now installing again the new one [14:34] I've renamed it to drop the " (1)" in the filename [14:34] ah that worked [14:34] jdstrand: was just a filename issue [14:34] ok cool [14:35] now I got http://paste.ubuntu.com/10791992/ [14:35] jdstrand seems ok on bb for me [14:35] kickinz1: ok, installed latest snap on pi2; what do I confirm? [14:36] lool: docker run -it armbuild/ubuntu [14:36] on the container just try some things like: "apt-get update && apt-get upgrade" [14:36] FATA[0000] Post http:///var/run/docker.sock/v1.17/containers/create: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS? [14:36] then docker stop "id of the container" [14:37] * lool removes docker, and grabs latest package [14:37] lool, sudo systemctl status docker_docker-daemon_1.5.0.001.service [14:38] kickinz1: switching to your latest snap first [14:38] lool ok [14:39] installing [14:40] Process: 1347 ExecStop=/apps/docker/1.5.0.001/bin/docker.stop (code=exited, status=0/SUCCESS) [14:40] Process: 1319 ExecStart=/apps/docker/1.5.0.001/bin/docker.start (code=exited, status=1/FAILURE) [14:41] lool, can you paste the tailed output of "sudo journalctl -l" [14:41] lool: you may have a stray docker running from before [14:42] kickinz1: cloud-init stuff only [14:42] jdstrand: yeah, that's what I think too [14:43] I dont see it in ps though [14:43] * lool reboots [14:45] uh -bash: docker: command not found [14:46] Loaded: not-found (Reason: No such file or directory) [14:47] I dont see the systemd service file under /etc/systemd/system [14:51] ok. trying BBB now [14:51] ok, docker is running [14:51] $ docker run -it armbuild/ubuntu [14:51] Unable to find image 'armbuild/ubuntu:latest' locally [14:51] Pulling repository armbuild/ubuntu [14:52] it's doign stuff [14:52] kickinz1: So not tested in full on BBB, but seems mostly working [14:52] lool, ok, thanks! [14:53] would love some help debugging the isuse on rpi2 [14:53] I'm removing docker snap, will search for stray files, and reboot [15:01] Active: failed (Result: exit-code) since Fri 2015-04-10 15:01:17 UTC; 13s ago [15:01] Process: 1033 ExecStopPost=/apps/docker/1.5.0.001/bin/docker.poststop (code=exited, status=0/SUCCESS) [15:01] Process: 1003 ExecStart=/apps/docker/1.5.0.001/bin/docker.start (code=exited, status=1/FAILURE) [15:02] /apps/docker/1.5.0.001/bin/docker.start: line 14: /home/ubuntu/etc/docker.conf: No such file or directory [15:02] /apps/docker/1.5.0.001/bin/docker.start: line 32: docker: command not found [15:03] FATA[0000] open /var/run/docker.pid: permission denied [15:05] jdstrand: what's the magic to force regenerating the profiles? probably because I installed multiple snaps with same version [15:05] [Fri Apr 10 15:04:36 2015] audit: type=1400 audit(1428678276.674:17): apparmor="DENIED" operation="mknod" profile="docker_docker_1.5.0.001" name="/run/docker.pid" pid=1185 comm="docker.armhf" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 [15:05] lool: sudo aa-clickhook -f ; sudo aa-profile-hook -f [15:05] thanks [15:06] jdstrand: I still get: [Fri Apr 10 15:05:58 2015] audit: type=1400 audit(1428678358.915:21): apparmor="DENIED" operation="mknod" profile="docker_docker_1.5.0.001" name="/run/docker.pid" pid=1209 comm="docker.armhf" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 [15:06] kickinz1: ah-- ^ [15:06] that's only on pi2 though [15:06] we have this rule: [15:06] /run/@{APP_PKGNAME}.pid rw, [15:07] jdstrand: note that I'm running this by hand because the job fails to start [15:07] but APP_PKGNAME is 'docker-daemon' [15:07] aha [15:07] jdstrand, I don't understand how it works on bbb as it is also running docker.armhf. [15:08] that isn't the part [15:08] name="/run/docker.pid" [15:08] we have: [15:08] @{APP_APPNAME}="docker-daemon" [15:08] /run/@{APP_PKGNAME}.pid rw, [15:08] oh wait [15:08] no, that is right, I misread it [15:09] [Fri Apr 10 15:07:34 2015] device-mapper: table: 254:0: thin-pool: unknown target type [15:09] [Fri Apr 10 15:07:34 2015] device-mapper: ioctl: error adding target to table [15:09] that seems to be the actual error from the job [15:09] ppisati: ^ [15:09] oh this is the docker command [15:09] kickinz1: hold on [15:10] jdstrand: I suspect it's non-fatal [15:10] yes [15:10] it is [15:10] so annoying, but systemd cleans things up [15:10] it refers to this: drivers/md/dm-thin.c: [15:10] interesting that amd64 didn't need it [15:11] ppisati: is it built in your rpi2 kernel? [15:11] lool: do you have that module? [15:11] no idea [15:11] ppisati: what's the module name? [15:12] DM_THIN_PROVISIONING [15:12] ppisati: # CONFIG_DM_THIN_PROVISIONING is not set [15:12] ppisati: I blame it all on you! [15:12] obj-$(CONFIG_DM_THIN_PROVISIONING) += dm-thin-pool.o [15:12] :) [15:12] ppisati: could you make sure this is part of our "Ubuntu standard options that always turned on"? [15:12] YES YES WHIP ME WHIPE!!! :D [15:13] yeppa [15:13] i can kick a new build [15:13] right now [15:13] ppisati: and coud you rebuild a rpi2 kernel with all interesting options we usually want turned on? [15:13] thanks [15:13] lool: we already have all the interesting options turned on [15:13] lool: this one wasn't part of it [15:13] kickinz1: so I think we wont hit the time for the pi2 demo, but we at least know how to get there and we seem close enough that we would have one, say, monday [15:13] * ppisati goes and kick a new build [15:13] lool: when did you see that? when the service was correctly running or when it wasn't? [15:13] jdstrand: that was on the rpi2 [15:14] was docker-daemon running? [15:14] jdstrand: trying to run the service by hand to trigger [15:14] jdstrand: no [15:14] ah [15:14] right, then that is correctly denied [15:14] jdstrand: actually on BBB I see *nothing* [15:14] jdstrand: so I guess it's not something you'd want to worry about [15:15] I guess side effect of me launching teh job by hand somehow [15:15] lool: to start by hand, do sudo aa-exec -p docker_docker-daemon_1.5.0.001 -- /apps/docker/current/bin/docker.armhf ... [15:15] thanks [15:16] lool: if you use 'docker' by hand, you get the 'docker cli command' and policy from /apps/bin [15:16] thanks [15:16] lool: but you want to run docker as a daemon, so you need to start it under that profile [15:16] kickinz1: nothing to be done [15:16] at least policy wise [15:16] ppisati: poke when you have a new PPA kernel, I'll update my device tarball with it [15:16] lool: yep [15:17] ppisati: I can update the initrd too; not quite sure how to generate the modules dep without booting a pi2 and running depmod -a though [15:17] lool: but do you actually need the modules during boot? i don't think so [15:18] ppisati: I dont think so, but I'm trying to keep them up-to-date nevertheless [15:18] ppisati: besides, I'm including the deps in the device tarball rootfs part [15:25] jdstrand: thanks again for the pointer to the unconfined profile, I created http://paste.ubuntu.com/10792277/ now, but it seems it does not like the last line I added "change_profile" - is the syntax here different? [15:27] jdstrand: aha, it seems like "change_profile -> *" is the right one (?) [15:27] change_profile -> *, [15:27] thanks! that helped me a lot [15:27] * mvo hugs jdstrand [15:27] but, if you did want to confine this, you can do stuff like [15:27] change_profile -> docker_*, [15:27] * jdstrand hugs mvo back :) [15:28] ogra_: around? [15:28] asac, in a meeting, but around, yeah [15:28] ogra_: can you check in on #snappy-internal ? [15:28] for a moment [15:32] ogra_: hi, I'm here [15:32] hey kirkland [15:33] ogra_: okay, we're getting started [15:41] lool: it's baking - https://launchpad.net/~p-pisati/+archive/ubuntu/embedded/+packages [15:49] beuno: hey, so in the store, you can upload a snap but there is no way to choose an architecture any more? [15:49] beuno: kickinz1 is uploading docker and in the yaml it has: architecture: [amd64, armhf] [15:50] beuno: that's fine. but then it comes up as arch all in the store, but it isn't 'all', it is 'multi' and only 'multi' for two archs, not all of them [15:52] jdstrand: same error i had for wget [15:52] interesting [15:53] maybe the store needs a little tweaking [16:22] beuno (and kickinz1 and ppisati): I adjusted the review tools to match what the store is currently doing so this shouldn't happen again [16:23] well, once the store is updated [16:23] jdstrand, ok thanks [16:25] jdstrand: what are these tools? [16:26] ppisati: they are the things that run during snappy build and what runs on the server [16:26] lp:click-reviewers-tools [16:27] jdstrand: jdstrand that means i shall rebuild and resubmit? or do i still need for a store update? i guess the latter [16:27] *need to wait [16:29] ppisati: no, you don't need to do anything [16:29] the next time you upload, if the store has pulled in my change, you won't have that review tool error [16:34] ubuntu@localhost:~$ sudo snappy update [16:34] ubuntu-core 124 MB [===================================================================================================================================================] OK [16:34] I've been stuck after that for 10+ minutes now [16:34] help? [16:35] kirkland on which board? [16:35] kickinz1: rpi2 [16:35] channel is devel-proposed? [16:35] kickinz1: how can I tell? [16:36] kirkland: I don't have rpi2, sorry [16:36] kickinz1: how can I tell what channel? [16:36] kirkland: cat/etc/syste-image/channel.ini [16:36] okay, it's applying now [16:36] kirkland: if channel is ubuntu-core/devel [16:37] kirkland, you will need to 'sudo mount -o remount rw /' [16:37] kirkland, change channel to ubuntu-core/devel-proposed, then reboot, then update [16:38] kirkland, but from me it is theory (as done on bbb), better have an anwer from an rpi2 owner [16:39] kickinz1: okay [16:39] kickinz1: can I just snappy install docker now? [16:39] kirkland, if on new image : yes [16:40] kickinz1: okay, i'm updated now, rebooting [16:40] kickinz1: where can I just download the latest rpi2 image now? [16:40] kirkland, but I don't know the status of docker on rpi2, I didn't get updates on that [16:42] kirkland, what 'snappy list' looks like? [16:42] snappy: error: invalid choice: 'list' (choose from 'info', 'versions', 'search', 'update-versions', 'update', 'rollback', 'install', 'uninstall', 'tags', 'config', 'build', 'booted', 'chroot', 'framework', 'fake-version', 'nap') [16:42] kirkland, ok old image [16:43] kickinz1: where can I get the new image? [16:43] kickinz1: why didn't snappy update get me the new image? [16:43] kirkland, cause latest image is not yet promoted [16:43] kirkland, I would go for channel change/ or backup solution is to use a docker-1.5.0-armhf for old image [16:44] kickinz1: channel: ubuntu-core/devel [16:44] jdstrand, asac, ^ [16:45] kirkland, try this package: https://mifamofi.net/owncloud/public.php?service=files&t=c2d37c5711ef8b323ac3da519142e21d [16:45] kickinz1: kirkland rpi has no upgrade path until we have a proper kernel in our repos [16:45] kirkland: someone said earlier it took 20 minutes [16:45] kickinz1: okay, I'm on devel-proposed now [16:45] ok good [16:45] if on devel-proposed, use the store [16:45] kirkland: lool has made an image prebuilt for you [16:46] asac: link? [16:46] in your inbox ;) [16:46] * asac looks it up [16:46] he sent an email [16:46] got it [16:46] kirkland: you cnanot update on the pi2 from alpha2 or even after because its nota certified enablement [16:46] so just install the one you have [16:47] new builds at least dont try to update [16:48] custom.img 09-Apr-2015 16:01 3.6G [16:48] kirkland: wget http://people.canonical.com/~lool/pi2-device-and-oem/custom.img [16:48] dd it [16:48] yeah [16:48] asac: I don't have enough bandwidth to pull that here [16:48] kirkland: ok i can xz it [16:48] one moment [16:49] lool: i have to wget that because you are not on lillypitty? [16:50] weird [16:50] or you have weird permissions [16:50] lool: could you .xz this ... assuing it will be popular for the moment? [16:50] and put checksums ni place [16:52] kirkland: i am xz'ing here rifght now: http://people.canonical.com/~asac/tmp/pi2/ [16:52] takes a it [16:52] bit [16:55] asac: you don't have to wget it [16:55] i couldnt copy it from ~lool [16:55] I logged into lillypilly and can see it [16:56] lool has always special permissions [16:56] hehe [16:56] ok [16:56] I didn't try copying [16:56] maybe i mistyped [16:56] but i have it now anyway [16:56] ok [16:56] "french permissions" [16:56] hehe [16:59] man xz is so slow [16:59] i thinkk my 3.6G wget will finish before it finish packing [17:02] asac: okay, thanks [17:02] asac: is ogra_ still around, or gone? [17:02] asac: we're also trying the node-snapper stuff right now [17:02] kirkland, i'm here [17:02] ogra_: alright!!! [17:03] kirkland, moving to the living room though ... i.e. no internal channels anymore :) [17:03] ogra_: can you post your metadata.yaml from your node-snapper example? [17:03] lool: http://people.canonical.com/~asac/tmp/pi2/custom.img.xz [17:03] i think its fine [17:03]