bushis there a set of comprehensive documentation on creating a ubuntu core port for a custom board that anyone knows of?00:20
frecelbush: I couldn't find anything, it would be nice if something like this existed00:21
bushI'm stuck trying to figure out how to include device specific bootloaders (FSBL, u-boot, etc.)00:22
frecelbush: what device are you working on?00:22
frecelbush: https://developer.ubuntu.com/en/snappy/guides/porting/00:23
bushthe target is ARM Cortex-A9, similar to BBB and RPi00:23
frecelI managed to find something00:23
bushI've followed that and exhausted a few other (outdated) guides, blogs, etc.00:24
bushIt seems the documentation isn't moving as quickly as the development, as I'm sure we've all been guilty of.00:25
frecelyeah, this seems to be the common case for fast moving projects00:27
sergiusensbush, where are you stuck wrt bootloader setup?01:21
jeffesquivelsbush: zynq? that's cool... I'm interested in the FPGA part of it01:21
jeffesquivelsbush: I think that's what the snickerdoodle has01:21
jeffesquivels(sorry about being OT, he he)01:22
bushsergiusens: I can't figure out how to specify a bootloader or .dtb within a device package when building an image with 'ubuntu-device-flash'01:35
sergiusensbush, you need to create an oem snap and pass --oem to u-d-f01:43
sergiusensone sec01:43
sergiusensbush, something like http://bazaar.launchpad.net/~snappy-dev/snappy-hub/snappy-systems/files/head:/beagleblack/01:44
bushsergiusens: I just include the oem snap within the device package under /assets?01:58
sergiusensbush, hmm, /assets in a device package is long gone02:24
sergiusensbush, where is this info coming from?02:24
sergiusensjdstrand, do you know why I get this http://paste.ubuntu.com/13222977/ ?02:24
bushsergiusens: One of the outdated guides I've been disecting: https://ograblog.wordpress.com/2015/01/25/porting-ubuntu-snappy-to-a-yet-unsupported-armhf-board/02:25
sergiusensbush, oh, that is indeed old02:25
sergiusensogra_, add a not mentioning it is outdated :-P02:26
bushsergiusens: Exploring the BBB package made me think the format was still relevant: https://developer.ubuntu.com/en/snappy/guides/porting/02:27
sergiusensbush, you need to create a snap out of what I just gave you and do ubuntu-device-flash ... --oem <thesnap> ...02:27
sergiusensthe yaml is indeed outdated02:28
sergiusensbush, use this as a base http://cdimage.ubuntu.com/ubuntu-core/daily-preinstalled/current/xenial-preinstalled-core-armhf.device.tar.gz02:29
bushseriusens: awesome, thanks.02:30
sergiusenschange $arch if relevant02:30
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
soffoklHey guys, we still have big problems with disk IO on Ubuntu Snappy for virtualbox.04:16
soffoklDisk blocked sometimes without any reasons, even just copying file.04:16
soffokldmesg shows following http://pastebin.com/M96u8Che04:16
soffoklWe are using SSD only systems and disk on host system not loaded.04:16
soffoklThere is no such problems with other OS on virtualbox.04:16
soffoklChecked on different hardware with 15.04, 15.10, 14.04, same results.04:16
soffoklogra_, Chipaca please help us, we have no idea about direction to dig04:17
=== chihchun_afk is now known as chihchun
liuxgI have a simple snappy project at https://github.com/liu-xiao-guo/go-webserver. If I do not want to use "source: git://github.com/liu-xiao-guo/golang-http" in the snapcraft.yaml to compile the go. Instead, I want to make the source code locally.  how can I modify the snapcraft.yaml file?06:39
mvoliuxg: hm, does the line "source: /home/liuxg/path/to/golang-http" work?06:47
liuxgmvo, I am not sure about it. Let me try it. thanks06:48
liuxgmvo, it does not seem to work http://paste.ubuntu.com/13225257/06:51
liuxgmvo, we have examples to show how to pull the sources, but it does not show how to compile a project whose sources are local.06:52
mvoliuxg: interessting, what version of snapcraft is that? the code has examples for local sources, e.g. "source: ." or "source: my-app". however no absolute paths in the examples, so maybe thats the problem06:54
mvoliuxg: could you try a relative path and put the source inside the dir? let me try to find you an example06:54
liuxgmvo, snapcraft (0.4). it shall be latest.06:55
mvoliuxg: yeah, that should be fine. here is a trivial example with local source https://github.com/ubuntu-core/snapcraft/tree/master/integration-tests/data/local-source06:55
mvoliuxg: and here is one that uses a subdir https://github.com/ubuntu-core/snapcraft/tree/master/integration-tests/data/simple-maven06:56
mvoliuxg: maybe thats helpful? i.e. put the snapcraft.yaml directly into your go source and use "source: ."?06:56
liuxgmvo, this is the result of it http://paste.ubuntu.com/13225279/06:57
liuxgmvo, do you mean that i need to move my snapcraft to the source code directory?06:58
liuxgmvo, for go, I need to have a directory name to come out the final binary name, right?06:59
mvoliuxg: hm, something funny is going on there, let me finish my current task and branch your code, it really should not crash like this07:00
liuxgmvo, ok. thanks for your help. I think it is a common practice to have the code locally. Once everything is fine, then it is pushed to the github or whatever.07:01
mvoliuxg: yeah and its supported in general, seems like there is a bug in the detection of whats local07:02
liuxgmvo, right. please let me the result of your testing.  thanks07:03
dholbachgood morning07:37
liuxgmvo, do you have any findings?07:44
mvoliuxg: sorry, got distracted. I think its a bug in the go plugin code, I'm investigating a bit now08:06
liuxgmvo, oK. thanks for the help. by the way, do we need to report a bug for it?08:08
mvoliuxg: I think a bugreport is prudent, yes. at least it should not crash08:08
liuxgmvo, OK. so, I just report a bug against for snapcraft at https://bugs.launchpad.net/snapcraft/+filebug08:09
liuxgmvo, I have reported the bug at https://bugs.launchpad.net/snapcraft/+bug/151513208:13
ubottuLaunchpad bug 1515132 in Snapcraft "Snapcraft crashes after defining a local source for a golang project" [Undecided,New]08:13
dholbachliuxg, I think snapcraft might more be a thing for sergiusens and tedg to answer08:14
liuxgdholbach, it is alright. I will check it with them later on :)08:14
mvoliuxg: yeah, I poked it a bit but it seems like there is more to it, i.e. seting up a go workspace or copying it into the go workspace etc08:16
liuxgmvo, setting a go env is straightforward. apt-get install golang, it will install everything, I think.08:17
JamesTaitGood morning all; happy Wednesday, and happy Armistice Day! 😃10:09
longsleepWhat is the best way to report and discuss security issues with Snappy?10:26
ogra_file bugs10:36
Chipacalongsleep: use the 'security' flag when filing the bug10:49
Chipacasoffokl: uh, ouch?10:49
Chipacasoffokl: are these errors in the host's dmesg, or in the vm's dmesg?10:50
soffoklChipaca, on vm's dmesg11:04
Chipacasoffokl: from googling the error it seems to have something to do with weird disc configurations11:07
Chipacabah. "weird" for a vm or an iot thing11:07
Chipacalike raid 6 on sas11:07
Chipacasoffokl: e.g. http://unix.stackexchange.com/questions/34173/mptscsih-ioc0-task-abort-success-rv-2002-causes-30-seconds-freezing11:08
ogra_especially since you wouldnt have a raid6 in snappy :)11:10
ogra_why is that driver even loaded inside the VM11:11
Chipacadunno if it's raid6 :)11:11
Chipacabut it seems to be sas11:11
Chipacawhich, sure, should work, but no idea how good/bad virtualbox's sas driver thing is11:11
Chipacaalso, always be suspicious of expensive storage hardware that just happens to have the same name as a secret agency11:12
soffoklmy vm is just OVA from Snappy website11:13
soffoklon the host system only single ssd11:14
Chipacasoffokl: i don't know who or how we build those; could you look up how it's set up? in the vb settings i mean?11:15
soffoklChipaca, I tried to change every settings that i found in vm configuration, nothing changed11:17
soffoklActually, we found workaround, we converting img for KVM from Snappy page to vmdk and using it for virtual box. And it works fine :)11:18
ogra_hmm, interesting11:19
soffoklfor OVA even copying 500MB file into VM freeze several times11:22
Chipacaogra_: do you know who builds the ova?11:23
Chipacasounds like something they need to know about11:23
Chipacasoffokl: bug in virtualbox11:24
ogra_Chipaca, no, i dont11:25
ogra_i'd expect the cloud people11:25
soffoklChipaca, Opened 4 years ago, hmmm11:25
frecelogra_: do you know anything about anyone actively working on a snappy build for intel edison?13:13
ogra_frecel, nope, i dont ... i know that lool took a look at it ages ago and there were probs13:13
freceldo you know when loop tends to hang out on irc?13:16
longsleepIs there some gear so a snap can run its own config hook, or should that be handled by the snap internall?13:20
longsleepi have a chicken egg issue, and need to make sure the config hook was run at least once before start13:20
longsleepbefore start of a service in the snap i mean13:20
=== fgimenez_ is now known as fgimenez
ogra_longsleep, make it touch a stampfile, add a check for the stampfile to the startup script13:25
longsleepogra_: yeah, but how do i run the config hook from the startup script? Directly?13:26
ogra_thats what i do13:27
ogra_if there is no initial config file i run the config.sh script once in my snap13:27
longsleepok, i was wondering if there is a way to trigger whatever "snappy config" is doing13:27
longsleepyeah makes sense, i can certainly do that13:28
ogra_snappy config only pipes strings into your hook anyway13:28
ogra_or rather "a string"13:28
longsleepright, but maybe it does or will do something more13:28
ogra_i think there was a bug open to restart the service once it applies a config, but that wont affect you on first start13:29
ogra_thats the only planned enhancement i know about13:29
longsleepogra_: yes, i think i created that bug13:29
longsleepfair enough13:29
ogra_ask Chipaca, he migh know more :)13:29
Chipacame? i know nothing13:35
* Chipaca <- in a meeting13:35
=== awe is now known as awe|afk
=== barry` is now known as barry_
=== barry_ is now known as barry
jdstrandsergiusens: it might be a bug in the review tools. there is some pretty ugly code due to the click compat bits that I think might be getting confused (ie, it is trying to detect if the yaml and the click compat manifest are in sync cause if they aren't, the snap could be crafted)14:28
jdstrandsergiusens: this won't be any issue once the pending feature branch mvo and I are working on lands (and I make the corresponding change to the review tools)14:29
jdstrandsergiusens: Chipaca saw this too the other day. I think something changed in snappy that started triggering this issue14:29
jdstrandsergiusens: can I have the snap?14:29
Chipacaabout what?14:30
Chipacajdstrand: is it about network-client?14:30
jdstrandit seems like snappy build isn't generating the compat apparmor profile correctly14:33
jdstrandwhen you specify nothing, you are supposed to have the default template and 'network-client'14:33
jdstrandoh, actually, I think I may know the issue14:33
jdstrandthis might be related to the networking -> network-client change14:34
jdstrandI'll fix that real quick14:34
jdstrandbut again, all this compat code will be leaving both snappy and the review tools once mvo and I are down with the policy regeneration branch14:34
mvojdstrand: :-D indeed, thats going to be a glorious day. let me know how I can help further, I prepared the warning for the compatitbility if security-override.apparmor,seccomp is used and I wrote the ubuntu-core-launcher upate14:36
jdstrandmvo: I saw! I think that is perfect. just ignore that it is there14:36
jdstrandmvo: I'm preparing an apparmor upload that is related to snappy image policy uploads and the new /var/lib/snappy/apparmor/profiles dir14:37
jdstrandmvo: I will have that done this morning and then get back to reviewing your changes14:37
rickspencer3stgraber, so, lxc is not working for me on my up to date (version 9) Beagle Bone Black: http://pastebin.ubuntu.com/13227521/14:38
jdstrandman I hate this compat code in the review tools...14:41
mvojdstrand: it will be over soon14:43
mvojdstrand: soon we have it all replaced14:44
=== awe|afk is now known as awe
sergiusensmvo, well, well; there will be one more point of sync as snapcraft would be assembling the snap14:48
=== chihchun is now known as chihchun_afk
stgraberrickspencer3: hmm, not completely clear what's the problem there. It looks like something's failing with lxc-net in there but then lxd itself is running or lxd-images would have failed differently...15:29
rickspencer3stgraber, ok, what should I do?15:29
stgraberrickspencer3: I'd recommend doing a reboot if you haven't yet, see if that gets things back in working order. If not, another possibility for that error would be that you're running out of disk space somehow.15:29
rickspencer3stgraber, I did reboot15:30
rickspencer3stgraber, what's a good way to check disk space?15:30
stgraberrickspencer3: "df -a | grep writable" may do it, it's a bit of a mess with all the bind-mounts though15:31
rickspencer3stgraber, http://pastebin.ubuntu.com/13227923/15:31
stgraberthat should be fine15:32
stgraberok, let me try to reproduce that issue on my beaglebone black here15:32
rickspencer3thanks stgraber15:33
jdstrandbeuno: can you pull r543 to the store. this is needed to address the error in things like https://myapps.developer.ubuntu.com/dev/click-apps/3675/seq/4/15:41
jdstrandbeuno: beuno more review tools changes will be coming in the next week or so, but this one is kinda needed now15:42
beunojdstrand, yeap. cc/ pindonga15:44
jdstrandbeuno: also, I don't seem to be able to waive https://myapps.developer.ubuntu.com/dev/click-apps/3675/seq/4/ through15:44
sergiusensjdstrand, beuno let me calm eveyone a bit though; only us devs see that as it is only in the tools-proposed area or xenial at most15:45
jdstrandbeuno: the first failure is what I fixed in the review tools. the second is Chipaca wanting access to snapd and I'm presuming he knows what he is doing :)15:45
stgraberrickspencer3: fyi, I did manage to reproduce the issue here on my bbb, I'm trying to figure out what's going on now15:55
rickspencer3thanks stgraber15:55
rickspencer3stgraber, if you give me a link to the project, I will log a bug for you if you want15:55
stgraberdoh, found the issue15:56
stgraberthe bbb doesn't have enough RAM to process the cloud image :)15:56
rickspencer3stgraber, ouch15:57
stgraberlooks like we could change lxd-images to use less RAM, it'd use more I/O though but probably still worth doing15:59
stgraberI'll file an upstream bug for that15:59
stgraberrickspencer3: https://github.com/lxc/lxd/issues/130016:02
rickspencer3stgraber, ok, doesn't sound like it will be fixed quickly16:03
rickspencer3keep me posted16:03
stgraberrickspencer3: fix should be pretty straight forward but it'll take another couple of weeks before it's in a release that hits snappy16:05
rickspencer3stgraber, ack, I get it16:05
stgraberrickspencer3: though you'll be able to grab the lxd-images script from git and manually use it until then16:05
rickspencer3stgraber, ooh16:06
rickspencer3ok, just let me know when you have something for me to try16:06
jdstrandbeuno, pindonga: actually, can you make that r544? r544 has the vendor checks removed too16:07
jdstrandbug #151052216:07
ubottubug 1510522 in Snappy "Remove vendor from meta" [Wishlist,In progress] https://launchpad.net/bugs/151052216:07
=== ev_ is now known as ev
=== Ursinha_ is now known as Ursinha
=== clivejo_ is now known as clivejo
jdstrandbeuno, pindonga: heh, make that r545 -- I missed sergiusens branch which I just merged16:29
stgraberrickspencer3: https://github.com/lxc/lxd/pull/130116:33
rickspencer3stgraber, nice16:34
stgrabertesting on my bbb now (prepared it on x86 obviously :))16:34
rickspencer3I'm working on something else right now, but if you want me to try your fix later, just post me some instructions16:34
stgraberdoh, /tmp is a tmpfs on snappy, so that's not helping much as it still ends up in memory16:38
stgraberpretty sure /tmp on tmpfs is a bad idea for low-memory devices...16:38
stgrabermvo: ^16:38
stgraberrickspencer3: sure enough, the MemoryError is now replaced by a No space left on device :)16:39
rickspencer3stgraber, so, I guess we need an image for a bigger sd card?16:39
stgraberwhat we'd need is for snappy to detect that the board has low memory and setup /tmp as a path on /writable instead of an in-memory tmpfs16:40
stgraberI'm basically doing that manually here now to confirm that this then all works16:40
mvostgraber: thanks! indeed, thats our default setup16:51
mvostgraber: i.e. use tmpfs16:51
stgraberrickspencer3: http://paste.ubuntu.com/13228814/ <- confirmed that this works fine here17:03
stgraberrickspencer3: so moving forward, hopefully snappy won't be using tmpfs for /tmp on beagleboneblack and LXD 0.23 will contain the lxd-images fix, at which point everything should just work (albeit very slowly, but that's because of the hardware)17:04
=== alexabreu is now known as alex-abreu
=== genii is now known as fishbot
=== fishbot is now known as genii
jerryGhow do i start mir manually?23:01
csandersI'm running through the "your first app" tutorial. After building the example webcam .snap, can I locally install this on my Snappy Ubuntu Core VM?23:50
csandersThe guide moves on to "publishing apps" but doesn't mention installing this to test that it built correctly.23:50

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