[09:29] <Mirv> anything for the meeting?
[09:55] <anpok_> cihelp: we have a problem in unity-system-compositor ci https://jenkins.qa.ubuntu.com/job/unity-system-compositor-wily-amd64-ci/88/console for some reason the builder is unable to find mirclient via pkg-config (but it does install libmirclient-dev from the mir staging ppa, which has the pc file) this seems to happen in several mps
[09:55] <psivaa> anpok_: looking
[10:09] <anpok_> psivaa: I believe this is a problem in mircookie .. having wrong dependencies
[10:09] <psivaa> anpok_: is this intended to run on wily?
[10:09] <anpok_> vs wily + overlay..
[10:09] <anpok_> ?
[10:10] <psivaa> no, xenial
[10:10] <psivaa> wily vs xenial
[10:12] <anpok_> psivaa: yes, that ci should rather target xenial.
[10:13] <psivaa> anpok_: OK, i'll replace wily jobs for that with xenial ones. It may need to wait for review until my US team members come online
[10:13] <anpok_> I believe the problem is caused by mircookie-dev ..
[10:16] <anpok_> psivaa: we have some private requires dependencies in pkg-config files that werent reflected by dev packages
[10:19] <psivaa> anpok_: That I believe you'll be taking on to fix?
[10:20] <psivaa> anpok_: and you'd want this to target vivid+overlay & xenial, just to confirm?
[10:27] <anpok_> psivaa: yeah .. actually alf_ will fix that through a change in lp:mir and this will be picked up through the mir-staging ppa
[10:27] <anpok_> psivaa: yes.. development target is vivid+o and xenial
[10:28] <psivaa> anpok_: ack, thanks. i'll do the change for targetting  xenial
[13:45] <zsombi> cihelp: huston, we have a problem: UITK is preparing to export a shared library (not a QML plugin as we did so far) and the build system generates some intermediate header files for the build time automatically under $BUILD_DIR/include folder. CI faisl continuously on it when checking the copyright https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/migrate_unity8_gestures/+merge/275146
[14:09] <jibel> bfiller, Hi, has gallery app 1271 approved Friday been published ?
[14:09] <bfiller> jibel: I'm building the click now and will upload to store
[14:09] <jibel> more precisely 2.9.1.1271
[14:09] <jibel> bfiller, ok
[14:09] <bfiller> jibel: should be ready soon
[14:10] <bfiller> jibel: will be rev 1245 as that's the latest in trunk
[14:11] <bfiller> I think the versioning of the click in the silo was not correct..
[14:13] <davmor2> popey: I have an issue. Silo 55 is an atempt to fix the issue with webm, but to me the way it fixes it is to simply drop anything that isn't supported, so as the reporter would expect to see videos that you have on the device even if you can't play them?  Just trying to think if this is the best way round the issue or not
[14:14] <popey> no, hide stuff you can't play
[14:14] <popey> IMO
[14:15] <davmor2> popey: that's fine then
[14:15] <xavigarcia> trainguards, hey guys... can we start landing things for ota-9?
[14:16] <jibel> xavigarcia, not before final freeze of OTA8
[14:17] <bfiller> popey: mind approving new gallery in the store?
[14:17] <popey> sure thing
[14:18] <xavigarcia> jibel: ok... thanks... when is the final freeze... this week, right?
[14:18] <jibel> xavigarcia, tomorrow night
[14:18] <xavigarcia> jibel: cool, thanks!
[14:19] <popey> bfiller, done
[14:19] <bfiller> popey: thanks, jibel gallery all set
[14:19] <popey> np
[14:24] <josepht> zsombi: Are you able to add a "GENERATED" copyright to those intermediate header files?
[14:24] <zsombi> josepht: nope
[14:25] <zsombi> josepht: and the thing is that this is only for build, the install copies the proper files
[14:26] <josepht> zsombi: another option is to have the built headers be placed in one of the directories the license check ignores: excludedirs="(3rd_party|_build)"
[14:27] <josepht> zsombi: is that possible?
[14:27] <zsombi> josepht: we cannot do that, we must obey upstream structure :/
[14:27] <zsombi> zbenjamin: ^
[14:27] <josepht> zsombi: ack, let me chat with fginther` and see if he has any ideas
[14:32] <zbenjamin> zsombi: ack
[14:43] <fginther> zsombi, those license check failures are not comming from anything added by CI. They are generated by a 'license' target in your project's makefile
[14:43] <fginther> zsombi, the A10checklicenseheaders check that is added by CI runs much earlier and didn't flag any files
[14:43] <zsombi> fginther: yes, but we were wondering whether we shoudl exclude the include path freely from our target, as if we do and CI doesn't then we are async.
[14:44] <zsombi> fginther: aaah, ok... zbenjamin: kalikiana: so we can exclude include freely seems
[14:45] <zbenjamin> zsombi: niiiiice
[14:45] <zsombi> zbenjamin: that works at least... ok, fginther, thx for your help!!!
[14:46] <josepht> zsombi: it looks like tests/license/checklicense.sh has some modification that the A10checklicenseheaders does not and vice-versa
[14:47] <fginther> zsombi, A10checklicenseheaders runs before build so it should never see those intermediate files
[14:47] <zsombi> fginther: ai sire, then we can add the exception freely
[14:47] <zsombi> fginther: josepht: thanks guys!
[14:47] <fginther> zsombi, you're welcome
[14:48] <josepht> zsombi: no problem
[14:57] <kalikiana> fginther: has that A10checklicenseheaders change at one point? I was certain it ran after build as we had some issues with generated files... but I could be mistaken. I don't even know where that script is coming from.
[14:59] <fginther> kalikiana, I think it's always been executed prior to build. I believe there are some projects which have generated files committed to the source tree.
[15:43] <fginther> kalikiana, A10checklicenseheaders comes from lp:pbuilderjenkins
[15:45] <kalikiana> fginther: ah. thanks! I'll have a look. so next time I know better what it does.
[16:12] <balloons> ping cihelp. I'd like to get the old core app jenkins, http://91.189.93.70:8080/, disabled completely
[16:13] <josepht> balloons: I'll add a card to trello for that.
[16:14] <balloons> josepht, thank you. I'm keen to test the backup/restore bits as well, and be done with the old system
[16:14] <josepht> balloons: https://trello.com/c/8wjtCHmW/838-vanguard-disable-old-core-apps-jenkins-http-91-189-93-70-8080
[16:14] <balloons> so you can tear it down complete. . .
[16:17] <josepht> balloons: I've taken all of the slaves offline
[16:32] <balloons> josepht, ack, ty
[16:41] <popey> what landed overnight last night? Terminal app has now got a massive font where it previously didn't.
[16:41] <jibel> popey, I noticed that too, probably something that landed last friday.
[16:42] <popey> my krillin is on r167
[16:42] <jibel> popey, there was a new unity/mir last Friday
[16:42] <popey> is there an easy way for me to see what changed that day?
[16:43] <popey> ah
[16:43] <jibel> popey, http://people.canonical.com/~ogra/touch-image-stats/vivid/20151106.1.changes
[16:44] <popey> thanks
[16:44] <jibel> it's on 167
[16:44] <jibel> I'll try 166
[16:46] <popey> jibel, my nexus 4 is still on r282 (8/11/2015) and shows massive font too
[16:46] <popey> oh, probably same as 166
[16:52] <popey> jibel, https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1514519 (cc mhall119 )
[16:55] <popey> is there a landing meeting in 5 mins?
[16:55] <jibel> popey, I don't think so unless you really want to do one
[16:55] <popey> no, just checking because my current call is overrrunning :)
[16:56] <popey> -r
[16:56] <jibel> popey, that's fine, we can skip the landing meeting
[17:04] <jibel> popey, I confirm it's a regression in 167
[17:04] <popey> ok, thanks.
[17:05] <popey> we need a task for whatever it was that landed in that image (i.e. not terminal)
[17:06] <mhall119> thanks popey
[17:07] <jibel> Saviq, bug 1514519 might be due to the unity8/mir landing last friday, can someone have a look?
[17:41] <robru> kenvandine: hey, does the package in silo 0 have autopkgtests?
[17:42] <kenvandine> no
[17:42] <robru> kenvandine: are you aware of any silos that have packages that have autopkgtests? I have some autopkgtest stuff I need to try out in production for the first time
[17:43] <kenvandine> not current silos
[17:43] <robru> k
[17:43] <kenvandine> but if you need to test something, content-hub has tests
[17:44] <kenvandine> we could create a silo to test :)
[17:44] <robru> kenvandine: oh if you can that'd be great
[17:44] <kenvandine> happy to help
[17:44] <robru> thanks
[17:45] <robru> kenvandine: I just have to make some breakfast, can you ping me once the new content-hub silo is built?
[17:45] <kenvandine> robru, sure, after it's built?
[17:45] <jibel> robru, mediascanner2 in silo 55 has autopkgtests
[17:48] <kenvandine> that's good, because bileto blew up when i tried to build content-hub in silo 44 :)
[17:49] <robru> ugh
[17:50] <robru> kenvandine: ok nm I'll fix that quick
[17:50] <robru> jibel: thanks
[17:51] <kenvandine> robru, should i delete the silo?
[17:52] <robru> kenvandine: yeah
[17:52] <rvr> popey: ping
[17:52] <popey> hello rvr
[17:52] <rvr> popey: I tested and approved the calculator update
[17:52] <rvr> popey: Forgot to ping you
[17:52] <popey> Awesomesauce!
[17:52] <popey> Thank you!
[17:52] <popey> That's a great end to my day. Appreciate it!
[17:52] <rvr> popey: I'm now with reminders
[17:53] <popey> ... which could now still go downhill ;)
[17:55] <kenvandine> popey, shutdown your computer and walk away now :)
[17:56] <popey> tempting :)
[17:57] <jibel> robru, do you know why indicator-sound is qa granted since Nov. 5th but not landed? https://requests.ci-train.ubuntu.com/#/ticket/528
[18:00] <robru> jibel: 1. nobody ever clicked publish. 2. there's some comment about it needing a rebuild and then no rebuild ever happened, so i doubt the silo is in any kind of releasable state. I'd ask Mirv for more info
[18:00] <robru> or maybe I misread the comment, maybe it is ready...
[18:00] <robru> brb
[18:06] <kenvandine> robru, what's up with the exception in silo 0?
[18:07] <robru> ugh
[18:07] <robru> kenvandine: I've apparently botched this rollout horribly
[18:07] <jibel> alecu, ^^ do you know what it the status of https://requests.ci-train.ubuntu.com/#/ticket/528 and if it is releasable?
[18:07] <kenvandine> :)
[18:09] <robru> kenvandine: what happened was I made an architectural shift and deleted a bunch of methods that I was sure weren't used anymore but apparently they're still used.
[18:09] <robru> kenvandine: fixes in trunk, should hit production in ~10
[18:10] <kenvandine> :)
[18:11] <alecu> jibel: after the QA ack, that silo got NACKd by cyphermox, because it's used in the desktop, but it adds new dependencies that are not in main.
[18:12] <alecu> jibel: we tried splitting the deps because they were only used by the tests during the build
[18:12] <alecu> jibel: but it did not got there in time, and the silo adds many very visible strings, and it was already past string freeze.
[18:13] <alecu> jibel: so, xavi is trying to find a solution for the dependency issues, and then will try to land it very early in the OTA-9 cycle.
[18:14] <robru> kenvandine: oh, but the failure in silo zero happened when it was attempting to mark the silo successfully built, so you can consider silo 0 to be 'Packages built.'
[18:15] <kenvandine> robru, yeah, i already told tiago he can start testing it
[18:21] <jibel> alecu, ah right, forgot all the details. Thanks
[18:21] <alecu> jibel: sure, no worries. I just added a comment about that to the silo
[18:21] <rvr> popey: I cannot create a notebook with a single word as title, needs an space. We had a similar problem with the notes, that was solved.
[18:24] <robru> brb
[18:30] <anpok> davmor2: hm wrt to landing-056 .. there is a problem and it is in usc...
[18:32] <anpok> davmor2: should I add usc to the silo.. or can we land libinput independently (as of now nobody uses it by default)
[18:51] <davmor2> anpok: no because if someone decides to use it and it breaks then it is no use to anyone, better that it lands fully fixed
[18:58] <robru> slangasek: skip landing team meeting since sil is off and we just had a sprint anyway?
[19:01] <slangasek> robru: yah
[19:02] <robru> k
[19:06] <robru> brb again
[19:26] <boiko> trainguards: can someone please trigger an amd64 rebuild of telephony-service in silo 25?
[19:33] <robru> boiko: one sec
[19:34] <boiko> robru: thanks
[19:36] <robru> boiko: you're welcome!
[21:01] <jgdx> alesage, hey, what's the cursor insertion pattern? :)
[21:02] <alesage> jgdx, find myself backspacing through an existing entry in order to enter a new #
[21:03] <alesage> jgdx, don't know if we have a better pattern for that, e.g. full highlight
[21:03] <alesage> jgdx, but again this is me being a cranky QE :)
[21:17] <jgdx> alesage, are we talking System Settings?
[21:18] <alesage> jgdx, yes in the call-waiting/forwarding entries
[21:18] <jgdx> alesage, oh, why'd you need a #?
[21:18] <jgdx> lol number
[21:18] <jgdx> right.. it's late here :p
[21:19] <jgdx> alesage, if you file a bug for it, I'm sure design will take another look at the spec.
[21:19] <alesage> jgdx, an entry exists, e.g., but my desired forwarding number has changed, e.g.
[21:19] <alesage> jgdx, ack, maybe a bit too finicky even for a bug
[23:15] <robru> slangasek: hey can you bump the priority of this rt? A couple things i need to do are blocked by this https://portal.admin.canonical.com/86110
[23:37] <Trevinho> robru: it looks like ci-train has some troubles in loading here... ANd i got a "0 error"
[23:38] <robru> Trevinho: what url?
[23:38] <Trevinho> robru: on create first then on main
[23:39] <robru> Trevinho: what do you mean? were you not able to make a new request at all?
[23:39] <Trevinho> robru: it went ok now, but before it didn't go
[23:39] <Trevinho> robru: yep, it hanged...
[23:40] <slangasek> robru: what specifically is this blocking?
[23:41] <robru> slangasek: the staging instance can't be deployed because it tries to install those packages and fails in trusty
[23:41] <robru> slangasek: also means I can't do production rollouts...
[23:41] <slangasek> robru: er, but that can be fixed by backing out your change to trunk
[23:41] <slangasek> so should not block you
[23:42] <slangasek> and I wouldn't think those changes should be landed to trunk before they're deployable (i.e. the RT should be done first)
[23:43] <robru> slangasek: ok, but that RT says itself it's a small amount of work and I filed it thursday. would be great if that could just go in
[23:43] <robru> rather than undoing work I've already done
[23:44] <robru> Trevinho: sounds intermittent, like a network issue. looks like you have the request no?
[23:44] <slangasek> robru: that is nevertheless not an argument for bumping the priority for the ticket - which for me to do, I want to understand what functionality is tied to these new dependencies so I can set a proper priority
[23:45] <robru> slangasek: it's just to do with gating MPs to trunk with pylint. that part is already set up and working in s-jenkins (because s-jenkins uses our backport PPA rather than trusty-cat-ue)
[23:45] <robru> slangasek: doesn't actually add any features or anything to production, it's just that the charm installs all those deps and breaks in production
[23:48] <slangasek> robru: well, then I definitely think you should back it out of trunk instead of us raising the priority of an RT
[23:48] <robru> slangasek: ok