[02:40] <robru> bfiller: that request says wily but then says overlay ppa, that doesn't make sense. Do you want wily or vivid or both?
[02:41] <bfiller> robru: where does it say overlay ppa? I think we just need for wily for now
[02:43] <robru> bfiller: it's in column L
[02:44] <bfiller> robru: fixed
[02:44] <robru> bfiller: got you silo 21, thanks
[02:44] <bfiller> thanks robru
[02:44] <robru> bfiller: you're welcome
[06:15] <Mirv> tvoss: wouldn't you want dual landing silo btw to land also to wily?
[06:16] <Mirv> tvoss: ok :)
[06:16] <tvoss> Mirv, yup, sorry :)
[06:19] <tvoss> Mirv, I found an issue where a package from the silo is older than the package in the overlay ppa
[06:19] <tvoss> Mirv, is that a known hiccup and do we have instructions for pinning available?
[06:19] <tvoss> Mirv, see http://pastebin.ubuntu.com/11405991/
[06:22] <Mirv> tvoss: the pinning is a known issue. QA knows how to fix it so testing is good. if you want to use the 'citrain' tool for upgrading, upgrade to the wily version by dpkg -i:ng phablet-tools-citrain .deb from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-020/+build/7443600
[06:22] <Mirv> tvoss: otherwise it's been discussed at https://lists.launchpad.net/ubuntu-phone/msg12749.html but this remind me that the phablet-tools upgrade should probably be put to the overlay PPA so that more people have the updated citrain upgrade tool.
[06:23] <tvoss> Mirv, yup
[07:28] <pstolowski> trainguards hello, can i get a silo for line #35?
[07:32] <Mirv> pstolowski: thanks! and yes.
[08:07] <jibel> sil2100, morning, can you build an rc-proposed image to grab silo 20 that landed last night? it fixes bug 1457129
[08:17] <sil2100> jibel: sure, on it
[08:17] <sil2100> jibel: did the location silo land?
[08:18] <sil2100> hm, doesn't look like it
[08:18] <ogra_> well, see the other channel
[08:28] <sil2100> ogra_: is imgbot out sick today?
[08:28] <ogra_> oops, i rebooted the server, forgot to start it again ... one sec
[08:28] <sil2100> It missed my image build... ;)
[08:29] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/vivid/20150527.changes is the last one available
[08:30] <ogra_> (i still havent had time to get the new mapping right for vivid)
[08:30] <ogra_> imgbot, stunt
[08:30]  * imgbot rolls on its back and purrs
[08:30] <ogra_> there he is
[08:44] <jibel> sil2100, location didn't land. location-service didn't start with the silo, and accuracy is still really ba
[08:44] <jibel> d
[08:54] <pstolowski> trainguards, hey, my silo 33 (line #29) can be freed
[08:55] <sil2100> pstolowski: oh, not needed?
[08:55] <pstolowski> sil2100, same stuff is in silo 29 :/
[08:55] <sil2100> huh
[08:56] <pstolowski> yeah, there was some messup and reconfigs between wily and vivid, ended up with two silos at the end
[11:42] <pmcgowan> sil2100, seb128 just emailed, I would fix those translation issues, we have time
[11:53] <Mirv> sil2100: jibel: I prepared a phablet-tools overlay sync for people on desktop vivid + overlay PPA to make the citrain functional for more people. if you think it's ok to land without separate QA testing (I smoke-tested citrain tool + starting a test with phablet-test-run) I could land it. diff is https://launchpadlibrarian.net/207675883/phablet-tools_1.1%2B15.04.20150330-0ubuntu1_1.1%2B15.04.20150519-0ubuntu1.diff.gz
[11:54] <Mirv> so that's what's in wily
[11:54] <Mirv> I've kept giving the wily .deb for people asking, but that'd reach more people
[12:09] <pmcgowan> jibel, silo 27 working for me
[12:09] <pmcgowan> fwiw
[12:10] <sil2100> pmcgowan: ok, aren't we a bit under deadline pressure though? ;)
[12:10] <sil2100> I thought that, you know, today is teh end
[12:11] <sil2100> Mirv: sounds okayish to me I suppose, since the phablet-tools aren't installed on our phones
[12:12] <pmcgowan> sil2100, after discussion with meizu they prefer we fix more issues rather than keep the date - so we can fit a couple more in
[12:12] <sil2100> \o/
[12:12] <pmcgowan> sil2100, still need to be strict about what issues
[12:12] <sil2100> True
[12:12] <sil2100> Ok, excellent news anyway
[12:15] <Mirv> sil2100: ack, I'll wait if ji_bel has an opinion but it's not on images and only affects two of the auxiliary tools
[12:15] <popey> pmcgowan: is https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1425172 on your radar for a fix soon?
[12:15] <pmcgowan> popey, yeah thats a bad one
[12:16] <popey> i just marked a bug I filed a year ago as a dupe of it, didn't realise it still happened.
[12:17] <pmcgowan> popey, probably comes and goes
[12:17] <popey> also, I rarely leave the house which helps avoid the bug ㋛
[12:29] <jibel> pmcgowan, yeah I confirmed tvoss's fix works quickly earlier.
[12:29] <jgdx> trainguards, any idea how I build silo 36?
[12:30] <jgdx> I used force and I specified that I only wanted to build ubuntu-system-settings.
[12:30] <jibel> tvoss, ^ wrt silo 27 is it ready for QA ?
[12:31] <pmcgowan> jibel, should be yes, tvoss is afk right now
[12:32] <jibel> OK, I'll do the verification it is already installed on my device.
[12:33] <pmcgowan> seb128, can we get a silo for your fixes at https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1447516
[12:34] <seb128> pmcgowan, sure, I was waiting on a code review, but I'm pretty confident it's correct so I can put that in a silo now
[12:35] <pmcgowan> seb128, great, any other regressions that slipped in you know of
[12:35] <Mirv> jgdx: you're trying to land to vivid overlay based on trunk which has stuff that's only on wily. you should either agree to land trunk to vivid overlay or target a vivid overlay specific branch of u-s-s
[12:36] <Mirv> jgdx: so wily is at 20150527 while vivid overlay is at 20150514
[12:36] <seb128> pmcgowan, no, but I'm unsure how much user testing vivid gets, I wonder if I should switch my bq to that channel rather than the rtm-proposed one
[12:36] <seb128> pmcgowan, or do we plan to switch -proposed to vivid before it's rolled as a stable ota to users?
[12:37] <pmcgowan> seb128, there are at least several folks dog fooding it, I did not switch yet
[12:38] <seb128> pmcgowan, right, I'm sure it's getting some testing, not sure enough to be confident there is no important issues though...
[12:38] <seb128> pmcgowan, is there any reason we don't switch all testers/people on -proposed to vivid?
[12:38] <seb128> since that's the candidate for the next ota
[12:38] <seb128> that would give extra testing on it
[12:39] <pmcgowan> seb128, I suppose we should really
[12:40] <pmcgowan> seb128, I think we need an image server fix first
[12:40] <ogra_> sil2100, oh, seb128's words above remind me ... do we have an update plan for people using rtm-proposed currently ?
[12:41] <seb128> pmcgowan, rolling out the ota to customers before having it pushed to beta testers seems a bit backward, why did we do it this way? (I assume that people on -proposed = beta testers)
[12:41] <pmcgowan> ogra_, right they should go to the vivid proposed
[12:41] <Mirv> jgdx: if you don't want solve u-s-s situation (and you've just a test silo), I don't think there's a force option to override this check, but if you want you could push revision 1416 from http://bazaar.launchpad.net/~system-settings-touch/ubuntu-system-settings/trunk/changes to somewhere and target that with your test MP...
[12:41] <pmcgowan> seb128, you are right, we were just focused on arale factory image, and next step is updating krillins
[12:41] <pmcgowan> we should move proposed over now
[12:42] <seb128> +1 :-)
[12:42] <seb128> Mirv, jgdx, what u-s-s situation?
[12:42] <jgdx> Mirv, hm, okay, I have to think about it. Might do a stableoverlay specific one
[12:42] <ogra_> pmcgowan, indeed, i was wondering if we can automate that ...
[12:42] <ogra_> (thus my question)
[12:43] <Mirv> seb128: 20150527 being in wily only. do you plan to fork the branches for vivid overlay or sync the wily version to overlay after this OTA has shipped?
[12:43] <pmcgowan> ogra_, but as I understand it we need a fix from barry for the delta creation as there is some glicth right now
[12:43] <Mirv> seb128: jgdx is trying to target vivid overlay with a trunk MP which doesn't work since overlay is at 20150514
[12:43] <seb128> Mirv, we already branched and no we don't plan to sync (or at least unsure if we can, is vivid supposed to be "open gate" again?)
[12:44] <seb128> Mirv, jgdx, kenvandine created https://code.launchpad.net/~system-settings-touch/ubuntu-system-settings/15.04 for vivid-overlay
[12:44] <Mirv> jgdx: ^ ok then you should target the branch instead of wily, probably doing another landing eventually to the wily (trunk) too
[12:44] <seb128> we should target stable fix there
[12:44] <ogra_> pmcgowan, ah
[12:44] <seb128> and yeah, you need to land to trunk as well
[12:44] <jgdx> seb128, Mirv, okay, I'll land in Wily then backport?
[12:44] <pmcgowan> ogra_, https://bugs.launchpad.net/canonical-devices-system-image/+bug/1444347
[12:44] <seb128> jgdx, wfm,
[12:44] <jgdx> Mirv, thx
[12:44] <ogra_> ouch
[12:45] <Mirv> jgdx: that's a good option, no problem
[12:45] <jgdx> Mirv, that requires a reconfigure?
[12:47] <jgdx> landingprocess docs does not explicitly state whether or not to
[12:49] <Mirv> jgdx: yes it actually needs a removal of the silo and reassigning it (changing series). if that's ok, I can do it now
[12:50] <jgdx> Mirv, can you hold on until ken apparates?
[12:50] <sil2100> ogra_: rtm-proposed? You mean like 14.09-proposed?
[12:50] <Mirv> jgdx: sure, and sil2100 can help if I'm already away at that point
[12:50] <jgdx> Mirv, thanks
[12:50] <ogra_> sil2100, yeah
[12:50] <sil2100> ogra_: they're already on vivid since long if they use that
[12:51] <ogra_> sil2100, what most canonical employees run ;)
[12:51] <ogra_> oh ?
[12:51] <sil2100> Since 14.09-proposed is now a redirect to rc-proposed
[12:51] <sil2100> Since the reordering that slangasek made
[12:52] <ogra_> my "about" page says 14.10 ... image 277
[12:52] <pmcgowan> sil2100, I dont think so
[12:52] <sil2100> Well, just saying what's in system-image
[12:52] <sil2100> That's how it's configured
[12:53] <sil2100> Maybe the issue is that since it's a redirect and the image numbers of 14.09-proposed were pretty high, now it doesn't see any new OTAs since rc-proposed has lower versions
[12:53] <seb128> sil2100, same as others, being on 14.09-proposed gives me a 277 utopic-rtm based image
[12:53] <seb128> not a vivid one
[12:53] <pmcgowan> sil2100, right, which is good since we have that server bug I posted above
[12:54] <sil2100> Yeah, barry is on it
[12:54] <ogra_> well, we should tell people to switch then
[12:54] <sil2100> Anyway, the server config is set so that 14.09-proposed is now vivid based, maybe we'll need to fix something for it to work properly
[12:55] <ogra_> since that channel looks like a dead end now
[12:55] <ogra_> the versions you import will most likely always be lower than 277
[12:55] <sil2100> Since ubuntu-touch/ubuntu-rtm/14.09-proposed is "redirect": "ubuntu-touch/rc-proposed/bq-aquaris.en"
[12:55] <ogra_> (or the versions you redirect to)
[12:56] <sil2100> I need to check how updates are determined, probably as I mentioned, it doesn't provide an upgrade path since version numbers of rc-proposed are lower
[12:56] <sil2100> I'll poke barry and slangasek once they're around
[12:56] <ogra_> yeah
[12:57] <ogra_> if upgrade doesnt work we should just wipe the channel and ask people to switch over
[12:57] <ogra_> (if it evidently is bound to the version number)
[13:11] <seb128> sil2100, can you check that l66 is fine and assign a silo if it is?
[13:11] <sil2100> seb128: I just did :)
[13:11] <sil2100> Silo 32 for you
[13:11] <seb128> sil2100, great, thanks ... I was a bit unsure, since wily was behind on version, I just pocket copied the overlay ppa package to wily
[13:12] <sil2100> No worries, should be ok if you do the dual landing now
[13:13] <jgdx> kenvandine, silo 36 won't build. We need to either target vivid+overlay properly, or wily then backport. I'd like the latter.
[13:13] <kenvandine> jgdx, yes, it should be wily now
[13:13] <kenvandine> i'll reconfigure
[13:14] <kenvandine> oh bugger
[13:14] <jgdx> okay, so we'll backport?
[13:14] <jgdx> RTM all over again?
[13:14] <kenvandine> libqofono
[13:14] <kenvandine> yes
[13:17] <jibel> tvoss, mandel I verified silo 27, it's good to land. Part of the fix was in silo 5, what do you do with this silo?
[13:18] <tvoss> jibel, we will decide later
[13:18] <tvoss> jibel, so I just set 27 to tested, if you are happy with it, we can immediately land 27 and then tackle 5
[13:18] <jibel> ok
[13:21] <sil2100> \o/
[13:23] <sil2100> tvoss: is this one approved? https://code.launchpad.net/~thomas-voss/location-service/fix-1426307/+merge/260365
[13:23] <tvoss> sil2100, getting rsalveti to do so ;)
[13:24]  * tvoss hands beers and stuff to rsalveti
[13:24] <sil2100> ;)
[13:25] <davmor2> tvoss: you fool now his hands are full and he can't do anything :P
[13:29] <tvoss> davmor2, at least he cannot break anything
[13:32] <davmor2> tvoss: no that's my job :D
[13:32] <tvoss> davmor2, yeah, although you most often prove that they are indeed broken ;)
[13:32] <alecu> hi trainguards! may I ask you to reconfigure silo 22? when I try it says: "ubuntuone-credentials was not in the initial list of components for that silo"
[13:34] <sil2100> alecu: indeed, let me help you here
[13:34] <alecu> thanks!
[13:35] <mandel> jibel, when you say that part of the fix was in silo 05, what do you mean?
[13:36] <jibel> mandel, this MR was in silo 27 https://code.launchpad.net/~thomas-voss/location-service/fix-1426307/+merge/260365
[13:37] <mandel> jibel, yes, I know that, and you needed that guy + silo 05, is that what you mean
[13:37] <mandel> ???
[13:37] <jibel> mandel, nope, I mean what is silo 5 supposed to fix now?
[13:37] <mandel> jibel, issues with the location service in vivid after the wizard
[13:38] <mandel> jibel, ignore it, let me merge both silos in 1 and we take it for a spin, leaving silo 27 as it is
[13:38] <jibel> mandel, verification of 27 is done, and accuracy is fine, I'd rather land them separately.
[13:39] <jibel> tvoss, ^ what do you think?
[13:40] <tvoss> jibel, mandel I would vote for landing 27 as is
[13:40] <mandel> jibel, I just want to have a build with all changes to test them together, but if you want, I would land 27 and do a rebuilf of 5 then
[13:40] <tvoss> mandel, just remove my mp from 5, reconfigure and rebuild
[13:40] <tvoss> mandel, did you verify if we actually need the fixes from 5? seems like the trust store interaction works perfectly fine on vivid
[13:41] <mandel> tvoss, did it work after the wizard? 'cause it is then when we have the issues
[13:41] <mandel> tvoss, the issues is when the location service is restarted, then the trust store does not work
[13:41] <tvoss> mandel, I did a --bootstrap, so I think yes
[13:41] <tvoss> mandel, probably best to retest silo 5
[13:41] <mandel> tvoss, let me double check, if that is the case I'm happy to kill 5
[13:42] <mandel> tvoss, you read my mind, doing it now
[13:42] <tvoss> mandel, or better: retest without silo 5
[13:42] <mandel> tvoss, my idea was to --wipe, test and see the error ;)
[13:44] <tvoss> mandel, also https://code.launchpad.net/~thomas-voss/location-service/fix-1426307/+merge/260365 could use a review
[13:44] <tvoss> seems like my beers for rsalveti don't help
[13:44] <mandel> tvoss, on it
[13:48] <mandel> jibel, tvoss, an arale with --wipe in  without silo 5 after running the wizard does not get the trust store prompt and the location service cannot be used by the browser
[13:48] <mandel> jibel, tvoss nor osmtouch
[13:48] <mandel> jibel, could you double check that I'm not saying utter bullshit? I'll try again
[13:49] <tvoss> mandel, okay, so if that is the case, let's clean up silo 5
[13:49] <tvoss> mandel, you also merged one of my branches in there, which are probably not required right now, we can land it later
[13:49] <tvoss> mandel, best to keep this as clean as possible
[13:51] <mandel> tvoss, then let me create an mr just for the trust store fix and add it to silo 27
[13:52] <mandel> tvoss, to fix both issues in that silo and then move  to add the rest of the code later
[13:52] <tvoss> mandel, nope, let's land silo 27 now as is and clean up silo 5
[13:52] <tvoss> mandel, why overload the silo? we haveboth anyway and one of them needs rebuild no matter what
[13:52] <mandel> tvoss, jibel ok, lets land 27 asap
[13:53] <pmcgowan> tvoss, mandel I get a trust prompt in the browser
[13:53] <pmcgowan> with last image plus 27
[13:53] <tvoss> pmcgowan, after the wizard?
[13:53] <pmcgowan> tvoss, oh no
[13:53] <mandel> pmcgowan, one trust prompt or a location trust prompt?? and, after the wizard?
[13:53] <pmcgowan> not first boot
[13:53] <pmcgowan> if thats the issue nm
[13:53] <mandel> pmcgowan, we are talking about first boot
[13:54] <pmcgowan> ack
[13:54] <mandel> pmcgowan, yes, that is the issues, acceptance of the license and usage of the location service
[13:54] <mandel> pmcgowan, so are you in the loop, we get silo 27 I clean silo 5 and rebuild it
[13:54] <mandel> pmcgowan, sounds good?
[13:54] <seb128> pmcgowan, sil2100, addressbook translation fix built in the silo & tested locally here (works fine), I guess it should still be qa validated but looks good to me
[13:54] <sil2100> Excellent
[13:55] <pmcgowan> seb128, awesome  mark for qa jibel ^^
[13:55] <sil2100> tvoss: is the MR reviewed?
[13:55] <seb128> jibel, https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1447516
[13:55] <mandel> sil2100, if not I'll do it
[13:55] <seb128> jibel, the fix is in silo 32
[13:55] <tvoss> sil2100, nope, waiting for either mandel or rsalveti
[13:55] <mandel> sil2100, on it
[13:57] <mandel> sil2100, tvoss everything looks good to me, and it works. I have approved and top approved
[13:57] <sil2100> Yay, ok, publishing
[13:57] <tvoss> ack
[14:00] <sil2100> hmmm
[14:01] <sil2100> The train went a bit crazy here, let me just note down the silo number
[14:01]  * rsalveti reads
[14:01] <rsalveti> tvoss: sorry, was in a meeting
[14:01] <rsalveti> it seems mandel already covered it
[14:02] <mandel> rsalveti, yes, tl;dr we need both silos, one for accurancy the other one to ensure the trust store appears after the wizard (and also after possible crashes)
[14:02] <mandel> rsalveti, 27 has been approved, I clean 5 and do a rebuild
[14:03] <rsalveti> great
[14:04] <gQuigs> I'm trying to understand the jenkins breakage's on http://people.canonical.com/~ubuntu-archive/pending-sru.html
[14:04] <gQuigs> specifically around the apt package updates autopkgtest for apport 2.0.1-0ubuntu17.8: Test in progress (Jenkins: public, private) ,
[14:04] <gQuigs> autopkgtest for apport 2.14.1-0ubuntu3.10: Regression (Jenkins: public, private)  and more for trusty
[14:09] <kyrofa> cihelp: I sent a request last week for a new project (unity-scope-snappy) to get integrated with CI (build, tests, coverage, and autolanding) and haven't heard anything. I just wanted to check and make sure it got through?
[14:10] <Ursinha> gQuigs: I'll have a look
[14:10] <gQuigs> ty
[14:12] <gQuigs> in trusty the apt and gtk-3 failures (at least apport) seem to be identical..
[14:16] <sil2100> Uuuuh, I think I see a bug in the train :|
[14:16] <sil2100> Daaamn
[14:17] <sil2100> Grrr
[14:19] <kenvandine> looks like the settings build in silo 33 got canceled?
[14:31] <Ursinha> tvoss: you left before I could say that the autolanding problem was the one we were discussing
[14:38] <mandel> sil2100, can you sync what was landed in that silo 27 to vivid? I now it was landed in trunk and we need it in vivid to get it to the image
[14:38] <mandel> sil2100, I can always create a backport branch, whatever is better
[14:38] <mandel> I think vivid and trunk branches only have that diff atm
[14:38] <sil2100> mandel: silo 27? The location stuff?
[14:38] <sil2100> It's in the overlay PPA already
[14:38] <sil2100> It was a dual-landing silo, so it landed both to vivid-overlay and wily
[14:40] <mandel> sil2100, ah, superb
[14:40] <mandel> sil2100, yest it did not merge against https://launchpad.net/location-service/15.04 correct?
[14:46] <sil2100> mandel: it merged against what the merge was targetting
[14:46] <mandel> sil2100, exactly, trunk, I'll create a branch and merge it
[14:46] <balloons> Ursinha, did you manage to make the switch to ubuntu-clock-app-ci yesterday?
[14:46] <mandel> sil2100, should be a no-brainer
[14:47] <Ursinha> balloons: no, sorry :/ the queue has been long since yesterday (production and LP problems didn't help much) -- let me poke vanguard and see if something can be done
[14:48] <balloons> Ursinha, thanks.. I was just going to ping them, but wanted to make sure you hadn't done any work
[14:48] <balloons> popey, are you ok / happy with switching all the core apps CI to vivid?
[14:52] <sil2100> mandel: dual-landings are most useful for projects that only have one trunk currently ;) So it's a bit more work for you this time
[14:53] <popey> balloons: I am glad you asked. I wanted to ask about this.
[14:53] <popey> balloons: In short, yes, I want them all to go to vivid asap.
[14:53] <Ursinha> balloons: can you send an email to ci-engineering-private@lists.launchpad.net with that request, please? it'll have more reach if you do so :)
[14:53] <balloons> popey, yea, I asked / pinged a few times.. I've requested clock be changed per nik as it's required
[14:54] <balloons> Ursinha, I can, since it's more widespread. If popey is happy to switch, I'm happy and ready too
[14:54] <jibel> seb128, without silo 32 I don't see any untranslated strings in the address book. On arale latest rc-proposed in French. Do you know which strings appear untranslated? the ones on the bug report are correct.
[14:54] <seb128> jibel, it's in the addressbook section of dialer/messaging
[14:54] <seb128> jibel, they import the widgets but don't specify a translation domain so try to load from their domain
[14:55] <seb128> jibel, just start the dialer and click on the contact icon at the top right
[14:55] <mandel> sil2100, yes, no worries
[14:55] <jibel> seb128, ah ok, I see it now. Thanks
[14:55] <popey> balloons: I am happy
[14:55] <seb128> jibel, yw!
[14:55] <mandel> sil2100, can you reconfigure line 15 and also making a dual silo?
[14:55] <mandel> sil2100, or lading.. you know
[14:55] <sil2100> mandel: ok, let me take a look at it
[14:55] <mandel> sil2100, thx
[14:56] <mandel> rsalveti or tvoss can you take a look at https://code.launchpad.net/~mandel/location-service/simple-trust-store-fix/+merge/260497
[14:57] <sil2100> mandel: hm, regarding line 15, sadly I would have to re-assign the silo, meaning wipe the current packages away ;/ This is because the current silo there is for vivid, while in dual landings the primary silo is wily (+ a sync to vivid)
[14:57] <sil2100> mandel: so I don't want to break your current work
[14:57] <sil2100> As you would have to re-build everything
[14:58] <mandel> sil2100, no problem, I mean, I need to rebuild it anyway
[14:58] <mandel> sil2100, at least for location service and the other is just a bunch of little scripts and takes nearly no time
[14:58] <sil2100> Ok then, let me do that, you might get a different silo number
[14:59] <mandel> sil2100, no problem, as long as I get one :)
[15:06] <sil2100> mandel: hah, you got the same one it seems
[15:06] <sil2100> Anyway, you can rebuild
[15:07] <mandel> sil2100, superb
[15:16] <jibel> seb128, silo 32 verified
[15:16] <seb128> jibel, great, thanks
[15:16] <seb128> sil2100, pmcgowan ^
[15:16] <sil2100> o/
[15:17] <sil2100> https://code.launchpad.net/~seb128/address-book-app/translations-gettext-domain/+merge/259926 <- we need review and a top approval here
[15:17] <sil2100> seb128: ^
[15:17] <seb128> pmcgowan, bfiller ^
[15:17] <bfiller> seb128: looking
[15:18] <bfiller> seb128: done
[15:19] <seb128> bfiller, thanks
[15:19] <seb128> sil2100, ^
[15:19] <mandel> pmcgowan, once silo 5 is done building you can take it for a spin, we need to tell qa to test the after wizard usecase and everything is back on track for the ota
[15:24] <seb128> hey
[15:24] <seb128> cihelp can anyone help with https://jenkins.qa.ubuntu.com/job/wily-boottest-address-book-app/lastBuild/console
[15:24] <seb128> "EnvironmentError: Unsupported device, autodetect fails device"
[15:24] <seb128> that blocks the migration
[15:30] <slangasek> sil2100: 14.09-proposed: there was an addition of a (reflexive) channel alias to force a full update, which I understood from barry and stgraber would force a channel reset and full update
[15:30] <slangasek> but perhaps, if ubuntu-touch/ubuntu-rtm/14.09-proposed was not an alias before, this had no effect on the client
[15:31] <sil2100> slangasek: hm, yeah, at least it seems right now that it didn't force a full update in the end
[15:32] <slangasek> barry: do you understand the semantics of the client "bug" that we've been relying on to force an update from 0 when redirecting channels?
[15:32] <slangasek> and can someone pastebin the client.ini from an affected device?
[15:32] <barry> slangasek: i don't think it's a bug
[15:33] <barry> iow, it's a feature, iiuyc
[15:33] <slangasek> barry: stgraber called it a bug, but I've been relying on it as a feature :)
[15:33] <barry> maybe we're talking about different thnings :)
[15:33] <barry>         # If we were tracking a channel alias, and that channel alias has
[15:33] <barry>         # changed, squash the build number to 0 before calculating the
[15:33] <barry>         # winner.  Otherwise, trust the configured build number.
[15:33] <barry>  
[15:33] <slangasek> ok
[15:34] <slangasek> so perhaps the problem is that there wasn't an alias before
[15:34] <slangasek> or perhaps the problem is that the alias didn't change?
[15:34] <slangasek> need client.ini to confirm
[15:34] <barry> and channel.ini
[15:34] <barry> look at [service]channel_target (that's the channel we're on based on the alias mapping in the config file)
[15:35] <barry> then we get the alias from the channel.json
[15:35] <barry> if both are defined and != then we squash the build number to 0 and perform the channel switch
[15:48] <ogra_> barry, slangasek http://paste.ubuntu.com/11414055/ in case that helps you :)
[15:49] <ogra_> seems 14.09-proposed was the actual channel here ... and ubuntu-touch/ubuntu-rtm/devel-proposed was the alias
[15:52] <slangasek> ogra_, barry: oh.  ubuntu-touch/ubuntu-rtm/devel-proposed is on the list of channels that haven't yet been changed
[15:52] <slangasek> so... I can fix that this week :)
[15:52] <ogra_> :)
[15:53] <mandel> sil2100, any idea => https://ci-train.ubuntu.com/job/ubuntu-landing-005-1-build/139/console ??
[15:53] <mandel> sil2100, 2015-05-28 15:51:01,875 ERROR Uncaught exception: HTTPError: HTTP Error 404: Not Found
[15:54] <sil2100> wow
[15:54] <sil2100> mandel: hm, on first glimpse this looks like some network issue, but let me look closer
[15:54] <mandel> sil2100, haha I know what a 404 is ;)
[15:55] <mandel> sil2100, but means you are getting out, and getting an error back for the server telling you that you are looking at the wrong place :)
[15:55] <sil2100> mandel: I know you know! But what I'm saying, it's probably some transient issue ;)
[15:55] <mandel> sil2100, remember, I did the download manager hehe
[15:55] <sil2100> Geez ;p
[15:55] <sil2100> ;)
[15:55] <sil2100> Well, let's try doing a watch only build
[15:55] <sil2100> Probably will work
[15:55] <mandel> sil2100, hehehehhe had to take the opportunity to brag ;)
[15:56] <sil2100> :D
[15:59] <mandel> sil2100, uh, a 502.. is more interesting..
[15:59] <sil2100> ...
[16:00] <sil2100> mandel: try again with a WATCH_ONLY build
[16:01] <mandel> sil2100, on it, I'll walk the dog while I wait, will be back in 20"
[16:11] <jhodapp> sil2100, can I get a silo for line 68 please?
[16:13] <jhodapp> or robru ^
[16:13] <robru> jhodapp: one sec
[16:13] <jhodapp> cool
[16:14] <robru> jhodapp: you sure you want wily and not dual?
[16:15] <jhodapp> robru, well we can't land in vivid right now right?
[16:15] <robru> jhodapp: true. I'm not sure how much longer the gates will be closed for...
[16:15] <jhodapp> robru, I'll do a separate landing for vivid when they open back up
[16:15] <robru> jhodapp: ok no worries
[16:16] <jhodapp> thanks for asking though
[16:16] <robru> jhodapp: you got 27
[16:16] <jhodapp> thanks!
[16:17] <robru> you're welcome
[16:17] <jhodapp> robru, I don't see it on the dashboard
[16:17] <robru> jhodapp: yeah it takes a sec to show up
[16:17] <cwayne> er, my tarball jobs are failing all of a sudden
[16:17] <jhodapp> ah ok
[16:17] <jhodapp> there it is
[16:19] <jhodapp> robru, think we have some infrastructure issues atm: https://ci-train.ubuntu.com/job/ubuntu-landing-027-1-build/81/console
[16:20] <jhodapp> robru, looks like silo 5 had the same issue
[16:21] <robru> jhodapp: can you try it again? I wonder if this is related to there being a package stuck in proposed.
[16:21] <robru> jhodapp: also do a FORCE_REBUILD to fix the changelog issue.
[16:22] <jhodapp> robru, ok
[16:22] <robru> jhodapp: no, wait
[16:23] <robru> cihelp: can I get a boottest retry for http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#media-hub please?
[16:23] <robru> jhodapp: let's get that version of media-hub landed and merged
[16:23] <jhodapp> robru, cancel my build?
[16:23] <jhodapp> robru, yeah was wondering why it hadn't merged
[16:23] <robru> jhodapp: ehhh, i guess not, but you'll need to rebuild after that one merges.
[16:23] <jhodapp> ok np
[16:24] <robru> jhodapp: you should ping us if you notice that kind of stuff, I don't always monitor it very closely ;-)
[16:24] <jhodapp> robru, oh ok, good to know
[16:24] <jhodapp> robru, I thought it would be noticed
[16:24] <jhodapp> robru, hey robru, why hasn't my package merged? ;p
[16:24] <Ursinha> robru: yes, but production services are in trouble as of now (the whole infrastructure our services run on top of)
[16:24] <robru> Ursinha: oh? what's up?
[16:25] <robru> jhodapp: it really shouldn't take more than a couple hours to get through -proposed. in this case it's sat there for 18 hours, so something's definitely wrong
[16:25] <jhodapp> robru, ok
[16:45] <slangasek> sil2100: are there any pending image spins that I would be in the way of if I offlined the importer for the above-mentioned channel fix-ups?
[16:46] <slangasek> (might be offline for a couple of hours)
[16:46] <sil2100> hm, I wanted to kick a new image to get the latest overlay fixes, but we are waiting for one more fix to land so I could wait
[16:47] <sil2100> slangasek: will you be working on it right now? If yes, I guess it's fine and we'll kick a new image once you're done
[16:49] <slangasek> sil2100: no, go ahead with your image
[16:49] <slangasek> I can delay starting on it
[16:51] <sil2100> Ok, building
[16:51] <jhodapp> looks like all silos are broken for building right now
[16:52] <sil2100> Yeah, I just got an LP error
[16:52] <jhodapp> is anyone looking into this?
[16:52] <sil2100> Seems like LP has issues, I can't even access the changes files for packages
[16:52] <jhodapp> geez
[16:58] <jhodapp> robru, do you know if anyone is trying to get media-hub out of the proposed-pocket for silo 20?
[16:59] <robru> jhodapp: huh, yeah Ursinha retried the boottest failure but it looks like it failed again.
[16:59] <robru> jhodapp: so at this point it's not moving, no
[16:59] <jhodapp> robru, perhaps it is failing because of the LP issues right now?
[16:59] <robru> jhodapp: could be
[17:00] <jhodapp> apparently it's a bad issue, nothing will work with the silos
[17:00] <jhodapp> :)
[17:01] <robru> jhodapp: https://imgs.xkcd.com/comics/garfield.jpg heh
[17:01] <robru> jhodapp: so what problems are you seeing?
[17:02] <robru> oh, same proxy error again
[17:02] <jhodapp> lol
[17:02] <robru> jhodapp: yeah not sure what to say, I guess just go for a walk and hope that the lp issues are resolved sooner than later.
[17:02] <jhodapp> yeah, librarian is down
[17:02] <infinity> robru: PS4 is down.  Librarian is in PS4.  All blobs in LP are in the librarian.  Extrapolate.
[17:02] <jhodapp> robru, my work here is done
[17:02] <jhodapp> :)
[17:03] <robru> infinity: but it's not "down" down... some things are working sometimes. it's a strange/flakey issue
[17:03] <robru> infinity: eg I can ssh into wendigo, that's in ps4 as far as I know.
[17:06] <jibel> mandel, any ETA for silo 5?
[17:10] <mandel> jibel, sil2100 I'm getting a 502 => https://ci-train.ubuntu.com/job/ubuntu-landing-005-1-build/141/console
[17:10] <mandel> jibel, sil2100 no idea what is going on
[17:11] <mandel> sil2100, jibel looks like it builds and then something in CI goes nuts
[17:11] <mandel> cihelp, any idea about this ^
[17:11] <cprov> mandel: let me check
[17:12] <mandel> cprov, thx
[17:12] <jibel> mandel, there are infrastructure issues
[17:12] <mandel> jibel, well, the silo is ready in terms of the code and MRs present, we just need to be able to build it :)
[17:12] <cprov> mandel: isn't it possibly about the LP outage ? I am not familiar with the ci-train jobs
[17:13] <sil2100> mandel: issues with the librarian
[17:13] <mandel> ok
[17:13] <sil2100> IS is on it, but anything related to the librarian (LP, PPAs) is down
[17:13] <mandel> jibel, so, shall we wait a few hours and try again?? I can be here by that time
[17:13] <sil2100> It's a complete apocalypse
[17:13] <jibel> mandel, there is not much else we can do
[17:14] <mandel> pmcgowan, ^
[17:14] <sil2100> ;)
[17:14] <cprov> sil2100: thanks for clarifying it
[17:14] <sil2100> np, let's hope this gets resolved soon
[17:14] <mandel> well, so we have to be patient.. just like compiling cpp ;)
[17:15] <mandel> I'm off to run a little and blow some steam instead of hitting Ctrl + F5
[17:20] <jibel> mandel, compiling cpp ... on a panda board ;)
[17:21] <infinity> jibel: Hey, don't speak ill of Pandas.  They treated us remarkably well for a long time.
[17:21] <infinity> (Not that I wasn't very, very happy to replace them...)
[17:21] <jibel> true :)
[17:53] <slangasek> sil2100: I assume that any silo build problems are related to the current ProdStack outage.  I guess that means I can go ahead with my channel changes?
[17:55] <sil2100> slangasek: yeah, this seems to be more serious
[17:56] <sil2100> Go on ahead, the world is burning anyway
[17:56] <sil2100> ;)
[17:56]  * sil2100 liked his panda-board
[17:57] <sil2100> Testing unity7 on it, lovely
[19:13] <slangasek> barry: "If we're tracking a channel alias and that channel alias has changed" - so if the channel alias is /dropped/, does that also force a full update?
[19:15] <barry> slangasek: i think it does not.  if the channel alias is dropped, then there is no "alias" key in the channel.json file, so we think this isn't a channel switch
[19:17] <slangasek> barry: ok, I like that answer ;)
[19:17] <barry> slangasek: phew :)
[20:02] <jhodapp> robru, can I get a silo for line 70?
[20:04] <jhodapp> Ursinha, any idea why media-hub is still stuck in the proposed pocket for silo 20?
[20:04] <Ursinha> jhodapp: proposed is after package left a silo, what do you mean?
[20:05] <robru> Ursinha: he wants you to retry the bootest again
[20:05] <jhodapp> Ursinha, it's been stuck in proposed for over a day
[20:05] <robru> jhodapp: 35
[20:05] <jhodapp> thanks robru
[20:06] <Ursinha> robru: jhodapp, production is having trouble right now, we've retried and I believe the device was poked directly but everything that touches launchpad slightly is broken
[20:06] <jhodapp> Ursinha, ok
[20:07] <jhodapp> thought it might be back up now
[20:09] <Ursinha> jhodapp: librarian is dead :/ so no artifacts from launchpad
[20:09] <Ursinha> (roughly speaking)
[20:10] <jhodapp> anybody know what happened yet?
[20:10] <jhodapp> is this hardware failure?
[20:12] <thomi> jhodapp: prodstack died.
[20:12] <jhodapp> thomi, ok
[20:12] <thomi> jhodapp: It's like that Dylan song: everything is broken
[20:12] <jhodapp> sounds like it'll be a while then ;)
[20:12] <jhodapp> indeed
[21:01] <jgdx> kenvandine, seen the latest uss ci failures?
[21:04] <jgdx> seems random… will have to do some investigation on an actual device tomorrow