[02:04] <imgbot> [03:39] <imgbot> [03:39] <imgbot> [03:59] <Mirv> 1morning
[04:00] <Mirv> so it should be #199 that will show better results, hopefully
[04:02] <sergiusens> good 19th
[04:03] <Mirv> hopefully soon ending good 18th to you
[04:03] <Mirv> "the sooner you assign to me that silo, the better", I guess
[04:04] <sergiusens> Mirv: it's the 19th here now too :-P
[04:04] <sergiusens> Mirv: if you assign it soon; I'll get through it soon :-)
[04:04] <Mirv> yeah :) already did, landing-008
[04:09] <sergiusens> ty
[04:28] <Mirv> rsalveti: the branches would need to be approved https://code.launchpad.net/~rsalveti/ubuntu-touch-session/update_touch_pa_add_voicecall_volume/+merge/231289 + https://code.launchpad.net/~rsalveti/telepathy-ofono/set_default_voicecall_volume/+merge/231290
[04:29] <Mirv> although you usually land your own stuff anyway, but just noticed from the queuebot
[04:30] <rsalveti> Mirv: yup, just got the silo before asking people to review/test
[04:54] <Mirv> rsalveti: right, there's just "Testing pass" preselected, that's why I checked
[04:55] <Mirv> thanks :)
[04:55] <rsalveti> Mirv: oh, my mistake
[04:55] <rsalveti> thanks
[05:39] <rsalveti> Mirv: something is busted with this silo, I pushed a new rev to my telepathy-ofono MR, tried a rebuild and it didn't get the new rev
[05:39] <rsalveti> tried a force rebuild and still nothing
[05:40] <rsalveti> it still tried to upload the src package with the same version as the one it is already available (from a previous build)
[05:40] <Mirv> rsalveti: it does say it took rev 99 at https://ci-train.ubuntu.com/job/ubuntu-landing-002-1-build/8/console
[05:41] <rsalveti>   Uploading telepathy-ofono_0.2+14.10.20140819-0ubuntu1_source.changes: done.
[05:42] <rsalveti> Mirv: ^ still the same version id as the older one already available in the ppa
[05:42] <rsalveti> for some reason it didn't add the .1
[05:42] <Mirv> oh, it's not increasing it and so the upload (silently) fails
[05:42] <rsalveti> yeah
[05:43] <Mirv> rsalveti: robru has fixed some versioning things 5h ago :)
[05:43] <rsalveti> hm
[05:43] <robru> Mirv, rsalveti nope nope nope nope
[05:43] <robru> nothing is fixed
[05:43] <robru> it's all broken
[05:43] <robru> broke broke broke
[05:43] <rsalveti> lol
[05:43] <Mirv> hehe
[05:44] <robru> Just got back from dinner, still looking into this
[05:44] <robru> initial experiments failed
[05:44] <Mirv> ok then
[05:45] <robru> something in the RTM changes broke the bit of code that knows to add .1 on rebuilds
[05:45] <Mirv> rsalveti: if you need it quickly, I can fix it for you by getting the branch, manually fixing the changelog from the PPA, and doing it as a direct upload (plus manual merge afterwards)
[05:45] <robru> fixing it to not add '+rtm+rtm+rtm' is pretty trivial but then you get identical version numbers that fail uploads, still figuring why .1 is missing
[05:45] <robru> Mirv, rsalveti: wait what are you seeing? I thought only rtm was affected by this.
[05:46] <Mirv> robru: so, https://ci-train.ubuntu.com/job/ubuntu-landing-002-1-build/8/console tried to upload with the same version number that is already in the PPA
[05:46] <rsalveti> robru: no, this is for ubuntu
[05:46] <rsalveti> Mirv: but wonder if that will cause even more issues :-)
[05:46] <Mirv> telepathy-ofono 0.2+14.10.20140819-0ubuntu1
[05:46] <robru> and you were expecting 19.1?
[05:46] <rsalveti> yup
[05:47] <Mirv> robru: yes, since 19 is already there, so in practice the upload failed
[05:47] <robru> ok, that's the same as I saw in rtm.
[05:47] <robru> will dig
[05:48] <Mirv> rsalveti: there's no problem as long as I don't get swamped with such requests. it's just manually doing what CI train does.
[05:48] <Mirv> but we can also just wait
[05:49] <rsalveti> Mirv: mind doing that upload then (at least for now), want to get tiago to test/review this silo tomorrow morning
[05:50] <rsalveti> there's a really annoying issue that is happening quite frequently with the latest images that makes me unable to launch apps
[05:50] <rsalveti> even with latest
[05:55] <Mirv> (not really, will relaunch watch only build after the manual upload is published there properly)
[05:56] <Mirv> and with this, we can even switch back to the normal MP method and see if .2 appears after CI Train is fixed
[06:07] <robru> Mirv, rsalveti ok the version stuff should be fixed, can you please try an upload?
[06:15] <robru> Mirv, rsalveti if you do run a build job, please check the DEBUG flag, I added a bunch of debugging messages to help figure out what's going on with the versioning.
[06:20] <Mirv> robru: ok, I'll reconfigure it back to using MP and try another rebuild
[06:23] <robru> Mirv, paste me the build log when it starts please ;-)
[06:25] <Mirv> robru: building https://ci-train.ubuntu.com/job/ubuntu-landing-002-1-build/11/console
[06:25] <Mirv> looks correct, .2 now there!
[06:33] <robru> Mirv, sweet, thanks, debug output looks sane too
[06:36] <Mirv> yes, it's building all good https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-002/+packages
[06:36] <Mirv> thanks!
[06:40] <robru> Mirv, you're welcome
[07:03] <jibel> what is the bug # for the 'app fails to launch' issue? I reproduced it with the reverted version of u-a-l 0.4+14.10.20140808.2.is.0.4+14.10.20140808.2-0ubuntu1
[07:22] <Mirv_> omg, network outage
[07:24] <sil2100> jibel: LP: #gookistan 1357252
[07:24] <sil2100> I mean
[07:24] <jibel> sil2100, :) found it thanks
[07:25] <sil2100> Ugh, why 'gookistan' o_O ?!
[07:25]  * sil2100 doesn't understand his pastebin
[07:29] <tsdgeos> Saviq: ah, the workaround doesn't seem to have worked :/ (or is a different crash)
[07:31] <tvoss> jibel, hah
[07:34] <sil2100> CRAP!
[07:34] <sil2100> tvoss, jibel: I think the revert was wrong
[07:34] <sil2100> tvoss, jibel: I think it didn't really revert ANYTHING
[07:34] <sil2100> F**K
[07:35] <sil2100> I screwed it
[07:35] <sil2100> ARGH
[07:35] <brendand> sil2100, the u-a-l revert?
[07:35] <sil2100> Yes
[07:35] <tvoss> sil2100, ?
[07:35] <brendand> sil2100, you didn't revert it at all, or made it worse ?
[07:35] <Mirv> indeed, https://launchpadlibrarian.net/182632645/ubuntu-app-launch_0.4%2B14.10.20140808.2-0ubuntu1_0.4%2B14.10.20140808.2.is.0.4%2B14.10.20140808.2-0ubuntu1.diff.gz
[07:35] <sil2100> Didn't revert it at all
[07:35] <Mirv> brendand: just no revert, a no-change rebuild
[07:36] <brendand> sil2100, ok don't panic
[07:37] <sil2100> I'm not panicing, I'm just really really pissed at myself
[07:38] <sil2100> This reveerter script doesn't really work as it should
[07:38] <Mirv> we have plenty of other blockers, so time-wise it's not any problem
[07:42] <brendand> sil2100, how does reversion work? don't we just delete the newest version from the archive?
[07:42] <sil2100> brendand: no, you can't do that, we need to upload a new version that's just like the old one
[07:42] <brendand> sil2100, the results are not that bad today - 97.7%
[07:42] <sil2100> But now I bloated it with a useless version
[07:45] <brendand> sil2100, good news - camera-app is better now :)
[07:52] <Mirv> brendand: and messaging/dialer!
[07:55] <sil2100> ogra_: will have to ask you for a re-upload of ubuntu-app-launch :<
[07:56] <sil2100> ogra_: http://people.canonical.com/~lzemczak/packaging/ :<
[07:57] <sil2100> ogra_: pretty please with cherries on top
[07:57] <ogra_> hmm, did we do anything specifically for dialer and messaging ?
[07:57] <ogra_> they got massively better
[07:58] <Mirv> ogra_: I believe it's the telephony-service
[07:58] <sil2100> ogra_: 199 had a ofono landing that might have helped
[07:58] <ogra_> k
[07:58] <sil2100> I mean, telephony-service
[07:59] <Mirv> :)
[07:59] <Mirv> it's starting to look bearable again
[07:59] <ogra_> sil2100, i get a 403 for .dsc, .diff.gz and .changes
[07:59] <ogra_> (fix the permissions please)
[08:00] <sil2100> uh, wth
[08:02] <sil2100> ogra_: should be ok now I guess?
[08:07] <ogra_> sil2100, uploaded
[08:07] <ogra_> (if you didnt get mail yet)
[08:09] <ogra_> sil2100, so tvoss just asked me for the recent trust store crashes ...
[08:09] <ogra_> sil2100, there are none !!!
[08:09] <ogra_> 199 seems to be crash free wrt trust store ...
[08:09] <sil2100> ogra_: thank you, and sorry for the wrong packageyesterday ;/
[08:09] <sil2100> OH!
[08:09] <sil2100> \o/
[08:09] <ogra_> np
[08:10] <tvoss> ogra_, sil2100 I still would like to retrace the previous crash file
[08:11] <ogra_> tvoss, default, camera ... webbrowser ... pick one of them and scroll down http://ci.ubuntu.com/smokeng/utopic/touch/mako/197:20140818:20140811.1/9753/
[09:17] <davmor2> sil2100: looking at the bug it looks like Saviq is looking at the clock out of sync
[09:17] <davmor2> Saviq: when you look at that wifi is out of sync too, I told me I was connected to my home network 12 miles away last night,  now I know my router has a good reach but that would be stretching it a bit
[09:23] <sil2100> davmor2: but that's just the unity8 bits probably, right?
[09:23] <dbarth> good morning
[09:23] <sil2100> davmor2: the indicator most probably also needs its own fix
[09:24] <dbarth> our infamous silo 13 is blocked in -proposed because of an ap test issue
[09:24] <dbarth> what's best to unblock that: rebuild silo13 and repush?
[09:24] <davmor2> sil2100: Saviq is awesome make him fix it all, it'll work then honest :)
[09:25] <sil2100> I guess we have limited Saviq resources :<
[09:25] <Saviq> davmor2, sil2100, sounds like the same issue
[09:25] <Saviq> dednick is looking into it
[09:26] <sil2100> dbarth: because of an ap issue?
[09:27] <dbarth> sil2100: ap test failing
[09:28] <sil2100> dbarth: which silo is it? And what packages? Since I don't see anything migrating in CI Train right now
[09:29] <dbarth> sil2100: it was silo 13, now gone
[09:29] <dbarth> sil2100: package is: ubuntu-system-settings-online-accounts
[09:30]  * sil2100 checks
[09:30] <dbarth> it had to be manually acked because of arch-dependent things
[09:30] <dbarth> i guess if we silo the fix real quick it can trigger a new upload request to unblock the previous one
[09:30] <dbarth> i just wanted to verify to avoid accumulating errors which would be harder to fix later on
[09:31] <sil2100> dbarth: but I see it in utopic already, it doesn't look stuck in -proposed
[09:31] <dbarth> pitti pinged me this moning about it
[09:31] <sil2100> Or is it causing some other package to get stuck?
[09:31] <dbarth> ah maybe
[09:31] <dbarth> well, you know what, i'll just silo the fix
[09:31] <dbarth> and that should work
[09:32] <sil2100> Yeah ;)
[09:32] <sil2100> I think it's the simplest and best way
[09:35] <dbarth> ok
[09:58] <jibel> jodh, I added some info to https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/comments/17 with cgmanager in debug mode if it helps
[09:59] <jodh> jibel: yes, thanks. saw that.
[10:12] <cjwatson> OK, back from holiday, trawling through mail.  How are we looking for the RTM branch refresh?
[10:15] <brendand> cjwatson, no promoted image still
[10:16] <sil2100> cjwatson: so, no promoted image sadly... but the infrastructure seems ok (besides the +rtm bug that's a bit annoying still, but it's just a bug with rebuilds and will be fixed)
[10:16] <cjwatson> Whoa, we haven't had a promoted image since I left?  Wow.
[10:16] <sil2100> cjwatson: we have 3 blockers left basically
[10:16] <sil2100> cjwatson: yeah ;/
[10:16] <sil2100> cjwatson: I'll be switching TRAINCON-0 in a moment, as we anyway slowed down landings already
[10:17] <cjwatson> Well, I wasn't going to be able to refresh the branch until we get a Launchpad deployment, so that I can avoid spamming uploaders with copy notices; but that sounds like I may not be able to do it today
[10:18] <cjwatson> Guess I'll check with managers when possible
[11:00]  * sil2100 out for lunch o/
[11:11] <jgdx> cihelp: s-jenkins down?
[11:11] <psivaa> jgdx: i just accessed it
[11:12] <ev> jgdx: yeah, working here. What are you seeing?
[11:12] <jgdx> psivaa, ev, webpage not available
[11:13] <jgdx> which I think means I am on the network
[11:13] <ev> jgdx: for a specific job or for the root URL?
[11:13] <jgdx> ev, http://s-jenkins.ubuntu-ci:8080/job/ubuntu-system-settings-ci/1243/
[11:13] <jgdx> oh and the root url
[11:13] <ev> yeah, it's there
[11:13] <ev> you're presumably not on the VPN
[11:15] <jgdx> ev, right, rebooting
[11:18] <jgdx> ev, reboot fixed it.
[12:01] <bzoltan1> psivaa:  I wonder if it would be possible to do more than a single build in the UITK autolanding http://10.98.3.13:8080/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-autolanding/
[12:02] <psivaa> bzoltan1: more than a single build?
[12:03] <bzoltan1> psivaa:  we have 41 active branches, half of them could build in few ten minutes and we could land a good bunch of fixes and improvement. Now it looks, that even after the applauncher is back in business it literally takes days to get the MRs landed on the staging.
[12:04] <bzoltan1> psivaa: I mean Mirv has triggered about 5-7 MRs build, but I see only one. Are the others queuing?
[12:04] <psivaa> bzoltan1: ohh, understand.
[12:04] <bzoltan1> psivaa:  :) I am not sure if I understand how this works :) maybe I am asking silly questions... would not be the first time
[12:07] <psivaa> bzoltan1: i dont see any of the -autolanding jobs in the queue.. only see a couple of -ci 's in the building state.
[12:09] <psivaa> bzoltan1: as per whether we can have multiple -autolanding jobs in parellel, i think fginther` would be able to give you a better answer
[12:10] <psivaa> my feeling is that it might cause some conflicts
[12:12] <bzoltan1> psivaa: Theoretically  it could, but if they would conflict then the conflict would be there in sequential landing order too... a conflict is conflict regardless of parallel or sequential landing order
[12:19] <greyback_> trainguards: could I get a silo for spreadsheet line 13 please?
[12:20] <psivaa> bzoltan1: yea, agree, but I wasn't only talking about text conflicts.. not entirely sure how MP's are proposed for UITK to decide if it'd cause any other issues :). so leaving it to fginther` :)
[12:23] <t1mp> psivaa: the code base is getting quite large and we are only 3 people and we know who is working on what, so while conflicts are not impossible, they are not common
[12:30] <psivaa> t1mp: ack, will raise it in the meeting today
[12:34] <Mirv> greyback_: done
[12:59] <ogra_> sil2100, what happened to that image you wanted to build ?
[13:10] <silDroid> Hi guys!
[13:10] <silDroid> sil2100 here, due to some car problems Im stuck in the city for some time
[13:11] <silDroid> With only my phone handy
[13:11] <ogra_> silDroid, tsk, use ubuntu !
[13:11] <silDroid> Just so you know that it might take a while since Im back at my PC again :/
[13:12] <ogra_> silDroid, i just pinged your other account, what happened to the image you wanted to build
[13:12] <silDroid> Hey, on ubuntu I wouldnt able to give you guys a sign!
[13:12] <ogra_> why ? just use the kiwi IRC client ;)
[13:12] <ogra_> wroks fine as long as you dont put it in the background for to long
[13:13] <silDroid> So, Ive been waiting for some input from the unity8 guys on the locker merge
[13:13] <silDroid> Yeah, but I would have to install it first!
[13:13] <silDroid> I have limited data here, eating up my payphone money
[13:14]  * ogra_ adds it to the seed ... with a note that silDroid will write a test suite for it 
[13:14] <silDroid> Not sure what happened with that merge, but I guess its best to just kick a new image
[13:14] <ogra_> *g*
[13:14] <silDroid> Hah!
[13:14] <silDroid> ogra_: cpuld you kick a new image now maybe? As its getting latish anyway
[13:14] <ogra_> yeah
[13:14] <ogra_> doing
[13:15] <silDroid> Ok, I go back to changing my tire, see you soon
[13:15] <silDroid> o/
[13:23] <greyback_> Mirv: I need advice. Job failed with https://ci-train.ubuntu.com/job/ubuntu-landing-016-1-build/5/console - is it because I made a debian/changelog entry specifying the utopic series?
[13:23] <greyback_> https://code.launchpad.net/~gerboland/unity-api/surfaceSizerCallback/+merge/230270 is the MR in question
[13:24] <imgbot> [13:25] <greyback_> 200 *\o/*
[13:25] <ogra_> )
[13:25] <ogra_> :)
[13:26] <ogra_> 200 images and not a single green one this release cycle ...
[13:26] <ogra_> thats a record ... (not a good one sadly)
[13:27] <davmor2> sil2100: is this the image with the revert and additional fixes in place?
[13:28] <ogra_> davmor2, only the revert i fear
[13:28] <davmor2> sil2100: and is this the image you would like om26er to start dogfooding?
[13:28] <ogra_> and some "normal" distro landings (udisks, apport)
[13:28] <davmor2> ogra_: meh that's not so good :(
[13:28] <Mirv> greyback_: yes, should be s/utopic/UNRELEASED/
[13:29] <ogra_> davmor2, i think we are still waiting for a unity8 fix or so
[13:29] <ogra_> davmor2, see backlog, sil2100 is busy changing a tire
[13:29] <davmor2> oh yeah]
[13:32] <greyback_> Mirv: figured, thanks
[13:39] <fginther`> psivaa, bzoltan1, -autolanding jobs are executed in serial to prevent logical conflicts. MPs A and B can pass independently and both merge cleanly, but the combination of A+B may cause tests or builds to fail.
[14:14] <davmor2> bfiller: you around?
[14:15] <bfiller> davmor2: yes, on call
[14:20] <bzoltan1> fginther`: psivaa: in that case we need to make the builds faster. This build http://10.98.3.13:8080/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-autolanding/367/ is running for 4 hours already. With 10-12 MRs in  queue that means 2-3 days before I can start landing on Utopic
[14:20] <bzoltan1> fginther`: psivaa: and that is horror.
[14:23] <cjwatson> bzoltan1: do you do any internal parallelisation in the test suite?
[14:24] <Mirv> jdstrand: if you're around, can you explicitly say "approve" to https://code.launchpad.net/~jpakkane/mediascanner2/apparmorfix/+merge/230977 ?
[14:27] <bzoltan1> cjwatson: no, we do not
[14:27] <jdstrand> Mirv: it looks like it is all done?
[14:27] <jdstrand> Status: Approved
[14:27] <Mirv> jdstrand: yes, but not by a core-dev (like you), and it's a packaging change :) so say "ack"
[14:27] <fginther`> bzoltan1, the biggest issue appears to be the mako testing, when it gets backed up, bad things happen all around, especially for uitk
[14:27] <jdstrand> Mirv: done
[14:28] <Mirv> jdstrand: thanks
[14:28] <fginther`> bzoltan1, I'm assuming removing this test would not be a good solution?
[14:31] <Mirv> sil2100: I released a couple of isolated, small and good sounding fixes to mediascanner2 (remove one apparmor restriction), webbrowser (bug fix, and webbrowser fixes have had a very good track record), and notify-osd autopkgtest change
[14:32] <Mirv> sil2100: I also finished the patched qtdeclarative testing and all AP:s + manual testing, but I'll leave it to you/robru to decide if you can have it before traincon-0 or not
[14:50] <greyback_> trainguard: can I get a reconfigure of silo16, needed to add qtmir/gles twin
[14:53] <sil2100> greyback_: hi! Sure
[14:53] <brendand> sil2100, did we have any major regressions in 199 worth mentioning?
[14:53] <greyback_> sil2100: thanks :)
[14:56] <sil2100> greyback_: hah, had problems finding your silo-line, someone sabotaged your line on the spreadsheet ;)
[14:56] <greyback_> the cheek!
[14:56] <sil2100> Mirv: thanks!
[15:01] <sil2100> brendand: not really, nothing visible at least...
[15:02] <sil2100> davmor2: so, #200 would be a dogfooding candidate I would say, yes
[15:03] <davmor2> sil2100: yeah it will be me hitting it with hammers, om26er|away had to disappear but will be back latter and take over.  so as soon as it lands I'll kill it with fire........erm I meant test it honest
[15:15] <dbarth> sil2100: i messed up my silo 6, can you help me clean it?
[15:15] <dbarth> sil2100: i would just like to keep the webapp-override branch, but the ppa contains something else which i can't seem to get rid of
[15:15] <sil2100> dbarth: hey! What's up?
[15:16] <dbarth> hi
[15:16] <sil2100> Oh
[15:16] <sil2100> Looking
[15:16] <dbarth> just asking you because you were last to talk on the chan
[15:16] <dbarth> sorry ;)
[15:18] <sil2100> uh, right, interesting
[15:18] <sil2100> Even though the build happened, I don't see your upload in the PPA
[15:19] <dbarth> sil2100: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-006/+packages
[15:19] <dbarth> has an old version + oSoMoN has a silo with same component, slated for landing right now
[15:20] <ogra_> sil2100, argh. looks like #200 failed to build
[15:20] <dbarth> so mine is next in line but may be caught in a crossfire
[15:20] <sil2100> dbarth: exactly, that's the old version, the new one did not appear in the PPA
[15:20] <dbarth> sil2100: right, it got kicked out
[15:20] <sil2100> ogra_: wait, what? How?
[15:20] <dbarth> https://ci-train.ubuntu.com/job/ubuntu-landing-006-1-build/4/console
[15:21] <sil2100> dbarth: let me delete and re-try
[15:21] <ogra_> cjwatson, hmm, are there issues with debootstrap atm ?
[15:21] <oSoMoN> sil2100, dbarth: there’s no need to rebuild in silo 6 until silo 10 has fully landed
[15:22] <sil2100> oSoMoN: so we're still waiting for silo 10, yes?
[15:22] <sil2100> Ah, right, it's not m&c'd
[15:22] <oSoMoN> sil2100, yes, and then we will rebuild silo 6 and attempt to land it
[15:23] <pete-woods> sorry my silo request is nagging. it seems someone deleted the description, so I just pasted it back
[15:23] <sil2100> dbarth, oSoMoN: ok, then let's wait with the test rebuild when silo 10 lands - if it will still cause trouble then I'll revisit
[15:23] <ogra_> http://paste.ubuntu.com/8089733/
[15:24] <dbarth> sil2100: ok
[15:25] <ogra_> oh, thats the same error cjwatson pointed out before in another channel
[15:25] <sil2100> pete-woods: the RTM-sync landing?
[15:25] <ogra_> "possibly the package package is at fault"
[15:25] <sil2100> pete-woods: but it's for utopic, right?
[15:25] <sil2100> ogra_: package package?
[15:25] <ogra_> yeah
[15:25] <ogra_> :)
[15:25] <pete-woods> sil2100: yes
[15:26] <pete-woods> sil2100: I misunderstood the process and landed something straight to RTM yesterday. so today I have to sync it to utopic
[15:26] <sil2100> pete-woods: ah ;) Ok, right, 2 things regarding that:
[15:27] <sil2100> pete-woods: 1) yes, as you know the normal way is first utopic, then backport to rtm
[15:27] <sil2100> pete-woods: 2) no worries! The RTM packages will be now cleared and it will start off clean
[15:27] <pete-woods> :D
[15:27] <sil2100> pete-woods: so most probably you'll have to re-land that for RTM anyway ;p
[15:27] <pete-woods> cool
[15:27] <cjwatson> ogra_: yeah, I just punted to slangasek
[15:27] <ogra_> cjwatson, any idea what that is ?
[15:27] <sil2100> oSoMoN: ^
[15:28] <sil2100> pete-woods: anyway, assigning a silo for you in a moment
[15:28] <ogra_> (just out of curiosity)
[15:28] <cjwatson> ogra_: something to do with the latest util-linux merge I think, but the reason I punted is that I don't understand insserv well enough to have an exact diagnosis myself :)
[15:28] <pete-woods> sil2100: thanks!
[15:28] <ogra_> ah, great, thanks
[15:28] <cjwatson> pete-woods: how did the RTM process work out for you otherwise?
[15:28] <oSoMoN> sil2100, excellent, I’ll M&C now
[15:29] <pete-woods> cjwatson: all good other than the add-apt tool
[15:29] <cjwatson> pete-woods: right, we have asana tasks for that ... had forgotten it would bite the citrain tool which I guess is where you ran into it
[15:29] <cjwatson> ogra_: re ubuntu-phone, did I miscommunicate something somewhere that implied we would be doing ongoing auto-syncs?
[15:29] <pete-woods> cjwatson: yep. but other than that it all went smoothly :)
[15:29] <cjwatson> pete-woods: excellent, thanks
[15:30] <cjwatson> ogra_: (BTW I committed a fix for debootstrap's unhelpful message upstream)
[15:30] <ogra_> cjwatson, well, no, i assumed rtm would behave towards ubuntu like ubuntu behaves towards debian ... (and we sould use something like an SRU process for syncing bits in)
[15:30] <ogra_> s/sould/would/
[15:31] <cjwatson> ogra_: I guess that's sort of true if you consider Debian import freeze to be this week :)
[15:31] <ogra_> right, my assumption was you always push to ubuntu and then sync into rtm
[15:31] <ogra_> but seems i got that the wrong way round :)
[15:32] <cjwatson> no, that's the right way round
[15:32] <cjwatson> but we will generally be relanding via citrain rather than syncing as such
[15:32] <sil2100> ogra_: first ubuntu, then rtm ;)
[15:32] <ogra_> ah
[15:32] <ogra_> there was my knowledge gap :)
[15:32] <cjwatson> maybe for non-citrain uploads it may work out easier to sync with binaries, in some limited circumstances
[15:33] <cjwatson> we do have proposed-migration, so it's possible, but we would have to work out how to QA things
[15:33] <cjwatson> I guess we could assign a silo, copy-with-binaries into it, then land
[15:34] <ogra_> i would also have expected the "traditional" touch arches to just stay with ubuntu
[15:34] <ogra_> though i understand we need a reference for the new arches
[15:34] <cjwatson> how do you mean by traditional arches?
[15:34] <ogra_> with the same codebase
[15:34] <ogra_> nexus line
[15:34] <ogra_> vs the upcoming arches
[15:35] <cjwatson> well, we'll still be building mako etc. from devel
[15:35] <cjwatson> I don't care what people use there, but we need to fork all the same code so it makes no difference to me :)
[15:35] <ogra_> right, but we likely wont really look at it much
[15:37] <ogra_> heh, looks like the first kdubs fallout ... https://plus.google.com/+JonathanCorbet/posts/Q4HvGmPGjPs
[15:37] <ogra_> *kdbus
[15:37] <sil2100> charles: hey!
[15:37] <sil2100> charles: so, just so I get things clear - the two blockers regarding time being out of sync and similar are not indicator-datetime issues?
[15:38] <sil2100> charles: since I see a merge from dednick there, but just wanted to make sure it fixes all the issues for both the indicator and the welcome screen
[15:38] <sil2100> dednick: ^ ?
[15:38] <cjwatson> ogra_: which is fine ... but I expect it'll be useful for QA all the same, since not everyone has the new platforms
[15:39] <ogra_> right, thats what i meant with "i understand we need a reference"
[15:39] <dednick> sil2100: yes. but still working on it
[15:58] <pete-woods> four whole free silos? nudge, wink, etc :)
[16:00] <dbarth> sil2100: oSoMoN confirms that his silo landed, so can i haz a silo 6 clean up please?
[16:01] <dbarth> or Ursinha maybe? ^^ see just above
[16:04] <Ursinha> dbarth: I think that would be a trainguards job
[16:04] <dbarth> ok nw
[16:04] <dbarth> any trainguards around who can hlp me?
[16:05] <robru> dbarth, one sec, we're all in a meeting
[16:07] <oSoMoN> dbarth, can’t you trigger a rebuild of silo 6? wouldn’t that work?
[16:13] <dbarth> oSoMoN: i tried already
[16:13] <dbarth> i think that's fixed now, i saw the dashboard moving
[16:14] <rsalveti> is 200 out already?
[16:15] <ogra_> rsalveti, you didnt listen in the standup :P
[16:15] <ogra_> rsalveti, builds are screwed
[16:15] <rsalveti> ogra_: nops, sorry
[16:15] <rsalveti> ogra_: oh, great
[16:15] <ogra_> 200 failed
[16:15] <ogra_> we're waiting for a fixed util-linux and will have to try again then
[16:15] <rsalveti> oh =\
[16:15] <ogra_> yeah
[16:16] <ogra_> smells like traincon might happen before 200 actually
[16:16] <rsalveti> that was another huge sync
[16:16] <rsalveti> yay, perfect time for lunch I guess then
[16:16] <rsalveti> :-)
[16:16] <ogra_> for a week off i guess
[16:16] <ogra_> :)
[16:16] <rsalveti> that might also work
[16:16] <popey> pete-woods: can you take a look at https://bugs.launchpad.net/mediascanner2/+bug/1358275 please? bfiller ← is the bug you mentioned earlier.
[16:18] <pete-woods> popey: err. I'd have to forward you on to either jamesh or Satoris
[16:18] <popey> ok, will poke them.
[16:18] <pete-woods> :)
[16:21] <pete-woods> trainguards: sorry to nag again about my silo request (line 33), but I'd really like to get this landed soon (and there are free silos)
[16:32] <pete-woods> oh. I guess there's already a silo for scopes-shell :(
[16:33] <bfiller> popey: thanks
[16:34] <bfiller> popey: is this the bug blocking the content-hub landing?
[16:35] <popey> bfiller: i believe so, will chase up when the guys are online
[17:18] <bzoltan1> psivaa: fginther`: and this type of stuff does not help either http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-utopic-touch/3755/console
[17:22] <bzoltan1> psivaa: fginther`: guys we really need to do something. It is just not OK to waith 7 hours to see an internal error for a single MR to build...
[17:45] <greyback_> trainguards: can I get a reconfigure for silo16 plz? Want to add another qtmir change (adds lttng timing stats)
[17:46] <robru> greyback_, as long as you're not adding a new source package you can click 'Recon' yourself in the dashboard.
[17:47] <greyback_> robru: ah cool, thanks. I thought it was once per MR.
[17:49] <sil2100> robru: btw.! Could you add to your dashboard the Landing instructions/image status field? :)
[17:49] <sil2100> robru: currently it only seems visible in the spreadsheet, would be nice to have it in the Dashboard as well
[17:49] <sil2100> (maybe in the page title even?)
[17:50] <robru> sil2100, sure
[17:50] <sil2100> Thanks
[17:51] <robru> greyback_, you do need to reconfigure if you add a new MR, but you only need our help if you're adding a new source package.
[17:51] <greyback_> robru: ah I see. Thanks
[18:36] <ogra_> sil2100, util-linux migrated ... should we be brave and try a built ?
[18:36] <ogra_> *build
[18:39] <sil2100> Brave is our second name
[18:39] <sil2100> Let's do it!
[18:39] <ogra_> yeah !
[18:40] <ogra_> will you ? or should i ?
[18:40] <sil2100> Let me do the honors
[18:41] <ogra_> :)
[18:41] <ogra_> i'll then read the fail-log :)
[18:41] <sil2100> The dashboard says it's still rebuilding though ;)
[18:41] <ogra_> you need to select the right thing and stop that first
[18:41] <sil2100> I'll request a build anyway
[18:41] <sil2100> Oh, stop it first?
[18:42] <sil2100> Remove from the list or disable?
[18:42] <ogra_> let me do that ... one sec
[18:42] <sil2100> Oh, cancel
[18:42] <ogra_> yeah
[18:42] <sil2100> Will you do that or should I press the cancel button?
[18:43] <ogra_> i just tried to ... doesnt really show in the UI
[18:43] <ogra_> still says re-building
[18:43] <ogra_> no go :(
[18:43] <ogra_> and no stgraber :(
[18:44] <sil2100> ;/
[18:45] <charles> sil2100: pong
[18:45] <sil2100> charles: ping
[18:45] <ogra_> hmm, log out and log in didnt make it react any different
[18:45] <charles> sil2100: pong
[18:46]  * ogra_ starts a build directly on the machine then
[18:46] <sil2100> charles: pong? ;)
[18:47] <ogra_> sil2100, build started from cmdline ...
[18:47] <charles> sil2100, you pinged me a few hours back in-channel, what I can I do for you?
[18:47] <charles> sil2100, or, more tersely: "pong" :-)
[18:48] <sil2100> charles: indeed! But I asked a question afterwards, let me find the backlog - but anyway, I guess dednick more or less answered it already instead
[18:48] <sil2100> charles: so I guess the ping might be a bit invalidated ;p
[18:53] <robru> ok, take a peek at https://code.launchpad.net/~robru/cupstream2distro/simplify-argparse/+merge/231438 when you get a chance, I'll take lunch now
[18:53] <robru> it looks like it works in preprod, I can't imagine any way it can go wrong ;-)
[18:54]  * ogra_ wonders about the bot 
[18:54] <robru> sil2100, ^
[18:54] <ogra_> oh, it still waits for 200 to show up ... thats why it didnt announce the start
[18:54] <robru> oops, wrong window, thought I sent that direct to sil2100 ;-)
[18:54] <sil2100> robru: o/
[18:54] <robru> luckily not super private info ;-)
[18:55] <sil2100> OH NO EVERYONE WILL KNOW
[18:56] <robru> everyone will know I'm doing work! gasp!
[18:56]  * robru goes back to furiously twiddling his thumbs
[18:57] <davmor2> robru: no everyone will know you are talking about doing work but obviously not working because you are too busy talking about it ;)
[18:57] <robru> lol
[18:58] <ogra_> sil2100, looks pretty good ... FYI https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/utopic/ubuntu-touch/+build/4318
[19:11] <sil2100> ogra_: \o/
[19:41] <robru> ToyKeeper, you around for some QA signoff? silos 12 adn 15 need attention when you get a chance. thanks!
[19:53] <ToyKeeper> robru: D'oh, when I checked half an hour ago no silos were ready.  I'll get started on those; any preference which is first?
[19:54] <robru> ToyKeeper, maybe 15, I think that's a smaller fix for a recent landing
[20:04] <ToyKeeper> dbarth ... isn't around, d'oh.
[20:07] <ToyKeeper> robru: Any chance you know of any specific bug or testable behavior for silo 015?
[20:07] <robru> ToyKeeper, one of the branches is labelled 'fix AP tests', so definitely run those... let me see if I can find more for you
[20:08] <ToyKeeper> Usually we do a before/after test to make sure the thing which was supposed to change changed and nothing else broke...  but I don't see any info on what was wrong before.
[20:08] <ToyKeeper> Two of the branches are a new upstream version, and I'm guessing the details there aren't well-known so it's just a smoke test.
[20:09] <robru> ToyKeeper, sounds good to me. last I heard about this was that it was blocked in proposed due to failing autopkgtests, so if you know how to run those locally (eg, before I hit publish), that'd be super
[20:09] <ToyKeeper> autopkg tests, no...  but I can at least try the autopilot tests.
[20:09] <robru> ToyKeeper, generally i'd say 'try registering some online accounts or whatever' ;-)
[20:12] <ToyKeeper> This week some discussion has started on our constant failure to promote images without traincon 0 and the causes for that...  there may soon be a push to ensure every silo includes permanent changes to test plans or AP suites, since it seems like many don't.
[20:15] <tedg> robru, I'm landing the world! Oh, not really. But could I have silos for line 32 and 33 please? :-)
[20:17] <robru> tedg, you got 9 and 10... but I must warn you, with great silos comes great responsibility!
[20:17]  * tedg is sad he only has a small silo
[20:17] <tedg> robru, Thanks!
[20:19] <ToyKeeper> In any case, 015 in progress.  Could take a while though, since the current approach requires testing four times...  (before/after on two devices)
[20:24] <imgbot> [20:24] <imgbot> [20:24] <popey> woop
[20:25] <ToyKeeper> ... why did that take 7 hours to build?
[20:27] <rsalveti> ToyKeeper: archive was broken
[20:27] <rsalveti> previous build failed
[20:31] <tvoss> davmor2, around?
[20:32] <cjwatson> the archive wasn't broken, util-linux was broken :P
[21:20] <ToyKeeper> Anyone know if there's already a bug for the clock indicator never updating (at all)?
[21:21] <ToyKeeper> Hmm, maybe it's already covered by https://bugs.launchpad.net/bugs/1328646
[21:21] <ToyKeeper> (which seems to have recently expanded in scope)
[21:47] <ToyKeeper> Well, that's weird.  Why would silo 015 make some of the app icons disappear?
[22:42] <charles> could I get a QA signoff for silo 10?
[22:43] <charles> ToyKeeper, yep, I think https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1357311 is also related
[23:21] <veebers> trainguards: what's the best (quickest) way to get line 36 through? It's packaging changes made by pitti, so shouldn't need a full gatekeeper run for testing.
[23:31] <robru> veebers, looking
[23:32] <robru> veebers, yeah, "isolated fixes" don't require QA acking, also that diff looks trivial, also pitti is a core dev. I can just ram that through...
[23:32] <veebers> robru: awesome, thanks for that :-)
[23:32] <robru> veebers, you know, after you test it ;-)
[23:35] <veebers> robru: ack, I'll run the unity8 tests in the gatekeeper once I've built the packages
[23:35] <robru> veebers, ok, you're in silo 20
[23:35] <ToyKeeper> charles: After silos 015 and 012.
[23:35] <robru> veebers, you are the alpha and the omega
[23:36] <veebers> robru: hah, silo 1 && 20 nice. I should be able to 'testing ok' silo 1 today, assuming the test run didn't explode (again)
[23:36] <robru> veebers, yep, please be extra careful with an autopilot landing, that is one of the few things that has the potential to break *everything* ;-)
[23:37] <veebers> robru: ack, that's why we run it through the gate keeper a number of times to ensure. Unfortunately we had some good runs then the image results went bad :-\
[23:47] <robru> veebers, urk, merge conflict. can you fix it or should we wait for pitti?
[23:47] <robru> veebers, or do you want me to fix it? ;-)
[23:52] <veebers> robru: i'm just looking now (I re-proposed to get the diff updated: https://code.launchpad.net/~pitti/autopilot-qt/py3-deps/+merge/231477)
[23:53] <veebers> robru: I'm pretty sure that diff lines 24-33 should just stay as is, not sure what to do about the difference in lines 9 & 12 (i.e. the removal of '| python-autopilot (>= 1.4),'))
[23:54] <veebers> I suppose just remove line 12 and keep 9
[23:55] <robru> veebers, I'm thinking the other way arund... pitti's diff would result in keeping 12 and dropping 9.
[23:57] <veebers> robru: looking at the log, that was removed in distro and I synced that in trunk (revno: 84)
[23:57] <robru> veebers, alright then.