[00:52] <fginther> michi, for lp:thumbnailer and lp:thumbnailer/devel, should MP -ci builds be done using wily or vivid+the overlay PPA?
[00:53] <michi> fginther: vivid for the time being, as far as I know.
[00:53] <fginther> michi, thx
[00:53] <michi> Dang, I should fill in the spreadsheet for that, my apologies.
[00:55] <fginther> michi, we've already collected changes, but if you know of other projects to change. now is easier then later
[00:55] <michi> unity-scopes-api and thumbnailer are the ones I’m directly involved with at the moment.
[00:56] <fginther> michi, ok, someone already spoke up for u-s-a
[00:56] <michi> That was me :)
[00:56] <michi> I just forgot to fill in thumbnailer
[00:56] <fginther> michi, I'll get thumbnailer updated
[00:56] <fginther> oh :-)
[00:57] <michi> Ah. Looks like thumbnailer isn’t in the spreadsheet
[00:57] <michi> Weird. It’s there.
[00:57] <michi> But, when I search for it in the spreadsheet, it’s not found
[01:00] <michi> fginther: I just filled in unity-api
[01:00] <michi> Pawel is the right contact, I believe. Or possibly mzanetti.
[03:54] <jhodapp> robru, ok...so I'll retarget for wily then
[03:54] <jhodapp> robru, is the sync back to vivid+overlay automatic?
[03:55] <robru> jhodapp: nope, i set you up with a second silo there for the sync
[03:55] <jhodapp> robru, ok...I got line 68 pointing at wily now
[03:55] <jhodapp> robru, ready for a silo then
[03:55] <robru> jhodapp: not sure if syncing is working, there was trouble with that earlier. Will have to watch it.
[03:56] <jhodapp> robru, ok
[03:57] <robru> jhodapp: 24 for wily and 25 for vivid. http://people.canonical.com/~platform/citrain_dashboard/#?q=jhodapp
[03:58] <jhodapp> robru, nice, thanks much
[03:58] <robru> jhodapp: you're welcome
[03:58] <jhodapp> robru, I didn't know I could just look at the silos that I own
[03:58] <jhodapp> that's nice
[03:59] <robru> jhodapp: heh, that features been there for a few months now, I've been trying to promote it but i guess not everybody knows yet ;-)
[04:00] <robru> jhodapp: bookmark it ;-)
[04:00] <jhodapp> it's so hard to keep track of what our tools are capable of doing, at least for me
[04:00] <jhodapp> Although I tend to stick to what I know until someone points out something new that I can't live without after
[04:00] <robru> jhodapp: yeah it's a moving target
[04:01] <jhodapp> robru, what does that error mean?
[04:02] <robru> jhodapp: you built the wrong one first. 25 is just a sync, but there's nothing in 24 to sync from yet
[04:02] <jhodapp> oh right
[04:02] <jhodapp> robru, cool thanks, I'll leave that to build now
[04:02] <jhodapp> off to bed, have a good one robru
[04:03] <robru> jhodapp: you're welcome!
[05:26] <Mirv> kenvandine: no I didn't have an idea what's wrong, but thought to try out if it
[05:26] <Mirv> kenvandine: 's something temporary. turns out it wasn't.
[06:57] <oSoMoN> good morning trainguards! can I have a silo for line 71, please?
[06:59] <robru> oSoMoN: 404: https://ci-train.ubuntu.com/job/prepare-silo/4915/console
[07:00] <oSoMoN> robru, d’oh, sorry about that, wrong copy/paste, the list of MRs is fixed now
[07:10] <Mirv> oSoMoN: sure, robru should be asleep anyway or else he doesn't see any sunlight during his "day"
[07:10] <Mirv> but there it is already, right
[07:13] <robru> Mirv: I got it ;-)
[07:16] <oSoMoN> robru, Mirv: thanks :)
[07:16] <robru> oSoMoN: you're welcome!
[07:53] <Mirv> Mirv: sure, assigning
[07:53] <Mirv> Mirv: thanks!
[08:03] <sil2100> :O
[08:03] <sil2100> ...wow
[08:26] <bzoltan> fginther: hi, would you have little time for us, please? the UITK CI tests keep failing for no reason.
[08:26] <Mirv> sil2100: what do you think about https://ci-train.ubuntu.com/job/ubuntu-landing-015-2-publish/lastSuccessfulBuild/artifact/indicator-network_packaging_changes.diff - moving connectivity-api src package to indicator-network? like, we can't "remove" connectivity-api src package from overlay PPA, but it shouldn't conflict as such as it's providing all the same packages, just a newer version
[08:29] <sil2100> hm, well, I remember someone mentioning the plans to move connectivity-api to indicator-network but I don't remember the rationale for that... seems a bit controversial, but besides that there shouldn't be anything against this move
[08:29] <sil2100> So I would say it's ok if that's how upstream wants to manage it
[09:42] <oSoMoN> ubuntu-qa: any chance silo 32 can be validated today ?
[09:42] <rvr> There is a chance
[09:43] <rvr> It's the only card in the "ready for testing" queue right now :)
[09:48] <oSoMoN> cool
[10:23] <bzoltan> Mirv: sil2100 ^
[10:30] <sil2100> o/
[10:30] <sil2100> On it
[10:32] <sil2100> robru: btw. could you take a look today at why certain landings aren't set as Landed in the spreadsheet but are cleared? Probably the train's doing something too quickly for the spreadsheet to notice
[10:33] <sil2100> robru: since the spreadsheet issues aren't related to update frequency I might simply re-enable spreadsheet updates once-per-5-minutes now
[10:33] <sil2100> bzoltan: assigned!
[10:36] <Mirv> sil2100: robru: that happens to maybe 1/3 of the landings
[10:37] <Mirv> I don't mind, we're sooo near getting rid of the spreadsheet, right?
[10:37] <sil2100> Right, although it gets in the way of commitlogs :< As it's not marking the released version numbers
[10:57] <sil2100> Mirv: I think most of the time the spreadsheet Landed bug happens on overlay landings, as it's too fast for the spreadsheet to notice
[10:59] <Mirv> right that's good thinking
[11:31] <cjwatson> Saviq: Is https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1408626 the same as https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1348535, or are you talking about some other builder jobs?
[11:32] <bzoltan> sil2100: Mirv: I would like to ask a reconf of the silo20 because I have added the gles MR to it.
[11:33] <Mirv> bzoltan: ok
[11:33] <Saviq> cjwatson, I *think* it's about the jenkins -ci jobs
[11:33] <Saviq> cjwatson, so bug target might be wrong
[11:33] <cjwatson> Saviq: The bug target for 1348535 was wrong, but the bug target for 1408626 is probably right if it's talking about Jenkins jobs
[11:34] <cjwatson> Saviq: Thanks for clarifying the bug summary
[11:34] <Saviq> I updated the title to be cleare
[11:34] <Saviq> nw
[11:39]  * sil2100 off to lunch
[11:43] <fginther> cihelp, can you please have a look at bzoltan's request above? "<bzoltan> fginther: hi, would you have little time for us, please? the UITK CI tests keep failing for no reason"
[11:51] <bzoltan> fginther:  for about 11 days nothing passed Jenkins
[11:52] <fginther> bzoltan, which branch is this for? I'll start by collecting some info
[11:52] <bzoltan> fginther:  the staging
[11:54] <bzoltan> fginther: lp:ubuntu-ui-toolkit/staging
[11:56] <fginther> bzoltan, this error "ASSERT failure in QTest::fetchData(): "Test data requested, but no testdata available.", file qtestcase.cpp, line 2044" was discussed a few days ago. let me try to find the notes
[11:59] <bzoltan> fginther: thank you
[12:00] <fginther> bzoltan, so the tst_components_benchmark.benchmark_creation_components failure (same as the above output) appears to have been introduced by this MP: https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/separate-uitk-versions/+merge/257455
[12:00] <fginther> kalikiana, have you had a chance to follow up on that ^ ?
[12:07] <kalikiana> fginther: yes, https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/whereDidMyBenchGo/+merge/258925
[12:08] <kalikiana> unfortunately it's failing on yet other issues
[12:08] <kalikiana> but we merged it manually
[12:09] <fginther> kalikiana, this testcase? "test_tst_listitem.qml.xml.<init>" I was seeing this a few times in my search too
[12:21] <ogra_> bah, seems the new vivid channel has the image numbers reset ...
[12:21] <fginther> kalikiana, bzoltan, we'll look some more, but I have to drop offline for a bit. I've started some notes in case someone else can pick it back up before then
[12:21] <kalikiana> fginther: yep. it might be a crash, but it's hard to reproduce locally
[12:22] <kalikiana> I think zsombi managed to see it on his machine
[13:54] <mpt> (Followup from yesterday: reported bug 1455506)
[14:05] <elopio> cihelp: UAL doesn't work yet without upstart as session manager. So for testing in wily we need it installed, for the moment.
[14:06] <elopio> this is related to kenvandine's error from yesterday. I'm not sure what to do next, can you take care of installing upsptart in the wily machines?
[14:07] <kenvandine> ugh...
[14:07] <kenvandine> we need UAL!
[14:07] <kenvandine> tedg, ^^
[14:13]  * ogra_ wonders if the initial idea to not build on wily at all wasnt perhaps the better idea
[14:14]  * sil2100 is not chaning the rules for the third time
[14:14] <sil2100> I would look stupid
[14:14] <sil2100> ;)
[14:14] <ogra_> naah ... just point at someone else
[14:14] <tedg> Upstart should be a dependency of Unity8
[14:15] <tedg> We're months away from not having Upstart as a session manager.
[14:18] <elopio> don't point at me, I'm just the messenger :)
[14:18] <elopio> well, and the one who didn't update the initctl scripts early...
[14:20] <elopio> tedg: shouldn't gir1.2-ubuntu-app-launch-2 depend on upstart?
[14:21] <tedg> elopio, Well, that's a discussion you're going to have with foundations. I contend that libraries should depend on the services that make them work, but I've lost that battle a few times :-/
[14:23] <tedg> To be clear, I think the gir should depend on the lib which should depend on the base ubuntu-app-launch which does depend on Upstart.
[14:23] <elopio> ok, we could make autopilot or ubuntu-ui-toolkit-autopilot depend on upstart for now. Or just make sure that it's installed on the lab until it's no longer required.
[14:24] <tedg> I'm really confused on why this is necessary. Upstart is seeded.
[14:24] <elopio> tedg: the error kenvandine was getting yesterday was because upstart is not installed.
[14:24] <tedg> elopio, What are you using as an image that doesn't have Upstart?
[14:24] <ogra_> tedg, upstart is onl yseeded on touch images
[14:25] <tedg> ogra_, It's needed for Unity7 session
[14:25] <tedg> So it's seeded for Ubuntu Desktop as well.
[14:25] <elopio> tedg: not me, the lab.
[14:25] <ogra_> tedg, are you sure it still is ?
[14:25] <tedg> elopio, Which seed is the lab image based on?
[14:25] <elopio> cihelp ^
[14:25] <tedg> ogra_, Yes, we have no unit files for any indicators :-)
[14:26] <ogra_> tedg, no, i meant are you sure it is still seeded on desktop :)
[14:26] <tedg> I know that the desktop won't work without it. So if we have any quality, it's getting into the image somehow :-)
[14:26] <kenvandine> and this isn't the CI lab machines, it's the adt stuff
[14:27] <kenvandine> so whatever those run
[14:27] <Ursinha> elopio: hi, in the standup now but I'll get to the scrollback here in 5 minutes
[14:27] <elopio> tedg: I got a question left from yesterday. Once I have systemd and upstart installed, how do I tell my machine to use upstart as the session manager? It happens just by installing upstart?
[14:27] <elopio> Ursinha: ack.
[14:29] <tedg> elopio, It happens by running a Unity desktop session
[14:29] <ogra_> tedg, so it isnt seeded in the image in either vivid or wily ... must be a dependency that pulls it in
[14:29] <tedg> ogra_, Yeah, just looking at that.
[14:29] <ogra_> it is only in the supported seed
[14:29] <ogra_> (which just mmeans it is kept in main)
[14:29] <tedg> unity-greeter depends on it.
[14:30] <tedg> So we're probably not getting it into the image in the best way :-)
[14:31] <jhodapp> sil2100, ping
[14:31] <sil2100> jhodapp: pong
[14:31] <jhodapp> sil2100, hey, what's going on here...any idea? https://ci-train.ubuntu.com/job/ubuntu-landing-024-1-build/147/console
[14:31] <rvr> pstolowski: Can you change this to "approved", is already reviewed, to unblock your silo? https://code.launchpad.net/~stolowski/ubuntuone-credentials/get-consumer-key-15-04/+merge/258787
[14:32] <sil2100> jhodapp: taking a look
[14:32] <tedg> Really ubuntu-session should depend on Upstart
[14:33] <sil2100> jhodapp: ok, it seems that your silo (or wily) is missing a newer version of media-hub which is a dependency for your qtubuntu-media
[14:34] <sil2100> jhodapp: and since those are builds of main architectures, the train is looping and waiting for the deps to be resolved
[14:34] <jhodapp> sil2100, yeah that's weird, I bumped the version of media-hub and kicked off a rebuild, yet it seems to be building the 3.1 version instead of 3.2
[14:34] <sil2100> jhodapp: it seems it needs media-hub of 3.2
[14:34] <kgunn> sil2100: on line 63, i have it for vivid...but with all the "settling" of images/branches/landing approaches....i wanna change this to target wily
[14:34] <sil2100> hm, let's take a look at that then, one moment
[14:34] <jhodapp> thanks
[14:35] <kgunn> can i just change in the spreadsheet ? and rebuild ?
[14:35] <kgunn> or does it need a manual reconfig
[14:35] <sil2100> kgunn: hm, uh, sadly we'll have to reassign the silo
[14:35] <sil2100> kgunn: and a full rebuild
[14:35] <jhodapp> sil2100, it could be something I forgot (or didn't know) to do with the media-hub debian package
[14:35] <kgunn> can i leave that with you to move  it ?
[14:35] <sil2100> Let me do that after the RTM meeting  :)
[14:35] <kgunn> :)
[14:35] <kgunn> thanks
[14:36] <sil2100> jhodapp: let me take a look deeper, I'm in a meeting so it might take a few more minutes than usual
[14:36] <jhodapp> sil2100, sure, thanks
[14:38] <sil2100> jhodapp: ah, I think I see what needs to be done - since you changed the minor version, you'll need to add a new debian/changelog entry
[14:38] <jhodapp> sil2100, ok...what's the command line app used to do that again...I forget the name of it
[14:40] <sil2100> jhodapp: for this merge: https://code.launchpad.net/~jhodapp/media-hub/signal-duration-changed/+merge/259177 - do `dch -i` and change the version there to 3.2.0 and leave it as UNRELEASED
[14:40] <jhodapp> sil2100, yes, dch that's the one...thanks :)
[14:40] <sil2100> And in the contents of the changelog, just enter the commit message as from your branch :)
[14:40] <jhodapp> cool thanks
[14:40] <cjwatson> tedg: Probably best to just put it into debian/tests/control for the autopkgtests
[14:40] <sil2100> yw, poke me if there's anything else
[14:40] <cjwatson> tedg: Since the base that those start from won't include all the desktop stuff
[14:41] <jhodapp> sil2100, can you kill that silo build?
[14:41] <cjwatson> elopio,kenvandine: ^-
[14:41] <sil2100> jhodapp: sure, you can abort it as well, just make sure you only abort the build job when it's done uploading the packages and just 'checking packages'
[14:42] <sil2100> It's safe in that phase
[14:42] <jhodapp> sil2100, ok, but isn't it stuck now so it won't get there?
[14:42] <sil2100> jhodapp: well right now it's in the state where it's safe to abort :)
[14:42] <sil2100> As it's waiting for packages to build
[14:42] <jhodapp> ok cool
[14:42] <elopio> cjwatson: the autopilot tests are not yet autopkgtests in all the projects. So it should be put in the jenkins job config, I guess.
[14:43] <pstolowski> rvr, working on it / asking the reviewer
[14:43] <sil2100> Once you see "INFO Looking at PPA: ..." then it's safe to cancel the jenkins job
[14:43] <jhodapp> sil2100, good to know
[14:46] <Ursinha> elopio: hello, I'm here now
[14:48] <Ursinha> elopio: let me see if I got this right: you are saying that as part of the setup to run tests, you want us to install upstart in wily?
[14:48] <Ursinha> which sounds a bit... crazy?
[14:48] <elopio> Ursinha: yes.
[14:49] <elopio> well, any other alternative that gets upstart installed could work.
[14:49] <Ursinha> elopio: and that would be because tests themselves depend on upstart, not the packages?
[14:49] <elopio> I'm wondering how you managed to install wily and unity7 in the lab without upstart, which according to the discussion in here shouldn't work.
[14:50] <elopio> Ursinha: the tests depend on ubuntu-app-launch which needs upstart.
[14:52] <Ursinha> elopio: thanks for clarifying, we're moving things to wily since we got the images (one week ago), these things are coming up slowly, I'm sorting that out
[14:54] <elopio> Ursinha: ok. kenvandine worked it around landing on the overlay instead, and nobody else has mentioned this blocking them, so it seems we don't need to get it solved today.
[14:55] <elopio> but as people start landing things in wily, they will get the same error.
[14:55] <elopio> in the meantime, we will prepare some branches for the tests that depend on upstart. That will be solved mainly by an extension on the toolkit.
[14:55] <sil2100> kgunn: ok, so line 63 (silo 004) - you want it to target wily, yes?
[14:56] <kgunn> sil2100: yes please
[14:56] <sil2100> I have your permission to reassign it?
[14:56] <sil2100> Ok
[14:56] <Ursinha> elopio: that's a very interesting problem
[14:58] <Ursinha> elopio: I'd say that if upstart isn't part of wily, tests should be modified accordingly to test the real thing, but then I'm not sure we could (even that being necessary) afford implementing smart tests that know what to depend on
[14:59] <elopio> Ursinha: once UAL is ported to systemd, the tests will be able to work with upstart or systemd, whatever is being used as pid1. Not hard to do, I think.
[14:59] <sil2100> kgunn: reassigned, you even got the same silo
[14:59] <sil2100> ;)
[14:59] <kgunn> cool, thanks
[15:00] <sil2100> robru: hey! Once you're around, since you probably know your way around this, there seem to be some issues with our staging instance on wendigo
[15:00] <sil2100> robru: did you tinker with it recently? I have a branch I'd like to test
[15:02] <Ursinha> elopio: I'd say people should stop the line and just fix it, as injecting upstart is fundamentally modifying the tested environment
[15:04] <sil2100> ogra_: hey! Did you find some time to fix up the changes generation? :)
[15:05] <ogra_> sil2100, still on it
[15:14] <Ursinha> elopio: kenvandine, I think proposed-migration isn't wrong by blocking the package, that is a valid failure
[15:15] <kenvandine> yeah, sort of... it's a missing depends for the test
[15:15] <kenvandine> but actually ubuntu-system-settings-online-accounts itself doesn't need upstart at all
[15:15] <kenvandine> but the test infrastructure needs it to run it's tests
[15:16] <kenvandine> promoting it wouldn't break devices with the package
[15:18] <Ursinha> kenvandine: right.. but for that we need dependencies that aren't in the archive, right? should that be allowed? I think that's a policy decision to make
[15:19] <kenvandine> upstart is still in the archive right?
[15:19] <kenvandine> but installing it in the test environment might be wrong though
[15:19] <dobey> upstart is still required on the phone no?
[15:20] <kenvandine> i don't think the autopkgtests run on phones
[15:20] <ogra_> yes, it wont go out of the archive before 16.04
[15:20] <dobey> the deb ones don't
[15:20] <dobey> the click ones do
[15:20] <kenvandine> this is just the tests that run in proposed
[15:20] <Ursinha> kenvandine: if the package is in the archive, why are tests failing? now I'm confused
[15:21] <dobey> kenvandine: for dep8 tests you should add test/runtime dependencies in debian/tests/control
[15:21] <kenvandine> they aren't installed in the VM or whatever the autopkgtests are run on
[15:21] <ogra_> Ursinha, because nothing requires the package to be installed while testing
[15:21] <mzanetti> sil2100, does the sync: thing work again already?
[15:21] <kenvandine> ogra_, well it does... autopilot tests that uses uitk do
[15:21] <ogra_> and there is no dependency since upstart is not needed for the package to work right
[15:21] <pstolowski> rvr, there is some confusion right now about where to land our changes from silo 33 wrt to target branches and distro, we may need to split the silo and retarget the branches
[15:21] <kenvandine> so i'd argue the autopilot package for uitk should dep on it
[15:21] <sil2100> mzanetti: not yet, the branch is ready but I couldn't test it on staging yet as it's b0rken
[15:22] <sil2100> ;/
[15:22] <ogra_> kenvandine, that might be an option, yeah
[15:22] <kenvandine> i think that's the right thing
[15:22] <kenvandine> it's what depends on it
[15:22] <mzanetti> sil2100, if I want to release something to wily and then sync it to vivid-overlay. what's the way to go atm?
[15:22] <kenvandine> not even the tests in uss-oa depend on it
[15:22] <kenvandine> it's the helpers in uitk that do
[15:22] <dobey> anyway, i need to get lunch
[15:22] <dobey> bbiab
[15:23] <ogra_> mzanetti, lots of praying ... (for the first bit of your question)
[15:23] <sil2100> mzanetti: the easiest way is to poke trainguards for that ;)
[15:23] <mzanetti> ack. works fo rme
[15:23]  * kgunn gets poking finger ready
[15:23] <sil2100> mzanetti: I can help you if you want it now, or robru if you want to do it later
[15:23] <Ursinha> ogra_: I'm trying to understand why that package isn't being installed, I first assumed the test dependencies were automatically pulled and the only reason a package wouldn't be installed is if that wasn't available
[15:23] <mzanetti> pstolowski, is the silo ready to be released?
[15:23] <dobey> mzanetti, pstolowski: if you need me to discuss with cihelp/trainguards after my lunch about this, to get things moving along, i'm happy to
[15:23] <sil2100> I hope that once robru's back he'll be able to deal with the staging issues and I can test my branch proper
[15:23] <Ursinha> ogra_: but I'm clearly missing something, and I'm looking into finding out what that is
[15:24] <dobey> just tell them to bug me for the silo and i'll help get it sorted out
[15:24] <ogra_> Ursinha, well, you just said it "the test dependencies" ...
[15:24] <kgunn> sil2100: so, we did have one thing, mir landing to vivid+ in flight...and then things changed to "we should land in wily first" and "no more syncs"...
[15:24] <ogra_> Ursinha, upstart isnt in the test dependencies :)
[15:24] <dobey> but i really do need to get food rignt now :)
[15:24] <kgunn> so do we need to do one follow up sync landing to wily for mir ?
[15:24] <pstolowski> mzanetti, no, cause my MPs target 15.04-touch branches meant to land in vivid-overlay ppa and yours unity8 targets trunk/wily
[15:24] <Ursinha> ogra_: hmm I thought that was defined in the package?
[15:24] <kgunn> or can we ask for a copy that direction (from vivid+ to wily)
[15:24] <pstolowski> mzanetti, so I think you need to take your MPs and just land them in wily and then sync into vivid-overlay
[15:25] <elopio> kenvandine: with my branch the toolkit will work either with upstart or systemd: https://code.launchpad.net/~canonical-platform-qa/ubuntu-ui-toolkit/systemd/+merge/259210
[15:25] <elopio> what remains depending on upstart is UAL.
[15:25] <Ursinha> ogra_: as I said, I'm clearly missing something here :)
[15:25] <ogra_> Ursinha, as kenvandine said, the package itself doesnt need upstart to function correctly ... only the test needs it
[15:25] <sil2100> kgunn: did the mir landing already land in vivid? A copy in both directions is fine, it's just that landing in wily is 'safer'
[15:25] <sil2100> kgunn: so we can copy the package from vivid overlay to wily if you want
[15:25] <ogra_> so the package itself has no dep ...
[15:25] <Ursinha> ogra_: I thought test dependencies were defined in the package
[15:25] <jhodapp> sil2100, does this look normal now or is it still stuck in a dependency checking loop? https://ci-train.ubuntu.com/job/ubuntu-landing-024-1-build/148/console
[15:25] <kgunn> sil2100: sure...it's been in "waiting on QA" for some time for landing in vivid+
[15:25] <kgunn> never landed in vivid (regular)
[15:25] <Ursinha> that's what I said
[15:25] <mzanetti> pstolowski, ok. moving the branches over to the other silo then
[15:25] <elopio> but as tedg said: <tedg> elopio, Well, that's a discussion you're going to have with foundations. I contend that libraries should depend on the services that make them work, but I've lost that battle a few times :-/
 To be clear, I think the gir should depend on the lib which should depend on the base ubuntu-app-launch which does depend on Upstart.
[15:25] <pstolowski> mzanetti, ok
[15:26] <ogra_> Ursinha, right, in which packae then ... ubuntu-system-settings-online-accounts does not need upstart installed to function properly, so it will not define a dependency
[15:26] <sil2100> jhodapp: it's good now I hope, let me kick the dep-waiting packages
[15:26] <kenvandine> uss-oa dep8 tests depends on the uitk autopilot packages
[15:26] <jhodapp> sil2100, ok great, I couldn't remember if "Dependency wait" is normal in this situation or not
[15:26] <cjwatson> ogra_: autopkgtests have separate test dependencies though, in debian/tests/control
[15:26] <ogra_> Ursinha, which means that some test specific package needs to add this dependency
[15:26] <cjwatson> nothing wrong with sticking things there
[15:26] <kenvandine> that pakcage should depend on upstart
[15:27] <Ursinha> ogra_: what cjwatson said
[15:27] <sil2100> kgunn: is that mir landing purely bug-fixing? Maybe QA didn't want to touch it because they thought its too invasive, hmmm
[15:27] <kgunn> sil2100: it's bug fixing goodness
[15:27] <sil2100> kgunn: let's ask QA what's up
[15:27] <kenvandine> Ursinha, i'm just saying adding that depends to debian/tests/control of the uss-oa only fixes it for uss-oa
[15:27] <tedg> It probably should just depend on "ubuntu-app-launch" instead of upstart-bin
[15:27] <sil2100> Ah
[15:27] <tedg> ubuntu-app-launch depends on upstart-bin, and will be changed as it gets ported.
[15:27] <sil2100> kgunn: I see it's being tested by davmor2 now!
[15:27] <kenvandine> making ubuntu-ui-toolkit-autopilot depend on upstart does
[15:28] <Ursinha> tedg: sounds sensible to me
[15:28] <ogra_> yeah
[15:28] <kenvandine> or more specifically depend on ubuntu-app-launch
[15:28] <Ursinha> but I don't know the details
[15:28] <sil2100> kgunn: once that lands we can do a manual sync for you to wily
[15:28] <kenvandine> then it fixes all packages that this affects
[15:28] <kenvandine> or... we land elopio's fix that makes it support both upstart and systemd :)
[15:29] <elopio> kenvandine: we can't land it yet, because of UAL, some of the tests in the toolkit fail
[15:29] <kenvandine> which we'll need anyway
[15:29] <kenvandine> ah
[15:29] <elopio> I see now that the online accounts tests use xvfb
[15:29] <elopio> so they don't have unity installed.
[15:29] <kenvandine> is anyone arguing that ubuntu-ui-toolkit-autopilot shouldn't depend on ubuntu-app-launch ?
[15:30] <elopio> so I think I can put upstart in their debian/tests/control as cjwatson suggested, and that could work.
[15:30] <kgunn> alan_g ^^ we can just poke sil2100 when mir lands, and he'll do a manual sync to wily for us
[15:30] <elopio> or make the dependency in upstart explicit in ubuntu-ui-toolkit-autopilot, while UAL is updated and my branch lands.
[15:30] <kenvandine> elopio, that isn't the right place to fix it...
[15:30] <sil2100> kgunn: maybe when that happens my branch will land and we'll be able to do that through the train even ;)
[15:31] <kenvandine> if ubuntu-ui-toolkit-autopilot depended on upstart or ubuntu-app-launch, all is fine
[15:31] <kgunn> sure
[15:31] <alan_g> kgunn: ack
[15:33] <Ursinha> kenvandine: so the "fix" for now would be change the dependency in ubuntu-ui-toolkit-autopilot?
[15:33] <kenvandine> yes
[15:33] <kenvandine> that's what depends on upstart here
[15:34] <kenvandine> and it should fix any of the packages that are currently blocked for promotion
[15:36] <Ursinha> kenvandine: would people object pushing this change? (even if that wasn't failing, this looks like the right thing to do anyway)
[15:36] <kenvandine> i think it's the right solution...
[15:36] <alan_g> cihelp - Is this known? I see "W: Failed to fetch http://ppa.launchpad.net/mir-team/staging/ubuntu/dists/wily/main/binary-amd64/Packages 404 Not Found" - http://jenkins.qa.ubuntu.com/job/mir-wily-amd64-ci/5/console
[15:37] <Ursinha> alan_g: let me see
[15:38] <Ursinha> alan_g: looking at the staging ppa it doesn't seem to have wily packages, so that is a valid failure
[15:38] <Ursinha> but then it looks wrong, because that was vivid + overlay ppa that is supposed to be vivid..
[15:39] <Ursinha> fginther: would you know about that?
[15:39] <Ursinha> alan_g: I'll have a look, we have migrated to the overlay ppas yesterday and this might have been overlooked in the checks
[15:41] <elopio> kenvandine: Ursinha: https://code.launchpad.net/~canonical-platform-qa/ubuntu-ui-toolkit/upstart/+merge/259262
[15:42] <elopio> luckily, online_accounts_ui doesn't launch with Ubuntu App Launch. It just calls the binary.
[15:44] <Ursinha> hm, okay
[15:44] <pstolowski> trainguards may I ask for reconfiguring of silo 33 and purging its ppa?
[15:45] <Ursinha> alan_g: I can see that camako asked that mir ci/autolanding jobs start using wily, I think that as a consequence (maybe) it started pulling mir staging PPA wily and there are no packages for wily there. Wild guess, I have to wait for fginther to confirm this is the right reading of the problem
[15:45] <kenvandine> elopio, that looks good to me
[15:46] <Ursinha> elopio: looks "right", let's see if that solves the problem :)
[15:46] <elopio> bzoltan: https://code.launchpad.net/~canonical-platform-qa/ubuntu-ui-toolkit/upstart/+merge/259262
[15:50] <fginther> Ursinha, alan_g, This is a consequence of moving to wily, let me see if there is simple fix for this
[15:53] <fginther> alan_g, updating this recipe to build for wily should fix the problem: https://code.launchpad.net/~mir-team/+recipe/mir-daily
[15:59] <alan_g> fginther: That's new to me. I need to add wily to "Distribution series"?
[16:00] <sil2100> Mirv, robru: hey, so I fixed as many landings as I saw in the spreadsheet that weren't set as 'Landed' - I also added the 'package versions published' information which is required by commitlogs
[16:00] <fginther> alan_g, yeah, that should be all it takes, and then request a new build
[16:01] <sil2100> Mirv, robru: if you see any landings that are landed but the spreadsheet fails to set those as 'Landed', please either leave them for me or, if you want to fix them, please be sure to fill in the version infos in column S
[16:02] <sil2100> Mirv, robru: it's troublesome so I can do that basically, but without that my commitlogs will be sad (once they're back operational)
[16:53] <dobey> cihelp: will ps jenkins pick up MPs on new branches that were listed in the spreadsheet, automatically now?
[16:54] <Ursinha> dobey: in my understanding it should work exactly as before, what changed are the dependencies considered
[16:55] <fginther> dobey, if a *new* branch was added to that spreadsheet, it should have some MPs picked up by now
[16:56] <dobey> fginther: hmm, ok
[16:56] <oSoMoN> ubuntu-qa: hey guys, any chance silo 32 might be validated today?
[16:56] <dobey> fginther: doesn't seem like https://code.launchpad.net/~stolowski/ubuntuone-credentials/get-consumer-key-15-04/+merge/258787 was picked up
[17:02] <fginther> dobey, I'll take a closer look
[17:03] <dobey> fginther: ok, thanks
[17:06] <fginther> dobey, I found part of the problem and put in a partial fix. The job that searches for and triggers all these MPs is now taking much longer is was timing out before finishing.
[17:06] <fginther> I increased the timeout to hopefully grab the MPs it was missing, but will need to revisit it as to why it is so horribly slow
[17:08] <dobey> probably so many branches it's looking for?
[17:08] <dobey> probably needs to be parallelized
[17:30] <dobey> fginther: i also pinged cihelp yesterday to ask for https://code.launchpad.net/~alecu/unity-scope-click/refunds-previews/+merge/257444 to have jenkins re-run the build tests against wily, but i didn't see any response about it
[17:38] <alex-abreu> trainguards can you reconfigure silo 26?
[17:40] <robru> alex-abreu: done
[17:41] <alex-abreu> robru, thx
[17:42] <robru> alex-abreu: you're welcome
[17:52] <fginther> dobey, sorry about that. I've retriggered https://code.launchpad.net/~alecu/unity-scope-click/refunds-previews/+merge/257444
[17:52] <dobey> fginther: ok, thanks.
[17:52] <dobey> i tried to do so, but i guess i got something wrong that i didn't notice
[17:53] <ogra_> sil2100, http://people.canonical.com/~ogra/touch-image-stats/vivid/196.changes ... there is also 197
[17:53] <ogra_> (wrt your landign mail)
[17:59] <sil2100> yay
[17:59] <sil2100> ogra_: do we have wily changes too?
[18:01] <ogra_> sil2100, nope, that vivid changelog is from yesterday still ... but i'm confident to have all set up later today
[18:01] <ogra_> (i'll fillow up on the landing mail with the locations once i'm done)
[18:04] <kgunn> robru: if i'm using citrain tool...i assume ubuntu==wily and ubuntu-rtm=vivid
[18:04] <kgunn> +overlay
[18:04] <kgunn> ?
[18:04] <robru> kgunn: uh, no? ubuntu is ubuntu and ubuntu-rtm is ubuntu-rtm.
[18:06] <kgunn> got it
[18:07] <robru> kgunn: I guess you're trying to verify a wily silo on a vivid phone image and having problems? that case is not well defined.
[18:07] <kgunn> robru: nope...wasn't anywhere yet, was just asking
[18:08] <kgunn> thinking it could get weird
[18:08] <kgunn> robru: i did notice tho....landing-030 is now against wily but also has "target ppa" set for overlay
[18:08] <kgunn> that would seem invalid atm ?
[18:09] <kgunn> row 54 in ci train sheet
[18:11] <robru> kgunn: yeah that would be invalid
[18:11] <ogra_> sil2100, 196 and 197 and upwards wont work anymore though ... the vivid channel for mako is ubuntu-touch/rc-proposed/ubuntu ... but that ends at 132
[18:11] <kgunn> robru: so does that need to get rebuilt or something ?
[18:11] <robru> kgunn: just reconfigured, hang on
[18:11] <kgunn> ta
[18:12] <ogra_> sil2100, in the new channel schema we dont seem to have anything corresponding to vivid 196 actually
[18:12] <robru> kgunn: not sure what you're looking at. silo 30 says "vivid primary" (which is also wrong) and row 55 says the same. do you want it for vivid overlay or wily?
[18:13] <robru> oh, row 54.
[18:14] <robru> kgunn: if you're switching it from vivid to wily it does need a rebuild.
[18:15] <robru> kgunn: yeah I'm really confused. your silo says vivid primary but your row says wily overlay, both of those are invalid, and I'm not sure what you're trying to do. your choices are vivid overlay or wily primary.
[18:15] <kgunn> robru: wily primary - i think zanetti changed it earlier and forgot the other bits
[18:16] <robru> kgunn: ok
[18:16] <kgunn> (as we generically wanna target wily first, we did a switcheroo this morning)
[18:17] <fginther> dobey, ah! I found the problem. the branch is named lp:ubuntuone-credentials/touch-15-04, we have it stored ast lp:ubuntuone-credentials/touch-15.04
[18:17] <robru> kgunn: ok, just one hiccup, train can't reconfigure from vivid to wily. so I had to free it, will assign a new one
[18:18] <fginther> dobey, I'll adjust the config
[18:18] <kgunn> robru: yep, i thot that'd be the case, np
[18:18] <robru> kgunn: ok you're in silo 3 now for wily, also note conflict with unity8 in silo 4.
[18:18] <kgunn> yep
[18:18] <dobey> fginther: ah ok. i wonder if the same happened for unity-scope-click too then
[18:18] <kgunn> intentional
[18:19] <robru> kgunn: alright, good luck. hopefully we figure out this wily/vivid stuff soon.
[18:19] <dobey> fginther: oops it is. that's totally my fault. i typed them wrong in the spreadsheet. sorry about that.
[18:21] <fginther> dobey, I should be able to have it updated shortly
[18:21] <dobey> fginther: ok thanks
[18:47] <robru> cyphermox: ^^ silo 23 configured for vivid, surely you meant wily? or is that an SRU?
[18:48] <cyphermox> yeah, it's a SRU
[18:48] <robru> cyphermox: ok. you wanna publish it or should I?
[18:48] <cyphermox> either way :)
[18:49] <robru> cyphermox: publishing!
[18:49] <cyphermox> thank you!
[18:50] <robru> cyphermox: k, I think this is our first SRU to vivid ;-) please poke that along with SRU team, I'd hate for that to languish for months
[18:50] <robru> train's first SRU to vivid I mean
[18:52] <robru> brb, lunch
[19:06] <fginther> Mirv, there are a number of -ci jobs for working with https://code.launchpad.net/kubuntu-packaging branches. Are these still useful?