=== ssweeny` is now known as ssweeny === _salem` is now known as _salem [03:13] robru: argg...for tomorrow, i think i'm gonna need that qtmir ppa force merged after all === fginther` is now known as fginther [04:30] kgunn: want me to merge it now? or tomorrow? === bpierre_ is now known as bpierre [08:23] dbarth__, https://requests.ci-train.ubuntu.com/#/ticket/591 is approved, you can publish unless there is something blocking it [08:51] jibel: ack === dbarth__ is now known as dbarth [09:48] cihelp, hey, I'm getting 404 when I click on Jenkins links in MPs since yesterday evening. example: https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-xenial-touch/131/console [09:50] mzanetti: due to a jenkins upgrade last week, publishing to jenkins.qa.u.c from s-jenkins,ubuntu-ci:8080 is disabled for the time being until IS does some maintenance activities. [09:50] mzanetti: you should be able to access http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-xenial-touch/131/console if you're in company VPN === Mirv_ is now known as Mirv === chihchun_afk is now known as chihchun [10:54] cihelp I see an error on https://code.launchpad.net/~alan-griffiths/mir/fix-1463873/+merge/277552/comments/702616 that I get a 404 for: https://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-vivid-armhf/4834/console. Possibly related: https://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-vivid-armhf/ stops on the 12th. [10:55] alan_g: looking [10:56] psivaa: alan_g: Note that all our jobs fail to get published to the public servers and there is a related error in s-jenkins, e.g., http://s-jenkins.ubuntu-ci:8080/job/mir-autolanding/2126/ [11:12] cihelp: I am trying to access job/webbrowser-app-vivid-amd64-ci/1173/console via http://s-jenkins.ubuntu-ci:8080/ via the VPN, but i get a page saying the job is not there. am i missing something ? [11:15] alan_g: alf_ : sorry for the delay. Yes, jobs are not published to publish jenkins waiting for a fix to land in jenkins.qa.u.c [11:15] alan_g: alf_: http://s-jenkins.ubuntu-ci:8080/job/mir-mediumtests-builder-vivid-armhf/4834/console should have the information that you may be interested [11:17] nerochiaro: Build 1173 looks a little too old that it has been pruned. http://s-jenkins.ubuntu-ci:8080/job/webbrowser-app-vivid-amd64-ci/ [11:18] the earliest one we have is 1181 [11:19] psivaa: can i request a rebuild of https://code.launchpad.net/~osomon/webbrowser-app/use-qml-SortFilterModel/+merge/273203 ? [11:19] nerochiaro, I can do that [11:20] cool [11:23] nerochiaro, building: http://s-jenkins.ubuntu-ci:8080/job/webbrowser-app-ci/2473/ [11:27] ubuntu-qa: what’s up with the autopkg tests for qtcreator-plugin-ubuntu and unity8 for the proposed migration? they have been marked as "test in progress" for the migration of webbrowser-app for almost a day now (http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#webbrowser-app) === oSoMoN_ is now known as oSoMoN === _salem is now known as salem_ [11:51] sil2100: ping [11:52] xavigarcia: pong [11:53] sil2100: Hi! so silo 000 is the one containing the new project I asked you about [11:53] sil2100: it should be ready to go [11:53] sil2100: it does no need QA as it's just a library to build integration tests [11:53] Let me take a quick look at it in a moment [11:53] Yeah, I suppose that should be good [11:54] sil2100: I guess somebody should review all the packaging stuff [11:54] sil2100: ok, thanks! [11:59] trainguards, has silo 1 landed successfully, or how is its state? The changes are not in trunk [12:29] mardy: queuebot answered you 2 mins later, still in proposed [12:30] mardy: it's always several hours minimum now that we land to real archives so that we don't skip proposed tests [12:30] the dual landing to PPA only was an exception that skipped a lot of our test infrastructure [12:31] Mirv: ok, thanks [12:36] xavigarcia: hey, just a quick question about silo 000 [12:36] xavigarcia: I see that the merge from silo 000 has another branch as a prerequisite, but that branch is not in the silo [12:37] xavigarcia: (talking about https://code.launchpad.net/~xavi-garcia-mena/gmenuharness/update-changelog/+merge/277441 ) [12:37] xavigarcia: shouldn't that merge be also included in the silo? [12:46] cihelp, what's the deal with https://code.launchpad.net/~seb128/camera-app/red-delete-button/+merge/277668/comments/702629 ? [12:46] "Problem accessing /job/camera-app-vivid-armhf-ci/149/console. Reason: " [12:46] " Not Found" [12:51] seb128: please use s-jenkins.ubuntu-ci:8080/job/camera-app-vivid-armhf-ci/149/console until IS sorts out publishing issue [12:53] psivaa, k, thanks, shouldn't that be announced somewhere? [12:54] also shouldn't the CI use what is in the vivid-overlay? [12:54] it doesn't find the 1.3 toolkit there... [12:54] seb128: Agree, we should announce. Will do that in a bit [12:54] thanks [12:57] psivaa, saw my overlay use question as well? [12:58] seb128: yea, looking into it [12:58] thanks === alan_g is now known as alan_g|lunch [13:01] seb128: https://trello.com/c/x8VCBKzk/865-vanguard-camera-app-not-using-vivid-overlay has been created. One of us will attend as soon as possible [13:04] psivaa, thanks [13:04] Kaleo, ^ just fyi, unsure if you still work on camera and if that's something you noticed === ssweeny` is now known as ssweeny [13:07] seb128, I still work on the camera [13:07] seb128, thanks [13:07] Kaleo, yw ;-) [13:08] sil2100: I fixed xavigarcia_lunch's missing MR from the silo [13:08] sil2100: the packaging is very standard apart from one thing [13:08] pete-woods: you'll need to rebuild now, right? [13:08] sil2100: I guess that's techinically true [13:08] even if the result will be identical [13:08] * pete-woods hits rebuild [13:09] sil2100: the special part of the packaging, btw, is to handle the ABI changes in xenial without separate branches [13:09] Kaleo, btw https://code.launchpad.net/camera-app/+activereviews has some things waiting for 1.5 years for review, maybe would be good to clean those out [13:09] we switch based on the distro name, and use a separate symbols file for each [13:09] sil2100: (https://code.launchpad.net/~pete-woods/gmenuharness/distro-specific-symbols-files/+merge/277663) [13:32] :) packages rebuilt ^ sil2100 [13:33] http://bazaar.launchpad.net/~pete-woods/gmenuharness/distro-specific-symbols-files/files/head:/debian/ <- debian dir for packaging review [13:52] greyback_: is it ok to get robru to force merge that qtmir in silo 49 ? [13:53] kgunn: it is if robru says so :) [13:53] long story...kdub's gotta fix in mir that richard needs, but in silo it builds against the old [13:53] cool === barry` is now known as barry === alan_g|lunch is now known as alan_g [14:39] sil2100: you about ? [14:39] kgunn: hey, yeah [14:40] sil2100: hey, i was pestering rob but he was on late...so any way you could force merge silo 49 for us ? [14:40] sutck in proposed [14:40] and now hampering another bug fix in a seperate silo [14:41] kgunn: yeah, ok, will do that as the migration problem is unrelated to mir [14:45] kgunn: done [14:48] tvoss, mardy silo 57 approved [14:50] ta [15:02] jibel, bzoltan, pmcgowan, what's the status of the fix for https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1512924 ? are we going to get that in ota8 (+ translators doing their job + langpack updates)? [15:02] Ubuntu bug 1512924 in ubuntu-ui-toolkit (Ubuntu) "Timestamps not localized in notifications" [High,In progress] [15:05] xavigarcia, pete-woods: ok, package looks okayish from my POV, although I always feel a bit meh with all the scripts to support two different distros [15:05] xavigarcia, pete-woods: but in this case it seems not so invasive anyway [15:05] xavigarcia, pete-woods: that being said... I would like someone from the archive admin team to take a look before I publish, as my button press will result in an instant copy to the overlay [15:05] So I want a preNEW review first [15:05] seb128: ping :) [15:05] sil2100, contentless ping warning [15:06] I was also just talking so you know I'm around ;-) [15:06] what's the package to review? [15:06] seb128: uh oh, apologies! Anyway, we'd need a preNEW review of silo https://requests.ci-train.ubuntu.com/#/ticket/650 [15:07] k [15:07] seb128: a new one, libgmenuharness [15:07] yetanothergmenulib?! ;-) [15:07] xavigarcia, pete-woods: one remark I have though... why is the source name different from the LP project name? [15:07] seb128, status is moved to OTA9 [15:07] I mean, it's not a blocker, but when a project is hosted on LP it's much easier as both are the same [15:07] jibel, that's a joke? [15:08] seb128, why? [15:08] jibel, how come we can't land a template update in 15 days and then need to rollout an ota with obvious UI part untranslated? [15:08] sil2100: there is no reason [15:08] it's like timestamp in the messaging indicators [15:08] difficult to do more visible [15:09] sil2100: I just created the project like that and I kept it... I know what you mean... but we thought it was OK [15:09] seb128, once we have a fix we will consider releasing it early, want to get input from folks [15:09] pmcgowan, you are speaking about what? the utik translation issue? [15:09] yes [15:10] the timestamps thing [15:10] we have a fix commited since 2015-11-05 [15:10] see https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/kickLocaleTemplate/+merge/276733 [15:10] it seems it just didn't make it an upload since [15:10] hmm thats bad [15:10] unsure why, I though jibel was pushing bzoltan to have an hotfix landing for that [15:10] rather than a full uitk update [15:11] also it doesn't even need an upload [15:11] it needs the new template to be commited which can be done manually [15:11] seb128, actually I just discovered that yesterday and spoke to bz about it [15:12] seb128, it can be fixed without landing uitk? [15:12] pmcgowan, well, that's a translation template [15:12] some project just commit the pot updates directly to trunk [15:12] to bypass the upload delays [15:13] but then it needs translator work and a langpack update [15:13] so unsure it's pratical for ota8 now [15:13] I see [15:13] I just don't get why it stalling since 11-05 [15:14] it was even on the ww46-2015 list [15:24] sil2100: it's a good question [15:25] we should probably change it to gmenuharness everwhere [15:25] xavigarcia: it's only the source package name that needs changing [15:36] pmcgowan, can we at least get somebody from the uitk to commit the template update so translators can do their work and we can see in maybe updating some langpacks if there is a window for that? [15:39] seb128, sure it needs to go from staging to trunk? [15:39] pmcgowan, yes [15:39] sil2100: I have added a branch to the MR that fixes the source package name [15:39] but I'm not quite sure how to rebuild it [15:39] pete-woods: \o/ if you added a new branch to the silo then just press build on the silo [15:40] pete-woods: we'll remove the old binaries [15:40] binaries/sources [15:47] sil2100: it won't rebuilt with an empty list of packages [15:47] and building with libgmenuharness didn't seem to do anything [15:47] trying gmenuharness now [15:48] that didn't work either [15:48] sil2100 ^ see build errors [15:48] might be easier to make a new silo? [15:49] and bin this one [15:51] edited a line of the train config [15:51] maybe that was is.. [15:51] *it [15:51] pete-woods: maybe, did you try force-rebuild? [15:51] no [15:51] it's getting further now [15:52] but it doesn't seem to have built the source package in the build log [15:52] https://ci-train.ubuntu.com/job/ubuntu-landing-000-1-build/556/console [15:52] it's just trying to wait on it [15:52] which is obviously not going to work [15:59] right, nuking the silo [15:59] it's not worth messing around [16:25] sil2100: it's obviously getting upset [16:25] I tried a new silo [16:26] (ended up with 000 again) [16:26] and it is still half looking for libgmenuharness [16:26] I don't know where it's getting this info from, though [16:26] as the source package is definitely just gmenuharness [16:43] kenvandine: Silo 24 approved [16:44] rvr, thx! === chihchun is now known as chihchun_afk [16:49] (see https://ci-train.ubuntu.com/job/ubuntu-landing-000-1-build/557/console) [16:57] robru: I seem to have upset citrain ^ we decided to rename a source package before first release, and citrain seems to have remembered the old value somehow? [17:04] pete-woods, the descriptions are not very useful is you don't know what "GMenu harness" is (why I don't, still trying to guess what that component does) [17:05] pete-woods, sil2100, otherwise packaging seems fine to me [17:05] seb128: it's a test harness for things that expose gmenu models [17:05] in particular, indicators [17:05] you might want to write a few liner description saying that [17:05] I wrote it to finally add tests to indicator-network [17:06] and it's going to be used for indicator-sound [17:09] seb128: thanks for looking over the packaging, by the way :) [17:10] pete-woods, yw! [17:10] cihelp, I am getting 'Unsupported device, autodetect fails device' on jenkins build: http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-runner-vivid-touch/4125/console [17:44] pete-woods: yes the source package name lookup is very slow so there's a disk cache, I'll clear it in a moment [17:53] cihelp: anyone has any ideas why this fails to build in ci ? https://code.launchpad.net/~uriboni/messaging-app/stickers/+merge/277446 doesn't seem like a problem with the code === alan_g is now known as alan_g|EOD [18:23] nerochiaro, indeed that MP was impacted by an issue related to the recent upgrade. I've restarted the job [18:24] fginther: thanks [18:24] bfiller: ^ === salem_ is now known as _salem === _salem is now known as salem_ === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === jdstrand_ is now known as jdstrand === salem_ is now known as _salem [21:22] trainguards: what does this error mean exactly? https://ci-train.ubuntu.com/job/ubuntu-landing-049-1-build/55/console [21:24] dobey: "native" versioning means that the version number has "-NubuntuN" in it or not, it looks like the "-0" is missing from that version string [21:25] native means it doesn't have it [21:25] which is correct [21:25] dobey: the "-gcc" madness it non native due to the dash [21:25] robru: that's not a dash [21:26] it's a tilde [21:26] dobey: s/madness/makes/ [21:26] dobey: sorry I'm on mobile [21:26] madness might be correct here :) [21:26] ok [21:27] how do i see what version number the tool is generating, in the log? [21:27] dobey: 2015-11-17 21:09:14,343 WARNING Created tag 15.11+16.04.20151117-0ubuntu1. [21:27] i guess this is a bug in the cupstream2distro script? [21:27] ah [21:27] yes that is wrong [21:28] hrmm [21:28] dobey: the version logic hasn't changed in a long time [21:28] dobey: perhaps you changed something that triggered a different code path [21:29] i'll try to specify a complete version in changelog and see what happens [21:29] dobey: no [21:29] dobey: hang on let me look [21:32] dobey: weird, there are tests to ensure that if the version doesn't start with -0ubuntu1 that it doesn't add that incorrectly http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro/trunk/view/head:/tests/unit/test_version.py#L152 [21:33] dobey: yeah I guess try the full version, not sure what's going on there [21:34] dobey: oh, just looked at your last commit, yeah [21:35] yeah, full version seems to work [21:35] Created tag 15.11+16.04.20151117.1. [21:36] i guess the gcc5.1 manual upload version exposed a bug [21:53] dobey: no, if you put in a version that doesn't have a +, the train generates "+16.04.YYYYMMDD-0ubuntu1". if you want the native version you have to start with a native version that has a + in it [21:54] robru: that part is fine. i tried the "15.11" by itself, because i got the error without tweaking the changelog [21:55] ugh [21:56] robru: anyway, worked around. i'll poke at it more later [21:56] thanks :) [21:56] dobey: you're welcome