[00:05] <elopio> sergiusens: can you add snappy-m-o to snapcraft and give him pull and push requests?
[00:14] <sergiusens> elopio, sure
[00:14] <sergiusens> elopio, what does that guy do?
[00:14] <elopio> sergiusens: trigger the examples tests in jenkins and report back the results.
[00:15] <sergiusens> elopio, should be there now; same team as us so should be able to do the right stuff
[00:15] <sergiusens> elopio, nice
[00:16] <elopio> sergiusens: https://github.com/ubuntu-core/snappy-jenkins/pull/40
[00:20] <sergiusens> elopio, your bug link should live in the commit https://github.com/ubuntu-core/snapcraft/pull/226/commits
[00:20] <sergiusens> not the merge commit
[00:20] <sergiusens> elopio, look at the blue here https://github.com/sergiusens/snapcraft/commit/143579fb4b68c2d79846c9b6de0a837a8f40bb54
[00:21] <sergiusens> elopio, when compared to here https://github.com/elopio/snapcraft/commit/accb773a7fb46bbaf0d83cd798ee289a592f1872
[00:21] <elopio> sergiusens: yes, I got it from your last comment. I'm sorry.
[00:21] <elopio> I can add it when I hit the Merge button.
[00:21] <sergiusens> elopio, no worries; the merge commit is not the same though
[00:23] <elopio> sergiusens: I almost got this right: https://github.com/ubuntu-core/snapcraft/commit/5fe67a88ca6c7d35c210758869e0882aae6196c5
[00:27] <sergiusens> elopio, pergect
[00:27] <sergiusens> well, if written correctly :-P
[00:27] <sergiusens> perfect*
[00:28] <elopio> next time :)
[00:31] <sergiusens> elopio, I'll check all your PRs later, need to spend some family quality time now
[00:31] <elopio> sergiusens: don't worry. This will be blocked until tomorrow.
[00:38] <Armenta> how to make work webdm behind a internet proxy? I do not know how to setup a proxy in ubuntu-core
[01:13] <sergiusens> elopio, what does 'okay' mean? :-)
[01:24] <Armenta> Hello people. I have a dimmie question, how to make work webdm behind a internet proxy? I know I need to configure the proxy, I try using  export http_proxy=ht***** in sudo and normal session but only affects the session, don't affect the wide system and the webdm complains: "Error: Get https://search.apps.ubuntu.com/api/v1/search?**** read: connection refused"
[01:31] <sergiusens> Armenta, I don't think proxies are supported
[01:32] <sergiusens> not hard to add, maybe log a bug
[01:32] <sergiusens> ?
[01:33] <Armenta> Thank you sergiusens, I will try to log a bug
[01:40] <liuxg> sergiusens, ping
[07:41] <dholbach> good morning
[07:41] <wxl> evening dholbach. just got through with a heated game of moon-buggy
[07:42] <dholbach> :-)
[07:42] <dholbach> wxl: that was more of a test of snapcraft's features :-)
[07:43] <wxl> dholbach: i know. still fun. but you should have done nethack XD
[07:43] <dholbach> see if you can do it :)
[07:43] <dholbach> for moon-buggy the "packaging" was just:
[07:43] <dholbach> http://bazaar.launchpad.net/~dholbach/+junk/moon-buggy/view/head:/snapcraft.yaml
[07:43] <wxl> thankfully ogra_ took care of that
[07:43] <dholbach> ah, great
[07:44] <wxl> like really whoa!
[07:44] <wxl> hm i'll have to snap something up now XD
[07:45] <dholbach> http://developer.ubuntu.com/snappy/build-apps/
[07:45] <wxl> yep. working on getting my way over there. had a heck of a time getting the download to get the right image.
[07:46] <wxl> i need to play with ubuntu-device-flash and create my own
[07:46] <dholbach> ok
[07:46] <wxl> it seems there's no ubuntu-core for i386, eh?
[07:47] <dholbach> somebody asked the question before, but I can't remember the answer
[07:47] <dholbach> mvo: ^ do you know?
[07:48] <mvo> wxl: no official release but you can build one using ubuntu-device-flash
[07:48] <mvo> dholbach: good morning!
[07:48] <dholbach> mvo: hola muchacho
[07:54] <wxl> mvo: ubuntu-device-flash query --device generic_i386 --channel ubuntu-core/15.04/stable --list-images → nil
[07:54] <mvo> wxl: yeah, no stable image, sorry for that, please try "edge" that should be ok, very little churn on the 15.04 channel.
[07:55] <wxl> ohhh great thanks mvo
[07:57] <wxl> creating image yay :)
[07:59] <mvo> :)
[08:01] <zyga> good morning! :)
[08:07]  * zyga needs to finish a few tests and push the changes for review
[10:00] <JamesTait> Good morning all; happy Wednesday, and happy Skeptics Day! 😃
[10:37] <seb128> mvo__, hey, did you notice that ubuntu-snappy was blocked in xenial-proposed because it fails to build on powerpc/s390x? the new snapshot you just upload still has the issue it seems...
[10:43] <mvo__> seb128: I have a look, but I think it would be good if it could be allowed through even though it fails on these two arches. but let me check what it takes to fix it
[10:50] <xnox> mvo__, to be allowed through, you should request binaries to be removed for those arches from xenial-release.
[11:01] <seb128> mvo__, what xnox said
[11:10] <sergiusens> elopio, kyrofa I need to take the car to the shop for maintenance today; I might barely make it to the standup
[11:11] <renat> Hi all! Its Renat from Screenly.
[11:11] <renat> =)
[11:11] <sergiusens> hello
[11:18] <zyga> one more test and caps simplification will work :)
[11:51] <renat> I'm trying to setup a service using a snapcraft tool. Here is the snapcraft yaml.: http://pastebin.com/SnzKHX2n
[11:51] <renat> But for the some reason - systemd is killing my service
[11:52] <renat> Here is its output. http://pastebin.com/UDG5ZS5C
[11:53] <renat> I can't see any reason, why application is killed, in journalctl output.
[11:53] <renat> Also - no security warnings I get.
[11:54] <renat> When I export all environment variables from the service file, and then execute ExecStart command - everything goes ok.
[11:56] <renat> Nothing interesting in dmesg too=(
[12:01] <renat> And here is the wrapper  script itself. http://pastebin.com/08hSijtW
[12:04] <renat> One more question. Is it possible to run a snap chrooted?
[12:18] <kyrofa> sergiusens, no problem :)
[12:21] <LefterisJP> hey guys click-review tools giving a lint error for a framework with (MANUAL REVIEW) specified basically means that in order to get that approved to be in the store I would need a manual review. I can still siedload and test of course?
[12:21] <enoch85> kyrofa, online :)
[12:24] <kyrofa> enoch85, hey there!
[12:27] <enoch85> kyrofa, how is your day today? I have around 3 hours I can work on the snappy right now
[12:27] <kyrofa> enoch85, works for me! Let's take it private
[13:13] <tzununbekov> beuno, hey. We are trying to upload our snap to app store but getting reject "(NEEDS REVIEW) 'security-policy' not allowed security_yaml_policy_present"
[13:14] <tzununbekov> beuno, could you please explain how can we pass review?
[13:14] <LefterisJP> I am working on a framework called ethereum. Sideloading it at the moment, and have a single service in it. Using an unconfined apparmor profile and a modified seccomp profile. The service's binary tries to use /root/ as it's home directory. It does so by reading the $HOME variable from what I know. Should it not be set to something like /apps/ethereum/VERSION/ ?
[13:15] <beuno> jdstrand, ^^
[13:17] <tzununbekov> according to the https://developer.ubuntu.com/en/snappy/guides/security-policy/ , custom "security-policy" will be manually reviewed, but not rejected :)
[13:23] <beuno> tzununbekov, jdstrand can tell you more, but in general we don't allow apps to escape confinement
[13:23] <beuno> a manual review just means you ask a human to make the decision
[13:24] <beuno> most of the time, the decision is to not allow it  :)
[13:24] <beuno> but we might have solved whatever you're trying to do differently
[13:26] <tzununbekov> beuno, our app is working on the top of lxc and we took security profiles from lxd package which is available in store
[13:30] <LefterisJP> anyone got any ideas about my question posted above?
[13:30] <tzununbekov> beuno, anyway, our app needs a custom security policy. With whom we can discuss it?
[13:33] <beuno> tzununbekov, jdstrand, who should be on in a short while
[13:33] <tzununbekov> beuno, thanks
[13:41] <dshihovtsev> Hi all, is there any way to read history of this channel somewhere online?
[13:43] <seb128> dshihovtsev, http://irclogs.ubuntu.com/2016/01/13/%23snappy.html
[13:43] <dshihovtsev> seb128, thanks
[13:43] <seb128> yw
[13:47]  * zyga pushed https://github.com/ubuntu-core/snappy/pull/320 for review
[13:47] <zyga> capabilities as interfaces and types!
[14:01] <tzununbekov> jdstrand, hey. What is a requirements for custom security policy to make it acceptable for uploading to store?
[14:02] <zyga> ls
[14:31] <sergiusens> kyrofa, but I made it back :-)
[14:31] <sergiusens> and waiting in the hangout :)
[14:31] <sergiusens> elopio, hangout?
[14:50] <rickspencer3> sergiusens, so, here is my snapcraft.yaml: http://bazaar.launchpad.net/~rick-rickspencer3/+junk/rest-cam/view/head:/snapcraft.yaml
[14:50] <rickspencer3> the snap builds and runs no problem
[14:51] <rickspencer3> but when I uploaded it to the store, I got this error:
[14:51] <rickspencer3> Missing required field 'description' snappy-systemd_package_yaml_required_key (rest-cam, description)
[14:51] <rickspencer3> required description field not specified snappy-systemd_package_yaml_description_present (rest-cam)
[14:51] <elopio> sergiusens: https://github.com/elopio/snapcraft/commit/eab93d52b4cd5fdca8191b8e25a17285683615f9 yay!
[14:51] <rickspencer3> any idea what I did wrong?
[14:54] <kyrofa> rickspencer3, your service needs a description
[14:54] <rickspencer3> oh!
[14:54] <kyrofa> sergiusens, should snapcraft catch that? ^^
[14:55] <sergiusens> kyrofa, 2.0 it is generated automatically
[14:55] <ogra_> yeah
[14:55] <kyrofa> sergiusens, ah
[14:55] <sergiusens> kyrofa, in 1.x it might be a required field
[14:55] <sergiusens> kyrofa, more so, in 2.0 it is not a required field in the internal format; for backwards compat it is generated automatically for package.yaml
[14:56] <sergiusens> elopio, well done ;-)
[14:56] <kyrofa> rickspencer3, are you still running out of master?
[14:56] <rickspencer3> kyrofa, I was never running out of master so far as I know
[14:56] <rickspencer3> I am on Xenial
[14:56] <sergiusens> kyrofa, I don't think he updated or else he would be complaining about 'apps' changing ;-)
[14:56] <rickspencer3> and I did sudo apt-get snapcraft in classic dimension
[14:57] <kyrofa> sergiusens, erhm, yes I suppose so
[14:57] <kyrofa> sergiusens, so it must not be required in 1.0 then
[14:57] <sergiusens> kyrofa, oh, it certainly isn't; the review tools do capture it though so it is all not that bad
[14:57] <kyrofa> Okay very good. Yeah rickspencer3 just add the description, you should be good to go
[14:58] <rickspencer3> thanks kyrofa, I'll get to is asap
[14:58] <rickspencer3> for our phone SDK, the IDE automatically runs the review tools locally after building a click
[14:58] <rickspencer3> so you can iterate on your packaging very easily
[14:59] <rickspencer3> without roundtripping through the store
[14:59] <rickspencer3> that would be a nice feature of snapcraft, to run those tools
[14:59] <sergiusens> rickspencer3, in 1.x it is run if installed
[14:59] <rickspencer3> sweet
[14:59] <kyrofa> sergiusens, oh cool, I didn't know that either
[14:59] <rickspencer3> thanks sergiusens and kyrofa
[14:59] <rickspencer3> I really appreciate your help
[14:59] <kyrofa> rickspencer3, any time!
[14:59]  * rickspencer3 hugs snappy community
[15:00] <rickspencer3> I am loving snappy these days, it is a joy to develop for
[15:00] <sergiusens> \o/
[15:00] <kyrofa> rickspencer3, then we're meeting our goal!
[15:02] <kyrofa> sergiusens, ignoring bug #1531481, I'm trying to understand how one builds part A from source, and then builds part B from source where part B depends upon part A
[15:02] <kyrofa> sergiusens, using the `after` key, does that mean part A is staged before B is ever built?
[15:04] <kyrofa> Ah, yes, okay docs for the win
[15:04] <elopio> kyrofa: sergiusens: tomcat built on xenial fails to install on rolling: tomcat-webapp-demo_1.0_amd64.snap failed to install: could not find specified cap: networking (&{apparmor /usr/share/apparmor/easyprof})
[15:04] <kyrofa> sergiusens, which makes you fix make sense, then. And using the `after` key is the official way to do exactly that (my A-B example, I mean)
[15:04] <kyrofa> Right?
[15:07] <kyrofa> sergiusens, assuming so, let's say I get to the point where A is built and staged, and now B is building. However, the process of building B not only requires access to headers and libs, but the ability to actually run a binary from A. However, said binary was built with a prefix and a destdir that are both invalid in the stage dir. How do I patch that binary to be runnable?
[15:10] <kyrofa> sergiusens, the only way I can think of right now is to patch the binary upon install (where it goes to 'parts/foo/install') to actually point to 'stage' so it's runnable when staged. That feels yucky, fragile, and very snapcraft-centric to me, which I think is not ideal
[15:12] <sergiusens> kyrofa, the latter is the only way I think so without patching upstream to make the script location independent
[15:13] <sergiusens> kyrofa, which is the other thing that can be done, make the script itself location independent
[15:15] <kyrofa> sergiusens, true... but yeah I don't see that happening for apache. The way apache modules are built is by calling the apxs binary which sets up all the include paths and stuff, which means it must be pointing to somewhere
[15:16] <sergiusens> kyrofa, hmm, we might then need and apache plugin :-/
[15:17] <kyrofa> sergiusens, hmm... yeah maybe. I'll keep that in mind as I continue. For now I'll just continue doing it all in one part
[15:17] <kyrofa> sergiusens, once I have something working I'll step back and see how complex it turned out to be :P
[15:19] <sergiusens> elopio, right, caps changed in xenial I think 'networking' is no longer required or not longer exists or changed name; tyhicks or jdstrand care to refresh my feeble mind?
[15:23] <sergiusens> mvo, does that recently released image have the env var changes too?
[15:27] <jdstrand> sergiusens, elopio: networking is now network-client
[15:27] <mvo> sergiusens: yes, sorry, forgot to mention that in the annoucement
[15:28] <mvo> sergiusens: the existing vars SNAP_* are still there for compatiblity though
[15:28] <elopio> jdstrand: let me try thtat.
[15:28] <sergiusens> mvo, yeah, but I'll get a PR now to be completely up to date
[15:28] <sergiusens> jdstrand, thank you
[15:28] <sergiusens> mvo, thanks :-)
[15:35] <mvo> sergiusens: yw!
[16:15] <tzununbekov> jdstrand, hey, beuno said that you can help with security policies for package
[16:16] <tzununbekov> what is a requirements for custom security policy to make it acceptable for uploading to store?	
[16:20] <jdstrand> tzununbekov: if you own your own store, you can upload/accept custom policy for your store. otherwise, the framework author (iirc, you had a question about frameworks) would need to engage with Canonical
[16:21] <jdstrand> tzununbekov: so, if this is for the public store, it might make sense to bring up your framework on the snappy-devel mailing list (regardless of security policy), especially since the notion of frameworks is changing in 16.04
[16:36] <tzununbekov> jdstrand, and what if it's not a framework?
[16:39] <jdstrand> tzununbekov: Canonical policies are such that we don't allow apps into the public store with custom security policy unless the app author has a relationship with Canonical. if the author has a private store, then the author can have whatever policy they want
[16:39] <jdstrand> tzununbekov: what are the accesses you need?
[16:40] <jdstrand> perhaps you don't actually need custom policy or there is a bug fix we can add
[16:43] <fgimenez> elopio, http://10.55.33.17:8080/ PR is on its way
[16:44] <elopio> fgimenez: cool :)
[16:53] <tzununbekov> jdstrand, we are running lxc containers and using cgroup manager to change the parent process id. Security profile that was applied for parent process blocks the commands inside the containers
[16:56] <tzununbekov> does it fit into the application functionality or it's more like framework?
[16:59] <jdstrand> tzununbekov: fyi, there is already the lxd framework that is in the store
[17:00] <jdstrand> tzununbekov: but to bundle it yourselves it could be either an app or a framework, but on 15.04 there is no policy that you can specify to allow this (obviously, running containers requires privileged access to the system (though not user containers and we are making those work, but I digress))
[17:03] <beowulf> hayalp, i can't seem to build an image with u-d-f on vivid: http://pastebin.ubuntu.com/14488444/
[17:06] <tzununbekov> jdstrand, btw, LXD is unrestricted, it has full access to the root
[17:06] <jdstrand> yes, but the author is a Canonical employee
[17:10] <tzununbekov> It would be nice to have a similar security privileges :)
[17:10] <tzununbekov>  actually, our app is pretty complex package and we have a several security related points to discuss with Canonical. How it's better to do?
[17:12] <jdstrand> tzununbekov: probably bring it up with manik or mectors or asac
[17:12] <jdstrand> tzununbekov: asac is here now, he may privmsg you, otherwise you can look for the others
[17:13] <sergiusens> kyrofa, https://github.com/ubuntu-core/snapcraft/pull/229
[17:13]  * zyga works on a capability type interface 
[17:13] <tzununbekov> jdstrand, thanks a lot for advise)
[17:14] <jdstrand> tzununbekov: np
[17:31]  * zyga -> some scotch and back to hacking
[17:56] <sergiusens> elopio, do you know what's going on with travis?
[17:57] <sergiusens> elopio, oh, this https://www.traviscistatus.com/
[18:31] <bellyfeel> is there a way to get more verbose output from snapcraft pull?
[18:31] <kyrofa> bellyfeel, still running into i386 issues on amd64?
[18:31] <bellyfeel> yes sir
[18:32] <kyrofa> You may have missed me yesterday-- Snapcraft isn't setup that way. It uses the sources for the host arch. Try running on a i386 VM
[18:33] <sergiusens> kyrofa, did you see my PR btw? seems to be network errors everywhere :-P
[18:33] <bellyfeel> interesting, thanks
[18:33] <kyrofa> sergiusens, haha, yeah I keep disconnecting too
[18:34] <kyrofa> bellyfeel, compiling for i386 on amd64 is cross compiling, just like compiling for armhf from amd64. Snapcraft doesn't support that yet
[18:35] <bellyfeel> ahh, okay.
[18:36] <bellyfeel> Yea I'm still learning snappy and understanding my workflow.
[18:55] <sergiusens> kyrofa, you know why the test is fragile though? They depend on get_arch_triplet :-P
[18:55] <sergiusens> I'll fix that
[18:55] <kyrofa> sergiusens, yeah mine do too... :P
[18:55] <sergiusens> kyrofa, yeah, I'm fixing it in setUp ;-)
[18:55] <kyrofa> sergiusens, yay!
[19:00] <sergiusens> done
[19:03]  * zyga pushed pull request 322
[19:04] <zyga> https://github.com/ubuntu-core/snappy/pull/322
[19:04] <zyga> this makes capability types extensible
[19:04] <zyga> please have a look if you are interested in capabilities
[19:25] <jerryG> Chipaca: hi
[19:26] <wxl> how do i debug ubuntu-device-flash complaing about issues when partitioning?
[19:30] <anpok> sergiusens: hi.. still around?
[19:30] <sergiusens> anpok, yes
[19:30] <anpok> do you have a branch for #1531481 i could continue to play with.. and then also fix nfs-utils
[19:44] <sergiusens> anpok, yes https://github.com/ubuntu-core/snapcraft/pull/229
[19:48] <elopio> I'm sorry, I had a blackout
[19:50] <kyrofa> elopio, it really does sound like you're in a jungle :P
[19:52] <kyrofa> Holy crap fingers. cp != rm -rf
[19:55] <sergiusens> elopio, did this work for you https://github.com/ubuntu-core/snapcraft/pull/228/files ?
[19:55] <sergiusens> elopio, no worries, travis died while you were gone
[19:56] <sergiusens> kyrofa, indeed, be careful
[19:56] <kyrofa> sergiusens, long day :P
[19:58] <sergiusens> kyrofa, the ubuntu unpacking needs more work; it isn't making it to the snap dir :-/
[19:58] <kyrofa> sergiusens, hmm...
[19:58] <sergiusens> kyrofa, because all matches originate from installdir ;-)
[19:59] <kyrofa> sergiusens, ah, right yeah. All the catkin env stuff uses the installdir, too
[19:59] <kyrofa> sergiusens, is that going to matter?
[20:00] <sergiusens> kyrofa, yes, I have another trick under my sleeve
[20:01] <sergiusens> kyrofa, too bad python apt doesn't give me a list of downloaded packages
[20:01] <sergiusens> would of been easier
[20:02] <rickspencer3> does anyone know if there is a sensible way for a snap to get its own version number?
[20:02] <sergiusens> rickspencer3, load the yaml from its meta dir
[20:03] <sergiusens> that's what we do in webdm fwiw
[20:03] <rickspencer3> just parse the yaml?
[20:03]  * rickspencer3 shrugs
[20:03] <sergiusens> yeah
[20:03] <rickspencer3> sounds straightforward enough
[20:12] <Chipaca> jerryG: 'sup
[20:31] <jerryG> Chipaca: Do you know what darren landol's username is on irc?... is he ever online?
[20:31] <Chipaca> jerryG: no, i don't
[20:32] <Chipaca> jerryG: i also don't know who darren landol is
[20:35] <sergiusens> kyrofa, check the branch again
[20:37] <zyga> I've pushed some more bits to https://github.com/ubuntu-core/snappy/pull/322
[20:38] <sergiusens> kyrofa, hmm, there are some corner cases to this...
[20:39] <sergiusens> darn stage-packages...
[21:12] <tedg> sergiusens: Looking at snapcraft, and when making the squashfs it mentions my uid. Is my UID encoded into the snap?
[21:29] <elopio> sergiusens: yes, it worked for me.
[22:05] <amriunix> install RPI2 GPIO API on snappy ?
[22:33] <rickspencer3> hey all
[22:33] <rickspencer3> fyi, I got my rest-cam snap into the store today
[22:34] <rickspencer3> It should be reasonably easy to use
[22:41] <kyrofa> enoch85, ping
[22:42] <enoch85> kyrofa, here
[22:50] <jerryG> Chipaca: k thx
[23:08] <sergiusens> tedg, now, the snapid is generated by the store, but beuno and friends are still working on that
[23:12] <tedg> sergiusens, thinking about the uid/guid stuff in the squash fs output https://www.irccloud.com/pastebin/YHD0RJqm/
[23:13] <tedg> Seems odd that's getting encoded into my snap
[23:14] <sergiusens> tedg, oh, now I see what you mean
[23:14] <sergiusens> I guess it needs some fakerooting magic ;-)
[23:15] <tedg> Yeah, perhaps, or some crazy command line argument. As kernel tools do.
[23:37] <liuxg> Chipaca, ping
[23:38] <liuxg> sergiusens, ping
[23:48] <fazer> sergiusens, Can I have some help squashing my commits? I used git rebase -i master but I wasn't allowed to squash all the commits, so I rebased a couple, but I over rebased and now I have a big mess of commits. This is the pr: https://github.com/ubuntu-core/snapcraft/pull/217
[23:54] <wxl> anyone know how to debug a partitioning issue with ubuntu-device-flash?
[23:55] <tsimonq2> wxl: RTFM? :P
[23:55] <tsimonq2> ¯\_(ツ)_/¯
[23:55] <fazer> elopio, kyrofa ^^
[23:55] <wxl> tsimonq2: you show me in the manual where that's covered
[23:56] <tsimonq2> wxl: heheheh, partitioning specifications? :P
[23:58] <wxl> tsimonq2: ubuntu-device-flash --verbose core --device generic_i386 --channel ubuntu-core/15.04/edge --output mysnappy.img
[23:58] <tsimonq2> oh
[23:59]  * tsimonq2 remains silent and waits for the experts XD