[00:00] <kyrofa> enoch85, works for me-- I have a working apache
[00:00] <enoch85> kyrofa, cool! :D
[00:01] <rickspencer3> arg
[07:33] <dholbach> good morning
[07:33] <dholbach> kyrofa: shall I upload snapcraft 1.0 to regular xenial (not the ppa) for you?
[07:34] <dholbach> mvo: do we want to change our docs on developer.u.c to mention 16.04 at some stage?
[07:36] <mvo> dholbach: I think so, especially now that some changes are in the pipeline that will appear really soon. the whole system a/b stuff is obsolete and replaced by all-snaps for example. some environment varialbles are simplified
[07:36] <mvo> etc
[07:37] <dholbach> mvo: the a/b stuff and the environment variables are part of snappy/docs, right?
[07:45] <mvo> dholbach: yes, the docs are not updated yet though, I put that on the todo
[07:47] <dholbach> ok
[07:47] <dholbach> and for developer.ubuntu.com/snappy/start - what would you suggest?
[07:47] <dholbach> that we advertise which 16.04 channels?
[07:48] <dholbach> do you know if 16.04 images for all different "targets" are built by us already?
[07:57] <dholbach> mvo: ok, let's chat about it in a bit - I'll relocate to the office - brb
[07:57] <mvo> dholbach: unfortunately not, we are transitioning the images right now and expect to have new images based on the all-snap architecture by the end of the week. at least for rpi2 and amd64
[07:57] <mvo> dholbach: see you
[07:58] <dholbach> ok cool - I'll file a bug so we can track the work
[07:58] <dholbach> thanks
[08:28] <dholbach> mvo: I filed https://bugs.launchpad.net/developer-ubuntu-com/+bug/1533099
[09:18] <zyga> good morning
[09:18]  * zyga works on capability type interface, so that everything is an API, not a DSL
[09:38]  * zyga thinks loudly: cap.Capability refers to cap.Type (iface) which can be a concrete BoolFileType which has interface methods for things like "grant permission(cap, snap)" "revoke permission(cap, snap)", internally the type will also know about snippets of seccomp/apparmor and will hand them out to security systems on demand
[09:59] <JamesTait> Good morning all; happy Tuesday, and happy Poetry At Work Day! 😃
[10:58] <LefterisJP> Hey guys, is DBUS the only way that a framework's service can listen to requests from the outside world (other snapps)?
[11:00] <zyga> LefterisJP: you can also use other sockets
[11:00] <zyga> LefterisJP: but security gets more complicated then
[11:02] <enoch85> ok kyrofa I'm here now
[11:04] <LefterisJP> zyga: I have an app that listens on plain unix sockets, which I need to have as the main daemon service of the framework. Are there any examples where such framework communication is achieved?
[11:05] <zyga> LefterisJP: I think mir would be one
[11:05] <zyga> LefterisJP: you'll need some extra security to handle other people talking to that socket
[11:08] <LefterisJP> zyga: Which of these repos is the framework? https://code.launchpad.net/~mir-team/mir/
[11:09] <LefterisJP> zyga: Any examples of what kind of extra security I would need to take care of, or well .. if the mir guys do that somewhere in code I could just look at that.
[11:10] <zyga> LefterisJP: you need extra apparmor permissions to let other people talk to your socket
[11:10] <zyga> LefterisJP: I'm sorry, I'm not sure where the mir snapcraft file is
[11:13] <LefterisJP> zyga: It's okay. It's already something good to know that I don't need to use Dbus. I thought I would have to make an extra service to read DBUS and write to that unix socket inside the framework. I will try to look at the apparmor documentation to see how to allow for this communication.
[11:13] <LefterisJP> If anyone has any tips/links I would be more than glad to have them
[11:20] <zyga> LefterisJP: I suggest looking for anything that uses mir in snappy
[11:27] <LefterisJP> zyga: Thank you will do and will come back here with more questions if I got any.
[12:52] <bellyfeel> does anyone have a link to the 16.04 image?
[12:54] <Chipaca> bellyfeel: which 16.04 image?
[12:55] <bellyfeel> rolling
[12:56] <Chipaca> bellyfeel: yeah, but there are a number. Maybe you want https://cloud-images.ubuntu.com/snappy/rolling/core/edge/current/ ?
[12:56] <bellyfeel> i'll check it out, thanks!
[12:56] <Chipaca> bellyfeel: or maybe you want to just use: sudo ubuntu-device-flash core rolling --channel edge --oem generic-amd64/stable --enable-ssh --output rolling_edge_amd64.img
[13:12] <icey> has anybody figured out how to run the maas controller on snappy?
[13:12] <icey> or thought about it?
[13:17] <kyrofa> dholbach, yes please!
[13:17] <kyrofa> enoch85, woo you beat me by a few hours. You still here?
[13:17] <dholbach> kyrofa: done
[13:17] <enoch85> kyrofa, yes :)
[13:18] <enoch85> kyrofa, so you got the apache up and running?
[13:18] <kyrofa> enoch85, I did. Shall we take this private?
[13:18] <kyrofa> dholbach, thank you!
[13:18] <enoch85> kyrofa, ok
[13:18] <dholbach> anytime
[13:43] <kyrofa> mvo, what is the state of classic?
[13:56] <kyrofa> sergiusens, did you ever send out that announcement email?
[14:01] <sergiusens> kyrofa, yeah, yesterday, it is all over the ubuntu and ubuntudev google plus and twitter accounts ;-)
[14:01] <sergiusens> kyrofa, and I pinged you here iirc, did I not?
[14:01] <sergiusens> kyrofa, are you and snappy-app-devel?
[14:01] <kyrofa> sergiusens, yeah you did, but I must not be on the right mailing list!
[14:02] <kyrofa> sergiusens, I thought I was. Guess not :P
[14:02] <kyrofa> sergiusens, now I am *cough*
[14:02] <sergiusens> kyrofa, https://plus.google.com/107265043789873157543/posts/DBonvXp7nen
[14:03] <kyrofa> sergiusens, very good :)
[14:11] <sergiusens> kyrofa, do you mind helping Fazer with a proper rebase?
[14:12] <kyrofa> sergiusens, love to
[14:15] <sergiusens> kyrofa, whose untriagle?
[14:15] <kyrofa> sergiusens, davidcalle
[14:16] <davidcalle> o/
[14:17] <sergiusens> davidcalle, mind doing a git commit --amend for https://github.com/ubuntu-core/snapcraft/pull/218 and putting LP: #XXXXX in there?
[14:17] <sergiusens> davidcalle, asking so you are not forced to rebase once my doc changes land (and I am instead) ;-)
[14:18] <bellyfeel> is there a way to build a snap using snapcraft without installing the dependencies?
[14:20] <kyrofa> bellyfeel, which dependencies?
[14:21] <bellyfeel> I might be getting confused about the snapcraft cycle but I have a list of packages in stage-packages that get downloaded and installed while doing a snapcraft build
[14:21] <bellyfeel> i only want them to be installed on my device after the snap is built
[14:21] <kyrofa> bellyfeel, ah
[14:21] <kyrofa> bellyfeel, but where do they come from on the device?
[14:21] <kyrofa> bellyfeel, your snap :)
[14:21] <kyrofa> bellyfeel, which means they must be downloaded and put into the snap to create it in the first place
[14:23] <davidcalle> sergiusens: git status
[14:23] <davidcalle> sergiusens: lol, sorry
[14:23] <davidcalle> Wrong window
[14:23] <bellyfeel> ok downloading is fine but it looks as if I'm having collisions with packages on my dev machine with packages that should go on my device
[14:23] <bellyfeel> with aptitude
[14:24] <kyrofa> bellyfeel, that should definitely not be happening
[14:24] <elopio> kyrofa: can you help this guy with the rebase? https://github.com/ubuntu-core/snapcraft/pull/217
[14:24] <kyrofa> bellyfeel, stage-packages are downloaded and unpacked only in parts/<name>/ubuntu and parts/<name>/install
[14:24] <kyrofa> elopio, yeah I'm typing it out now
[14:24] <elopio> thanks :)
[14:25] <kyrofa> bellyfeel, what sort of collisions are you seeing?
[14:25] <bellyfeel> I think it might have something to do with 32bit dependencies
[14:25] <bellyfeel> so for instance binutils:i386
[14:26] <bellyfeel> snapcraft gives me a "failed doing pull for device: binutils:i386"
[14:27] <bellyfeel> no other output information is given, so I tried running aptitude by itself
[14:28] <kyrofa> bellyfeel, please pastebin the entire log, let me have a look
[14:28] <bellyfeel> snapcraft log?
[14:28] <kyrofa> bellyfeel, yeah, where you see the error
[14:28] <bellyfeel> ok
[14:31] <elopio> kyrofa: sergiusens: no standup today?
[14:32] <kyrofa> elopio, no I'm just slow
[14:44] <sergiusens> elopio, kyrofa ah, more slots have been added http://ubucon.org/en/events/ubucon-summit-us/schedule/ ; the lightning talk is 15 minutes, probably 10 gven setup and such :-)
[14:44] <kyrofa> sergiusens, whew
[14:44] <elopio> sergiusens: maybe 5, to answer questions :)
[14:46] <davidcalle> sergiusens: I think I've successfully amended the commit, but being new to git, please check I've made no mistakes, I had to try several times before git let me push it :)
[14:47] <kyrofa> davidcalle, since you amended, you probably had to force push yes?
[14:47] <bellyfeel> kyrofa, pastebin.com/Vp7uGRgw
[14:47] <kyrofa> davidcalle, that's normal, since your history and github's history officially "diverged"
[14:48] <kyrofa> Gahh, rolling is so broken
[14:49] <davidcalle> kyrofa: ok, just trying to get the hang of the git workflow, which feels a bit alien when coming from bzr :)
[14:51] <kyrofa> davidcalle, no problem, we understand!
[14:53] <mvo> kyrofa: rolling is broken in what way?
[14:54] <kyrofa> mvo, http://pastebin.ubuntu.com/14478142/ . Any thoughts?
[14:55] <mvo> kyrofa: uh, that should not have been imported
[14:55] <kyrofa> mvo, hahaha
[14:55] <mvo> kyrofa: I disabled the importing monday
[14:55] <mvo> kyrofa: thats really anyoing
[14:55] <mvo> kyrofa: sorry for this
[14:56] <kyrofa> mvo, hey, it's rolling. Not supposed to be perfectly stable :)
[14:56] <kyrofa> davidcalle, looks like you played a merge game of some kind to make git happy
[14:57] <mvo> kyrofa: well, this change breaks stuff left and right. what kind of image is that? a normal snappy rolling edge or did you copy snappy on it manually or something?
[14:57] <kyrofa> davidcalle, you should squash up and force push
[14:57] <mvo> kyrofa: if its not the snappy of the image I will stop panicing
[14:57] <kyrofa> mvo, it's a canonistack VM created from the rolling edge image
[14:57] <mvo> kyrofa: hm, thats bad
[14:58] <kyrofa> mvo, want SSH?
[14:59] <mvo> kyrofa: no, its fine
[14:59] <kyrofa> davidcalle, I just walked another PR author through it if you want a reference: https://github.com/ubuntu-core/snapcraft/pull/217
[15:00] <kyrofa> davidcalle, just remember, if you change history, you'll need to push with --force
[15:01] <davidcalle> kyrofa: ah, excellent, thanks
[15:03] <mvo> kyrofa: thanks for letting me know!
[15:03] <elopio> fgimenez: I have a meeting with Iftikhar and Jibel during our slot. Do you want to move it or cancel it today?
[15:05] <kyrofa> mvo, no problem!
[15:09] <fgimenez> elopio, np, i think we can cancel, my report: the jenkins swarm thing is almost done, i hope to have it finished for today
[15:09] <elopio> fgimenez: yay.
[15:19] <mvo> kyrofa: could you please try to upgrade your image?
[15:19] <kyrofa> mvo, just a snappy update?
[15:19] <kyrofa> mvo, or a new image?
[15:20] <mvo> kyrofa: I think a snappy update should help, not sure if it is available yet
[15:20] <mvo> but should be soon
[15:20] <kyrofa> mvo, trying now, it's applying something anyway
[15:20] <mvo> kyrofa: yay, lets see if stuff is normal after a reboot
[15:32] <mvo> kyrofa: is it looking better?
[15:33] <kyrofa> mvo, oops sorry, it took a minute to reboot and I saw a squirrel
[15:33] <kyrofa> mvo, yep! All fixed :)
[15:33] <kyrofa> mvo, thank you!
[15:34] <mvo> kyrofa: \o/ thanks! sil2100 saved the day with his system-image superpowerz
[15:34] <kyrofa> mvo, heh, awesome :)
[15:38] <bellyfeel> is there a way to get more verbose output from snapcraft
[15:45] <kyrofa> bellyfeel, I'm sorry, I missed your pastebin above
[15:46] <kyrofa> bellyfeel, my initial assumption is that Snapcraft is not using the i386 sources
[15:46] <kyrofa> bellyfeel, you should try running this on an i386 host (virtualized is fine)
[15:47] <renat> Hi all! It's Renat from Screenly. Yes, again me with my questions=)
[15:47] <kyrofa> Hey renat :)
[15:47] <renat> kyrofa, hi!=)
[15:47] <renat> So - the question is Raspberry Pi /dev/vchiq device relateed
[15:49] <renat> We created a snap which should use that device to display an interface with OpenGL ES. So - I do snappy hw-assign, and then I can run that snap from the root user. It fails when I try to run it from the ubuntu user, or If I try to run it as a service.
[15:49] <renat> Perhaps, because of /dev/vchiq access rights
[15:49] <renat> crw------- 1 root root
[15:51] <renat> Is it right settings for that device? I believe that display devices should be accessible from any snap, if access granted by the hw-assign.
[15:54] <kyrofa> renat, I'd normally refer you to ogra, but he's out until the 16th
[15:56] <renat> kyrofa, thanks. I will create a bug report in hope that he will see it.
[15:57] <kyrofa> renat, yeah good idea
[16:03] <pindonga> elopio, hi there... got any ETA for when https://github.com/ubuntu-core/snapcraft/pull/202 will get merged?
[16:07] <sergiusens> pindonga, he needs a review from his QA colleagues last I heard
[16:08] <sergiusens> kyrofa, did you see elopio's pings to you in the docs review?
[16:08] <sergiusens> davidcalle, you seem to have forgotten to squash
[16:09] <kyrofa> sergiusens, oh, no, reading now
[16:09] <pindonga> sergiusens, care to explain the rationale for squashing all the work into a single commit?
[16:10] <pindonga> I think I need to do that on my PR
[16:10] <sergiusens> pindonga, I'll let kyrofa do that since he is better versed in that
[16:10] <sergiusens> pindonga, I have 2 reasons, easier to cherrypick and easier to revert
[16:10] <kyrofa> pindonga, are you familiar with `git blame`?
[16:11] <pindonga> kyrofa, the same as bzr blame right? :)
[16:12] <kyrofa> pindonga, ah, yeah same purpose. So you get a line-by-line "this is who made this change and why"
[16:12] <kyrofa> If you didn't squash into a feature commit, some of those "whys" would be "crap, forgot this."
[16:12] <pindonga> well, but that's the truth :)
[16:12] <kyrofa> pindonga, hahaha
[16:13] <kyrofa> But then it would require more digging. "Well, what feature was this a part of?"
[16:13] <pindonga> k
[16:13] <kyrofa> pindonga, when you're developing a feature, checkpoint commits and good and healthy
[16:13] <kyrofa> But when your feature is done, checkpoint commits have no place in a project history
[16:14] <kyrofa> For the reasons I mentioned as well as cherry-picking and reverting reasons mentioned by sergiusens among others I'm sure
[16:14] <pindonga> kyrofa, I differ somewhat, but that's not the issue here, I appreciate you explaining me the reasons
[16:14] <pindonga> am happy to follow the defined process
[16:15]  * pindonga goes squash his commits
[16:16] <kyrofa> pindonga, yeah you can imagine how squashing might get out of hand
[16:16] <kyrofa> pindonga, but that's why we try to keep our features as small as possible
[16:16] <kyrofa> pindonga, which also lends itself well to the reasons above
[16:16] <pindonga> kyrofa, also it's mainly due to a limitation of the tool at hand
[16:17] <pindonga> that doesn't show you the 'merge' commit
[16:17] <pindonga> as a unit
[16:17] <kyrofa> pindonga, it does actually, assuming it wasn't a fast forward
[16:18] <kyrofa> pindonga, but the others are also part of the history
[16:18] <kyrofa> bzr totally hides that from you
[16:18] <pindonga> right
[16:18] <sergiusens> kyrofa, I wished we had ff support on github too :-)
[16:18] <kyrofa> which is fine, just a different tool
[16:18] <pindonga> kyrofa, exactly , which is why I'm not ranting here :)
[16:18] <kyrofa> sergiusens, yeah I'm curious about the justification behind that. Gitlab does that too
[16:18]  * pindonga just prefers bzr model on this, but understand the reasons in git-world
[16:19] <kyrofa> pindonga, oh it's not taken as a rant! I'm sorry if what I'm saying is coming off that way :P
[16:19] <pindonga> no , totally not
[16:19]  * pindonga was just covering his bases :)
[16:19] <kyrofa> pindonga, heh. I appreciate your willingness to follow other workflows :) . I know this would be totally weird in bzr
[16:20] <pindonga> it's also probably bc I'm not that used to it
[16:20] <kyrofa> pindonga, understandable :)
[16:21] <kyrofa> pindonga, I came to bzr from a git background, and was frustrated by the inability to easily clean up my work
[16:25] <kyrofa> dholbach, do the developer.ubuntu.com docs handle ``` correctly?
[16:25] <dholbach> kyrofa: they should soon
[16:25] <kyrofa> dholbach, or do you need to indent as in normal markdown?
[16:26] <kyrofa> dholbach, okay
[16:26] <dholbach> we're going to use pymdown-extensions in one of our next landings
[16:27] <kyrofa> dholbach, awesome. Have you synced the 1.x docs since 1.0 was released?
[16:27] <dholbach> kyrofa: no, it's still manual until we do the landing I talked about
[16:28] <dholbach> like manual manual
[16:28] <kyrofa> dholbach, heh. Copy-paste?
[16:28] <dholbach> and convert some bits and pieces, so links work, etc
[16:28] <kyrofa> dholbach, blech, poor guy
[16:28] <dholbach> yes
[16:28] <kyrofa> dholbach, when is that landing happening?
[16:28] <dholbach> very soon
[16:28] <dholbach> we had lots of stumbling blocks along  the way
[16:29] <kyrofa> dholbach, this week very soon or this month very soon?
[16:29] <sergiusens> I did that twice on the portal, I felt like dying
[16:29] <kyrofa> sergiusens, hahaha
[16:29] <dholbach> kyrofa: I guess the latter
[16:29] <dholbach> this or next week
[16:29] <dholbach> fingers crossed and all
[16:29] <dholbach> it's been quite a bit of work
[16:30] <sergiusens> dholbach, I think kyrofa asks because of https://github.com/ubuntu-core/snapcraft/pull/221/files
[16:30] <dholbach> I'm in a hangout on air right now - I'll get back to you in a bit
[16:30] <sergiusens> dholbach, I am watching you fwiw ;-)
[16:30] <dholbach> :-)
[16:30] <dholbach> always watching me
[16:30] <sergiusens> I don't expect instant replies ;-)
[16:30] <sergiusens> lol
[16:31] <sergiusens> 1984 style
[16:31] <kyrofa> dholbach, okay, and understood! How would you feel about me copy-pasting the ROS docs? So I can point people there? Would that interfere with your landing?
[16:31] <dholbach> I think the extension I mentioned above should make ```yaml and stuff like that work
[16:31] <dholbach> if you want to update manually, feel free to
[16:31] <dholbach> it's not going to interfere
[16:32] <kyrofa> dholbach, oh sheesh, I'm sorry for interrupting you! When you get a chance, I've not done that before, I'd appreciate it if you could point me in the right direction. I'm not even sure I have permission to do something like that
[16:33] <sergiusens> kyrofa, dholbach http://stackoverflow.com/questions/7694887/is-there-a-command-line-utility-for-rendering-github-flavored-markdown
[16:33] <sergiusens> you can probably strips atom's previewer ;-)
[16:34] <sergiusens> kyrofa, also, pandoc supports github flavored markdown
[16:34] <dholbach> sergiusens: http://bazaar.launchpad.net/~dholbach/developer-ubuntu-com/rework-importer/view/head:/md_importer/importer/article.py#L50
[16:35] <dholbach> kyrofa: sure - let me add you and give you links and stuff
[16:35] <sergiusens> pandoc -f markdown_github
[16:35] <wxl> hey folks is there a 15.04 amd64 image that i can zsync or torrent? i keep having problems getting one where the checksum matches :/
[16:36] <kyrofa> sergiusens, by the way, you were spot on regarding why I was asking about that :P
[16:36] <kyrofa> sergiusens, saved you a comment
[16:37] <kyrofa> dholbach, thank you!
[16:37] <sergiusens> kyrofa, I have lost context but good to know I hit a target by accident :-P
[16:37] <elopio> pindonga: lets say end of the week. I'm fighting coveralls now, I hope that's the last one.
[16:37] <kyrofa> sergiusens, :D
[16:37] <elopio> but every change I have to wait for travis to tell me if I made something wrong. So it's slow.
[16:42] <sergiusens> jdstrand, so what was wrong in snapcraft, security-policy or security-override?
[16:47] <jdstrand> sergiusens: on 16.04, security-override
[16:47] <fgimenez> elopio, http://10.55.33.14:8080/ this is the first deployment, all the slaves come from the same xenial container
[16:48] <fgimenez> elopio, i'll propose the branch in a few minutes, let me know if we need different slaves
[17:00] <sergiusens> jdstrand, do we have any docs or guidelines so I know what to do? or a snapcraft bug report (I can write one if the info is elsewhere)
[17:09] <elopio> fgimenez: for snapcraft 1.x, we need vivid or trusty. But for now, I'm more than happy with xenial.
[17:10] <jdstrand> sergiusens: see docs/security.md in snappy git trunk
[17:11] <fgimenez> elopio, ok, it's very easy to add them, i'll put hands on it. when we switch to k8s will be even easier, and we don't need to have them around, they'll live while the job that requires them is up
[17:23] <sergiusens> jdstrand, what is an 'abstraction', have an example handy?
[17:24] <jdstrand> sergiusens: it is what's in /etc/apparmor.d/abstractions
[17:25] <sergiusens> jdstrand, the file names or the contents of those files?
[17:25] <jdstrand> file names
[17:25] <sergiusens> looks like raw apparmor
[17:25] <sergiusens> got it
[17:33] <sergiusens> jdstrand, are all four entries optional?
[17:37] <rickspencer3> hi all
[17:38] <rickspencer3> I just uploaded my rest-cam snap to the store
[17:38] <rickspencer3> I guess I can't install it from there because I am running 16.04?
[17:40] <kyrofa> rickspencer3, I thought I remembered seeing rolling as a valid channel?
[17:40] <kyrofa> rickspencer3, or edge or something
[17:40] <rickspencer3> kyrofa, yeah, I put it there
[17:40] <kyrofa> rickspencer3, oh. I figure that would have worked
[17:40] <kyrofa> rickspencer3, you too I suppose :P
[17:40] <rickspencer3> well, the bug could be between my head and the keyboard ;)
[17:43] <kyrofa> rickspencer3, I assume you don't even see it as available, correct?
[17:44] <kyrofa> rickspencer3, and the automated checks have all passed etc.?
[17:44] <rickspencer3> kyrofa, I was just told that it is not done the checks yet :)
[17:44] <kyrofa> Ahh
[17:44] <kyrofa> rickspencer3, you just move too fast. Slow down. Grab a cup of coffee or something
[17:44] <rickspencer3> kyrofa, turns out I had a bug somewhere so it didn't work
[17:45] <rickspencer3> I got too used to it "just working" :)
[17:45] <kyrofa> Heh
[18:10] <sergiusens> Chipaca, after reading kyrofa's comment about stop-timeout I read the man page and it seems we can make services wait forever to stop if I read it correctly
[18:11] <sergiusens> should it trigger manual review is my question
[18:11] <sergiusens> maybe more of a question for jdstrand
[18:16] <sergiusens> kyrofa, wrt rolling and ros, maybe check the envvars and make sure they are correct
[18:18] <kyrofa> sergiusens, yeah I will. Working on a demo now though
[18:18] <sergiusens> demo beats bug :-)
[18:18] <kyrofa> sergiusens, timelines man, timelines ;)
[18:25] <jdstrand> sergiusens: if this is a value of stop-timeout that makes the service wait forever, and we don't want to allow that, the review tools can verify the value is within approved parameters and prompt for manual review if it is outside of those values
[18:25] <jdstrand> Chipaca, sergiusens: if you'd like this change in the review tools, please file a bug
[18:25] <sergiusens> jdstrand, right, seems 0 disables it, so it is a number we don't want to allow I guess
[18:31] <kyrofa> sergiusens, what happens if you specify "0min 0s" or something similar?
[18:31] <sergiusens> kyrofa, value needs to be an int
[18:31] <sergiusens> it will likely fail in some other place
[18:32] <kyrofa> sergiusens, oh right, the yaml requires an integer okay
[18:38] <wxl> sorry for asking again, but does anyone know of a zsync or torrent available for ubuntu-15.04-snappy-amd64-generic.img.xz? i keep getting mismatched checksums
[18:49] <kyrofa> wxl, I don't know that there are any
[18:50] <kyrofa> wxl, you could always make the image yourself
[18:50] <wxl> kyrofa: well sheesh we should have one! i'd seed it bud i need to get the darn thing right, first
[18:50] <wxl> kyrofa: link me to instructions? i might have not drilled down enough for that
[18:53] <kyrofa> wxl, install ubuntu-device-flash and run sudo ubuntu-device-flash core 15.04 --channel stable --output ubuntu-15.04-snappy.img
[18:53] <kyrofa> wxl, ... I think. It's been a while :P
[18:54] <wxl> kyrofa: i'll grab ubuntu-device-flash and read the man page. thanks for the pointer in the right direction :)
[18:54] <kyrofa> wxl, sure thing :)
[19:03] <wxl> ugh sheesh how do i find the device names?
[19:04] <wxl> i would think these are them but it doesn't seem to be the case http://system-image.ubuntu.com/ubuntu-core/15.04/stable/
[19:08] <wxl> ubuntu-device-flash query --list-images --channel ubuntu-core/15.04/stable --device generic_amd64 yields several images
[19:09] <jerryG> is darren landol online?
[19:09] <wxl> oh i see. even though you use the core command you need to specific the full path of the channel (ubuntu-core/15.04/stable not 15.04/stable or just stable)
[19:09] <wxl> also, have i386 images stopped getting updated?
[19:10] <jerryG> Chipaca:  how do i check the mir socket being used?
[19:17] <sergiusens> jdstrand, and kyrofa care to check https://github.com/ubuntu-core/snapcraft/pull/222/files ?
[19:56] <sergiusens> kyrofa, I don't understand your question; as in, what you are asking is what I think subtests are for
[19:56] <sergiusens> kyrofa, removing all but one will make the test fail but validation pass
[19:59] <kyrofa> sergiusens, yeah I may not understand what's happening here. So it looks to me like you have only one app definition within self.data['apps'], whose definition seems meant to fail all four invalid combinations. No?
[19:59] <sergiusens> kyrofa, yup
[20:00] <sergiusens> kyrofa, so first I straight out validate as is in a subTest context expecting to fail
[20:00] <sergiusens> kyrofa, then I create a real copy of the dict and iterate over the three keywords removing them before a validation expecting them to fail as well
[20:01] <kyrofa> sergiusens, ahh, tricky, I missed the deletion
[20:01] <kyrofa> sergiusens, okay ignore me
[20:01] <sergiusens> it does what you ask for, we can argue about elegance
[20:01] <kyrofa> sergiusens, no argument from me :)
[20:01] <sergiusens> but I'd only se testscenarios with testtools
[20:02] <kyrofa> sergiusens, +1 from me
[20:10] <sergiusens> kyrofa, \o/
[20:24] <sergiusens> kyrofa, docs are also updated fwiw
[20:29] <jerryG> sergiusens: link plz?
[20:30] <sergiusens> jerryG, for what?
[20:31] <jerryG> sergiusens: idk. new docs
[20:31] <jerryG> sergiusens: :}
[20:31] <sergiusens> jerryG, it is just a PR, feel free to look though https://github.com/ubuntu-core/snapcraft/pull/221#discussion_r49486380
[20:31] <jerryG> sergiusens: ty
[20:38] <kyrofa> sergiusens, what is the currently recommended way to create a .snap for an arm device using snapcraft? Is classic in a state to allow that so we can do it on-device? Or a qemu VM?
[20:39] <sergiusens> kyrofa, classic
[20:39] <sergiusens> kyrofa, at least rickspencer3 has used it :-)
[20:39] <kyrofa> sergiusens, excellent. I don't suppose that's available in vivid?
[20:40] <sergiusens> kyrofa, it only rolls
[20:40] <kyrofa> sergiusens, alright thanks :)
[20:41] <kyrofa> sergiusens, rolling edge? Or 15.04?
[20:41] <kyrofa> Or do I have that backward... rolling stable? :P
[20:58] <sergiusens> kyrofa, rolling and 15.04 are the releases
[20:58] <sergiusens> stable and edge are channels
[20:58] <sergiusens> there is no stable channel on rolling
[20:58] <kyrofa> sergiusens, ah, so rolling edge is it
[20:59] <sergiusens> more so; you probably want an all snaps image
[20:59] <kyrofa> Ah, okay
[20:59] <sergiusens> kyrofa, maybe build u-d-f out of this branch https://code.launchpad.net/~snappy-dev/goget-ubuntu-touch/all-snaps/+merge/275273
[21:03] <kyrofa> sergiusens, hmm... does hw-assign need something special in the package name? I'm using the name snappy list is giving me and I'm getting "snappy package not found"
[21:05] <kyrofa> Oh... .sideload
[21:05] <kyrofa> Been a while since I used that one
[21:17] <sergiusens> kyrofa, hah
[21:17] <kyrofa> sergiusens, alright I have a demo that works outside of snappy, but within snappy I can't get permission to access the webcam, even with hw-assign. Know anything about that?
[21:17] <sergiusens> kyrofa, snappy install snappy-debug
[21:17] <kyrofa> sergiusens, I've got it-- no denials
[21:18] <sergiusens> kyrofa, not even seccomp?
[21:18] <sergiusens> kyrofa, what about running the binary from within the package and no launcher?
[21:18] <sergiusens> kyrofa, as in exec /apps/package/version/bin/my-app
[21:20] <kyrofa> sergiusens, still denied.
[21:20] <kyrofa> crw-rw---- 1 root video 81, 0 Jan 12 21:10 /dev/video0
[21:21] <sergiusens> kyrofa, oh, sudo mypackage.myapp
[21:21] <sergiusens> kyrofa, I assume service all the time
[21:21] <kyrofa> sergiusens, ROS blows up if you run as sudo :( . This works on my local machine with the same permissions-- must be a group thing?
[21:22] <kyrofa> sergiusens, I can make it a service though-- I guess it'll need to be anyway
[21:23] <sergiusens> kyrofa, it is a group thing; we just went over this the other day with jdstrand
[21:23] <sergiusens> kyrofa, add ubuntu to the video group
[21:23] <kyrofa> sergiusens, oh heh. Sorry to drag it back up
[21:23] <sergiusens> kyrofa, oh, didn't mean it like that; just that I had it fresh in my mind
[21:23] <kyrofa> sergiusens, ah, good :)
[22:49] <sergiusens> kyrofa elopio, still around? are we good to merge this https://github.com/ubuntu-core/snapcraft/pull/221
[22:49] <sergiusens> elopio, btw, do you want to have a look at this? https://github.com/ubuntu-core/snapcraft/pull/222
[22:59] <elopio> sergiusens: I'm good with #221. And you already got 2 reviews for #222, so land it when you want. I'll take a peek later.
[23:09] <sergiusens> elopio, here's one for you https://github.com/ubuntu-core/snapcraft/pull/225 but lets wait for the tests to finish just in case
[23:12] <wxl> how do you guys deal with the fact that you seem to primarily do development on github but generally bugs are being reported on launchpad? i know there's no upstream issue tracker for github on lp, so it seems like you have to fight with two totally separate systems
[23:17] <sergiusens> wxl, to be fair, the tracker in launchpad is much better
[23:17] <sergiusens> but we just do
[23:17] <sergiusens> it is not a problem
[23:18] <wxl> yeah i'm sure you get by but it's interesting, sergiusens :)
[23:57]  * tsimonq2 spots wxl :)