=== chihchun_afk is now known as chihchun [02:40] 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] robru: where does it say overlay ppa? I think we just need for wily for now [02:43] bfiller: it's in column L [02:44] robru: fixed [02:44] bfiller: got you silo 21, thanks [02:44] thanks robru [02:44] bfiller: you're welcome === chihchun is now known as chihchun_afk === marcusto_ is now known as mr_t_ === mr_t_ is now known as marcustomlinson [06:15] tvoss: wouldn't you want dual landing silo btw to land also to wily? [06:16] tvoss: ok :) [06:16] Mirv, yup, sorry :) [06:19] Mirv, I found an issue where a package from the silo is older than the package in the overlay ppa [06:19] Mirv, is that a known hiccup and do we have instructions for pinning available? [06:19] Mirv, see http://pastebin.ubuntu.com/11405991/ [06:22] 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] 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] Mirv, yup [07:28] trainguards hello, can i get a silo for line #35? === chihchun_afk is now known as chihchun [07:32] pstolowski: thanks! and yes. === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [08:07] sil2100, morning, can you build an rc-proposed image to grab silo 20 that landed last night? it fixes bug 1457129 [08:07] bug 1457129 in media-hub (Ubuntu) "All sound stops playing after receiving SMS messages" [Critical,Fix committed] https://launchpad.net/bugs/1457129 === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [08:17] jibel: sure, on it [08:17] jibel: did the location silo land? [08:18] hm, doesn't look like it [08:18] well, see the other channel [08:28] ogra_: is imgbot out sick today? [08:28] oops, i rebooted the server, forgot to start it again ... one sec [08:28] It missed my image build... ;) === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [08:29] http://people.canonical.com/~ogra/touch-image-stats/vivid/20150527.changes is the last one available [08:30] (i still havent had time to get the new mapping right for vivid) [08:30] imgbot, stunt [08:30] * imgbot rolls on its back and purrs [08:30] there he is [08:44] sil2100, location didn't land. location-service didn't start with the silo, and accuracy is still really ba [08:44] d === chihchun is now known as chihchun_afk [08:54] trainguards, hey, my silo 33 (line #29) can be freed [08:55] pstolowski: oh, not needed? [08:55] sil2100, same stuff is in silo 29 :/ [08:55] huh [08:56] yeah, there was some messup and reconfigs between wily and vivid, ended up with two silos at the end === chihchun_afk is now known as chihchun === MacSlow is now known as MacSlow|lunch === chihchun is now known as chihchun_afk [11:42] sil2100, seb128 just emailed, I would fix those translation issues, we have time [11:53] 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] so that's what's in wily [11:54] I've kept giving the wily .deb for people asking, but that'd reach more people [12:09] jibel, silo 27 working for me [12:09] fwiw [12:10] pmcgowan: ok, aren't we a bit under deadline pressure though? ;) [12:10] I thought that, you know, today is teh end [12:11] Mirv: sounds okayish to me I suppose, since the phablet-tools aren't installed on our phones [12:12] sil2100, after discussion with meizu they prefer we fix more issues rather than keep the date - so we can fit a couple more in === alan_g is now known as alan_g|lunch [12:12] \o/ [12:12] sil2100, still need to be strict about what issues [12:12] True [12:12] Ok, excellent news anyway [12:15] 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] pmcgowan: is https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1425172 on your radar for a fix soon? [12:15] Launchpad bug 1425172 in network-manager (Ubuntu RTM) "Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)" [High,Confirmed] [12:15] popey, yeah thats a bad one [12:16] i just marked a bug I filed a year ago as a dupe of it, didn't realise it still happened. [12:17] popey, probably comes and goes [12:17] also, I rarely leave the house which helps avoid the bug ㋛ === mzanetti is now known as mzanetti|run === MacSlow|lunch is now known as MacSlow [12:29] pmcgowan, yeah I confirmed tvoss's fix works quickly earlier. [12:29] trainguards, any idea how I build silo 36? [12:30] I used force and I specified that I only wanted to build ubuntu-system-settings. [12:30] tvoss, ^ wrt silo 27 is it ready for QA ? [12:31] jibel, should be yes, tvoss is afk right now [12:32] OK, I'll do the verification it is already installed on my device. [12:33] seb128, can we get a silo for your fixes at https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1447516 [12:33] Launchpad bug 1447516 in address-book-app (Ubuntu) "Contact strings under All & Favorites are not localized" [High,In progress] [12:34] 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] seb128, great, any other regressions that slipped in you know of [12:35] 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] jgdx: so wily is at 20150527 while vivid overlay is at 20150514 [12:36] 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] pmcgowan, or do we plan to switch -proposed to vivid before it's rolled as a stable ota to users? [12:37] seb128, there are at least several folks dog fooding it, I did not switch yet [12:38] pmcgowan, right, I'm sure it's getting some testing, not sure enough to be confident there is no important issues though... [12:38] pmcgowan, is there any reason we don't switch all testers/people on -proposed to vivid? [12:38] since that's the candidate for the next ota [12:38] that would give extra testing on it [12:39] seb128, I suppose we should really === greyback__ is now known as greyback [12:40] seb128, I think we need an image server fix first [12:40] sil2100, oh, seb128's words above remind me ... do we have an update plan for people using rtm-proposed currently ? [12:41] 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] ogra_, right they should go to the vivid proposed [12:41] 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] seb128, you are right, we were just focused on arale factory image, and next step is updating krillins [12:41] we should move proposed over now [12:42] +1 :-) [12:42] Mirv, jgdx, what u-s-s situation? [12:42] Mirv, hm, okay, I have to think about it. Might do a stableoverlay specific one [12:42] pmcgowan, indeed, i was wondering if we can automate that ... [12:42] (thus my question) [12:43] 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] 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] seb128: jgdx is trying to target vivid overlay with a trunk MP which doesn't work since overlay is at 20150514 [12:43] 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] Mirv, jgdx, kenvandine created https://code.launchpad.net/~system-settings-touch/ubuntu-system-settings/15.04 for vivid-overlay [12:44] jgdx: ^ ok then you should target the branch instead of wily, probably doing another landing eventually to the wily (trunk) too [12:44] we should target stable fix there [12:44] pmcgowan, ah [12:44] and yeah, you need to land to trunk as well [12:44] seb128, Mirv, okay, I'll land in Wily then backport? [12:44] ogra_, https://bugs.launchpad.net/canonical-devices-system-image/+bug/1444347 [12:44] Launchpad bug 1444347 in Ubuntu system image "/usr/bin/aa-clickhook:ImportError:/usr/bin/aa-clickhook@14:/usr/lib/python3/dist-packages/apparmor/click.py@15:/usr/lib/python3.4/ctypes/__init__.py@7" [Critical,In progress] [12:44] jgdx, wfm, [12:44] Mirv, thx [12:44] ouch [12:45] jgdx: that's a good option, no problem [12:45] Mirv, that requires a reconfigure? [12:47] landingprocess docs does not explicitly state whether or not to [12:49] 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] Mirv, can you hold on until ken apparates? [12:50] ogra_: rtm-proposed? You mean like 14.09-proposed? [12:50] jgdx: sure, and sil2100 can help if I'm already away at that point [12:50] Mirv, thanks [12:50] sil2100, yeah [12:50] ogra_: they're already on vivid since long if they use that [12:51] sil2100, what most canonical employees run ;) [12:51] oh ? [12:51] Since 14.09-proposed is now a redirect to rc-proposed [12:51] Since the reordering that slangasek made [12:52] my "about" page says 14.10 ... image 277 [12:52] sil2100, I dont think so [12:52] Well, just saying what's in system-image [12:52] That's how it's configured [12:53] 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] sil2100, same as others, being on 14.09-proposed gives me a 277 utopic-rtm based image [12:53] not a vivid one [12:53] sil2100, right, which is good since we have that server bug I posted above [12:54] Yeah, barry is on it [12:54] well, we should tell people to switch then [12:54] 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] since that channel looks like a dead end now [12:55] the versions you import will most likely always be lower than 277 [12:55] Since ubuntu-touch/ubuntu-rtm/14.09-proposed is "redirect": "ubuntu-touch/rc-proposed/bq-aquaris.en" [12:55] (or the versions you redirect to) [12:56] 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] I'll poke barry and slangasek once they're around [12:56] yeah [12:57] if upgrade doesnt work we should just wipe the channel and ask people to switch over [12:57] (if it evidently is bound to the version number) === mzanetti|run is now known as mzanetti [13:11] sil2100, can you check that l66 is fine and assign a silo if it is? [13:11] seb128: I just did :) [13:11] Silo 32 for you [13:11] 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] No worries, should be ok if you do the dual landing now [13:13] 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] jgdx, yes, it should be wily now [13:13] i'll reconfigure [13:14] oh bugger [13:14] okay, so we'll backport? [13:14] RTM all over again? [13:14] libqofono [13:14] yes [13:17] 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] jibel, we will decide later [13:18] 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] ok === alan_g|lunch is now known as alan_g [13:21] \o/ [13:23] tvoss: is this one approved? https://code.launchpad.net/~thomas-voss/location-service/fix-1426307/+merge/260365 [13:23] sil2100, getting rsalveti to do so ;) [13:24] * tvoss hands beers and stuff to rsalveti [13:24] ;) [13:25] tvoss: you fool now his hands are full and he can't do anything :P [13:29] davmor2, at least he cannot break anything [13:32] tvoss: no that's my job :D [13:32] davmor2, yeah, although you most often prove that they are indeed broken ;) [13:32] 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] alecu: indeed, let me help you here [13:34] thanks! [13:35] jibel, when you say that part of the fix was in silo 05, what do you mean? [13:36] mandel, this MR was in silo 27 https://code.launchpad.net/~thomas-voss/location-service/fix-1426307/+merge/260365 [13:37] jibel, yes, I know that, and you needed that guy + silo 05, is that what you mean [13:37] ??? [13:37] mandel, nope, I mean what is silo 5 supposed to fix now? [13:37] jibel, issues with the location service in vivid after the wizard [13:38] 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] mandel, verification of 27 is done, and accuracy is fine, I'd rather land them separately. [13:39] tvoss, ^ what do you think? [13:40] jibel, mandel I would vote for landing 27 as is [13:40] 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] mandel, just remove my mp from 5, reconfigure and rebuild [13:40] 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] tvoss, did it work after the wizard? 'cause it is then when we have the issues [13:41] tvoss, the issues is when the location service is restarted, then the trust store does not work [13:41] mandel, I did a --bootstrap, so I think yes [13:41] mandel, probably best to retest silo 5 [13:41] tvoss, let me double check, if that is the case I'm happy to kill 5 [13:42] tvoss, you read my mind, doing it now [13:42] mandel, or better: retest without silo 5 [13:42] tvoss, my idea was to --wipe, test and see the error ;) [13:44] mandel, also https://code.launchpad.net/~thomas-voss/location-service/fix-1426307/+merge/260365 could use a review [13:44] seems like my beers for rsalveti don't help [13:44] tvoss, on it [13:48] 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] jibel, tvoss nor osmtouch [13:48] jibel, could you double check that I'm not saying utter bullshit? I'll try again [13:49] mandel, okay, so if that is the case, let's clean up silo 5 [13:49] mandel, you also merged one of my branches in there, which are probably not required right now, we can land it later [13:49] mandel, best to keep this as clean as possible [13:51] tvoss, then let me create an mr just for the trust store fix and add it to silo 27 [13:52] tvoss, to fix both issues in that silo and then move to add the rest of the code later [13:52] mandel, nope, let's land silo 27 now as is and clean up silo 5 [13:52] mandel, why overload the silo? we haveboth anyway and one of them needs rebuild no matter what [13:52] tvoss, jibel ok, lets land 27 asap [13:53] tvoss, mandel I get a trust prompt in the browser [13:53] with last image plus 27 [13:53] pmcgowan, after the wizard? [13:53] tvoss, oh no [13:53] pmcgowan, one trust prompt or a location trust prompt?? and, after the wizard? [13:53] not first boot [13:53] if thats the issue nm [13:53] pmcgowan, we are talking about first boot [13:54] ack [13:54] pmcgowan, yes, that is the issues, acceptance of the license and usage of the location service [13:54] pmcgowan, so are you in the loop, we get silo 27 I clean silo 5 and rebuild it [13:54] pmcgowan, sounds good? [13:54] 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] Excellent [13:55] seb128, awesome mark for qa jibel ^^ [13:55] tvoss: is the MR reviewed? [13:55] jibel, https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1447516 [13:55] Launchpad bug 1447516 in address-book-app (Ubuntu) "Contact strings under All & Favorites are not localized" [High,In progress] [13:55] sil2100, if not I'll do it [13:55] jibel, the fix is in silo 32 [13:55] sil2100, nope, waiting for either mandel or rsalveti [13:55] sil2100, on it [13:57] sil2100, tvoss everything looks good to me, and it works. I have approved and top approved [13:57] Yay, ok, publishing [13:57] ack [14:00] hmmm [14:01] The train went a bit crazy here, let me just note down the silo number [14:01] * rsalveti reads [14:01] tvoss: sorry, was in a meeting [14:01] it seems mandel already covered it [14:02] 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] rsalveti, 27 has been approved, I clean 5 and do a rebuild [14:03] great [14:04] I'm trying to understand the jenkins breakage's on http://people.canonical.com/~ubuntu-archive/pending-sru.html [14:04] specifically around the apt package updates autopkgtest for apport 2.0.1-0ubuntu17.8: Test in progress (Jenkins: public, private) , [14:04] autopkgtest for apport 2.14.1-0ubuntu3.10: Regression (Jenkins: public, private) and more for trusty [14:09] 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] gQuigs: I'll have a look [14:10] ty [14:12] in trusty the apt and gtk-3 failures (at least apport) seem to be identical.. [14:16] Uuuuh, I think I see a bug in the train :| [14:16] Daaamn [14:17] Grrr [14:19] looks like the settings build in silo 33 got canceled? [14:31] tvoss: you left before I could say that the autolanding problem was the one we were discussing [14:38] 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] sil2100, I can always create a backport branch, whatever is better [14:38] I think vivid and trunk branches only have that diff atm [14:38] mandel: silo 27? The location stuff? [14:38] It's in the overlay PPA already [14:38] It was a dual-landing silo, so it landed both to vivid-overlay and wily [14:40] sil2100, ah, superb [14:40] sil2100, yest it did not merge against https://launchpad.net/location-service/15.04 correct? [14:46] mandel: it merged against what the merge was targetting [14:46] sil2100, exactly, trunk, I'll create a branch and merge it [14:46] Ursinha, did you manage to make the switch to ubuntu-clock-app-ci yesterday? [14:46] sil2100, should be a no-brainer [14:47] 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] Ursinha, thanks.. I was just going to ping them, but wanted to make sure you hadn't done any work [14:48] popey, are you ok / happy with switching all the core apps CI to vivid? [14:52] 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] balloons: I am glad you asked. I wanted to ask about this. [14:53] balloons: In short, yes, I want them all to go to vivid asap. [14:53] 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] popey, yea, I asked / pinged a few times.. I've requested clock be changed per nik as it's required [14:54] Ursinha, I can, since it's more widespread. If popey is happy to switch, I'm happy and ready too [14:54] 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] jibel, it's in the addressbook section of dialer/messaging [14:54] jibel, they import the widgets but don't specify a translation domain so try to load from their domain [14:55] jibel, just start the dialer and click on the contact icon at the top right [14:55] sil2100, yes, no worries [14:55] seb128, ah ok, I see it now. Thanks [14:55] balloons: I am happy [14:55] jibel, yw! [14:55] sil2100, can you reconfigure line 15 and also making a dual silo? [14:55] sil2100, or lading.. you know [14:55] mandel: ok, let me take a look at it [14:55] sil2100, thx [14:56] rsalveti or tvoss can you take a look at https://code.launchpad.net/~mandel/location-service/simple-trust-store-fix/+merge/260497 [14:57] 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] mandel: so I don't want to break your current work [14:57] As you would have to re-build everything [14:58] sil2100, no problem, I mean, I need to rebuild it anyway [14:58] sil2100, at least for location service and the other is just a bunch of little scripts and takes nearly no time [14:58] Ok then, let me do that, you might get a different silo number [14:59] sil2100, no problem, as long as I get one :) === chihchun_afk is now known as chihchun [15:06] mandel: hah, you got the same one it seems [15:06] Anyway, you can rebuild [15:07] sil2100, superb [15:16] seb128, silo 32 verified [15:16] jibel, great, thanks [15:16] sil2100, pmcgowan ^ [15:16] o/ [15:17] https://code.launchpad.net/~seb128/address-book-app/translations-gettext-domain/+merge/259926 <- we need review and a top approval here [15:17] seb128: ^ [15:17] pmcgowan, bfiller ^ [15:17] seb128: looking [15:18] seb128: done [15:19] bfiller, thanks [15:19] sil2100, ^ [15:19] 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] hey [15:24] cihelp can anyone help with https://jenkins.qa.ubuntu.com/job/wily-boottest-address-book-app/lastBuild/console [15:24] "EnvironmentError: Unsupported device, autodetect fails device" [15:24] that blocks the migration [15:30] 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] but perhaps, if ubuntu-touch/ubuntu-rtm/14.09-proposed was not an alias before, this had no effect on the client [15:31] slangasek: hm, yeah, at least it seems right now that it didn't force a full update in the end [15:32] 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] and can someone pastebin the client.ini from an affected device? [15:32] slangasek: i don't think it's a bug [15:33] iow, it's a feature, iiuyc [15:33] barry: stgraber called it a bug, but I've been relying on it as a feature :) [15:33] maybe we're talking about different thnings :) [15:33] # If we were tracking a channel alias, and that channel alias has [15:33] # changed, squash the build number to 0 before calculating the [15:33] # winner. Otherwise, trust the configured build number. [15:33] [15:33] ok [15:34] so perhaps the problem is that there wasn't an alias before [15:34] or perhaps the problem is that the alias didn't change? [15:34] need client.ini to confirm [15:34] and channel.ini [15:34] look at [service]channel_target (that's the channel we're on based on the alias mapping in the config file) [15:35] then we get the alias from the channel.json [15:35] if both are defined and != then we squash the build number to 0 and perform the channel switch [15:48] barry, slangasek http://paste.ubuntu.com/11414055/ in case that helps you :) [15:49] seems 14.09-proposed was the actual channel here ... and ubuntu-touch/ubuntu-rtm/devel-proposed was the alias [15:52] ogra_, barry: oh. ubuntu-touch/ubuntu-rtm/devel-proposed is on the list of channels that haven't yet been changed [15:52] so... I can fix that this week :) [15:52] :) [15:53] sil2100, any idea => https://ci-train.ubuntu.com/job/ubuntu-landing-005-1-build/139/console ?? [15:53] sil2100, 2015-05-28 15:51:01,875 ERROR Uncaught exception: HTTPError: HTTP Error 404: Not Found [15:54] wow [15:54] mandel: hm, on first glimpse this looks like some network issue, but let me look closer [15:54] sil2100, haha I know what a 404 is ;) [15:55] 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] mandel: I know you know! But what I'm saying, it's probably some transient issue ;) [15:55] sil2100, remember, I did the download manager hehe [15:55] Geez ;p [15:55] ;) [15:55] Well, let's try doing a watch only build [15:55] Probably will work [15:55] sil2100, hehehehhe had to take the opportunity to brag ;) [15:56] :D [15:59] sil2100, uh, a 502.. is more interesting.. [15:59] ... [16:00] mandel: try again with a WATCH_ONLY build [16:01] sil2100, on it, I'll walk the dog while I wait, will be back in 20" [16:11] sil2100, can I get a silo for line 68 please? [16:13] or robru ^ [16:13] jhodapp: one sec [16:13] cool [16:14] jhodapp: you sure you want wily and not dual? [16:15] robru, well we can't land in vivid right now right? [16:15] jhodapp: true. I'm not sure how much longer the gates will be closed for... [16:15] robru, I'll do a separate landing for vivid when they open back up [16:15] jhodapp: ok no worries [16:16] thanks for asking though [16:16] jhodapp: you got 27 [16:16] thanks! [16:17] you're welcome [16:17] robru, I don't see it on the dashboard [16:17] jhodapp: yeah it takes a sec to show up [16:17] er, my tarball jobs are failing all of a sudden [16:17] ah ok [16:17] there it is [16:19] robru, think we have some infrastructure issues atm: https://ci-train.ubuntu.com/job/ubuntu-landing-027-1-build/81/console [16:20] robru, looks like silo 5 had the same issue [16:21] jhodapp: can you try it again? I wonder if this is related to there being a package stuck in proposed. [16:21] jhodapp: also do a FORCE_REBUILD to fix the changelog issue. [16:22] robru, ok [16:22] jhodapp: no, wait [16:23] cihelp: can I get a boottest retry for http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#media-hub please? [16:23] jhodapp: let's get that version of media-hub landed and merged [16:23] robru, cancel my build? [16:23] robru, yeah was wondering why it hadn't merged [16:23] jhodapp: ehhh, i guess not, but you'll need to rebuild after that one merges. [16:23] ok np [16:24] jhodapp: you should ping us if you notice that kind of stuff, I don't always monitor it very closely ;-) [16:24] robru, oh ok, good to know [16:24] robru, I thought it would be noticed [16:24] robru, hey robru, why hasn't my package merged? ;p [16:24] robru: yes, but production services are in trouble as of now (the whole infrastructure our services run on top of) [16:24] Ursinha: oh? what's up? [16:25] 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] robru, ok [16:45] 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] (might be offline for a couple of hours) [16:46] 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] 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] sil2100: no, go ahead with your image [16:49] I can delay starting on it [16:51] Ok, building [16:51] looks like all silos are broken for building right now [16:52] Yeah, I just got an LP error [16:52] is anyone looking into this? [16:52] Seems like LP has issues, I can't even access the changes files for packages [16:52]