[06:13] <dholbach> good morning
[06:14] <clobrano> good morning dholbach, good morning to all ;)
[06:15] <dholbach> hey clobrano
[06:47] <clobrano> :)
[07:05] <fgimenez> good morning
[07:24] <davidcalle> Morning o/
[07:44] <dholbach> mvo, hum... I get the following when I try to run the autopkgtest of snappy:
[07:44] <dholbach> Package gudev-1.0 was not found in the pkg-config search path.
[07:44] <dholbach> Perhaps you should add the directory containing `gudev-1.0.pc'
[07:44] <dholbach> maybe build-tools is still required?
[07:44] <dholbach> or does libgudev-1.0-dev need to be added to the test depends?
[07:44] <dholbach> fgimenez, ^
[07:45] <dholbach> I used the following to run the test:
[07:45] <dholbach> adt-run --setup-commands="apt-get update" --source ../snapcraft_0.2.dsc --- qemu ~/vm/adt-wily-amd64-cloud.img
[07:49] <fgimenez> dholbach, i'll try to reproduce, give me a second
[07:50] <dholbach> no worries, take your time
[08:06] <longsleep> Good morning snappy :)
[08:09] <Chipaca> longsleep: o/
[08:25] <Chipaca> mvo: o/
[08:28] <mvo> hey Chipaca
[08:28] <Chipaca> mvo: mo'in! What's the plan with trunk vs 15.04?
[08:29] <Chipaca> clobrano: would you mind signing the CLA, so I can review & land your branch?
[08:29] <mvo> Chipaca: I would say lets keep them in sync for now, until the next huge change (the os/kernel snap/squashfs work)
[08:30] <mvo> Chipaca: or how do you feel about it?
[08:30] <Chipaca> mvo: i ask because we have some branches aimed at one, and some aimed at the other :)
[08:32] <mvo> clobrano: here is the link (in case you do not have it yet) http://www.ubuntu.com/legal/contributors
[08:32] <mvo> Chipaca: yeah
[08:34]  * Chipaca just wants to land all the good stuff
[08:35] <mvo> Chipaca: ok, lets land it all in trunk
[08:36] <dholbach> lool, asac, mvo, ogra, davidcalle, can we move the community sync half an hour earlier today? UE Personal has an Allhands call at the same time
[08:36] <ogra_> fine with me
[08:36] <Chipaca> mvo: that means resubmitting your untar perms fix
[08:36] <Chipaca> mvo: so i agree ;)
[08:36] <Chipaca> (it's the smallest resubmission, compared to landing everything in 15.04, or >shudder< landing in both and two-way-merging
[08:36] <Chipaca> )
[08:38] <Chipaca> husk retargeted
[08:40] <mvo> Chipaca: thanks, retargeted
[08:42] <lool> dholbach: fine with me too
[08:49] <Chipaca> mvo: did you have a chance to look at fgimenez's comment & error & patch on https://code.launchpad.net/~mvo/snappy/lp1480248-test-reenable/+merge/269176 ?
[08:50] <JamesTait> Good morning all; happy Wednesday, and happy Restless Legs Awareness Day! ☺
[08:50] <Chipaca> JamesTait: are you ever not aware of restless legs? isn't that the whole problem?
[08:51] <fgimenez> Chipaca, mvo lot's of things have change since then, let me check again
[08:52] <JamesTait> Chipaca, for those who suffer from the condition, yes.  I think the point is for those who don't even know it exists, to know it exists.
[09:19] <dholbach> mvo, asac, davidcalle: fine to move community sync today half an hour earlier?
[09:23] <mvo> dholbach: fine with me
[09:30] <fgimenez> dholbach, i can confirm the problem but can't find a proper solution from the test side, it keeps trying to find the seemingly unexisting gudev-1.0 package, maybe mvo can help
[09:31] <dholbach> ok
[09:31] <davidcalle> dholbach, not sure I'll be able to make it, but that's fine :)
[09:32] <dholbach> ok davidcalle, no worries
[09:32] <dholbach> fgimenez, thanks a lot for checking
[09:34] <mvo> fgimenez: what command should I run to reproduce the issue?
[09:34] <dholbach> mvo,
[09:34] <dholbach> adt-run --setup-commands="apt-get update" --source ../snapcraft_0.2.dsc --- qemu ~/vm/adt-wily-amd64-cloud.img
[09:34] <mvo> ta
[10:48] <mvo> dholbach, fgimenez sorry that this took forever, but I know now why the godd example fails, it looks like "go get" already runs pkgconfig (for gudev)  which is a bit odd and breaks snapcraft that only installs it in the build stage
[10:48] <dholbach> don't worry - thanks a lot for looking into it
[10:50] <mvo> dholbach: I'm trying to fix it no
[10:50] <mvo> w
[10:50]  * dholbach hugs mvo
[10:53] <fgimenez> dholbach, ok thanks a lot :)
[10:55] <fgimenez> mvo,  ^^ :)
[10:59] <mvo> fgimenez, dholbach: do we have a bug for this autopkgtest failure already?
[11:00] <dholbach> no, I don't think
[11:04] <sergiusens> mvo, dholbach that is strange, stage-packages are downloaded and unpacked during 'pull'
[11:05] <mvo> sergiusens: yeah, I think I found the issue
[11:05] <sergiusens> mvo, ted has a branch to fix paths from pkg-config fwiw
[11:05] <sergiusens> but it is failing its tests :-)
[11:05] <mvo> sergiusens: give me 5min to verify, it seems like its downloading and building when it really should just download
[11:05] <mvo> sergiusens: I push a branch
[11:05] <sergiusens> mvo, okie dokie
[11:15] <sergiusens> mvo, btw, wrt pkg-config https://code.launchpad.net/~ted/snapcraft/pkg-config-sysroot/+merge/271751
[11:15] <mvo> sergiusens: yeah, this one is missing
[11:57] <sergiusens> dholbach, want to look at this one https://code.launchpad.net/~sergiusens/snapcraft/pull-python-projects/+merge/272057 ?
[12:04] <dholbach> sergiusens, I'm a but busy with something else right now
[12:04] <dholbach> asac, around?
[12:09] <Chipaca> sergiusens: what was it you wanted me to review?
[12:10] <Chipaca> elopio: fgimenez: could you guys not be shy with "needs fixing" in reviews? makes finding things needing reviews a lot easier
[12:11] <Chipaca> e.g. https://code.launchpad.net/~fgimenez/snappy/1504_validation/+merge/271777
[12:11] <Chipaca> that's a needs fixing, if i'm reading elopio's comments right
[12:11] <Chipaca> same as https://code.launchpad.net/~elopio/snappy/new_kernel_file_name/+merge/271901 wrt fgimenez's comment
[12:13] <sergiusens> Chipaca, https://code.launchpad.net/~sergiusens/snapcraft/pull-python-projects/+merge/272057
[12:13] <Chipaca> fgimenez: mvo: also what's up with https://code.launchpad.net/~mvo/snappy/lp1480248-test-reenable/+merge/269176
[12:14] <sergiusens> fgimenez, all plainbox changes are missing in snapcraft now :-P
[12:14] <Chipaca> it's nearly a month old, and i don't know
[12:16] <fgimenez> Chipaca: wrt https://code.launchpad.net/~elopio/snappy/new_kernel_file_name/+merge/271901 i'm asking for confirmation, not sure if my results are reproducible, anyway you are right, i'll try to be more explicit
[12:17] <clobrano> Chipaca, mvo: sorry I was out of office, I'll look at it as soon as possible
[12:17] <mvo> no worries :)
[12:19] <fgimenez> Chipaca, i'll take a look at test-reenable branch, iirc there's other disabled test that we should be able to reenable
[12:21] <fgimenez> sergiusens, "missing" sounds bad... :)
[12:22] <sergiusens> fgimenez, it seems to work now... not sure if it was a plainbox thing, as I got a huge message saying it was analyzing stuff and then exited
[12:23] <clobrano> mvo: what's "Project Contact" in CLA?
[12:23] <Chipaca> clobrano: Alexander Sack, afaik
[12:24] <clobrano> Chipaca: ok, thanks
[12:24] <Chipaca> asac: right?
[12:26] <dholbach> mvo, ogra, lool: I haven't heard back from asac about the call, but didn't have too much to bring up apart from a clinic date - I can talk now, but can't in 30m - what do we do?
[12:27] <lool> clinic?
[12:27] <lool> dholbach: I dont have much either
[12:27] <lool> dholbach: I wonder: should we pull in davidcalle in these calls in the future? he's been working on the public facing docs too IIUC
[12:27] <dholbach> lool, snappy clinic
[12:27] <lool> oh right
[12:27] <dholbach> lool, yes, he's invited
[12:27] <dholbach> but he couldn't attend today
[12:27] <lool> ah ok
[12:28] <lool> dholbach: well I dont mind if we skip today, albeit I have missed last week so perhaps you want to sync real quick
[12:28] <dholbach> sure
[12:28] <lool> dholbach: asac is often triple-booked, so I wouldn't worry about his avail as much
[12:28]  * lool joins HO
[12:28] <lool> let me grab a headset of some sort
[12:29] <ogra_> one sec, gimme 3min
[12:29] <mvo> dholbach: sure, joining now
[12:32] <mvo> dholbach: hm, ff crashed, one sec
[12:45] <clobrano> Chipaca: CLA signed, thank you ;)
[12:46] <sergiusens> dholbach, btw, is there a calendar entry for the snappy clinic?
[12:46] <sergiusens> or am I meddling :-)
[12:46] <sergiusens> ?
[12:47] <ogra_> sergiusens, there isnt
[12:47] <ogra_> (we were just searching)
[12:48] <dholbach> sergiusens, no - I have no idea -- we just thought about it and asked if we shouldn't do it on Friday or are you flying there?=
[12:48] <asac> dholbach: for me that comm call is at 3 :)
[12:49] <tedg> sergiusens: were you able to get the pkgconfig tests to fail locally?
[12:49] <dholbach> asac, I have a call at the same time
[12:50] <sergiusens> tedg, hah, dholbach has
[12:50] <sergiusens> tedg, well he added the exact cause to the MP
[12:50] <sergiusens> dholbach, I am out Friday
[12:50]  * tedg looks
[12:50] <dholbach> sergiusens, ok.....
[12:50] <tedg> Hmm, mail still syncing
[12:52] <sergiusens> tedg, that's not a problem with webmail
[12:52] <sergiusens> :
[12:52] <sergiusens> :-P
[12:54] <tedg> sergiusens: Yes, but *everything* else is :-)
[12:55] <sergiusens> fgimenez, should we make tarmac run the examples?
[12:58] <dholbach> sergiusens, lool suggested tomorrow 12:30 UTC - would that work for a clinic for you?
[12:58] <sergiusens> dholbach, perfect
[12:58] <lool> 13:30 UTC actually
[12:58] <lool> oh sorry
[12:58] <tedg> sergiusens: dholbach: I'm not seeing it... where was it?
[12:59]  * tedg can't beleive that LP didn't send him e-mail about something
[12:59] <dholbach> tedg, it's a new suggestion
[12:59] <lool> half an hour ago, tomorrow
[12:59] <sergiusens> tedg, look it up on the web, don't be lazy ;-)
[12:59] <lool> in 23h30
[12:59] <fgimenez> sergiusens not sure, i think that elopio and dholbach talked about that a few days ago
[13:00] <dholbach> tedg, it never was in the calendar :)
[13:01] <tedg> Ah, on the MR.
[13:03] <Chipaca> clobrano: did you get an email or something when signing the CLA?
[13:03] <Chipaca> clobrano: trying to figure out why the person that does the paperwork at our end hasn't received the email yet
[13:03] <clobrano> Chipaca: nope
[13:04] <clobrano> no emails
[13:04] <sergiusens> Chipaca, clobrano if it is showing up on launchpad I think it should be fine
[13:04] <Chipaca> sergiusens: it isn't
[13:04] <Chipaca> sergiusens: that step is manual, unless i'm very mistaken
[13:04] <Chipaca> that is: there is a person at canonical that receives a particular email, and adds people to a particular laucnhpad group
[13:05] <clobrano> maybe I'm missing the GPG key..
[13:05] <Chipaca> but maybe the email goes to asac?
[13:05] <sergiusens> yeah, that cn do it
[13:05] <clobrano> openPGP
[13:05] <sergiusens> gpg missing means there is nothing to sign with
[13:05] <sergiusens> fgimenez, super simple one https://code.launchpad.net/~sergiusens/snapcraft/no-test-print/+merge/272099
[13:16] <rickspencer3> hi all
[13:16] <rickspencer3> I'd like to upgrade my rpi2 to the latest and greatest with rolling
[13:16] <rickspencer3> can anyone easily give me the right commands to get and build the correct image?
[13:20] <ogra_> rickspencer3, wily you mean ?
[13:21] <fgimenez> sergiusens ok done, if needed the tests could use the logging module
[13:22] <rickspencer3> ogra_, I dunno, I'd like to get daily updates
[13:22] <rickspencer3> I assumed that I would get on "rolling" for that
[13:22] <ogra_> rickspencer3, well, we do daily builds in 15.04/edge and in rolling/endge
[13:23] <ogra_> the latter is wily based
[13:23] <rickspencer3> ogra_, I think rolling/edge
[13:23] <ogra_> ok ... not sure if it works, i doubt anyone ever tried booting that on a rpi ....
[13:24] <rickspencer3> ogra_, ok, nm
[13:24] <rickspencer3> I'll take 15.04/edge, then :)
[13:24] <ogra_> sudo ubuntu-device-flash core rolling --channel edge --developer-mode --oem pi2 --device-part  device-pi2-0.15.tar.xz -o pi2-rolling-edge.img
[13:24] <ogra_> that would be the line for rolling
[13:24] <ogra_> and indeed you need the device tarball
[13:24] <ogra_> from http://people.canonical.com/~platform/snappy/raspberrypi2/
[13:24] <rickspencer3> ogra_, right, but if it is not even tested to boot on the rpi2 yet, I think I would be better off with 15.04, I guess
[13:25] <ogra_> then you just replace the "rolling" in that line with 15.04
[13:25] <sergiusens> rickspencer3, we don't guarantee a boot on edge though
[13:26] <ogra_> i'm waiting for the kernel package to land in the archive (stuck in -proposed) and will then provide an upgraded device tarball
[13:26] <rickspencer3> ogra_, so I should wait until later today?
[13:26] <ogra_> right, what sergiusens said ... but i booted edge the last days
[13:26] <rickspencer3> I kind of sorta am desperate for pwm support
[13:27] <ogra_> rickspencer3, depends on how fast the archive admins and rtg are
[13:27] <ogra_> there is a packaging bug he needs to fix
[13:27] <rickspencer3> ok
[13:27] <tedg> sergiusens: Adding PKG_CONFIG_PATH, can't really remove GLib on my system to test it though. I still doesn't fail here :-)
[13:27] <ogra_> i wouldnt hold my breath for "landing today"
[13:27] <ogra_> but there is always hope indeed :)
[13:27] <sergiusens> Chipaca or mvo mind looking at https://code.launchpad.net/~sergiusens/snapcraft/printless/+merge/272101 ?
[13:27] <rickspencer3> ogra_, well, if I won't get pwm today, there is no point to upgrade, I'll stick with what I have for now
[13:28] <ogra_> by end of week i hope we'll have an auot-built rolling/edge image ... if that works i'll move that to 15.04 next week
[13:28] <ogra_> *auto-built
[13:28] <sergiusens> tedg, run in lxc/lxd or apt remove glib
[13:29] <sergiusens> tedg, no one builds with glib these days anyways ;-)
[13:29] <ogra_> inbetween i might do a release of 15.04 #5 for the RPi
[13:29] <tedg> Doesn't systemd use glib?
[13:30] <tedg> Oh, I guess this is only the dev package.
[13:30] <sergiusens> tedg, yeah :-)
[13:30] <sergiusens> tedg, or chose a different -dev pkg with pkg-config support :-)
[13:31] <ogra_> the binary only uses the "c" version of glib
[13:31] <ogra_> :P
[13:35] <tedg> It seemed like the others would all pull in glib.
[13:35] <tedg> Sure there's some
[13:42] <mvo> sergiusens: I got some extra homework, I'm not sure I can get to it
[13:43] <sergiusens> mvo, ok, I'll bug Chipaca or maybe tedg :-)
[13:46] <clobrano> Chipaca: the CLA seems signed now
[13:48] <rickspencer3> ogra_, I guess I should ask .. does the rpi2 current support spi?
[13:48]  * rickspencer3 asks after having fully wired it together with his MCP3008
[13:51] <ogra_> rickspencer3, find /sys -name '*spi*'
[13:51] <ogra_> ;)
[13:52]  * rickspencer3 hopes that is a "yes" :)
[13:52] <ogra_> i see devices when i do that but i have no idea if the default devicetree enables any of them
[13:52] <ogra_> you might need to apply an overlay for it
[13:56] <rickspencer3> arg
[13:56] <rickspencer3> ok, I'll have to wait a bit to try it out
[13:56] <rickspencer3> will see later
[13:57] <ogra_> (RaspberryPi2)ubuntu@localhost:~$ cat  /sys/firmware/devicetree/base/soc/spi@7e2004000/status
[13:57] <ogra_> disabled
[13:57] <ogra_> yeah, as expected
[14:23] <sergiusens> tedg, any luck with pkg-config?
[14:23] <tedg> sergiusens: Still building the lxc image
[14:33] <tedg> sergiusens: I'm now getting this, no clue what to do with it: http://paste.ubuntu.com/12531319/
[14:45] <sergiusens> tedg, oh nice,
[14:45] <sergiusens> tedg, merge trunk; the run test rework reverted a change to only mccabe check or project
[14:46] <sergiusens> should be fixed in trunk again; this most likely happened after pulling in external sources
[15:06] <tedg> sergiusens: Merged trunk, still got the same error
[15:19] <clobrano> QUESTION: what is snappy update --automatic-reboot? How it is triggered?
[15:26] <Chipaca> clobrano: what do you mean how is it triggered?
[15:27] <tedg> sergiusens: Thinking let's just let tarmac give it another try.
[15:27] <mvo> clobrano: we have a systemd unit that runs it every N hours
[15:27] <mvo> tedg: at what point in the build do you get that?
[15:27] <sergiusens> tedg, sure; did you fix anything already?
[15:28] <mvo> tedg: do you use LC_ALL=C in your environment? could you try LC_ALL=C.UTF-8 instead?
[15:28] <tedg> mvo: When doing "./runtests.sh"
[15:28] <tedg> sergiusens: Yeah, I added the environment variable and cleaned up the long lines.
[15:29] <clobrano> mvo, Chipaca: I was testing snappy, and I got a message like "another snappy is running". Does it really do an automatic reboot from time to time?
[15:29] <elopio> sergiusens: tedg: what I know is that I got the same error in testtools because my locale is EO https://github.com/testing-cabal/testtools/issues/76
[15:29] <tedg> mvo: Cool, that moved forward. New error :-)
[15:29] <Chipaca> clobrano: unless you've disabled that, yes
[15:29] <tedg> We need a release so that apt-get build-dep works again :-)
[15:30] <sergiusens> tedg, hah :-)
[15:30] <Chipaca> clobrano: if you're logged in when it happens, you'll get a message plus given a way to cancel the reboot
[15:31] <clobrano> oh ok, I didn't see that message, yet
[15:42] <elopio> ogra_: is it safe to assume that sectors will be 512 bytes?
[15:42] <ogra_> elopio, i think sergiusens hardcoded that recently, so yes
[15:42] <elopio> yay for sergiusens!
[15:44] <sergiusens> ogra_, that's such a stron word :-P
[15:44] <tedg> sergiusens: Okay, verified it works :-)
[15:44] <sergiusens> tedg, \o/
[15:45] <ogra_> elopio, i think sergiusens polished the code to support that recently, so yes
[15:45] <ogra_> sergiusens, sounds better ?
[15:45] <ogra_> :)
[15:46] <elopio> it's configurable, but only one option is supported at the moment :)
[15:46] <sergiusens> elopio, choose wisely!
[15:47] <sergiusens> tedg, your mixing of " and ' will disturb elopio :-P
[15:48] <elopio> tedg: oh yes. No beers for you on our next sprint!
[15:49] <ogra_> tedg, just switch to » and «
[15:50]  * tedg uses all the quotes
[15:51] <bjf> i'm trying to use the doc @ developer.ubuntu.com for the rpi2 regarding "building your own image". neither example actually works
[15:51] <tedg> sergiusens: I think that " is only used for shell strings...
[15:51] <bjf> 1. can we clean up the examples to ones that work and 2. is there other documentation that is more up-to-date?
[15:51] <sergiusens> tedg,         env.append("PKG_CONFIG_PATH=" + ':'.join([
[15:51] <sergiusens> tedg, in PKG_CONFIG_PATH ;-)
[15:52] <sergiusens> tedg, I can build godd again, so I don't care ... mvo and his project names ;-)
[15:53] <sergiusens> tedg, building a couple of c based projects to triple check
[15:54] <elopio> finally, the resize test passed again!
[15:54] <elopio> bjf: can you please report bugs for the issues you are getting?
[15:54] <bjf> elopio, against which package/project?
[15:54] <elopio> bjf: ogra_ here is working on rpi, so he can tell you more.
[15:55] <longsleep> bjf: Take a look at https://github.com/longsleep/snappy-odroidc - thats how i build my images if you want to look at working examples
[15:55] <tedg> Ah, found one. Fixed it.
[15:55] <elopio> bjf: https://bugs.launchpad.net/developer-ubuntu-com/
[15:55] <ogra_> bjf, hmm, what exactly isnt working ?
[15:56] <ogra_> (i know they did once mention versions, but we replaced that by * )
[15:56] <bjf> ogra_, https://pastebin.canonical.com/140433/
[15:58] <bjf> ogra_, there is a link there "from Paolo Pisati's binary build" that says it's to a device tarball but pulls down a .deb
[15:59] <ogra_> bjf, well, i'm in the process to make official images, that whole section will be obsolete in a week or so
[16:00] <ogra_> hmm, your paste looks like someone reverted my changes
[16:00] <elopio> sergiusens: I think that on your release notes you should mention more clearly that yamls with the previous format won't work, and need to be updated.
[16:01] <sergiusens> elopio, sure, feel free to write that down
[16:09] <ogra_> bjf, "On this page, you will find pre-built bits to bootstrap your Raspberry Pi 2 with a Snappy image." ... there is a link in that line
[16:09] <ogra_> i dont think it is wrong to mention that the device tarball includes palos kernel
[16:09] <bjf> ogra_, yup and that works. i get an image that i can dd and the rpi2 will boot
[16:09] <ogra_> (or to link to it)
[16:10] <ogra_> could surely be phrased better
[16:10] <ogra_> but as i said, will be obsolete very soon
[16:10] <ogra_> we'll soon have all bits properly on the server once the linux-raspi2 package migrates out of -proposed
[16:11] <bjf> ogra_, i am trying to build my own image and the instructions for doing so don't work. do you suggest i wait for a couple of weeks and try again?
[16:11] <elopio> Chipaca: the 15.04 we want to release is in edge now?
[16:11] <Chipaca> elopio: at this stage, i don't know
[16:11] <Chipaca> elopio: it's on trunk
[16:12] <Chipaca> elopio: is edge getting built from trunk?
[16:12] <Chipaca> elopio: I don't know
[16:12] <Chipaca> ogra_: do you?
[16:13] <elopio> should be, but that something fails. Chipaca, but lp:snappy/15.04 right, not lp:snappy ?
[16:13] <ogra_> bjf, didnt you just say it works ?
[16:13] <bjf> ogra_, i just read it all a couple more times, maybe i see my mistake
[16:13] <Chipaca> elopio: lp:snappy
[16:13] <Chipaca> elopio: which should be in sync with 15.04
[16:13] <Chipaca> let me just doublecheck that
[16:13] <ogra_> edge is getting built from the PPA
[16:14] <ogra_> wether your trunk change ends up in the PPA snappy package by default i dont know
[16:14] <Chipaca> ogra_: 15.04 edge
[16:14] <ogra_> yes
[16:14] <Chipaca> ok
[16:14] <elopio> Chipaca: right, I see the latest merge. But now I'm confused, why do we have the 15.04 branch?
[16:14] <Chipaca> elopio: because they're in sync only because disruptive changes haven't landed yet
[16:15] <Chipaca> elopio: and because mvo is in pre-sprint-rush so is less tidy than usual
[16:15] <elopio> right. Not complaining here :)
[16:15] <Chipaca> nor here
[16:15] <Chipaca> elopio: trunk has two revs that are not in 15.04
[16:15] <Chipaca> elopio: and we want them in the release
[16:15] <Chipaca> as they're both small but nasty bugs
[16:16]  * Chipaca hugs 'bzr missing'
[16:20] <elopio> if I understand correctly, the recipe for lp:snappy/15.04 puts the vivid version on the ppa, which is used to build 15.04 edge. The recipe for lp:snappy puts the wily version on the ppa, which is used to build rolling edge.
[16:21] <ogra_> elopio, right, someone needs to move the commits over
[16:21] <elopio> Chipaca: if so, we need your update-qualified-name backported to the lp:snappy/15.04, rerun the recipe, and ask somebody to trigger and edge build.
[16:21] <ogra_> and we need to decide if we should just drop lp:snappy/15.04
[16:21] <ogra_> and simply use lp:snappy for both
[16:21] <Chipaca> elopio: ahead of you :)
[16:21]  * ogra_ would actually prefer if we did all developmennt in 15.04 
[16:22] <ogra_> saves all the backporting :)
[16:22] <Chipaca> elopio: https://code.launchpad.net/~chipaca/snappy/trunk-to-15.04/+merge/272140
[16:23] <bjf> ogra_, i think i'm closer. i downloaded all the files "this page" pointed me at of pre-built bits. https://pastebin.canonical.com/140436/
[16:24] <ogra_> bjf, hmm, is your ubuntu-device-flash outdated ?
[16:24] <bjf> ogra_, ubuntu-device-flash          0.31-0ubuntu1
[16:25] <elopio> wow, launchpad is really crazy
[16:25] <bjf> ogra_, does it look in the current directory for what is specified by the --oem flag ?
[16:25] <ogra_> it shoudl
[16:26] <ogra_> bjf, the 0.15 pi2 sanp is in the store though, "--oem pi2" should work as well
[16:29] <elopio> Chipaca: take a look at the recent revisions in https://code.launchpad.net/~snappy-dev/snappy/snappy
[16:29] <elopio> what it shows as merged branches don't match with the rev.
[16:29] <elopio> somebody will have to calm William's wrath for breaking launchpad.
[16:32] <bjf> ogra_, similar error trying just "--oem pi2": pi2 failed to install: snappy package not found
[16:33] <ogra_> bjf, very weird
[16:34] <bjf> ogra_, indeed. feels like i have some basic misconfiguration which i don't understand
[16:34] <ogra_> well, the official image was created exactly the same way
[16:41] <ogra_> bjf, i'm super busy with some customer stuff, i'll take a look later and try to roll an image here
[16:41] <bjf> ogra_, ack
[16:41] <ogra_> (if you dont find a solution before)
[16:41] <ogra_> bjf, any reason why you dont use the pre-built image ?
[16:42] <bjf> ogra_, that does work... i'm trying to come up to speed so i can start testing rpi2 kernels
[16:42] <ogra_> bjf, ah
[16:45] <ogra_> well, you can just cp the binaries in place over the ones in /boot/uboot/b and /system-b/lib/modules as a quick fix ... then run: sudo fw_setenv snappy_ab b ... and reboot
[16:45] <ogra_> (that will boot into the b system, and should reboot back into a if something fails
[16:45] <ogra_> )
[17:39] <elopio> Chipaca: snappy 15.04 failed to build for arm64. We don't care about that one, right?
[17:39] <ogra_> nope
[17:39] <ogra_> definitely not on 15.04
[17:39] <elopio> ogra_: can you kick 15.04 edge to pull this version?
[17:39] <ogra_> not yet
[17:40] <ogra_> waiting for a few other changes before i can build an image
[17:40] <ogra_> but yeah, as soon as i can
[17:40] <elopio> ogra_: cool. Let me know.
[17:41] <elopio> sergiusens: what you want to release is snapcraft from trunk, or snapcraft from the tools-proposed ppa?
[17:42]  * Chipaca hugs elopio 
[17:43] <elopio> :D
[17:45] <ogra_> Chipaca, elopio, image build kicked off
[17:56] <elopio> dholbach: I think you send the wrong date on your clinic invitation.
[17:56] <elopio> dholbach: really cool idea btw, thanks.
[17:57] <dholbach> elopio, sent an update
[17:57] <dholbach> Jeff Lane noticed the same
[17:59] <dholbach> sorry, mail was in the moderation queue
[18:03] <sergiusens> elopio, snapcraft - 0.2-0~207~ubuntu.* which is building now
[18:24] <sergiusens> elopio, build is done; I'm doing a test build of all the example packages
[18:49] <rayn> hello there. Cant find a way to edit files, like in nano. Is there an editor?
[18:49] <plars> ogra_: does the boot process on rpi2 read snappy-system.txt at any point? I'm not seeing where it does, but if not, I'm confused how it knows whether to use snappy-a or snappy-b
[18:50] <ogra_> plars, out of uboot.env
[18:50] <ogra_> snappy-system.txt is obsolete
[18:50] <ogra_> rayn, there is vi
[18:50] <plars> ogra_: oh! that could mess me up I guess
[18:51] <plars> ogra_: so if I'm booting snappy from a usb stick, is it going to rewrite the one on the mmc or on the usb stick?
[18:51] <ogra_> plars, it is like that since the 15.04 #4 release ... i.e. like 8 weeks ago (or was it more) for all arm boards
[18:51] <plars> ogra_: It just recently started mattering for me, due to looking at how to automate rpi2
[18:51] <ogra_> it is going to rewrite the one in /boot/uboot/a|b
[18:52] <ogra_> the rewriting happens from a systemd job
[18:52] <plars> ogra_: ok, so it's going to rewrite the one on usb, which is safer, but I'm not going to be able to see those changes
[18:52] <rayn> ogra_ thanks
[18:52] <ogra_> fw_printenv will show them
[18:52] <ogra_> we ship it
[18:53] <ogra_> (and you can modify them with fw_setenv if needed)
[18:53] <plars> ogra_: I'm not sure how that will help me unfortunately :(
[18:53] <plars> but thanks
[18:53] <plars> this may just be a limitation on rpi for now
[18:54] <ogra_> it is like that on all arm installs now
[18:54] <elopio> sergiusens: I've verified all the points on your release notes. I'm happy with this release.
[18:54] <plars> ogra_: well, on bbb we have two places to boot from, so it's fine
[18:54] <elopio> and tomorrow we'll get many new eyes to catch interesting bugs for 0.3
[18:54] <plars> ogra_: but on rpi2 we have to fake it
[18:54] <sergiusens> elopio, yup; ok now I need confirmation from asac ;-)
[18:54] <sergiusens> well I guess he already knew :-P
[18:56] <elopio> sergiusens: we can blame him when things are on fire because he missed the stand up ;)
[19:06] <asac> sergiusens: whats the one line summary of what i knew? :)
[19:07] <sergiusens> asac, looking good (is that a valid summary?)
[19:27] <elopio> sergiusens: could you push a new version to the store for a package with no alias?
[19:45] <sergiusens> elopio, which package?
[19:45] <elopio> sergiusens: anyone from our examples.
[19:45] <elopio> but please tell me before you do it so I can check.
[19:46] <sergiusens> elopio, examples from snapcraft?
[19:46] <elopio> sergiusens: no, like hello-world and those. I'm not sure which have alias.
[19:46] <elopio> I just need one with no alias to show me an update.
[19:46] <sergiusens> elopio, oh, it is easy to check
[19:47] <sergiusens> elopio, but why not upload hello-world to your own account?
[19:47] <sergiusens> elopio, unless you are talking about an automated tests
[19:47] <elopio> sergiusens: no, I think that will work.
[19:47] <elopio> let me play with my own account.
[19:48] <sergiusens> elopio, it should :-)
[19:49] <elopio> Chipaca: I installed 15.04 alpha #179 and it seems to lad the ppp service properly. But after updating #178 to #179, it shows the same bug.
[19:49] <elopio> s/lad/load
[19:50] <Chipaca> grmbl
[20:01] <elopio> hum, what's the command to update one snap?
[20:02] <elopio> I think I've never tried that.
[20:03] <Chipaca> elopio: there isn't one
[20:03] <Chipaca> elopio: not from the commandline
[20:04] <sergiusens> elopio, I don't think you can
[20:04] <sergiusens> elopio, well, you can try and install it again
[20:04] <Chipaca> elopio: you can via the REST API though :)
[20:05] <elopio> yeah, the problem is that if I'm in #178 and do snappy update, it will go to #179 instead of updating the snap.
[20:05] <Chipaca> elopio: rest api rest api
[20:05] <elopio> so I can't confirm the problem. But I could update hello-world on #179. Is that good enough Chipaca?
[20:05] <Chipaca> no
[20:05] <Chipaca> because hello-world has an alias
[20:06] <Chipaca> :)
[20:06] <Chipaca> or :-(
[20:06] <elopio> Chipaca: not the one I'm using. hello-world.elopio.
[20:06] <Chipaca> ah, ok :)
[20:06] <Chipaca> then yes :)
[20:06] <Chipaca> elopio: "list -u" is also broken before
[20:07] <Chipaca> elopio: ie it doesn't show an update for a non-aliased package
[20:07] <Chipaca> elopio: and the broken part is the same between that and update
[20:07] <elopio> ok, let me try that.
[20:08] <Chipaca> elopio: otherwise echo '{"action":"update"}' | uPOST /1.0/packages/hello-world.elopio
[20:08] <Chipaca> for funky values of uPOST
[20:10] <elopio> #178 doesn't show the update. #180 shows it. All good.
[20:11] <elopio> so, the two bugs are fixed. But for the ppp one, it will remain failing if you are updating from our previous stable.
[20:13] <Chipaca> elopio: is that even if you haven't touched the config?
[20:14] <elopio> Chipaca: the only thing I did was systemctl status.
[20:26] <elopio> I restarted the service in #180 and now it seems fine.
[20:28] <jdstrand> whoever implemented 'snappy service', kudos!
[20:28] <jdstrand> asac: feel free to pass that along :) ^
[20:28] <jdstrand> it works great and is super helpful
[20:30] <sergiusens> Chipaca, ^
[20:31] <Chipaca> jdstrand: and it's not finished yet!
[20:31] <jdstrand> I can't wait to see the new stuff :)
[20:31] <Chipaca> jdstrand: it should give you service and security logs
[20:31] <jdstrand> oh, nice indeed
[20:31] <jdstrand> I think it has service logs already, no?
[20:32] <jdstrand> or is that different?
[20:32] <Chipaca> ah, yes, just not in 'status'
[20:32] <Chipaca> original request was to have all that in status output
[20:32] <jdstrand> I see
[20:32] <Chipaca> but i think it'd be messy unless you're asking about a particular service
[20:33] <Chipaca> anyway, thanks :)
[20:37] <jdstrand> Chipaca: re messy: fwiw, I like the separate logs command for that reason. status is different than logs imho
[20:39] <Chipaca> oh, it wouldn't replace the separate logs, just give you a snippet if you've got space
[20:39] <Chipaca> *handwaving intensifies*