=== salem_ is now known as _salem === _salem is now known as salem_ === fginther` is now known as fginther === salem_ is now known as _salem [09:02] seb128: hey! Would need a quick formal binNEW ACK for the usual mir ABI bump binary package renames: https://ci-train.ubuntu.com/job/ubuntu-landing-051-2-publish/12/console :) [09:02] (if you have a moment) [09:02] sil2100, hey! looking in a minute [09:03] Thanks! [09:22] sil2100, looks fine, +1 from me [09:22] \o/ Thanks again :) [09:23] yw! [10:18] alan_g: sil2100 already published it an hour ago [10:18] Mirv: cool. Thanks === joc|away is now known as joc_ === _salem is now known as salem_ [13:28] jgdx: ping [13:28] sil2100, hey, not sure if you're the one to ask, but any idea why ubuntu-touch/rc-proposed/ubuntu is hidden: true? https://system-image.ubuntu.com/channels.json [13:29] someone was indeed asking why of all the channels the recommended channel isn't showing when listing the channels.. [13:29] Mirv, indeed [13:29] rvr, pong [13:29] jgdx: Hi [13:29] jgdx: I'm testing silo 12 and found an issue with system settings and indicators. [13:30] jgdx: Tapping on the settings options on various indicators eventually makes the panel not to hide automatically. [13:30] rvr, it's known and not introduced by this silo [13:31] rvr, let me fetch you the bug [13:31] jgdx: Oh, really? I tried without the silo and couldn't reproduce [13:33] trainguards, is it normal getting "Automated Signoff" == Running for a long time? See https://requests.ci-train.ubuntu.com/#/ticket/1027 [13:34] rvr, https://bugs.launchpad.net/canonical-devices-system-image/+bug/1502223 :) [13:34] Launchpad bug 1502223 in unity8 (Ubuntu) "Delay in opening system-settings from indicators" [High,Triaged] [13:35] rvr, who's this victor guy :p [13:36] rvr, seems it has something to do with unity8, since Ken found the url-dispatcher to launch USS immediately, always. [13:37] jgdx: lol [13:37] jgdx: Hmm [13:38] rvr, fix seems to be targetted for 08, i.e. ota10 [13:38] jgdx: Right, it is a long delay [13:48] abeato: you can check the excuses page to see what exactly is running [13:48] Mirv, https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-046/excuses.html [13:48] abeato: yes, so armhf ntp [13:48] test in progress for armhf [13:49] abeato: following that link brings you to a page that at least no longer mentions ntp, so if it's still not updated 1h from now, it might be time to ping pitti about a stale autopkgtest. but it might be also that it's just waiting to be refresh the page. [13:50] Mirv, apparently there is lack of resources for armhf, yesterday it took hours for another silo to build for armhf too [13:52] abeato: hours is also unfortunately the length of some test runs, added by delay of up to an hour before the excuses page updates [13:52] Mirv, :-/ [14:49] jgdx: Silo 12 approved [14:49] rvr, thank you [15:14] robru, hey, any idea why it suddenly takes 50mins to prepare just qtmir https://ci-train.ubuntu.com/job/ubuntu-landing-064-1-build/52/console ? [15:15] it's four source packages in total, but still... [15:37] Mirv, mind publishing https://requests.ci-train.ubuntu.com/#/ticket/1027 ? need permissions for that [15:41] morphis_: hey! [15:41] sil2100: hey! [15:42] morphis_: if you'd have a moment, could you take a look at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-062/+sourcepub/6095171/+listing-archive-extra ? I prepared a xenial android upload to remove the manta and hammerhead builds from it [15:42] morphis_: could you check if that looks ok? [15:42] sil2100: sure [15:43] morphis_: thanks :) [15:43] morphis_: I checked the build logs and found no mention of manta or hammerhead builds (at least the kernels are not used) [15:53] sil2100: are we landing the same change for vivid? === morphis_ is now known as morphis [15:56] morphis: I could potentially, it wasn't a direct requirement as we're not really building any manta images for rc-proposed [15:57] And yeah, the kernel team never really cared about what's in the overlay [15:57] sil2100: I would like to to minimize the diff between both [15:58] sil2100, mind publishing https://requests.ci-train.ubuntu.com/#/ticket/1027 ? [15:59] morphis: ok, I can push the same change to the same silo for vivid :) But I would take care of a full android source sync some other time [16:01] sil2100: I have that still on my list as there are some changes we need to land [16:06] morphis: ok :) But does the android change look good so far? [16:07] sil2100: yes, fine with that [16:12] morphis: thanks! [16:12] morphis: so I'll add the vivid part and then publish if you're fine with that [16:13] sil2100: yes [16:16] morphis: regarding the fix for ntp - is that change already in xenial, or is this phone-specific only? [16:17] sil2100: better to ask abeato about that [16:17] sil2100: I just did the silo upload for him :-) [16:17] Oh, ok, since I saw the changelog was from you ;) [16:17] abeato: ^ [16:17] ping pong [16:18] sil2100, it's for xenial too, see https://bugs.launchpad.net/canonical-devices-system-image/+bug/1526264 [16:18] Launchpad bug 1526264 in Canonical System Image "ntpdate fails with invalid argument when device is set to a date in the future (delta > 2^16)" [High,Confirmed] [16:18] sil2100, but we need it in the overlay too [16:19] abeato: indeed - we'll have to prepare a version for xenial too then [16:22] sil2100, changing topic, I've built a new system image for frieza with capomastro, which is the process for releasing it? [16:23] abeato: hmmm, you mean a new device tarball? [16:23] correct [16:24] john-mcaleely is out but we need to continue creating images [16:24] abeato: not sure about the details, john-mcaleely would know more, but system-image expects the new tarball in http://people.canonical.com/~jhm/avila/ubuntu/device_frieza.tar.xz [16:24] abeato: and the build ID file here: http://people.canonical.com/~jhm/avila/ubuntu/device_frieza.build [16:25] abeato: once s-i notices a new build in the build ID file, it fetches the device_frieza tarball [16:26] sil2100, hmm, I see, I'll need john-mcaleely to push the files there then [16:32] robru: something weird happened: https://ci-train.ubuntu.com/job/ubuntu-landing-042-1-build/12/consoleFull [16:38] abeato: I could use a different URL if needed [16:38] sil2100: do you have any clue on what happened above? ^ [16:38] sil2100, john-mcaleely is telling me that he will upload it, let's stick with that for the moment [16:39] Trevinho: hey! This usually means someone updated one of the branches from the MPs without rebuilding the silo [16:39] Trevinho: so, if you have an MP, build the silo and then someone pushes a change to that branch, the train will notice and alarm that you have unbuilt revisions (IIRC) [16:40] sil2100: no... I mean https://ci-train.ubuntu.com/job/ubuntu-landing-042-1-build/12/consoleFull [16:40] It looks like the committer value has too many apices.. [16:40] ouch yeah... committer: ""Andrea Azzarone [16:40] "" [16:41] bzr per se doesn't fail though, so maybe... For such cases bileto should just trim the string [16:46] Trevinho: hm, I suppose robru would have too look into that [16:46] sil2100: do you think he could fix it or, should I rebuild the branch? [16:47] I mean, in short time? Since we'd need to get this before beta freeze [16:47] Trevinho: I guess rebuilding might help, but robru should be around in ~1-2 hours to give professional advice [16:48] sil2100: ok thanks [17:05] Trevinho: I have no idea where those quotes are coming from, but I can push a branch that trims the string, yeah. Will hit production in about an hour [17:05] robru: nice, well... It was a mistake from the committer indeed... Since the log has these [17:05] robru: see https://www.irccloud.com/pastebin/VqXKKr8W/ [17:06] However, if you can fix that it would be ncie [17:06] nice* [17:06] Ugh [17:06] OK [17:06] Just need coffee [17:18] Trevinho: ok fix is in trunk, should hit production in exactly one hour, try again then [17:18] robru: nice, thanks [17:22] sil2100, do you want me to do something for the ntp? I'm waiting for some sponsor for xenial, but would like to land this for frieza as it was raised by clients [17:47] dbarth__: mardy: Silo 61 approved [17:50] trainguards, can you please retry the failed i386 build in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-010 thanks [17:51] for messaging app I mean [17:51] Saviq: done [17:51] tx [17:51] yw [18:29] robru: things are working fine now... Thanks for fixing this very-edge case! === alan_g is now known as alan_g|EOD [18:29] Trevinho: haha it was a one-liner. you're welcome [18:30] robru: well, I guess it was just about stripping, but still it was kind of you ;-) [18:30] Trevinho: i love stripping! [18:30] :-P [18:31] ahah :D === blr_ is now known as blr [20:05] rvr: thanks [20:28] robru, can you please copy oxide-qt from ppa:saviq/train to silo 10 (for vivid only atm, xenial in progress) [20:29] OK [20:31] actually xenial's still in proposed, won't bump that until that's out of proposed [22:43] robru: not sure about that message/error for veebers/autopilot ^ [22:44] wtf [22:45] veebers: so sync code is a little bit bit-rotty... [22:47] veebers: so the package is built in the PPA if you want to start testing it in vivid. can you please file a bug with that traceback? there's some code that's assuming everything is merges and then that sync is failing because there's no merge. [22:52] robru: where would I see the traceback? I can't see it in the jenkins job [22:52] veebers: what are you looking at? if you click 'status' on the ticket page it goes directly to the jenkins log that is like 90% traceback. [22:55] robru: ah right :-) I was just looking at the build job log that popped up when I hit 'build' [22:55] veebers: oh yeah no, the status job runs every 15 minutes, it's a different job.