[09:31] <anpok_> ping trainguards
[09:31] <sil2100> anpok_: pong
[09:31] <anpok_> AlbertA resolved the boottest issues last night
[09:31] <anpok_> in silo004
[09:32] <anpok_> do we have to deo the our test process?
[09:32] <anpok_> *redo
[09:33] <sil2100> anpok_: what packages had to be changed to get those working?
[09:33] <sil2100> Since normally we recommend re-testing, but it also depends on what changes and where had to be made
[09:33] <sil2100> General recommendation is: please re-test, since even the smallest change or even a rebuild can cause potential trouble
[09:34] <anpok_> sil2100: we reverted changes inside mir - that affected libmirprotobuf0
[09:35] <anpok_> ok
[10:28] <karni> sil2100: < davmor2> karni: you might want to ping sill2100 to get a unique number and mark the other section as yes so we get a ticket in trello
[10:28] <karni> sil2100: is this something you can help with:)?
[10:29] <karni> sil2100: I've added Telegram row in line 53 of the CI Train sheet /Tarballs and Clicks/. The one in row 50 should be marked as failed, if it's something you can do.
[10:39] <sil2100> karni: on it!
[10:39] <sil2100> :)
[10:39] <karni> sil2100: cheers! :)
[10:40] <ogra_> wow, thats quite a list
[10:44] <davmor2> ogra_: what is
[10:55] <ogra_> davmor2, that silo4 list
[10:55] <ogra_> (of packages)
[10:56] <davmor2> ogra_: yes an it increases all the time :)
[10:56] <nerochiaro> elopio: hi, quick question: in an autopilot test, is there a reason why calling self.skipTest() will not actually skip the test ? is there anything extra i should do to make it work ? and is it documented anywhere ?
[10:56] <ogra_> davmor2, yeah, the insatiable anpok_ :)
[10:57] <anpok_> hmm
[10:57] <anpok_> i just noticed that qtmir-gles has a different version number..
[10:58] <anpok_> in other words.. those are not the droids you are looking for
[11:48] <Laney> sil2100: hi, do you know where the branch for ^ is by any chance?
[11:50] <seb128> Laney, https://code.launchpad.net/~indicator-applet-developers/indicator-datetime/trunk.15.10 ?
[11:51] <Laney> doesn't have 0710.1
[11:51] <seb128> Laney, https://code.launchpad.net/~indicator-applet-developers/indicator-datetime/trunk.15.04 in fact it seems
[11:51] <seb128> http://bazaar.launchpad.net/~indicator-applet-developers/indicator-datetime/trunk.15.04/revision/419
[11:52] <Laney> k, what happened there?
[11:53] <seb128> dual landing I guess?*
[11:54] <seb128> unsure why they branched if they dual land though
[11:54] <seb128> charles or tedg might know
[11:57] <Laney> it also has a very unhelpful changelog
[11:58] <mardy> trainguards: can you please help me find out how to see the test output from https://launchpadlibrarian.net/212289175/buildlog_ubuntu-vivid-amd64.online-accounts-api_0.1%2B15.04.20150722-0ubuntu1_BUILDING.txt.gz ?
[11:58] <mardy> I got some failed tests, and I'd like to see what's failing
[12:04] <seb128> mardy, they can't, is "make tests" not outputing the errors on stdout/err?
[12:04] <mardy> seb128: no, it's producing a file
[12:05] <mardy> seb128: it's how cmake works, I'm afraid; how do you deal with it in u-s-s?
[12:05] <seb128> mardy, to debug those I usually makes debian/rules cat the log
[12:05] <seb128> cmake is buggy in that regard imho
[12:06] <mardy> seb128: I agree; ok, I'll try working around that in debian/rules
[12:06] <mardy> seb128: thanks
[12:07] <seb128> yw
[12:09] <seb128> mardy, I think something like that should work
[12:09] <seb128> override_dh_auto_test:
[12:10] <seb128>     dh_auto_test || cat dir/somelog.log
[12:10] <seb128> mardy, non tested, but I did hacks like that before with success
[12:13] <mardy> seb128: cool, I'll try
[12:20] <jhodapp> hey sil2100, can you please publish silo 19 for me?
[12:23] <anpok> @trainguards: had to reconnect a few minutes ago.. is silo-004 ok now?
[12:35] <sil2100> jhodapp: on it, was eating lunch
[12:36] <jhodapp> sil2100, np, thanks!
[12:36] <sil2100> anpok: let me try publishing
[12:37] <sil2100> jhodapp: https://code.launchpad.net/~phablet-team/qtubuntu-media-signals/fix-black-video-issues/+merge/262363 still needs approval
[12:37] <jhodapp> sil2100, alright, one min
[12:38] <sil2100> anpok: grrrr... platform-api needs a rebuild ;/
[12:38] <sil2100> Version of platform-api at dest changed from 3.0.0+15.10.20150706-0ubuntu1 to 3.0.0+15.10.20150707-0ubuntu1 since packages built
[12:38] <sil2100> This is crazy
[12:38] <anpok> ok
[12:39] <jhodapp> sil2100, ok that's approved now
[12:39] <sil2100> jhodapp: republishing then
[12:39] <jhodapp> thanks
[12:45] <jhodapp> sil2100, is there still an issue?
[12:52] <sil2100> jhodapp: no, reviewing
[12:52] <jhodapp> ok
[12:55] <sil2100> It's good
[12:55] <sil2100> Too bad we won't be able to dual land those anymore
[12:58] <anpok> sil2100: now
[12:59] <sil2100> o/
[12:59] <sil2100> Aw come ooooon
[13:00] <sil2100> anpok: now qtmir...
[13:08] <tedg> seb128, Not sure, there was a big rebuild for Mir, wonder if that got pulled in.
[13:11] <seb128> tedg, but why did the wily update got commited to the 15.04 branch?
[13:11] <tedg> seb128, Not sure. Someone screwed up? ;-)
[13:12] <seb128> tedg, that was sort of part of the ping/question
[13:12] <seb128> or is the indicator in dual landing?
[13:12] <tedg> seb128, We should ask charles to be sure as I haven't been following as closely.
[13:12] <seb128> in which case was the branching needed/wanted?
[13:12] <tedg> No, none of the indicators or dual landing.
[13:12] <tedg> are
[13:12] <seb128> shame
[13:12] <seb128> that spare works
[13:13] <tedg> Eh, kinda. If you don't care about what ends up in wily, sure.
[13:13] <seb128> why would bugfixes not be good for wily?
[13:16] <tedg> Because there are always integration issues. Bug fix works on foo version of a library but not bar.
[13:17] <tedg> If you're not looking at those, you basically get bit rot.
[13:20]  * sil2100 pokes ogra_ about the endorsement
[13:20]  * ogra_ whistles innocently 
[13:42] <anpok> sil2100: ^ now rebuilding qtmir-gles
[13:42] <sil2100> anpok: thanks!
[13:50] <pete-woods> trainguards: hi guys, could I get silo 46 reconfigured? thanks! :)
[13:52] <Laney> https://launchpadlibrarian.net/212294587/indicator-datetime_13.10.0%2B15.10.20150720-0ubuntu1_13.10.0%2B15.10.20150722-0ubuntu1.diff.gz and it got an empty changelog
[13:58] <sil2100> pete-woods: on it
[13:58] <pete-woods> sil2100: thanks :)
[13:58] <sil2100> pete-woods: actually, you can now reconfigure yourself! :)
[13:59] <pete-woods> sil2100: say what??
[13:59] <sil2100> I keep forgetting about that
[13:59] <sil2100> The train is becoming more and more self-service
[13:59] <pete-woods> sil2100: I don't see any links for that on the dash..
[14:00] <pete-woods> I take it the jenkins jobs are there
[14:00] <sil2100> anpok: ok, this is stupid... the train doesn't check all components, just one after another - now it's qtubuntu
[14:00] <pete-woods> I just need to know which to run
[14:00] <sil2100> pete-woods: you need to use the spreadsheet :)
[14:01] <sil2100> pete-woods: find your landing line (it's written on the dashboard), click on any cell of the row, go to the 'Landing tools' menu and Reconfigure ;)
[14:01] <pete-woods> sil2100: I'm on the line, but too stupid to find the Landing Tools menu
[14:02] <sil2100> pete-woods: it's next' to 'Help'
[14:02] <pete-woods> d'oh
[14:02] <pete-woods> seen it now
[14:02] <pete-woods> was looking in addons, etc
[14:02] <sil2100> :) No worries, soon the whole spreadsheet will be gone ;p
[14:02] <pete-woods> but won't you guys miss it?
[14:03] <sil2100> hm, a little bit, so much sweat and tears soaked into that spreadsheet
[14:03] <ogra_> google will surely miss getting all the incident reports
[14:04] <pete-woods> ha
[14:09] <elopio> nerochiaro: no, it should be enough. Maybe you are skipping the test but it's failing during the setUp?
[14:09] <nerochiaro> elopio: i am actually skipping the test during the setup, because the condition under which to skip the test will be detected only after the window appears
[14:10] <elopio> nerochiaro: then that should be enough.
[14:10] <elopio> do you have a trace and a link to the code?
[14:17] <nerochiaro> elopio: let me try that again. i have a suspicion that i want to verify before submitting an actual bug
[14:20] <anpok> sil2100: any idea why 0.14.0 is already in wily?
[14:20] <anpok> mir-0.14.0
[14:20] <sil2100> I don't know, I think this silo got published once right? But blocked in -proposed
[14:20] <anpok> that was my understanding .. yes!
[14:20] <anpok> but now:
[14:21] <sil2100> Yes, I see it's in -proposed indeed
[14:21] <sil2100> Ah, so those package versions were caused by the earlier mir landing
[14:21] <sil2100> ?
[14:21] <sil2100> The rebuilds requested?
[14:21] <anpok> http://archive.ubuntu.com/ubuntu/pool/main/m/mir/ <- there is a 0.14.0
[14:22] <anpok> seems so.. yes..
[14:22] <sil2100> If that's the case, let's force publishing - I'll double check that and try to force it
[14:24] <anpok> sil2100: thx
[14:25] <anpok> qtubuntu-gles now as a different version number -- but if it is true the source should be identical
[14:35] <kenvandine> mandel, so what's the plan for silo 9?  i see it's been approved to be published?
[14:35] <kenvandine> mandel, are you going to do a separate silo for vivid?
[14:36] <mandel> kenvandine, yes, that is the idea :)
[14:36] <mandel> kenvandine, do to click-scope
[14:36] <kenvandine> mandel, however... that silo has an unapproved merge proposal
[14:36] <anpok> sil2100: sorry for the fuzz .. those packages are still just in wily-proposed
[14:36] <sil2100> Yeah, we'll have to overwrite them
[14:36] <kenvandine> mandel, can you get that published so i can rebuild and publish my other silo?
[14:37] <mandel> kenvandine, vivid?
[14:37] <mandel> kenvandine, or the wily one?
[14:37] <kenvandine> wily
[14:37] <Laney> anpok: It's best to look on launchpad (https://launchpad.net/ubuntu/+source/mir) or use rmadison to see the archive state
[14:37] <kenvandine> i have a dual landing silo ready to go though :)
[14:37] <Laney> You can't see where packages are just by looking in the archive's pool
[14:37] <kenvandine> so i need to get your's published first
[14:37] <kenvandine> mandel, do you have a vivid silo already?
[14:38] <mandel> kenvandine, not yet, I had issues building the wily one, just got it fixed
[14:38] <mandel> kenvandine, I'm in a standup, as soon as I get out I'll create the vivid one
[14:38] <kenvandine> mandel, ok, thx
[14:38] <mandel> kenvandine, will ping someone to approve the mr missing
[14:38] <kenvandine> the udm branch is the one not approved
[14:38] <kenvandine> at least the only one i looked at :)
[14:39] <sil2100> anpok: I'm now double confirming if it's ok to land
[14:40] <anpok> it is ok
[14:40] <anpok> better than ok ..
[14:44] <sil2100> anpok: yep, confirmed
[14:44] <sil2100> Trying to force publish
[14:46] <sil2100> anpok: this silo has bad-luck - we have unbilt revisions here https://code.launchpad.net/~unity-system-compositor-team/unity-system-compositor/trunk/+merge/262866
[14:46] <sil2100> anpok: https://code.launchpad.net/~mir-team/qtubuntu/qtubuntu-gles-mir-release-0.14.0/+merge/264185 <- here as well, but we know about this one
[14:47] <anpok> sil2100: yip
[14:47] <sil2100> anpok: anyway, unity-system-compositior might require a rebuild (and qtubuntu-gles in the same time might be rebuilt as well, since why not?)
[14:47] <sil2100> anpok: or...
[14:47] <anpok> ok
[14:47] <sil2100> anpok: or you could revert the changes that got pushed to that u-s-c branch
[14:48] <sil2100> Not sure if that's wise though
[14:48] <anpok> hmm
[14:49] <sil2100> It's hard to say which new commits we're missing, would have to dig inside the train
[14:49] <sil2100> I suppose the 3 recent commits
[14:49] <anpok> yes
[14:49] <anpok> I am rebuilding those.
[14:50] <sil2100> anpok: fingers crossed that now we'll be able to JUST PUBLISH
[14:50] <sil2100> ;)
[14:51] <ChrisTownsend> sil2100: Hi!  So I want to add a slightly modified version of the lxc package to the vivid+overlay PPA.  What do I need to do to accomplish this?  Is there a Wiki or something so I don't need to pester you too much?
[14:52] <sil2100> ChrisTownsend: hey! Yes, the best way would be to use the train as then QA can do the necessary testing - we have some documentation for that:
[14:52] <sil2100> ChrisTownsend: https://wiki.ubuntu.com/citrain/LandingProcess
[14:53] <sil2100> ChrisTownsend: the "Landing your change to Ubuntu" has an overall train-guide, but "Landing your change to the Stable Overlay PPA" (or "Dual-landing for stable and devel" if that fits your project) is what you would be most interested probably
[14:53] <sil2100> Since the first section is more for people that never used the train before
[14:53] <sil2100> ChrisTownsend: you landed things through the CI Train already, right?
[14:53] <ChrisTownsend> sil2100: Ok, thanks!  I've used the train for Unity landings before, so I'm familiar with that.
[14:58] <ChrisTownsend> sil2100: Ok, since this is not a MP, I'll need to send you (or some other trainguard) the source package, right?  My plan was just to use "apt-get source lxc" in Vivid, make my changes, update changelog, and build source package.  Is this correct?
[14:59] <ChrisTownsend> sil2100: I'm looking at the "CI Train for manual source uploads" section.
[15:03] <sil2100> ChrisTownsend: yeah :)
[15:04] <sil2100> ChrisTownsend: well.. not exactly apt-get source
[15:04] <sil2100> ChrisTownsend: since the overlay already has some changes on top of it
[15:05] <sil2100> lxc-android-config 0.227 <- that's the version in overlay
[15:05] <ChrisTownsend> sil2100: Well, it's just the lxc package itself.
[15:05] <sil2100> Aaaaah!
[15:05] <sil2100> Sorry, yeah ;)
[15:05] <ogra_> ohh ...
[15:05] <ogra_> be very very careful with that though
[15:06] <sil2100> ChrisTownsend: right, then apt-get source is fine, sorry, miss-read that
[15:06] <ogra_> since our architecture kind of depends on a functioning lxc container for the android layer
[15:06] <sil2100> ChrisTownsend: but also make sure the same changes are in wily as well (if that's possible)
[15:07] <ChrisTownsend> ogra_: Hmm, ok.  What I'm doing is adding one line in debian/lxc.preinst to add a "phablet" user in the section that creates /etc/lxc/lxc-usernet.
[15:08] <ChrisTownsend> sil2100: I don't really want this to go in the wily archive.
[15:08] <ChrisTownsend> sil2100: Ideally, only the overlay PPA.
[15:08] <ogra_> ChrisTownsend, well, test it very carefully, we modify the hell out of lxc on the phone already to make the container work properly (there are various bits we had to disable like network support in containers and such)
[15:09] <ChrisTownsend> ogra_: Oh.....
[15:10] <ChrisTownsend> ogra_: Then this won't work anyways.  Back to the drawing board...
[15:13] <ogra_> ChrisTownsend, take a look at all the override upstart jobs in lxc-android-config ... thats our "hacks" pac kage for the phone where we keep them central
[15:13] <ChrisTownsend> ogra_: Ok, I'll take a look.  Thanks!
[15:29] <sil2100> mandel: some of your merges need approval/review:
[15:29] <sil2100> mandel: list here: https://ci-train.ubuntu.com/job/ubuntu-landing-009-2-publish/100/console
[15:37] <kenvandine> sil2100, don't let silo 9 land yet... mandel asked me to give it a quick test and i had problems
[15:37] <sil2100> ACK, let's switch it to 'not-tested' then
[15:37] <kenvandine> yeah
[15:38] <kenvandine> sil2100, done
[15:38] <sil2100> kenvandine: thanks :)
[15:39]  * kenvandine passes silo 9 and publishes 30 :)
[15:39] <kenvandine> mandel, sorry, silo 9 will also need a rebuild
[15:40] <kenvandine> mandel, with silo 9 it's just not downloading click updates :/
[15:52] <anpok> sil2100: silo 004 looks good..
[15:53] <sil2100> Ok, on it again
[15:57] <sil2100> anpok: were any packaging changes necessary to fix the boottest issues?
[15:58] <anpok> sil2100: we did bump an ABI for mir-graphics-drivers-android.
[15:58] <anpok> but it turned out not to be the cause..
[15:58] <anpok> sil2100: we fixed it by reverting abi breaking changes in libmirprotobuf0
[15:59] <sil2100> anpok: ok, let me just get someone re-approving the mir packaging changes then
[15:59] <sil2100> ogra_, slangasek: could anyone of you review this change? https://ci-train.ubuntu.com/job/ubuntu-landing-004-2-publish/82/artifact/mir_packaging_changes.diff
[16:00] <sil2100> Actually more slangasek would be required here, as we need an archive admin
[16:02] <kyrofa> trainguards: I saw my soli go from "in the Proposed pocket" to "empty," and my MPs were merged. Where does that mean my package is?
[16:03] <kyrofa> s/soli/silo/, apparently I'm dyslexic when I lack coffee
[16:03] <sil2100> kyrofa: hey, this means the package has been released to the main pocket and is now available in the target archives
[16:03] <sil2100> kyrofa: if it was a dual landing then it means that the package is now both in the vivid overlay-ppa and the wily archive
[16:03] <kyrofa> sil2100, sweet, I was hoping that was the case, but I searched packages.ubuntu.com and saw nothing. Does it take a while for that to update?
[16:04] <sil2100> kyrofa: what package did you publish?
[16:04] <kyrofa> unity-scope-snappy
[16:04] <sil2100> kyrofa: it's there already ;) https://launchpad.net/ubuntu/+source/unity-scope-snappy
[16:04] <sil2100> packages.ubuntu.com is not a super reliable source of information
[16:05] <sil2100> Not instantly reliable I would say
[16:05] <kyrofa> sil2100, heh, good to know. Alright great, thank you!
[16:08] <davmor2> sil2100, karni: all good to go on telegram
[16:08] <sil2100> davmor2, karni: let's ship it!
[16:08] <karni> davmor2: win \o/
[16:08] <karni> yes!
[16:09] <sil2100> It works now finally, yes?
[16:09] <jibel> davmor2, you tried on OTA4/5 too?
[16:09] <karni> sil2100: yes, we resolved the thumbnailer regression
[16:10] <davmor2> jibel: meh I forgot ota4, ota5 was good give me a minute karni and sil2100
[16:10] <sil2100> I think if OTA-5 is good then it should be good
[16:10] <karni> davmor2: naturally, take your time
[16:10] <karni> yes
[16:10] <karni> but davmor2's on the safe side to double check that
[16:11] <jibel> although if someone updates telegram he should see an upgrade to ota5
[16:11] <davmor2> sil2100: it will only take a couple of minutes after the flash
[16:17] <sil2100> slangasek, robru: could you guys make sure to release silo 004? It needs a force publish as the previous 0.14.0 is still in -proposed
[16:17] <sil2100> slangasek, robru: the mir packaging changes needs review by an archive admin, but then it should be fine to just force publish
[16:17] <sil2100> robru: and a reminder from me about the compoment name ci train branch!
[16:17]  * sil2100 needs to jump out now
[16:17] <sil2100> o/
[16:25] <davmor2> karni, jibel: video, image and text all sent on ota4 too
[16:26] <jibel> davmor2, \o/
[16:26] <karni> davmor2: \o/ !
[16:26] <karni> great news, thank you davmor2
[16:26] <davmor2> sil1200 has ofcourse disappeared now :0
[16:34] <fginther> ogra_, do you happen to know if the latest wily image (152) is known to work on krillin?
[16:34] <ogra_> fginther, https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1477051
[16:34] <ogra_> infinity, is on it
[16:34] <fginther> ogra_, danke!
[16:34] <ogra_> wall last nights wily buiolds are affected
[16:34] <ogra_> *all
[16:38] <infinity> ogra_: There's a build going on cdimage right now with the new live-build...
[16:39] <ogra_> yay
[16:39] <infinity> ogra_: Which I just realised will be broken, cause I didn't wait for it to migrate, and that build doesn't use proposed.
[16:39] <infinity> ogra_: So, uhm.  After this, there will be ANOTHER build that fixes it. :P
[16:39] <ogra_> heh, all fine
[16:39] <ogra_> it is wily after all
[16:39] <ogra_> as long as your change didnt migrate into vivid yet we're all fine
[16:39] <infinity> Yeahp, but I'm using wily to validate the bugfix for vivid (since the symptom and the fix are identical).
[16:40] <infinity> Fix is uploaded to both, so once I'm happy with the state in wily, then yay.
[16:40] <ogra_> yeah
[16:53] <robru> kenvandine: mterry: anybody got a sec for a packaging review? https://ci-train.ubuntu.com/job/ubuntu-landing-004-2-publish/82/artifact/mir_packaging_changes.diff/*view*/
[17:00] <slangasek> robru: that requires an archive admin review for package name changes
[17:01] <slangasek> I'm looking at it
[17:01] <slangasek> robru: and have all the other packaging changes in that silo already been reviewed?
[17:02] <robru> slangasek: yes, they were reviewed the last time it was published. I think by mterry.
[17:03] <slangasek> robru: ok.  and why is the build-dependency on abi-compliance-checker being dropped?
[17:04] <robru> slangasek: I dunno... anpok? ^^
[17:04] <slangasek> anpok: your mir upload in silo 004 is dropping the build-dependency on abi-compliance-checker relative to the archive, with no explanation in the changelog, no bug references, and we *just* got abi-compliance-checker promoted to main as part of an MIR to satisfy this build-depedency; nack on these packaging changes
[17:49] <kenvandine> anyone around that can override ubuntu-system-settings promotion to release in wily?  It's held because of a missing depends in autopilot, which I've proposed a fix for
[17:50] <ogra_> kenvandine, try #ubuntu-release perhaps ?
[17:50] <anpok> re
[17:51] <anpok> slangasek: we dropped it because it was optional, and we were asked to drop ist..
[17:52] <slangasek> anpok: who asked you to drop it?
[17:53] <anpok> slangasek: we intend to add it as soon as it is in main  https://bugs.launchpad.net/mir/+bug/1475982
[17:53] <slangasek> anpok: that's not how it works.
[17:55] <slangasek> anpok: first, the build-dependency on abi-compliance-checker has been in the mir packaging for at least one stable release (which means the MIR should have been done /last/ cycle).  Second, abi-compliance-checker is /already/ in main now, as a result of that MIR bug being processed.  And third, packages get *dropped from main* if they're not being used
[17:55] <slangasek> anpok: please revert this packaging change
[18:01] <anpok> this will take about an hour
[18:01] <anpok> slangasek: shall I ping you again as soon the landing ppa is updated again?
[18:14] <slangasek> anpok: yes, that's fine
[18:22] <jdstrand> fyi, not sure what is going on with the spreadsheet for telepathy-mission-control-5. the package is in stable-phone-overlay but the spreadsheet's Status cell is empty and the ppa is empty
[18:40] <slangasek> robru: ^^ spreadsheet explosion?
[18:41] <robru> jdstrand: what row?
[18:41] <jdstrand> 59
[18:42] <robru> jdstrand: are you surprised that the PPA is empty?
[18:42] <robru> jdstrand: sounds like you published it, and it published fine, but the spreadsheet just displays wrong/no status
[18:43] <jdstrand> robru: no, it was successfully copied over
[18:43] <jdstrand> robru: that is what happened. I just didn't do a merge/clean
[18:43] <jdstrand> so was mildly surprised it was empty
[18:43] <robru> jdstrand: yeah merge/clean happens automatically after a successful publish
[18:43] <jdstrand> so wanted to make sure it did the right thing
[18:43] <jdstrand> ah, ok
[18:43] <jdstrand> cool
[18:43] <robru> jdstrand: yeah the spreadsheet is a steaming pile, generally jenkins is working really well but the spreadsheet has trouble updating itself properly.
[18:56] <pmcgowan> robru, how do I tell citrain command I want vivid version of a package
[18:56] <pmcgowan> or dont I
[18:56] <robru> pmcgowan: point it at a silo containing vivid packages?
[18:57] <robru> pmcgowan: what's the scenario? are you trying to downgrade after having installed a silo?
[18:58] <pmcgowan> robru, I want silo 3
[18:58] <pmcgowan> which is dual landing
[18:58] <pmcgowan> do I just use ubuntu for the distro?
[18:59] <robru> pmcgowan: yes if your device is vivid you'll get the vivid packages, if your device is wily you'll get the wily packages
[19:00] <pmcgowan> robru, very good
[19:00] <robru> pmcgowan: thanks
[19:03] <pmcgowan> robru, is it supposed to get updates to every package that landed?
[19:04] <robru> pmcgowan: not sure what you mean. the tool will install every package in the silo onto the phone.
[19:04] <davmor2> pmcgowan: did you pin the silo first?
[19:04] <davmor2> pmcgowan: https://wiki.ubuntu.com/QATeam/TestingProcessesUbuntuPersonal
[19:05] <pmcgowan> robru, it updated everything in the overlay
[19:05] <robru> pmcgowan: oh yeah the version of the tool in vivid has a bug, if you branch the trunk version from lp:phablet-tools it should work
[19:05] <robru> pmcgowan: I believe that's expected, yes.
[19:05] <davmor2> pmcgowan: yes expected, but you probably didn't get the silo stuff unless you pinned it if you are running vivid on your desktop
[19:05] <pmcgowan> robru, I have the phablet-tools ppa enabled but dont see an update
[19:06] <pmcgowan> davmor2, did not know about pinning, but seems I got the package
[19:06] <robru> davmor2: the trunk version does the pinning.
[19:06] <davmor2> robru: oh nice
[19:06] <pmcgowan> robru, can you publish a citrain package in the tools ppa?
[19:07] <robru> pmcgowan: I'll have a look. never done that before
[19:09] <robru> sergiusens: who maintains phablet-team/tools ppa?
[19:27] <popey> robru: you mentioned it last, so you do. (I don't think anyone does)
[19:27] <robru> popey: cool, I'll just build some packages quick and cram 'em in there then
[19:29] <robru> anpok: lol, you missed: https://ci-train.ubuntu.com/job/ubuntu-landing-004-1-build/lastSuccessfulBuild/artifact/mir_packaging_changes.diff/*view*/
[19:29] <robru> slangasek: new packaging diff w/abi-compliance-checker restored: https://ci-train.ubuntu.com/job/ubuntu-landing-004-1-build/lastSuccessfulBuild/artifact/mir_packaging_changes.diff/*view*/ wanna ack?
[19:34] <robru> mandel: https://ci-train.ubuntu.com/job/ubuntu-landing-009-2-publish/101/console need these merges top-approved
[19:39] <robru> davmor2: pmcgowan: ok I have an updated phablet-tools-citrain package uploaded to phablet-team/tools PPA, can you guys update to that and check if the silo pinning works correctly in vivid?
[19:49] <kenvandine> mandel, i did find a problem with silo 9... your unity-scope-click branch used in the silo has been superseded, and the new branch has conflcts
[19:50] <kenvandine> mandel, i think we can just change the status from superceded though
[19:50] <kenvandine> but we should have something from the right team set it to approved
[19:51] <kenvandine> mandel, ok, i changed it to needs review... which is weird because it still says it's superseded :)
[19:51] <kenvandine> but i think that's ok, just need someone to approve it
[20:10] <mandel> kenvandine, ok, that is weird..
[20:11] <mandel> kenvandine, sorry, I was having dinner..
[20:11] <mandel> kenvandine, is 22 here, I'm going to rest for the rest of the day, will do as much as possible in the morning to fix that
[20:23] <slangasek> robru: yes, ack on the mir packaging now
[20:26] <slangasek> robru: trying to publish fails because trust-store was already published to the archive, is that the bit that sil2100 was saying needs forced?
[20:27] <robru> slangasek: let me check
[20:28] <robru> slangasek: yeah seems so. I should really fix that check so that it doesn't block on packages dangling in -proposed
[20:28] <slangasek> robru: er, that doesn't sound right
[20:29] <robru> slangasek: hm?
[20:29] <slangasek> the purpose of this check is to avoid accidentally clobbering changes from another silo that have already been published
[20:29] <slangasek> skipping the warning for packages which are in -proposed just means you're letting things be clobbered
[20:29] <robru> slangasek: don't we already have a silo dirty check for that? the purpose of this check is to not clobber manual archive uploads done by non-train-users
[20:30] <robru> slangasek: anyway I'll force publish for now
[20:30] <slangasek> robru: the version numbers shown there are not manual uploads
[20:31] <slangasek> and being in -proposed vs. wily again does nothing to invalidate this check
[20:31] <robru> slangasek: no, but that's because the check just says "this version is different than it used to be!" it doesn't inspect what the version number is
[20:31] <slangasek> "ERROR Version of trust-store at dest changed from 1.1.0+15.04.20150213-0ubuntu1 to 1.1.0+15.10.20150629-0ubuntu1 since packages built".
[20:31] <kenvandine> mandel, no problem
[20:32] <slangasek> 1.1.0+15.10.20150629-0ubuntu1 wasn't a manual upload, that came from another silo landing
[20:32] <kenvandine> mandel, i think we just need someone to give the current branch an ack and set it to approved
[20:32] <robru> slangasek: or an earlier publish of this same silo
[20:32] <kenvandine> even though it's superseded, this is the branch we tested and it should be fine to land
[20:32] <slangasek> ah
[20:32] <robru> slangasek: point is, that check was written in order to protect manual uploads by other people. my argument is that because this isn't a manual upload, it's a false positive, and should not be blocking publishing
[20:33] <slangasek> robru: ok, but that has nothing to do with "packages dangling in -proposed" which was what you first said
[20:34] <robru> steve pls
[20:34] <robru> slangasek: "packages dangling in -proposed" means "we're fixing a previous publish that failed and got stuck in -proposed"
[20:36] <robru> slangasek: I feel like this is a false positive on that test. sometimes silos get published and then fail in -proposed and need to be rebuilt & republished. but *every time* that happens, that check explodes because it finds it's own version in -proposed and says "hey, that's not the right version!" and prevents you from publishing
[20:36] <slangasek> right
[20:36] <slangasek> I agree this is a false positive
[20:37] <robru> slangasek: so if that test was changed to ignore versions in -proposed, it wouldn't false positive like this ;-)
[20:43] <slangasek> robru: that's still the wrong fix.
[20:43] <slangasek> just because the package is in -proposed at the time you click 'publish' does not mean it's ignorable
[20:44] <slangasek> (or stuck, or from this silo...)
[20:45] <robru> slangasek: right
[23:07] <fginther> anpok, robru, FYI unity-system-compositor from http://people.canonical.com/~platform/citrain_dashboard/#?q=ubuntu%2Flanding-004 is having trouble in boottest
[23:08] <fginther> it appears that adb fails to come up after the reboot. Testing locally to confirm
[23:10]  * fginther goes offline for dinner
[23:21] <robru> fginther: I'm seeing a mix there. it used to be they all had boottest regressions now it seems only some do. Did you retry all of them?
[23:24] <fginther> robru, the *gles packages failed due to a known bug so they can be ignored. I've only retried unity-system-compositor locally so far
[23:24] <fginther> robru, anpok, and can confirm that unity-system-compositor boottest fails locally. After rebooting, the device is stuck on the Google screen
[23:24] <robru> fginther: hm, that is worrying. I guess we'll have to leave for anpok to investigate, it's not my area
[23:25] <fginther> robru, right, just trying to pass on the failure info since boottest has been less then reliable
[23:25]  * fginther leaves again