[07:55] <dholbach> good morning
[08:15] <didrocks> good morning dholbach :)
[08:15] <dholbach> salut didrocks
[08:28] <sergiusens> ogra_, hey do you know what vmlinuz-4.2.0-2014-generic-dragon410c is?
[09:03] <noizer> Good morning
[09:22] <ysionneau> morning !
[09:26] <sergiusens> ricmm, http://paste.ubuntu.com/15319880/
[09:26] <noizer> zyga-phone Hi is the update done for the interfaces etc?
[09:27] <noizer> zyga-phone Hi is the update done for the interfaces etc?
[09:29] <zyga-phone> jdstrand: https://github.com/ubuntu-core/snappy/pull/591/files
[09:29] <zyga-phone> noise][1: hey, no, we haven't released yet AFAIK, I will see what the state of the stack is and then we'll probably release
[09:29] <zyga-phone> noise][1: but it is certainly on our plan today
[09:30] <noizer> zyga-phone: ok :D
[09:40] <mvo> ogra_: will you be able to test my new uploads of the os and kernel snaps for arm64? I uploaded to rolling/edge
[09:41] <mvo> ogra_: i.e. if it boots :)
[09:41]  * zyga-phone can test as well
[09:41] <zyga-phone> mvo: on dragon
[09:43] <mvo> zyga-phone: yes, updating to them is enough, so sed /channel: stable/channel: edge/ might be the easiest way (in /var/lib/snappy/meta/*.manifest
[09:43] <zyga-phone> k, one sec
[09:44] <mvo> zyga-phone: no problem, the review task is still running so its not published yet anyway
[09:45] <zyga-phone> did the sed
[09:45] <zyga-phone> rebooting to see if snappy picks it up
[09:47] <zyga-phone> mvo: that didn't make snappy see any updates, am I missing something?
[09:48] <zyga-phone> all the *.manifest files say channel: edge
[09:49] <zyga-phone> canonical-dragon       2016-02-12 0.7.1                         canonical
[09:49] <zyga-phone> canonical-dragon-linux 2016-02-19 4.2.0-2014-generic-dragon410c canonical
[09:49] <zyga-phone> mvo: ^^
[09:51] <ricmm> ppisati: hey
[09:52] <ppisati> ricmm: hey
[09:52] <ricmm> having some pain here
[09:52] <ppisati> ricmm: ???
[09:52] <ricmm> ppisati: how do I fire off a build for your ubuntu kernel tree for 96b?
[09:53] <ppisati> ricmm: hold on
[09:54] <mvo> zyga-phone: its now updated
[09:55] <zyga-phone> mvo: still nothing?
[09:55] <ppisati> ricmm: export ARCH=arm64; export $(dpkg-architecture -aarm64); export CROSS_COMPILE=aarch64-linux-gnu-
[09:55] <mvo> zyga-phone: in /edge ?
[09:55] <ppisati> ricmm: if you are trying to build the 4.2.0 dragon410c branch:
[09:55] <zyga-phone> mvo: I did the sed, in /var/lib/snappy/meta, anything else I should change?
[09:55] <zyga-phone> (and I rebooted to reset snapd memory state)
[09:55] <ppisati> ricmm: fdrc && debian/rules build && fdr binary-generic-dragon410c
[09:56] <ppisati> ricmm: if you are trying to build the 4.4 snapdragon/96boards tree:
[09:56] <ppisati> ricmm: fdrc && debian/rules build && fdr binary-[snapdragon|96boards]
[09:56] <mvo> zyga-phone: I investigate
[09:56] <ppisati> ricmm: fdr = fakeroot debian/rules / fdc = fdr clean
[10:01] <ricmm> ppisati: thanks
[10:01] <ricmm> ppisati: just to confirm, for arm64 your scripts still copy to vmlinuz right
[10:01] <ricmm> even tho its not really compressing
[10:02] <ppisati> ricmm: yes, it creates the vmlinuz image file
[10:02] <ricmm> ok
[10:02] <ricmm> slightly misleading to have vmlinuz if its not compressed
[10:02] <ricmm> but unrelated to today anyways
[10:03] <ricmm> ppisati: how about getting the tree in a state where I can issue a final make command
[10:03] <ricmm> as if it was a normal tree
[10:03] <ricmm> as-in get the right config built, then CROSS_COMPILE, ARCH, make Image
[10:03] <ricmm> can I do that starting with an ubuntu source package tree?
[10:04] <ppisati> ricmm: when i need to do that, i issue:
[10:05] <ppisati> ricmm: fdr prepare-[generirc-dragon410c|snapdragon|96boards]; cp debian/build/build-.../.config .; make ...
[10:06] <ppisati> ricmm: what are you doing over there? why are you compiling kernels?
[10:06] <ricmm> im with sergio, we are looking at the kernel plugin
[10:06] <mvo> ogra_: is your script to build the arm64 kernel snap somewhere?
[10:06] <ricmm> mvo: last I asked him that question he said he uses your script
[10:06] <ricmm> so probably you are the answer
[10:08] <ricmm> ppisati: make: *** No rule to make target 'prepare-generic-96boards'. Stop.
[10:08] <ppisati> ricmm: oh, that tree was renamed
[10:08] <ppisati> ricmm: fdr prepare-96boards
[10:08] <ricmm> im at the tip of your x-96boards branch
[10:11] <sergiusens> ricmm, hey
[10:21] <ysionneau> funny that snappy list tells me to reboot to use ubuntu-core-xxxx-13 but if I do ls -l /writable/system-data/snaps/ubuntu-core.canonical/
[10:21] <ysionneau> then current already points to -13 and not -12
[10:23] <mvo> ricmm: I wonder where he gets the kernel from, but I will talk to him once he is around
[10:24] <ricmm> mvo: for which device?
[10:24] <ricmm> short answer is ubuntu packages
[10:24] <mvo> ricmm: the dragonboard
[10:24] <ricmm> paolo's ppa
[10:26] <mvo> ta
[10:37] <ogra_> mvo, will test ... and what ricmm said, i use your script with a lot of manual dpkg -x'ing and a depmod call
[10:37] <ogra_> i'll trun that into proper code (to merge it into livecd-rootfs)
[10:37] <mvo> ogra_: aha, ok. I had hoped to upload a new kernel, but there are manual steps I leave it to you :)
[10:37] <ogra_> ok
[10:38] <ogra_> ricmm, note that you need the patched devicetree file when usinh ppisati's build ...
[10:39] <ogra_> there is one called -touch ...
[10:39] <ogra_> err
[10:39] <ogra_> sorry
[10:39] <ogra_> -snappy
[10:49] <noizer> Hi, I have a question about daemons in snappy. Is it possible to set a variable so the daemon don't start at startup?
[10:49] <zyga-phone> not at present; I don't think this is something you can do
[10:49] <zyga-phone> noizer: what's the use case?
[10:52] <noizer> zyga-phone A service needed only running when they tabbing on something. But first i tought i will do that with starting an other snap(execute a wrapper from an other snap) but that isn't possible but starting a service is possible out of the REST API
[10:53] <noizer> Sorry for service but its a bacground app I mean
[11:20] <ricmm> ogra_: about that manual depmod, did you have more info on that somewhere?
[11:21] <ricmm> 2.6G of modules is intense ;)
[11:21] <noizer> zyga-phone So at this moment a daemon will always start at startup?
[11:24] <ricmm> ppisati: lots of modules build automatically :(
[11:25] <ppisati> ricmm: we build as many modules as possible
[11:25] <zyga-phone> noizer: yes
[11:26] <noizer> hmmm ok
[11:26] <ricmm> ppisati: sure, how do we then select which ones to package?
[11:26] <ricmm> I'm assuming this is the depmod magic that ogra is talking about
[11:26] <ogra_>  depmod -ea -F unpack-19022016/boot/System.map-4.2.0-2014-generic-dragon410c -b xenial-chroot/snap/ 4.2.0-2014-generic-dragon410c
[11:26] <ogra_> that's from my shell history
[11:26] <ogra_> for the last build
[11:28] <ogra_> -F is the part to System.map, -b is your target dir
[11:29] <ogra_> s/part/path
[11:29] <ogra_> instead of -a you can also give a list of .ko files
[11:30] <ogra_> (at the end of the line then)
[11:32] <ricmm> ogra_: thanks
[11:32] <ogra_> ricmm, the depmod "magic" is only to create the modules.dep files, nothing more ... else modprobe wouldnt work
[11:32] <ogra_> it doesnt make any selection about what gets installed
[11:32] <ricmm> ok, and in your snap what are you making about the 2.6G of modules?
[11:32] <ogra_> i dont have 2.6G of modules
[11:32] <ogra_> :)
[11:33] <ogra_> i use the binary deb and unpack it ...
[11:33] <ricmm> right, so maybe a q for paolo
[11:34] <ricmm> ppisati: I see 2.6G of modules if I build manually, but only 400MB in the package
[11:34] <ogra_> linux-image-* is 52MB big (the deb(
[11:35] <ogra_> unless ppisati invented an awesome new comoression method and will get very rich with that i guess you are building to much or counting it wrong :)
[11:35] <ogra_> *compression
[11:35] <ogra_> 400MB ? thats cerazy
[11:36] <ricmm> ok, 200
[11:36] <ricmm> ;)
[11:36] <ppisati> -rw-r--r-- 1 ppisati ppisati 55214720 Mar  1 10:18 linux-image-4.4.0-1012-96boards_4.4.0-1012.12_arm64.deb
[11:36] <ogra_> mvo, i was wondering if we should not consider to mount the vfat not async anymore and instead make a few sync calls in the code that copies the kernel in place
[11:36] <ogra_> mvo, my last dragonboard update took ages
[11:37] <ogra_> from the uboot env POV we should be fine
[11:37] <ogra_> and mounting sync wont gain us much for kernel and initrd copying
[11:40] <ogra_> (weather it gets corrupt while doing a sync call with power loss or while syncing due to the mount option doesnt really matter(
[11:44] <mvo> ogra_: yeah, +1
[11:44] <noizer> I try to make a socket but I gets always a permission error. this are my skill that I uses: uses:
[11:44] <noizer>   listener:
[11:44] <noizer>     type : migration-skill
[11:44] <noizer>     caps:
[11:44] <noizer>        - network-client
[11:44] <noizer>        - network-listener
[11:44] <mvo> ogra_: just go ahead and change it
[11:44] <noizer> Somebody nows more about it?
[11:45] <ogra_> mvo, great, will do
[11:45] <mvo> ta
[11:46] <mvo> ogra_: do you happen to have any idea why only two amd64 builders are online right now?
[11:46] <ogra_> nops
[11:47] <ogra_> i guess thats a colin/adam question
[11:47]  * ogra_ bets doko has eaten them ;)
[11:47] <mvo> I go and ask on #launchpad
[11:47] <mvo> thanks
[11:59] <ogra_> mvo, hmm, what about the efi dir, that is currently also mounted with "sync"
[12:00] <ogra_> (not sure if firmware requires that)
[12:00] <mvo> ogra_: its the same filesystem/partiton iirc . I don't think we actually write anything to it
[12:00] <mvo> ogra_: we just need it for the efi binaries
[12:00] <ogra_> well, its a different code path, thats why i ask
[12:00]  * ogra_ switches it to "defaults" from "sync" as well
[12:02] <mvo> yeah, lets do it and see what breaks
[12:02] <zyga-phone> noizer: s/type: migration-skill/interface: old-security/
[12:04] <noizer> zyga-phone snapcraft doesn't support it for now so I wait for today so that i can have a new snapcraft
[12:04] <zyga-phone> noizer: yeah, I know :-(
[12:05] <noizer> zyga-phone I want it so bad xD
[12:05] <zyga-phone> noizer: we're working on a release, you just have to wait a little longer
[12:06] <noizer> zyga-phone what is a little longer?
[12:07] <zyga-phone> noizer: we still plan to release today
[12:07] <zyga-phone> noizer: no further ETA
[12:07] <noizer> zyga-phone owkay
[12:20] <ppisati> ricmm: if you want to put your kernel/modules on diet , turn off this option in the .config
[12:20] <ogra_> mvo, hmm, i see you tried to upload a 4.4 dragonboard kernel to the store, where does that come from ? i see no deb anywhere for it
[12:20] <ppisati> ricmm: CONFIG_DEBUG_INFO=y
[12:20] <ppisati> ricmm: to # CONFIG_DEBUG_INFO is disabled
[12:20] <mvo> ogra_: its the generic arm64 kernel, but I removed that version from the publishing history
[12:21] <ppisati> ricmm: this will greatly reduce the size of kernel / modules.ko
[12:21] <ogra_> ah, k
[12:21] <ogra_> mvo,  what makes you think that would boot ? :)
[12:21] <mvo> ogra_: hopeless optimism ;)
[12:21] <ogra_> haha
[12:21] <mvo> ogra_: but seriously, after uploading I remembered it would probably not work and immediately removed it from the channels
[12:22] <ogra_> ppisati, do we have any newerr dragonboard kernel than your linux-dragon410c - 4.2.0-2014.14  yet ?
[12:22] <mvo> ogra_: I need to test the beaglebone though, that should work with the stock kernel
[12:22] <ogra_> i know you were working on something 4.4ish
[12:22] <ogra_> mvo, yeah
[12:23] <ogra_> GRRRR !
[12:23] <ogra_> Installing ubuntu-core.canonical_16.04.0-9.arm64_arm64.snap
[12:23] <ogra_> WARNING: could not unmap partitions
[12:23] <ogra_> WARNING: unexpected issue: remove /tmp/diskimage493904108/system/apps: read-only file system
[12:23] <ogra_> ...
[12:23] <ogra_> i wish u-d-f would still work on trusty
[12:23]  * ogra_ goes and builds on a wily system 
[12:24] <ricmm> ppisati: well im basically trying to replicate the module list from your kernel package
[12:25] <Rinsan> Will Snappy Core support Raspberry PI 3?
[12:26] <ogra_> Rinsan, at some point, yes
[12:27] <ogra_> i was looking at that on the weekend, but it seems u-boot isnt fully there yet for the Pi3 ... and snappy needs u-boot
[12:27] <Rinsan> ogra_, Ok thanks for the quick reply!
[12:27] <ogra_> if thats ready i'll surely try to integrate it
[12:28] <Rinsan> So it
[12:28] <Rinsan> Sorry... cat :)
[12:29] <ppisati> ricmm: by default our config has the debug info built-in, and then we strip the symbols out for the vanilla linux-image deb package
[12:30] <ppisati> ricmm: this way from the same config we build debug version and (after stripping) the non debug version
[12:30] <ppisati> ricmm: so either you keep the config as is, and then strip out the symbols
[12:31] <ppisati> ricmm: or disable that option
[12:33] <ogra_> ppisati, while we talk about options ... can we trun off that scary kernel message on boot about trace_printk()  ? http://paste.ubuntu.com/15320455/
[12:33] <ogra_> doesnt really seem appropriate for release
[12:41] <ppisati> ogra_: i agree, last week i tried to disable that but i couldn't figure out
[12:41] <ogra_> ah, k
[12:41] <ppisati> ogra_: like, even turning off that debug option the message was still there
[12:41] <ppisati> ogra_: but yeah, i'll turn it off
[12:41] <ppisati> ogra_: about 4.4
[12:41] <ppisati> ogra_: i have two trees
[12:42] <ogra_> but only one deb :)
[12:42] <ppisati> ogra_: one is the qualcomm-only and the other is the merged qualcomm+hikey
[12:42] <ppisati> ogra_: hold on
[12:42] <ysionneau> This means syscall number 289 has been called? http://pastebin.com/uE4tGQCA
[12:42] <ogra_> ysionneau, exactly
[12:42] <ysionneau> not sure how to know which one it is
[12:42] <ysionneau> I'm browsing the kernel sources ...
[12:43] <ogra_> ysionneau, scmp_sys_resolver 289
[12:43] <ppisati> ogra_: https://launchpad.net/~p-pisati/+archive/ubuntu/embedded/+files/linux-image-4.4.0-1006-snapdragon_4.4.0-1006.6_arm64.deb
[12:43] <ogra_> that prints the name
[12:43] <ppisati> ogra_: it's a couple of weeks old, i'm waiting for qualcomm to announce their support period for that kernel this week @ connect
[12:43] <ogra_> ppisati, ah, thanks ... do you think thats stable enough to switch to it ?
[12:44] <ysionneau> nice! it's send()
[12:44] <ysionneau> thx
[12:44] <ppisati> ogra_: it's stable, but don't switcj until we hit the archive
[12:44] <ogra_> ok
[12:44] <ysionneau> send is forbidden by default?
[12:45] <ogra_> you need the network-client "capability^Wskill^Wslot^Wplug"
[12:45] <ysionneau> ahahah
[12:45] <ogra_> or just "network" not sure ... try them out
[12:45] <ysionneau> the name bikeshedding is going crazy
[12:45] <ogra_> there are a few
[12:46] <ysionneau> this really needs to be documented somewhere
[12:47] <ogra_> it is in total flux ... but i think there are docs (dont as me where though)
[12:48] <ysionneau> I'll try what Michael Vogt sent on march the 1st "snap.yaml skill->interface change"
[12:48] <ysionneau> or maybe it's not yet effective
[12:48] <ogra_> only half
[12:48] <ogra_> slots and plugs have been flipped around
[12:49] <ogra_> or was ist s/slots/sockets/ ?
[12:49] <ogra_> "things"
[12:49] <ogra_> :P
[12:50] <ysionneau> yes and followed by emails about changing the names again
[12:50] <ogra_> thats what i mean
[12:50] <zyga-phone> ysionneau: it's not released, just wait for the release
[12:50] <ogra_> there is a pending os snap (in testing atm) that should have the final implementations
[12:51] <zyga-phone> ysionneau: all the docs have been updated but the bit relase is in the making
[12:51] <ysionneau> if you have a link to all the security/caps/overrides stuff doc' :')
[12:51] <ysionneau> please do share :)
[13:02] <zyga-phone> ysionneau: we'll release public docs soon
[13:05] <ysionneau> \o/
[13:15] <ysionneau> lots of interesting documentation in here: https://github.com/ubuntu-core/snapcraft/blob/master/docs/debug.md
[13:21] <ysionneau> don't know if you are aware of that but snappy-debug.security crashes: http://pastebin.com/ekxwPREL
[13:23] <ogra_> mvo, new os snap boots on arm64 ... i still see it trying to run grub migration (and fail), beyond that it seems fine
[13:23] <mvo> ogra_: great, thanks!
[13:23] <ogra_> mvo, any package in the sotre that i should try to make sure the changes work ?
[13:23] <ogra_> *store
[13:27] <ogra_> wow, gross ... so installing a package from the store succeeds, the services dont start though and there is no error message at all
[13:28] <ogra_> Chipaca, ^^^ snappy install should really spill an error for that
[13:29] <ogra_> (syslog is full of denials at least ... but there was no idication at all that anything failed when using snappy install)
[13:32] <ogra_> mvo, i also still see bug 1543764
[13:33] <ogra_> (i.e. no classic mode at all on arm64)
[13:37] <mvo> ogra_: I know :(
[14:01] <elopio> iahmad: I'm just seeing the meeting now. Are you guys still around?
[14:09] <noizer> does somebody used seccomp filters before in snappy?
[14:16] <ysionneau> any idea why I get this error message ? http://pastebin.com/LawTNuDi
[14:16] <ysionneau> I'm using latest commit from master of snapcraft (github)
[14:22] <jdstrand> zyga-phone: that's awesome
[14:22] <jdstrand> zyga-phone: (https://github.com/ubuntu-core/snappy/pull/591/files)
[14:26] <zyga-phone> jdstrand: I'll fan out with more of those later today, they should be easy to maintain for anyone on the security team
[14:27] <jdstrand> zyga-phone: cool, thanks
[14:29] <zyga-phone> jdstrand: I'll also move the base apparmor template
[14:30] <zyga-phone> jdstrand: so that there's no dependency on the base security templates anywhere and it's all self-contained
[14:32] <jdstrand> zyga-phone: sure-- I thought of another case where all of it in the go code is painful but I understand why you are doing it this way. I look forward to working through this after 16.04 some time
[14:34] <zyga-phone> jdstrand: with all the bits in snappy we can at least consistently push new test snapd over, I know it's not like editing files manually but they are on squashfs anyway now
[14:34] <zyga-phone> jdstrand: do you know my devtools scripts?
[14:42] <iahmad> elopio, I have rescheduled it for later today, let me know if that works for you?
[14:43] <elopio> iahmad: yes, it works. We can make it 30 minutes earlier also, so you don't stay so late.
[14:44] <iahmad> elopio, ok, let me check with jibel
[14:46] <iahmad> elopio, scheduled time is fine
[14:46] <elopio> alright.
[15:58] <ysionneau> hmm that does not sound right https://github.com/ubuntu-core/snapcraft/blob/master/snapcraft/common.py#L35
[15:58] <ysionneau> what if you install by doing python3 setup.py develop --user
[15:58] <ysionneau> ?
[15:58] <ysionneau> then it will still try to fetch the schema from /usr/share/snapcraft
[15:58] <ysionneau> even though it should look in the source dir
[16:00] <jdstrand> mvo: http://bazaar.launchpad.net/~click-reviewers/click-reviewers-tools/trunk/view/head:/clickreviews/common.py#L39
[16:00] <jdstrand> mvo: basically, the review tools, snapcraft (and now I learned) snappy build need to use the same options to mksquashfs otherwise the resquash test in the store will fail
[16:01]  * jdstrand didn't realize snappy build was still around (that's fine, it's just I would have communicated this ooner)
[16:01] <jdstrand> sooner*
[16:02] <mvo> jdstrand: cool, fixing now
[16:02] <jdstrand> thanks
[16:07] <ysionneau> sorry I missed that: https://github.com/ubuntu-core/snapcraft/blob/master/snapcraft/dirs.py#L30
[16:08] <ysionneau> so there is no issue :p
[16:36] <noizer> Hi is it possible to do some changes on the apparmor? in an app?
[16:36] <mvo> jdstrand: I pushed a branch for --no-xattrs
[16:36] <mvo> jdstrand: I can not do --all-root, this breaks the OS snap which has various files that are not owned by root
[16:37] <mvo> jdstrand: like /var/mail
[16:49] <jdstrand> mvo: can you do --all-root when 'type: app' or 'type: framework'?
[16:50] <noizer> mvo what are the possibilities of changing the apparmor of your snap?
[16:55] <mvo> jdstrand: yeah, that would be ok
[16:56] <mvo> jdstrand: essentially !os -> all-root
[16:56] <jdstrand> mvo: I think that sounds like a fine start
[16:57] <jdstrand> this does mean I'll probably not be able to do a resquash test for the os snap though
[16:57] <jdstrand> I think that is ok considering it will always come from a trusted source
[17:45] <noizer> is snapcraft already updated?
[17:56] <ogra_> kyrofa,   https://plus.google.com/+DrewFustini/posts/1Z5iPDsYaXy perhaps you might like to chime into the ROS discussion here
[18:15] <zyga> ogra_: hey
[18:15] <ogra_> yo
[18:16] <zyga> ogra_: FYI, we're changing some stuff around ubuntu-core-launcher
[18:16] <zyga> ogra_: I'll simplify it to take less arguments and just be smarter as to what it is doing
[18:16] <ogra_> hmm
[18:16] <zyga> ogra_: and I'm killing/changing some of the environment as well
[18:16] <zyga> ogra_: all TMP* bits are now gone from the generated wrapper (the launcher handles that)
[18:16] <ogra_> i havent seen any snap yet that actually used the launcher directly
[18:16] <zyga> ogra_: I've dropped SNAP_FULLNAME
[18:16] <zyga> ogra_: none of them do, it's just FYI
[18:17] <ogra_> ah
[18:17] <zyga> ogra_: and SNAP_ORIGIN becomes SNAP_DEVELOPER with actual developer bits inside
[18:17]  * ogra_ has never used either :)
[18:18] <ogra_> thanks for the info though :)
[18:53] <enoch85> kyrofa: hey there
[18:53] <enoch85> kyrofa: sorry, been busy the last weeks
[18:54] <enoch85> kyrofa: I felt confident in your work, it felt like I was only slowing things down :)
[19:14] <enoch85> kyrofa: anything I can help you with?
[20:12] <zyga> jdstrand: hey
[20:12] <zyga> jdstrand: aroudn?
[20:36] <jdstrand> zyga: hey, I have a little time before my next meeting
[20:42] <zyga> jdstrand: hey, I'm changing ubuntu-core-launcher a little
[20:42] <zyga> jdstrand: I'll make it take just 'snap.[app]' + command to execute as input
[20:43] <zyga> jdstrand: and derive all the security tokens from snap.[app]
[20:43] <zyga> jdstrand: this affects aa profile, seccomp and the udev tag
[20:45] <zyga> jdstrand: I wanted to let you know that this is happening
[20:45] <zyga> jdstrand: also the launcher will change the name of the executable but that's less important
[20:45] <zyga> jdstrand: (I mean that the launcher will be renamed, not that the launched application will think it got renamed)
[20:45] <jdstrand> zyga: so, you are going to be touching the privileged part of the code then. this will also need changes to the systemd unit generation and the scripts generation
[20:47] <jdstrand> zyga: how are you going to derive all security tokens from snap.[app]?
[20:47] <zyga> jdstrand: I know, I'll handle both changes
[20:47] <jdstrand> each command has a different profile and how will you determine the version?
[20:47] <zyga> jdstrand: I plan to rename the aa profile to snap-$snapName.$appName
[20:47] <zyga> jdstrand: we'll drop the version
[20:47] <jdstrand> these are big changes
[20:48] <zyga> jdstrand: various files will be hard-coded (location is /snappy/$snapName/current/ + $command
[20:48] <jdstrand> have they been discussed anywhere else?
[20:48] <zyga> jdstrand: we've just brainstormed this on telegram a little with niemeyer and Chipaca
[20:48] <jdstrand> I wish I was part of that conversation
[20:49] <niemeyer> jdstrand: Sorry, this has been talked about literally an hour ago
[20:49] <niemeyer> jdstrand: I can provide the full background to it
[20:49] <jdstrand> unfortunately this is a difficult day to participate in these conversations because I have a ton of meetings
[20:50] <niemeyer> jdstrand: and this is still a strawman, so please don't feel like we have decided without you.. chipaca and mvogt haven't even seen that conversation yet, so these changes are being made in an attempt to improve the status quo, if it passes through reviews
[20:50] <jdstrand> is there a doc or something I can look at/think about/respond to?
[20:50] <jdstrand> I see
[20:50] <jdstrand> it sounded more concrete a moment ago :)
[20:50] <niemeyer> jdstrand: No, but I can either: a) Explain here; or b) Write an email and send to the list
[20:51] <niemeyer> jdstrand: The proposal is concrete
[20:51] <jdstrand> I don't mind changing stuff, I just want to understand why we are changing and the changes themselves
[20:51] <niemeyer> jdstrand: But it's not done until we say so
[20:51] <niemeyer> jdstrand: Okay, do you prefer a or b?
[20:52] <niemeyer> To be clear, this is my proposal.. Chipaca hasn't seen it yet as it's too late there
[20:52] <jdstrand> I am not going to have time for 'a' today. I will have time for 'a' tomorrow. I could even do a hangout
[20:52] <jdstrand> if that doesn't work, 'b'
[20:52] <jdstrand> maybe a hangout with the 5 of us?
[20:52] <niemeyer> jdstrand: Ok, let me shoot an email to the list first then, since people will see the proposals earlier than that, and we can get together in a hangout to decide on ripples from that
[20:52] <jdstrand> tomorrow at 1500 UTC-ish
[20:52] <jdstrand> ok, that's fine too
[20:53] <zyga> +1, thanks everyone :)
[20:53] <niemeyer> Indeed, thanks to you both
[20:54] <jdstrand> np