[00:43] <robru> veebers: oh hey, what's up?
[00:43] <robru> he says, 2 hours later
[00:44] <veebers> robru: heh, I'm sure you're supposed to be off anyway right? So to follow up me asking about getting the autopilot in the spreadsheet landed, I have an email from Pat stating it's all cool to do so. Should I fwd to you so we can get this done?
[00:46] <robru> veebers: yeah sure. 5PM sunday here, but it's easy for me to click publish if you're ready to go ;-)
[00:47] <veebers> robru: yep, I ran the testing etc. and it's all good
[00:47] <robru> veebers: needs QA though
[00:47] <veebers> robru: have fwd the email
[00:48] <veebers> robru: surely that's me though right? :-)
[00:49] <robru> veebers: are you on the QA team? (honest question). typically for all landings in RTM we'd have the "upstream lander" (you) propose a landing, then QA (ToyKeeper or davmor2 among others) would verify that the silo doesn't make the phone explode, then I can publish it
[00:50] <veebers> robru: heh yes I am (QA Projects team). Autopilot is a little bit odd as it's not on the image, but used to test the image.
[00:50] <robru> veebers: why does it need to be in RTM if it's not in the image?
[00:50] <veebers> In the past we've normally done the gatekeeper job, presented a report on the runs and then approved or removed from there. I believe ToyKeeper stated that I just needed a managers sign off in this case.
[00:51] <robru> veebers: ToyKeeper is my go-to QA person so if she says it's ok then I'll allow it ;-)
[00:51] <veebers> robru: it's needed so that when the automated testing is done on it the right version is available (i.e. has features we're using in the sanity testing)
[00:51] <veebers> robru: I have no problem if you would like ToyKeeper to weigh in on this :-)
[00:52] <robru> veebers: I think she's NZ as well so maybe she's even around right now...
[00:52] <veebers> robru: heh, she doesn't live in NZ but seems to keep the hours (I'm not even sure she sleeps) :-)
[00:53] <robru> veebers: alright well, if I'm interpreting http://pastebin.ubuntu.com/9753224/ correctly it means there's no regressions caused by this landing? and I have no reason not to trust you, so if you say that in the past ToyKeeper gave you a blanket approval, and you got pat's approval, I guess I'll just publish it.
[00:54] <veebers> robru: right, that pastebin shows that I ran the smoke dash a couple of times and no new regressions popped up (failures were do to tests/apps not autopilot etc.)
[00:54] <robru> veebers: alright, I know you've been pushing for this for a while, I'm happy to just land it then.
[00:55] <veebers> robru: no worries, its something that needs to happen correctly :-) Awesome thanks
[01:50] <robru> veebers: cheers ^ ;-)
[01:53] <veebers> robru: ah, I didn't do anything ;-) Thank you for sorting that out
[01:54] <robru> veebers: you're welcome! (does 'cheers' mean your welcome? I meant it more along the lines of "you're welcome". heh)
[01:55] <veebers> robru: heh, cheers is used as in 'Thank you' :-) I see now. Cheers robru ;-)
[01:55] <robru> veebers: I'm learnding ;-)
[01:58] <thomi> robru: FWIW, I use "cheers" to mean many things, including "thanks", "you're welcome", "time to get another drink", and "can you take the dog for a walk please, only don't forget his collar, I think I left it on top of the fridge"
[01:58] <robru> thomi: oooh that's a tricky one. I've never heard anybody say it in Canada unless they were obviously british / australian / nz tourists.
[01:59] <thomi> heh
[02:10] <imgbot> [03:10] <imgbot> [03:20] <imgbot> [03:20] <imgbot> [04:15] <imgbot> [04:15] <imgbot> [07:36] <abeato> trainguards, line 62 ready for a silo
[08:12] <pstolowski> jibel, good morning! can we give rtm silo 11 (row #29) a higher priority, we have another important fix in the queue for unity-scopes-api (row #63)?
[08:16] <pstolowski> qa ^
[08:18] <jibel> pstolowski, good morning. looking.
[08:25] <brendand> pstolowski, it contains two fixes that have not been approved
[08:25] <brendand> https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1398813
[08:25] <brendand> https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1401860
[08:27] <pstolowski> dbarth, marcustomlinson, ^
[08:29] <marcustomlinson> brendand: yeah, I guess we should technically mark those as duplicates of #1380914
[08:30] <marcustomlinson> brendand: they are needed to solve the issues described in that bug's description
[08:31] <brendand> marcustomlinson, or get them milestoned
[08:32] <brendand> marcustomlinson, the fact they are needed to fix a milestoned bug will work in their favour
[08:32] <marcustomlinson> brendand: see, the thing is, removing the splashscreen from online-accounts causes that seemingly frozen UI bug.
[08:46] <dbarth> pstolowski: uh, why aren't those approved
[08:47] <dbarth> ?
[08:47] <dbarth> brendand: ah, but check the first one is a duplicate of an approved bug itself
[08:47] <dbarth> ie, https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1380914
[08:47] <dbarth> that explains one
[08:48] <brendand> dbarth, right - marcustomlinson just made that change
[08:48] <dbarth> the second one, is linked but we could put it on the product team radar real quick this morning
[08:49] <marcustomlinson> brendand, dbarth: we just need this one approved: https://bugs.launchpad.net/ubuntu-rtm/+source/unity-scopes-shell/+bug/1401860
[08:49] <dbarth> brendand: can you hold the silo for a few hours?
[08:49] <marcustomlinson> dbarth: that bug is caused as a result of the splash screen not appearing now
[08:49] <marcustomlinson> dbarth: could you get that one milestoned for us?
[08:50] <dbarth> marcustomlinson: oh, a new bug?
[08:50] <dbarth> yes, sure
[08:50] <brendand> dbarth, yes
[08:50] <marcustomlinson> dbarth: 1401860
[08:50] <dbarth> ah right, but fixed by the silo !
[08:51]  * dbarth was starting to think he is getting crazy
[08:51] <marcustomlinson> dbarth: yes thats fixed in the silo too.
[08:51] <dbarth> i did that test several times, so that's why i was surprised
[08:51] <marcustomlinson> :)
[09:39] <michi> ci-help: I need some help with Jenkins.
[09:39] <michi> Basically, a whole bunch of tests have started suddenly failing for us, both for CI in the build silos.
[09:40] <michi> The symptoms are consistent with either terribly slow machines, or possibly with a change in one of the libs we depend on. This started happening sometime over the weekend, possibly as early as Friday.
[09:40] <michi> Has anything changed in the Jenkins set-up?
[09:41] <michi> We are definitely seeing the problem for Vivid. Not totally sure about RTM right now.
[10:38] <oSoMoN> trainguards: can I please have a silo for line 63 ?
[10:38] <sil2100> oSoMoN: o/
[10:43] <oSoMoN> thanks sil2100
[11:05] <dbarth> hey trainguards, can you help me land silo 007 (vivid) ?
[11:09] <sil2100> dbarth: looking!
[11:12] <sil2100> dbarth: is it ready already? It's still saying it's building
[11:12] <sil2100> Ah, build-dep-wait
[11:12] <dbarth> sil2100: that's the dep wait
[11:12] <dbarth> right
[11:12] <dbarth> we were waiting for -proposed to be purged of the old package
[11:12] <dbarth> sil2100: and i confirmed with Colin last Friday that it was now good to go
[11:13] <sil2100> hmm
[11:13] <sil2100> Ok, let me try publishing, but the situation is a bit strange
[11:14] <sil2100> I thought the powerpc-like packages have been removed from the archive
[11:14] <sil2100> Well, let me publish anyway, we can see if it gets blocked in -proposed or not
[11:14] <sil2100> :)
[11:14] <dbarth> ok
[11:15] <dbarth> i'll stay around as i need to prep the SRU now
[11:20] <sil2100> geh
[11:21] <sil2100> dbarth: so, looking at silo 007's unity-chromium-extension I really don't like the changelog
[11:22] <sil2100> dbarth: I mean, I see that in the merge you have directly modified debian/changelog, but since the added entry had 'utopic' instead of UNRELEASED, it treated it as something already released
[11:22] <sil2100> So the top-most version now only has "* New rebuild forced"
[11:23] <dbarth> sil2100: uh
[11:23] <dbarth> sil2100: how can we fix that?
[11:23] <cjwatson> I think it was probably Building before I removed those binaries, maybe
[11:23] <cjwatson> But you could check against the publication history
[11:24] <sil2100> dbarth: we would have to rebuild and change the branch, but let me think if how it is there is good anyway
[11:25] <dbarth> let me know if i need to update the branch or do something special
[11:27] <cjwatson> Uh, hm, maybe my removal didn't stick
[11:27] <cjwatson>  unity-chromium-extension | 3.2.0+14.10.20140626-0ubuntu1 | vivid/universe  | source, amd64, arm64, armhf, i386, powerpc, ppc64el
[11:28] <cjwatson> I guess when p-m copied it from -proposed it copied all the old binaries again
[11:28] <sil2100> cjwatson: yeah, that's what I meant by that the situation looked strange, since LP still had the binaries - strange
[11:28] <cjwatson> let me fix that
[11:28] <sil2100> cjwatson: thanks! :)
[11:28] <cjwatson> done (leave it until rmadison agrees, though)
[11:30] <sil2100> dbarth: ok, so I would say it like this - if some core dev +1's the packages, I'll publish
[11:31] <sil2100> Since I'm not sure if such a changelog is super good
[11:32] <sil2100> cjwatson: maybe you would have time to check 2 packaging diffs? ;) Since I need councelling, not sure if the changelog maddness is acceptable there
[11:32] <sil2100> (and one of the packages is in main)
[11:37] <cjwatson> libunity-webapps seems fine, but I think unity-chromium-extension should be rebuilt with a fixed changelog.  The changelog is an important part of the documentation of any delivery.
[11:37] <sil2100> ogra_, cjwatson: if anyone of you could: https://ci-train.ubuntu.com/job/ubuntu-landing-007-2-publish/lastSuccessfulBuild/artifact/packaging_changes_unity-chromium-extension_3.2.0+15.04.20141217-0ubuntu1.diff https://ci-train.ubuntu.com/job/ubuntu-landing-007-2-publish/lastSuccessfulBuild/artifact/packaging_changes_libunity-webapps_2.5.0~+15.04.20141217.2-0ubuntu1.diff <- the changelogs are fishy
[11:38] <cjwatson> There's some junk in the libunity-webapps one, but it's at least informative.  I don't particularly have a problem there.
[11:39] <cjwatson> But unity-chromium-extension's one is utterly uninformative.
[11:41] <sil2100> Yeah
[11:45] <sil2100> cjwatson: so, the debian/changelog does have an entry below the one in the diff that's a proper description, but that one is actually sparse as well
[11:45] <dbarth> sil2100, cjwatson: it should really say "+  * Support native messaging. (with Alberto Mardegan)", which was in the staging2 branch
[11:46] <sil2100> dbarth: so, actually https://code.launchpad.net/~webapps/unity-chromium-extension/staging2/+merge/244966 has debian/changelog modified and this should be set to UNRELEASED
[11:46] <sil2100> Then CI Train would pick it up and create the entry properly
[11:48] <sil2100> dbarth: ah, and please approve merges from silo 14
[11:56] <dbarth> brendand: victor marked the bug ok for this week, hope this let's you land more safely now (bug 1401860)
[11:56] <dbarth> marcustomlinson: ^^
[11:59] <sil2100> pstolowski: hmm
[12:00] <sil2100> pstolowski: in unity-scopes-api I see that you modify some existing symbols
[12:00] <sil2100> Won't that cause breakage?
[12:01] <pstolowski> sil2100, hey, what are you looking at?
[12:03] <pstolowski> sil2100, add-logging branch?
[12:04] <sil2100> pstolowski: silo 15, https://ci-train.ubuntu.com/job/ubuntu-landing-015-2-publish/lastSuccessfulBuild/artifact/packaging_changes_unity-scopes-api_0.6.11+15.04.20150119-0ubuntu1.diff
[12:05] <pstolowski> sil2100, this is fine, these are all symbols from unity::scopes::internal namespace
[12:05] <brendand> dbarth, thanks
[12:06] <pstolowski> sil2100, no one links against them, except from us (binaries that we ship together with same package)
[12:07] <pstolowski> sil2100, and the only reason ::internal namespace is exposed at all in symbols is afair because our binaries (scoperegistry, smartscopesproxy) need them
[12:07] <sil2100> ACK
[12:07] <sil2100> pstolowski: thanks!
[12:07] <pstolowski> yw
[12:08] <cjwatson> Oh, nobody's mentioned it here.  FYI, there's been a power issue in one datacentre which among other things means that all the non-virtualised armhf builders are currently down.
[12:09] <cjwatson> Hopefully will be back soon ...
[12:09] <sil2100> ogra_: if you have a moment, could you sign off https://ci-train.ubuntu.com/job/ubuntu-landing-013-2-publish/lastSuccessfulBuild/artifact/packaging_changes_dbus-test-runner_15.04.0+15.04.20150116-0ubuntu1.diff ?
[12:09] <sil2100> cjwatson: uhh
[12:09] <sil2100> Ok, good to know
[12:29] <jibel> Elleo, I'm verifying silo 2, and 2 autopilot tests fail: test_emoji_input and test_emoji_deletion http://paste.ubuntu.com/9784632/
[12:29] <jibel> Elleo, it's on krillin #202, any idea what it is?
[12:30] <Elleo> jibel: is this on RTM?
[12:31] <jibel> Elleo, yes
[12:31] <Elleo> jibel: the emoji package might not be installed (they haven't been added to the RTM meta-package yet)
[12:31] <Elleo> jibel: so you might need to manually apt-get install ubuntu-keyboard-emoji before running the autopilot tests
[12:32] <jibel> Elleo, shouldn't it be a dependency of ubuntu-keyboard then?
[12:33] <Elleo> jibel: it should possible be a dependency of the autopilot package I guess, but not really of the keyboard (since there might be cases where people don't want an emoji keyboard installed)
[12:34] <Elleo> jibel: I can prepare an MR that adds it to the ubuntu-keyboard-autopilot package depends if you think that's best?
[12:35] <jibel> Elleo, yes, update the packages in the silo with a fix, and I'll continue testing when it's done. Thanks.
[12:35] <Elleo> jibel: okay, thanks
[13:01] <cjwatson> ARM builders are back.
[13:02] <alecu> hi trainguards! may I ask for an rtm silo for row 48 in the spreadsheet?
[13:05] <sil2100> alecu: sure o/
[13:05] <sil2100> cjwatson: \o/
[13:08] <alecu> thanks!
[14:21] <sil2100> Chipaca: hey! We need your merges approved before release
[14:21] <Chipaca> sil2100: oh, qa approved?
[14:21] <sil2100> Chipaca: https://code.launchpad.net/~chipaca/ubuntu-push/fix-1376282-for-rtm/+merge/246740 https://code.launchpad.net/~chipaca/ubuntu-push/fix-1380662-for-rtm/+merge/246754
[14:21] <sil2100> Yeah, now the merges need top-approval ;)
[14:22] <Chipaca> sil2100: thanks for the heads up; i'll get somebody else to top-approve those and get back to you
[14:49]  * sil2100 goes back to his bed
[14:52] <om26er_> camako, Hi! do you have the results for unity8 and webbrowser autopilot tests that you ran for Mir silo 3 ?
[15:00] <oSoMoN> trainguards: can silo 16 be published please?
[15:01] <sil2100> o/
[15:02] <sil2100> oSoMoN: hmm, I see pstolowski commented on this silo, but I don't understand the rationale there
[15:02] <sil2100> oSoMoN: pstolowski left: "pstolowski 19/01: needs to wait for rtm silo 11 (OA fix) to land"
[15:03] <sil2100> Why does it need to wait for an RTM silo if it's a vivid silo
[15:03] <sil2100> pstolowski: ^
[15:03] <oSoMoN> sil2100, I’m not seeing the comment
[15:03] <sil2100> oSoMoN: it's on the dashboard
[15:04] <sil2100> oSoMoN: and the spreadsheet
[15:04] <sil2100> In the comments field
[15:05] <oSoMoN> sil2100, not seeing it in the spreadsheet, but that looks like an error to me
[15:06] <sil2100> oSoMoN: huh, even after a refresh? Since it's not possible that I'm seeing a broken state in 2 different places - the dashboard polls the spreadsheet directly, so it cannot be cached somewhere locally
[15:06] <sil2100> Anyway, ok
[15:06] <sil2100> The comment doesn't make much sense anyway
[15:08] <sil2100> ogra_: heey! Need a packaging ACK https://ci-train.ubuntu.com/job/ubuntu-landing-016-2-publish/51/artifact/packaging_changes_webbrowser-app_0.23+15.04.20150119-0ubuntu1.diff <- looks good
[15:11] <oSoMoN> sil2100, I hit refresh and now the spreasheet won’t load at all :/
[15:11] <oSoMoN> sil2100, but I see the comment in the dashboard, and I don’t understand it
[15:11] <oSoMoN> sil2100, it looks like a mistake to me, probably commented on the wrong line
[15:11] <sil2100> Yeah, I think so too
[15:15] <pstolowski> sil2100, that was mostly comment to myself to make sure i build after that other fix lands, cause both silos were scopes-api
[15:17] <ogra_> sil2100,  ACK
[15:18] <pstolowski> sil2100, ouch, wait, that comment is in wrong row
[15:18] <sil2100> pstolowski: this silo didn't have scopes-api ;)
[15:18] <pstolowski> sil2100, now i undesrand the confusion
[15:19] <pstolowski> sil2100, so, either google messed something up, or somebody removed my landing request :/
[15:20] <pstolowski> sil2100, or i messed something
[15:22] <pstolowski> sil2100, fixed. re-added my original request in #66
[15:24] <sil2100> Ok!
[15:28] <vila> ogra_: I'm searching for the canonical place where the packages used in a phone image are defined, is it http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/20150112/vivid-preinstalled-touch-armhf.manifest ? (context being boot testing for -proposed migration)
[15:40] <sil2100> pstolowski: another silo with scopes-api? ;)
[15:40] <sil2100> pstolowski: re: 65
[15:41] <ogra_> vila, lp:~ubuntu-core-dev/ubuntu-seeds/ubuntu-touch.vivid/
[15:41] <pstolowski> sil2100, yes, but this is vivid
[15:42] <vila> ogra_: and there 'touch' ?
[15:42] <sil2100> pstolowski: right but remember you have another silo with -scopes-api (21)
[15:43] <ogra_> vila, right or the sdk ones
[15:43] <ogra_> (most libs go into the sdk ... which is essentially our framework, touch is the "desktop apps" of teh phone)
[15:44] <pstolowski> sil2100, yes, 21 is for experimenting with some abi changes, we aren't going to land anything from it
[15:44] <pstolowski> sil2100, we should soon be able to give 21 back
[15:46] <vila> ogra_: hmm, but those are the high level packages and used as input to build the image right ? I was after 'dpkg -l' on the phone which is the extensive list (but slightly harder to get: you need a phone running the right image ;)
[15:47] <ogra_> vila, well, the manifest is the ooutput, the seed is where the packages are defined ... you asked where we define them :)
[15:47] <ogra_> so if you just want the list, yeah, go with the manifest
[15:47] <mandel> sergiusens, have you been able to reproduce bug 1387514
[15:48] <vila> ogra_: sure, sorry, newbie question ;) And the manifest is http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/pending/vivid-preinstalled-touch-armhf.manifest right ?
[15:48] <mandel> sergiusens, I have been trying to reproduce it and so far I have had no luck
[15:48] <ogra_> vila, right, thats the latest
[15:49] <vila> ogra_: perfect, so seed or manifest, got that. So seed is 'sdk' + 'touch' or should 'sdk-*' also be considered ?
[15:51] <sergiusens> mandel let me open the link
[15:52] <sergiusens> mandel: so you don't remove the sdcard after clicking that safely remove and try to format, right?
[15:52] <mandel> sergiusens, no, I dont
[15:52] <sergiusens> mandel: look at comment 3 please
[15:52] <sergiusens> mandel: you just need to grey out the format button
[15:53] <sergiusens> mandel: simplest bug fix ever :-P
[15:53] <mandel> sergiusens, the bug there states that it loads the formatting dialog, which is not the case
[15:54] <mandel> sergiusens, I can reproduce the safely remove and then format
[15:54] <mandel> sergiusens, but if I do, safely remove, the safetly remove buttons is gray out yet the format button is not
[15:55] <mandel> sergiusens, so, I can do a format while it was safetly removed (I don't know if I'm making any sense)
[15:56] <oSoMoN> trainguards: can I please get a silo for line 68 ?
[16:06] <sergiusens> mandel: ah, right
[16:13] <sil2100> oSoMoN: sure
[16:14] <dbarth> trainguards: i approved the 2 branches in silo 014, it's good to go into vivid
[16:16] <sil2100> dbarth: excellent, let me re-publish then
[16:21] <sil2100> ogra_, jibel, robru, popey, davmor2, brendand: let me cancel today's meeting, I'm trying to rest today and besides we all know what to do anyway
[16:21] <ogra_> ++
[16:22] <davmor2> sil2100: but then we can't pick on you, damn it ;)  rest up dude and get better
[16:24] <jibel> sil2100, OK, get some rest and get well soon!
[16:25] <popey> sil2100: ok
[16:26] <dbarth> sil2100: ty
[16:27] <dbarth> sil2100: oh and is 007 ok now? do you need me for a changelog update?
[16:27] <dbarth> ie update it to says UNRELEASED, right?
[16:28] <sil2100> dbarth: I would say it would be best to change it to UNRELEASED and rebuild, as even a core-dev was not happy with this changelog ;)
[16:32] <dbarth> sil2100: :) ok, i'll do that now
[16:37] <sil2100> Ok everyone, robru should be up in ~30 minutes
[16:38] <brendand> pstolowski, https://wiki.ubuntu.com/Process/Merges/TestPlan/scopes says that remote scopes should *not* be visible in the manage dash view if there is no connectivity. is that right?
[16:38] <sil2100> o/
[16:38] <brendand> pstolowski, i recall there might have been a fix for that recently
[16:39] <Chipaca> sil2100: ready to go---noooooo!
[16:39] <Chipaca> i guess he was ready to go too :)
[16:40] <pstolowski> brendand, no, this is not right! thanks for catching
[16:40] <brendand> pstolowski, so the test plan should be updated?
[16:43] <pstolowski> brendand, yes. i'll take care of it
[18:34] <robru> jibel: sergiusens: hey I'm trying to use phablet-screenshot but it isn't working, can you help me troubleshoot?
[18:41] <jhodapp> robru, can I get a silo for line #69 please?
[18:42] <jhodapp> robru, crap, pasted the wrong thing...one sec
[18:42] <robru> k
[18:43] <jhodapp> robru, ok now it's readty
[18:44] <robru> jhodapp: ok you got silo 1, mind the conflict with media-hub in silo 11
[18:44] <jhodapp> robru, oh thanks, didn't realize that yet
[18:44] <jhodapp> robru, I'll re-pull
[18:44] <robru> jhodapp: what do you mean re-pull? might you consider adding your fix to silo 11?
[18:45] <jhodapp> robru, didn't merge with trunk
[18:45] <robru> jhodapp: ok but silo 11 isn't published yet so it's not in trunk ;-)
[18:45] <jhodapp> robru, oh silo 11, sorry
[18:45] <jhodapp> robru, yes I'll be merging before that
[18:45] <jhodapp> robru, I'm working with tvoss on that other silo still
[18:46] <robru> jhodapp: ok
[18:49] <robru> Ursinha: slangasek: I vote we cancel the meeting since sil is off sick. and I don't think anything has changed since last week.
[18:49] <slangasek> robru: bank holiday here, I wasn't going to come anyway :)
[18:50] <robru> slangasek: and yet you're on IRC... ;-)
[18:50] <Ursinha> robru: fine by me :)
[18:50] <slangasek> big difference between "on IRC" and "working"
[18:50] <robru> slangasek: nahhhhh ;-)
[21:53] <jhodapp> robru, can you reconfigure silo 1 please (vivid)
[22:23] <robru> jhodapp: oops, sorry for the delay. Done, just be aware you now have two packages conflicting with silo 11
[23:24] <jhodapp> thanks robru
[23:24] <robru> jhodapp: you're welcome!