[00:11] <bfiller> kenvandine: failed again on quiet_logging branch
[00:11] <kenvandine> damn
[00:12] <kenvandine> that's the one that has peer_picker_ui in it
[00:12] <kenvandine> wtf!
[00:12] <kenvandine> oh
[00:12] <kenvandine> peer_picker_ui is still in it
[00:12] <kenvandine> robru, can you remove that from the config?
[00:14] <cjwatson> cyphermox,thomi,robru: xnox's changes are in https://code.launchpad.net/~xnox/upstart-app-launch/sync-archive/+merge/209908
[00:14] <cjwatson> please just land that as well if you're landing another UAL change
[00:21] <robru> cjwatson, oh, I already pushed the changes direct to trunk. so that MP is stale / conflicting now. wasn't aware of the MP, sorry
[00:22] <cjwatson> It would have landed weeks ago if the landing process were remotely functional.
[00:23] <robru> i see
[00:24] <robru> kenvandine, sorry remove which from the config? I removed one already..
[00:24] <cyphermox> ugh
[00:24] <kenvandine> robru, which did you remove?
[00:24] <kenvandine> the only one that should get removed is the peer_picker_ui branch
[00:24] <kenvandine> which was in that second run
[00:24] <robru> kenvandine, the one that was conflicting from the previous build run... can't remember the name right now
[00:25] <robru> but not that one you just said
[00:25] <kenvandine> peer_details?
[00:25] <kenvandine> peer_picker_ui looked like the one that failed the first time
[00:25] <robru> kenvandine, fix_pending_check
[00:25] <kenvandine> that shouldn't have
[00:25] <kenvandine> it was a tiny change on top of more_handlers
[00:25] <kenvandine> it got much further than that
[00:25] <robru> kenvandine, not sure what you mean? "the first time" http://<IP_ADDRESS>/job/landing-014-1-build/36/console i saw fix_pending_check giving conflicts
[00:26] <kenvandine> oh.. i was looking at the criss cross stuff for peer_picker_ui
[00:26] <kenvandine> let me merge that into quiet_logging too
[00:26] <robru> kenvandine, ok, so i'm going to add fix_pending_check back, drop peer_picker_ui, then what?
[00:26] <kenvandine> robru, so drop peer_picker_ui and give me a minute
[00:27] <robru> kenvandine, wait, do I add fix_pending_check back or not?
[00:29] <kenvandine> no, it might blow up again
[00:29] <robru> ok
[00:29] <kenvandine> i merged it into quiet_logging
[00:29] <kenvandine> like bfiller said, we'll get a mamoth MP :/
[00:29] <kenvandine> but it works :)
[00:29] <kenvandine> ok, pushed
[00:31] <kenvandine> robru, remove peer_picker_ui though
[00:31] <kenvandine> if you didn't already
[00:31] <kenvandine> so drop fix_pending_check and peer_picker_ui
[00:31] <kenvandine> and i think it'll be clean
[00:31] <robru> kenvandine, ok, those are dropped, i'm kicking the build now
[00:34] <robru> kenvandine, bfiller : ok here is the latest attempt: http://<IP_ADDRESS>/job/landing-014-1-build/38/console
[00:38] <kenvandine> robru, thx
[00:38] <robru> kenvandine, you're welcome!
[00:38] <robru> kenvandine, are we rooming in Malta?
[00:38] <kenvandine> we can
[00:38] <kenvandine> :)
[00:38] <kenvandine> put it on the spreadsheet
[00:39] <robru> yeah, just got my approval today
[00:39] <kenvandine> cool
[00:39] <kenvandine> i'm booked already
[00:40] <robru> kenvandine, heh, neither of us are in the spreadsheet yet ;-)
[00:44] <kenvandine> ?
[00:44] <kenvandine> i was the other day
[00:44] <kenvandine> robru, oh... look at the second worksheet
[00:44] <kenvandine> there are 2 weeks
[00:44] <kenvandine> we are on the second
[00:44] <robru> ooooooooOOOOOOOOOOOOoooooooooooooh
[00:44] <bregma> hey guys, I got a weird build fail (looks like a write fail) on amd64 in my silo, other arches built OK ... is there a way to restart just that one build, to see if it was a transient error in the builder?
[00:45] <robru> that explains why there were no names I recognized on the whole thing ;-)
[00:45] <robru> bregma, should be in the PPA a 'retry build' button if you dig.
[00:45] <robru> bregma, which silo?
[00:45] <bregma> landing-006
[00:46] <cjwatson> robru: he won't have access unless he's in ci-train-ppa-service
[00:46] <robru> ok, i'm on it
[00:46] <cjwatson> I don't see the failure though
[00:46] <cjwatson> oh yes I do
[00:47] <bregma> https://launchpad.net/~ci-train-ppa-service/+archive/landing-006/+build/5832899 fyi
[00:47] <bregma> looks suspicious to me
[00:47] <cjwatson> I guess you mean
[00:47] <cjwatson> make[3]: *** [generated/glib-2.0/schemas/org.compiz.networkarearegion.gschema.xml] Error 9
[00:48] <cjwatson> it's pretty scary if our builders are throwing random write errors, but I guess in this case it's OK to give it another try
[00:48] <robru> bregma, ok, i restarted it, if you keep watching the jenkins log you should see the status revert from "failed" to "building" (eventually)
[00:49] <bregma> yeah, the usual, and hopefully not continue on to "failed to build"
[00:49] <robru> bregma, if jenkins says "failed to build", just immediately re-run build with WATCH_ONLY and then it'll see the newer status of that rebuild
[00:50] <bregma> well, I just watch the PPA itself, it tells me everything
[00:52] <kenvandine> bfiller, woot... it's building in the ppa now
[00:53] <kenvandine> robru, thx for the help
[00:53] <robru> kenvandine, you're welcome
[00:54] <kenvandine> i'm going to disconnect now, before i get tempted to work more :)
[00:54] <kenvandine> good night all!
[01:16] <robru> ok, i'm off for dinner, but i'll be back in an hour or so in case anybody needs anything
[01:40] <kgunn> cyphermox: you around ?
[01:41] <kgunn> robru: ...hey when you get back, can you reconfig silo 4 ...one...more...time....
[01:41] <kgunn> it doesn't like me doing reconfig with those "ubuntu-touch-session" MPs
[01:41] <kgunn> wondering what trick you are doing to reconfig without it griping
[01:46] <kgunn> robru: i gotta boot into my macos for a bit...i'll check back in about an hour or so
[01:48] <plars> robru: cyphermox: 249 finished, just those two calendar app errors on mako so I'm going to rerun those. hopefully they will not be reproducible
[01:50] <cyphermox> ok
[01:52] <cyphermox> robru: reconfiguring silo 4...
[01:54] <robru> cyphermox, thanks
[01:54] <robru> just got back
[01:54] <cyphermox> well, it's failing...
[01:54] <cyphermox> http://<IP_ADDRESS>/job/landing-004-0-reconfigure/14/console
[01:56] <robru> i... what
[01:57] <cyphermox> weird huh
[01:57] <robru> cyphermox, try again? maybe it's a connection issue
[01:57] <robru> i mean that's a standard MP. it's not like i did anything that would change that.
[01:58] <cyphermox> some issue with launchpad
[01:58] <robru> thomi, !!!! omg i'm so sorry that took all day. i just confirmed the trunk resync was successful and now published autopilot!
[01:59] <veebers> robru: that's awesome news! :-)
[01:59] <robru> veebers, will you be around in an hour? that's usually how long it takes for stuff to get through proposed, then I can merge & clean, then I can assign your next silo... but I might need to be reminded because i seem to be easily distracted and forgetful today
[02:00] <veebers> robru: yep, it's only 3pm for me :-)
[02:00] <robru> veebers, oh sweet, you australian or something? 7PM here, I'm EOD, but I've got things to do ;-)
[02:00] <veebers> robru: Close, New Zealand :-)
[02:00] <robru> nice
[02:01] <veebers> robru: I presume you'll be around on my Tuesday morning? (um, probably your Monday afternoon right?)
[02:01] <robru> veebers, i should be, yeah.
[02:01] <robru> i'm taking off early friday for a weekend trip but i should be back monday no problems
[02:02] <veebers> robru: coolio, if you're not around in an hour I might hold off and get a silo on my Tues, save holding a silo over the weekend (it's Friday arvo here)
[02:02] <thomi> robru: wooo! thanks man
[02:03] <robru> thomi, you're welcome!
[02:03] <robru> veebers, ok no worries
[02:04] <robru> cyphermox, hmmm what happened in silo 4?
[02:05] <cyphermox> the what?
[02:05] <cyphermox> it's the one that is broke for reconfig
[02:06] <robru> oh right. sorry I was just looking at the most recent *build* log error and got confused
[02:08] <cyphermox> yeah, it's still failing anyway
[02:08] <cyphermox> need to ask ops.
[03:13] <thomi> robru: I see the M&C job running - thanks :)
[03:13] <thomi> was just about to kick it off myself :)
[03:13] <robru> thomi, you're welcome! do you have some MPs to snag a new silo with?
[03:14] <thomi> veebers: ^ ?
[03:14] <thomi> I did this release, it's veebers turn to feel the pain for the next one :)
[03:14] <robru> haha
[03:15] <robru> veebers, I'd recommend jumping into a silo now, even if you don't test until next week -- i predict silos will be hard to come by next week...
[03:18] <thomi> robru: I guess he's AFK for a second
[03:19] <robru> no worries. lunch or dinner perhaps?
[03:20] <thomi> I predict: coffee break
[03:20] <thomi> it's 4:20 PM
[03:20] <veebers> robru: hey, sorry was running tests
[03:20] <veebers> thomi: :-)
[03:20] <thomi> bah.. was close...
[03:20] <robru> thomi, I've had lunch at 4PM some days ;-)
[03:20] <veebers> robru: one moment I'll update the spreadsheet
[03:20] <robru> veebers, great
[03:24] <veebers> robru: Thanks for the heads up. I've setup line 49.
[03:24] <robru> veebers, great, i'll assign it now
[03:25] <veebers> robru: Even if silos are hard to come by, it won't be hard to reconfigure right? i.e. I might need to add a MR for gallery-app
[03:25] <veebers> robru: awesome, thank you
[03:25] <robru> veebers, nope, reconfigs are trivial
[03:26] <veebers> robru: sweet
[03:26] <robru> veebers, ok, you got silo... wait for it... 3! ;-)
[03:26] <robru> veebers, are you able to kick the build yourself? or do you need me to?
[03:27] <veebers> robru: nice :-) thanks again
[03:27] <veebers> robru: I can kick the build
[03:27] <robru> veebers, you're welcome!
[03:29] <thomi> ahhh, it feels so good to pass the "release autopilot" baton to the next person
[05:04] <Mirv> morning
[05:16] <Mirv> I'll build the landing-015, since it seems like a good idea to have testable asap
[06:14] <robru> Mirv, good morning
[06:14] <robru> Mirv, don't panic, but I published autopilot today. I tested it for at least 5 hours. it looked really good
[06:24] <Mirv> robru: PANIC!!
[06:24] <Mirv> robru: ok, sounds good :)
[06:35] <tvoss> cyphermox, around?
[06:35] <tvoss> cyphermox, if so, can I get a silo for line 43?
[06:36] <Mirv> tvoss: I'm not good enough for you!? :)
[06:37] <Mirv> that said, we're full in silo usage (regarding the limits we've set to ourselves), let's see if something could be freed
[06:37] <tvoss> Mirv, oh, you are around :) sorry for that :)
[06:38] <tvoss> Mirv, I'm just looking for an available silo-dealer :) but my needs will not be fulfilled I guess
[06:41] <Mirv> tvoss: I try to get that one tested line published and I'll let you know when dbus-cpp could have a chance
[06:41] <tvoss> Mirv, yup, thank you
[06:52] <Mirv> mandel: hi, it was pointed out at #ubuntu-devel that the QML plugin dependency is too strict - or is it on purpose?
[06:53] <Mirv> mandel: I mean, are you planning to break ABI on purpose without bumping the library soname?
[08:04] <sil2100> Morning
[08:11] <sil2100> \
[08:12] <sil2100> I mean, hm, why did robru publish autopilot? Didn't he get the e-mail and didn't read the meeting summary?
[08:14] <Mirv> sil2100: he said not to panic in the morning, and that he had tested it for at least 5h before publishing and that it looked really good
[08:15] <Mirv> and... morning!
[08:16] <sil2100> Mirv: smoketesting looks ok, just it's really unwise to land risky things like autopilot while we're in the state 'do not publish anything besides fixes'
[08:16] <sil2100> Mirv: since even if you test everything, you never know if it won't introduce additional flakyness or the likes
[08:17] <sil2100> For me stopping the line means stopping the line ;)
[08:24] <Mirv> sil2100: yeah, it's not without risks I agree, not sure why he wanted it in (well, of course it's nice to always to get stuff in, just hard to be 100% sure nothing breaks)
[08:26] <sil2100> Mirv: this time it's a no-issue, but for the future I would really like to avoid that
[08:34] <asac> sil2100: autopilot landing worked well?
[08:35] <asac> hmm. dont see it in 250
[08:37] <Mirv> sil2100: I'm now running the UITK tests for double-testing to spot regressions. it's for the notes-app, I believe that's something that should go in since it's a 5.2 regression? (even though notes-app was workarounded)
[08:38] <Mirv> sil2100: meanwhile, I've the updated indicator-datetime installed too. not sure about that one, I didn't have much alarm success but it looks like the branches are supposed to fix real bugs
[08:38] <asac> Mirv: is it in the blocker list?
[08:38] <sil2100> Mirv: for now don't land anything that's not fixing the blockers, so even UITK I would not move
[08:39] <Mirv> asac: it was on the blocker list earlier, but then workarounded. so yeah it can be postponed.
[08:39] <Mirv> sil2100: true, that
[08:39] <asac> right
[08:39] <asac> cool
[08:39] <Mirv> sil2100: finally, thomas would like to have a silo for line 43, but we're out of silos
[08:39] <sil2100> asac: I don't see the changes file for 250 on ogra's machine, but from my calculations it should be in 250
[08:39] <asac> sil2100: do you know where we are on the blockers?
[08:40] <asac> sil2100: you are right. thta one is missing
[08:40] <Mirv> I think we're at the point that Savi_q is sleeping and he filed upstream bug report in the night
[08:40] <sil2100> asac: I just read all the e-mails and checked the bugs, and as Mirv mentioned there's an Qt upstream bug filled in and some insight on the LP bug as well
[08:40] <sil2100> We would have to wait for upstreams to wake up and comment how they want to proceed
[08:40] <Mirv> then the alarms problem alone seems complex, and that's why I'm asking about indicator-datetime - there's the general event issue, and then bugfixes that claim to now have branches
[08:41] <sil2100> But it seems that most issues are related ;/
[08:41] <asac> sil2100: we cant solve this on our own?
[08:41] <sil2100> asac: by upstreams I mean our upstreams
[08:41] <asac> ah
[08:41] <sil2100> Like, Saviq and kgunn ;)
[08:41] <Mirv> I built indicator-datetime in the morning with those branches, but since the event issue is also there I'm uncertain how to test the branches properly
[08:41] <asac> sil2100: ic... those guys are always laggers :P
[08:41] <asac> hehe
[08:42] <Mirv> sil2100: feel free to give the indicator-datetime a whirl
[08:42] <Saviq> excuse me!
[08:42] <sil2100> Mirv: let me try then, I'll just reflash my device to latest
[08:42] <sil2100> Saviq: :O ! Awake already?!
[08:42] <Saviq> sil2100, for an hour now :P
[08:43]  * sil2100 shocked
[08:43] <sil2100> ;)
[08:43] <asac> seems ogra's bot is more unreliable than our AP tests
[08:43] <asac> guess thats a good thing
[08:43] <asac> hehe
[08:43] <sil2100> heh ;p
[08:43] <asac> after all we get some maturity into this stuff
[08:43] <Mirv> FWIW I'm running full AP suite with both UITK and indicator-datetime updated, so if everything passes that's at least additional data point in addition to actual manual testing
[08:43] <asac> afaik the trainbot died two days ago already :)
[08:43] <sil2100> Saviq: anyway, do you have any ideas on how to proceed with this Qt-event-stopping bug?
[08:43] <asac> and that doesnt do mcuh :)
[08:44] <Mirv> sil2100: well there was the ugly hack to refresh Mir once a second...
[08:45] <sil2100> Mirv: sounds like a promotion candidate then! :D
[08:45] <sil2100> ;p
[08:45] <Mirv> haha
[08:45] <Mirv> seriously, I guess it depends how deep the change of behavior in Qt is, ie. is it really that the events handling can't be just forced somewhere where wanted
[08:46] <sil2100> ANyway, seriously, I don't know much about Qt5 insides, but it's strange that this happens for like music and such, but for instance phone calls on a screen turned off still works
[08:46] <Saviq> sil2100, yeah, am waiting for QML upstream to show up and comment
[08:46] <Mirv> Saviq: are you on #qt-labs?
[08:46] <Saviq> Mirv, yes
[08:46] <Saviq> Mirv, talked with thiago yesterday, and they did see this behaviour as weird
[08:46] <Saviq> but referred me to Alan
[08:47] <Mirv> Saviq: if you want to have additional data points, there is ppa:canonical-qt5-edgers/backup-qt511 and I could provide with an apt line to downgrade eg. a chroot:s environment to it
[08:47] <Mirv> ie Qt 5.1.1 built against trusty
[08:47] <Mirv> I had that done in December
[08:47] <sil2100> Nice :)
[08:47] <Saviq> Mirv, let me try, I'll be fine with the versions I think
[08:48] <sil2100> Convinient!
[08:48] <Mirv> ok
[08:48] <Mirv> sil2100: /me likes backups, you never know when they might be useful
[08:54] <Saviq> Mirv, hmm, libicu48 not there :/
[08:55] <Mirv> Saviq: let me try it and possibly give some ugly hacks
[08:56] <Saviq> Mirv, so I'm down to http://pastebin.ubuntu.com/7129585/
[08:57]  * Saviq tries to force this in
[08:57] <tvoss> Mirv, sil2100 a silo for line 51 would be highly appreciated :)
[08:57] <Mirv> Saviq: first one being wget 'https://launchpad.net/ubuntu/+source/icu/<IP_ADDRESS>-13+nmu1ubuntu1/+build/5185636/+files/libicu48_<IP_ADDRESS>-13%2Bnmu1ubuntu1_amd64.deb'
[08:57] <Saviq> Mirv, the latter pulls in -dev packages for some reason
[08:58] <Saviq> or maybe my apt-cache foo is wrong
[08:59] <Saviq> Mirv, I'm fine it seems
[09:00] <Saviq> Mirv, yup, same in 5.1.1
[09:00] <Mirv> Saviq: \o/ dist-upgrade in my chroot still running. I was thinking about apt pinning
[09:00] <Mirv> Saviq: aha, so it has changed already there...
[09:00]  * Saviq marks
[09:01] <Mirv> useful data to upstream too
[09:01] <seb128> Mirv, hey, thanks for the silos/starting the build/adding the commit messages
[09:02] <Mirv> seb128: you're welcome
[09:02] <seb128> Mirv, I'm doing testing now, giving the silos back then hopefully
[09:03] <Saviq>     Created:
[09:03] <Saviq>         Today 12:25 AM
[09:03] <Saviq>     Updated:
[09:03] <Saviq>         Today 10:02 AM
[09:03] <Saviq> no, that's not confusing _at all_
[09:04] <seb128> Saviq, you found a way to go back in time to update things before they get created? ;-)
[09:04] <Mirv> Saviq: there's only small part of the world you need to convince to leave 12h clock behind :)
[09:04] <sil2100> tvoss: bad news! We're in *that* mode again, which means we don't assign any silos for anything that's not a blocker fix
[09:04] <Saviq> seb128, Mirv, yeah
[09:05] <Mirv> I always need to read the Wikipedia article on the am/pm stuff
[09:05] <Mirv> especially the part of what 12:00am meant
[09:05] <Mirv> so simple http://en.wikipedia.org/wiki/12-hour_clock#Confusion_at_noon_and_midnight
[09:06] <Saviq> Mirv, what do you mean, it's obvious that after 12:59 it's 1:00, isn't it? ;)
[09:06] <sil2100> Sooo obvious
[09:07] <Mirv> Saviq: yes, it's obvious that after 12:00pm it's 12:01 am and then at some point 01:00, at least according to one interpration :)
[09:07] <bzoltan> Mirv: sil2100: May I ask for a silo to proceed with the line nro 13?
[09:07] <Mirv> bzoltan: TRAINCON-0 announced by asac on the mailing list
[09:08] <Mirv> assigning silos would be possible, though, but we're out of them as well
[09:08] <sil2100> bzoltan: sadly we are very low on silos right now...
[09:08] <Mirv> probably in 1-2h there'll be silos available
[09:09] <sil2100> uh, need to reflash my device again
[09:09] <bzoltan> Mirv: may I put some extra MRs on the silo16 then?
[09:10] <Mirv> bzoltan: hehe, actually yes you can, since that's not going in either since it's not anymore a blocker after notes-app was workarounded
[09:11] <bzoltan> Mirv: ohh... nice :) should we just add the line 13 to that silo and reconfigure?
[09:11] <Mirv> bzoltan: yeah I think so
[09:11] <sil2100> thostr_: ping
[09:11] <bzoltan> Mirv:  thanks mate :)
[09:11] <Mirv> and modify the description
[09:11] <thostr_> sil2100: pong
[09:11] <sil2100> thostr_: I see charles prepared a merge fixing the #1295237 blocker?
[09:11] <sil2100> https://code.launchpad.net/~charlesk/indicator-datetime/lp-1295237/+merge/212021
[09:12] <sil2100> thostr_: do we have a landing for that? Is this a final fix?
[09:12] <sil2100> Mirv: ^
[09:12] <Mirv> sil2100: yep
[09:12] <sil2100> Mirv: ah, I see now it's part of the datetime landing
[09:12] <Mirv> sil2100: that's what I asked you to give a whirl to
[09:13] <sil2100> thostr_: ok, so it's in a silo now but with some other fix, nvm then!
[09:13] <thostr_> charles told be that cyphermox was already silo'ing it
[09:13] <Mirv> sil2100: the other fix is the fix Charles pointed out in the bug report that is on the blocker list
[09:13] <Mirv> thostr_: sil2100: yep, cyphermox did the silo and I launched a build in the morning so it's ready to be tested from there
[09:14] <thostr_> in total charles has three patches:  https://code.launchpad.net/~charlesk/indicator-datetime/lp-1295271/+merge/212028, https://code.launchpad.net/~charlesk/indicator-datetime/lp-1295237/+merge/212021 and https://code.launchpad.net/~charlesk/indicator-datetime/lp-1293646/+merge/212056
[09:15] <seb128> the first 2 are in silo 15
[09:16] <seb128> sil2100, Mirv: is that fine if I add the third one and reconfigure/rebuild? or do you want to get the touch fixes through and do another landing for the desktop fix later?
[09:17] <sil2100> seb128: let's do another landing later, since this way we won't have to wait for a rebuild now and simply test and publish
[09:17] <sil2100> seb128: if that's fine with you
[09:17] <seb128> sil2100, ok, can you help testing it?
[09:17] <sil2100> seb128: yes, just finishing re-flashing ;)
[09:17] <seb128> sil2100, sure, if you don't tell me the other landing is going to be blocked because the lockdown :p
[09:19] <sil2100> seb128: pfff ;p
[09:19] <Saviq> sil2100, can you please kick rebuild in https://launchpad.net/~ci-train-ppa-service/+archive/landing-004/+build/5833499 ?
[09:19] <Saviq> or well, "try again"
[09:20] <sil2100> Saviq: sure
[09:31] <sil2100> ogra_: hello! Are you coming? :)
[09:34] <seb128> mhr3, do you watch your silos? you have one failing to build and one woth "code cleanup" waiting to be tested since yesterday morning at least
[09:35] <mandel> Mirv, I have read your comment in the MR and it makes sense
[09:36] <Mirv> mandel: did you read the last one too? :)
[09:37] <Mirv> mandel: so it seems it's not something required to be changed. now we just have the TRAINCON-0 so I'm afraid even with it ready for publishing we can't publish it
[09:37] <mandel> Mirv, just did.. ok, so it looks like is not a huge problem then
[09:37] <mandel> Mirv, indeed, I read asacs email and I know the current situation, we will have to wait
[09:38] <Mirv> mandel: let's keep in the silo and ready to be published at moment's notice.
[09:38] <mandel> Mirv, is not a blocker for me atm and I have talked with the browser people and they are not yet in the point where they are going to be using it, os we are ok
[09:39] <mandel> Mirv, keeping the silo is awesome :)
[09:42] <mhr3> seb128, i do
[09:42] <seb128> mhr3, so fix your build or give the silo back ;-)
[09:43] <mhr3> seb128, the testing failed and i already warned Wellark that the indicator stuff needs to move
[09:44] <Laney> the last promoted image still uses 5.0, right?
[09:44] <ogra_> Laney, yup
[09:44] <Laney> NEAT
[09:44] <ogra_> 237 iirc
[09:44] <Laney> this is handy for testing behaviour differences
[09:44] <Laney> we should keep one around
[09:45] <ogra_> we keep the promoted ones
[09:45] <seb128> Laney, what do you test? the tz stuff?
[09:45] <Laney> ya
[09:45] <seb128> cool, I assumed you would
[09:45] <Laney> pretty sure it worked before
[09:45] <Laney> but who knows
[09:45] <seb128> I'm 90% sure it did work correctly
[09:46] <seb128> I was wondering what changed
[09:46] <Laney> qt :P
[09:46] <seb128> but now that you mention it, it's probably qt5.2 :p
[09:46] <seb128> I though we used datetimed there
[09:46] <Laney> although the report doesn't say what version it was
[09:46] <Laney> yes, to change the tz
[09:46] <seb128> well, I get the issue on current trusty desktop
[09:46] <Laney> but then there's a call to tell qml that it has changed
[09:46] <Laney> Date.timeZoneUpdated()
[09:46] <seb128> k
[09:47] <seb128> it's a bit weird
[09:47] <seb128> like I'm utc+1
[09:47] <seb128> if I pick SF it gaves me california as utc+2
[09:47] <seb128> if I pick Paris back it gives me france as utc-8
[09:47] <seb128> e.g it's one step behind
[09:47] <seb128> maybe the order of signals changed or something
[09:50] <davmor2> Morning all
[09:50] <ogra_> signals done seem to be a strength of Qt 5.2 :P
[09:50] <ogra_> *don't
[09:53] <seb128> Laney, btw, you should be able to test click updates now :p
[09:54] <Laney> yeah it works for me on that image
[09:54] <Laney> that's both good and bad at the same time :P
[09:57] <sil2100> davmor2: so, ppa:ci-train-ppa-service/landing-015 if anything, and upgrade indicator-datetime from it :)
[09:57] <seb128> sil2100, indicator-datetime seems fine to me, but I'm unsure how to trigger the original bug so I can't really confirm that's fixed
[09:58] <sil2100> seb128: I'm trying to do it right now, but I asked davmor2 (who reported it) to give it a spin as well
[09:58] <seb128> good
[09:58] <sil2100> As he knows the best how to trigger it
[09:58] <sil2100> seb128: thanks for testing!
[09:58] <seb128> yw!
[10:00] <davmor2> sil2100, seb128: right my phone is now flashed so let me make sure I can replicate on the new image and then I'll look at installing the ppa and seeing if the fix solves the issue
[10:00] <sil2100> davmor2: thanks!
[10:13] <davmor2> right reproduced now to install the ppa
[10:22] <Mirv> FYI I've not seen regressions from indicator-datetime in full AP suite so far, 3/4 done or so
[10:22] <Mirv> one calendar app AP fail but that has happened before too
[10:24] <sil2100> Mirv: general dogfooding also didn't reveal any problems here, although I'm having a hard time doing the testing as mentioned on the bug ;)
[10:24] <sil2100> Mirv: I guess davmor2 will give us a definite +1 on if the issue is fixed
[10:27] <Mirv> ToyKeeper: nice round of bugs you have. I mean, those seem like more cornercase problems but definitely something that people will eventually hit if not kept on radar.
[10:30] <Mirv> being a beta tester of jolla these kind of problems seem quite familiar. now they're non-beta, but still some similar bugs there, which is not surprising given the complexity of a phone.
[10:35] <davmor2> sil2100, seb128: Okay so I seem to be able to dismiss alarms now \o/ :)
[10:36] <seb128> davmor2, great!
[10:39] <sil2100> davmor2: yessss!
[10:39] <sil2100> davmor2: actually, on my device every alarm attempt I made was dismissable
[10:39] <sil2100> Mirv: you want to do the honor of publishing inidicator-datetime? ;)
[10:40] <Mirv> sil2100: so testing has concluded? mine _just_ finished as well, no regressions.
[10:40] <Laney> yeah I got a simple reproducer
[10:41] <Laney> dateTimeUpdated() seems buggy
[10:41] <Laney> I mean timeZoneUpdated
[10:41]  * Mirv hears if what Laney is saying is somehow related to indicator-datetime landing
[10:42] <Laney> it's a qt problem
[10:43] <sil2100> Mirv: it's a different issue, related to TZ's
[10:44] <Mirv> sil2100: ok. so changing Tested to be yes as per davmor2 and publishing then.
[10:44] <sil2100> Mirv: you can publish indicator-datetime as it is now anyway I guess
[10:44] <sil2100> \o/
[10:45] <Mirv> indicator-datetime published
[10:46] <seb128> sil2100, Mirv, davmor2: thanks
[10:47] <popey> davmor2: adb shell ls /opt/click.ubuntu.com/com.ubuntu.calculator - what do you see?
[10:47] <Laney> http://paste.ubuntu.com/7129959/
[10:48] <davmor2> popey: root@ubuntu-phablet:/# davmor2@stryder:~$ adb shell ls /opt/click.ubuntu.com/com.ubuntu.calculator
[10:48] <davmor2> ls: cannot access /opt/click.ubuntu.com/com.ubuntu.calculator: No such file or directory
[10:48] <popey> wat
[10:50] <ogra_> Saviq, hmm, i just worke up my mako and the shell is dead .... indicators work, switching apps work, the launcher shows if i swipe from the left, but the shell itself is stuck on the application lens and i cant move it
[10:50] <Saviq> ogra_, right, I think I encountered that once or twice, it felt like mouse input isn't delivered
[10:50] <ogra_> (lockscreen works too)
[10:50] <davmor2> popey: root@ubuntu-phablet:/opt/click.ubuntu.com# ls -al
[10:50] <davmor2> total 8
[10:50] <davmor2> drwxr-xr-x 2 clickpkg clickpkg 4096 Mar 21 03:17 .
[10:50] <davmor2> drwxr-xr-x 3 root     root     4096 Mar 21 09:26 ..
[10:51] <Saviq> ogra_, edges are different 'cause they deal with touch events
[10:51] <popey> davmor2: is this a clean device you have just flashed?
[10:51] <Saviq> ogra_, but everything else deals in mouse events and it looks like that gets b0rked
[10:51] <davmor2> popey: yeap and then added a ppa and opened calculator
[10:51] <ogra_> hmm, k
[10:51] <Saviq> ogra_, I didn't find a way to repro, though :/
[10:51] <Saviq> ogra_, but please file a bug
[10:52] <ogra_> Saviq, anything you want me to capture specifically ?
[10:53] <Saviq> ogra_, steps to repro...
[10:53] <ogra_> lol
[10:54] <ogra_> i dont reallly have any ... i had a paused music app up and the device was suspended over night
[10:54] <ogra_> waking it up got me this
[10:54] <ogra_> ugh
[10:54] <ogra_> i just tried to use the hud to close the music app ... now i cant swipe it away anymore
[10:55] <ogra_> swiping down brings up the indicators behind the opened hud
[10:55] <ogra_> this device is seriously confused
[10:57] <davmor2> ogra_: do you see the little down arrow on the hud transparency at the top?
[10:58] <ogra_> no
[10:58] <ogra_> err
[10:58] <ogra_> yes, see ... use, no
[10:59] <davmor2> ogra_: :(
[10:59] <ogra_> tapping there expands the indicator pane a few mm
[10:59] <davmor2> don't find bugs we want to promote and image :P
[10:59] <ogra_> i can use the left swipe to get back to the shell
[11:00] <ogra_> davmor2, how do you expect us to promote an image with the signal processing bug
[11:00] <davmor2> ogra_: it won't help if you find more in the meantime though ;)
[11:00] <ogra_> heh, indeed
[11:00] <ogra_> filing anyway ...
[11:04]  * davmor2 sends a message to LP to block the Report bug button if login == "ogra"
[11:10] <ogra_> Saviq, bug 1295623
[11:10]  * ogra_ reboots the device
[11:12] <Saviq> ogra_, thanks
[11:12] <ogra_> not really helpful i think ...
[11:12] <ogra_> but at least it is logged
[11:17] <ogra_> hmpf ... my flo doesnt offer me to upgrade
[11:18] <ogra_> i'm on 248, i'm online but neither the notification in system-settings comes up nor do i see any update when i tap on the update icon in sysstem-settings
[11:19]  * ogra_ reboots the device
[11:20] <ogra_> aha, works after reboot
[11:21] <seb128> still seems a bug in the service
[11:21] <ogra_> nah, must be system-settings :P
[11:21] <seb128> ogra_, not a bug, you locked down our archive, we are locking down your upgrades
[11:21] <seb128> :p
[11:21] <ogra_> lol
[11:22] <ogra_> i didnt lock down anything ... complain to the sack ;)
[11:22] <sil2100> ;)
[11:22] <ogra_> (/me just notices that that sounds like "talk to the hand")
[11:23] <seb128> talking to the sack is like talking to wall ;-)
[11:23] <seb128> *to a wall
[11:23] <ogra_> nah, depends what you say really :)
[11:23] <seb128> if you say something he doesn't want to hear I should have added
[11:23]  * ogra_ knows that "want a whisky ?" always gets him a response
[11:23] <seb128> lol
[11:43] <asac> whats the word on the train block?
[11:44] <thostr_> sil2100: can I get a silo for line 10?
[11:45] <sil2100> asac: we're still blocked on the event thing, it's still being discussed
[11:45] <asac> Saviq: do we have any leads on our side?
[11:45] <sil2100> thostr_: we're in TRAINCON-0 and low on silos right now
[11:46] <asac> e.g. still straws?
[11:46] <sil2100> asac: he's on lunch right now
[11:46] <sil2100> asac: but I saw a lot of discussion on -unity
[11:46] <thostr_> sil2100: ok
[11:46] <sil2100> greyback: maybe you have any leads?
[11:48] <greyback> sil2100: not really, Saviq is looking after it
[11:57] <Mirv> in case bzoltan asks, landing-016 was reconfigured as discussed to include "all" the UITK branches hoped to be landed at some point when traincon is over
[12:04] <ogra_> asac, seems the issue is there sice Qt 5.1 .... Saviq filed an upstream bug
[12:05] <Saviq> yup /me bisects
[12:05] <asac> yeah
[12:06] <asac> i am sure we are on our own
[12:06] <asac> to get this fixed
[12:06] <asac> or hacked
[12:06] <asac> until upstream has time to look at it
[12:07]  * ogra_ thinks we should reconsider the block, looks like fixing might take longer and we are finally constantly green atm
[12:07] <seb128> yeah
[12:07] <seb128> locking down everyone also doesn't help to fix that qt bug
[12:08] <seb128> it's like a few people working on it/knowing the topic enough, it's not going to be fixed earlier by preventing others to do their work
[12:10] <asac> Saviq: so once you have the commit, feel free to pull bzoltan and his team in
[12:11] <Saviq> seb128, ogra_ +1
[12:11] <seb128> asac, what about listening to the teams rather than being stubborn? or at least explain why the lockdown is helping
[12:21] <sil2100> Ok, I jump out for quick lunch now
[12:23] <Saviq> Mirv, can you please kick the dependency-wait armhf builds in https://launchpad.net/~ci-train-ppa-service/+archive/landing-004/+packages
[12:24] <Saviq> Mirv, i.e. unity-mir and platform-api
[12:25] <Mirv> Saviq: I don't see missing armhf builds for them. other archs?
[12:25] <Saviq> Mirv, sorry, my eyes are broken
[12:25] <Saviq> Mirv, ignore please :)
[12:25] <Mirv> Saviq: ignoring:)
[12:27] <cjwatson> Saviq: you might just not have reloaded recently - dep-waits are auto-retried if possible at 25,55 * * * *
[12:27] <cjwatson> and those successful armhf builds are recent
[12:27] <Saviq> cjwatson, yeah, I must've
[12:36] <davmor2> ogra_: don't change imgbots name :)  [12:37] <popey> get a better irc client ☻
[12:37] <ogra_> davmor2, robru asked me to put "trainguard" into the string it posts ... just highlight onn that
[12:38] <davmor2> popey: I can get a plugin for it but I don't trust unofficial 3rd party plugins
[12:38] <davmor2> ogra_: that's the other alternative I guess :)
[12:41] <davmor2> ogra_: just reading your email to the phone list.  I don't think we should keep mir running that's just daft.  but might be a force on us if QT are not going to change the upstream do we know if things will actually be changed though?
[12:44] <ogra_> davmor2, it affects X11 too and i dont think it is wanted to stop processing in Qt, so i am confident upstream will fix it (or accept a patch from us once we have one)
[12:44] <ogra_> davmor2, though Saviq is the better person to judge this
[12:45] <Saviq> ogra_, I'm slightly worried "this is a feature, not a bug"
[12:45] <ogra_> i just personally think we should see that we release one of the green images tonight ... that gives the SDK team still the rest of the day and a chance to fix it but wont block the world ... we are (as i said) in a special situationn with the beta freeze and all
[12:45] <Saviq> ogra_, should know a bit more once I pinpoint a commit
[12:46] <ogra_> anyway, not up to me, just stating an opinion here ... the final decision is in rickspencesrs and asac's hands
[12:47] <davmor2> Saviq: thanks for the update
[12:53] <mhr3> sil2100, giving up 002
[12:58] <davmor2> popey: I just got the warning on facebook login I just hit continue and it all worked for me
[12:58] <davmor2> popey: and an email from facebook to
[12:59] <davmor2> +o
[12:59] <popey> ☹
[13:12] <kenvandine> bfiller, what do we do about clicks that are part of a silo?  like gallery in silo 14?
[13:13] <bfiller> kenvandine: we have to build it manually I guess
[13:13] <bfiller> kenvandine: was about to do that to test
[13:21] <cyphermox> seb128: thostr_: I was told by charles that he wasn't sure about the third, so he said not to add it, that's why there were only two
[13:22] <thostr_> cyphermox: ok with me. the first two seem more critical anyway
[13:22] <davmor2> popey: let me open up friends and make sure it actually works though
[13:23] <davmor2> popey: yeap Friends shows facebook posts
[13:25] <sil2100> mhr3: ok
[13:25] <sil2100> Saviq: hi! Any progress?
[13:25] <ogra_> don't be pushy !
[13:25] <Saviq> sil2100, it's BUILDING! ;)
[13:25] <ogra_> :)
[13:26] <sil2100> :O
[13:26] <Saviq> unfortunately qt's pretty heavy to build ;)
[13:26] <Saviq> especially when you're trying to bisect...
[13:26] <sil2100> Saviq: you think we'll have to distro-patch Qt to get it fixed, or maybe we can workaround it in our projects instead?
[13:27] <ogra_> in all of them ?
[13:27] <Saviq> sil2100, Qt
[13:27] <sil2100> ogra_: yes, in every one in the archive ;)
[13:27] <ogra_> we shouldnt have to distro-patch though ... upstream should ifx it :P
[13:28] <sil2100> ogra_: we're being priority-pushed here, Qt upstream doesn't understand the PRESSURE I have on me and the PRESSURE I put on Saviq right now to get this fixed ;p
[13:29] <Saviq> sil2100, ogra_'s trying to lift the pressure on ubuntu-devel for you ;)
[13:29] <ogra_> i think it doesnt need you to make Saviq feel the pressure :)
[13:29] <ogra_> (or me, or anyone)
[13:29] <sil2100> Phew
[13:30] <Saviq> it doesn't help that 5.0 doesn't build on trusty...
[13:30]  * Saviq changes approach
[13:33] <davmor2> it's almost like everyone is under the microscope + magnifying glass at the same time I don't think we need to announce the pressure on top of that :)
[13:35] <davmor2> popey, ogra_, sil2100: would you agree with me that other than the issues when the screen is blanked 250 is pretty solid?  Also I think i would hold off on looking at promotion till the image with the dismiss alarms fix is up :)
[13:39] <popey> 250 is solid
[13:40] <ogra_> yeah
[13:40] <sil2100> davmor2: I just played around with the phone and noticed no issues as well
[13:42] <davmor2> I'm just testing location which is the final test
[13:49] <kenvandine> bfiller, i just updated my gallery-app branch since trunk had a landing yesterday
[13:49] <kenvandine> bfiller, so if you didn't merge from trunk before building a click, you might want to pull again
[13:49] <bfiller> kenvandine: ack
[13:50] <bfiller> kenvandine: have you tested the other parts yet (like uss and address book?)
[13:50] <bfiller> with the silo
[13:50] <bfiller> ok
[13:50] <bfiller> oh
[13:50] <bfiller> needs gallery in all these cases, doh
[13:50] <kenvandine> bfiller, not yet... right
[13:50] <kenvandine> i've installed them all :)
[13:50] <kenvandine> just building gallery
[13:51] <kenvandine> i wish the silo could give us a click build :/
[13:51] <bfiller> kenvandine: I know, sergio build me a click version of gallery from trunk yesterday. I'm actually testing that the AP tests still work as a click
[13:52] <bregma> sil2100, I have a desktop-only (unity7+compiz) landing in silo 006 ready for publish, if and when it is safe and convenient to do so
[13:52] <sil2100> bregma: sure! Let me take a look
[13:53] <sil2100> bregma: I believe these are only bugfixes, yes? ;)
[13:53] <bregma> sil2100, yes
[13:54] <kenvandine> bfiller, my build it at 65%, if you want i can send you the click when it's ready
[13:54] <kenvandine> takes quite a while on the device
[13:55] <bfiller> kenvandine: that would be good
[14:05] <kenvandine> bfiller, http://ubuntuone.com/2ynawe58vvRLCkon6RFBU3
[14:05] <bfiller> kenvandine: thanks
[14:10] <kenvandine> bfiller, oh bugger...
[14:10] <kenvandine> the version is the same as the preinstalled click
[14:12] <kenvandine> bfiller, building another... with a different rev
[14:13] <kenvandine> bfiller, http://ubuntuone.com/78m3eVPfkLq9AR47CQCIrN
[14:14] <sil2100> ogra_: you have a moment for a packaging ACK?
[14:17] <sil2100> ogra_: http://<IP_ADDRESS>/job/landing-006-2-publish/48/artifact/packaging_changes_compiz_1%3A0.9.11+14.04.20140320.1-0ubuntu1.diff
[14:17] <sil2100> ogra_: the migration file looks sane, the dconf meddling is also done in other migration files already
[14:22] <ogra_> sil2100, hmm that last bit looks weird, is the "s0_active_plugins =" removal actually including the following line ?
[14:23] <ogra_> (apart from that ... ACK)
[14:24] <sil2100> ogra_: the final line just modifies s0_active_plugins = to not include gnomecompat in it
[14:25] <ogra_> sil2100, right, but the removal looks like it doesnt remove the list of plugins, only the variable
[14:25] <ogra_> might be a wrapping issue with the debdiff
[14:25] <ogra_> i would like you to make sure it actually also removes everything after =
[14:26] <ogra_> if thats clear, go wild :)
[14:27] <sil2100> ogra_: hah, it's cool - as you might see there is no 'whitespace' at the beginning of the second line, so it means it's part of the '-'
[14:27] <ogra_> great
[14:27] <sil2100> ogra_: if it was a separate line that is left unmodified there would be a " " at the beginning ;)
[14:27] <ogra_> so yes, go ahead
[14:27] <sil2100> ogra_: thanks!
[14:30] <bfiller> kenvandine: I'm reflashing then will test, any luck so far?
[14:31] <asac> davmor2: did you fully test the latest image?
[14:32] <sil2100> asac: yes, from what we know the whole dogfooding process has been finished successfully
[14:32] <sil2100> asac: as per https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Ai33BkOcORLLdE4xLTFtSE80ZkpITXZ3aV85cWtPX2c&usp=drive_web#gid=0
[14:42] <kenvandine> bfiller, all our pre-defined test cases work
[14:42] <kenvandine> but i did find a bug in the loader elleo added to ContentPeerModel
[14:43] <kenvandine> not a regression and doesn't break our default apps
[14:43] <kenvandine> doesn't need to block, but it's probably an easy fix
[14:43] <bfiller> kenvandine: let him know and hopefully he can fix it today
[14:43] <bfiller> kenvandine: the train is blocked anyway from releasing
[14:43] <bfiller> so we have some time (:
[14:44] <kenvandine> yeah
[14:44] <kenvandine> i just pinged him about it
[14:52] <davmor2> asac: popey and I have done the daily smoke that we normally do.  Everything is looking like the normal bugs are in place the only others are the Alarm and 2nd music track.  I can do a full image test but it will take maybe 3-4 hours
[14:53] <bfiller> kenvandine: installed everyting, gallery doesn't launch from system-settings for me when trying to choose background photo
[14:53] <kenvandine> bfiller, does gallery launch at all?
[14:54] <kenvandine> and confirm you installed <IP_ADDRESS>7.3
[14:54] <davmor2> asac: hence asking if you wanted me to do it on #ubuntu-touch
[14:54] <davmor2> asac: it'll give you a full break down like on image 237
[14:55] <bfiller> kenvandine: gallery launches on it's own, but not from uss or address-book. I have <IP_ADDRESS>7.3 installed
[14:55] <kenvandine> bfiller, also ensure content-hub-service has restarted
[14:55] <kenvandine> or even reboot it to be sure it's all clean
[14:58] <bfiller> kenvandine: I rebooted, hub service is not running after reboot or after requesting gallery from uss
[14:58] <bfiller> maybe I missed something
[14:59] <kenvandine> apt-cache policy content-hub
[15:02] <asac> davmor2: i think we want a firm +1 on this image
[15:02] <bfiller> kenvandine: 0.0+14.04.20140321-0ubuntu1, segfaults if I run /usr/bin/content-hub manually. let me get a trace
[15:02] <asac> davmor2: from you
[15:02] <bfiller> i'm on the latest
[15:02] <asac> in case we agree to whitelist this bug for this promotionm
[15:02] <asac> discussion is ongoing as always :)
[15:02] <kenvandine> bfiller,  i wonder if you have gsettings cruft
[15:02] <bfiller> kenvandine: image 250
[15:02] <bfiller> kenvandine: possible, I didn't wipe
[15:02] <davmor2> asac: right I'll start a full image test I'll throw a link at the mailing list in a bit
[15:03] <kenvandine>  gsettings get com.ubuntu.content.hub.default pictures
[15:03] <kenvandine> bfiller, ^^
[15:03] <kenvandine> bfiller,  and gsettings get com.ubuntu.content.hub.source pictures
[15:03] <bfiller> kenvandine: ['com.ubuntu.gallery_gallery_<IP_ADDRESS>1']
[15:04] <bfiller> kenvandine: which is wrong, that's the prior version I had installed
[15:04] <kenvandine> which is that from?
[15:04] <bfiller> kenvandine: that's the one sergio built me from trunk yesterday that I had installed
[15:04] <kenvandine> i meant which setting?
[15:05] <kenvandine> gsettings get com.ubuntu.content.hub.default pictures
[15:05] <kenvandine> ['com.ubuntu.gallery', 'gallery', 'current-user-version']
[15:05] <kenvandine> that's what you should get from default
[15:05] <bfiller> kenvandine: oh  gsettings get com.ubuntu.content.hub.default pictures = ['com.ubuntu.gallery_gallery_<IP_ADDRESS>1']
[15:05]  * davmor2 reflash 237 for an upgrade path
[15:05] <kenvandine> bugger... why didn't that default get reset
[15:06] <kenvandine> bfiller, had you maybe manually set the default before?
[15:06] <bfiller> kenvandine: no I didn't
[15:06] <bfiller> kenvandine: let me reflash with a wipe and try it again
[15:06] <bfiller> kenvandine: it's working ok for you?
[15:06] <kenvandine> gsettings reset com.ubuntu.content.hub.source pictures
[15:06] <kenvandine> do that
[15:06] <bfiller> ok
[15:06] <kenvandine> but we need to make sure this transition works
[15:06] <kenvandine> it worked for me...
[15:07] <kenvandine> but that isn't enough :)
[15:07] <kenvandine> bfiller, so that should have already been broken for you, because we changed that default to a tuple a couple weeks ago
[15:07] <kenvandine> that landed
[15:07] <kenvandine> bfiller,  so this issue isn't really related to this silo...
[15:08] <bfiller> kenvandine: maybe when I installed sergio's click yesterday it didn't do the right thing with gsettings?
[15:08] <kenvandine> the click shouldn't change defaults
[15:08] <kenvandine> they register themselves, but they can't change the default
[15:08] <kenvandine> was the hub working for you yesterday?
[15:09] <bfiller> I didn't try it
[15:09] <kenvandine> that should have already been crashing, since it isn't a tuple
[15:09] <bfiller> probably was
[15:09] <bfiller> probably wasn't working I mean
[15:09] <bfiller> kenvandine: ah wait
[15:09] <kenvandine> davmor2, can you run this "gsettings get com.ubuntu.content.hub.default pictures" ?
[15:09] <kenvandine> popey, ^^
[15:09] <bfiller> kenvandine: I also had been installing gallery-app deb to test, maybe that did it?
[15:09] <kenvandine> shouldn't have...
[15:10] <kenvandine> lets see what that default is set to for some people that doesn't have the silo or ppa added
[15:10] <davmor2> kenvandine: popey can you help with that
[15:10] <kenvandine> bfiller, resetting that should fix your problem though
[15:11] <cyphermox> seb128: just checking, all good with charles' indicator-datetime silo I set up for you?
[15:13] <popey> davmor2: on a hangout..
[15:13] <seb128> cyphermox, yes, that landed/got merged back, thanks
[15:13] <bfiller> kenvandine: resetting both of those keys fixed it
[15:13] <bfiller> kenvandine: now seeing a different problem on address book though..
[15:14] <kenvandine> bfiller, yeah?
[15:14] <cyphermox> seb128: oh good
[15:14] <davmor2> kenvandine: I'm on a mission to help with the decision to promote R250 which starts on 237  So I won't be much use to you till latter
[15:14] <bfiller> kenvandine: after choosing a picture from address book it shows up, but after hitting save it disapears
[15:14] <cyphermox> so then we're good with the alarms blocker? :D
[15:14] <bfiller> kenvandine: wondering if could be related to Elleo changes on address book on the image path
[15:14] <davmor2> kenvandine: if you can wait a bit I can run it on a tablet
[15:15] <kenvandine> davmor2, sure, just want to see what the default is in a current image without our silo added
[15:17] <kenvandine> bfiller, do you know what it does with the image?  keep a copy of it or just add it to the contact?
[15:17] <bfiller> kenvandine: not sure, I'm asking renato and Elleo on #ubuntu-touch
[15:31] <davmor2> kenvandine: from flo on current root@ubuntu-phablet:/# gsettings get com.ubuntu.content.hub.default pictures
[15:31] <davmor2> ['com.ubuntu.gallery', 'gallery', 'current-user-version']
[15:33] <davmor2> kenvandine: ^ is that good or bad news?
[15:43] <kenvandine> davmor2, that's good :)
[15:44] <kenvandine> davmor2, thanks
[15:50] <popey> davmor2: i am still concerned that my flo is constantly restarting unity8 after being upgraded from 237 to 249
[15:50] <popey> and now 250 too
[15:50] <ogra_> still works fine for me
[15:50] <popey> did you go 237 -> 249?
[15:50] <popey> skipping everything in between?
[15:50] <ogra_> (and obviously for the test infra as well)
[15:50] <davmor2> popey: still works fine for me
[15:51] <ogra_> i did go 238 -> 248 ... and today 248 -> 250
[15:51] <popey> right, I'm going to do it again (3rd time now) and if it still breaks I'm raising the priority of that bug report.
[15:51] <davmor2> popey: in date time if I click on clock it opens clock if I click on date should it open the calendar?
[15:52] <t1mp> popey: how often is "constantly" restarting?
[15:52]  * t1mp did 239 --> 249 --> 250
[15:53] <popey> boot it up, its restarting constantly
[15:53] <popey> by the exact definition you know that word
[15:53] <popey> phablet   2456  2.9  4.2<PHONE_NUMBER>8 ?        Ssl  15:49   0:06 unity8
[15:53] <popey> phablet   2705  118  3.0<PHONE_NUMBER>2 ?        Ssl  15:53   0:04 unity8
[15:54] <popey> phablet   2848  122  1.7<PHONE_NUMBER>6 ?        Ssl  15:54   0:02 unity8
[15:54] <popey> etc
[15:54] <ogra_> out of diskspace ? /tmp not writable ? (or something similar)
[15:54] <ogra_> did you check the upstart log for unity8
[15:54] <popey> tmpfs                           903M  288K  903M   1% /tmp
[15:55] <popey> http://paste.ubuntu.com/7131249/
[15:57] <ogra_> (process:2848): GLib-GIO-CRITICAL **: g_bus_watch_name: assertion 'g_dbus_is_name (name)' failed
[15:57] <ogra_> smells like it cant connect to dbus for whatever reason
[15:58] <popey> http://paste.ubuntu.com/7131263/ dbus log
[15:58] <popey> right, going to flash clean again
[16:00] <ogra_> well, since nobody else is seeing it i would suspect something in your home gets in the way
[16:01] <ogra_> (nothing sticks out in the dbus log ... but then i'm no unity dev :) )
[16:01] <popey> i wiped
[16:02] <popey> which is why it worries me more, because I did a --wipe when i put 237 on, so it's stock 237 to stock 249
[16:02] <ogra_> did you check that home is really empty ?
[16:02] <ogra_> probably an issue with ubuntu-device-flash
[16:03] <popey> will check
[16:03] <popey> its flashing
[16:11] <popey> ogra_: its clean, 237
[16:11] <plars> anyone know how to trick adb into running a process in the background (not background on the host, background on the device)
[16:11] <popey> ooh, there's suf in .local
[16:11] <plars> I tried something like adb shell "nohup foo &" but to no avail
[16:11] <popey> looks sane though
[16:12] <popey> plars: we should ship gnu screen or tmux on the device *hint* ogra_
[16:15] <ogra_> heh
[16:15] <ogra_> plars, i never tried but adbd tears down the shell when you disconnect, so nohup is unlikely to work
[16:18] <ogra_> plars, there is a way to put user upstart jobs into ~/.init or so ... you could dump something there, and fire it up via initctl then
[16:18] <ogra_> (not sure about the path)
[16:19] <sil2100> asac: in case I miss something, could you poke me once we're clear to resume normal landing? :)
[16:19] <plars> ogra_: in this case, it's not something I'd want to leave running forever. It times itself out after a specified amount of time and I don't want it to restart or anything
[16:20] <ogra_> so dont use repawn in the job ;)
[16:20] <plars> ogra_: but I do need it to dump a file, and it's output somewhere
[16:20] <plars> I'll look into it give that a try, seems an odd use of upstart
[16:21] <ogra_> why ?
[16:21] <ogra_> thats what user session support was designed for
[16:22] <asac> davmor2: things looking good so far? whats ETA?
[16:22] <asac> for finishing your run?
[16:22]  * ogra_ hopes we have some info for the meeting in 40min
[16:23] <davmor2> asac: a while yet but pretty much everything is green except for outstanding minor issues that are already known
[16:23] <davmor2> ogra_: doubtful look at the doc
[16:24] <ogra_> ah, k
[16:24] <asac> davmor2: yeah. the doc looks like you are currently testing the upgraded variant
[16:24] <asac> not the clean install
[16:25] <asac> not sure if i parse that correctly and whether there will be another run for clean install
[16:25] <ogra_> the run he is doing is the verification run anyway
[16:25] <ogra_> there was already a successful test run before
[16:26] <davmor2> asac: I did a fresh install for the dogfooding this morning.  This was to test that you could upgrade from the current promoted to 250 with no issues
[16:26] <davmor2> asac: I figured that was an Important test
[16:28] <plars> ogra_: seems to work ok, thanks! looks like it's $HOME/.config/upstart/foo.conf
[16:28] <ogra_> ah, cool
[16:34] <asac> davmor2: yeah
[16:34] <asac> thx
[16:41] <popey> reproduced bug 1295170 again
[16:42]  * ogra_ doesnt get why only you are affected
[16:43] <popey> probably because nobody else follows the procedure exactly ☻
[16:43] <popey> you have to put music on it
[16:43] <popey> and then wait, and then unity8 goes mad
[16:44] <ogra_> well, ToyKeeper tests music on the flo a lot ... (judging by her reports)
[16:44] <ogra_> it probably doesnt like your kind of music :P
[16:44] <popey> right, but you have to be not-connected before putting it on
[16:44] <popey> then when you connect, it does the mass update of album art or something
[16:44] <popey> and boom
[16:46] <ogra_> oh, wait ... you wipe only the first time and re-use the whatever generated metadata from the former install
[16:46] <ogra_> sounds like a data migration issue
[16:47] <popey> well, the --wipe cleans surely?
[16:47] <ogra_> it should
[16:47] <popey> the home looked clean to me
[16:48] <popey> and there was no music on it before I upgraded
[16:48] <ogra_> oh, ok
[17:05] <sil2100> cyphermox: will you be on the meeting?
[17:27] <sil2100> davmor2: let me take a lookie
[17:34] <sil2100> davmor2: looks good so far, as I see you're making music playback now - could you check video playback as well?
[17:34] <sil2100> davmor2: ah, I see you're doing that as well
[17:34] <davmor2> sil2100: I did say I was in the process of doing the scopes ;)
[17:35] <sil2100> davmor2: scopes ;) For me video playback is not part of scopes functionality! It's, like, functionality of its own ;p
[17:36] <robru> brb
[17:42] <sil2100> davmor2: sooo, is it a final +1?
[17:43] <davmor2> sil2100: looks like it but I think asac might want to have a quick look before you do.  I'm just going back through and adding links to the bugs
[17:43] <sil2100> asac: ^
[17:43] <sil2100> asac: can you check that provided document?
[17:43] <sil2100> davmor2: I think asac might be AFK right now
[17:44] <sil2100> Let's wait 15 minutes and if asac doesn't pop-up, let's +1 and promote \o/
[17:48] <robru> alright, who wants some landings?! ;-)
[17:49] <asac> davmor2: is there anything not known before?
[17:49] <asac> davmor2: if not, we delegated the +1 power to QA :)
[17:49] <davmor2> asac: on the click package Tagger crashing
[17:49] <cjwatson> robru: (cc thostr_) I'd love line 15 ...
[17:49] <cjwatson> (though I guess things already in silos come first)
[17:50] <davmor2> asac, sil2100: In that case by the power invested in me +1 looks pretty solid
[17:50] <robru> cjwatson, I suppose I can assign that. no promises on when it can be published though
[17:50] <sil2100> \o/
[17:50] <sil2100> Let's promote!
[17:50] <robru> sil2100, oh excellent
[17:51] <cjwatson> robru: it was blocked on autopilot, but I gather not any more
[17:51] <sil2100> ogra_: can you promote #250? Thank you :)
[17:51] <ogra_> sil2100, ok, doing so
[17:52] <robru> cjwatson, that's right, i did publish autopilot yesterday!
[17:52] <asac> davmor2: i dont know tagger, so you are better suited to make that call
[17:52] <robru> cjwatson, ok, i gave you silo 6, please build
[17:53] <davmor2> asac: 3rd party 3d tag reader creator will just need the dev to look at it and maybe rebuild against QT5.2.1
[17:54] <asac> davmor2: thats new? compared to yesterday?
[17:54] <asac> :)
[17:54] <cjwatson> robru: thanks
[17:54] <asac> or just newly noticed?
[17:54] <asac> davmor2: doesnt matter i guess
[17:54] <robru> cjwatson, you're welcome
[17:54] <davmor2> newly noticed
[17:54] <asac> ok then thats not new for me :)
[17:57] <dbarth> asac: ping?
[17:57] <asac> dbarth: ?
[17:57] <ogra_> [17:58] <dbarth> asac: hi
[17:58] <sil2100> ogra_: \o/
[17:58] <ogra_> :D
[17:58] <dbarth> i'd like to discuss the opportunity of having a silo for the big bad oxide landing
[17:58] <sil2100> Yay for no alarms for users!
[17:58] <sil2100> ;D
[17:58] <dbarth> right now, we can't have one because we need the FFE/MIR
[17:58] <davmor2> popey: what's your mtp not updating bug please
[17:58] <ogra_> who wants alarms on a weekend anyway
[17:58] <dbarth> but at the same time having a silo would help us smooth the test and release process
[17:59] <sil2100> ogra_: I actually need to wake up at 6 tomorrow morning!
[17:59] <dbarth> a bit like qt-5.2, at a smaller scale
[17:59] <ogra_> sil2100, insane !
[17:59] <asac> dbarth: we are starting to publish, so opportunity should arrive soon
[17:59] <dbarth> how does that sound?
[17:59] <asac> unless there is a silo already
[17:59] <asac> check with sil2100 who is in charge and later robru
[17:59] <dbarth> ok, but on the principle of getting a silo /before the FFE is formally acked/ you ok?
[18:00] <dbarth> (knowing that oxide is a must-have for the security team)
[18:00] <asac> dbarth: unless we are very low on silos, we dont really care as long as you put a note so we dont accidentially publish it
[18:00] <asac> dbarth: its your risk after all :)
[18:00] <dbarth> ok
[18:00] <dbarth> cool
[18:00] <asac> e.g. if FFE gets nacked you loose word
[18:00] <asac> work
[18:00] <dbarth> isure
[18:00] <dbarth> i'll add a line to the spreadsheet
[18:00] <dbarth> we'd better get started
[18:01] <asac> yeah. also depends a bit on how many things go into the silo
[18:01] <asac> and what the backlog of landings for those things is
[18:05] <robru> dbarth, need a silo? i'm your guy!
[18:05] <ogra_> the silo dealer
[18:07] <Laney> i give good price, many nice silo
[18:07]  * ogra_ imagines robru as Lefty the salesman ...
[18:07] <robru> silos, get your silos!
[18:07] <sil2100> dbarth: yeah, actually, if we have enough silos, we can assign a silo for the needs of features without even FFe approval, but with the 'note' that they can be flushed if something else high-priority appears
[18:08] <asac> sil2100: robru: so at bgest we would be a bit careful in which order we flush ready silos etc. and kicking images in between to get the engine going :)
[18:08] <asac> but well, i leave it you to you guys :)
[18:08] <robru> asac, no worries,thanks
[18:08] <asac> think though its common sense :P
[18:09] <dbarth> sil2100: ok
[18:10] <sil2100> The problem with current landings is that we have a lot of silos assigned but not tested yet
[18:10] <dbarth> sil2100: i'll continue piling things up on line 40 for now
[18:10] <dbarth> sil2100: i still need to have oxide touch the universe archive first
[18:11] <dbarth> otherwise we won't be able to build anything
[18:11] <sil2100> dbarth: ok, we'll keep an eye on that ;)
[18:15] <dbarth> sil2100: it's more for monday now i guess
[18:26] <jdstrand> dbarth: I didn't read all backscroll-- your silo is dependent on oxide in the archive, no?
[18:30] <sil2100> Ok, need to drive out now, see you on monday
[18:30] <sil2100> If there's anything urgent during the weekend - mup me
[18:30] <sil2100> Have a nice weekend!
[18:31] <asac> robru: ogra_: so will we kick images after flushing every other silo? just so we have them as checkpints?
[18:31] <asac> thats my last input before going into background
[18:32] <ogra_> asac, well, depends if cyphermox is around after the flushing ... else there will be the 3am build
[18:32] <asac> robru doenst have powers to push that button?
[18:32] <asac> interesting
[18:32] <asac> ok
[18:32] <ogra_> only ubuntu-devs have
[18:32] <asac> cyphermox: you around for a bit?
[18:32] <asac> ogra_: kk
[18:32] <cyphermox> well yeah
[18:32] <robru> asac, nope, i can't kick images
[18:32] <cyphermox> 3 more hours at the very least
[18:33] <cyphermox> i can kick the images
[18:33] <asac> cyphermox: i think its about taking image snapshots after each couple of silos
[18:33] <asac> and then trying to be smart about what silos to put togeher
[18:33] <cyphermox> err
[18:33] <asac> so we dont end up withh images that have 100 packages :)
[18:33] <ogra_> asac, hm
[18:33] <ogra_> asac, that wont work
[18:33] <cyphermox> well, it depends when it's worth spending time creating new images like this
[18:33] <asac> what wouldn work?
[18:33] <robru> asac, the problem with that is that each image kick takes fully 1 hour.
[18:33] <asac> cyphermox: why not? its just a button
[18:33] <cyphermox> yeah
[18:33] <ogra_> asac, if you build one after each landing they step on each other in the testing infra
[18:34] <asac> robru: right, so we have 1 hourly shots
[18:34] <cyphermox> asac: it takes a lot of time, for the little benefit it gives
[18:34] <ogra_> running the tests still takes 4-5h
[18:34] <asac> ogra_: that doesnt amtter as long as we have the iamges
[18:34] <ogra_> so you wont have any info
[18:34] <asac> i dont want to wait
[18:34] <asac> just have the images so we can rerun tests in case we break something during the shots
[18:34] <ogra_> right, you will have the snapshots, but not know if they broke
[18:34] <asac> right
[18:35] <asac> so in case something broke
[18:35] <ogra_> yup, understood
[18:35] <asac> we can easily just ask plars to run the iamges in bisecting style
[18:35] <cyphermox> how about we just ask people to not break stuff?
[18:35] <ogra_> lol
[18:35] <asac> cyphermox: thats not possible :)
[18:35] <asac> cyphermox: everyone tries hard
[18:35] <asac> but there are gaps :)
[18:35] <cyphermox> sure it is, it's software
[18:35] <ogra_> cyphermox, thats a good idea
[18:35] <asac> and mistakes
[18:35]  * ogra_ wants the t-shirt
[18:35] <cyphermox> yes
[18:35] <cyphermox> mistakes do happen
[18:35] <asac> and we have big silos in the queue
[18:35] <asac> so i am sure there will be something hidden
[18:36] <cyphermox> but at some point our proper, careful testing should mitigate the bad, ugly, stop-the-line mistakes
[18:36] <asac> and the faster we can remove such "bomb" the better we can continue running smooth
[18:36] <asac> cyphermox: sure. we are getting there
[18:36] <asac> we have the right incentives
[18:36] <dbarth> jdstrand: it is yes, i made a note next to the silo for that
[18:36] <asac> a) upstreams test on their own now
[18:36] <dbarth> jdstrand: chris is to start the upload this evening
[18:36] <asac> b) we add tests to their test plan after they slipped something accidentially
[18:36]  * ogra_ wants just 40 more makos in the lab so we can run all tests in parallel
[18:36] <cyphermox> asac: not sure it's the right incentives.
[18:36] <asac> c) they might choose manual, but given that thats work that encuourages them to automate
[18:37] <cyphermox> plus before we land, me and robru have to re-test everything quickly to make sure
[18:37] <asac> cyphermox: it is. we back their stuff out. they fix it and improve test plan
[18:37] <asac> cyphermox: right. we only want that for TRAINCON-1
[18:37] <jdstrand> dbarth: ah, ok
[18:37] <asac> cyphermox: but given the backlog, we should do it smartly
[18:37] <asac> for the first landings to get the engine booting
[18:38] <asac> cyphermox: you needed to double check because we had high alert state since qt5.2 landing. and before because of android 4.4 bustage.
[18:38] <asac> we dont want that alert state. key is really that if you find a gap, you talk to the lander and ensure he adds it to testplan
[18:38] <davmor2> seb128: you about still?  Do you know if the date in the datetime indicator is is meant to tie into anything?
[18:39] <asac> also taking random samples from the MPs and checking that they really followed checklist is important to ensure they get feedback
[18:39] <asac> anyhow.
[18:39] <seb128> davmor2, tie?
[18:39] <asac> would be cool if we could flush silos in steps and kick images in the middle to get checkpoints so we can go risky
[18:39] <ogra_> davmor2, it was a no-op in the past ...
[18:39] <ogra_> but its a long time since i tapped it last
[18:39] <davmor2> seb128: so if you click on the clock/time it opens the clock app
[18:40] <cyphermox> in the end, I don't really care, just tell us what you need and we'll get it done, but we're saying it will take lots of time and it doesn't mean it will catch the problems, nor make it easy to revert when you have additional packages that may depend on the broken ones, etc. and need to be rebuilt should stuff have to be backed out
[18:40] <davmor2> seb128: so I was wondering if the date bit was meant to open in the calendar
[18:40] <cyphermox> robru: you ready? you start from the top and I start from the end and we just try to land stuff when asac says go?
[18:41] <davmor2> ogra_: yeah I've hit it in the past but I'm wondering if it is meant to and has just never been implemented
[18:41] <robru> cyphermox, good god. well i'm here. are we seriously dumping it all at once?
[18:41] <seb128> davmor2, I don't think so, but that's a valid wishlist to open for design I guess
[18:41] <asac> cyphermox: haha
[18:41] <cyphermox> robru: no, not all at once
[18:41] <asac> cyphermox: pick the silos smartly
[18:41] <davmor2> seb128: thanks I was pretty sure it never had but just wanted confirmation thanks
[18:41] <asac> i would start with one shot of very leave apps
[18:41] <asac> and usually risk free things
[18:41] <asac> then image
[18:42] <cyphermox> we'll iteratively go through the silos, pick the easiest, safest first, then go from there
[18:42] <asac> then pick another silo with one big thing and a couple of more simpel things
[18:42] <asac> right
[18:42] <seb128> davmor2, yw, thanks for checking
[18:42] <asac> easiest first is probably goodie
[18:42] <asac> cyphermox: starting with leav'ish stuff also will prevent invalidaating silos accidentially
[18:42] <cyphermox> robru: also probably best to not assign new silos in between
[18:42] <asac> think we didnt enforce locks so some might conflict :)
[18:42] <asac> you guys do :)
[18:42] <asac> go!!
[18:42] <asac> :)
[18:43] <asac> and innovate how to do this engine kickstarting :)
[18:45] <davmor2> asac: right everything that had a bug now has it tagged I'm going to write up the new ones and the doc is then complete
[18:59] <cyphermox> asac: we sure did innovate, we're done
[19:00] <cyphermox> so there's nothing currently marked as having been tested, so we're not in a position to land anything new except for ubuntu-download-manager, which was just pushed
[19:00] <davmor2> seb128: not sure how I should assign this to design do they have a tag or something, I set wish list though https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295799
[19:12] <davmor2> asac: Right doc is good, all is good in the world, ogra_ why has imgbot not said anything?
[19:13] <davmor2> ogra_: or does it not say Promoted?
[19:14] <ToyKeeper> I was wondering about that too...  did imgbot already break?
[19:16] <ToyKeeper> The last line I saw from it was about image 249.
[19:16] <boiko> robru: so, just to be clear, is landing opened again?
[19:17] <robru> boiko, yes! do you have a tested silo for me?
[19:17] <boiko> robru: almost, I just found one weird thing: so, I flashed 250 on a nexus4, installed messaging-app-autopilot from the silo
[19:18] <boiko> robru: but when I try to run the autopilot tests, it says ImportError: No module named gi.repository
[19:18] <robru> boiko, oh god
[19:18] <boiko> robru: has something changed on autopilot itself lately?
[19:18] <robru> boiko, well there was just an autopilot release
[19:19] <asac> cyphermox: wtf
[19:19] <asac> cyphermox: so everything else was already landed?
[19:19] <asac> guess lets kick an image NOW then
[19:19] <asac> unless you tell me nothing was landed because nothing was ready
[19:19] <asac> that would be a shame :P
[19:20] <elopio> boiko: I remember having to install gir1.2-upstart-app-launch-2
[19:20] <elopio> they added the dependency on this branch: https://code.launchpad.net/~thomir/autopilot/trunk-upstart-support/+merge/210906
[19:20] <cyphermox> just waiting for ubuntu-download-manager to be in the archive
[19:21] <boiko> elopio: it is already installed
[19:21] <kgunn> robru: we added one more proj to the silo4 for the testing...mind hitting reconfig ?
[19:21] <kgunn> thanks
[19:21] <cyphermox> kgunn will do
[19:21] <kgunn> cyphermox: thanks....don't hit build tho
[19:21] <cyphermox> no that's up to you
[19:21] <kgunn> we only need to target build one or 2
[19:21] <kgunn> cool
[19:21] <robru> ah, beat me to it
[19:22] <robru> asac, yeah, that's what we are saying. only one silo was marked as ready, so only one silo got landed just then
[19:22] <boiko> robru: elopio: installing python-gi (as suggested by robru) did the trick
[19:24] <cyphermox> ah crap, this is the one where we need to ingore conflicts
[19:24] <elopio> python-gi is in build-depends. Should it be in a different section on t he deb?
[19:24] <boiko> elopio: so, python3-gi was installed, maybe that one is providing the required names?
[19:25] <robru> elopio, i think this is related to the python3 transition. it seems they dropped the python-gi dependency at some point without actually switching to running the tests in python3.
[19:27] <elopio> boiko, robru: ok, I don't know much about that. nuclearbob, should they report a bug? ^
[19:28] <robru> elopio, i'm not sure a bug is necessary, i know the python3 transition is in progress, i think they're working on it.
[19:28] <robru> they have another silo already
[19:28] <cyphermox> kgunn:  done
[19:28] <kgunn> thank you sir
[19:29] <robru> alright gents, I'm off for lunch and then I gotta catch a bus. I'll check in a little bit later!
[19:31] <nuclearbob> elopio: did you figure out that a bug wasn't necessary?  I've been trying to read the conversation in reverse, and I'm not yet sure which part I need
[19:32] <elopio> nuclearbob: it seems not. Maybe just keep an eye on the dependencies after the py3 things land.
[19:32] <nuclearbob> elopio: all right, can do
[19:32] <nuclearbob> :)
[19:32] <elopio> thanks nuclearbob.
[19:34] <bfiller> anyone know why I'm getting this error trying to run autopilot on the device? http://pastebin.ubuntu.com/7132306/
[19:34] <bfiller> not sure what I'm missing
[19:34] <bfiller> balloons: ^^^^
[19:35] <balloons> bfiller, looks like you are missing some python modules while running
[19:35] <balloons> copy them into /home/phablet/autopilot
[19:35] <balloons> or use click-buddy to provision
[19:36] <bfiller> balloons: I'm using phablet-click-test-setup --click com.ubuntu.gallery && phablet-config autopilot --dbus-probe enable && phablet-test-run -v gallery_app
[19:36] <bfiller> balloons: sergio told me gallery not setup for click buddy yet
[19:36] <balloons> ahh :-(
[19:36] <bfiller> not sure why
[19:37] <ToyKeeper> bfiller: We were *just* talking about that missing module.
[19:37] <balloons> is it click-fied?
[19:37] <ToyKeeper> python-gi should do it, I think.
[19:37] <sergiusens> bfiller, because it needs cross compilation support and has some qmake calls inside; the cmake file needs a cleanup
[19:38] <bfiller> sergiusens: you live!
[19:38] <bfiller> sergiusens: thought you were off today
[19:38] <sergiusens> bfiller, I'm off today (in theory, and monday)
[19:38] <sergiusens> bfiller, I'm in the middle of nowhere so irc is all you can expect from me :-P
[19:38] <bfiller> sergiusens: darn
[19:38] <bfiller> sergiusens: having problems testing the gallery click autopilot
[19:39] <balloons> bfiller, adb push /usr/lib/python2.7/dist-packages/gi/ /home/phablet/autopilot/gi
[19:39] <balloons> I believe that will sort you
[19:39] <sergiusens> bfiller, from the trace, it could be the new autopilot stuff and upstart-app-launch python modules (from robru's email)
[19:40] <sergiusens> that's just a guess a missing dep might be required
[19:40] <bfiller> balloons, sergiusens: installing python-gi sorted it
[19:40] <bfiller> at least tests running now
[19:40] <boiko> cyphermox: rsalveti: just a heads up, landing-009 is fully tested again, ready to land
[19:40] <balloons> yep, that works too bfiller
[19:40] <sergiusens> balloons, can we get python-gi into the autopilot-touch meta?
[19:42] <balloons> sergiusens, mm.. there's not mch in there now
[19:42] <balloons> sergiusens, talk to thomi
[19:46] <bfiller> sergiusens: who besides you can cooridinate the click release of gallery? we have it in the content-hub silo and needs to be released at same time as content-hub or it will break
[19:50] <cyphermox> boiko: ack
[20:00] <sergiusens> bfiller, balloons or xnox
[20:28] <bfiller> cyphermox: are you doing landings?
[20:29] <cyphermox> yes, looking at them
[20:29] <bfiller> cyphermox: line 21 ready for release, slightly complicated as click package for gallery needs to be released in sync with this release
[20:30] <cyphermox> where is this? why is it not in the PPA?
[20:30] <bfiller> cyphermox: gallery-app is both a deb and a click
[20:30] <bfiller> cyphermox: deb is needed for desktop, click for touch images
[20:31] <bfiller> cyphermox: the silo only builds debs, not clicks
[20:31] <bfiller> cyphermox: click upload needs to be manual
[20:31] <cyphermox> well it should still have the deb for desktop testing.
[20:31] <bfiller> cyphermox: it does
[20:31] <bfiller> silo 14
[20:32] <cyphermox> it's not listed at line 21.
[20:32] <davmor2> Night all have a great weekend
[20:34] <bfiller> cyphermox: it's one of the MR's
[20:35] <cyphermox> ver well
[20:42] <kgunn> cyphermox: wanna reconfig silo4 one more time ? ...we add 1 more proj to it
[20:44] <imgbot> [20:44]  * ToyKeeper hugs imgbot
[20:49]  * popey returns from being afk
[20:50]  * popey sees 17:57:55 < ogra_> [20:50]  * popey is happy
[21:15] <nuclearbob> woo!
[21:21] <bregma> cyphermox, would you be able to assign a silo for line 51 (Unity7 fixes)?
[21:21] <cyphermox> bregma: give me a moment
[21:49] <imgbot> [21:49] <imgbot> [22:08] <cyphermox> boiko: so far, silo 9 is a no go. I can't send phone calls or send SMS
[22:11] <cyphermox> kgunn: http://<IP_ADDRESS>/job/prepare-silo/625/console
[22:21] <cyphermox> bfiller: my system is flashing right now, as soon as it's done I'll test your silo
[22:23] <cyphermox> hey robru
[22:23] <robru> ahhhhhh finally
[22:23] <robru> been having a terrible time finding internet
[22:23] <cyphermox> why have you been looking?
[22:24] <robru> so what's up? i see three tested silos, two seem like big landings but that libclick one looks small and landable.
[22:24] <robru> and IRC ports seem to be blocked, so i'm just using frenode web chat
[22:25] <asac> 251 didnt reach the dashboard yet?
[22:25] <asac> ogra_: ?
[22:25] <asac> image still building?
[22:26] <asac> robru: ?
[22:27] <asac> ok seems image is in index
[22:27] <asac> so guess wait a bit for dashboard to pick it up
[22:27] <robru> cyphermox: yeah just checking in since i found some internet. did you not want me around? :-P
[22:35] <robru> hmmmm i don't seem to be getting any messages....
[22:38] <robru_> wow IRC is a remarkably flaky protocol in the face of connectivity issues
[23:31] <cyphermox> bfiller: still around?
[23:32] <cyphermox> how do I test without gallery-app?