[03:37] trainguards: can I have a silo for line 56, please? [03:38] (I’ll also need a binary copy into that silo, once assigned) [03:39] oSoMoN: on it [03:39] oSoMoN: didn't I just do an oxide-qt for yo? [03:39] robru, that was for 1.7.4, yesterday [03:40] robru, but we found more critical issues, which were fixed in 1.7.5 and 1.7.6, now we need to land the fixes [03:40] oSoMoN: heh, ok [03:40] * robru is totally out of the loop [03:41] oSoMoN: what's the PPA to copy from? [03:41] robru, https://launchpad.net/~phablet-team/+archive/ubuntu/ppa/+packages [03:41] oSoMoN: thanks [03:42] oSoMoN: ok, copy looks good. feel free to run build job [03:42] robru, thanks! [03:42] oSoMoN: you're welcome! [04:24] early oSoMoN :) (or late) [04:50] Most likely going to need some pay-ui fixes before this next milestone... nobody has been able to get an app purchase to work. === chihchun is now known as chihchun_afk [08:21] Saviq: Don't think you're getting off that lightly....oh no sir.....now it will be blaming you twice.......once for leaving that team and again for not fixing it before leaving ;) Enjoy your excursion into magic pendants :D [08:21] davmor2, tx ;) [08:23] ;) happy journey to server, Saviq [08:23] ;) [08:24] Serviq [08:27] hi trainguards, i need permission for requesting a silo [08:28] trainguards, could you help me with this please? [08:28] fgimenez: hey, sure, I can add you to the permission lists - do you know the essentials of how the CI Train works? [08:29] sil2100, more or less, i'm following https://wiki.ubuntu.com/citrain/LandingProcess [08:30] Ok then, let me add you in this case but remember to poke us whenever you have any questions [08:32] fgimenez: you should be set-up now [08:32] sil2100, thanks a lot :) we have the MR ready and i have a link for the test plan [08:32] sil2100, ok thx! [09:51] fgimenez: assigning a silo - just make sure no existing AP tests regress with the new autopilot :) [09:52] fgimenez: ...actually, it seems I can't assign a silo since we're out of free silos [09:52] sil2100, ok thanks! yep that's it :) [09:53] Mirv: do we need silo 18 now? [09:54] sil2100: well it'd be the testbed for further upstream work, but as silos are full I can free it for now (I've also checked no recent upstream activity on the branches) [09:56] freed [09:57] Mirv: thanks :) Let's hope we can open up the gates soon === 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: devel (vivid) touch landing gates now closed! Low on vivid silos. [09:57] Mirv: I guess since we won't be using ubuntu-rtm anymore, might be a good idea to increase the number of silo PPAs [09:58] Since we don't have ephemeral PPAs yet [09:58] Having both stable and 'w' in only 30 silos will be hell [10:18] that's true [11:11] * Mirv makes a deal about XPS 13 Developer Edition \o/ [11:22] Mirv: blog your experience pls :) [11:22] Mirv: I'm considering just keeping my x220 till it dies. [11:29] * sil2100 off to prepare lunch [11:35] cihelp: Can we make MR created by community members also get run in CI? === MacSlow is now known as MacSlow|lunch [11:35] Like https://code.launchpad.net/~feng-kylin/unity8/openPrepopulatedScopeInManageDash/+merge/257616 doesn't get run automatically because it's a community member (or that's the only difference i could find to any other MR) [11:36] so i have to trigger a CI build manually [11:36] which is a bit suboptimal [11:37] isn't it because the person isn't in the team [11:37] not that they're community [11:37] community core apps developers have CI run against their merges just fine. [11:37] but if a random drive by community person does a merge then it doesn't because they're not in the team. [11:38] tsdgeos: ^ [11:38] maybe [11:38] still i think it makes sense to get run CI all the time [11:38] what does it matter if they are on the team or not? [11:39] drive by malicious code executed on our hardware? [11:39] (I suspect) [11:41] i feel that's a rare possibility compared to the burden of me having to trigger builds manually [11:41] but oh well [11:42] trainguards, sorry, don't know if this is already done, is there a free silo for the AP request? [11:51] popey: I'll blog about it, yes [11:53] fgimenez: you have the silo already, 018 [11:53] Mirv, ok thanks! === MacSlow|lunch is now known as MacSlow [12:49] sil2100, whats the latest [12:53] sil2100, sorry disconnected [14:29] sil2100, jibel update? [14:29] pmcgowan: hey! [14:29] pmcgowan: we sent out e-mails to you [14:29] Check your mail ;) [14:29] ok will look [14:30] pmcgowan, I just sent the testing report [14:30] pmcgowan: in the meantime jibel finished the final formal report, it should be sent out soon (if it wasn't yet) [14:32] kenvandine: you'll have to wait probably, we're out of vivid silo ;) [14:32] sil2100, no rush on the vivid silo [14:32] but we are rushed for an rtm silo, which i already assigned :) [14:33] pmcgowan, ^^ building now, so far on schedule :) [14:34] oSoMoN_: hey! How's testing of oxide-qt 1.7.6 going? [14:34] sil2100, jibel even the wizard crash requires specific back forward and timing to hit [14:34] so not sure thats a blocker [14:34] sil2100, on it, looking good so far, should be good for QA validation very soon [14:35] only the browser crash seems worthy of discusuion [14:37] pmcgowan: the store issues also seem webbrowser related [14:42] sil2100: that is my best guess and might not be at all [14:45] sil2100, pmcgowan: I'm assuming that the intial screen is a webview that creates a frame and is then destroyed to open the ubuntu one account web frame instead. At that point crashes. It seemed the most logical explanation considering it works when you have a u1 account [14:46] davmor2, that would be good as we have that fix in progress [14:47] pmcgowan, re wizard if mterry_ is sure that back/forward is key to triggering the bug, I'm fine to not block on it. [14:47] pmcgowan: anyway, if the wizard bug requires specific steps to reproduce then I suppose it would be fine to let it slip for this release [14:47] I just didn't want new users to curse when trying to change their language ;) [14:48] yeah if it needs a back with specific timing I would not block [14:48] pmcgowan, bug 1450243 is a blocker IMO, the only way out is to reboot [14:48] bug 1450243 in Oxide "Stuck on select element during app store purchase" [Undecided,New] https://launchpad.net/bugs/1450243 [14:48] jibel, we can address that in day one update though [14:48] user wont hit it in first hour? [14:49] if they don't try to purchase something in first hour they won't hit it [14:49] since we have only a handful of purchases in last months [14:50] I would say no [14:50] mterry_: ping [14:55] jibel, do we still have the issue with the version string? I was thinking that was sortof critical but maybe not for one image [14:58] jibel: how much time do you think would be needed to re-run 30% of tests due to the oxide-qt landing? [14:59] pmcgowan, the version string is fine on this image. It must be confirmed on an image where the rootfs didn't change. [14:59] Kaleo, Hi! [14:59] Kaleo, I reported camera-app test failures a few days ago. Can you look into those now ? [15:09] sil2100, last time it took 3 hours with 2 testers [15:11] jibel: so in theory if we land the new oxide-qt in the nearest time we would sill be able to get the image re tested today by the US crew, right? [15:11] om26er, sure [15:12] Kaleo, I fixed one of them, the MR is here: https://code.launchpad.net/~om26er/camera-app/test-fix/+merge/256382 [15:13] sil2100, in theory yes [15:13] jibel: well, it indeed depends when we get oxide in, since image builds take a while too... ok, thanks :) [15:14] om26er, 2 to go? [15:14] pmcgowan: so, what's the decision from your side? We try to get the webbrowser issues fixed (new oxide), retest and done? [15:14] https://bugs.launchpad.net/camera-app/+bug/1444655 [15:14] Ubuntu bug 1444655 in camera-app "Autopilot failure: test_recording_stop" [Undecided,New] [15:14] https://bugs.launchpad.net/camera-app/+bug/1444645 [15:14] Ubuntu bug 1444645 in camera-app "Autopilot failure: test_picture_quality_setting" [Undecided,New] [15:14] Kaleo, yep [15:14] sil2100: If we begin to test the pending silos, anything to take into account? [15:15] rvr: the highest priority, as it's a blocker fix, would be silo 28 - but it's not ready yet [15:16] rvr: not much else that would be safe to land to vivid right now [15:16] rvr: we have a few good ubuntu-rtm silos that need releasing, but they're not set as ready for QA yet [15:16] pstolowski: how's the scopes fix RTM testing going? [15:16] sil2100: I have one for RTM in the queue [15:17] sil2100: ubuntu-rtm/landing-002 - gst-plugins-good0.10,qtmultimedia-opensource-src,qtmultimedia-opensource-src-gles : rsalveti [15:17] there is another one coming in a minute [15:17] hotfix, rtm [15:17] sil2100, yes land oxide fix and retest [15:18] rvr: yeah, well, that one I think was meant to land as well, but I think it wasn't signed-off yet since it probably needed a bit more testing [15:18] But it's targetted to land indeed [15:18] pmcgowan: ok, thanks [15:18] renatu, Hi! [15:18] rsalveti: Silo 4? [15:19] rvr: yeah, silo 4, just moved to QA [15:20] sil2100, not good unfortunately :(. we've just found a few moments ago that this fix, when backported, uncovers some other issues that affect only RTM. Fixing it proper would need a great chunk of other trunk code to be backported. I'm currently preparing a workaround for the favorites bug that can be applied on the shell plugin side [15:20] rsalveti: "On airplane mode battery discharge more rapidly than with airplane mode off" [15:21] rsalveti: So this requires leaving the phone some hours to discharge, right? [15:22] rvr: I added more info to the bug, but yeah, that is the best way to check [15:23] rsalveti: Ok [15:24] sil2100, can you reconfigure silo 3 for me? it's failing because I changed it to shell plugin [15:24] pstolowski: sure [15:24] jibel, sil2100 just to check - the vivid tarball for krillin is still in queue for +1, yes? [15:25] john-mcaleely: yes, sorry about that, RC and hot-fix OTA are in the way ;) [15:25] john-mcaleely: still in the queue [15:25] om26er, hi [15:25] no worries. just don't want to miss the news when it arrives :-) [15:25] renatu, I left a comment on https://code.launchpad.net/~renatofilho/address-book-app/fix-test_import_from_sim/+merge/256204 [15:25] rvr: this might be a good thing to work on if no vivid-blocker or rtm silos are ready [15:25] ^ [15:25] renatu, can you please fix that so we can merge that fix [15:25] ok [15:26] om26er, btw it is on silo 20 [15:26] sil2100: Yeah [15:27] renatu, hmm, ok we can rename the test later. [15:27] om26er, I can rename it now before it lands [15:27] trainguards can I get silo 005 reconfigured?? We need to add location-service to it else the fix does not work [15:28] renatu, that'd be great. [15:29] mandel: on it [15:29] mandel: I assume ubuntu silo 005, right? [15:29] sil2100, i have another initramfs-tools-ubuntu-touch dput to do ... (just FYI ... as always this will only get used and tested from a device tarball build later) [15:29] elopio, is silo 0 ready for qa? [15:30] om26er, done, could you approve it? [15:30] sil2100, rvr for rtm we want silos 0 and 4 [15:30] pmcgowan: wrong ping? I don't know what's in silo 0. [15:30] renatu, done. [15:30] elopio, sorry :( [15:30] om26er, thanks [15:30] pmcgowan: Not 2? [15:31] ogra_: hope it doesn't introduce any big changes, since we're almost done with the RC [15:31] rvr, oh yeah we sadi 2 as well [15:31] overooked it [15:31] pmcgowan: Ok, so 0, 2 and 4 [15:31] ack [15:32] sil2100, it is needed for factory images, else all devices will only use 8GB, even the ones that have 32 ... (it resizes the userdata FS on first boot in the factory) [15:32] sil2100, we need the binary built in the PPA to actually test it ... but it is irrelevant on the rootfs (only used in the initrd in the device tarball) [15:33] ogra_: ok, makes sense [15:33] ogra_, is that going into todays image for rc? [15:33] RTM silo 0 is not marked for QA sign off yet [15:33] ogra_, we had defered the resizing stuff [15:34] pmcgowan, oh ? i was told it has to be ready be EOW ... but anyway it ia an all manual process to pull that bit into the device tarball, so no risk here [15:34] s/ia/is/ [15:35] ogra_, so does it dynamically resize on first boot now? [15:35] vs fixed size [15:35] it checks how much space is unused and if thats above a threshold it will expand the FS to the full disk size [15:35] ogra_: pmcgowan: iirc we're using 16gb by default [15:35] ah [15:35] which is the device we are currently using [15:35] but, we need the resizing [15:36] * ogra_ didnt know the exact number [15:36] just not required to land for the factory image [15:36] right not today [15:36] yeah [15:36] ok [15:36] sil2100, ^^ [15:36] pmcgowan, yeah, but we need the binary in the PPA to actually be able to test it [15:36] ok [15:36] else we are stuck [15:36] I see [15:36] ok [15:36] so its there but not turned on [15:36] no worries, it wont actually land anywhere [15:37] ok [15:37] (apart from showing up on the changes indeed ... ) [15:37] * ogra_ dputs [15:50] ubuntu-qa: silo 28 (with oxide 1.7.6) is ready for validation [15:50] oSoMoN_: Ack [16:02] jibel: meeting! [16:10] sil2100, sorry, was afk [16:10] sil2100, but am here for a moment :) [16:11] mterry_: a question about the wizard crash [16:11] mterry_: does it require some really specific steps, or is it easily reproducible? [16:12] sil2100, fairly easily reproducable. Just have to change language, go forward, go back, repeat a few times [16:13] sil2100, can that change be silo'd? I'm on vacation for the next 8 days and won't be able to babysit it, but I'd like to see it land [16:16] sil2100: jibel: going to create another silo now for a small, contained fix, that fixes the size of the booting logo (spinning ubuntu logo) [16:16] mterry_, you have a fix? [16:16] should be ready in a few [16:16] pmcgowan, https://code.launchpad.net/~unity-team/qmenumodel/nullify-state-variant/+merge/257902 [16:17] pmcgowan, already top-approved [16:19] sil2100, jibel so we can try to take that fix as well, and there is a cosmetic fix to the boot logo in 26 that we can take as well [16:19] that being the wizard crash fix [16:32] mterry: is the fix tested? When would it be ready for QA sign-off? [16:36] sil2100: Silo 28 is empty [16:37] sil2100: Oh, right, creating the new image, don't mind [16:38] pmcgowan: so, we landed oxide - you think I should wait for the wizard fix before kicking a new image? [16:38] Or the spinner fix? [16:39] sil2100, why not kick an image inbetween [16:39] so the oxide fix gets some real life testing already [16:39] sil2100, spinner fix is ready for a quick verifiction [16:39] it is not like image builds cost us anything (except time, that we have while waiting for the rest) [16:39] sure we can kick it twice is you want [16:40] sil2100, seems someone can check the boot logo in a few mins [16:41] pmcgowan: few mins to QA verification? [16:41] sil2100, can i grab a vivid silo now? or is there someone else ahead of me in the queue? [16:41] sil2100, for qa its been ready [16:42] pmcgowan: oh, it's ready for QA? [16:43] kenvandine: not sure if we won't need one for mterry's fix [16:43] ok [16:43] his is more important [16:44] the click update bug isn't really going to be noticed by vivid users, it's really just critical for rtm [16:44] pmcgowan, ogra_, jibel: I'll kick a new image now and then we can re-kick in case the spinner lands (and maybe the wizard) [16:44] but i do want to get it landed in trunk soon [16:44] +1 [16:45] sil2100, its not yet marked couple mins it seems [16:45] so yeah go ahead [16:46] sil2100: pmcgowan: already tested with the deb, just waiting the jenkins job to show that it is built and tested [16:46] should take just a few minutes [16:46] if we can test it right away, I'd wait this silo === oSoMoN__ is now known as oSoMoN [16:47] I'd wait until we land this silo [16:49] sil2100, the favorites fix in rtm silo 3 is good to go [16:52] \o/ [16:54] rsalveti: what's the status of silo 15? it looks a bit stale and isn't in the qa queue... [16:54] \o/ [16:55] ogra_: where's imgbot?! [16:55] robru: it was but then a dput happened [16:55] still need to check it [16:55] sil2100: pmcgowan: silo 26 is ready for QA [16:55] rsalveti: also silo 13 ;-) We're out of silos so it's possible to free any that'd be great [16:56] sil2100, damn ... dead it seems ... and i have no access to my home machine atm :( [16:56] robru: I think we can free 19 [16:56] ogra_: can we free silo 19? [16:56] or is there any other work you need to do in there [16:56] Noooo poor imgbot! [16:57] i'll free silo 16 [16:57] kenvandine: thanks [16:57] done [16:57] robru: released 15 [16:58] but we'll have the same issue soon [16:58] as we already got a big pile of silos waiting the freeze to be released [16:58] what about silo 0? that was for mwc, and quite old [16:58] rsalveti: shouldn't take long, the RC is almost good [16:58] or did we want to keep that around? [16:59] sil2100: famous last words [17:00] kenvandine: kgunn had requested that silo relatively recently... although if he's done with it now it would be nice to free, yeah [17:00] ok, we have 2 free now :) [17:00] kenvandine: rsalveti: great, thanks guys [17:04] now that we have 2 free, do you guys mind if i grab one? [17:04] that'll still leave one for mterry's fix [17:04] kenvandine: bah, we just freed them up! [17:04] this is why :) [17:04] kenvandine: j/k, but as long as it's not an SRU it should be fine [17:04] it's not [17:05] kenvandine: k, go fo it [17:05] robru, and since i set col L, it should publish properly right? [17:06] kenvandine: yep, as long as you set column L before assigning it's all good [17:06] great [17:06] * kenvandine is nervous now :) [17:07] kenvandine: yeah you can see 'stable-phone-overlay' in the dashboard, it's good === alan_g is now known as alan_g|EOD [17:07] i see [17:12] sil2100, you asked if my crash fix was tested, ready for QA -- it was by me, the fixer [17:18] imgbot, stunt [17:18] * imgbot rolls on its back and purrs [17:18] sil2100, ^^ [17:18] Ah ha! [17:18] It's back! :) [17:19] sil2100: it never left you just weren't looking in the right place ;) [17:23] elopio, all changes merged on: https://code.launchpad.net/~renatofilho/address-book-app/fix-test_import_from_sim/+merge/256204 [17:23] elopio, could you approve it? [17:23] sil2100, flowers go to my GF for being my remote typist ;) [17:23] renatu: yes, thanks. [17:28] sil2100, yes, but rsalveti took care of it, thx! [17:49] crap... dep wait... guess i need to refactor my tests to not depend on ubuntu-sdk-libs [17:52] ricmm, where do I find the test plan for USC ? the one attached to the spreadsheet is non-existent. [17:54] rsalveti, do you know ? ^ [17:55] om26er: not sure we have one [17:57] rsalveti, interesting, what should I test apart from making sure the Ubuntu logo is bigger on boot ? :) [17:57] om26er: that was the only change [17:57] rsalveti, I guess that code only runs on device boot ? so if it boots then things are fine ? [17:58] om26er: that code yeah [17:58] om26er: you'll see a big difference on arale [17:58] rsalveti, yeah, I noted === davmor2_ is now known as davmor2 [18:10] === IMAGE 188 DONE (finished: 20150430-18:10) === [18:10] === changelog: http://people.canonical.com/~ogra/touch-image-stats/188.changes === [18:42] om26er_: as salveti said, the only binary that changed is the actual spinner program [18:42] which is different than usc itself [18:42] however, just making use the phone boots to unity and you can use apps and so on it means its fine [19:01] sil2100: pmcgowan: ricmm: publishing silo 26 [19:02] Did it pass sign-off? :) [19:02] Ah, it did [19:03] so whats left ? [19:03] I'm semi-EOD now so missed it [19:03] mterry, do you have a silo yet? [19:03] The wizard fix [19:03] But I don't see it in a silo yet [19:03] mterry: how far are you with the fix? [19:03] sil2100, pmcgowan: no --- I thought I saw you guys putting it in a silo... [19:03] sil2100, the fix is ready and top-approved. a one-liner [19:04] Uh oh :) [19:04] mterry: do you ahve a moment to put in a request? [19:04] sil2100, https://code.launchpad.net/~unity-team/qmenumodel/nullify-state-variant/+merge/257902 [19:04] sil2100, ok... [19:04] mterry: if you're busy I can do that [19:04] sil2100, in a meeting now, but will be done soon [19:04] mterry: ok, creating one then [19:05] sil2100, ok thanks -- sorry I dropped the ball on that [19:05] I thought I saw you folks talking about a silo with a few tiny fixes, including the crash one [19:05] * mterry is not on top of things today [19:06] mterry: I'm afraid there are zero silos available. [19:06] kick one out then [19:06] we need it for RC [19:06] robru, boo [19:06] ogra_: well I did two already, but then they filled up again. I'm not sure what others are freeable [19:07] just be evil (we will point people at you later) [19:07] oh heh, 26 just freed... [19:07] yep [19:07] :) [19:08] mterry: k ^ [19:09] Building the silo [19:09] ;) [19:10] * mterry hugs robru [19:10] * mterry also throws an arm around sil2100 [19:11] and what about powerpc ? [19:18] pmcgowan: can you add the milestone for https://bugs.launchpad.net/powerd/+bug/1450568 ? it's quite high as if a process holding a wakelock dies, the lock itself wasn't going away with the process [19:19] Ubuntu bug 1450568 in powerd (Ubuntu) "Requests are not cleared if a client dies unexpectedly and drops from the bus" [Undecided,In progress] [19:19] this fixes it, releases once the process that requested it goes away from the bus [19:19] pmcgowan: fix already in a silo, testing, and waiting qa [19:19] could be one of the reasons why a unity8 crash could end up draining the battery [19:20] +1 [19:20] *tested [19:23] \o/ === rsalveti_ is now known as rsalveti [19:47] mterry: are you testing silo 26? :) [19:47] mterry: please switch it to tested whenever it's ready for QA sign-off [19:47] It's the only critical thing we need before kicking a new image [19:49] sil2100, any qa around? [19:49] pmcgowan, qa is around [19:50] there he is [19:50] jibel, silo 16 has a wakelock fix if we want it [19:51] jibel, and rtm 0 4 and 5 all ready [19:51] jibel, what moves a silo from needs signoff to ready to test? [19:52] pmcgowan, manual review [19:52] essentially check the diff, changelog, bugs, and approved for a milestone [19:52] gotcha [19:53] jibel, what do you think about ubuntu 16, rsalveti wanted to land it [19:53] probably more important for rtm really [19:53] it's nice to have as long as it is not too invasive. [19:53] its a one liner when an app disappears [19:55] jibel, we could wait on vivid, ut get it out sooner in rtm [19:55] but [19:57] I want mterry's fix in vivid ASAP [20:19] sil2100, seems it requires a fresh flash [20:19] so not sure how we even test it [20:24] sil2100, ok I got it with just a wizard re-enable [20:28] sil2100, with the fix I cannot hang the wizard [20:28] without it I hung it in 4 tries [20:29] tested on 29 [20:29] arale [20:30] Nice [20:30] pmcgowan, what are the steps I should try to reproduce. I was not able to reproduce the crash yesterday. [20:30] Ok, I say the silo is tested locally now, let's hand it over to QA [20:31] now I need to be able to reproduce it so that I can validate the silo [20:31] om26er_, I eneabled the wizard, change language continue back change language continue back etc [20:31] on te continue it hung for me [20:31] blank screen [20:31] om26er_: silo 26 ready for sign-off, pmcgowan can give you useful info :) [20:31] om26er_, but you need to change the language [20:33] pmcgowan, aah, finally. [20:33] took me 8 language switches [20:33] om26er_, awesome [20:34] sil2100, any testplan to run ? [20:40] tedg, how do we test a change to qmenumodel per https://code.launchpad.net/~unity-team/qmenumodel/nullify-state-variant/+merge/257902 [20:43] om26er_, I would say verify indicators and settings still work properly [21:04] pmcgowan: so silo rtm 6 is ready for QA [21:09] pmcgowan, silo 26 approved. [21:10] om26er_, woot [21:12] will land it and trigger a build [21:29] pmcgowan, do we know if bug 1446584 affects arale as well ? [21:29] bug 1446584 in Canonical System Image "[krillin] On airplane mode battery discharge more rapidly than with airplane mode off" [High,In progress] https://launchpad.net/bugs/1446584 [21:32] om26er_, it does yes [21:33] om26er_, silo 16 and 30 are both battery related that are slated for rtm ota [21:34] pmcgowan, they are showing up as vivid silos, not RTM on the board. [21:35] om26er_, there are sios for both [21:35] om26er_, we wanted to stop landings for vivid though [21:35] unfortunately out of time [21:35] silo 4 is the rtm silo matching silo 30 [21:36] if I understand things [21:40] Publishing [21:42] pmcgowan: once the silo migrates I'll kick a new image [21:42] sil2100, vg sir [21:42] I think we lock now [21:42] * pmcgowan crosses fingers [21:42] alright [21:42] then sil2100 will take care of it :-) [21:42] * rsalveti gets back to the camera bug [21:43] :) Yeah, I'm still around [21:50] Ok, building the image [21:51] o/ [21:51] * sil2100 off now [21:51] o/ [21:51] If anything, tomorrow there's a national holiday, so I'll be only around briefly [21:51] See you! [21:55] === IMAGE 189 building (started: 20150430-21:55) === [22:21] bfiller_: no silos available, sorry [22:22] bfiller_: I'll send an email asking people to free any that aren't needed [22:22] robru: thanks [22:22] bfiller_: it's been tight all day. as soon as I free one, one more fills it up... [22:43] mzanetti: camako: are you guys using silo 0? I just noticed kgunn is on holiday [22:44] robru, kgunn put anpok in charge of it. Yes we are using it. [22:44] camako: ok thanks [22:50] silo 003 good for qa, if you want to reclaim some more silos [22:51] davidbarth: thanks for moving that along! [23:17] imgbot, status 189 vivid [23:18] Status: succeeded, Started: 2015-04-30 21:51:39 UTC, Finished: 2015-04-30 22:43:37 UTC [23:18] Build URL: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/vivid/ubuntu-touch/+build/25965 [23:18] Changelog: http://people.canonical.com/~ogra/touch-image-stats/189.changes [23:18] aha [23:25] robru: mind reconfiguring silo 28 [23:25] robru: added a new package [23:26] bfiller_: sure, one sec. [23:27] bfiller_: ok done. [23:27] robru: thanks [23:28] bfiller_: you're welcome!