=== laza_ is now known as laza === xnox_ is now known as xnox [06:45] good morning [08:10] good morning [09:49] Good morning all! Happy Thursday, and happy Get Out Your Guitar Day! 😃 [10:45] hi, I'm having trouble with my mirror, can I redirect snapcraft 2.2 (when pulling) to use the main archive instead? [10:46] whats the new SNAP_APP_DATA_PATH env? [10:46] hm. guess i would need to upload hello world again [10:47] didrocks: you made a central place for examples in github right? [10:52] okay, the mirror is up again now [11:01] Hi guys is nginx supported on snappy? [11:01] Chipaca, tickle [11:02] noizer, if you manage to package it, it is supported :) [11:02] nicee :D just i can't get it started xD [11:03] ogra_ where can we find the image for the dragonboard for snappy? [11:03] are you not on the mailing list ? [11:04] oooh ok sorry i didn't have time to look at it the last couple of days [11:04] http://people.canonical.com/~ogra/snappy/all-snaps/dragonboard/ [11:04] i mailed yesterday ;) [11:04] (snappy-devel that is) [11:05] as for ngnix ... i think the spreedbox guys use it in their spreedbox snap in the store [11:05] no idea where their code is (and this is for 15.04 only iirc) [11:05] you could install their snap on a 15.04 armhf install and inspect the installed snap though [11:06] ok thx ogra_ === pindonga` is now known as pindonga [11:40] ogra_, tockle [11:46] asac, he has, but it seems bare bones now https://github.com/ubuntu-core/demos [11:50] Chipaca, damn, i forgot what i wanted to ask you now :( [11:51] ogra_, \o/ [11:51] Chipaca, oooh ... ubuntu-snappy ftbfs on arm64 since a while again, i need to re-build images after fixing the resizing for dragonboard setups [11:52] would be good if someone could take a look (and since mvo is away ...) [11:52] ogra_, ouch [11:53] i'll take a look in a bit [11:53] thanks ... take your time though ... i'm still working on the resize fixes [11:57] sergiusens: ok thats demos then... guess moving snappy-examples to 16.04 in its current place is worthwhile then still... [12:07] asac: yeah, it needs sorting, and it quite empty, but it should be a central place [12:07] the difference I see is that demos will be more complete real pieces [12:07] and snapcraft should keep examples separated [12:07] (as more "simple way of doing X") [12:11] noizer: try https://github.com/zyga/devtools/blob/master/ubuntu-image and tell me if it works for you [12:12] zyga what is that? [12:13] is that for the dragon board or is that for my nginx [12:13] ogra_: hi, i'm trying to boot the new all-snap dragonboard image, but i'm not seeing any output on hdmi. do you have any ideas on why not? [12:14] ogra_: same setup works ok with the install image from 96board website [12:14] joc__, because the boot console still points to serial ... once it booted you should get a login prompt on hdmi though [12:14] (i definitely do here) [12:14] joc__, also regard the big fat warning in the readme [12:14] (to not use a card bigger than 4GB) [12:16] ogra_: will it resize and reboot before the hdmi login prompt? [12:17] it resizes before it mounts anything [12:17] (so thats a yes) [12:18] i'm hoping to have that bit fixed today :) [12:18] ok thank you, plars was saying that he had one successful boot before the resize would stop his board working so I was hoping for that - he may have been using serial though [12:18] kyrofa, when you get on, mind looking at https://launchpad.net/snapcraft/+milestone/2.2.1 ? [12:20] joc__, i havent tried booting without the serial board attached, perhaps that blocks somewhere else though ... [12:20] * ogra_ gives that a try [12:24] noizer: that's for building images easily [12:24] noizer: including dragonborad [12:26] zyga can I make then custom images for myself? [12:27] zyga ps I will first make my nginx up and running [12:28] Who will also join the clinic tommorow? [12:28] noizer: depends on what you mean by custom [12:28] noizer: anyway, have a look, the tool is _tiny_ [12:29] zyga ok [12:29] joc__, hmm, yeah, looks like it hangs somewhere at the bootloader if the serial board isnt attached .... [12:30] Good morning [12:30] joc__, so for now, please attach the serial board, i'll research that [12:31] Good morning kyrofa [12:32] sergiusens, what should I be looking at here? [12:39] good morning kyrofa! [12:40] kyrofa, the PRs :-) [12:40] Hey noizer, didrocks :) [12:40] * sergiusens needs to go to the bank, will bbl [12:40] sergiusens, ah, that's what I'm on now [12:40] sergiusens, alright, seeya! [12:41] ogra_ What is the name of the application of spreedbox? [12:41] noizer, spreedbox :) [12:41] (iirc ) [12:41] kyrofa Hi do you know where I can get more information about netwerk listeners etc [12:42] ppisati, did you ever try to boot without serial board attached ? seems it hangs at the bootloader [12:42] noizer, you mean what permissions are encompassed by it? [12:42] yes [12:42] ppisati, dragonboard that is [12:42] ogra_: uhm no, i never trie [12:42] d [12:42] let me tru [12:42] let me try [12:42] kyrofa its for the rolling version. Or will it be explained tomorrow on the clinic? [12:42] seems to not be kernel related ... i just did set console=tty0 and it still hangs [12:44] ogra_ I installed the 15.04 version on my Raspberry Pi 2 and tried to install spreedbox with the following command: sudo snappy install spreedbox but he dont find it [12:45] ppisati, wow .... trying to set "stdin, stdout or stderr" at the uboot prompt with setenv actually complains [12:46] i cant set it to serial,lcd [12:46] noizer, I'm not aware of any documentation on each one. jdstrand might know more [12:48] ogra_: ## Error inserting "stdin" variable, errno=22 [12:48] :O [12:48] yeah [12:49] i know i can set that var on the rpi [12:49] i did that multiple times [12:49] ogra_: i was using https://github.com/hallor/u-boot.git / dragonboard-for-mainline-v2 [12:50] ogra_: i just did a git fetch, and there's a 'dragonboard-for-mainline-v3' [12:50] let's see [12:51] ah [12:52] though i fear there is some build time hardcoding going on here [12:56] ogra_: same story, doesn't boot and you can't set stdin&c [12:57] yeah, i suspected that [12:57] i just pinged in #96boards ... lets see, perhaps a known issue [12:57] ogra_, i can't find the build failure email, could you fwd it me? [12:58] i have to dig it up [12:58] Cghbtw, vivid failed too (on arm64, powerpc and ppc64el) [12:59] https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+packages [12:59] arm64 xenial is here https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+build/8962323 [13:01] => setenv stdout serial,lcd [13:01] ## Error inserting "stdout" variable, errno=22 [13:01] => setenv stdout serial [13:01] => [13:01] ppisati, ^^^ [13:01] so its the parameter [13:01] just setting it to serial works [13:01] oh ok [13:01] kyrofa did you already installed an apache in a snap? [13:02] i guess we miss a build time option somewhere in uboot to enable lcd at all [13:02] noizer, indeed, yes [13:02] noizer, that owncloud snap uses apache [13:02] though i still dont get why it hangs hard ... it shoudlnt [13:03] general question: if the app has some files in /usr/share/ - but with snappy, they're instead in $SNAP/share or $SNAP/usr/share, what's the smartest way to have the app (or one of its library dependencies) look there instead of in /usr/share ? [13:03] kyrofa owkay i will look for the yaml because I can't run nginx :s [13:03] noizer, how come? [13:03] noizer, I can share my plugin with you if you like [13:04] yea i would like that maybe i can get some info for my nginx from there [13:05] noizer, alright. It's still a work-in-progress, no decent documentation or anything, but it works: https://github.com/kyrofa/owncloud-snap/blob/apache_plugin/parts/plugins/x_apache.py === nessita_ is now known as nessita [13:05] ppisati, ah, seems we just need to set CONFIG_LCD in dragonboard.h [13:06] kyrofa You didn't installed it with stage-packages? why? [13:06] noizer, you give it a source (like any other plugin) and it'll unpack it into htdocs. You also specify the modules you want built/enabled, and you can specify some sections of the config and a startup script if you want [13:07] noizer, because debian packaging uses a different apache layout than the standard, and it's all setup in a post-inst [13:07] postinst, rather [13:07] kyrofa ok. [13:07] noizer, since Snapcraft only unpacks debs, that stuff never gets run [13:08] noizer, so it led to a lot of hackery. Not to mention this way I could tune it exactly the way I wanted and get it down to a few megs [13:08] so nginx won't run with the deb package? [13:08] noizer, it might, it might not. Depends on how it's packaged [13:08] ogra_: let m,e try that [13:09] noizer, that was the first lesson I learned making that massive snap: debian packages only get you so far in snappy [13:09] ok so maybe the best way is from source code. [13:09] noizer, indeed [13:11] kyrofa, ok thats a lot harder then using a deb package :p [13:11] kyrofa lets give it a try [13:11] noizer, yeah it's a bit complex. Apache was particularly painful because it writes its prefix _everywhere_, config files, scripts, etc [13:12] hopefully is nginx not so painful :p [13:12] ogra_: nope, it doesn't compile with only CONFIG_LCD [13:12] noizer, heh, good luck [13:12] kyrofa thx. if I succeed maybe then i will post an easy example of it for other users of Snappy [13:13] ppisati, how does it fail ? [13:13] noizer, the way snapcraft works requires software that can be configured and built in one location, and run in a complete different location, with different paths. Some software works fine that way. Some though, like apache, do not [13:13] ogra_: http://pastebin.ubuntu.com/15015948/ [13:14] ogra_: CONFIG_LCD is just the machine independent code, every hw needs some specific bits to make it work [13:14] crap [13:14] ogra_: we should talk to guy who ported uboot to this board [13:15] ppisati, thats hallor in #96boards i think [13:18] kyrofa is that not a good idea to use docker in the snap. Because docker have already a build with nginx? [13:19] noizer, hmm... I'm not sure I understand [13:19] Ok you know docker? So when I'm installing docker and on the docker side you can install nginx easily (normally) [13:20] noizer, alright, I'm with you so far [13:21] So when im installing nginx on docker. into my snap then can I maybe refer to my data in my nginx.conf? [13:22] noizer, that's where you lose me. How does docker relate to your snap? [13:22] hmm i don't know is it possible to use docker and nginx into my snap? [13:22] kyrofa i didn't use docker before so I'm really noob at docker [13:24] noizer, okay so you're thinking "It's easy to put nginx on docker. It's hard to put nginx into the snap. So can I get docker into my snap instead and put nginx on there?" [13:24] noizer, sound about right? [13:24] kyrofa yes :p [13:24] noizer, I know a docker framework exists on 15.04, though I'm not sure what the plans are for 16.04 [13:25] oooh ok xD i will do it the hard way and I think the best way then :D [13:25] noizer, you'd have to depend on the docker framework and make your .snap that way. I've not done that, though there are people here that have [13:26] noizer, yeah, there's non-negligible overhead associated with things like docker. You don't want it if you don't need it [13:27] kyrofa ok. I will you update on my status of nginx. If you want that :D [13:27] noizer, sure :) . It may not be as bad as you think! [13:28] kyrofa ok hopefully xD [13:30] noizer, I strongly suggest you experiment with it outside of snapcraft until you understand the build process [13:32] kyrofa [13:32] ok i will do that first [13:33] ppisati, try bui9lding with CONFIG_USB_KEYBOARD (and perhaps with CONFIG_SYS_USB_EVENT_POLL_VIA_CONTROL_EP) [13:36] ogra_: compiling... [13:40] dragonboard410c => setenv stdin serial,usbkbd [13:40] ## Error inserting "stdin" variable, errno=22 [13:40] ogra_: ^ [13:40] bah [13:40] with these: [13:40] ok, i gues si have to disable bootdelay then [13:40] +#define CONFIG_USB_KEYBOARD [13:40] +#define CONFIG_SYS_STDIO_DEREGISTER [13:40] ogra_: you mentioned something else before [13:40] ogra_: setenv stdin ... [13:41] i only know serial.usbkbd [13:41] err ... comma indeed [13:41] ogra_: oh ok [13:42] * ogra_ tries the evil way [13:42] ubuntu@localhost:~$ sudo fw_setenv stdin serial,usbkbd [13:42] ubuntu@localhost:~$ [13:42] muhahaha ! [13:42] oh [13:42] did it work? [13:42] ubuntu@localhost:~$ fw_printenv |grep stdin [13:42] stdin=serial,usbkbd [13:42] ubuntu@localhost:~$ [13:42] it sets it [13:43] weather it will boot is another question :) [13:43] reading uboot.env [13:43] In: serial [13:43] Out: serial [13:43] nope [13:43] ignores it [13:43] doh :( [13:44] Environment size: 4424/131067 bytes [13:44] => printenv stdin [13:44] stdin=serial [13:44] wow [13:44] it even unsets it during boot [13:44] (it accepted my bootdelay change) [13:45] well, people wanting to debug the bootloader can always set bootdelay from the running system, so i guess i'll default to bootdelay=0 [13:46] ogra_: k, i sent an email to the uboot guy, just in case (you are in cc:) [13:46] thanks [13:47] he already said there might be a bug in hserial [13:48] joc__, thanks a lot for bringing that up !!! [13:48] (no dev would ever have catched it since we all boot with serial board attached ) [13:55] ogra_: np, thanks for the info [14:04] noizer: re documentation, install snappy-debug then do 'snappy-debug list -i' [14:04] noizer: the 16.04 names will be changing based on skills work though [14:05] hopefully those will be settled within the next couple weeks [14:13] noizer, questions over here please :) [14:15] jdstrand ok [14:16] ogra_, https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+build/8962323 [14:19] ogra_, the good news is, I did nothing more than rebuild [14:19] ogra_, but that is also the bad news [14:19] ogra_, there are tests in there i'm not proud of :-( [14:19] that depend on the test starting and ending the same minute [14:46] Chipaca, well, at least we have a binary now to make the image build, thanks a lot ! [14:46] Hi I have a question about Ubuntu as an OS [14:58] sergiusens, FYI, as soon as netbase is in an all-snaps image I'll make MOOS an example. Until then, if you're curious: https://rainveiltech.com/posts/that-s-one-snappy-moos [15:00] kyrofa, nice === vrruiz_ is now known as rvr [15:00] kyrofa, oh, thanks for the reminder :P [15:00] * ogra_ hacks the seeds [15:00] ogra_, ha! Thanks again on that :) [15:01] ogra_, can you upload new OS images? or is it only mvo? or does slangasek have the priv as well? [15:01] * sergiusens heads back home [15:01] sergiusens, walk safely. Look both ways [15:02] sergiusens, i dont know what account mvo used for them ... i'd rather have hiom do it [15:03] fgimenez: why do we have offline slaves? Did I break something? [15:03] kyrofa, seeded and pushed, next image should have it [15:04] * kyrofa hugs ogra_ [15:04] elopio, i have no idea, was waiting to ask you :) [15:04] I don't know. Didn't notice yesterday. [15:05] i'll remove them [15:08] Hey didrocks I wanted to ping you regarding the owncloud snap. Is that in a good state for demo? We still have some time to fix things if necessary [15:08] kyrofa, an arm64 buiold would be so awesome :) [15:08] kyrofa where can i see the deamons running in a snap? [15:08] ogra_, ha! I'm working on it, the dragon keeps dying [15:09] noizer, snappy service status [15:09] kyrofa, even with the new image ? [15:09] ogra_, ah, I haven't tried yet. I'll get back to you [15:09] great [15:11] kyrofa: I guess it's good enough for the demo, I played with it and didn't spot anything bad :) [15:12] thanks for pushing this btw! [15:12] didrocks, you GUESS? Psshh [15:12] didrocks, and no problem, it's nice to get it some exercise [15:13] kyrofa: I still think (but maybe once 16.04 is out) we need to centralize all those "demos" in the git repo [15:13] but I tend to wait for 16.04 for now (at least, that it starts to stabilize with snapcraft 2) [15:13] so I hope for end of March/early April :) [15:13] didrocks, yeah it's too much of a moving target right now [15:14] seen that :p [15:14] ogra_, nooo, I don't have a 4GB SD card [15:14] didrocks, heh, yeah I bet you have :P [15:14] kyrofa, you can resize the writable partition before first boot [15:14] just use gparted [15:15] ogra_ can I see why it is inactive my service? [15:15] or gnome-disks [15:15] noizer, snappy service logs ? [15:15] ogra_, your README leads me to believe there will be nothing to resize? [15:15] or something along these lines [15:15] noizer, the only reason it would be down is if it crashed. Check the syslog for reasons (or your application's log, if any) [15:16] noizer, or yeah, snappy service logs [15:16] kyrofa, dd to a big SD ... then re-plug and open gnome-disks ... pick the writable partition and resize it to occupy all free space ... then the resite on boot wont kick in [15:16] I keep forgetting about that command [15:16] *resize [15:16] ogra_, ahhh, okay [15:17] it checks for more than 10% free space on the SD ... if thats not there it wont run [15:17] ogra_, kinda neat that it's there at all, honestly [15:17] yeah, i just wish i had picked the right partition tool from the start [15:18] (who would have thuoght we ever have u-boot devices with GPT partitions !) [15:18] ogra_, it gets ingrained and it's difficult to switch, eh? [15:18] ogra_ i got no error in my syslog or in my log of the service [15:18] well, it needs a bunch of code changes ... it is just annoying to test since you need to dd all images for all devices to SD multiple times [15:19] enervingly time consuming [15:19] ogra_, ah, sure [15:30] * zyga reflashed his BBBs [15:35] fgimenez: hangout. [15:36] elopio, yep omw [15:56] ogra_, do I need to do anything fancy with these switches on the dragon to boot? [15:57] you need to turn the SD one on [15:57] and leave all others off [16:03] could it be taht running udf as root (not sudo)... is not working at all? [16:04] i get weird error that it cannot create /root/.cache etc. [16:07] noizer, by the way, if you're curious about the actual apparmor snippets relating to each capability, check out /usr/share/apparmor/easyprof/policygroups/ubuntu-core/16.04/ [16:09] okey i see [16:09] ps i tried to run the standard nginx ( installed with stage-packages) and it do not work at all :s [16:09] noizer, /usr/share/seccomp/policygroups/ubuntu-core/16.04 for seccomp filters [16:10] asac, i never ran it as root, might interfere on some levels [16:10] noizer, yeah, not surprising [16:10] kyrofa i can see it start but not that it crashes in the logs :s [16:11] ogra_, gnome-disk is just showing be a bunch of unknown partitions. I'm in trusty... too old? [16:11] s/showing be/showing me/ [16:11] kyrofa so i need to compile it myself [16:11] kyrofa, you should see at least two usable ones (the last two) [16:11] but so I can see it says make serve [16:11] to build it [16:11] ogra_, nope... everything is unknown [16:12] kyrofa, the rest will most likely still be unknown today, they are part of the bootloader and use very specific IDs [16:12] thats weird [16:12] noizer, maybe. You might be able to get away with some sed magic [16:12] the last two are just vfat and ext4 [16:12] with no special signature [16:13] gparted sees that, but then gets super confused when I try to resize the ext4 saying the partition doesn't exist [16:13] hmpf [16:13] gnome-disk doesn't actually show the last two at all, now that I look closer [16:13] ogra_, just 1-7 [16:13] kyrofa sed magic? [16:13] well, you can always use gdisk on the cmdline [16:14] ogra_, ah, I didn't actually know about gdisk. Tried using fdisk to obvious dispair [16:14] yeah, the old tools all kind of lack if it comes to GPT [16:15] noizer, if for example it's dying because it's trying to save logs in a non-writable place, you can try copying a new config file over the top that uses the right paths [16:15] hmmm. running bluetoothctl hangs my pi2 ... or at least my ssh session goes down [16:16] woot, all boards operational :) [16:17] ok i will do that first [16:20] asac: maybe get beefier psu [16:20] asac: I'm using a big 5-port 10A supply [16:20] asac: works great for a small farm [16:21] hmm. you say this could be power? [16:21] it happens even without a dongle attached [16:21] hmmmmm [16:22] asac, anything in syslog or dmesg ? [16:23] ogra_: not really [16:23] let me see after this reboot [16:23] the last two times nothing was written [16:23] even though i had entries from yesterday in there [16:23] so something got persistet, but not these boots it seems [16:23] also try to use serial to make sure its only ssh/network that goes down [16:24] yeah it seems to really not persist the syslog [16:24] culd be your USB hub dying ... (since everything on the rpi is USB) [16:24] if it dowenst shut down cleanly [16:24] guess thats a bit of a bad feature :) [16:24] ogra_: could be, but i dont attach anything and just run bluetoothctl [16:24] and it dies [16:24] my pi2 is in an orange box [16:24] cant connect serial [16:25] if you have a pi2 with 16.04 just install bluez5 [16:25] asac, you have a USB NIC ... [16:25] anywsay, i connectd it now to strong USB power supply [16:25] let me try again [16:25] nope same... with 4A [16:25] yeh [16:25] just dead the second i run bluetoothctl [16:25] without attaching any dongle and nothing [16:25] k... llet me try to find my other pi2 where i can make a serial avail [16:26] i think i had another one [16:26] ogra_: which pins do i connect the ttl to? [16:27] ugh ... i dont have my rpi nearby [16:28] asac, http://workshop.raspberrypiaustralia.com/assets/console-cable-connections.jpg [16:28] (you dont need VCC usually) [16:29] yay, i like raw boards with serial console :OP [16:29] works [16:29] lets see what happens there [16:29] they look so nice on the desk [16:29] yeah, my desk is plastered with them :) [16:30] right, but its your life style to have raw boards on your desk ... i am trying to get to a clean desk (not succeeded yet) [16:30] hehe [16:30] my desk is clean ! [16:30] (everything around it is a mess admittedly) [16:31] ok first thing i notice is: http://paste.ubuntu.com/15017149/ [16:31] lol [16:31] so thats probably not the best indicuation of successful bluez5 usage [16:31] ouch [16:31] yeah [16:31] yeah [16:31] dead [16:31] morphis, ^^ [16:31] console dead when running bluetoothctl [16:31] no oops [16:31] nothing [16:31] end of life [16:31] bang [16:31] guess this is bogus stuff [16:31] thts with a USB dongle ? [16:31] no [16:32] nothign attached but serial, power through USB and LAN cable [16:32] is tere any BT onboard on the rpi ? [16:32] i dont think so [16:32] right, so why would it start then :) [16:32] kyrofa, elopio here's a weird one https://github.com/ubuntu-core/snapcraft/pull/316 [16:32] ogra_: what would start? bluez5? [16:32] yeah [16:32] i think its a deamon that should just there [16:32] until something gets plugged in [16:32] if there isnt a BT device there is nothing to attch to [16:32] also how can bluetoothctl binary just crash everything [16:33] sure, but its a service [16:33] no? [16:33] ask the kernel :) [16:33] the kernel doesnt even spit out anything before it dies [16:33] ppisati: ^^ [16:33] 16.04 pi2 ... install bluez5 and run bluetoothctl [16:33]