/srv/irclogs.ubuntu.com/2016/03/07/#snappy.txt

dholbachgood morning07:55
didrocksgood morning dholbach :)08:15
dholbachsalut didrocks08:15
sergiusensogra_, hey do you know what vmlinuz-4.2.0-2014-generic-dragon410c is?08:28
noizerGood morning09:03
ysionneaumorning !09:22
sergiusensricmm, http://paste.ubuntu.com/15319880/09:26
noizerzyga-phone Hi is the update done for the interfaces etc?09:26
noizerzyga-phone Hi is the update done for the interfaces etc?09:27
zyga-phonejdstrand: https://github.com/ubuntu-core/snappy/pull/591/files09:29
zyga-phonenoise][1: hey, no, we haven't released yet AFAIK, I will see what the state of the stack is and then we'll probably release09:29
zyga-phonenoise][1: but it is certainly on our plan today09:29
noizerzyga-phone: ok :D09:30
mvoogra_: will you be able to test my new uploads of the os and kernel snaps for arm64? I uploaded to rolling/edge09:40
mvoogra_: i.e. if it boots :)09:41
* zyga-phone can test as well09:41
zyga-phonemvo: on dragon09:41
mvozyga-phone: yes, updating to them is enough, so sed /channel: stable/channel: edge/ might be the easiest way (in /var/lib/snappy/meta/*.manifest09:43
zyga-phonek, one sec09:43
mvozyga-phone: no problem, the review task is still running so its not published yet anyway09:44
zyga-phonedid the sed09:45
zyga-phonerebooting to see if snappy picks it up09:45
zyga-phonemvo: that didn't make snappy see any updates, am I missing something?09:47
zyga-phoneall the *.manifest files say channel: edge09:48
zyga-phonecanonical-dragon       2016-02-12 0.7.1                         canonical09:49
zyga-phonecanonical-dragon-linux 2016-02-19 4.2.0-2014-generic-dragon410c canonical09:49
zyga-phonemvo: ^^09:49
ricmmppisati: hey09:51
ppisatiricmm: hey09:52
ricmmhaving some pain here09:52
ppisatiricmm: ???09:52
ricmmppisati: how do I fire off a build for your ubuntu kernel tree for 96b?09:52
ppisatiricmm: hold on09:53
mvozyga-phone: its now updated09:54
zyga-phonemvo: still nothing?09:55
ppisatiricmm: export ARCH=arm64; export $(dpkg-architecture -aarm64); export CROSS_COMPILE=aarch64-linux-gnu-09:55
mvozyga-phone: in /edge ?09:55
ppisatiricmm: if you are trying to build the 4.2.0 dragon410c branch:09:55
zyga-phonemvo: 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
ppisatiricmm: fdrc && debian/rules build && fdr binary-generic-dragon410c09:55
ppisatiricmm: if you are trying to build the 4.4 snapdragon/96boards tree:09:56
ppisatiricmm: fdrc && debian/rules build && fdr binary-[snapdragon|96boards]09:56
mvozyga-phone: I investigate09:56
ppisatiricmm: fdr = fakeroot debian/rules / fdc = fdr clean09:56
ricmmppisati: thanks10:01
ricmmppisati: just to confirm, for arm64 your scripts still copy to vmlinuz right10:01
ricmmeven tho its not really compressing10:01
ppisatiricmm: yes, it creates the vmlinuz image file10:02
ricmmok10:02
ricmmslightly misleading to have vmlinuz if its not compressed10:02
ricmmbut unrelated to today anyways10:02
ricmmppisati: how about getting the tree in a state where I can issue a final make command10:03
ricmmas if it was a normal tree10:03
ricmmas-in get the right config built, then CROSS_COMPILE, ARCH, make Image10:03
ricmmcan I do that starting with an ubuntu source package tree?10:03
ppisatiricmm: when i need to do that, i issue:10:04
ppisatiricmm: fdr prepare-[generirc-dragon410c|snapdragon|96boards]; cp debian/build/build-.../.config .; make ...10:05
ppisatiricmm: what are you doing over there? why are you compiling kernels?10:06
ricmmim with sergio, we are looking at the kernel plugin10:06
mvoogra_: is your script to build the arm64 kernel snap somewhere?10:06
ricmmmvo: last I asked him that question he said he uses your script10:06
ricmmso probably you are the answer10:06
ricmmppisati: make: *** No rule to make target 'prepare-generic-96boards'. Stop.10:08
ppisatiricmm: oh, that tree was renamed10:08
ppisatiricmm: fdr prepare-96boards10:08
ricmmim at the tip of your x-96boards branch10:08
sergiusensricmm, hey10:11
ysionneaufunny 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
ysionneauthen current already points to -13 and not -1210:21
mvoricmm: I wonder where he gets the kernel from, but I will talk to him once he is around10:23
ricmmmvo: for which device?10:24
ricmmshort answer is ubuntu packages10:24
mvoricmm: the dragonboard10:24
ricmmpaolo's ppa10:24
mvota10:26
ogra_mvo, will test ... and what ricmm said, i use your script with a lot of manual dpkg -x'ing and a depmod call10:37
ogra_i'll trun that into proper code (to merge it into livecd-rootfs)10:37
mvoogra_: aha, ok. I had hoped to upload a new kernel, but there are manual steps I leave it to you :)10:37
ogra_ok10:37
ogra_ricmm, note that you need the patched devicetree file when usinh ppisati's build ...10:38
ogra_there is one called -touch ...10:39
ogra_err10:39
ogra_sorry10:39
ogra_-snappy10:39
noizerHi, 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-phonenot at present; I don't think this is something you can do10:49
zyga-phonenoizer: what's the use case?10:49
noizerzyga-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 API10:52
noizerSorry for service but its a bacground app I mean10:53
ricmmogra_: about that manual depmod, did you have more info on that somewhere?11:20
ricmm2.6G of modules is intense ;)11:21
noizerzyga-phone So at this moment a daemon will always start at startup?11:21
ricmmppisati: lots of modules build automatically :(11:24
ppisatiricmm: we build as many modules as possible11:25
zyga-phonenoizer: yes11:25
noizerhmmm ok11:26
ricmmppisati: sure, how do we then select which ones to package?11:26
ricmmI'm assuming this is the depmod magic that ogra is talking about11: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-dragon410c11:26
ogra_that's from my shell history11:26
ogra_for the last build11:26
ogra_-F is the part to System.map, -b is your target dir11:28
ogra_s/part/path11:29
ogra_instead of -a you can also give a list of .ko files11:29
ogra_(at the end of the line then)11:30
ricmmogra_: thanks11:32
ogra_ricmm, the depmod "magic" is only to create the modules.dep files, nothing more ... else modprobe wouldnt work11:32
ogra_it doesnt make any selection about what gets installed11:32
ricmmok, and in your snap what are you making about the 2.6G of modules?11:32
ogra_i dont have 2.6G of modules11:32
ogra_:)11:32
ogra_i use the binary deb and unpack it ...11:33
ricmmright, so maybe a q for paolo11:33
ricmmppisati: I see 2.6G of modules if I build manually, but only 400MB in the package11:34
ogra_linux-image-* is 52MB big (the deb(11:34
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_*compression11:35
ogra_400MB ? thats cerazy11:35
ricmmok, 20011: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.deb11: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 place11:36
ogra_mvo, my last dragonboard update took ages11:36
ogra_from the uboot env POV we should be fine11:37
ogra_and mounting sync wont gain us much for kernel and initrd copying11:37
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:40
mvoogra_: yeah, +111:44
noizerI 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-skill11:44
noizer    caps:11:44
noizer       - network-client11:44
noizer       - network-listener11:44
mvoogra_: just go ahead and change it11:44
noizerSomebody nows more about it?11:44
ogra_mvo, great, will do11:45
mvota11:45
mvoogra_: do you happen to have any idea why only two amd64 builders are online right now?11:46
ogra_nops11:46
ogra_i guess thats a colin/adam question11:47
* ogra_ bets doko has eaten them ;)11:47
mvoI go and ask on #launchpad11:47
mvothanks11:47
ogra_mvo, hmm, what about the efi dir, that is currently also mounted with "sync"11:59
ogra_(not sure if firmware requires that)12:00
mvoogra_: its the same filesystem/partiton iirc . I don't think we actually write anything to it12:00
mvoogra_: we just need it for the efi binaries12:00
ogra_well, its a different code path, thats why i ask12:00
* ogra_ switches it to "defaults" from "sync" as well12:00
mvoyeah, lets do it and see what breaks12:02
zyga-phonenoizer: s/type: migration-skill/interface: old-security/12:02
noizerzyga-phone snapcraft doesn't support it for now so I wait for today so that i can have a new snapcraft12:04
zyga-phonenoizer: yeah, I know :-(12:04
noizerzyga-phone I want it so bad xD12:05
zyga-phonenoizer: we're working on a release, you just have to wait a little longer12:05
noizerzyga-phone what is a little longer?12:06
zyga-phonenoizer: we still plan to release today12:07
zyga-phonenoizer: no further ETA12:07
noizerzyga-phone owkay12:07
=== morphis_ is now known as morphis
ppisatiricmm: if you want to put your kernel/modules on diet , turn off this option in the .config12: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 it12:20
ppisatiricmm: CONFIG_DEBUG_INFO=y12:20
ppisatiricmm: to # CONFIG_DEBUG_INFO is disabled12:20
mvoogra_: its the generic arm64 kernel, but I removed that version from the publishing history12:20
ppisatiricmm: this will greatly reduce the size of kernel / modules.ko12:21
ogra_ah, k12:21
ogra_mvo,  what makes you think that would boot ? :)12:21
mvoogra_: hopeless optimism ;)12:21
ogra_haha12:21
mvoogra_: but seriously, after uploading I remembered it would probably not work and immediately removed it from the channels12:21
ogra_ppisati, do we have any newerr dragonboard kernel than your linux-dragon410c - 4.2.0-2014.14  yet ?12:22
mvoogra_: I need to test the beaglebone though, that should work with the stock kernel12:22
ogra_i know you were working on something 4.4ish12:22
ogra_mvo, yeah12:22
ogra_GRRRR !12:23
ogra_Installing ubuntu-core.canonical_16.04.0-9.arm64_arm64.snap12:23
ogra_WARNING: could not unmap partitions12:23
ogra_WARNING: unexpected issue: remove /tmp/diskimage493904108/system/apps: read-only file system12:23
ogra_...12:23
ogra_i wish u-d-f would still work on trusty12:23
* ogra_ goes and builds on a wily system 12:23
ricmmppisati: well im basically trying to replicate the module list from your kernel package12:24
RinsanWill Snappy Core support Raspberry PI 3?12:25
ogra_Rinsan, at some point, yes12:26
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-boot12:27
Rinsanogra_, Ok thanks for the quick reply!12:27
ogra_if thats ready i'll surely try to integrate it12:27
RinsanSo it12:28
RinsanSorry... cat :)12:28
ppisatiricmm: by default our config has the debug info built-in, and then we strip the symbols out for the vanilla linux-image deb package12:29
ppisatiricmm: this way from the same config we build debug version and (after stripping) the non debug version12:30
ppisatiricmm: so either you keep the config as is, and then strip out the symbols12:30
ppisatiricmm: or disable that option12:31
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 release12:33
ppisatiogra_: i agree, last week i tried to disable that but i couldn't figure out12:41
ogra_ah, k12:41
ppisatiogra_: like, even turning off that debug option the message was still there12:41
ppisatiogra_: but yeah, i'll turn it off12:41
ppisatiogra_: about 4.412:41
ppisatiogra_: i have two trees12:41
ogra_but only one deb :)12:42
ppisatiogra_: one is the qualcomm-only and the other is the merged qualcomm+hikey12:42
ppisatiogra_: hold on12:42
ysionneauThis means syscall number 289 has been called? http://pastebin.com/uE4tGQCA12:42
ogra_ysionneau, exactly12:42
ysionneaunot sure how to know which one it is12:42
ysionneauI'm browsing the kernel sources ...12:42
ogra_ysionneau, scmp_sys_resolver 28912:43
ppisatiogra_: https://launchpad.net/~p-pisati/+archive/ubuntu/embedded/+files/linux-image-4.4.0-1006-snapdragon_4.4.0-1006.6_arm64.deb12:43
ogra_that prints the name12:43
ppisatiogra_: it's a couple of weeks old, i'm waiting for qualcomm to announce their support period for that kernel this week @ connect12:43
ogra_ppisati, ah, thanks ... do you think thats stable enough to switch to it ?12:43
ysionneaunice! it's send()12:44
ysionneauthx12:44
ppisatiogra_: it's stable, but don't switcj until we hit the archive12:44
ogra_ok12:44
ysionneausend is forbidden by default?12:44
ogra_you need the network-client "capability^Wskill^Wslot^Wplug"12:45
ysionneauahahah12:45
ogra_or just "network" not sure ... try them out12:45
ysionneauthe name bikeshedding is going crazy12:45
ogra_there are a few12:45
ysionneauthis really needs to be documented somewhere12:46
ogra_it is in total flux ... but i think there are docs (dont as me where though)12:47
ysionneauI'll try what Michael Vogt sent on march the 1st "snap.yaml skill->interface change"12:48
ysionneauor maybe it's not yet effective12:48
ogra_only half12:48
ogra_slots and plugs have been flipped around12:48
ogra_or was ist s/slots/sockets/ ?12:49
ogra_"things"12:49
ogra_:P12:49
ysionneauyes and followed by emails about changing the names again12:50
ogra_thats what i mean12:50
zyga-phoneysionneau: it's not released, just wait for the release12:50
ogra_there is a pending os snap (in testing atm) that should have the final implementations12:50
zyga-phoneysionneau: all the docs have been updated but the bit relase is in the making12:51
ysionneauif you have a link to all the security/caps/overrides stuff doc' :')12:51
ysionneauplease do share :)12:51
zyga-phoneysionneau: we'll release public docs soon13:02
ysionneau\o/13:05
ysionneaulots of interesting documentation in here: https://github.com/ubuntu-core/snapcraft/blob/master/docs/debug.md13:15
=== beowulf_ is now known as beowulf
ysionneaudon't know if you are aware of that but snappy-debug.security crashes: http://pastebin.com/ekxwPREL13:21
ogra_mvo, new os snap boots on arm64 ... i still see it trying to run grub migration (and fail), beyond that it seems fine13:23
mvoogra_: great, thanks!13:23
ogra_mvo, any package in the sotre that i should try to make sure the changes work ?13:23
ogra_*store13:23
ogra_wow, gross ... so installing a package from the store succeeds, the services dont start though and there is no error message at all13:27
ogra_Chipaca, ^^^ snappy install should really spill an error for that13:28
ogra_(syslog is full of denials at least ... but there was no idication at all that anything failed when using snappy install)13:29
ogra_mvo, i also still see bug 154376413:32
ubottubug 1543764 in Snappy "snappy classic must use officially supported lxd images from simplestream; not unsupported ones from linux-containers.org" [High,New] https://launchpad.net/bugs/154376413:32
ogra_(i.e. no classic mode at all on arm64)13:33
mvoogra_: I know :(13:37
elopioiahmad: I'm just seeing the meeting now. Are you guys still around?14:01
noizerdoes somebody used seccomp filters before in snappy?14:09
ysionneauany idea why I get this error message ? http://pastebin.com/LawTNuDi14:16
ysionneauI'm using latest commit from master of snapcraft (github)14:16
jdstrandzyga-phone: that's awesome14:22
jdstrandzyga-phone: (https://github.com/ubuntu-core/snappy/pull/591/files)14:22
zyga-phonejdstrand: I'll fan out with more of those later today, they should be easy to maintain for anyone on the security team14:26
jdstrandzyga-phone: cool, thanks14:27
zyga-phonejdstrand: I'll also move the base apparmor template14:29
zyga-phonejdstrand: so that there's no dependency on the base security templates anywhere and it's all self-contained14:30
jdstrandzyga-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 time14:32
zyga-phonejdstrand: 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 now14:34
zyga-phonejdstrand: do you know my devtools scripts?14:34
iahmadelopio, I have rescheduled it for later today, let me know if that works for you?14:42
elopioiahmad: yes, it works. We can make it 30 minutes earlier also, so you don't stay so late.14:43
iahmadelopio, ok, let me check with jibel14:44
iahmadelopio, scheduled time is fine14:46
elopioalright.14:46
ysionneauhmm that does not sound right https://github.com/ubuntu-core/snapcraft/blob/master/snapcraft/common.py#L3515:58
ysionneauwhat if you install by doing python3 setup.py develop --user15:58
ysionneau?15:58
ysionneauthen it will still try to fetch the schema from /usr/share/snapcraft15:58
ysionneaueven though it should look in the source dir15:58
jdstrandmvo: http://bazaar.launchpad.net/~click-reviewers/click-reviewers-tools/trunk/view/head:/clickreviews/common.py#L3916:00
jdstrandmvo: 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 fail16:00
* jdstrand didn't realize snappy build was still around (that's fine, it's just I would have communicated this ooner)16:01
jdstrandsooner*16:01
mvojdstrand: cool, fixing now16:02
jdstrandthanks16:02
ysionneausorry I missed that: https://github.com/ubuntu-core/snapcraft/blob/master/snapcraft/dirs.py#L3016:07
ysionneauso there is no issue :p16:08
noizerHi is it possible to do some changes on the apparmor? in an app?16:36
mvojdstrand: I pushed a branch for --no-xattrs16:36
mvojdstrand: I can not do --all-root, this breaks the OS snap which has various files that are not owned by root16:36
mvojdstrand: like /var/mail16:37
jdstrandmvo: can you do --all-root when 'type: app' or 'type: framework'?16:49
noizermvo what are the possibilities of changing the apparmor of your snap?16:50
mvojdstrand: yeah, that would be ok16:55
mvojdstrand: essentially !os -> all-root16:56
jdstrandmvo: I think that sounds like a fine start16:56
jdstrandthis does mean I'll probably not be able to do a resquash test for the os snap though16:57
jdstrandI think that is ok considering it will always come from a trusted source16:57
noizeris snapcraft already updated?17:45
ogra_kyrofa,   https://plus.google.com/+DrewFustini/posts/1Z5iPDsYaXy perhaps you might like to chime into the ROS discussion here17:56
zygaogra_: hey18:15
ogra_yo18:15
zygaogra_: FYI, we're changing some stuff around ubuntu-core-launcher18:16
zygaogra_: I'll simplify it to take less arguments and just be smarter as to what it is doing18:16
ogra_hmm18:16
zygaogra_: and I'm killing/changing some of the environment as well18:16
zygaogra_: 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 directly18:16
zygaogra_: I've dropped SNAP_FULLNAME18:16
zygaogra_: none of them do, it's just FYI18:16
ogra_ah18:17
zygaogra_: and SNAP_ORIGIN becomes SNAP_DEVELOPER with actual developer bits inside18:17
* ogra_ has never used either :)18:17
ogra_thanks for the info though :)18:18
enoch85kyrofa: hey there18:53
enoch85kyrofa: sorry, been busy the last weeks18:53
enoch85kyrofa: I felt confident in your work, it felt like I was only slowing things down :)18:54
=== jkridner|work is now known as jkridner
enoch85kyrofa: anything I can help you with?19:14
zygajdstrand: hey20:12
zygajdstrand: aroudn?20:12
jdstrandzyga: hey, I have a little time before my next meeting20:36
zygajdstrand: hey, I'm changing ubuntu-core-launcher a little20:42
zygajdstrand: I'll make it take just 'snap.[app]' + command to execute as input20:42
zygajdstrand: and derive all the security tokens from snap.[app]20:43
zygajdstrand: this affects aa profile, seccomp and the udev tag20:43
zygajdstrand: I wanted to let you know that this is happening20:45
zygajdstrand: also the launcher will change the name of the executable but that's less important20:45
zygajdstrand: (I mean that the launcher will be renamed, not that the launched application will think it got renamed)20:45
jdstrandzyga: 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 generation20:45
jdstrandzyga: how are you going to derive all security tokens from snap.[app]?20:47
zygajdstrand: I know, I'll handle both changes20:47
jdstrandeach command has a different profile and how will you determine the version?20:47
zygajdstrand: I plan to rename the aa profile to snap-$snapName.$appName20:47
zygajdstrand: we'll drop the version20:47
jdstrandthese are big changes20:47
zygajdstrand: various files will be hard-coded (location is /snappy/$snapName/current/ + $command20:48
jdstrandhave they been discussed anywhere else?20:48
zygajdstrand: we've just brainstormed this on telegram a little with niemeyer and Chipaca20:48
jdstrandI wish I was part of that conversation20:48
niemeyerjdstrand: Sorry, this has been talked about literally an hour ago20:49
niemeyerjdstrand: I can provide the full background to it20:49
jdstrandunfortunately this is a difficult day to participate in these conversations because I have a ton of meetings20:49
niemeyerjdstrand: 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 reviews20:50
jdstrandis there a doc or something I can look at/think about/respond to?20:50
jdstrandI see20:50
jdstrandit sounded more concrete a moment ago :)20:50
niemeyerjdstrand: No, but I can either: a) Explain here; or b) Write an email and send to the list20:50
niemeyerjdstrand: The proposal is concrete20:51
jdstrandI don't mind changing stuff, I just want to understand why we are changing and the changes themselves20:51
niemeyerjdstrand: But it's not done until we say so20:51
niemeyerjdstrand: Okay, do you prefer a or b?20:51
niemeyerTo be clear, this is my proposal.. Chipaca hasn't seen it yet as it's too late there20:52
jdstrandI am not going to have time for 'a' today. I will have time for 'a' tomorrow. I could even do a hangout20:52
jdstrandif that doesn't work, 'b'20:52
jdstrandmaybe a hangout with the 5 of us?20:52
niemeyerjdstrand: 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 that20:52
jdstrandtomorrow at 1500 UTC-ish20:52
jdstrandok, that's fine too20:52
zyga+1, thanks everyone :)20:53
niemeyerIndeed, thanks to you both20:53
jdstrandnp20:54

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!