[00:00] hah [00:00] but sometimes even :) [00:00] cjwatson, apps start fine for me on 288 [00:00] ogra_: I like the new indicators I like how it swipes down very swish [00:01] why doest my mako on 288 have new indicators ? [00:01] that still hase the old headers here [00:01] ogra_: thanks for the confirmation [00:02] oooh [00:02] that horrible dots from the launcher are gone [00:02] wow, this is the first time utopic fells like it is behind [00:02] ogra_: why do you think I was hugging Saviq earlier [00:02] haha [00:02] that was a well deserved hug [00:03] ogra_: indeed no ugly dots [00:03] and the icons fold again [00:03] hmm [00:04] * rsalveti back from dinner [00:04] cjwatson, ogra_: so we should be safe with the new custom tarball and rootfs then, right? [00:04] On krillin that is [00:04] sil2100, well, no idea ... i know we are safe on utopic 288 [00:04] * sil2100 notes down that we need to sync up utopic later [00:05] ogra_: if it works on utopic, I would say it should be the same on 14.09 [00:05] yeah, but proof is better at this point in time i guess :) [00:05] great, new image is out [00:07] heh, scrolling through my music still gives the thumbnailer some grief [00:08] sil2100: I believe so [00:12] cwayne: oi mr what the hell [00:13] davmor2, ? [00:13] * cyphermox back from dinner, if I can help with anything [00:15] davmor2: ? [00:15] cyphermox: o/ [00:17] sil2100: there is a tiny bit more than expected in the new tarball ;) [00:18] davmor2: in a good way or bad way? [00:18] I totally told you guys there were some new scopes! [00:18] cwayne: some I'm gonna hurt you yet ;) [00:19] davmor2, :P if it helps, just test the dashboard aggregator, that's where all the new ones are aggregated [00:19] we just added scopes that go into dashboard and dashboard itself, so if dashboard works, then they all work [00:29] bah [00:29] i thought the dash restarting was fixed [00:29] why do i still see it here ? [00:29] It should have been long ago [00:30] well, when starting 20 apps here it still gets respawned [00:30] i actually thought that was in Saviq's big silo [00:30] (was that 23 ?) [00:31] boing ... again [00:34] I think that only landed in utopic [00:34] not sure yet if that piece went to rtm [00:35] Wasn't that in the big silo 6 for ubuntu-rtm? [00:36] davmor2: any ETA on the custom tarball? :) [00:37] * cwayne just verified ringtones work [00:40] cwayne: what is that ringtone. Yani [00:41] ha, stuff from the customer :) [00:41] is it possiblt to sync my desktop-only landings to utopic still? Ubuntu final freeze is tomorrow and I have a couple critical fixes waiting to be published (silos 28 and 29) [00:41] bregma: hey! What do you mean by sync? [00:41] I mean publish, that was a mind slip [00:42] bregma: sure, basically desktop-only sounds a good thing for publishing [00:42] The big stop of landings is mostly for touch [00:42] I understand, these are definitely touch-free landings [00:44] bregma: so, are those nux and unity from silos 28 and 29? [00:44] sil2100, yes [00:45] oh cwayne come here so I can hit you ;) bug number one with the new code. Add a task, schedule it for today, tick it so it is completed, is it removed from the dashboard, is it boat ;) [00:46] bregma: ok, just to make sure - since I remember we're using some small parts of unity7 in our touch images [00:46] I think that was the -schemas package? [00:47] sil2100: OK, I'm off to bed because dear God look at the time. slangasek should be back in a bit should there be any snags with livecd-rootfs [00:47] cjwatson: ok :) [00:47] cjwatson: I'll wait for slangasek here just in case - goodnight and thanks again for everything! [00:48] hi [00:48] Yaay, he's back! [00:48] just sat down at the keyboard a minute ago; getting through scrollback now [00:48] bregma: so... just want to make sure the shared package with touch didn't get changed [00:48] slangasek: summarised briefly for you in /msg [00:48] ok [00:48] sil2100, the unity -schemas package would have to be manually synched, but there aren't any schema changes so no need [00:49] sil2100, hmm, so i thought the dash one was a promotion blocker [00:49] bregma: ok, sounds good [00:49] sil2100: cwayne: okay so I have run through everything I don't like the new ringtones but they might grow on me, then there is that minor niggle with the tasks other than that the tarball looks good [00:49] sil2100, it clearly didnt land in rtm yet [00:49] * ogra_ just dug through the qtmir changes [00:49] davmor2: hm, when I refresh the scope it's gone [00:50] and if it's done it should be gone [00:50] ogra_: hmmm, you checked that? I was almost sure we had a landing for that [00:50] But maybe that was utopic only indeed? [00:50] cwayne: it's gone in the app but not in the scope [00:50] sil2100, it was fixed in qtmir 0.4.4 [00:50] sil2100, which is not in rtm yet [00:50] Crap [00:50] cwayne: let me refresh the scope again [00:50] davmor2: even after a pull-to-refresh? [00:50] we landed 0.4.3 today [00:50] it's gone in mine [00:50] and I see 288 has been tested already, good; also installing it here atm [00:50] ogra_: anyway, too lat for that now - let's see if QA find it as a blocker too ;/ [00:51] Anyway, it seems there's a +1 on the tarball [00:51] sil2100, well, it makes using more than ten apps a pretty awful experience [00:51] cwayne: ah and now it has gone, maybe the backend scope only checks every so often [00:51] the dash restarts every few mins and steals the focus (which means a black screen saying "scopes") [00:52] davmor2: :) yeah, I don't know how often it updates itself, i'm a big fan of pull-to-refresh though :P [00:52] cwayne: that was about the 3rd time I had [00:52] sil2100: davmor2: so I'm good to press the magic button? [00:52] ogra_: hm, you think we should do a quick sync of that? [00:53] sil2100, i have no idea what a quick sync means in terms of stability and other bugs ... in any case that thing is on our promotion blocker list since a while [00:54] sil2100, https://launchpad.net/ubuntu/utopic/+source/qtmir/0.4.4+14.10.20141013-0ubuntu1 ... [00:54] that has more than just the one fix [00:54] Yeah, so what we could do is cherry-picking this fix, preparing a landing for qtmir-14.09, getting it tested and trying pushing it into this image... [00:54] ogra_, sil2100: ok - someone explain to me why I should not expedite things by kicking off the next ubuntu-rtm build immediately [00:55] slangasek: we're still discussing one issue that doesn't seem to have been fixed yet ;/ [00:55] https://code.launchpad.net/~unity-team/qtmir/dash-killed-less-likely/+merge/237915 [00:55] sil2100: there will always be more issues. It takes < 2h to rebuild; do you expect investigation of this new issue to have any real chance of taking < 2h? [00:55] slangasek, https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1379296 ... is longstanding on our blocker list and very user visible (as soon as you have some memory pressure the dash gets into the app lifecycle mgmt) [00:55] Ubuntu bug 1379296 in qtmir (Ubuntu) "unity8-dash should be excluded from app lifecycle management" [Critical,Fix released] [00:56] right, my concern here isn't that we have all the bugs fixed [00:56] my concern is that we're serializing things that ought not be serialized under time pressure [00:56] ogra_: so the change seems fairly simple, but I don't feel confident we have enough upstream people for that to get properly tested [00:56] ogra_: so let's leave it for an OTA update [00:56] qtmir takes 22 minutes to build [00:56] on armhf [00:56] that's a fair bit of time in an already very tight schedule [00:56] sil2100, well, your call [00:57] cwayne: I guess you can publish your custom tarball, and I think slangasek can build a new image [00:57] ah, the custom tarball isn't published yet? [00:57] \o/ [00:57] slangasek, so if sil doesnt want to block on it (and QA is fine with that too (it was their call to not promote with that bug)) then just go and build [00:57] I thought that was to be published at the same time as the apparmor landing, but ok [00:57] ogra_: I'm not talking about promotions here at all [00:58] slangasek: no, we just tested it [00:58] slangasek, turn off the import images cronjob [00:58] I'm talking about keeping our build pipe full [00:58] ok [00:58] slangasek, then you can have one image for rootfs and tarball [00:58] and dont need to wait for an import run [00:58] ok [00:58] cwayne, needs to publish while the rootfs is buuilding indeed [00:59] uh, i jsut did it [00:59] well, then it doesnt matter i guess [01:00] slangasek, but the plan was to have this image promoteable :) [01:01] looks like import-images was commented in time :) [01:01] cool [01:01] so we shouldn't get a spurious extra image [01:01] ogra_: that is not a reason to leave the build pipeline empty if the actual promotable image is > 1.5h out [01:01] true indeed [01:01] cwayne: so that means you've published your new tarball to the "gated" url, correct? [01:01] slangasek: yes [01:01] ok [01:01] kicking off a build [01:01] oh, possibly we just did [01:01] I see image 108 in there [01:02] Guys I'm off see you at the sprint, ogra_ sil2100 slangasek if you can ping ToyKeeper and elopio when the final image is up that would be awesom I'm off to bed night [01:02] ok [01:02] davmor2: thanks [01:02] so probably no point people spending time testing 108 FWIW [01:02] davmor2: thanks for all your work today! [01:02] See you next week! [01:02] yeah, that was an awesome effort davmor2 [01:02] that's just 107 plus the new custom tarball [01:02] oh? so the import ran already? [01:03] yeah you were slightly too slow [01:03] but no worries [01:03] ok [01:03] slangasek: note that (aiui) iso.qa doesn't work for starting 14.09 builds [01:03] its just numbers :) [01:03] cjwatson: no problem, I'm old skool anyway ;-) [01:03] ok :) [01:03] ah, I see it running now [01:03] * cwayne needs to take a bit of a break, will be around in a little bit if anyone needs me === cwayne is now known as cwayne-afk [01:04] right, really off to bed [01:04] night [01:07] cjwatson: goodnight :) [01:07] ogra_, sil2100, cwayne, ToyKeeper, elopio: so 108 on krillin -proposed is not expected to matter for testing. 109 should be upcoming and will be the version with the updated custom tarball split; it will be available in ~1.5h but is not considered promotable due to known bug #1379296 [01:07] bug 1379296 in qtmir (Ubuntu) "unity8-dash should be excluded from app lifecycle management" [Critical,Fix released] https://launchpad.net/bugs/1379296 [01:07] slangasek: yes :) [01:07] cjwatson: night, and thanks [01:08] ok [01:08] now what's the plan for getting bug #1379296 taken care of? [01:08] slangasek: we know, at least that was our original vision, since 107 was the one without custom, 108 with custom and 109 with custom + the rootfs [01:08] slangasek, see the bot ;) [01:08] sil2100: I'm repeating it to make sure everyone involved is on the same page [01:08] ok [01:08] silo 012 has the fix [01:09] sil2100: are you driving this silo? the train claims you+Saviq, but I don't see Saviq_ speaking up in scrollback :) [01:09] Yep, just filled that in [01:09] slangasek, prob is that all upstreams are asleep now ... [01:09] slangasek: it's his change so I'll ping him to help out [01:09] === trainguards: RTM IMAGE 109 building (started: 20141016 01:10) === [01:09] yay [01:10] As I'm only the cherry-picking guy, would like him to double check all is ok before we publish [01:10] sil2100: yeah, but unlike wherever you are, it's the middle of night for Saviq_ so he might not respond ;-) [01:10] pffff [01:10] unlike [01:10] haha [01:10] We're in the same TZ so he should be here! [01:10] heh [01:10] yeah, slacker [01:10] so, what's actually realistic here? [01:10] I don't think you're going to get Saviq_ back at 3am [01:11] Well, I think silo 12 might only be ready for tomorrow, so it won't be in the promoted image anyway, but we might get it in the next one [01:11] or 4am [01:11] we can prepare the silo up to the point where QA signs off [01:11] 3am is right [01:11] I wouldn't push it forcefully now, but I can get it built and pre-tested so that it's ready for morning [01:11] is it ok to promote this image with bug #1379296 present? Who should make that call, olli_? [01:11] and have Saviq nod it off tomorrow morning [01:11] bug 1379296 in qtmir (Ubuntu) "unity8-dash should be excluded from app lifecycle management" [Critical,Fix released] https://launchpad.net/bugs/1379296 [01:11] slangasek: I usually leave it up to QA to decide, since they will do promotion testing [01:12] slangasek, promotion is perhaps fine but i dont thinnk we want to gic it to manufacturer in that state [01:12] and if we're saying silo 12 won't land until morning, and the promotion needs to happen before then, we should surely let QA know to test image 109 [01:12] It's a serious issue, but for instance Selene missed it out when doing the pre-promotion testing on 105 [01:12] *give [01:12] sil2100: I think this is a product manager call, not a QA call [01:12] slangasek: well, that's the plan - QA will test 109 [01:12] slangasek: So... 109 won't be promote-able? Are we going to wait for 110, or send 109 anyway? [01:12] slangasek, they should test image 109 for sure ... [01:13] ToyKeeper: I would say we test 109 for promotion [01:13] and test the silo on top as well [01:13] But yeah, would be best to have olli_'s decision [01:13] ToyKeeper: well, this is what I asserted earlier, but now I understand that 110 won't kick off until the morning UTC [01:13] so there's a call to be made about whether to release to the OEM with this bug outstanding [01:13] slangasek: from what olli_ mentioned, we're already REALLY tight in our deadline, so waiting for 110 might be a bit impossiblish [01:14] will the manufacturer get the same OTAs ? [01:14] or wont they [01:14] ogra_: olli_ clarified that this is an image we're giving to the OEM now, but it's not the final image going to factory [01:14] if we can puch a direct OTA (promote a new one right after with only this fix) that could be doable too [01:15] slangasek, i know that :) [01:15] ok, so I didn't understand the question ;) [01:15] slangasek, the question is if they test as is or allow OTAs to happen [01:15] if they're getting this image, of course they get the same OTA as everyone else ;) [01:15] right, well, I don't think we control that [01:16] Let's not get carried away here on this channel guys ;) [01:16] heh [01:16] yeah [01:16] Not really my call, I'll just test 109 and send the results. Someone else can decide if it's promote-able even with known bugs. [01:17] ToyKeeper: could you ask elopio for help? It might take less time then [01:17] ToyKeeper: ok. In that case, eta for 109 availability remains ~1.5h :-) [01:17] thanks [01:17] From what I know jfunk mentioned elopio can help out as well [01:17] afk for dinner now for a bit; reachable by phone/text if you need me [01:17] slangasek: ACK :) [01:17] slangasek, i might go to bed as well then [01:18] slangasek, in case you need to promote [01:18] I might be dropping off soon as well [01:18] ogra_: probably a good idea :) [01:18] ogra_, sil2100: thanks to both of you [01:18] slangasek, rtm-promo.log in my home in nusakan has the promotion commands i used for former images [01:18] ogra_: yep, got it [01:18] should be easy to deduct from that [01:18] (as cdimage indeed) [01:19] sil2100: Yes, elopio is planning to help... but since we have a while before the image is ready he's doing something else for a while. [01:20] ToyKeeper, getting silo 012 signed off on top of 109 would be good as well [01:20] so that we can potentially land it as hotfix in case time permits [01:21] Not sure if there will be time for that now though [01:21] indeed [01:22] anyway, i'm off as well [01:22] see you tomorrow [01:22] sil2100, i assume we have a normal meeting ? [01:24] ogra_: I guess, if I wake up on time ;) [01:24] heh [01:24] Anyway, I'll see how much strength I have, I'll try to test te silo once it builds [01:24] But anyway I'll send out an e-mail to Saviq_ to pick it up from the morning [01:24] (since it'll be built already) [01:24] For now I go clean up some silos [01:35] ogra_, slangasek: I sent an e-mail to Saviq_, so he should be able to pick it up from the very morning [01:35] I think 3:30 am is the perfect time for sleep [01:35] Goodnight everyone! [01:36] o/ [01:48] Good god y'all [01:56] robru, what's going on with my build? https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-016-1-build/36/console [01:58] Hm [01:58] jhodapp, just a guess but 2014-10-16 01:55:32,398 WARNING A version (0.7.1+14.10.20141015.1~rtm-0ubuntu1) is available at the destination archive for that component but is not in the destination branch which is still at 0.7.1+14.10.20140926-0ubuntu1. You need to ensure that your version contains the fix in the destination or you can force rebuild to bypass the check.alues (0 6) [01:59] pmcgowan, yeah rsalveti is trying that last route [01:59] pmcgowan, thanks! [01:59] maybe some repo was not merged properly [01:59] let me check the repos [02:00] we just had one landing for qtubuntu-media a few hours ago [02:01] yeah, latest qtubuntu-media in bzr is not the same one that is available in rtm [02:01] let me sync that [02:05] That exception is really bizarre. Hopefully rsalveti can fix it [02:05] rsalveti, hmm, I merged with trunk before pushing [02:05] yeah, I think I know what is wrong [02:05] jhodapp: trunk is not reflecting latest [02:05] oh no [02:05] for some reason the branch tvoss created wasn't merged automatically with the landing [02:05] rsalveti: oh is there a silo that was published but not merged? [02:05] robru: silo is gone already [02:05] Ah [02:06] crap [02:06] so what's the process to remedy this? [02:07] jhodapp: manually mergint it [02:07] jhodapp: done for qtubuntu-media [02:07] ah right [02:08] alright, rebuilding [02:08] rsalveti, awesome [02:08] thanks [02:08] that was me aborting the previous build [02:09] rsalveti, ok :) [02:09] was just going to ask [02:09] === trainguards: IMAGE 289 building (started: 20141016 02:10) === [02:10] I should probably change that message to say "build aborted" or something... [02:11] argh [02:12] jhodapp: ^ [02:12] jhodapp: might need another merge with trunk [02:13] ok [02:17] rsalveti, try again [02:18] alright, now we wait [02:18] :) [02:18] rsalveti, eating lunch and dinner...only had breakfast today [02:18] haha, know the feeling [02:18] :) [02:22] rsalveti, the thumbnails of the self-recorded videos are still incorrect...it doesn't utilize qtubuntu-media or qtvideo-node as it goes straight to gstreamer [02:22] jhodapp: right, how to fix that? [02:22] rsalveti, the thumbnailer needs to listen for the same GstTag that media-hub does and do the still image rotation, height/width swap [02:22] wrong window [02:23] jhodapp: oh, right [02:24] rsalveti, it'd be very similar to what I just did [02:24] rsalveti, I'll have to bring Satoris/jamesh up on it [02:24] right [02:24] === trainguards: RTM IMAGE 109 DONE (finished: 20141016 02:25) === [02:24] === changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/109.changes === [02:25] guess this one is with latest device tarball [02:25] nice [02:27] jhodapp: ok, packages are finally building now [02:27] excellent! [02:27] time to watch some TV while it builds [02:28] oh no [02:29] rsalveti, same thing with qtvideo-node [02:30] the fuck [02:30] rsalveti, lol [02:30] that definitely should be in sync with trunk [02:30] job is still running [02:30] https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-016-1-build/40/console [02:30] weird [02:30] * elopio flashes 109 to start testing. [02:30] still building at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-016 [02:30] good [02:39] aborted the latest run so I can rebuild qtvideo-node [02:39] but the packages are still building on the ppa [02:48] ToyKeeper, is 109 the candidate? [02:49] jfunk, did someone notify AlexK [02:49] * olli_ waves at elopio too [02:49] elopio, ToyKeeper I have some baby bedtime duty but will then stick around [02:50] hello olli_. [02:51] olli_: We're testing 109, anyway... even though it doesn't have a fix for https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1379296 [02:51] Ubuntu bug 1379296 in qtmir (Ubuntu) "unity8-dash should be excluded from app lifecycle management" [Critical,Fix released] [02:51] olli_: Whether it gets promoted is someone else's call. I'll just report results minus that bug. [02:51] ToyKeeper, yeah [02:52] olli_: I am talking to Alex at this very moment [02:52] olli_: he knows already [02:52] jfunk, awesome, sending my mail update too [02:52] olli_: I am about to send a test status update myself :) [02:52] then ToyKeeper will send one after leo and her are finished [02:56] olli_: saw some talk earlier in the channel about important stuff and maybe 110 is the candidate [02:56] can you comment on that? [02:59] I think sil killed that before he left [03:00] ack, Alex K confirms [03:00] jfunk, if I am not misreading the backlog, then it was about https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1379296 [03:00] thx [03:00] Ubuntu bug 1379296 in qtmir (Ubuntu) "unity8-dash should be excluded from app lifecycle management" [Critical,Fix released] [03:00] yes [03:01] * olli_ doublechecks [03:01] not on the PM list [03:01] ok [03:02] slangasek, ^ btw [03:03] missed you q earlier [03:03] your [03:09] === trainguards: RTM IMAGE 110 building (started: 20141016 03:10) === [03:12] olli_: "not on the PM list" - well, it was also marked as fixed already, and no one tracked that it wasn't fixed on ubuntu-rtm, fwiw - not that I'm encouraging us to further block the promotion... [03:18] olli_: about to EOD [03:18] olli_: anything else you need? [03:18] elopio: and ToyKeeper will carry the torch for the next hour or two [03:18] rsalveti, can you try out silo 16 to see if it rotates for you cleanly? [03:18] jfunk, I think we are good [03:19] ack nite then [03:19] morning [03:19] thanks [03:19] nn [03:22] * Mirv catches up [03:26] ToyKeeper: hey torchkeeper :) assumably nothing goes in atm. are we waiting for anything in particular? 110 just started building, does it have that unity8 lifecycle fix mentioned above? [03:27] slangasek, so, I was reading the backlog again [03:28] not sure why https://launchpad.net/bugs/1379296 is a worry, it seems like it wasn't on the list to start with [03:28] Ubuntu bug 1379296 in qtmir (Ubuntu) "unity8-dash should be excluded from app lifecycle management" [Critical,Fix released] [03:28] Mirv: I don't know if it has the fix or not... I'm busy with 109. ;P [03:29] ToyKeeper: ok! [03:29] This test plan is really quite long though... will take a while to finish, even with two of us splitting the work. [03:31] ToyKeeper: keep up the good work, I'll dig up what I need from publish logs etc === olli_ is now known as olli [03:39] ubuntu-qa, or anybody: where do I report a bug for the facebook app? [03:42] Hmm... remind me not to make embarrassing photos/videos when I might need a screenshot for a bug report. ;P [03:42] I'm guessing webapps-core. There it goes... [03:48] elopio, got an ID? [03:49] olli: the bug was on promotion blocker list earlier, but apparently it somehow missed rtm and landed only in utopic. it's now cherry-picked in silo 12. [03:49] olli: ID for what? [03:49] elopio, webapps-core bug [03:51] Mirv, ah, promo blocker list [03:52] olli: bug #1381857 [03:52] bug 1381857 in The Webapps-core project "facebook web app is closed when the phone is locked" [Undecided,New] https://launchpad.net/bugs/1381857 [03:53] elopio, escalated [03:54] olli: do you want us to report here all the bugs we are finding, or do you prefer just to get the summary email? [03:55] elopio, ToyKeeper if you don't mind right here, then I can just escalate accordingly [03:56] I'll be around for another 2h [03:56] olli: bug #1377939 [03:56] bug 1377939 in Ubuntu UX "Scope using location cause a dialog "An unconfined application wants to access your current location"" [Undecided,Triaged] https://launchpad.net/bugs/1377939 [03:57] olli: and two minor details: [03:57] bug #1381857 [03:57] bug #1381849 [03:57] bug 1381857 in The Webapps-core project "facebook web app is closed when the phone is locked" [Critical,New] https://launchpad.net/bugs/1381857 [03:57] bug 1381849 in libqtelegram "Country list shows □ " [Undecided,New] https://launchpad.net/bugs/1381849 [03:59] sorry, I repeated the first. [03:59] It's bug #1381860 [03:59] bug 1381860 in The Webapps-core project "Facebook web app always has a cancel button that closes the app" [Undecided,New] https://launchpad.net/bugs/1381860 [04:00] jhodapp: working for some use cases [04:00] jhodapp: not every rotation though [04:00] let me record again to make sure [04:01] rsalveti, are the times that it doesn't work always reproducible? [04:02]