[02:04] <imgbot> [03:04] <imgbot> [04:09] <imgbot> [04:09] <imgbot> [04:19] <imgbot> [04:19] <imgbot> [05:26] <Mirv> mornings
[05:56] <robru> Mirv: heya. everything's back to normal but there'll probably be lots of failed merges. each time a merge fails you have to investigate the target branch and then make sure ci-train-bot gets added to the right team to gain access to that branch ;-)
[05:57] <Mirv> robru: heya. yes, I read the e-mails, makes sense.
[05:59] <robru> Mirv: cool, have fun!
[06:00] <Mirv> sure!
[06:08] <robru> Mirv: ^^ oh yeah that message means 'job aborted', will clean that up later.
[08:55] <ogra_> argh ... my whole browser history and all open tabs are gone after the latest upgrade
[08:56] <sil2100> ogra_: in vivid?
[08:56] <ogra_> no
[08:56] <sil2100> On RTM?!
[08:56] <ogra_> on my krillin
[08:56] <ogra_> webbrowser-app was upgraded in 173
[08:56] <ogra_> oSoMoN, hey
[08:57] <oSoMoN> ogra_, morning!
[08:57] <ogra_> oSoMoN, looks like all my open tabs and my browser history are gone with the recent rtm upgrade
[08:57] <jibel> I'm on 173, history and open tabs are still there.
[08:58] <oSoMoN> huh, that’s unexpected, let me see if that happens for me (not upgraded my krillin yet)
[08:58] <oSoMoN> ogra_, do you still have files under ~/.local/share/webbrowser-app/ ?
[08:58] <ogra_> i havent seen the ubuntu start page in quite a while :)
[08:59] <ogra_> yep, i do ...
[09:00] <ogra_> should i have a session.json.lock file even with the browser closed ?
[09:01] <ogra_> apart from Cache and cookies.sqlite nothing has a timestamp from today
[09:02] <ogra_> aha
[09:02] <ogra_> removing the .lock file gets me my session back
[09:03] <oSoMoN> ogra_, that’s weird, the lock file is associated to a given PID, did you have a stale webbrowser-app process by any chance?
[09:04] <ogra_> heh, i doubt i can find that out now
[09:04] <oSoMoN> right
[09:04] <ogra_> if there was one it is gone
[09:04] <oSoMoN> let me upgrade my krillin and see if I can observe the same thing
[09:06] <sil2100> ogra_: btw. I just noticed that the cgmanager fix we had deployed for ubuntu-rtm still didn't make it to vivid - does this mean vivid is uneffected by this big bug?
[09:07] <ogra_> sil2100, hmm, it shouldnt
[09:10] <oSoMoN> ogra_, just upgraded, and all is fine, I got my history and open tabs back
[09:11] <Mirv> ^ those two landings are marked as Landed for some reason, while they are not... I'm trying to see whether I could get the status right (and then publish mine)
[09:12] <ogra_> hmm, i have no recent webbrowser-app crash files either ...
[09:14] <Mirv> hmmph, no luck
[09:16] <Mirv> ah, yes, the O column was broken
[09:20] <sil2100> Mirv: the formula was missing?
[09:23] <Mirv> sil2100: yes. apparently nowadays the Train writes manually "Landed" over there (a fix for those pending "Merging..." things?), so because it for some reason had thought they had landed the formula was no longer there
[09:23] <Mirv> uh oh, publish broken for it, anyhow!
[09:23] <Mirv> reconfigured, watch only worked, publish - https://ci-train.ubuntu.com/job/ubuntu-landing-005-2-publish/52/console
[09:24] <Mirv> oh, hmm, the rsync file looks correct, why the console looks empty then?
[09:25] <Mirv> sil2100: maybe that's the new normal then, additional source packages are not noticed in the publish console log at all?
[09:25] <Mirv> that's ok, the rsync file is useful to check manually anyway
[09:42] <Saviq> Mirv, sorries again, silo 1 all approved!
[09:45] <Mirv> Saviq: ok!
[09:54] <Mirv> pstolowski: you'd need to rebuild the unity8 silo 012 unfortunately since like robru has mentioned there was another unity8 landing (not sure why both were assigned a silo)
[09:56] <Saviq> Mirv, that was expected
[09:57] <pstolowski> Mirv, hey, yeah, I saw the comments. waiting for 03 to land
[09:57] <Mirv> pstolowski: oh, you're correct, why it's in proposed...
[09:59] <Mirv> bzoltan: the oxide landing has now broken things, it will be probably reverted
[10:01] <Mirv> catz!
[10:01] <Mirv> sil2100: ^
[10:01] <Mirv> sil2100: I mean, the oxide landing
[10:02] <Mirv> sil2100: https://lists.canonical.com/archives/vivid-changes/2014-December/002230.html apparently causes now autopkgtest failures, so it would probably need to be reverted
[10:02] <Mirv> hmm, where did pstolowski go...
[10:05] <sil2100> Mirv: revert needed? :)
[10:07] <Mirv> sil2100: yeah, I'm doing one now. but I also forced m&c on 003 since the problem was not related to that landing, so that pstolowski can continue on 012.
[10:08] <sil2100> Is it just oxide? Or multiple components need reverting?
[10:09] <Mirv> sil2100: just oxide. it was a packaging change for SDK / Click chroot needs, but apparently not perfect
[10:31] <bzoltan> Mirv:  what the problem is?
[10:32] <Mirv> bzoltan: https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1399597
[10:32] <ubot5`> Launchpad bug 1399597 in oxide-qt (Ubuntu) "The last oxide upload breaks autopkgtests" [Undecided,New]
[10:32] <Mirv> so unity8 etc blocked in -proposed because of those failing autopkgtests, ie failing packages to install
[10:34] <bzoltan> Mirv:  how is that oxide issue? I see a broken environment there. The clonflict works as we planned. But why dpkg thinks that the codecs package is there when it is not???
[10:35] <bzoltan> Mirv:  But good to know that it is not a runtime breakage but an autopkgtest thingy
[10:41] <Mirv> bzoltan: it's apt / installing packages failure. maybe apt gets confused by the complex conflict definitions.
[10:41] <Mirv> so it's not random test failure, it's something that needs a fix (or a revert)
[10:42] <bzoltan> Mirv:  do we have a silo or a PPA with the new oxide, so I could work on it?
[10:43] <Mirv> bzoltan: 003 has the revert, further uploads can be made to try to get the fix done. first it'd be nice to know how to reproduce the problem.
[10:44] <seb128> Mirv, does the revert means going back to not being able to create frameworks env again?
[10:50] <Saviq> Mirv, help... https://ci-train.ubuntu.com/job/check-publication-migration/71833/console
[10:52] <Saviq> the branch it pushed to looks b0rken
[10:52] <Saviq> lp:~/cmake-extras/latestsnapshot-ubuntu-recup
[10:52] <Saviq> pete-woods, jenkins has no rights to push to lp:cmake-extras :?
[10:52] <pete-woods> Saviq: weird!
[10:53] <Saviq> pete-woods, well, not really weird, there's a "cmake-extras" team that's not part of PS and stuff
[10:53] <pete-woods> Saviq: yeah. that's what I meant was weird
[10:53] <pete-woods> tempted to make it owned by someone else
[10:54] <Saviq> the project is definitely not set up right
[10:54] <Saviq> https://launchpad.net/cmake-extras
[10:54] <pete-woods> Saviq: blame allan :)
[10:54] <Saviq> pete-woods, can you hcange the maintainer to PS PM team
[10:54] <Saviq> pspmteam
[10:55] <pete-woods> Saviq: done
[10:55] <Saviq> pete-woods, and add canonical-product-strategy to the cmake-extras team
[10:56] <pete-woods> jenkins bot just joined the team it seems :)
[10:56] <pete-woods> okay, added canonical-product-strategy
[10:57] <Saviq> pete-woods, thanks, that should sort things out for now
[10:57] <pete-woods> cool
[10:58] <Saviq> sil2100, uh oh, what are the empty commits in https://code.launchpad.net/~mir-team/qtmir/trunk ?
[10:58] <Saviq> same in https://code.launchpad.net/~mir-team/qtmir/gles
[11:01] <Saviq> looks like the repeated jobs failing to push to cmake-extras trunk resulted in these empty commits
[11:01] <Mirv> seb128: it would mean that, yes... so a fix would be nicer, if someone understands the problem
[11:02] <Mirv> Saviq: that means the new user needs to be added to the team
[11:02] <Saviq> pete-woods, ah, there's a different bot now, "CI Train Bot", it worked before because PS Jenkins Bot was already there
[11:02] <Saviq> Mirv, yeah, added canonical-product-strategy to the team
[11:02] <Saviq> pete-woods, you can drop the explicit membership of PS Jenkins Bot
[11:03] <sil2100> Saviq: it would be best it you added ubuntu-unity to the mir-team members as well
[11:04] <Saviq> sil2100, done, is that the preferred solution now? to add ubuntu-unity to the owner/driver teams?
[11:05] <Saviq> (and not canonical-product-strategy?)
[11:05] <Saviq> pete-woods, ↑
[11:07] <pete-woods> Saviq: I've dropped the jenkins bot
[11:07] <Saviq> Mirv, sil2100, in any case there seems to be a bug or two in the publishing job (see the blank commits at the top of qtmir and qtmir-gles)
[11:07] <Mirv> Saviq: you need this guy http://launchpad.net/~ci-train-bot added to all teams
[11:07] <Saviq> and then there's the temp branch to which the bot supposedly tried to push
[11:08] <pete-woods> Saviq: I'll set the owner / driver to whatever is expected
[11:08] <Mirv> nothing else needs changing
[11:09] <Saviq> Mirv, I'd rather not have a single user to be added, because it might change again ;)
[11:09] <Saviq> ubuntu-unity sounds like a good compromise
[11:09] <Mirv> right, so ci-train-bot to the ubuntu-unity team? why not
[11:09] <Saviq> it's there already
[11:10] <Saviq> and yeah, the publish job is missing "ci-train-bot" in the string where it says it pushed things
[11:13] <Saviq> and then it pushes some random empty commits ;(
[11:13]  * Saviq purges them
[11:25] <Ursinha> sil2100: are you looking into the publisher bug? if not I'll file one so robru can work on it when he's here
[11:25] <sil2100> Ursinha: a bug would be good to have anyway, but I'm briefly looking at it
[11:25] <Ursinha> sil2100: also, were you able to add all the subscriptions necessary to the bot? I can help you with some lp api foo if you want to check that in a more automated way :)
[11:26] <Ursinha> sil2100: I'll file one for you then
[11:26] <sil2100> Ursinha: thanks!
[11:26] <sil2100> :)
[11:28] <Ursinha> Saviq: would you have a way to see the empty commits in those branches you mentioned? I see you might have deleted them already
[11:29] <Ursinha> just so I can add to the bug about the publisher being silly
[11:30] <Saviq> Ursinha, sorry, no, they just said "Resync trunk" and were empty
[11:30] <Saviq> Ursinha, I wanted them gone asap so they don't populate among devs
[11:31] <Ursinha> Saviq: fair enough :) some information is better than none, thanks!
[11:31] <Saviq> Ursinha, should have backed them up before that
[11:31] <Saviq> Ursinha, but really it was just an empty commit by CI Train Bot with "Resync trunk" as the commit message
[11:31] <sil2100> Saviq: do you remember which silo landing caused this?
[11:31] <Saviq> sil2100, 1
[11:32] <Ursinha> Saviq: that's fine, just let me know if that happens again then we can add to the bug, if not fixed yet
[11:32] <sil2100> Thanks
[11:32] <Saviq> sil2100, it tried multiple times because it couldn't push to lp:cmake-extras
[11:33] <Saviq> sil2100, Ursinha, this is what caused it https://ci-train.ubuntu.com/job/check-publication-migration/71833/console
[11:33] <Saviq> sil2100, Ursinha, ah I know what happened
[11:33] <Saviq> it pushed qtmir and qtmir-gles to trunks on the first try
[11:34] <Saviq> and then noticed that trunks are ahead of what the silo branches were built on
[11:34] <Saviq> so decided it needs to reconcile
[11:34] <Saviq> and so on, and so on
[11:34] <Ursinha> hmm
[11:34] <sil2100> Yeah
[11:34] <Ursinha> thanks Saviq
[11:34] <sil2100> Since now it auto merges and it doesn't fail as normal merge and cleans do
[11:34] <Ursinha> sil2100: it should keep failing
[11:35] <sil2100> Ursinha: it should keep failing but not try to push branches that already got pushed
[11:35] <Saviq> this is a rather corner case
[11:35] <Ursinha> sil2100: I mean, the auto merge should happen only if it can be merged, there's no point forcing a merge that wouldn't happen before (am I overlooking something?)
[11:35] <Saviq> where it couldn't push to the project's trunk
[11:35] <Ursinha> Saviq: I'm yet to find something landing-related that's not a corner case :)
[11:35] <sil2100> Ursinha: well, this should be fixed in such a way that it should register which merges it succeeded with and not try to push those again
[11:36] <Ursinha> sil2100: that's a good plan
[11:36] <sil2100> The main problem is that we have no feedback right now
[11:36] <sil2100> So we would also have to add this
[11:36] <sil2100> i.e. in this case it remembers which components succeeded and inform the frontend that some M&C's failed
[11:43] <Ursinha> sil2100: what do you think? bug 1399625
[11:43] <ubot5`> bug 1399625 in CI Train [cu2d] "publisher job is pushing empty commits" [Undecided,New] https://launchpad.net/bugs/1399625
[11:58] <sil2100> Damn, so many things changed in the publisher
[12:00] <sil2100> Ursinha: thanks :)
[12:04] <Ursinha> sil2100: yeah, it was hard to review that branch :) but I have a good idea on what changed if there's something I could help shedding a light on
[12:04] <Ursinha> re. publisher
[12:38] <pstolowski> trainguards may i ask for publishing of silo 12?
[12:39] <Mirv> pstolowski: sure
[12:51] <jgdx> trainguards: hi, can I have spreadsheet perms or can you mark rtm-004 as tested OK "Yes (#10 krillin jgdx)"
[12:53] <Mirv> jgdx: sil2100 could give you rights, but I'll do what you asked anyhow
[12:54] <jgdx> Mirv, thank you.
[13:07] <seb128> jgdx, is #10 a krillin rtm revision?
[13:07] <jgdx> seb128, yes
[13:07] <seb128> weird
[13:07] <seb128> I though we were at 173 on krillin rtm
[13:07] <seb128> those numbers confuse me ;-)
[13:07] <jgdx> used ubuntu-touch/ubuntu-rtm/14.09
[13:08] <jibel> seb128, it's the released version, proposed is 173
[13:08] <seb128> jibel, oh ok
[13:09] <seb128> jibel, I though we had promotions are 169
[13:09] <seb128> are->around
[13:09] <seb128> or is that "proposed r169 becomes stable r10"?
[13:09] <jibel> seb128, right, 14.09/10 = 14.09-proposed/10
[13:10] <jibel>  14.09/10 = 14.09-proposed/169
[13:10] <jibel> sorry
[13:10] <seb128> k
[13:10] <jibel> I'm confused too :)
[13:10] <seb128> confusing still ;-)
[13:10] <seb128> thanks
[13:53] <pmcgowan> sil2100, how is silo 16 coming
[13:55] <Saviq> jibel, as you know bits'n'bobs about adt... http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#unity-api
[13:56] <jibel> Saviq, looking
[13:56] <Saviq> looks like unity8 and unity-api are blocked on the two failures
[13:56] <Saviq> jibel, which seems to be a oxideqt-codecs uninstallability issue
[13:57] <Mirv> robru: sil2100: please read through bug #1399597 and hopefully land the Oxide (if ok for everyone) in the US timezone in about 5 hours. the theory is that it'd fix the bug without causing regression for the SDK guys. that bug blocks many vivid proposed->release migrations at the moment, so either a revert or this fix is needed anyhow.
[13:57] <ubot5`> bug 1399597 in oxide-qt (Ubuntu) "The last oxide upload breaks autopkgtests with a package installation failure" [Undecided,New] https://launchpad.net/bugs/1399597
[13:57] <sil2100> pmcgowan: the silo is now built with latest changes, waiting for Ken to appear and do silo testing
[13:58] <Saviq> jibel, oh actually looks that's what Mirv just wrote about
[13:58] <pmcgowan> sil2100, ok I may load it up as well
[13:58] <jibel> Saviq, okay
[13:59] <sil2100> We want to land it today so that it can be widely tested by Monday by everyone
[13:59] <Mirv> Saviq: yes..
[15:15] <sil2100> o/
[15:18] <ogra_> pushy bot !
[15:27] <pmcgowan> jgdx, are you looking at the silo 2 failure
[15:27] <jgdx> pmcgowan, yeah, pushed a fix
[15:27] <pmcgowan> great
[15:28] <pmcgowan> jgdx, you lost silo karma though
[15:29] <jgdx> pmcgowan, oh man, we're keeping score?
[15:29] <pmcgowan> jgdx, we are indeed
[16:04] <sil2100> Ursinha: ah, forgot to ask before lunch - do we have the staging instance up and running already? :)
[16:04] <ogra_> hmm, still no ken :/
[16:06] <Ursinha> sil2100: the citrain one? :) there is one partially working, and I can point you to that so you can have a look :)
[16:06] <Ursinha> sil2100: on bootstack
[16:09] <sil2100> Ursinha: since I suppose I need a way to test my fix before doing a global deployment, and I think preprod won't work anymore since the permission change, right?
[16:10] <kgunn> sil2100: quick theoretical question....if something were merged into our mir0.8 branch, but didn't go thru silo...would it ever hit the image ?
[16:10] <kgunn> or is the image ever only created off source tarballs
[16:10] <kgunn> ....and if someone were to do a rebuild, is that off the tarball or proj branch ?
[16:11] <cjwatson> the image is only ever created based on binaries in the archive, which are only ever created based on source packages
[16:11] <sil2100> kgunn: it won't be in the image until you get trunk released through the silo
[16:11] <kgunn> awesome
[16:11] <kgunn> camako: you won ^
[16:11] <camako> cool
[16:11] <sil2100> kgunn: so if you have that, just prepare a silo with a merge (can be even an empty merge) to get the current trunk released into the archive
[16:12] <Ursinha> sil2100: we need to talk about how the staging instance is going to be, if that is supposed to be really a pre-production and contain MP approved code, it's easier
[16:13] <Ursinha> sil2100: if you want to be able to deploy whatever the hell you want, then I can teach you how to locally deploy with juju and lxc :)
[16:27] <bfiller> sil2100: can you publish ubuntu silo 2 please
[16:29] <sil2100> bfiller: looking!
[16:30] <sil2100> robru: wow, I found an issue in the new publisher
[16:30] <sil2100> robru: you're actually showing all packaging diffs, even for old versions from the PPA
[16:30] <sil2100> robru: so if there were 3 rebuilds of a package in the PPA, the packaging diff is uploaded 3 times
[16:30] <sil2100> robru: https://ci-train.ubuntu.com/job/ubuntu-landing-002-2-publish/
[16:35] <cjwatson> oh thank God, node-mapnik finally built.  so the protobuf transition (with no-change rebuilds of compiz and mir) should land shortly.
[16:40] <sil2100> \o/
[16:48] <Saviq> trainguards, is a set of 4 bugs as seen in row 76 acceptable for a RTM landing? if so, can you please get me a silo ↑?
[16:50] <sil2100> jibel: are we proceeding according to the threshold rules already?
[16:50] <sil2100> Saviq: let me quickly get some answers
[16:51] <Saviq> sil2100, can you assign a silo for line 74 regardless, we'll not build before silo 12 lands
[16:51] <ogra_> sil2100, i dont think we have made the new rules public yet
[16:51] <ogra_> (unless i missed a mail)
[16:52] <sil2100> Saviq: I suppose it's still not public
[16:52] <sil2100> ogra_: pmcgowan mentioned it here so I thought we're already using it
[16:52] <ogra_> sil2100, we dont use anything without telling the developers in advance i hope :P
[16:53]  * sil2100 hopes as well
[16:53] <sil2100> I was out sick for the first 2 days so I could have missed it ;)
[16:54] <ogra_> no, i dont think we have published anything, only discussed it
[16:54] <ogra_> so we cant really use it yet
[16:54] <sil2100> ogra_: especially that we still didn't formally define the 'fix' notion ;)
[16:55] <ogra_> right
[16:55] <sil2100> pmcgowan: hey! I think we can land a translation enablement to ubuntu-rtm, right?
[16:55] <pmcgowan> sil2100, yes is that sebs fix?
[16:55] <sil2100> pmcgowan: since seb128 prepared a sync silo for ubuntu-ui-extras to use langpacks
[16:55] <pmcgowan> yes approved that
[16:56] <sil2100> Oh, right, I digged up the bug number from the original package an now I see
[16:56] <sil2100> Let me modify the landing description
[16:56] <seb128> sil2100, did I copy the wrong bug reference there?
[16:57] <sil2100> seb128: it's all ok, just want it to be in the landing description as well for QA to have better access to it
[16:58] <seb128> sil2100, I put it as a comment
[16:58] <seb128> but ok ;-)
[16:58] <seb128> noted for next time
[16:58] <seb128> sil2100, thanks for fixing it!
[16:59] <sil2100> seb128: no worries, not a big issue, it was my bad in overall
[16:59] <sil2100> ogra_: and still no ken :(
[16:59] <ogra_> yeah :(
[16:59] <ogra_> and two other system-settings silos too
[16:59] <seb128> sil2100, I think Ken is off today?
[17:00] <seb128> that's what Jonas said earlier
[17:00] <ogra_> assuming these need to go first :/
[17:01] <sil2100> Not sure, I think the order is not strict
[17:01] <sil2100> But still, without Ken around we might not make it
[17:01] <sil2100> Not much we can do though
[17:02] <sil2100> ogra_: still in a meeting?
[17:02] <ogra_> on my way
[17:02] <sil2100> plars: ping o/
[17:03] <sil2100> plars: (although the network issues are probably still there and not much CI updates will be available)
[17:12] <plars> sil2100: sorry, had to step away for a few, yeah, not much I can do until the move is complete
[17:18] <bfiller> sil2100: we had a couple of MR's land yesterday in silo (maybe day before) in camera-app that seem to be in trunk but the MR's have not been updated to merged
[17:19] <bfiller> sil2100: https://code.launchpad.net/~fboucault/camera-app/camera-app-multi_selection/+merge/243385 and https://code.launchpad.net/~fboucault/camera-app/camera-app-self_timer/+merge/243389
[17:28] <robru> bfiller: hm, that's odd. those look merged in trunk with the old creds from before citrain went down
[17:29] <bfiller> robru: yeah, for some reason the MR's didn't get updated it seems
[17:35] <robru> bfiller: tough to say what could have caused that. citrain doesn't have any code that tells lp to mark merges as merged, lp just does that automatically when the commits appear in trunk. so it seems more like a bug in lp than in the train. I don't see any harm in marking them merged manually
[17:35] <bfiller> robru: ack
[17:52] <bfiller> robru: needs silos for 77 and 78 when you have a chance
[17:54] <robru> bfiller: alright, vivid 7, rtm 11
[17:55] <bfiller> robru: cheers
[17:55] <robru> bfiller: you're welcome
[17:59] <cjwatson> bfiller,robru: hm, that's curious, let me see if I can find logs about that
[18:01] <bfiller> cjwatson, robru: seems what was merged was a few revs back than the latest in the MR's. Not sure why that happened, possibly I didn't rebuild the silo
[18:01] <bfiller> could be my fault
[18:01] <robru> bfiller: if you didn't rebuild the silo that means those latest revs are also not in distro ;-)
[18:02] <bfiller> robru: I know
[18:03] <bfiller> we haven't released a click as we don't have a way to only release it for vivid, so only the debs will be wrong and they are not really used. but'll we;ll correct on the next upload
[18:04] <cjwatson> bfiller,robru: Those weren't actually the branches that were merged.
[18:04] <cjwatson> [2014-12-04 22:16:00,480: INFO/PoolWorker-2] Merge detected: lp:~artmello/camera-app/camera-app-multi_selection => lp:camera-app
[18:05] <cjwatson> [2014-12-04 22:16:00,497: INFO/PoolWorker-2] lp:~artmello/camera-app/camera-app-multi_selection now Merged.
[18:05] <cjwatson> [2014-12-04 22:16:00,526: INFO/PoolWorker-2] Merge detected: lp:~artmello/camera-app/camera-app-self_timer => lp:camera-app
[18:05] <cjwatson> [2014-12-04 22:16:00,533: INFO/PoolWorker-2] lp:~artmello/camera-app/camera-app-self_timer now Merged.
[18:05] <cjwatson> Not the same owner.
[18:05] <robru> bfiller: I guess you merged the pre-superceded MPs then
[18:06] <cjwatson> And if you check out lp:camera-app and run "bzr missing --theirs lp:~fboucault/camera-app/camera-app-multi_selection" and "bzr missing --theirs lp:~fboucault/camera-app/camera-app-self_timer", you can see the commits on those branches that aren't merged.
[18:08] <cjwatson> So yeah, don't mark those as merged manually unless the same textual content was actually merged and you want to effectively abandon whatever different history is on those branches.
[18:19] <bfiller> cjwatson: thanks
[18:23] <pmcgowan> ogra_, sil2100 I ran silo 16 all day, can we have QA check it now
[18:25] <ogra_> pmcgowan, well, we have 3 silos with system-settings ...
[18:25] <ogra_> 16 is the one that hasnt even been set to testing done
[18:25] <pmcgowan> it is now
[18:25] <ogra_> and ken is off today
[18:26] <pmcgowan> its not really a system settings issue, its the nasty powerd events dus eats cpu thing
[18:26] <pmcgowan> dbus
[18:26] <sil2100> pmcgowan: we weren't sure if we can land that, since we wanted to know from Ken if it's good to land before all those other ones
[18:26] <pmcgowan> sil2100, I see, I dont know about ordering them
[18:26] <popey> ooh, is it the one that makes system settings hang after boot?
[18:26] <pmcgowan> yep
[18:26] <popey> s/boot/resume/
[18:26] <popey> oh man
[18:26] <pmcgowan> popey, if it cant land maybe you can run it over the weekend
[18:26] <ogra_> popey, yes, it is that one
[18:27] <popey> sure thing!
[18:27] <ogra_> ToyKeeper ran it over night for one night already
[18:27] <popey> ok, I'll install now and not reboot this weekend.
[18:27] <popey> thanks chaps!
[18:27] <pmcgowan> ogra_, sil2100 ok so I guess wait for ken on monday and more results
[18:28] <ogra_> yeah :(
[18:28] <popey> got a link to it?
[18:28] <ogra_> i wish we could have an image for the weekend testing
[18:28] <pmcgowan> me too
[18:28] <pmcgowan> that was my urgency testing it
[18:28] <ToyKeeper> Oh, silo rtm-16?  It seemed to cut the dbus noise in half and reduce side effects by even more.
[18:28] <ToyKeeper> I only tried it for one night though.
[18:29] <ogra_> yeah
[18:29] <pmcgowan> the silo got tweaked to have a more exact system settings change set
[18:29] <pmcgowan> thats the only change from before
[18:31] <popey> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-016
[18:31] <popey> that seems empty?
[18:31] <ogra_> ubuntu-rtm
[18:31] <popey> aha
[18:31] <popey> ta
[18:37] <popey> dpkg: error processing archive powerd_0.16+15.04.20141031.2~rtm-0ubuntu1_armhf.deb (--install): unable to make backup link of `./usr/share/powerd/device_configs/config-default.xml' before installing new version: Invalid cross-device link
[18:37] <popey> is that normal?
[18:45] <popey> ogra_: ^ any ideas?
[18:52] <ogra_> popey, oh, powerd needs to be installed via recovery
[18:52] <popey> oh, how?
[18:52] <popey> boot to recovery, then is there some other magic than just dpkg -i the deb?
[18:59] <popey> ogra_: sorry, I don't know how to install this.
[19:01] <ogra_> popey, https://wiki.ubuntu.com/Touch/Testing/lxc-android-config same process
[19:01] <popey> ta
[19:04] <popey> sh is missing...
[19:05] <ogra_> try /bin/sh
[19:06] <popey> http://paste.ubuntu.com/9386061/
[19:06] <popey> ⍨
[19:06] <ogra_> (even though the env command should have set your path properly)
[19:06] <popey> is that okay?
[19:06] <popey> invoke-rc.d: unknown initscript, /etc/init.d/powerd not found.
[19:06] <ogra_> theoretically, yes
[19:07] <popey> so reboot and it should be sane?
[19:07] <ogra_> no
[19:07] <ogra_> the install obviously failed ...
[19:07] <ogra_> iirc davmor2 and jibel have better ways to install such packages
[19:07] <popey> ☹
[19:07] <ogra_> hmm, or was that brendand
[19:08]  * popey wonders if any of them are about
[19:08] <popey> ToyKeeper: how did you install that powerd package when you tested it?
[19:17] <robru> popey: ⍨ is the greatest emoticon ever, how did I not know about this?
[19:17] <popey> hah
[19:23] <dobey> cihelp: does jenkins MP testing run autopkgtests on the proposed change as well?
[19:23] <fginther> dobey, autopkgtests are not executed during MP testing at this time. It is planned in the future.
[19:24] <fginther> dobey, by the way, the rtm chroots are almost ready
[19:24] <fginther> dobey, should have the branch added soon
[19:24] <dobey> fginther: ok, thanks
[20:01] <ToyKeeper> popey: Sorry, was in a meeting...  I just installed it via the citrain device-upgrade command.