[00:18] <ToyKeeper> I see image 267 now.  I don't see a notification about it though.  Is 267 the new OTA target?
[07:46] <Mirv> dbarth_: note line 29 is not marked as Ready. please marke it so if that's an error.
[07:47]  * sil2100 checks his mailbox for CI Train errors
[07:48] <Mirv> mandel: whtat's the status of line 12 (vivid) / 11 (rtm), will those land at some point?
[07:48] <Mirv> "Propagate the hash errors to the udm clients."
[07:48] <Mirv> if it's not yet in rtm I guess it won't be
[07:50] <dbarth_> Mirv: checking
[07:50] <dbarth_> Mirv: you can clear line 29; that one got merged into another silo
[07:51] <Mirv> dbarth_: ok!
[07:52] <Mirv> I see, line 21
[07:52] <jibel> sil2100, I'm out for an appointment, not sure I'll be back for the standup
[07:52] <sil2100> jibel: ACK
[07:53] <sil2100> jibel: how's the testing proceeding so far?
[07:53] <Mirv> jgdx: should you consider merging the three ubuntu-system-settings silos? only one can enter at a time, and with the QA signoff those won't be in vivid at this rate if done one by one, first waiting for the current u-s-s landing in silo 006 to go for QA signoff for publishing
[07:54] <jibel> sil2100, so far so good. nothing critical found yet, 27% tests left
[07:54] <Mirv> sil2100: or is there a limit of u-s-s MP:s to land in a single landing?
[07:54] <Mirv> I'm just worrying about the amount of weeks to get those bug fixes in with so many landings
[08:06] <sil2100> Mirv: there shouldn't be any limit, maybe besides URL length limits - but when that happens, we can assign the silo manually
[08:06] <Mirv> sil2100: ok
[08:12] <mandel> Mirv, agh! I forgot about that guy, yes!, but please, remove the silo, I probably need to redo some of the mrs
[08:26] <Mirv> mandel: ok! so remove silo and the rtm line but keep the vivid line available for later use?
[08:28] <mandel> Mirv, perfect, thx
[08:32] <ogra_> imgbot, status 166 vivid
[08:32] <imgbot> Status: succeeded, Started: 2015-04-09 02:03:01 UTC, Finished: 2015-04-09 02:57:35 UTC
[08:32] <imgbot> Build URL: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/vivid/ubuntu-touch/+build/24714
[08:32] <imgbot> Changelog: http://people.canonical.com/~ogra/touch-image-stats/166.changes
[09:08] <bzoltan> Mirv:  may I get a silo for the QtC landing?
[09:09] <Mirv> bzoltan: there would be one free silo yes, if you file a line
[09:09] <bzoltan> Mirv:  #59
[09:09] <Mirv> bzoltan: https://wiki.ubuntu.com/citrain/ ?
[09:09] <bzoltan> Mirv:  I will give the silo back today
[09:10] <Mirv> are you on the old spreadsheet?
[09:11] <bzoltan> Mirv:  ahh... new file. #53 it is
[09:11] <Mirv> I had to remove quite lot of my browser history entries to get rid of everything related to the old address (with "0au" in it)
[09:21] <ogra_> bzoltan, mzanetti, qtpim and ssl merged ...
[09:21] <mzanetti> nice!
[09:21] <bzoltan> ogra_: \o/ thanks
[09:24] <ogra_> bzoltan, also about your snappy question ... i think having a framework that easily enables you to create a snap for an external push-service poller/proxy for your app would be cool, so people can run a snappy cloud instance and do a one click install to get an external push service up and running
[09:24] <ogra_> tied directly into your application in the click
[09:25] <ogra_> bzoltan, do we have some place where we collect such ideas ?
[10:23] <bzoltan> ogra_:  not yet
[10:26] <davmor2> ogra_: how do I use the bot to figure out what version 20 is on rtm stable please
[10:26] <davmor2> ogra_: rtm proposed even
[10:28] <ogra_> davmor2,  teh bot only knows -proposed of either RTM or vivid
[10:29] <ogra_> hmm, i dont have a "latest" command, i shoudl probably add one :)
[10:29] <davmor2> ogra_: no worries I'll do it the old fashioned way :)
[10:29] <sil2100> jibel: good idea on the QA time-schedule graph, this is something really useful
[10:29] <ogra_> davmor2, well, i'll add such a function :)
[10:30] <ogra_> thanks for asking
[10:32] <davmor2> ogra_: thanks.  It will be useful for knowing what proposed images to flash for testing factory→latest  so for example we know that 224 was image 16, but we assume that most people will update so would be on 20 and not 16 any more if that makes sense :)
[10:33] <davmor2> ogra_: so we will still test 224 for ota but would also need to test 20 →21 too
[11:11] <jgdx> Mirv, ping
[11:14] <Mirv> pong
[11:29] <jgdx> Mirv, line 37 does not have a lot of backers it seems. I don't mind that not hitting vivid. Line 35 (arale fixes) is the most important one.
[11:31] <jgdx> I can't merge 35 and 36 since 36 is a bit risky.
[11:32] <popey> sil2100: i dont see calculator on https://trello.com/b/AE3swczu/qa-testing-requests-for-questions-ping-eu-jibel-us-jfunk-or-ubuntu-qa-on-ubuntu-ci-eng
[11:36] <popey> jibel: ^
[11:39] <rvr> popey: Do you want me to create a card for it?
[11:39] <popey> please
[11:39] <popey> http://people.canonical.com/~alan/calculator/com.ubuntu.calculator_2.0.153_all.click
[11:39] <popey> http://pad.ubuntu.com/CalculatorAppManualTesting
[11:39] <popey> thats the click and the steps we use to manually test
[11:40] <Mirv> jgdx: ok, then those being separate makes sense. thanks!
[11:42] <rvr> popey: Done
[11:42] <jgdx> Mirv, thank you
[11:43] <sil2100> Yeah, the spreadsheet reverted the landing of course
[11:43] <sil2100> popey: sorry about that, I could have anticipated CI Train troubles erasing it
[11:48] <popey> thanks rvr, no worries sil2100
[11:53] <jibel> popey, if you submit the request on the spreadsheet the card should be added automatically.
[11:53] <jibel> sil2100, ^ it is still supported by the spreadsheet, isn't it?
[11:53] <popey> jibel: spreadsheet glitch I guess.
[11:54] <jibel> popey, ah no, it on a separate sheet with tarballs
[11:54] <jibel> and we didn't update the trellobot
[11:54] <jibel> +is
[11:54] <sil2100> jibel: ah, ok, so brendand_ still didn't re-target then
[11:54] <sil2100> Ok, nvm
[12:21] <ogra_> imgbot, last
[12:22] <ogra_> imgbot, last
[12:24] <ogra_> imgbot, last
[12:24] <imgbot> The last krillin RTM build is 267
[12:24] <imgbot> The last mako vivid build is 166
[12:24] <ogra_> davmor2, ^^^ there you go
[12:29] <davmor2> ogra_: Yay
[12:49] <sil2100> On it
[12:57] <sil2100> alexabreu: hey! Regarding silo 23 - the silo mentions only AP and doc fixes, but the following merge also seems to modify real code: https://code.launchpad.net/~abreu-alexandre/ubuntu-html5-theme/fix-ap-tests/+merge/255084
[12:59] <sil2100> jibel, davmor2: we might need to block OTA-3 on that wizard regression, john-mcaleely confirmed my worries that BQ might use it in the production line
[13:00] <sil2100> We would have to explicitly ask them not to use it until we have a fix
[13:00] <sil2100> Or just block on it
[13:00] <jibel> sil2100, ack
[13:00]  * sil2100 waits for mterry
[13:01] <davmor2> chrisccoulson: did you get chance to look into the issue with the terms and conditions on the welcome wizard with mterry?  I think he pinged you last night to start the discussion
[13:02] <chrisccoulson> davmor2, yesterday afternoon
[13:02] <chrisccoulson> The crash is fixed in the 1.6 branch of Oxide, which is going to be pushed out as a security update next week
[13:02] <alexabreu> sil2100, yes there were bugs uncovered by the AP test failures
[13:02] <alexabreu> sil2100, one bug actually
[13:03] <chrisccoulson> But the experience without the crash won't be acceptable, because it will use software compositing
[13:03] <pmcgowan> davmor2, we decided to live with it as this image is not going to be flashed on new phones
[13:05] <cwayne_> sil2100, we found a small regression in the today scope, it *may* be a quite small fix, looking into it right now
[13:05] <davmor2> pmcgowan: from what john-mcaleely has said to sil2100, sil2100 is prepared to block it because bq will be flashing it to phones
[13:05] <sil2100> alexabreu: hm, sadly in this case I would personally prefer QA to sign it off
[13:05] <sil2100> alexabreu: but let me consult them in a moment
[13:05] <sil2100> pmcgowan: john-mcaleely said it will be flashed on new phones in a factory probably
[13:06] <sil2100> pmcgowan: see my question on barajas
[13:06] <pmcgowan> sil2100, we already had this discussion, let me check
[13:06] <sil2100> If we can explicitly tell them not to, then I suppose we can live with it - if, of course, we get the proper fix
[13:07] <davmor2> chrisccoulson: awesome, that's great news :)
[13:15] <sil2100> chrisccoulson: what do you mean exactly?
[13:23] <sil2100> chrisccoulson: also, another important question: would we be able to get the fix this week still, at least as a distro-patch or something?
[13:27] <alexabreu> sil2100, I'll rebuild the silo w/o the AP test fix branch to land the others that are more urgent
[13:27] <alexabreu> sil2100, (about silo 23)
[13:27] <chrisccoulson> sil2100, see https://bugs.launchpad.net/oxide/1.6/+bug/1439829/comments/6
[13:28] <pmcgowan> chrisccoulson, so we need 1.7
[13:30] <sil2100> alexabreu: wait a moment
[13:30] <sil2100> alexabreu: I'll ask QA to take a quick look
[13:31] <sil2100> alexabreu: ok... I see it's too late ;p
[13:31] <alexabreu> sil2100, ah yeah :)
[13:31] <alexabreu> sil2100, I'll do it in 2 steps
[13:35] <sil2100> chrisccoulson: thanks, when is the earliest we can get oxide 1.7?
[13:37] <sil2100> chrisccoulson: since this bug might actually block our OTA-3 update and similar, we would actually need a fix (or even a workaround, anything!) ASAP
[13:39] <chrisccoulson> sil2100, 1.7 is not ready for OTA. That's bleeding edge stuff
[13:39] <sil2100> Ouch
[13:39] <sil2100> chrisccoulson: can you join pmcgowan's hangout?
[13:39] <sil2100> I'll be there in a minute
[13:47] <sil2100> We're saved \o/
[13:54] <alexabreu> sil2100, you can land silo 23
[13:55] <bfiller> jibel: will QA have time today to test some of the silos that are ready? there are bunch in the queue
[13:55] <jibel> bfiller, yes we'll find some time.
[13:56] <bfiller> jibel: great, thanks. wrapping up our sprint this week and hoping to land some of these
[13:58] <sil2100> alexabreu: o/
[13:59] <sil2100> alexabreu: hmm, did you reconfigure?
[14:03] <alexabreu> sil2100, no just rebuild, dont think I needed to reconfigure do I?
[14:05] <sil2100> alexabreu: yeah, removal of an MP needs a reconfigure - let me do it, I think a no-op build should be enoohg
[14:05] <sil2100> On it now
[14:05] <jibel> sil2100, for info bug 1442156
[14:06] <sil2100> jibel: private bug?
[14:06] <jibel> sil2100, yes
[14:07] <alexabreu> sil2100, sil2100 thx
[14:11] <alexabreu> sil2100, do I need to re +1 silo 23?
[14:12] <sil2100> https://code.launchpad.net/~mhall119/ubuntu-html5-theme/add-docs-package/+merge/255279 needs approval ;)
[14:14] <mhall119> alexabreu: ^^
[14:14] <mhall119> is that branch still the one we want, or did you and dholbach replace it?
[14:14] <rvr> popey: The reminders app update had lots of strings.
[14:14] <alexabreu> mhall119, still the one we want
[14:15] <popey> rvr: yeah, we left it for a few days for the translators to do their stuff
[14:15] <alexabreu> sil2100, +1'd it
[14:15] <popey> rvr: which is why I didn't ask for QA last week
[14:15] <rvr> popey: I translated it to Spanish
[14:15] <popey> rvr: awesome, I wanted QA to approve it (but om26er found a couple of bugs) and then I'd re-submit with only language updates
[14:15] <popey> and put that in the store
[14:16] <rvr> popey: The one that comes in the RTM image, is not public yet?
[14:16] <kgunn> sil2100: hey, quick one...on this bug, i linked to your infamous "commit" report...did i match it up correctly ?
[14:16] <kgunn> https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1441822
[14:17] <sil2100> kgunn: hey! Looks to be the right thing - why is it infamous?! ;p
[14:18] <popey> rvr: we haven't updated the one in RTM recently
[14:18] <popey> rvr: thats why I submitted to QA
[14:18] <sil2100> Well, some info might me missing from it as it takes the data from the spreadsheet
[14:18] <kgunn> sil2100: cause it's use to go spank people that released stuff that resulted in a bug for me :D
[14:18] <sil2100> hah!
[14:18] <sil2100> ;)
[14:18] <sil2100> But yeah, that's the commitlog for #125, and since it seems it's broken with that image, I guess we can narrow down the source now
[14:19] <rvr> popey: I got the local/Evernote login dialog in English at start, that I didn't see before.
[14:19] <popey> rvr: what version of reminders you using?
[14:20] <rvr> popey: I'm regression testing image 266
[14:20] <rvr> Let me check
[14:20] <popey> rvr: the latest reminders isnt in that image
[14:20] <popey> rvr: r400 is what we wanted to go in, but it failed
[14:21] <rvr> com.ubuntu.reminders	0.5.380
[14:24] <sil2100> chrisccoulson: if you could give me and pmcgowan a poke once the oxide is ready in a PPA then it would be awesome
[14:24] <sil2100> alexabreu: publishing then
[14:24] <alexabreu> sil2100, thx
[14:26] <sil2100> alexabreu: grrr, need to rebuild again, changelog wrong, doing that now ;/
[14:55] <dbarth> hey trainguards; i'm getting jenkins build issues due to a gpg signature error in silo 28
[14:55] <dbarth> is there an outage somewhere?
[14:56] <om26er> Kaleo, ping
[14:56] <om26er> Kaleo, silo15 fails testing, see comment here: https://trello.com/c/JACWoVDb/1349-ubuntu-landing-015-qtubuntu-camera-bfiller-kaleo
[14:57] <sil2100> dbarth: let me take a look
[14:59] <dbarth> sil2100: ah no, that worked for armhf, i386, etc.
[14:59] <dbarth> sil2100: but not for some 64-bit platforms now
[15:01] <sil2100> dbarth: hm, this CI Train error might be a bug anyway
[15:06] <dbarth> sil2100: can i land the silo as-is (once tested) or will that take a rebuild for the error platforms?
[15:06] <sil2100> dbarth: I think we need the platforms rebuilt somehow, since if CI Train tracks those then it means they're in the archive
[15:06] <dbarth> the merge proposals block another one for a tst library down the line
[15:06] <dbarth> hmm, ok
[15:06] <sil2100> dbarth: we'd have to ask an archive admin to remove them if those platforms are to be dropped
[15:07] <sil2100> Which is possible, but I guess we would have to have good argumentation for that :)
[15:07] <dbarth> sil2100: and can i retrigger the build directly in the ppa for the failed arches?
[15:08] <sil2100> dbarth: I'll do it, the code for this is still not deployed :)
[15:08] <dbarth> hmm, at leat i cannot; no button for me
[15:08] <dbarth> ah!
[15:08] <dbarth> sil2100: cool, thanks
[15:09] <Kaleo> om26er, you're switching the camera while it's focusing?
[15:09] <sil2100> dbarth: re-triggered
[15:10] <Kaleo> om26er, and it was not happening before?
[15:10] <Kaleo> om26er, (that's on BQ?)
[15:10] <om26er> Kaleo, it happens during focus, yes. But I also see a hang if I wait for it to focus
[15:11] <om26er> Kaleo, yes krillin
[15:11] <om26er> I reverted back the package and it was not happening, re-installed the silo and issue is back.
[15:11] <Kaleo> om26er, focus, wait 10 seconds, switch camera, still broken?
[15:13] <om26er> Kaleo, hmm, seems it happens when I try to switch while its focusing
[15:13] <Kaleo> om26er, right
[15:17] <Kaleo> om26er, taking a look
[15:35] <dholbach> alexabreu, sil2100: I don't have that much experience with the silo process and everything, but http://people.canonical.com/~platform/citrain_dashboard/ says "Can't publish: Packaging changes need manual ACKing." for silo23
[15:35] <dholbach> who can approve it?
[15:35] <alexabreu> dholbach, sil2100 ...
[15:36] <sil2100> On it
[15:36] <sil2100> Sorry, meetings ;/
[15:37] <sil2100> dholbach: you're a core-dev, right?
[15:37] <dholbach> yes
[15:38] <sil2100> dholbach: ok, so I suppose you signed off both, let me publish then
[15:38] <dholbach> thanks a lot sil2100
[15:40] <sil2100> bfiller: I noticed one of the dialer-app tests got disabled in the silo 14 landing - is that correct?
[15:40] <sil2100> bfiller: I'm a bit worried that there's a lot of things that are not mentioned in the changelog
[15:41] <bfiller> sil2100: it's a new test that was written and that is not working yet
[15:42] <bfiller> sil2100: we wanted to leave it in the MR even though it's not ready yet
[15:42] <bfiller> sil2100: the MR fixes the bug mentioned only, and adds test infrasturcutre
[15:43] <sil2100> bfiller: ah, ok, now all those deps make sense
[15:43] <sil2100> So they're not really used yet, right?
[15:44] <bfiller> sil2100: if all the tests are disabled then no they are not used yet, salem_ are all the tests disabled on the branch or just some?
[15:45] <sil2100> bfiller: ok, I'll approve this anyway, but please try making sure next time (when the tests are enabled) the dep-additions are mentioned
[15:46] <dholbach> sil2100, maybe it's documented somewhere, but ... what is the abyss in the silo context? :)
[15:46] <bfiller> sil2100: ok, thanks
[15:46] <sil2100> dholbach: hah ;)
[15:46] <sil2100> dholbach: that means it's published, but didn't pop up in the -proposed pocket yet
[15:46] <sil2100> It's a good state
[15:46] <sil2100> It's just in transit
[15:46] <dholbach> ok
[15:46] <alexabreu> dholbach, you are too eager ;)
[15:46] <dholbach> I guess that's because the -doc packages are in binNEW?
[15:47] <dholbach> alexabreu, the API website deployment is sort of blocked on this
[15:47] <sil2100> Oh! WAIT, crap
[15:47] <sil2100> DAMN
[15:47] <sil2100> Archive admins will be mad at me...
[15:48] <sil2100> Because it was an upload from you dholbach, I didn't actually check the packaging diff, and I was supposed to first ask for an ACK from archive admins
[15:48] <sil2100> Oooh boy, I'll get beaten for it
[15:49] <sil2100> Oh well
[15:50] <ogra_> sil2100, now all beer for infinity might be on you during the sprint ...
[15:50] <dholbach> probably not... it's just an added -doc package - we need it to populate developer.ubuntu.com/api
[15:50] <sil2100> slangasek, infinity: hey guys, I made a big no no
[15:51] <sil2100> slangasek, infinity: I mean, I published dholbach silo that adds a new bin package without first approving it with an AA
[15:51] <slangasek> sil2100: which package?
[15:51] <sil2100> slangasek, infinity: can you take a look and do a post-publish ACK? https://ci-train.ubuntu.com/job/ubuntu-landing-023-2-publish/14/artifact/ubuntu-html5-theme_packaging_changes.diff <-
[15:52] <sil2100> slangasek, infinity: sorry for that, I let my guard down since it was a core-dev upload ;)
[15:52] <dholbach> sil2100, slangasek, infinity: I wasn't quite aware of the protocol - sorry about that.
[15:53] <sil2100> dholbach: no worries, it's something I should do on my side ;)
[15:53] <sil2100> I just missed it
[15:53] <slangasek> sil2100: a *doc* package?! you fiend
[15:53] <sil2100> YES
[15:54] <sil2100> I can perform seppuku if you just say a word
[15:54] <ogra_> didnt happen if there isnt a video !
[15:55] <slangasek> sil2100, infinity: acked
[15:55] <sil2100> slangasek: thanks o/
[15:57] <dholbach> sil2100, I'm glad I pinged you about it again :)
[16:02] <sil2100> robru: ping
[16:03] <robru> sil2100: oh hey
[16:07] <salem_> bfiller, all new tests are disabled
[16:29] <robru> bfiller: silo 7 needs to be rebuilt due to new revisions
[16:33] <om26er_> popey, Hi!
[16:33] <popey> om26er_: yo!
[16:33] <sil2100> chrisccoulson: ping
[16:33] <om26er_> popey, calculator seems to be a totally different app, seems its missing its icon
[16:33] <popey> it is a totally different app :)
[16:34] <popey> icon is known.
[16:34] <om26er_> popey, so what kind of testing is needed for it ? do you want to land that in vivid image ?
[16:34] <popey> om26er_: see the etherpad link?
[16:34] <popey> om26er_: it could be tested on rtm or vivid
[16:35] <popey> http://pad.ubuntu.com/CalculatorAppManualTesting
[16:35] <om26er_> popey, right, thats fine. I just want to make sure its not something thats going to land as is
[16:36] <popey> om26er_: okay, thanks for checking.
[16:54] <dbarth> hey sil2100; on silo 28, we just miss amd64 now
[16:58] <om26er_> lool, Hi! what kind of testing does the ubuntu-touch-meta require ?
[17:02] <lool> om26er_: it's noted in the spreadsheet, but essentially just confirming you can still install apps
[17:02] <lool> om26er_: it's basically a forward feature to allow having 15.04 apps in the store, but right now it doesn't change anything
[17:02] <lool> it's really a trivial change I'm afraid
[17:03] <om26er_> lool, great, thats good to know.
[17:03] <sil2100> dbarth: is it again a key-failure?
[17:09] <oSoMoN> trainguards: is the spreadsheet operational to request a new silo?
[17:10] <sil2100> oSoMoN: yes, currently no issues are visible, let me change the topic
[17:11] <oSoMoN> sil2100, cool, can I have a silo for line 57 then, please?
[17:19] <sil2100> oSoMoN: sure
[17:19] <sil2100> hmm
[17:20] <sil2100> Wait, actually we don't have enough silos I think
[17:20] <om26er> popey, are the designs for the calculator approved ? well it seems not "crispy"
[17:20] <popey> what does "crispy" mean? :)
[17:22] <sil2100> om26er: I think design actually requested all of this
[17:22] <popey> om26er: but to answer your question, we have approval from design for this release, and further design changes are yet to come.
[17:22] <sil2100> It's the redesign of a redesign
[17:22] <popey> yeah, they asked for this
[17:22] <sil2100> ;D
[17:22] <popey> no, there's more to come! :D
[17:22] <sil2100> OH NO, redesign of the redesign of a redesign?
[17:22] <popey> if the developers can stay motivated enough to re-re-design a freaking calculator!
[17:22] <sil2100> That's incalculation
[17:25] <om26er> popey, does the app come with automation, I wonder ?
[17:25] <popey> eh?
[17:28] <om26er> popey, calculator used to have lots of autopilot tests, can you please share the reboot branch ?
[17:29] <om26er> I couldn't find it
[17:29] <popey> https://code.launchpad.net/~ubuntu-calculator-dev/ubuntu-calculator-app/reboot
[17:32] <om26er> I wonder why would people favorite their old calculations :p
[17:37] <popey> om26er: mzanetti is fixing the bug you found in reminders
[17:37] <popey> om26er: but the crasher you found is not a regression, we know about that one for a while.
[17:38] <popey> om26er: so once fixed, I'll resubmit (shall I just move the card back to the left lane?)
[17:38] <popey> jibel said om26er might be able to fast-track the test rather than re-test everything
[17:40] <mzanetti> s/crasher/freeze/
[17:40] <mzanetti> hang
[17:40] <popey> yeah, that
[17:42] <om26er> popey, sure, he gave me a heads up in our standuo.
[17:47] <rvr> popey: Music app. We have a regression test for tracks that have "Unkown" genre. I am copying albums with that, and I see nothing in the Genres section.
[17:47] <rvr> Unknown
[17:48]  * rvr comparing with the stable release.
[17:49] <rvr> Bah, the version is the same
[17:50] <popey> Not a regression :)
[17:51] <rvr> popey: Did the behavior changed?
[17:52] <popey> From when to when?
[17:52] <rvr> From when the last time we run this regression test
[17:52] <popey> thats hard for me to say because I have no idea when you last ran it.
[17:52] <rvr> popey: I mean, is the expection still valid?
[17:53] <popey> rvr: https://bugs.launchpad.net/music-app/+bug/1396971
[17:53] <popey> intentional.
[17:56] <rvr> I see
[17:56] <bfiller> robru: rebuilding
[17:57] <Kaleo> om26er, still around?
[17:57] <om26er> Kaleo, yes
[17:58] <Kaleo> om26er, I pushed a fix, silo 15 is rebuilding
[17:58] <Kaleo> om26er, please let me know if it fixes it for you
[18:02] <charles> renatu, there were a couple of other landings in datetime this week. Silo 8's branch needs to be synced to it and I haven't gotten around to it yet
[18:02] <charles> renatu, I'll do that now
[18:17] <kgunn> Mirv: you around ?
[18:24] <Kaleo> om26er, silo 15 is now ready with new packages including the tentative fix
[18:24] <om26er> Kaleo, I already picked it from the ppa, seems to fix the issue I reported
[18:24] <Kaleo> om26er, great
[18:24] <Kaleo> om26er, :)
[18:35] <robru> bfiller: thanks. I think the new commits are just ap tests, so just give it a quick smoke test, shouldn't need a full qa run
[18:35] <bfiller> robru: ack
[18:35] <popey> om26er: I've uploaded a new click for calculator to http://people.canonical.com/~alan/calculator/com.ubuntu.calculator_2.0.155_all.click - any chance you could install it and give me a +1 that the icon is fixed?
[18:36] <om26er> popey, right now I am testing camera-app fix, will get back to that in a bit
[18:36] <popey> om26er: ok, I've added the link to the card, and will move it as a reminder
[18:36] <popey> om26er: no I won't, I don't have access to
[18:57] <bfiller> robru: silo 7 is good to go
[18:57] <robru> bfiller: great thanks
[19:02] <robru> lool: looks like your u-t-m conflicts with an upload ogra did direct to distro, can you coordinate with him?
[19:25] <om26er> popey, icon looks good now
[19:25] <popey> thanks om26er
[19:26] <popey> sil2100: when are you planning to rebuild the image?
[19:26] <popey> om26er: shortly I'll have a reminders click for you which fixes the issue you had with text disappearing.
[19:27] <om26er> popey, sure.
[20:07] <popey> pmcgowan: we've had the *new* calculator app approved by QA. Am I okay to upload to the store?
[20:07] <popey> pmcgowan: It looks quite different from the existing calculator.
[20:08] <popey> pmcgowan: like this.. http://people.canonical.com/~alan/screenshots/device-2015-04-03-135433.png
[20:10] <pmcgowan> what are the left arrow and checkmark for
[20:10] <pmcgowan> popey,
[20:10] <popey> backspace and square root
[20:11] <pmcgowan> what happened to the clear button
[20:11] <popey> long press on backspace
[20:11] <pmcgowan> guess thats backspace
[20:11] <pmcgowan> ok
[20:11] <popey> new design from design team
[20:11] <pmcgowan> looks nicer
[20:11] <popey> ya, it is.
[20:11] <popey> less blue :)
[20:11] <pmcgowan> too much white though
[20:11] <popey> http://people.canonical.com/~alan/calculator/com.ubuntu.calculator_2.0.155_all.click
[20:11] <popey> if you want to play
[20:12] <pmcgowan> it has a bottom edge it seems
[20:12] <pmcgowan> maybe we should run it by joe
[20:12] <popey> yes
[20:12] <popey> want me to mail him?
[20:12] <pmcgowan> yes please
[20:13] <popey> It would be unfortunate for him to bounce it given we've been through this with design.
[20:15] <pmcgowan> popey, I am sure he will approve but feel better asking
[20:15] <popey> ok
[20:16] <pmcgowan> in case design never shared
[20:16] <popey> will mail now
[20:27] <robru> wow, two free silos, I think that's a record high for this week. anybody around to use one?
[20:28] <jgdx> bfiller, good test on silo 6.
[20:29] <bfiller> jgdx: great, thanks
[20:29] <popey> om26er: added a new reminders click which fixes the issue you found, if you could re-test that and let me know that would be _awesome_
[20:29] <jgdx> bfiller, should be noted that I saw 14GB, which is not 16GB, but far from ~2GB.
[20:32] <pmcgowan> popey, sounds like joe is +1
[20:34] <popey> excellent
[20:34] <popey> pmcgowan: do you know when we plan to spin a new image?
[20:34] <popey> (not entirely related to the upload)
[20:35] <pmcgowan> popey, any min, as soon as oxide is built
[20:35] <popey> ok
[21:22] <sil2100> I see oxide armhf still building
[21:23] <sil2100> Will probably take 2 more hours
[21:23] <sil2100> cwayne_: did you publish the new custom? :)
[21:26] <cwayne_> sil2100, yep :)
[22:30] <alesage> sil2100, would you ping me and/or ToyKeeper when the new oxide is available?
[22:30] <ToyKeeper> Yes, please.  :)
[22:30] <ToyKeeper> I get distracted too easily to poll for updates.
[22:53] <sil2100> Looking
[22:53] <sil2100> It's almost done
[22:53] <sil2100> The armhf binaries are still pending publication
[22:54] <sil2100> Once that's done, I'll copy them over to a silo PPA and try to publish
[22:57] <alesage> ok thx sil2100
[22:58] <sil2100> brb in around ~20 mins, it should be available by then I suppose
[22:58] <alesage> sil2100, ack thx
[23:27] <sil2100> Ok, packages copied to the silo PPA
[23:27] <sil2100> Now a watch only build, publish, wait for migration and I kick a new image
[23:27] <sil2100> pmcgowan: ^
[23:29] <sil2100> It's late here, but I'll be around to do all those
[23:36] <sil2100> The train's taking its sweet time
[23:38] <ToyKeeper> sil2100: Is anything needed for rtm-000 aside from the silo's PPA?  (rtm krillin 267 + ppa)
[23:39] <ToyKeeper> Er, rtm krillin 268 it seems?
[23:40] <sil2100> ToyKeeper: no :)
[23:41] <sil2100> ToyKeeper: but as per what me and jibel agreed - no need to sign-off the silo itself, I'll publish it straight away and then oxide will be tested in the new image
[23:41] <sil2100> ToyKeeper: what you could do in the meantime I guess is checking if it's not badly broken
[23:41] <sil2100> Like, install silo 000 and see if browser works
[23:41] <sil2100> Not sure if it makes sense to test more, I'll publish it instantly
[23:42] <ToyKeeper> sil2100: Okay, fair enough.  Do you know if the fix for bug 1442156 (today scope, location) will be in that image too?
[23:42] <sil2100> ToyKeeper: from what I know it's already published, cwayne_ included those in the custom tarball that has been uploaded
[23:43] <ToyKeeper> Okay, so that was in 268, and the oxide fix will be in 269?
[23:43] <ToyKeeper> I just want to make sure I'm testing the right bits.
[23:44] <cwayne_> righto, i've pushed
[23:45] <sil2100> ToyKeeper: yes :)
[23:45] <sil2100> Ok, oxide published, let's wait for it to migrate
[23:45] <sil2100> I'll kick a new build then, imgbot will be your guide
[23:55] <sil2100> It should migrate with the next run
[23:58] <sil2100> Ok, it's in now