[09:16] <Saviq> jibel, hey, what's the verdict on https://requests.ci-train.ubuntu.com/#/ticket/877 - will you guys be testing it for OTA9.5 or not? (/me lost in when was the image supposed to be spinned)
[09:20] <jibel> Saviq, it's in the list of updates to land when it's ready.
[09:20] <jibel> Saviq, the image was supposed to be ready Friday night but there are still lot of landings in the pipe for today
[09:21] <Saviq> jibel, it won't show up in your "QA Ready" queue automagically, I mentioned on Friday that we've one last flaky test that Britney marked a Regression now
[09:22] <Saviq> but I would rather not block that silo on that, if possible - it's our first silo that has Pass elsewhere anyway
[09:26] <Saviq> jibel, would you be willing to overlook the Britney result (since there's no way to restart...), we'll have a fix for the test with the next silo
[09:26] <sil2100> hm, right, no retry button in the train version of Britney
[09:29] <sil2100> morphis: hey! You back again with us? :) We'd need silo 45 ready for QA today and, of course, the bluetooth issues on mako solved
[09:30] <morphis> sil2100: hey, yeah, I am back :-)
[09:30] <morphis> sil2100: then let me approve silo 45
[09:31] <jibel> Saviq,the failure is with unity8 and the new gsettings-ubuntu-touch-schemas. Are you sure it's a flaky test?
[09:32] <morphis> sil2100: you have a bug url for the mako bluetooth issue?
[09:33] <jibel> sil2100, google don't like me today
[09:34] <Saviq> jibel, yes, see it passed on xenial, and it's known to be flaky
[09:34] <Saviq> we've even a fix for it in that silo, but apparently not enough
[09:34] <sil2100> morphis: sure, LP: #1539566
[09:34] <ubot5`> Launchpad bug 1530807 in indicator-bluetooth (Ubuntu) "duplicate for #1539566 Bluetooth cannot be activated on Nexus 7" [High,Confirmed] https://launchpad.net/bugs/1530807
[09:34] <sil2100> jibel: we're waiting, no worries ;)
[09:35] <morphis> sil2100: which is a indicator bug ...
[09:35] <morphis> assigned to charles
[09:35] <sil2100> hmm, ok, this changed, my last understanding was: "introduced by hybris"
[09:42] <morphis> sil2100: who said that?
[09:47] <sil2100> morphis: ok, so it seems someone mistakingly duped the bug
[09:47] <sil2100> morphis: this is the right one: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539566
[09:47] <ubot5`> Launchpad bug 1539566 in Canonical System Image "Bluetooth dead on mako and flo." [Critical,New]
[09:48] <morphis> sil2100: I see
[09:48] <jibel> Saviq, is bug 1536714 as part of silo 19?
[09:48] <ubot5`> bug 1536714 in Canonical System Image "Fix the user login experience on the greeter" [Critical,Confirmed] https://launchpad.net/bugs/1536714
[09:51] <morphis> sil2100: on it
[10:06] <jibel> Saviq, ^ FYI, I forced 'ready for qa'
[10:33] <morphis> sil2100: ping
[10:38] <sil2100> morphis: pong
[10:38] <morphis> sil2100: looks like silo 12 isn't really landed yet
[10:38] <morphis> MPs aren't merged etc.
[10:38] <sil2100> Oh?
[10:39] <sil2100> Ok, it's blocked in -proposed
[10:39] <morphis> sil2100: where can I see that?
[10:39] <sil2100> http://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#libhybris <- kwin, as we discussed
[10:39] <morphis> sil2100: yes, so we're blocked on them dropping the dependency?
[10:40] <sil2100> Yeah, I guess we'd need them to upload that ASAP
[10:40] <sil2100> I could force-merge the silo now, but this needs to be resolved anyway
[10:41] <morphis> sil2100: I need to do another MP for bluetooth-touch
[10:41] <morphis> I can just mark the other MP as prerequisite
[10:52] <morphis> sil2100: ok, that not-merged MP prevents me now from generating a new package in another silo as it wants the version we released to the overlay ppa already in the changelog
[10:53] <sil2100> morphis: could you poke the kwin guys to fix that ASAP?
[10:53] <sil2100> I mean, we don't have to wait for them to do that, but I want the package to be unblocked as soon as possible
[10:53] <morphis> sil2100: I did already over in #kubuntu-devel
[10:54] <morphis> sil2100: but no sign yet
[10:54] <sil2100> Ok, if you'll be the guard of this happening, I'll force-merge the silo as it's critical for us, but I don't want hybris to be blocked in -proposed for too long
[10:56] <sil2100> morphis: did you check the autopkgtest output to make sure that this is the reason for the failure?
[10:57] <morphis> sil2100: basically kwin fails to compile its hybris support
[10:57] <sil2100> Ok, yeah, saw complile failures, but if it's the hybris bits then ok
[10:59] <sil2100> Force merging
[11:01] <sil2100> Arghhh
[11:02] <sil2100> morphis: could you make phablet-team or something similar the owner of lp:bluetooth-touch ?
[11:02] <morphis> sil2100: sure
[11:02] <morphis> sil2100: done
[11:03] <sil2100> morphis: hm, I still see lp:bluetooth-touch is under your LP name, you'd have to change the branch's membership
[11:04] <sil2100> morphis: so 'change branch details' and maybe ownership there would help
[11:04] <sil2100> Since the train needs to have access to the branch
[11:05] <morphis> sil2100: really?
[11:05] <morphis> I though it is just lp:bluetooth-touch
[11:06] <sil2100> morphis: the alias is lp:bluetooth-touch, but currently the branch is lp:~morphis/bluetooth-touch/trunk
[11:06] <morphis> ah
[11:06] <sil2100> So only you can upload to it
[11:06] <morphis> changed that
[11:06] <morphis> https://code.launchpad.net/~phablet-team/bluetooth-touch/trunk
[11:06] <sil2100> \o/
[11:06] <sil2100> THanks, let me re-run the force merge
[11:08] <morphis> sil2100: ok
[11:12] <sil2100> morphis: all should be merged and landed
[11:13] <morphis> sil2100: awesome!
[11:13] <Mirv> I guess someone correctly handled my mistaken xenial builds in 012 from 3h ago by deleting them, maybe it was train and no-one even noticed :)
[11:14] <Mirv> I should have uploaded them to the 011
[11:15] <Mirv> it really looks to me excellent timing and sil2100 didn't notice the last three lines at https://ci-train.ubuntu.com/job/ubuntu-landing-012-3-merge-clean/2/console and even train didn't notice them before deleting them :)
[11:16] <sil2100> uh oh ;)
[11:16] <sil2100> During merge and clean no publishings happen anyway
[11:17] <sil2100> The silo was published last week, it just didn't migrate - so no risk was involved and the train just removed those packages
[11:19] <Mirv> right it do, and I was puzzled when I noticed I had used wrong dput and the silo was even empty when I looked there
[11:19] <sil2100> hah
[11:47] <Saviq> jibel, no, that bug is not part of it
[11:48] <jibel> Saviq, it is still planned for this OTA?
[11:49] <jibel> it's the last remaining critical for 9.5
[11:49] <Saviq> jibel, not on my side, but I've been trying to find out how to set GECOS for the phablet user
[11:49] <Saviq> jibel, but nobody seems to know where does the user creation happen...
[11:49] <Saviq> somewhere during image build, that I know
[11:49] <Saviq> but wasn't able to find out where exactly, and what to change
[11:54] <jibel> Saviq, there apparently http://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk/view/head:/live-build/ubuntu-touch/hooks/01-setup_user.chroot
[11:55] <jibel> this hook is executed during the creation of the rootfs
[11:57] <sil2100> We didn't modify those parts recently
[11:57] <sil2100> At least I don't remember seeing that modified
[11:58] <Saviq> sil2100, well, yeah, we should, we need GECOS on the user :)
[11:58] <Saviq> to say something different than "phablet"
[11:58] <Saviq> sil2100, as per bug #1536714
[11:58] <ubot5`> bug 1536714 in Canonical System Image "Fix the user login experience on the greeter" [Critical,Confirmed] https://launchpad.net/bugs/1536714
[11:59] <sil2100> hm, ok
[12:00] <sil2100> I'll take a look at this bug, but do we know the details of what exactly should it include for phablet?
[12:01] <Saviq> sil2100, "Ubuntu" afaict, let me confirm
[12:12] <Saviq> jibel, sil2100, I tried setting GECOS here and realized there's something missing in the middle as well, still getting just the user name on the greeter
[12:12] <Saviq> so we need to investigate that
[12:12] <sil2100> Saviq: ok
[12:12] <Saviq> but it should be set nevertheless
[12:12] <Saviq> I mean to Ubuntu, for now
[12:13] <sil2100> I can push the changes to the GECOS if needed (just need to know what design wants to be visible there) on the livecd-rootfs side
[14:10] <morphis> sil2100: ping
[14:10] <sil2100> morphis: pong
[14:11] <morphis> sil2100: when we land silo 45 which has vivid/xenial packages for pulseaudio, can we wait with the xenial one a bit more than with the vivid one?
[14:11] <sil2100> morphis: you mean, not releasing it along with the silo?
[14:13] <morphis> if that is possible
[14:13] <morphis> sil2100: I know that davmor2 doesn't want me to touch the silo until he is done with testing but we have to do another change for xenial before we can land it
[14:13] <sil2100> morphis: hm, that might be hard, it's possible but only if we remove the xenial packages from the silo...
[14:14] <sil2100> morphis: but, we can always publish those manually to vivid
[14:14] <sil2100> By manually copying
[14:14] <sil2100> So hm, I guess we could do that
[14:16] <morphis> davmor2: you already started testing silo 45?
[14:19] <davmor2> morphis: I'm not no I already have my hands full with 24 and 19
[14:20] <morphis> davmor2: ok
[14:20] <morphis> sil2100: then we might not need that if I get the pulse package fixed in time :-)
[14:20] <sil2100> Phew ;)
[14:21] <sil2100> Well, we can do it with the manual copies, but I prefer to do full releases as then all the proper history is recorded
[14:23] <rvr> oSoMoN: ping
[14:23] <oSoMoN> rvr, pong
[14:23] <rvr> oSoMoN: I'm testing silo 14... When opening a new tab, top sites and bookmarks are not highlighted by default.
[14:24] <oSoMoN> rvr, is that with a narrow layout or wide one?
[14:24] <rvr> oSoMoN: Wide
[14:24] <rvr> oSoMoN: See screenshot here https://trello.com/c/bJLXKx8T/2715-925-ubuntu-landing-014-webbrowser-app-osomon
[14:25] <oSoMoN> rvr, right, that’s because the address bar has focus by default, which is expected, but if you press the Down arrow key, it should focus the view below
[14:26] <rvr> oSoMoN: Ahh, let me see
[14:27] <oSoMoN> rvr, bug #1539176 is about making the selection highlight more prominent, it’s not about focusing the new tab view by default
[14:27] <ubot5`> bug 1539176 in webbrowser-app (Ubuntu) "highlighting of selected item not visible with external monitor" [Medium,In progress] https://launchpad.net/bugs/1539176
[14:27] <rvr> oSoMoN: Ok
[14:27] <rvr> oSoMoN: Then, approving the silo. Everything else seems ok.
[14:30] <sil2100> Woo
[14:43] <jgdx> ltinkl, hey, any luck chasing down the merge conflicts in silo 51?
[14:43] <ltinkl> jgdx, working on it (the MPs are under review, I had to throw on more into the mix)
[14:46] <jgdx> ltinkl, okay, great.
[14:55] <oSoMoN> rvr, thanks!
[14:57] <oSoMoN> trainguards: the packaging changes in silo 14 were already approved by jdstrand, so it should be good to publish (see https://code.launchpad.net/~osomon/webbrowser-app/bottom-edge-mouse/+merge/284283)
[14:58] <Mirv> oSoMoN: ok
[15:00] <Mirv> found the approval too
[15:00] <sil2100> Look good anyway
[15:43] <morphis> sil2100: ok, fixed silo 45, we can now land it for both
[15:45] <seb128> charles, the indicator publication  failed https://ci-train.ubuntu.com/job/ubuntu-landing-046-2-publish/10/console
[15:45] <seb128> 2016-02-01 15:35:28,969 ERROR Publish failed: Unexpected upload at destination.
[15:46] <seb128> I guess I can override the no change upload from La_ney
[16:07] <Saviq> sil2100, jibel, Bug #1536714 is between unity8 and livecd-rootfs then: https://code.launchpad.net/~mterry/livecd-rootfs/ubuntu-real-name/+merge/284637 https://code.launchpad.net/~mterry/unity8/display-real-name/+merge/284635
[16:07] <ubot5`> bug 1536714 in unity8 (Ubuntu) "Fix the user login experience on the greeter" [Critical,In progress] https://launchpad.net/bugs/1536714
[16:08] <Saviq> jibel, so unless you guys fail silo 15 (please don't!) we'll have to land post-9.5
[16:08] <Saviq> or well, if you fail silo 15 I assume it'd be post-9.5 anyway :P
[16:14] <mterry> Saviq, :(
[16:15] <Saviq> mterry, j/k, it's not looking bad
[16:39] <rvr> morphis: Hi
[16:39] <rvr> morphis: I'm testing pulseaudio (silo 45)
[16:39] <morphis> rvr: oh good
[16:40] <rvr> morphis: This test case fails, both in OTA9 and with the silo, so no regression. Is it known? "turn the bluetooth device off. The audio from music-app should automatically move to the internal speaker"
[16:41] <morphis> rvr: ota9 means you installed the silo not on rc-proposed?
[16:41] <rvr> morphis: Right, OTA9 means "stable" :)
[16:41] <rvr> morphis: I have my own krillin for personal use, and just checked
[16:42] <ltinkl> jgdx, https://requests.ci-train.ubuntu.com/#/ticket/938 building
[16:42] <morphis> rvr: so you have a A2DP speaker or a headset connected, right?
[16:42] <rvr> morphis: Right
[16:43] <rvr> morphis: The audio is placed correctly in the bluetooth speaker
[16:43] <rvr> morphis: But when it's switched off, track doesn't continue to be played in the device
[16:44] <rvr> It stops
[16:44] <morphis> rvr: ah
[16:44] <morphis> that is known
[16:44] <morphis> its the same also for HFP when you do calls
[16:45] <morphis> rvr: but can't find the bug currently
[16:45] <morphis> rvr: but if you play the track again its played from the speaker?
[16:45] <morphis> the internal one I mean
[16:45] <rvr> morphis: Yes, if I tap "play" it continues playing in the device
[16:45] <morphis> good
[16:46] <morphis> then yes, that is a known thing
[16:46] <rvr> Ok
[16:46] <morphis> but would be good if you can file another bug, I will mark it as duplicated if I find the original one
[16:46] <morphis> but its nothing easy to fix as it requires a bigger rework of the actual routing to move streams properly
[16:47] <rvr> Doing it
[16:48] <jgdx> ltinkl, cool!
[16:51] <rvr> morphis: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540478
[16:51] <ubot5`> Launchpad bug 1540478 in pulseaudio (Ubuntu) "Audio not automatically moved to the internal speaker" [Undecided,New]
[16:54] <morphis> rvr: thanks
[17:05] <jgdx> :(
[17:11] <sil2100> rvr, davmor2, jibel: just double confirming - the unity8 silo is good to go, right?
[17:12] <jibel> sil2100, yes, davmor2 is filing bug reports for the issues he found
[17:12] <sil2100> ACK
[17:12] <davmor2> silo 24 and silo 19 are both good to go, but there will be some ota 10 blocking bugs for the issues I found
[17:12] <davmor2> sil2100: ^
[17:12] <sil2100> morphis: could we get https://code.launchpad.net/~morphis/bluetooth-touch/fix-lp1539566/+merge/284575 approved?
[17:15] <sil2100> ARGH
[17:15] <sil2100> The unity8 silo seems to have some issues
[17:16] <sil2100> Saviq: on the first sight of it, looks like the qtmir landing of silo 19 is reverting the latest version of qtmir from the archive (the one that went out with mir 0.19)
[17:16] <sil2100> Saviq: https://ci-train.ubuntu.com/job/ubuntu-landing-019-2-publish/1/artifact/qtmir_xenial_packaging_changes.diff
[17:16] <sil2100> Why is that so?
[17:16] <Saviq> sil2100, ARGH indeed
[17:17] <sil2100> Saviq: did you guys rebuild after mir got merged?
[17:17] <Saviq> sil2100, there's no qtmir in that silo
[17:17] <sil2100> Oh, even weirder
[17:17] <Saviq> sil2100, there was, however
[17:17] <sil2100> Yeah, the train probably took the last one deleted from the PPA
[17:18] <Saviq> sil2100, so it's likely just confused
[17:18] <sil2100> Saviq: ok, so no qtmir is required by this landing, right?
[17:18] <Saviq> sil2100, nope
[17:18] <sil2100> hmm, ok,
[17:18] <sil2100> Fingers crossed it won't publish the deleted one then
[17:20] <sil2100> Saviq: anyway, thanks for clearing it up, didn't expect the diffs will be out of sync with the contents of the silo
[17:22] <rvr> Hmm
[17:22] <Saviq> ;)
[17:22] <Saviq> fingers crossed indeed
[17:22] <rvr> sil2100: I can't set silo 45 to approved
[17:25] <sil2100> rvr: it's probably because the autopkgtests are still starting
[17:25] <sil2100> Saviq: ...so far so good!
[17:26] <jibel> sil2100, no, they ran earlier today:  2016-02-01 16:10:31 +0100 (britney-bot) britney_signoff: Approved
[17:26] <sil2100> Strange
[17:26] <jibel> but the lander and automated signoff disappeared
[17:26] <jibel> sil2100, it seems the silo has been rebuilt
[17:27] <sil2100> Ah
[17:27] <sil2100> Yes, the xenial bits
[17:27] <sil2100> Re-running diff_only
[17:31] <Saviq> sil2100, thanks!
[17:57] <dobey> hmm
[17:57] <dobey> is there a google calendar, or an ics file somewhere on-line, with the ota freeze dates in it?
[18:05] <pmcgowan> dobey, good idea I will add them to the UES calendar
[18:07] <dobey> pmcgowan: well, a separate public calendar might be nice, but sure :)
[18:09] <pmcgowan> dobey, yeah, can check that
[18:58] <sil2100> robru, slangasek: I won't be around for today's meeting, I'm a bit flu-ish today and would like to lay down for a while
[18:59] <slangasek> sil2100: saw your decline, and have cancelled the meeting - thanks, feel better soon!
[19:02] <robru> sil2100: take care
[20:30] <bfiller> robru: any idea what happened to silo 23? stuff in the ppa is not from the silo
[20:30] <bfiller> robru: should be u-d-m and nuntium
[20:31] <robru> bfiller: what ticket are you looking at? https://requests.ci-train.ubuntu.com/#/ticket/944 looks right to me
[20:31] <bfiller> robru: https://requests.ci-train.ubuntu.com/#/ticket/866
[20:31] <robru> bfiller: abandoned jan 27th
[20:32] <bfiller> robru: damn
[20:32] <robru> bfiller: by michael sheldon
[20:32] <bfiller> robru: thanks, will check with him
[20:33] <robru> bfiller: you're welcome
[20:43] <Elleo> bfiller: sorry, thought that just had the udm changes in, not the nuntium ones
[20:43] <Elleo> bfiller: which we'd decided to leave alone since the retry logic was moving to nuntium
[20:44] <bfiller> Elleo: no worries
[21:58] <Saviq> robru, hey, can you please recycle the unity-scope-click regression http://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#unity8 (not sure you're able to, requires Ubuntu upload rights...)
[21:59] <robru> Saviq: yeah, no, I can't
[21:59] <robru> sorry
[21:59] <Saviq> now who do I bug about this then
[21:59] <robru> Saviq: any core dev
[22:01]  * Saviq rolls a dice at https://launchpad.net/~ubuntu-core-dev/+members#active
[22:57] <robru> Mirv: still around? I just rolled out the fix for britney hints, and the log claims that it ran with hints: https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-023/excuses.html but this still looks the same / many regressions. can you double check?
[22:58] <robru> Mirv: oh you can see "but forced by" in the excuses so i guess that means hints are working
[23:05] <michi> trainguards: I have a question… https://requests.ci-train.ubuntu.com/#/ticket/911
[23:06] <michi> This one has passed testing but isn’t showing as having passed.
[23:07] <robru> michi: what, you mean qa? I'm seeing Approved/Approved/Ready
[23:08] <michi> robru: Ah...
[23:08] <michi> So “Ready” means “Approved”?
[23:08] <michi> As in “ready for publication”?
[23:08] <michi> robru: I thought “Ready” meant “Ready for QA testing"
[23:09] <michi> But it’s passed testing: https://trello.com/b/AE3swczu/qa-testing-requests-for-questions-ping-ubuntu-qa-on-ubuntu-ci-eng
[23:09] <robru> michi: ready means ready for qa testing, yes.
[23:09] <robru> michi: I guess whoever approved it forgot to set the ticket
[23:09] <michi> OK, so no misunderstanding then.
[23:09] <michi> robru: This is weird.
[23:10] <michi> Now the card is back to “Ready for testing” in Trello.
[23:10] <michi> Earlier, I found it in the “Passed” column
[23:10] <robru> michi: yeah that's where I see it as well
[23:10] <robru> michi: maybe it was a mistake? ask a qa person
[23:10] <michi> OK, so maybe it was accidentally moved.
[23:10] <michi> Yes.
[23:10] <michi> My apologies for the noise.
[23:10] <robru> no worries
[23:20] <robru> brb
[23:42] <sil2100> ^ overriding that, critical landing... eh, need to talk with morphis about those
[23:43] <sil2100> o/