[06:40] <dholbach> good morning
[07:04] <fgimenez> good morning
[07:06] <davidcalle> Morning all o/
[07:20] <ogra_> https://www.kickstarter.com/projects/beaglecore/beaglecore-100-open-source-iot-device
[07:21] <zyga> ogra_: hey
[07:21] <ogra_> hey
[07:53] <vmayoral|pc> ppisati: ping
[08:34] <Chipaca> mo'in!
[08:35] <Chipaca> ogra_: finally, a secure computer! because it's not plugged in to anything at all
[08:39] <ogra_> heh, yeah :)
[08:39]  * ogra_ is off to the dentist ... back in a few hours (i hope)
[08:53] <ljose> Hi, is there a cross toolchain availalble for snappy arm? I trying to build some libraries for beaggle board in my dev machine.
[08:58] <Chipaca> ljose: what is your dev machine?
[08:59] <Chipaca> ljose: if on ubuntu, often installing gcc-arm-linux-gnueabihf is enough
[09:07] <ljose> Chipaca: thanks, I using Ubuntu 15.04
[09:09] <ljose> So I want to distribute a static library to be used with snappy, what is the recommened way to do that?
[09:10] <Chipaca> ljose: not sure I understand, how would people use the library?
[09:11] <ljose> They will use it to build new applications,  static linking with the library
[09:11] <ljose> for Ubuntu we distribute it as a collection .deb packages i386/amd64
[09:12] <Chipaca> ljose: applications are not build on snappy, so you continue to distribute it as .debs which people use to build the snaps
[09:12] <Chipaca> ljose: static linking is resolved at build time
[09:12] <Chipaca> ljose: so, distribute debs, people build with those, done
[09:12] <ljose> Chipaca: cool
[09:14] <JamesTait> Good morning all; happy Monday, and happy Camera Day! 😃
[09:32] <vmayoral|pc> ogra_: just to make sure, ppisati is the one that takes care of kernel aspects, right? I'd love to request access for the vivid BBB kernel sources for v4+ kernels
[09:39] <ogra_> vmayoral|pc, yes he is
[09:40] <vmayoral|pc> ogra_: thanks
[10:24] <longsleep> hey folks - if i want to implement a snappy framework for a secure web server/virtual host server/tls proxy - would that make sense?
[10:48] <ogra_> longsleep, as a snap, yes, i dont think that is what frameworks are for though
[10:56] <Chipaca> longsleep: why'd you figure it was a framework?
[11:38] <Chipaca> ogra_: the arale only looks at the first core for load? wut?
[11:39] <ogra_> Chipaca, nope ... it looks at *some* core for the load avg.
[11:39] <Chipaca> ogra_: ah! much better then
[11:39] <ogra_> i dont think it is the first one
[11:40] <ogra_> (assuming the first one would at least give constant values ... 90% of the time my top output shows fixed values)
[12:57] <balloons> elopio, here's the bug from friday about snappy update failing. It seems it's not an issue in newer versions, but is repeatable for me from the original edge image. https://bugs.launchpad.net/snappy/+bug/1469716
[13:03] <mvo> balloons: thanks, thats interessting - this looks a bit like it might be a server side issue (or network releated).
[13:22] <balloons> one other question / bug that has come up: https://bugs.launchpad.net/snappy/+bug/1466674. For the legacy packages with namespaces in the store, should they still be supported for installation? If the app developer doesn't updating the package name, but they are still in the store, it's confusing trying to install
[13:23] <ogra_> no, they shouldnt
[13:23] <ogra_> all my apps were kicked out and i had to re-upload them
[13:23] <balloons> so is this something for beuno then? Should all those legacy packages be unpublished from the store
[13:23] <ogra_> i'm not sure how that one could slip thrugh
[13:24] <ogra_> they are unpublished (not removed but hidden for users)
[13:24] <balloons> ahh. Yea, i point it out because the tutorial has you search for web servers, and this is one of the ones that pops up. So it's fairly visible. it's how I got the error
[13:24] <ogra_> yep
[13:24] <balloons> ogra_, right. That makes sense and is my expectation. Just unpublish and as dev to fix naming
[13:25] <ogra_> but yeah, thats a beuno thing
[13:25] <balloons> *ask
[13:25] <ogra_> (who is on vac. this week i think)
[13:25] <ogra_> seems that package somehow slipped through
[13:25] <balloons> I guess for this instance I can ask Victor directly to fix it :-)
[13:25] <ogra_> ;)
[14:07] <elopio> good morning
[14:15] <fgimenez> hi elopio
[14:16] <fgimenez> pitti, thank you so much for such a quick fix! =)
[14:17] <pitti> fgimenez: you're welcome :)
[14:22] <elopio> hello fgimenez. Want to hang out?
[14:23] <fgimenez> elopio, ok, omw
[15:37] <Chipaca> jdstrand: you around?
[15:48] <Chipaca> jdstrand: in case i forget, it's about nuking click-apparmor :)
[15:55] <tyhicks> jdstrand: he's not around this week
[15:56] <tyhicks> jdstrand: I may be able to help you out in his place (although I'm about to join a meeting)
[15:56] <tyhicks> bah
[15:56] <tyhicks> Chipaca: ^
[16:18] <elopio> mvo: this regressed: https://bugs.launchpad.net/snappy/+bug/1464502
[16:18] <elopio> I made a small patch, please take a look when you have some time.
[16:35] <balloons> is raspberry pi 2 unofficially supported?
[16:42] <svij> balloons: nope
[16:43] <balloons> I suppose my question is a bit backwards. I want to know if / when ras pi 2 will have official snappy support
[16:44] <svij> there was a discussion about rpi2 support on the ML
[16:44] <balloons> svij, ahh I see it, thank you. I'll read
[16:45] <svij> balloons: great, I just try to find the mail. :)
[16:45] <olli> while we are on the topic of rpi2, if I dd the prebuild image, do I still need to worry about the device* and pi* parts?
[16:45] <olli> guess is, I don't, just want to confirm
[16:46] <olli> https://developer.ubuntu.com/en/snappy/start/ - is a bit confusing
[16:46] <sergiusens> olli: you shouldn't, no; that's all bundled in the img
[16:47] <olli> thx sergiusens
[16:54]  * Chipaca sorta-EODs a little early today
[16:57] <olli> sergiusens, is it right that we don't supply updated snappy images for the rpi2 and I can't update from commandline either?
[17:01] <plars> sergiusens: any idea how https://code.launchpad.net/~zyga/snappy-hub/fix-1464275/+merge/261833 can be made to finally land?
[17:06] <sergiusens> plars: yes, it just needs to be done
[17:09] <plars> sergiusens: by who? any idea who can do it?
[17:09] <plars> or when we could expect it to land?
[17:09] <sergiusens> plars: either myself or mvo; I just forgot about it on Friday, so today seems reasonable
[17:10] <plars> sergiusens: awesome, thanks!
[17:39] <balloons> ping elopio
[17:39] <elopio> balloons: pong.
[17:39] <balloons> elopio, so I wanted to touch base with you on setting up the system for capturing test results. Have you started anything on it yet?
[17:40] <elopio> balloons: nothing yet.
[17:42] <ljose> Hi, is there a list of system libraries included in Snappy armhf?
[17:44] <tedg> ljose, Not really, generally the answer is "none" other than libc.
[17:44] <tedg> ljose, They should get bundled with the app snaps.
[17:47] <ljose> so no OpenSSL bzip2 or suck?
[17:47] <ljose> Do I really need to build this  libraries for my application?
[17:50] <balloons> elopio, ok good :-) I'll start working on it later today and share
[17:51] <elopio> balloons: thanks. Are we still talking about a wiki page with links to extra notes?
[17:51] <balloons> elopio, yes. I'll do that, and some variations with spreadsheets and forms
[17:52] <elopio> balloons: cool. We were also looking at ways to record input and output from the terminal. If we can find some time for that, maybe we can turn one of the recorders into a snap :)
[17:55] <tedg> ljose, We're working on ways to make it easier to include the version from the Ubuntu archive, so you wouldn't have to build them. But they would still be included in your application.
[18:00] <ljose> So meanwhile what are my options, build my own copy of OpenSSL bzip2 for my device?
[18:01] <tedg> ljose, I'd just grab the copies from the Ubuntu archive by hand, and copy them into my project.
[18:01] <tedg> ljose, dpkg --unpack foo.deb ./
[18:05] <ljose> tedg:  Where can I found the packages for armhf?, in vivid repositories there is just i386 amd64 http://packages.ubuntu.com/vivid/openssl
[18:07] <tedg> ljose, http://ports.ubuntu.com/dists/vivid/main/
[18:08] <balloons> elopio, you wanted manually executed 'automatic' test scripts or just to have a log of what you did?
[18:08] <tedg> ljose, http://ports.ubuntu.com/pool/main/o/openssl/
[18:08] <elopio> balloons: a log of the manual commands and replies.
[18:09] <elopio> not something we must have, I just thought it could be nice.
[22:36] <Saviq> ogra_, hey, I'm trying to put your new rpi2 images into my orange matchbox, but all I'm getting is garbage on boot, any ideas?
[22:37] <Saviq> tried both the stable and wily image, same happens :/
[23:16] <Chipaca> apptove ALL the branches \o/
[23:16] <Chipaca> Saviq: you're holding it wrong :-p
[23:17] <Saviq> Chipaca, that's my current thinking indeed
[23:21] <Saviq> ok that's dumb... the emonpi attachment makes it do that...
[23:22] <Saviq> that I didn't expect