[04:32] <bzoltan> is here anybody who knows (remembers) how to convince mako to keep adb available even when the screen is locked? Flashing the latest rc-proposed + touching /userdata/.adb_onlock does not make it.
[04:32] <bzoltan> robru: ^
[04:34] <robru> Uhhh
[04:35] <robru> bzoltan: i dunno. Maybe jibel or fginther might know more about the device side.
[04:37] <bzoltan> robru: thank you.. hopefully someone can help.. it would be nice to put my mako back to work as contnious testing agent ...
[04:38] <bzoltan> I remember ogra mentioned that we might need a special firmware for this... but not sure
[04:39] <robru> bzoltan: maybe ask cihelp if they can share the secret of how they test with devices.
[04:40] <bzoltan> robru: for Mirv it works
[04:41] <Mirv> yeah for some reason I don't have that problem, and I've been flashing a lot again now this week.
[04:41] <robru> bzoltan: Mirv should be around soon
[04:43] <bzoltan> robru:  he is :) already
[05:13] <iahmad> evanwang, ping
[05:13] <evanwang> iahmad, pong
[05:20] <evanwang> iahmad, failed to connect canonical irc server from our site, how is the connection from you site?
[05:20] <iahmad> evanwang, working for me
[05:21] <evanwang> iahmad, seems something wrong at our site :(
[06:09] <bzoltan> robru: Mirv: this failure seems to be serious -> https://launchpadlibrarian.net/218108553/buildlog_ubuntu-wily-amd64.ubuntu-ui-toolkit_1.3.1639%2B15.10.20150916.2-0ubuntu1_BUILDING.txt.gz  "/usr/bin/ld.gold: --push-state: unknown option"
[06:10] <Mirv> bzoltan: FYI robert is on vacation
[06:11] <Mirv> bzoltan: eh..
[06:11] <bzoltan> Mirv:  ohh... i am sorry robru
[06:12] <Mirv> bzoltan: I have never seen that
[06:12] <bzoltan> Mirv:  me neither... it is new to me
[06:16] <Mirv> let's see if anyone else has that on devel
[07:20] <dbarth> mardy: hi
[07:21] <dbarth> mardy: about facebook, i think the solution is to get a pro account
[07:21] <mardy> dbarth: hi!
[07:21] <mardy> dbarth: let's wait a bit, I'm discussing the issue in the forums
[07:21] <dbarth> mardy: i saw a link that offers to go pro, and then you get an "account manager", ie a human, to help with the review
[07:21] <dbarth> ah, do you?
[07:21] <dbarth> do you have a pointer, are they replying ?
[07:22] <mardy> dbarth: some users are replying, but I believe that one might actually be a facebook employee
[07:22] <mardy> dbarth: https://www.facebook.com/groups/fbdevelopers/
[07:40] <dbarth> mardy: i can't find the link to that pro contact, as it was linked from the failed review page
[07:41] <mardy> dbarth: yes, it disappeared. But let's wait for the results of this review
[07:42] <sil2100> pete-woods: hey! Did you manage to test the package from the silo I pasted yesterday? :)
[07:43] <dbarth> mardy: but if next time it fails please keep it as is, and we will check that path
[07:44] <pete-woods> sil2100: sorry, I didn't read my scrollback
[07:44] <pete-woods> will have a look now
[07:44] <mardy> dbarth: ok
[07:45] <pete-woods> sil2100: just snapshotting the VM now
[07:45] <sil2100> Thanks :) I doubt this will work, but at least we'll know that the latest is needed
[07:46] <pete-woods> asdas
[07:46] <pete-woods> whoops
[07:46] <pete-woods> that's fine
[07:46] <pete-woods> happy to do exploratory testing of it
[07:58] <pete-woods> sil2100: the PPA seems to fix the problem! :)
[08:00] <sil2100> pete-woods: uh oh!
[08:00] <sil2100> Who would have thought, a no-change rebuild
[08:00] <pete-woods> sil2100: is that a bad thing?
[08:00] <sil2100> pete-woods: it's good, just didn't expect that ;p
[08:01] <sil2100> Let me copy it to the overlay then
[08:03] <pete-woods> thanks
[08:22] <bzoltan> Mirv: ehh... 2015-09-17 08:19:47,420 ERROR dch: fatal error at line 1141:
[08:22] <bzoltan> New version specified (1.3.1639+15.04.20150917-0ubuntu1) is less than
[08:22] <bzoltan> the current version number (1.3.1639+15.10.20150916-0ubuntu1)!  Use -b to force.
[08:23] <sil2100> bzoltan: yeah, that happens when you want to turn a wily trunk into a vivid one - what do you want to release exactly?
[08:23] <bzoltan> sil2100:  I want a dual landing like normally.. but wily is blocked so I could settle with a vivid only
[08:24] <Saviq> cihelp, hey, it looks like unity8's autopilot on wily/mako is busted, ENOSPC when installing dependencies http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-runner-wily-mako/380/console
[08:27] <Mirv> sil2100: there's a bug #1496743 introduced by new GCC 5 in wily, not sure how it should be fixed
[08:27] <ubot5> bug 1496743 in qtbase-opensource-src (Ubuntu) "/usr/bin/ld.gold: --push-state: unknown option" [Undecided,New] https://launchpad.net/bugs/1496743
[08:29] <psivaa> Saviq: I dont think i saw this on Mako before,  would need to take a closer look. How urgent is this?
[08:29] <psivaa> i.e. can this wait until late this afternoon?
[08:29] <Saviq> psivaa, yeah
[08:29] <psivaa> Saviq: ack, thanks
[08:30] <Saviq> psivaa, apparently an issue for quite some time now, but we didn't pay close enough attention to wily http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-runner-wily-mako/376/console
[08:30] <psivaa> Saviq: right, i see
[08:31] <psivaa> Saviq: will add this to the list. We'll look into it
[08:31] <Saviq> psivaa, thanks
[08:31] <Saviq> psivaa, likely the wily image just grew too much
[08:42] <Saviq> trainguards, can we please have publish on https://requests.ci-train.ubuntu.com/#/ticket/359 ?
[08:43] <sil2100> Saviq: on it
[08:53] <sil2100> dobey: hey! Looking at silo 29 now - did those changes land in wily already, or are there any reasons for it not to work there?
[09:04] <sil2100> ogra_: hey! :) I want to upload the new ubuntu-touch-meta source to wily that includes the new pocket-desktop seed - can I have you looking at the debdiff before I upload it?
[09:05] <ogra_> sil2100, after the mtng i'm currently in
[09:05] <sil2100> ogra_: thanks, let me prepare teh diff
[09:06] <sil2100> ogra_: the debdiff - the changes are rather straightforward: http://paste.ubuntu.com/12436400/
[09:06] <sil2100> The generated meta package has proper deps
[09:20] <ogra_> sil2100, the diff looks ok to me
[09:20] <sil2100> ogra_: thanks :)
[09:37] <Laney> is there such a thing as deleting a request?
[09:37] <Laney> (not assigned)
[09:37] <Laney> or do they just stay foreverrrrrrrr
[09:37] <sil2100> Damn, using SUBPROJECT in livecd-rootfs is soo tempting, making ubuntu-pd a separate project would mean sooo much copy & paste
[09:37] <sil2100> Laney: yeah, there's a manual method for that
[09:38] <sil2100> Laney: you edit the request and change its status manually to 'Abandoned'
[09:38] <sil2100> (that's the official way to do it)
[09:38] <Laney> which drop down has that?
[09:38]  * Laney can't find it
[09:39] <sil2100> Laney: it's the 'Status' field, no drop-down there
[09:39] <sil2100> Laney: if you hover over it it says 'Do not touch, auto updated', but that's just for already assigned silos
[09:39] <Laney> ok, I did that, thanks!
[09:39] <sil2100> yw!
[09:39] <Laney> no silos :(
[09:39] <sil2100> Oh! Let me free up mine
[09:41] <sil2100> Laney: silo 35 should be free now
[09:41] <Laney> thanks
[09:41] <sil2100> Ugh, that's a bug that needs to be fixed ^
[09:41] <Laney> it's like building more roads eh
[09:42] <Laney> seb128: on the no free silos, the libusermetrics one failed to clean, do you know why?
[09:45] <Saviq> sil2100, I remember reading something about boot failures in wily, will the boottest failure prevent migration? http://people.canonical.com/~ubuntu-archive/proposed-migration/wily/update_excuses.html#unity8
[09:50] <seb128> Laney, no, I don't
[10:52] <sil2100> Saviq: I think it will... boottests currently are a bit a pain in the ass
[10:53] <Saviq> sil2100, how do we deal with that?
[10:53] <Saviq> FWIW the unity-scope-click tests seem to take a long time, too
[10:53] <Mirv> sil2100: any idea about the part of 029 that it claims it requires qtmir from 027 but davmor2 approved 029 anyway so apparently nothing hugely crashy?
[10:54] <sil2100> Mirv: not sure, I was waiting for dobey to comment on this landing, since I didn't know if the same things landed in wily already or not
[10:54] <sil2100> Mirv: btw. do you have power to re-run boottests?
[10:54] <sil2100> Saviq: I think this requires cihelp, but from what I know currently boottests are unmaintained really ;/
[10:57] <psivaa> sil2100: Saviq: Which job is this?
[10:57] <Mirv> sil2100: yes, just give me boottest urls
[10:57] <psivaa> or package
[10:57] <Saviq> psivaa, unity8
[10:57] <Saviq> psivaa, http://people.canonical.com/~ubuntu-archive/proposed-migration/wily/update_excuses.html#unity8
[10:57] <Mirv> sil2100: but some of them are pretty permanently failing (lately) so needs psivaa anyway
[10:59] <psivaa> Saviq: i've kicked this off again, and watch it
[10:59] <Saviq> psivaa, thanks
[11:01] <psivaa> Saviq: Sorry for this long txt, regarding previous failure:
[11:01] <psivaa> "Tested this manually and found that the UI does not come up when testing unity8. The device is accessible via 'adb shell' so it does pass the basic boottest requirement, it's just failing on the adt-run check for a working UI.
[11:01] <psivaa> The device did come up fully when the rest of the silo containing unity8 was installed. This points to a missing dependency. I discussed this with the unity8 team and this was expected and the silo will all be promoted together."
[11:02] <davmor2> Mirv: I can look at 27 now but everything worked like it has before.
[11:04] <Saviq> psivaa, I think this was resolved by now
[11:04] <psivaa> Saviq: ack, let me see if the rerun works
[11:07] <Saviq> psivaa, btw, (where) can I monitor adt runs in progress? like the unity-scope-click ones from http://people.canonical.com/~ubuntu-archive/proposed-migration/wily/update_excuses.html#unity8
[11:08] <Mirv> davmor2: ok. it's not yet set ready for QA though.
[11:08] <Mirv> davmor2: oh, it is, sorry
[11:08] <psivaa> Saviq: http://d-jenkins.ubuntu-ci:8080/view/Wily/view/BootTest/job/wily-boottest-unity8/23/console, but this would not show anything until the job actually finishes
[11:08] <rvr> abeato: ping
[11:09] <davmor2> Mirv: its' in our queue :P
[11:09] <abeato> rvr, pong
[11:09] <rvr> abeato: Regarding the failures...
[11:09] <rvr> abeato: Can you confirm they work well in your case?
[11:10] <abeato> rvr, call forwarding works fine for pepephone
[11:10] <rvr> abeato: I also had problems with USSD
[11:11] <abeato> rvr, hmm, I tried some ussd strings for vodafone and all looked one
[11:11] <abeato> *good
[11:11] <abeato> rvr, what failed?
[11:12] <rvr> abeato: The first case of the test plan
[11:13] <rvr> abeato: I got an unsupported error
[11:13] <abeato> rvr, which ussd string and which operator?
[11:15] <rvr> abeato: Yoigo
[11:15] <rvr> abeato: “*118#”
[11:17] <abeato> rvr, ussd strings are operator-specific, “*118#” works only for vodafone (ES), I'll make that more explicit in the test
[11:17] <rvr> abeato: Ahh
[11:18] <rvr> abeato: Ok, I see... googling for yoigo's ones
[11:19] <Saviq> psivaa, that's only boottest, how about the package ones?
[11:19] <psivaa> Saviq: you mean 'autopkgtest' ?
[11:20] <Saviq> psivaa, yeah, like unity8 is waiting for unity-scope-click results for a few hours now
[11:20] <psivaa> if that's the case that's now handled by the release team, I think.
[11:20] <Saviq> wanted to check what's going on
[11:20] <Saviq> right
[11:20] <abeato> rvr, if you find something for yoigo please add that to the test case
[11:21] <abeato> rvr, note that ussd codes are for services like asking your balance, data consumed,etc. some time operators use different means for that (say, sms), so maybe yoigo does not have ussd strings
[11:39]  * sil2100 jumps out for some lunch groceries
[11:49] <rvr> abeato: send-ussd "*111#" dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.ofono.SupplementaryServices" doesn't exist
[11:50] <abeato> rvr, is that krillin
[11:50] <abeato> ?
[11:50] <abeato> rvr, if that's the case try "send-ussd  /ril_0  "*111#""
[11:52] <rvr> abeato: Yes, krillin
[11:52] <rvr> It worked... somehow USSD: Yoigo Info: Este servicio no esta disponible para clientes de contrato.
=== alan_g is now known as alan_g|lunch
[12:02] <rvr> Google results are crappy lately
[12:17] <rvr> abeato: I can't check the USSD menu test, and "3. Receive a USSD notification" fails for me
[12:17] <rvr> abeato: I don't see "{SupplementaryServices} [/ril_0] NotificationReceived" in the logs
=== alan_g|lunch is now known as alan_g
[13:14] <abeato> rvr, in krillin you need to specify which modem slot to use when executing the script, that's why you need either /ril_0 or /ril_1 as argument
[13:15] <dobey> sil2100: hmm?
[13:15] <abeato> rvr, for the third test you need an operator that provides those notifications, again, that's operator specific
[13:15] <abeato> rvr, and that's not very common, I know only Tesco UK as an operator that does that
[13:16] <dobey> sil2100: what's the problem with 29?
[13:19] <dobey> sil2100: anyway, yes, the changes there are already in wily
[13:20] <sil2100> dobey: excellent
[13:20] <sil2100> That's what I wanted to know
[13:21] <Saviq> psivaa, any word on the boottest? and any idea who can I ask about autopkgtests?
[13:23] <sil2100> ogra_: heeeey, I know you're probably super busy as always, but - could you maybe take a look at this merge? :) https://code.launchpad.net/~sil2100/livecd-rootfs/pocket-desktop/+merge/271448
[13:24] <sil2100> ogra_: I know I'm pushing on this subproject idea a bit too much, I can seriously change that to a separate project, just want to know if there are any objections to do it this way - as the change now is only 3 lines
[13:31] <psivaa> Saviq: still looking at the boottest issue
[13:32] <psivaa> afaik, pitti was handling the autopkgtests
[13:37] <pstolowski> hey trainguards, any idea what's wrong with silo 35 - https://ci-train.ubuntu.com/job/ubuntu-landing-035-1-build/55/console ?
[13:39] <sil2100> pstolowski: hmm, strange, looks like there's a problem with dh, even though I see it in the Build-Depends
[13:41] <sil2100> pstolowski: ah, maybe the change wasn't there when the silo was built?
[13:41] <sil2100> pstolowski: since I don't see the train installing debhelper
[13:44] <pstolowski> sil2100, no, debhelper was definately there. note however that i'm testing some crazy stuff in this silo (control file is re-generated from control.in)
[13:45] <pstolowski> let me try to rebuild just in case
[13:49] <sil2100> kenvandine: hey! Could you take care of https://ci-train.ubuntu.com/job/ubuntu-landing-029-2-publish/45/ ? I have no power here ;)
[13:51] <pstolowski> sil2100, hmm, failed, debhelper should be installed, see the MP https://code.launchpad.net/~stolowski/unity-scopes-shell/singletree/+merge/271314
[13:51] <kenvandine> sil2100, sure
[13:51] <sil2100> kenvandine: thanks :)
[13:53] <sil2100> pstolowski: interesting... it seems as if the train is unable to find any build deps
[13:53] <sil2100> Let me check this locally here
[13:58] <pstolowski> sil2100, we did same trick in singletree branch of unity-scopes-api, and it worked
[14:05] <kenvandine> sil2100, exception while publishing
[14:11] <sil2100> pstolowski: indeed, so far everything looks fine, but somehow it's not resolving the missing build-deps
[14:11] <sil2100> kenvandine: ouch
[14:13] <rvr> awe_: abeato: Approving the silo
[14:14] <awe_> thanks rvr!
[14:14] <abeato> rvr, \o/ thanks
[14:19] <kenvandine> sil2100, let me know if you need me to try to publish that again
[14:23] <sil2100> kenvandine: thanks, I see the packages have reached the destination so I just merge&cleaned it
[14:23] <kenvandine> oh, cool
[14:28] <dbarth> hey there, i can't find that in the faq, but is there a quick way to force rebuild a package in a silo from bileto?
[14:28] <dbarth> ie, i would do a null merge-proposal or something, but is there something cleaner
[14:28] <dbarth> this is to get a new build of a webapp-container, with the newer platform-api lib we have in a silo
[14:36] <sil2100> dbarth: I think the no-change MP is the fastest, not counting poking someone to prepare the package manually ;)
[14:37] <dbarth> aye aye sir
[14:49] <dbarth> gnn
[15:00] <pstolowski> sil2100, is "debconf: delaying package configuration, since apt-utils is not installed" relevant for that failure in silo 35?
[15:25] <pstolowski> sil2100, btw, any news on silo 10? can we get somebody to push the magic button? ;) we need to that in asap, it's blocking other stuff...
[15:26] <sil2100> pstolowski: poking!
[15:59] <fginther> Saviq, hello, any suggestions on the unity8 wily phone test running out of space?
[15:59] <Saviq> fginther, only thing I can think of is that the wily image grew too much for the unity8 autopilot dependencies to fit on top
[16:01] <fginther> Saviq, that's what I thought too. I don't know if there is anything we can do in CI to make this work... I think we just need a resized or cleaned up image
[16:01] <Saviq> fginther, yeah most likely, we need a bug and some investigation to happen
[16:02] <fginther> Saviq, If the test is of no use, can we disable it for now to free up the resources?
[16:02] <Saviq> fginther, let me just confirm this is what's happening
[16:03] <fginther> Saviq, thanks
[16:03] <jibel> sil2100, is there a landing meeting?
[16:04] <davmor2> sil2100: popey meeting????
[16:04] <sil2100> Oh crap!
[16:04] <sil2100> Be right there
[16:04] <Saviq> I've 500MB free on a freshly installed wily (dual booted, though)
[16:07] <psivaa> Saviq: btw, http://people.canonical.com/~ubuntu-archive/proposed-migration/wily/update_excuses.html#unity8 is not having boottest PASS.
=== nuclearbob is now known as nuclearbob_lunch
[16:15] <Saviq> psivaa, "now" you meant? thanks, anything we should do or is this going to be better now?
[16:16] <Saviq> now, in absence of pitti, who can help with autopkgtests being stuck in "Test in progress" for the whole day? :/
[16:17] <psivaa> Saviq: yes, 'now'. Sorry finger memory.
[16:17] <fginther> Saviq, I think psivaa meant "now" (as it does show a PASS)
[16:18] <psivaa> Saviq: this unity8 failure is tricky, as we're testing with an older image (191). With the latest one the provisioning is not very complete
[16:19] <Saviq> fginther, "75 upgraded, 127 newly installed, 6 to remove and 412 not upgraded.
[16:19] <Saviq> Need to get 150 MB/168 MB of archives.
[16:19] <Saviq> After this operation, 577 MB of additional disk space will be used.", there's less than .5GB free on wily
[16:19] <Saviq> fginther, I wonder why that list is so big...
[16:20] <Saviq> like g++, really?
[16:20] <Saviq> looks like unity-scope-tool has excessive deps
[16:21] <Saviq> let's see if we can drop that, and/or fix it
[16:21] <sil2100> seb128: hey! Did you get any news regarding the libusermetrics regression?
[16:22] <greyback_> trainguards: any reason silo27 hasn't been landed? QA was granted.
[16:24] <sil2100> greyback_: will land in a minute if possible, just still working on something
[16:24] <greyback_> sil2100: no biggie, just curious
[16:35] <seb128> sil2100, there is a fix approved on https://code.launchpad.net/~mterry/unity8/handle-empty-infographic-label/+merge/271479
[16:35] <sil2100> seb128: would it be able to land today?
[16:40] <seb128> sil2100, don't ask me, I'm not maintaining unity8
[16:40] <seb128> Saviq & co probably know?
[16:40] <sil2100> seb128: ok, thanks for the info ;)
[16:40] <sil2100> Saviq: hey!
[16:41] <seb128> yw
[16:41] <Saviq> sil2100, here, whatup?
[16:41] <sil2100> Saviq: any ETA on mterry's branch ^ to land? :)
[16:42] <sil2100> The one seb128 pasted above
[16:42] <Saviq> sil2100, we've an approved branch for that
[16:42] <Saviq> sil2100, we'll land soon
[16:43] <sil2100> Saviq: you know if that's possible today still?
[16:43] <Saviq> sil2100, no, we're stuck in proposed since this morning
[16:43] <Saviq> because unity-scope-click autopkgtests are endlessly In Progress
[16:43] <sil2100> Ok, so I'll soft-revert the libusermetrics landing in the overlay and then re-release once unity8 is out
[16:43] <sil2100> Uuugh
[16:47] <Saviq> fginther, ok seems we can drop unity-scope-tool, which is the reason all the packages are pulled in, from the job conf, let me try a run without it
[16:47] <Saviq> we need to fix that in any case
[16:50] <Saviq> or is there a reason why all the packages are explicitly installed?
[16:51] <Saviq> fginther, this is the stripped-down run, let's see how it goes http://s-jenkins.ubuntu-ci:8080/job/unity8-ci/6290/console
=== pstolowski is now known as pstolowski|eod
=== alan_g is now known as alan_g|EOD
[17:02] <cjwatson> Saviq: pitti was saying earlier today that it's just processing a long queue
[17:03] <Saviq> cjwatson, anywhere we can see that?
[17:03] <cjwatson> dunno sorry
[17:06] <Saviq> tx anyway, let's hope it sorts itself out then
[17:07] <sil2100> kenvandine: could you publish the two silos that are ready for release? Those are dual silos so with th e current train bug I can't publish them...
[17:07] <sil2100> kenvandine: https://requests.ci-train.ubuntu.com/#/trainguards
[17:08] <kenvandine> sil2100, sure
[17:08] <sil2100> kenvandine: thanks :)
[17:25] <fginther> Saviq, AIRC, those were needed to make sure all of the latest test dependencies were installed. The list could easily be stale now
[17:36] <pmcgowan> silo 55 is being tested now or is it blocked still?
[18:00] <pmcgowan> silo 55 is being tested now or is it blocked still?
[18:00] <pmcgowan> davmor2, ^^
[18:01] <davmor2> pmcgowan: I will have a look at it shortly
[18:02] <pmcgowan> davmor2, cool thanks
=== nuclearbob_lunch is now known as nuclearbob
[18:10] <pmcgowan> popey, so is there a new music app to go with that mpris silo?
[18:17] <popey> pmcgowan: there is a merge that's being worked on
[18:18] <popey> pmcgowan: issues list -> https://docs.google.com/document/d/1xzI4D6knVJ6VmXxqJ2gyGSMowbtVVoNPgQl1fywim_U/edit
[18:19] <pmcgowan> popey, those seem to be all over the stack, so wondering how silo 55 can be ready for testing
[18:19] <popey> indeed.
[18:19] <popey> this doc was collaboration between jim and ahayzen
[18:20] <popey> ahayzen: that's right, right?
[18:23] <davmor2> pmcgowan, popey: ouch, I wonder why Jim was pushing for the silo then.  Aiui this couldn't land till the ui fix was in place, that has been added to the silo this afternoon so is due a retest and this unblocked everything else then, I was not made aware of a previous issues list
[18:23] <pmcgowan> davmor2, yeah the indicator with fixes is now in the silo but does not sound readt
[18:23] <pmcgowan> ready
[18:25] <davmor2> pmcgowan: also the bulk of stuff you can't actually test due to the fact that nothing uses the playlist feature yet :(
[18:26] <pmcgowan> davmor2, should be a way to at least test the indicator and see no regressions, plus the music app
[18:27] <pmcgowan> then we can land inline playback stuff after
[18:28] <davmor2> pmcgowan: yes so the indicator works for play pause but skip back and forward just end the track/video because there is only one item in the playlist
[18:28] <pmcgowan> davmor2, seems we wait for abeato to give the all clear
[19:21] <ahayzen_> popey, yup that doc is a list tracking issues that me and jim know of between music-app/media-hub/indicator-sound
[19:22] <ahayzen_> popey, silo 55 adds MPRIS support in media-hub... and had some other improves bundled
=== ahayzen_ is now known as ahayzen
[19:35] <popey> pmcgowan: ^
[19:39] <pmcgowan> popey, ahayzen right but not clear to me when they get addressed and we can land everything
[19:40] <ahayzen> i think Jim has been trying to iteratively land things and keep them all contained in separate silos
[19:40] <ahayzen> from our point of view the music-app is pretty close, most of the issues are with media-hub itself
[19:41] <ahayzen> or indicator-sound or whatever
[19:41] <pmcgowan> ahayzen, we have al the latest in silo 55, but it cannot land if it breaks music=app
[19:42] <ahayzen> how does it break the music-app?
[19:42] <pmcgowan> davmor2, ?
[19:43] <ahayzen> remember the current music-app in the store isn't using the bg playlists, so assuming the indicator-sound doesn't show the MPRIS controls when running with that, i don't think anything in the existing app would break?
[19:44] <pmcgowan> ahayzen, right but the goal is to enable them in the indicator
[19:44] <pmcgowan> so we can do inline playback in scopes
[19:44] <ahayzen> can it not detect when you are using playlists?
[19:45] <ahayzen> and i assume the scopes will probably have the same issues we are having in our WIP branch
[19:48] <ahayzen> IIRC 047 has just the MPRIS stuff in it as well https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-047
[19:55] <fginther> Saviq, your change to get unity8 on wily running worked, at least it was able to install and run the tests
[19:57] <fginther> Saviq, Also, for dual landing of unity-api, should we drop CI on lp:unity-api/trunk-15.04 ?
[20:26] <Saviq> fginther, yes, and yes
[20:27] <Saviq> fginther, we want dual-landing for lp:qtmir as well, so ci for it on both wily and vivid please
[20:29] <Saviq> fginther, can you please drop unity-scope-tool and indicator-client from unity8's test_packages param?
[20:42] <fginther> Saviq, yes as well. I don't see any other branches for qtmir except lp:qtmir, so nothing to remove there (which is why I only asked about unity-api)
[20:43] <fginther> Saviq, will also have the unity8 job updated shortly
[21:07] <Trevinho> We're still out of free silos?
[21:09] <Saviq> fginther, nothing to remove, but we'd also like both wily and vivid testing on them
[21:10] <fginther> Saviq, I'm setting up qtmir now. See http://s-jenkins.ubuntu-ci:8080/job/qtmir-ci/426/console for the results of testing with lp:qtmir
[21:10] <Saviq> fginther, great, thanks a lot