[03:27] <jtam> Hi, recently I am playing with snappy on raspberry pi, I want to use docker to run my application. while running the command 'docker run -d --device=/dev/ttyAMA0:/dev/ttyAMA0 --device=/dev/mem:/dev/mem --privileged -ti <name>', I got this error 'open /dev/bus: permission denied ', any ideas how to solve it?
[07:54] <shuduo> ogra_: ping
[07:58] <shuduo> ogra_: hi, i have asked you regarding OEM snap few days ago. Now I'm generating an oem snap and snappy image on xenial environment. I refer snappy-systems code and built out oem snap but u-d-f refused to generate snappy image with msg "kylin-oem/canonical-rockchip-kylin_1.0_all.snap failed to install: open /tmp/read-file931124659/unpack/DEBIAN/manifest: no such file or directory".
[08:01] <shuduo> and u-d-f refused eailer oem snap due to package.yaml can't be found. seems 15.04 use meta/package.yaml but 16.04 use meta/snap.yaml
[08:02] <shuduo> i copied snap.yaml to package.yaml to make u-d-f satisfied but stuck at DEBIAN/manifest. anything wrong I made?
[08:06] <shuduo> anyone help me for above issue?
[08:10] <zyga> good morning
[08:12] <zyga> shuduo: OEM snaps are gone right? we have kernel (or platform really as it's more than the kernel), os snap (shared among all core devices) and gadget snap
[08:12] <zyga> shuduo: OEM is the old name for what 16.04 calls the kernel snap
[08:13] <shuduo> zyga: morning
[08:13] <shuduo> zyga: is there a doc for how to port snappy 16.04 to a new platform I can read?
[08:14] <zyga> shuduo: maybe, but I don't know of one, I'd start with raspberry pi as a learning device (to see how it's made) and then try to transplant bits and pieces to a different hardware
[08:15] <zyga> shuduo: so get 16.04 gadget and kernel for pi2
[08:15] <zyga> shuduo: and see what's inside
[08:15] <zyga> shuduo: make sure you can rebuild them
[08:15] <zyga> shuduo: and iterate
[08:16] <zyga> noizer: hey
[08:16] <zyga> noizer: I wasn't around yesterday
[08:16] <zyga> noizer: I can help you out, I'd just prefer to do it in public here, as others can benefit, ok?
[08:18] <noizer> ok
[08:18] <shuduo> zyga: thanks. could you pls point me where I can download gadget and kernel snap of PI2?
[08:19] <zyga> shuduo: I wish I can remember, gimme a sec
[08:19] <shuduo> and u-d-f command line parameters for 16.04
[08:19] <shuduo> thanks
[08:19] <zyga> shuduo: http://bazaar.launchpad.net/~snappy-dev/snappy-hub/snappy-systems/files
[08:20] <zyga> shuduo: have a look at this, I haven't tried in a while but I think this is the right version
[08:20] <zyga> shuduo: http://bazaar.launchpad.net/~snappy-dev/snappy-hub/snappy-systems/view/head:/pi2/meta/snap.yaml
[08:20] <zyga> shuduo: this is the gadget snap
[08:21] <zyga> shuduo: now the kernel... hmm
[08:21] <noizer> zyga how can i check that I did everything correct from the core?
[08:21] <shuduo> zyga: yes, i read it and thought it's OEM snap
[08:21] <zyga> noizer: so what did you do so far?
[08:22] <zyga> shuduo: this is a bad week to try this because of MWC and EW trade shows both allocating lots of people away from their normal work
[08:22] <zyga> shuduo: but I'll try to find where the kernel lives
[08:22] <zyga> dholbach: hey, do you know where the source for kernel snaps live? (pi2)
[08:22] <dholbach> good morning
[08:22] <dholbach> hey zyga
[08:22] <dholbach> no idea - ppisati should probably know
[08:23] <dholbach> or ogra_
[08:23] <zyga> dholbach: we should put this into the topic of the channel
[08:23] <zyga> dholbach: a small wiki page with essential snapy hacker links
[08:23] <zyga> dholbach: +1/-1?
[08:23] <noizer> I've done everything to the point of building
[08:23] <zyga> dholbach: ogra is on EW, won't respond for a week
[08:23] <noizer> zyga that was the last thing I've done
[08:23] <zyga> noizer: ok cd $GOPATH/src/github.com/ubuntu-core/snappy/cmd/snap
[08:23] <zyga> noizer: go build
[08:23] <zyga> noizer: if that works you're 99% there
[08:24] <noizer> ok done that
[08:24] <zyga> noizer: built fine?
[08:24] <zyga> noizer: you can try ./snap --help
[08:25] <zyga> noizer: just as a sanity check
[08:25] <shuduo> zyga: or i can iterate 15.04 ... but make a few sense. :)
[08:25] <zyga> shuduo: no, use 16.04
[08:25] <noizer> zyga that works fine
[08:25] <zyga> noizer: clone my devscripts somewhere please (github.com/zyga/devscripts)
[08:25] <zyga> er
[08:25] <zyga> devtools
[08:25] <zyga> sorry
[08:25] <zyga> http://github.com/zyga/devtools
[08:26] <dholbach> zyga, sounds good - feel free to add it to https://wiki.ubuntu.com/Snappy/
[08:26] <zyga> dholbach: thanks, will do
[08:27] <dholbach> zyga, maybe on http://people.canonical.com/~ppisati/ somewhere?
[08:27]  * dholbach shrugs
[08:27] <zyga> dholbach: well, _maybe_ :D
[08:27] <zyga> in that pile over there ;)
[08:28] <zyga> noizer: then make sure you have a compatible ssh config (look at the README.md file) -- you must be able to login to your device with ssh snappy-pi2
[08:28] <noizer> zyga i've downloaded it
[08:28] <zyga> noizer: if not, tweak your ssh config
[08:28] <zyga> noizer: if you have to, build a new image (you can use the ubuntu-image script from the same repo to get one)
[08:28] <zyga> noizer: (just make sure to build a developer image with your ssh keys inside)
[08:28] <zyga> noizer: run the ubuntu-image script without arguments to do that
[08:29] <noizer> zyga ow does i need to build it on my rpi2 the snappy image?
[08:29] <zyga> noizer: nope
[08:29] <noizer> okey :D
[08:29] <zyga> noizer: on your usual computer
[08:29] <noizer> where does i need to set the config for my ssh then?
[08:30] <zyga> noizer: ~/.ssh/config
[08:30] <zyga> noizer: you have to be able to run 'ssh snappy-pi2' and login to your device without any prompts
[08:31] <zyga> noizer: https://github.com/zyga/devtools#ssh-configuration
[08:33] <noizer> the ssh does need to changed on my rpi2 but what does needs to run on my rpi2?
[08:38] <noizer> zyga I don't understand it completely
[08:40] <noizer> Where exactly does i need to change the ssh config file?
[08:40] <noizer> on my own device?
[08:42] <zyga> noizer: yes
[08:42] <zyga> noizer: everything I said so far happens on your host device
[08:43] <noizer> zyga ok busy with it
[08:43] <zyga> kk
[08:44] <zyga> ppisati: hey, do you happen to know where the sources for kernel snap for pi2 are?
[08:44] <ppisati> zyga: i know where the source for the kernel are
[08:45] <zyga> ppisati: how are they built to a kernel snap?
[08:45] <zyga> ppisati: with snapcraft or manuall?
[08:45] <zyga> manually?
[08:45] <ppisati> zyga: i think still manually
[08:45] <zyga> ppisati: can you share that, I'm collecting the knowledge and I could use the links and simple instruction
[08:45] <zyga> ppisati: plus it will help me with my skills work
[08:46] <ppisati> zyga: ask mvo or sergiuns they are building these snaps
[08:46] <zyga> ah, cool, will do, thanks
[08:46] <noizer> ssh: Could not resolve hostname pi2-1.lan: Name or service not known
[08:47] <zyga> noizer: have you read what I wrote in the readme file?
[08:47] <zyga> "Put something similar to your ~/.ssh/config file. Do change bbb-1.lan and pi2-1.lan to an appropriate hostname (or IP address) that is valid in your setup."
[08:47] <zyga> to quote ^^
[08:47] <noizer> auwtch lol
[08:47] <noizer> just read it xD
[08:48] <noizer> does it need to be a raspberry pi with an os on it?
[08:50] <zyga> noizer: yes, build the OS with the ubuntu-image script first
[08:50] <zyga> noizer: copy it to an SD card (dd the whole image)
[08:50] <zyga> noizer: and boot your pi
[08:50] <zyga> noizer: make sure you can log in first
[08:50] <zyga> noizer: (1) flash (2) setup ssh and login (3) use refresh-bits.sh script to do other stuff
[08:52] <noizer> I need to make the devel image?
[08:52] <zyga> yep
[08:52] <zyga> to be able to log in without a password
[08:53] <zyga> it just puts your public ssh key in ~ubuntu/.ssh/authorized_keys
[08:55] <noizer> zyga wait a minute just need to install some deps first
[09:01] <noizer> wtf i did make image and got very strange thing with my VM
[09:16] <noizer> zyga http://imgur.com/lKrYoEK
[09:22] <zyga> noizer: I have no idea what that is, maybe your machine is broken somehow
[09:24] <noizer> rebooted it and try again zyga :p
[09:26] <noizer> dammed the .ssh file not found
[09:27] <zyga> noizer: it is a directory, just create it
[09:27] <noizer> ok
[09:28] <zyga> noizer: and make an ssh key
[09:28] <zyga> noizer: ssh-keygen -t rsa
[09:30] <zyga> mvo: hey, can you please point me to the source of pi2 kernel snap
[09:30] <zyga> mvo: and perhaps instructions on how to rebuild it
[09:43] <zyga> dholbach: I've added a link to https://wiki.ubuntu.com/Snappy
[09:43] <dholbach> awesome :)
[09:46] <mvo> zyga: here is the script that builds the kernel snap http://bazaar.launchpad.net/~mvo/snappy/mksnap-os-kernel/view/head:/mk-kernel-rpi2.sh - note that it get the actual kernelfrom  http://cdimage.ubuntu.com/ubuntu-core/daily-preinstalled/curren
[09:48] <zyga> woot, thanks mvo
[10:12] <mvo> zyga: could you please re-merge your two pending branches with master? this should fix the integration test failures
[10:13] <mvo> zyga: ups, three
[10:16] <zyga> mvo: sure
[10:40] <zyga> mvo: done, pushed now
[11:06] <noizer> zyga sorry for the delay but know i can ssh to my rpi2 with ssh snappy-pi2
[11:06] <noizer> zyga what should i need to do now?
[11:07] <noizer> i did now ./refresh-bits.sh on my host computer
[11:11] <zyga> noizer: cool, so now you can do two things:
[11:12] <zyga> noizer: you can use refresh-bits.sh to push new snap, snappy and snapd
[11:12] <zyga> noizer: you can use setup and run-snapd to run snapd that you've built on the board
[11:12] <zyga> noizer: now what you want to do is to go to $GOPATH/src/github.com/ubuntu-core/snappy
[11:12] <zyga> noizer: and do this:
[11:13] <zyga> git remote add zyga https://github.com/zyga/snappy.git
[11:13] <zyga> noizer: git fetch zyga
[11:13] <zyga> noizer: git checkout zyga/skills-demo-i2c
[11:13] <zyga> noizer: with that you will have my development branch
[11:13] <zyga> noizer: then re-run refresh-bits with all arguments (setup snap snappy snapd run-snapd)
[11:14] <zyga> noizer: then ssh into the board and run sudo ./snap experimental
[11:14] <zyga> NOTE: ./snap not snap
[11:14] <zyga> noizer: then you should be good to go for the next step
[11:15] <zyga> noizer: you should see a bunch of extra commands for working with skills
[11:16] <noizer> something goes wrong :s will send you what I done
[11:17] <noizer> http://pastebin.com/mWdaGdAx
[11:17] <noizer> zyga
[11:19] <zyga> noizer: refresh-bits.sh --pi2
[11:20] <zyga> noizer: use --pi2 to work against a raspberry pi
[11:20] <zyga> noizer: by default it tries to talk to a VM running localy
[11:20] <zyga> locally
[11:20] <noizer> ok that worked
[11:21] <zyga> noizer: now you can add an i2c skill using:
[11:22] <noizer> the snap file where is it on my rpi2?
[11:22] <zyga> noizer: in ~/
[11:22] <noizer> because you said I need to do sudo ./snap
[11:22] <zyga> noizer: in the home directory of the ubuntu user
[11:22] <noizer> ooh ok xD
[11:22] <zyga> noizer: refresh bits copies it
[11:23] <noizer> ist need to be in /home/ubuntu?
[11:23] <zyga> noizer: ?
[11:24] <noizer> the snap file to execute ./snap
[11:24] <noizer> on my rpi2
[11:24] <zyga> noizer: if it's not then refresh-bits didn't work
[11:24] <zyga> noizer: read the code of refresh bits
[11:24] <zyga> noizer: it just copies it there
[11:25] <zyga> sudo ./snap experimental add-skill ubuntu-core i2c i2c --label="I2C controller" -a device=i2c-1
[11:26] <zyga> noizer: ^^ this should add the i2c skill to the ubuntu-core snap
[11:26] <zyga> noizer: now you need something that wants to use this skill
[11:26] <zyga> noizer: ping me with more details once you have that
[11:26] <noizer> zyga just it wont copy it http://pastebin.com/Fus2JEH0
[11:28] <zyga> noizer: you have to use --pi2 with other arguments
[11:29] <zyga> noizer: ./refresh-bits.sh --pi2 snap snappy snapd setup run-snapd
[11:29] <zyga> noizer: :)
[11:29] <noizer> haha fail fromme xD
[11:32] <noizer> weird he does not find go
[11:32] <zyga> mvo, fgimenez: do you think that https://github.com/ubuntu-core/snappy/pull/478 failure is related to the change in the branch or is that some kind of fluke
[11:33] <fgimenez> zyga, mvo it seems to be the same as http://pastebin.ubuntu.com/15126149/, not related to the changes in the branch IMO
[11:34] <zyga> fgimenez: thanks
[11:34] <mvo> fgimenez: aha, thanks
[11:36] <fgimenez> mvo, zyga i'll try to check if the sync call before installing the snaps mitigates it, otherwise i'm totally lost with this one, no idea where can it come from
[11:38] <zyga> fgimenez: I wonder how two other branches I refreshed at the same time made it
[11:39] <zyga> fgimenez: maybe one of the jenkins slaves is just odd
[11:39] <zyga> fgimenez: integration tests passed elsewhere
[11:39] <noizer> zyga got the following error :s http://pastebin.com/W5QyLwru
[11:40] <fgimenez> zyga, yes it's random, in fact the tests are executed in pristine cloud instances, they should be the same for all the executions, the slaves are not involved in the results once the testbeds are up
[11:40] <zyga> fgimenez: then I have no idea what might be the cause
[11:41] <zyga> noizer: you need to install cross toolchain: https://github.com/ubuntu-core/snappy/blob/master/docs/cross-build.md
[11:41] <zyga> noizer: just the sudo parts there, the rest is handled by the script
[11:41] <fgimenez> zyga, we have also this one http://paste.ubuntu.com/15169442/ which is randomly failing too, maybe they are related, both fail trying to install a snap from the filesystem, one of them doesn't find snap.yaml and the other find it full of '\x00'
[11:43] <zyga> mmmm
[11:43] <zyga> maybe a race that's unfortunate somewhere
[11:43] <zyga> fgimenez: how long have you been seeing those?
[11:44] <fgimenez> zyga, since last thursday i think
[11:57] <beuno> jdstrand, ack, will do
[12:28] <pindonga> jdstrand, hi there.. I'll do the deploy today
[12:30] <noizer> zyga ok everything is done xD
[12:30] <noizer> So now I can acces and read the value of my gpio?
[12:58] <noizer> zyga can i use snapcraft then again for building my snap with you skill?
[13:09] <zyga> noizer: you can build a snap but don't use the skills syntax yet, it's not allowed for now, you can just add the skill (and skill slot) after the snap is installed
[13:09] <zyga> noizer: please look at the bool-file skill
[13:09] <zyga> noizer: snap experimental add-skill
[13:10] <zyga> the skill can live on the ubuntu-core snap, it's not important
[13:10] <zyga> noizer: the skill slot (the thing that actually uses it) needs to be on your snap
[13:10] <zyga> noizer: that's snap experimental add-skill-slot
[13:11] <zyga> noizer: bool-file needs the "path" attribute -a path=/sys/class/gpio/gpio123/value
[13:11] <zyga> noizer: then you need to grant the skill (snap grant)
[13:11] <zyga> noizer: and then snap experimental apply-skill-security
[13:11] <zyga> noizer: then you can inspect the state of the system
[13:11] <zyga> noizer: more in a moment
[14:22] <ysionneau> http://pastebin.com/yPELZ2Bi < any idea why I get an error on this package.yaml?
[14:22] <ysionneau> (I'm using snapcraft 1.0.2, snappy 15.04)
[14:49] <zyga> ysionneau: looks like last line needs to change
[14:50] <zyga> I don't remember the 15.04 syntax though
[14:50] <zyga> look at some examples from snapcraft sources
[14:51] <ysionneau> yes that's what I did
[14:51] <ysionneau> http://bazaar.launchpad.net/~snappy-dev/snappy-hub/snappy-examples/view/83/hello-world/meta/package.yaml
[14:52] <ysionneau> but, I kind of get it now
[14:52] <ysionneau> those file need to exist before building?
[14:52] <ysionneau> how can I do the same for binaries generated by the build?
[14:53] <zyga> no, they don't have to exist, I think
[14:54] <zyga> ysionneau: notice that there "binaries" is a list of objects
[14:55] <zyga> ysionneau: so try "- hello:\n\tname: hello"
[14:55] <zyga> ysionneau: so that "hello" is the binary
[14:59] <ysionneau> hummm :o
[14:59] <ysionneau> you mean
[15:00] <ysionneau> binaries:\n\tname: hello
[15:00] <ysionneau> ?
[15:01] <zyga> no
[15:01] <zyga> try what I said
[15:01] <zyga> biaries:
[15:01] <zyga>   - hello:
[15:02] <zyga>     name: hello
[15:02] <zyga> (perhaps more indent)
[15:02] <ysionneau> Issues while validating snapcraft.yaml: [{'hello': None, 'name': 'hello'}] is not of type 'object'
[15:02] <zyga> the error you got was essentially that your binary was not a python dict, you have to make the yaml look right, so that each binary is a python dict/javascript/json object
[15:02] <ysionneau> oh
[15:03] <zyga> can you pastebin the snapcraft yaml again
[15:03] <ysionneau> yes
[15:03] <ysionneau> http://pastebin.com/mkU1nFXc
[15:06] <zyga> hmmm
[15:06] <zyga> maybe the syntax changed again, ask sergio when he's around
[15:06] <ysionneau> ack
[15:06] <ysionneau> thanks! :)
[15:06] <zyga> I know how it works in 16.04
[15:06] <zyga> I don't remember 15.04
[15:06] <ysionneau> no problem
[15:06] <zyga> (BTW: Try 16.04 instead if you can)
[15:06] <ysionneau> for now I prefer to stay on 15.04
[15:08] <noizer> zyga I've build my snap again. but now how can i add the skill to it?
[15:09] <zyga> noizer: currently only at runtime, I'm working on reading those from the snap.yaml file
[15:09] <zyga> noizer: have a look at some of my notes for a quick idea:
[15:09] <zyga> # Add skills, grant and apply
[15:09] <zyga> sudo ./snap experimental add-skill ubuntu-core i2c i2c --label="I2C controller" -a device=i2c-1
[15:10] <zyga> sudo ./snap experimental add-skill-slot pi2-piglow i2c i2c --label="I2C controller connected to piglow" --app=foreground --app=background
[15:10] <zyga> sudo ./snap grant ubuntu-core:i2c pi2-piglow:i2c
[15:10] <zyga> sudo ./snap experimental apply-skill-security pi2-piglow
[15:10] <zyga> noizer: this works with this snap: http://github.com/zyga/snappy-pi2-piglow
[15:10] <noizer> ok thx
[15:10] <zyga> noizer: explore each of those commands with --help to understand what's going on
[15:11] <noizer> ok
[15:11] <zyga> noizer: you can also fetch the code of that snap I just linked to, enable classic mode on your pi, install git and snapcraft and build it there
[15:11] <zyga> noizer: the snap is specific to piglow but the parts that deal with i2c are generic
[15:11] <zyga> noizer: and you should be able to see what's going on
[15:12] <zyga> noizer: note that in my branch, skills are not persistent yet so after you reboot the device they are gone
[15:12] <zyga> noizer: but apply-skill-security is persistent
[15:12] <zyga> noizer: though this will all change to just work as soon as some prerequisites land in 16.04
[15:12] <zyga> noizer: so all the hackery won't be needed
[15:13] <noizer> ok first i will try it with my snap ist just checking the value's from the gpio's
[19:00] <jdstrand> sergiusens: hi! I was going to attach a suggested diff to bug #1546821, but see you may be working on it already. here is what I was thinking: http://paste.ubuntu.com/15182501/
[19:00] <jdstrand> sergiusens: adjust as necessary and thanks for working on it
[19:01] <jdstrand> sergiusens: I've got a review tools update that will require squashes be created in this manner that I'll what on until there is a new snapcraft
[19:01] <jdstrand> s/what/wait/
[19:13] <sergiusens> jdstrand, thanks! the -all-root I have been procastinating on, you just pushed me to get it done ;-)
[19:13] <jdstrand> :)
[19:26] <sergiusens> jdstrand, https://github.com/ubuntu-core/snapcraft/pull/334
[19:32] <jdstrand> thanks
[19:51] <jdstrand> pindonga: hey, so, fyi, r594 and below is ok to pull. r595 you can pull, but the tools will add a 'warn'ing until the machine running the tools has a squashfs-tools that supports -fstime
[19:51] <pindonga> jdstrand, I bumped to 592 today
[19:51] <jdstrand> ok that's fine
[19:51] <pindonga> but deploy didn'th appen yet
[19:52] <pindonga> bc no webops coverage
[19:52] <pindonga> so might happen tomorrow
[19:52] <pindonga> I can bump to 594/5 if you like
[19:52] <jdstrand> pindonga: but that brings up the question-- how do we get an updated squashfs-tools on the system running review tools?
[19:53] <jdstrand> pindonga: (593 and 594 aren't worth an update, they can come with 595+)
[19:53] <pindonga> it should be picked up automatically during the next rollout I believe, bc afaict we don't have it pinned
[19:53] <pindonga> but follow whatever's there in the distro
[19:53] <jdstrand> pindonga: what is that machine running? 14.04?
[19:53] <pindonga> yep
[19:53] <pindonga> and will do so for the foreseeable future
[19:53] <jdstrand> sure
[19:54] <pindonga> :)
[19:54] <jdstrand> pindonga: does it pull from any other sources?
[19:54] <pindonga> deb source?
[19:54] <sergiusens> elopio, you might need to rebase https://github.com/ubuntu-core/snapcraft/pull/326
[19:54] <jdstrand> trying to decide if I need to do an SRU or if this can be an internal thing
[19:54] <pindonga> jdstrand, I think we can have some cat
[19:54] <pindonga> repo
[19:54] <jdstrand> pindonga: no, like internal IS archives
[19:55] <pindonga> jdstrand, right, so a trusty-cat should work right?
[19:55] <pindonga> jdstrand, let's get 592 out of the way first (bc the changeset is quite big already)
[19:55] <jdstrand> pindonga: that is what I was thinking, but I've not done this sort of thing
[19:55] <jdstrand> pindonga: yes, please push 592 outside of this
[19:55] <pindonga> and then we'll see how to get squashfs-tools updated + newer revnos
[19:55] <pindonga> but I think trusty-cat should work
[19:56] <jdstrand> ok, let me talk to some folks
[19:56] <jdstrand> and I'll see how I can get a trusty-cat going
[20:00] <pindonga> jdstrand, ok, yes, we got trusty-cat available
[20:01] <pindonga> so if you can land there, it should be "easy" to get it installed
[20:01] <jdstrand> ok, thanks. talking to IS
[20:08] <pindonga> jdstrand, which version do we need?
[20:47] <sergiusens> jdstrand, I can swear I saw a comment from you here https://github.com/ubuntu-core/snapcraft/pull/334
[21:57] <sergiusens> camako, https://bugs.launchpad.net/snapcraft/+bug/1541620/comments/4
[21:57] <sergiusens> camako, sorry for taking so long; but it seems you are just missing a stage-package in there
[21:58] <sergiusens> camako, also, this may mean the server needs a dep against the client-dev
[22:17] <jdstrand> sergiusens: I did make one :)
[22:18] <jdstrand> I don't know where it went...
[22:19] <jdstrand> I re-acked it just now
[22:19] <jdstrand> pindonga: ok, based on conversations with is, I'm pursuing an SRU. I'd probably want to anyway so this seems fastest overall.
[22:20] <jdstrand> pindonga: fyi, bug #1548988