[00:14] Robru, I added the MP for Saviq to the spread sheet ---> https://code.launchpad.net/~mir-team/platform-api/rtm-14.09-compat-mir-0.8.1/+merge/246370 [00:14] robru ^^ [00:15] camako, ah, I see you unconfused this, glad [00:15] Saviq, yeah it builds [00:15] camako, you need to include this diff before your changelog change https://launchpadlibrarian.net/194801806/platform-api_2.5.0%2B14.10.20141015-0ubuntu1_2.5.0%2B14.10.20141015-0ubuntu2.diff.gz [00:15] camako, the train will complain otherwise [00:16] Saviq, you added platform-api to column G, now we are adding papi MP.. I dunno if it makes a difference [00:16] Saviq, ok I'll take that in too [00:16] camako, yeah, remove it from the sources column [00:17] Saviq, ok [00:19] robru, camako, because of the nature of the change I would not "revoke" the QA sign-off, just build it and publish straight away to unblock the migration [00:20] Saviq, I think I'm ok with that [00:20] one sec [00:20] Saviq, changelog updated [00:21] camako, thanks, ACK [00:35] Saviq, camako: sorry guys I gotta run to the doctor's, will be back in about 2 hours. Hopefully rsalveti is around to hit publish on that when it finishes building, otherwise I can do it later. [00:36] robru, nw, it's almost build, I'll just do a quick validation and set the spreadsheet accordingly [00:54] ok, robru, rsalveti, if you're around ↑, everything seems finally in order [00:54] please publish rtm/018 (only papi needs publishing, not sure how the job looks) [02:10] === IMAGE 65 building (started: 20150114-02:10) === === robru_ is now known as robru [02:38] Saviq: ok, sorry for the delay, republished [02:40] ToyKeeper, i saw your comment about the autopilot failures [02:40] you need python3-evdev installed [02:40] which i can't figure out why it isn't getting installed [02:40] python3-autopilot depends on it [02:40] for some reason when CI runs the AP tests, that package gets installed [02:41] but installing ubuntu-system-settings-autopilot doesn't... [02:41] i don't want to add a depends for it myself, since ubuntu-system-settings-autopilot depends on python3-autopilot, which depends on python3-evdev [02:56] ToyKeeper, i went ahead and added the depends and kicked off a rebuild [02:56] this way i know it doesn't bite us again [02:57] but if you like, you can just install that package then start the tests [02:57] the rebuild just adds the depends on the package [03:00] ToyKeeper, and silo 3 can land separately, just without it any settings test that mocks upower will fail [03:00] but they are failing now anyway [03:11] === IMAGE RTM 193 building (started: 20150114-03:10) === [03:18] ಠ_ಠ [03:21] Saviq: you still around? some kind of merge conflict cleaning your silo. [03:21] just looking into it now... [03:31] Saviq: nm, fixed it. all landed and merged now! [04:15] === IMAGE RTM 193 DONE (finished: 20150114-04:15) === [04:15] === changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/193.changes === [08:06] sil2100, good morning [08:07] sil2100, could you take a look at line 52, I adjusted needs qa to no, elaborated in the test plans column [08:07] Morning! [08:09] tvoss: I'll check that in a moment, but I might have to consult QA as well [08:21] pstolowski: hey! I would need you to get https://code.launchpad.net/~unity-team/unity-scope-click/fix-1390191-rtm/+merge/242214 approved by someone [08:22] tvoss: ok, so I'll have to talk about your silo with QA - normally I would let it in with this rationale, but since it's location-service QA might think there's additional risk assigned etc. [08:22] sil2100, hi! uhm, sure [08:25] dobey: ^ [08:25] (actually I see dobey was the lander) [08:28] sil2100, done [08:28] sil2100, dobey will be available in a few hours [08:32] sil2100: I am done with the rtm silo10, feel free to empty it and put back to the pool. Also the line 58 can be deleted from the sheet. Thank you a lot for the resources. It was a super valuable exercise. The Vivid edition of the UITK passes all tests on RTM. [08:34] bzoltan: that's good to know - does it also run without any user-visible problems? You dogfooded it? [08:34] pstolowski: thanks! [08:35] ogra_, davmor2, popey: I have a doctor's appointment in 10 minutes so I'll have to jump out, in theory I should make it in time for the meeting but this depends on the waiting queue === sil2100 changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: sil2100 out for a doctors appointment, trainguard back in ~1h [08:38] sil2100, sure, let me know if I can help [08:47] sil2100, hey, rtm silo 012 passed QA but Omer must've forgot to push the button, what do we do in that case https://trello.com/c/E7oTClp2/571-ubuntu-rtm-landing-012-unity8-saviq ? [09:00] ah actually no, it's the broken silo [09:10] sil2100, ogra_ - is now a good time to push a *vivid* device tarball? [09:10] john-mcaleely, sure, go ahead [09:10] o/ [09:11] thanks [09:11] john-mcaleely: yeah, no plans for vivid this week, so +1 === sil2100 changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: - [09:11] Saviq: broken silo..? [09:11] sil2100, yeah, see Timo's comment [09:11] I hope davmor2 will be along at some point today with news of the rtm device tarball :-) [09:11] Ah, this one [09:11] Yeah [09:12] Saviq: it will land soon then [09:12] sil2100, well, it's my fault as I accidentally built it and we tried to recover by bincopying to a different silo, but it never go to a coherent state [09:12] sil2100, thanks [09:12] ok, so vivid tarball pushed [09:12] john-mcaleely: no I decided I was bribed enough as a child [09:13] heh [09:13] I'm not sure I get that [09:13] sil2100, it seems like it won't do anything automagically, might even require manual copy to proposed [09:13] unless you find a way to get it to work... [09:16] geez .... test results for 192 and 193 look really bad [09:16] ~20 new crashers [09:17] Wow, 193 had mir, but this would mean it's unrelated? [09:17] seems unity-scopes_scoperunner crashes in every test [09:17] sil2100, yeah, started one image before [09:18] Looks like a scoperunner issue [09:18] sil2100: I blame ogra_ [09:19] ogra_: yeah... [09:19] sil2100, might be an apparmor one though, i cant open any log file so i cant tell [09:19] john-mcaleely: wasn't even now it might make more sense :) [09:19] * sil2100 logs in into the VPN [09:22] ogra_, health-check didn't run on 192 and 5 tests are failing. [09:24] jibel, yeah, thats not the issue, we have a new constant crasher (unity-scopes_scoperunner) [09:25] that worries me more than a few new crashes [09:25] right, could be bug 1357143 ? [09:25] err [09:25] bug 1357143 in unity-scopes-api (Ubuntu) "/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:unity::scopes::Variant::get_string" [Critical,Confirmed] https://launchpad.net/bugs/1357143 [09:25] failures [09:25] ogra_: looking at the console logs and comparing with earlier images, so far I don't see any additional apparmor denials [09:26] sil2100, yeah, smells like it could be the bug above [09:27] funnily on my own device ... while i have a unity-scopes_scoperunner.crash file, it is from the 9th ... so 5 days old [09:28] Maybe autopilot triggers it in a funny way [09:28] seems https://code.launchpad.net/~alecu/unity-scope-click/fix-empty-variant/+merge/246365 has the fix [09:28] alecu: ping [09:32] trainguards, I can has reconfigure on rtm silo 006 please, added qtmir there [09:37] hi there, any pending issues with ci ? [09:45] pstolowski: hey! [09:45] sil2100, hey === sil2100 changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: ubuntu-rtm landing gates closed! [10:03] tvoss: hey, so we had a talk about your silo, and it will have to wait for next milestone - sadly one of the reasons is also that it's not yet approved by the product team [10:03] john-mcaleely, ^, could you take care of that issue, please? [10:16] john-mcaleely: can you throw me the link for the tarball again please [10:19] sil2100, any word on publishing rtm silo 12? [10:19] Saviq: trying this now :) [10:19] sil2100, ah, thanks :) [10:19] john-mcaleely: nevermind found it [10:21] Saviq: if you could make sure to document adding dependencies in commit-messages/changelog-entries I would be really happy ;) Anyway, it seems it's publishing! [10:22] sil2100, I'll try to remember, sorries [10:22] sil2100, can I have a reconf on silo 6 in the mean time [10:22] No worries, it's cosmetics really [10:22] Saviq: sure [10:23] sil2100, btw, https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-012-2-publish/26/console seems to have a wrong path to the branch it pushed to [10:23] missing "ci-train-bot" [10:24] Saviq: this is really strange, actually the ci-train-bot LP account seems to be missing [10:24] Where did it push it to then..? [10:25] sil2100, it pushed fine [10:25] sil2100, just the log is wrong [10:25] sil2100, well, actually, maybe it pushed to ~/, which is the user's path then [10:25] Saviq: might be the case here then [10:26] Since CI Train prints exactly the string it did bzr push to [10:26] Didn't know you could do ~/something/something === marcusto_ is now known as marcustomlinson_ === marcustomlinson_ is now known as marcustomlinson [10:29] sil2100, see the last commit in https://code.launchpad.net/~indicator-applet-developers/qmenumodel/trunk - something's funky there as well [10:30] Saviq: yeah, noticed that in another trunk as well, the user config is somehow busted [10:30] The problem is that I don't have much power over the CI Train machine now after it got pushed to IS [10:30] But I'll re-try today to get someone looking at this [10:30] sil2100, nw, thanks [10:39] sil2100, sorries, one last resync of rtm silo 6, added a sync of qtubuntu from vivid :) [10:40] Saviq: sure ;) [10:40] s/qtubuntu/qmenumodel/ === cking_ is now known as cking [10:41] Done! [10:54] sil2100, how do I get tvoss gps testing silo approved? [10:54] sil2100, it's an urgent request from a customer [10:55] john-mcaleely, probably best to check with pmcgowan once he comes up [10:55] john-mcaleely: is this required for this milestone? [10:55] sil2100, yes. testing GPS needs to be done well before other dates coming soon :-) [10:56] It's a little bit latish you know ;) [10:56] *lateish [10:56] jibel: ^ [10:57] sil2100, my fault. I forgot to get the bug raised to the product team. Mostly because it was a feature request... [11:01] sil2100, is the silo creation closed? I'd need to create one for rtm quite urgent :-/ [11:02] sil2100, I though it could be done yesterday night [11:02] mandel: for testing you mean? [11:03] mandel: since for a silo to get it for this week's promotion it's already too late [11:03] sil2100, I guess it was promotion.. but well, if it is too late is too late, nothing we can really do I suppose [11:03] sil2100, I'll add it to the spreadsheet then [11:08] john-mcaleely, it's too late and not reviewed by the product team. You can escalate it to Pat. [11:20] jibel, do you know when the product team triage canonical-devices-system-image? It seems I filed it there four days ago [11:20] https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1408984/+activity [11:20] Launchpad bug 1408984 in location-service (Ubuntu) "No tool exists to test SNR &TTFF on a handset" [High,In progress] [11:20] pmcgowan, when you're online ^ please get this in this milestone [11:22] (the alternative is for our customer to wait at least a week, possibly two, to start this testing.) [11:24] john-mcaleely, idk when the review is. [11:29] hi trainguards, i have silo 007 vivid finally tested and good to land on vivid [11:29] I have also tested backports to 14.04 if I can get a sync to Trusty, to initiate the SRU process [11:30] dbarth: hey! Ok, let me do that [11:30] But let's first release to vivid [11:30] sure, that's the goal [11:30] upstream, then SRUs [11:31] dbarth: btw. you know why the build job was waiting for infinity? Do you remove some arches in this silo? [11:32] sil2100: it was a build wait because the chrome build fails on powerpc, etc. [11:32] same as oxide [11:33] That shouldn't have caused the build job to wait unless the package was previously built on those architectures [11:33] Which would then imply that you'll have trouble getting out of -proposed without archive admin intervention, and it would be best to have it analysed up-front [11:34] Yeah, looking at LP it seems that previously it had powerpc binaries [11:34] but: [11:34] unity-chromium-extension | 3.0.0+14.04.20140318-0ubuntu1 | vivid/universe | source, amd64, armhf, i386 [11:34] cjwatson: i think i stopped the job cause it was being stuck on those arches [11:34] No, wait [11:34] so IMO the build job is wrong [11:34] that one is a new piece of code [11:34] dbarth: You did, but it shouldn't have broken this way [11:34] using the newest chrome API [11:34] cjwatson: https://launchpad.net/ubuntu/+source/unity-chromium-extension [11:34] cjwatson: this page confuses me [11:34] ie, a replacement for the old NPAPI which has been deprecated [11:35] cjwatson: the version in -proposed seems to have powerpc binaries [11:35] cjwatson: while the one in the archive, LP says it's build-dep-waiting on something [11:35] sil2100: Yeah, clearly managed to build somehow, but that was in a utopic PPA so who knows [11:35] cjwatson: ah, scratch the last sentence of mine [11:35] cjwatson: it's actually dep-waiting on the 3 arches [11:36] do you have links to the individual builds that were on dep waits ? [11:36] And it was stuck in -proposed because those three arches had unsatisfiable binaries [11:36] dbarth: that's not necessary [11:36] ah right, so it couldn't have worked anyway [11:36] sil2100: so how about I just remove the binaries for those three arches from -proposed [11:36] they aren't going to work, and they're evidently now no longer built [11:36] +1 [11:36] cjwatson: sounds like a plan, thanks :) [11:37] it's disappointing that nobody followed this up for the 201 days that unity-chromium-extension has been stuck in -proposed [11:37] somebody dropped the ball in epic style there [11:37] 201 days? [11:37] oh, that was the initial landing attempts [11:37] and then we went into fixing the package-kit problem [11:37] given how easy this was to address, it should have been addressed ~200 days ago [11:38] and not ignored [11:39] 201 days?! Oh damn [11:39] I've removed those binaries now; I strongly suggest letting the 200-day-old upload migrate before dealing with the next one [11:39] sorry, i was not aware this package was still blocked there [11:39] I suspect somebody cleared a silo when they shouldn't have [11:40] i asked the initial silo to be unloaded, knowing it would take a bit to fix the other bug [11:40] yeah, but this is how things get lost [11:40] and then we went into 'phone focus' mode... ;) === tvoss is now known as tvoss|lunch [11:58] davmor2, any news on the device tarball? (I'm on hols today, and will be out this afternoon, if it needs pushing) [11:59] john-mcaleely: running still should be done in about 25-30 minutes [12:00] davmor2, cool, no problem [12:03] * sil2100 goes off to prepare dinner [12:03] john-mcaleely: once you get a +1 from davmor2, feel free to push it [12:04] sil2100, thanks! [12:05] must be quite some dinner if you start preparing it around noon :) [12:05] lol [12:10] jibel, looks like victorp got to it before pmcgowan . I believe #1408984 is now approved for this milestone [12:10] sil2100, ^ === MacSlow is now known as MacSlow|lunch [12:34] ogra_: it has to cook in the oven for over an hour ;) [12:34] :) [12:34] ogra_: oh, and I meant the 'dinner' dinner [12:34] You know, dinner can mean 'supper', but can also mean 'lunch' [12:34] Confusing [12:35] heh [12:52] sil2100, john-mcaleely: tarball complete [12:53] davmor2, yay. +1 ? [12:53] pete-woods: did you ever figure out the "(missing upload)" thing for the store? [12:53] john-mcaleely: yeap [12:53] davmor2, double yay [12:55] sil2100, ogra_ pushed, per your comment above. Coming to an rtm build near you soon :-) [12:55] thank you! [12:55] john-mcaleely, enjoy your holiday now ! [12:55] :) [12:55] o/ [12:55] :-) [12:59] So now we just need to wait for rvr to finish testing telephony-service [12:59] sil2100: I did, but I need boiko to confirm an issue [12:59] Oh [12:59] Either him or bfiller [13:00] john-mcaleely: now get outta here ;) [13:00] jibel, brendand, davmor2, rvr: did you notice any scoperunner crashes during todays usage [13:00] ? [13:00] _usr_bin_webapp-container.32011.crash [13:00] _usr_bin_webapp-container.32011.upload [13:00] _usr_bin_webapp-container.32011.uploaded [13:00] sil2100: ^ that's it [13:02] _usr_share_click_preinstalled_com.ubuntu.camera_3.0.0.412_camera-app.32011.crash [13:03] No scope crashes, though === alan_g is now known as alan_g|lunch [13:08] davmor2, rvr: great news [13:08] We'll anyway inform cwayne once he's up [13:08] sil2100: whatsup? [13:09] you broke it !! [13:09] :) [13:09] cwayne: hey! So, after the custom tarball upload yesterday we noticed scoperunner crashes for every autopilot test in the smoketesting suite [13:09] cwayne: it's always reproducible on the testing environment, but it seems to happen only during running autopilot tests [13:10] hmm, there were only changes to like 2 scopes.. shouldnt have affected any of the other ones [13:10] sil2100, that is wierd, nothing else landed on the actual scope running? [13:10] cwayne: it seems some scope is crashing, and since no scope-related thing got updated besides the custom tarball [13:11] victorp: no... nothing besides that [13:11] do you have some logs? [13:11] victorp: there were a lot of landings, but nothing to do with scopes [13:11] as i said before, apparmor changes landed too, but we dont seem to have any apparmor denials in the logs [13:12] iirc the apparmor changes were custome related [13:12] -e [13:12] it's happening for every single autopilot test? [13:12] victorp: http://rtm-dashboard.ci.ubuntu.com/smokeng/utopic/touch_stable/krillin/192:20150113:20150107-5ffb790/223/reminders/ <- here's for instance one of the tests that had the crash, you can access the crashfile there [13:12] cwayne, yup [13:12] cwayne: almost every, but in overall there's like 20 scoperunner crashes in the smoketesting runs [13:12] http://rtm-dashboard.ci.ubuntu.com/smokeng/utopic/touch_stable/krillin/192:20150113:20150107-5ffb790/223/ [13:13] sil2100, it looks like I cant see that :( [13:13] I guess I dont have vpn setup [13:20] sil2100, not today, but I've a scope runner crash from 2 day sago === kalikiana_ is now known as kalikiana [13:30] bzoltan: aargh, unapproved branches! :) Check merges from silo 10 [13:31] sil2100: ohh, I am sorry. So amateurish mistake ...fixed [13:37] sil2100, so you know why the status of rtm 004 is "ready to build" on the dashboard when the package is built in the ppa since yesterday? [13:38] seb128, an MP branch or is it a source package upload ? [13:38] ogra_, copy from a vivid source [13:38] (the latter need a watch only build) [13:39] then try a watch only build [13:39] well, it's built [13:39] https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-004 [13:39] the train doesnt watch the actual build for source packages [13:39] you need to tell it to ... [13:39] it only works fully automatic for MPs [13:44] ogra_, danke, that worked [13:44] :) [13:44] john-mcaleely, om26er is on silo19 === alan_g|lunch is now known as alan_g [13:45] john-mcaleely, I am actually waiting for tvoss|lunch to give me steps to verify the fix. [13:45] cwayne: no. it's still happening today === tvoss|lunch is now known as tvoss [13:46] om26er, please see the bug report linked on the spreadsheet. Also: the patch does not alter the service's behavior [13:46] jibel, ^ :) [13:47] ogra_: do you know what happened with vivid? [13:48] rsalveti, was something supposed to happen with it ? [13:48] ogra_: well, it failed to build [13:48] E: Unable to locate package libmirclient8driver-android [13:48] E: Unable to locate package libmirplatform4driver-android [13:48] still that hack? [13:49] sigh [13:49] yeah, needs build system changes [13:50] ogra_: right, let me bump that [13:52] actually, there was no mir upload for days, maybe it just got promoted [13:52] maybe component-mismatches? [13:53] oh, no, those are the old names [13:53] there was a mir upload to rtm yesterday ... it should have gone into vivid too [13:53] yeah, you need to fix livecd-rootfs [13:53] $ bzr grep libmir live-build [13:53] live-build/auto/config: add_package install ubuntu-minimal libmirclient8driver-android libmirplatform4driver-android ubuntu-touch [13:53] live-build/ubuntu-touch/hooks/80-enable-libhybris.chroot:if dpkg -l libmirclient8driver-android 2>/dev/null|grep -q ^ii; then [13:53] yup [13:53] live-build/ubuntu-touch/hooks/80-enable-libhybris.chroot:if dpkg -l libmirplatform4driver-android 2>/dev/null|grep -q ^ii; then [13:54] right, but the upload for vivid happend at 8th [13:54] is there a mir ABI bump checklist that this could go on? there are several things that seem to be forgotten nearly every time [13:54] rsalveti, if you touch it anyway, drop that ugly check in the .chroot script [13:54] ogra_: sure [13:55] yeah, we need a checklist [13:55] camako: ^ [13:55] rsalveti: I processed NBS binaries yesterday: https://launchpad.net/ubuntu/vivid/armhf/libmirclient8driver-android [13:55] the old not-built-from-source binary would have been hanging around in the archive until then [13:55] right, that explains then [13:57] yeah, package got renamed [13:57] that was a big change [13:57] -Package: libmirclient8driver-android [13:57] +Package: mir-client-platform-android [13:57] wonder why nobody from touch was involved in that landing [13:58] most likely because it was prepared last year ... lying around til after holidays and then picked up again and touch people were forgotten [14:00] ogra_: why dropping that from .chroot? [14:01] only the check [14:01] not the command it wraps, just that dpkg -l code ... it is pointless [14:02] needed for libmirplatform5driver-android at least [14:02] right [14:03] argh, will need to brb, family around, need to have lunch at the right time [14:03] will fix this once back [14:04] pstolowski, sil2100: eh? [14:06] dobey, ? [14:06] the apparmor changes were to apparmor-easyprof-ubuntu and were only to allow more access to the sdcard for the camera and gallery in reserved policy groups. there is nothing in there that would've caused scopes to fail === jdstrand_ is now known as jdstrand [14:07] there was a custom tarball landing that incorporated those changes to fast boot. I can't comment on what else was in there [14:07] pstolowski: you and sil2100 mentioned me earlier. about your branch i guess? [14:07] s/to fast/for fast/ [14:09] dobey: all is cool [14:09] dobey, yes, we needed top-approval [14:09] seb128: it looks ok to me now [14:09] jdstrand, right, perhaps a scope falls over *because* it can access the SD card now :) [14:09] dobey, the silo was tested alreadt by om26er [14:10] well, they had access before, the only change was being able to readdir /media// [14:10] sil2100, seems the store scope is broken :/ [14:10] yeah. oh. i was pretty sure it was top approved already. anyway, ok. :) [14:10] ogra_: for users as well? [14:10] * sil2100 tries [14:10] sil2100, try it [14:10] but that would only affect scopes that were confined and used these policy groups-- and I know of none [14:11] i only get a wqallpaper and bouncin bottom bar [14:12] ogra_: hmm, I'm running 193 here and the store scope works fine [14:12] Let me experiment a bit [14:13] sil2100, i think victorp sees it too [14:15] sil2100, after reboot it works [14:15] ogra_: really strange, looks fine here [14:15] i upgraded to 192 this morning and to 193 just now ... so it probably only happens after a while [14:17] sil2100, or perhaps a server issue ... [14:17] sil2100: Approved silo 16 [14:18] rvr: \o/ [14:18] ogra_: so, you anyway think it might be the store scope at fault? [14:19] sil2100, see the other channel ... seems there is a server issue === MacSlow|lunch is now known as MacSlow [14:27] sil2100, yeah, I needed to do a watch only rebuild [14:27] thanks [14:29] ogra_, jibel: so I think we can label the scoperunner crash as low impact for now, right? [14:29] yeah [14:46] Ok, I see telephony-service has migrated completely, nothing in the proposed migration is left [14:46] ogra_, jibel: what do you say for building the candidate image now? === charles_ is now known as charles [14:53] tvoss, it timedout for me: "Problem executing the CLI: Wait for fix timed out." [14:53] om26er, sure, that's fine [14:53] FWIW I am sitting near a window [14:54] om26er, it's gps only, might well happen [14:54] om26er, could you pastebin the complete output? [15:01] rsalveti, something wrong with Mir? [15:01] tvoss, it took a long time to scroll in the terminal to copy that text. ~15000 lines. http://paste.ubuntu.com/9748370/ [15:01] camako: we need some sort of checklist when landing mir, because we're currently hardcoding the package name at the script that builds the touch image [15:02] camako: latest update included a package rename and abi bumpa [15:02] *bump [15:02] which broke vivid, which I'm currently fixing [15:02] om26er, thanks [15:03] rsalveti, I see.. bummer... who owns the script? [15:04] camako: it's part of livecd-rootfs, so any core dev should be able to update that if needed [15:04] camako: but just ping either me or ogra_ and should be fine [15:04] until we fix this properly [15:06] rsalveti, I was under the impression that it was fixed. I'll talk to Chris (RAOF). [15:06] the issue is the update alternatives for the android/desktop backend [15:06] to fix this properly we basically need to remove mesa from touch [15:07] rsalveti, gotcha [15:07] ogra_: once you're around, maybe let's kick a new image if jibel has nothing against it [15:07] because we're installing both mir-client-platform-mesa and mir-client-platform-android [15:07] when we should only be installing mir-client-platform-android [15:07] but the dep chain ends up bringing both [15:08] rsalveti, ok I'll chase it [15:15] camako: so, with latest mir we don't need update-alternatives for the client library, right? [15:16] just for the server [15:16] platform actually [15:16] rsalveti yes only platform [15:16] camako: great === plars changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping plars | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: ubuntu-rtm landing gates closed! [15:28] sil2100, waiting for silo 19 [15:28] jibel: oh, wait, so this got approved by Pat? [15:28]