[00:06] <asac> kgunn: already asked for landing the pre-start thingy?
[07:08] <Mirv> hi. unfortunately powerpc among else is slowing down things. hopefully after qtdeclarative it'll become smoother, but I expect that a person in US timezone able to land the non-qt packages would be beneficial
[07:09] <Mirv> didrocks: ^ I already spend last evening occasionally pushing things further, but it would have helped also with Qt if someone during my night could have pushed the buttons
[07:09] <Mirv> also, it seems armhf builds in Debian are not all done, so I need to upload qttools ubuntu version for its symbols again, after qtdeclarative rebuild finishes
[07:10] <didrocks> Mirv: if you can add at your end of day some infos, I guess we can have someone doing that
[07:10] <Mirv> didrocks: yeah, will do
[07:10] <didrocks> Mirv: ack on qttools
[07:11] <Mirv> didrocks: in other news, http://pad.ubuntu.com/qt52-dependencies should be now ready - ie it includes (bolded) all the packages that need something else done than re-building trunk or current archive version
[07:11] <Mirv> I guess for non-CITrain packages a manual upload would be done, and for CI Train packages a merge request
[07:12] <didrocks> Mirv: can we have a trial without any rebuild on our packages, just the Qt part?
[07:13] <didrocks> Mirv: like, running all AP tests
[07:13] <didrocks> (do you think that will be ready soon?)
[07:13] <didrocks> (on armhf)
[07:13] <didrocks> I guess that will give some data on management who wants to do how Qt handled minor release, even with this ABI break
[07:14] <Mirv> didrocks: yes, the combination of the silo and the beta2 PPA should give something to test where the Qt of the silo is used instead. I think after qttools and qtmultimedia are ready quite many tests should use the newer builds
[07:14] <Mirv> qtwebkit won't be ready by my EOD, but hopefully I get far enough (qt3d, qtsensors, qtlocation) that I can push a build of it
[07:15] <didrocks> Mirv: ok, keep us posted :)
[07:16] <didrocks> (nice to have that bar on the pastebin)
[07:17] <Mirv> didrocks: do you by the way know any way to get the builder output all changed symbols, since it tends to stop after the first symbols file? that's why I've now the second rebuild of qtdeclarative for powerpc symbols
[07:17] <didrocks> Mirv: you can lower the warning so that it doesn't trigger any error
[07:17] <didrocks> but that's about it
[07:17] <Mirv> right
[07:17] <didrocks> (and it will then need another rebuild)
[07:42] <Mirv> qtdeclarative finished on powerpc \o/
[07:43] <Mirv> that's actually the first time ever, since V8 wasn't available for powerpc before 5.2
[07:44] <didrocks> yeah ;)
[08:14] <didrocks> sil2100: hey, how are you?
[08:22] <sil2100> didrocks: hey! Upgrading my system ;)
[08:22] <sil2100> How about you?
[08:23] <didrocks> sil2100: I'm good, thanks (even if it's rainy here)
[08:23] <didrocks> sil2100: can you prepare an order of safe landings for the meeting that you and Mirv will be able to proceed today? As you are going to test them as well, try maybe to match them in logical chunks?
[08:25] <sil2100> Ok, on it then
[08:27] <didrocks> thanks!
[08:55] <sil2100> Damn, my phone is acting strange
[09:20] <didrocks> \o/ look at line 23
[09:20] <sil2100> Wooooo
[09:20] <sil2100> Didn't know we had that feature!
[09:20] <didrocks> well, we didn't have it 5 minutes ago :p
[09:20] <didrocks> ok, let me get that triggered every 5 minutes
[09:21] <sil2100> You did-*rock* ;)
[09:21] <didrocks> heh ;)
[09:21] <didrocks> (there are a lot of checks to ensure we don't overwrite if a job is in progress or rollback or whatever)
[09:21] <didrocks> and it's checking every silos
[09:21] <sil2100> Let's just not trigger the spreadsheet breakage again!
[09:23] <didrocks> heh, I guess it won't make that many changes
[10:02] <didrocks> grrr, delivery of a 20 kgs pack between 8am and 7pm
[10:03] <didrocks> and of course, they choose the meeting time
[10:10] <ogra> [10:15] <sil2100> ;)
[10:30] <Mirv> I might be able to eat some very random "lunch" now while the phone is flashing
[10:36] <didrocks> ok, automated migration check done
[10:36] <didrocks> and deployed
[10:39] <davmor2> didrocks: okay so looking at 211 it is pretty much on par with 210, I'll carry on testing it but I've not had any crashes yet
[10:39] <didrocks> davmor2: great! keep us posted :)
[10:39] <sil2100> bzoltan1: hmm.. one of your merges doesn't seem to exist anymore
[10:39] <sil2100> bzoltan1: in the list of 13 landings
[10:40] <sil2100> bzoltan1: https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/tabbar-apfix-unit/+merge/208368 <- the branch is there but no merge request, can you clarify this?
[10:40] <davmor2> didrocks: well other than the camera app :)  which we know and blame rsalveti for whole heartedly right ;)
[10:40] <bzoltan1> sil2100: that must be renato's one
[10:40] <didrocks> davmor2: sure sure ;)
[10:40] <bzoltan1> sil2100:  ohh that one... sure, a sec
[10:41] <didrocks> sil2100: ah, ensure renato one (if still listed) is removed btw, it's already listed
[10:41] <didrocks> landed*
[10:41] <sil2100> bzoltan1: ah, ok ;)
[10:41] <sil2100> didrocks: I mean: ah, ok
[10:41] <didrocks> ;)
[10:41] <sil2100> bzoltan1: could you also check for renato one? ;)
[10:44] <didrocks> psivaa: ok, so gallery_app is the v8 crash
[10:44] <didrocks> psivaa: so, what I have done to quickly check
[10:45] <didrocks> wget <crashfile>
[10:45] <didrocks> apport-unpack <crashfile> foo
[10:45] <didrocks> gdb gallery-app foo/CoreDump
[10:46] <didrocks> then I'm seeing: #0  0x50b0d8f8 in ?? ()
[10:46] <didrocks> (on the phone of course)
[10:46] <psivaa> didrocks: ohh on the phone.
[10:46] <sil2100> phew
[10:46] <psivaa> didrocks: thanks for the steps.
[10:46] <didrocks> psivaa: yeah, I tried on the desktop, but symbols don't match
[10:46] <didrocks> yw! :)
[10:46] <didrocks> no need to install any dbgsym, nothing :p
[10:46] <bzoltan1> sil2100:  that MR was replaced by an other one
[10:46] <didrocks> just work on /tmp
[10:47] <bzoltan1> sil2100: renato's legendary MR has landed on the trunk already and so it is not in my MP
[10:48] <sil2100> bzoltan1: could you remove/replace what's needed in the list? I'll assign a silo then ;)
[10:50] <bzoltan1> sil2100:  done
[11:02] <Mirv> sil2100: err, unity-scope-scopes isn't installed by default on the image?
[11:02] <Mirv> so what exactly needs testing I'm wondering
[11:03] <didrocks> Mirv: if it's not installed (it's for the new scope API), just get it in
[11:03] <didrocks> Mirv: the real testing will come when we activate them
[11:06] <Mirv> thanks, just double checking because of the toll this context switch is having on my brain :)
[11:09] <didrocks> heh ;)
[11:09] <didrocks> I'm pretty sure it's not activated anyway
[11:09] <didrocks> (it's on the mwc image)
[11:10] <sil2100> I just love my ISP
[11:19] <Mirv> I kind of love my ISP but I'm currently pondering if I love it so much I'd get a two year fixed contract - the contract terms are usually so that even if in reality it would start to suck, there's no real chance to abort the contract
[11:19] <Mirv> I'd just get 100/10 instead of 24/10 and for slightly less price
[11:20] <Mirv> but I generally hate all "bind yourself to us for N years" deals
[11:30] <sil2100> Yeah, I'm also bound to a 2 year contract here
[11:41] <Mirv> sil2100: so based on your experience it'd be an valuable option to be able to switch :)
[11:49] <sil2100> didrocks: packaging ACK needed! Looks ok, although the description seems to be doubled ;/ python 2 and 3 ones have the same desc... not sure if we should block on that? http://162.213.34.102/job/landing-009-2-publish/lastSuccessfulBuild/artifact/packaging_changes_window-mocker_1.4+14.04.20140220.1-0ubuntu1.diff
[11:49] <ogra> [11:50] <ogra> (yay, and my desktop build notification tool works)
[11:50] <popey> didrocks: did you want me to dogfood 212?
[11:51] <didrocks> sil2100: +1, I think the package name helps knowing what it is
[11:52] <didrocks> popey: weather-app only + everything related to sound
[11:52] <didrocks> popey: if you can rerun the weather-app AP test btw, just in case :)
[11:52] <ogra> definitely dogfood it
[11:52] <ogra> make sure calls work again
[11:52] <popey> k
[11:52] <ogra> thats the importand change in this image
[11:52] <didrocks> so, after that one, only:
[11:52] <ogra> *important
[11:52] <didrocks> - the qt crash
[11:52] <didrocks> - camera app
[11:53] <didrocks> - clock apps
[11:53] <didrocks> should be the remaining issues
[11:57] <davmor2> popey: On the click updater I saw the new image for the calculator however once it had installed I still see the old one, also the calculator doesn't seem to open once updated even after a reboot so I'm wondering if something got broken there
[11:58] <davmor2> didrocks: ^ other than that issue and the camera app locking up all seems good here on mako :)
[11:58] <didrocks> davmor2: excellent, and so, no crash at all?
[11:58] <davmor2> didrocks: not so far
[11:58] <didrocks> great
[12:00] <davmor2> popey: the new weather opens fine I don't know if that was the fix for the qt5.2.1 issue we saw or what :)
[12:04] <sil2100> didrocks: packaging change! http://162.213.34.102/job/landing-014-2-publish/6/artifact/packaging_changes_unity-scope-click_0.1+14.04.20140226.1-0ubuntu1.diff <- added dependency, it's used so it should be ok
[12:04] <didrocks> sil2100: yeah, +1
[12:06] <Mirv> mh, that cordova thing is a bit hard, but I guess I can downgrade and see if it looks identical with that
[12:06] <Mirv> I've a "non-styled" app after instead of just running on device I installed it. plus the instructions on the google docs don't exactly match what I have in the SDK
[12:08] <Mirv> ah hmm, I guess I should use the SDK PPA even though archive version is only a week old
[12:08] <Mirv> maybe that helps with the desktop side of things and wrapping up what's going to get installed
[12:13] <didrocks> sil2100: seems ubuntu-ui-extras had a silo but nobody checked the lander for him
[12:13] <didrocks> so I assigned bill as he requests to flush trunk
[12:14] <sil2100> didrocks: indeed, right, thanks!
[12:14] <didrocks> yw
[12:19] <Mirv> eh, now the docs instructions for testing HTML5 apps are even more wrong
[12:20] <didrocks> hum, no dbarth
[12:20] <didrocks> Mirv: maybe just put a comment and move to the next one then?
[12:20] <didrocks> (put your comment on red background)
[12:20] <sil2100> ;/
[12:24] <Mirv> sil2100: can you check if l12 is proper now? I just added my stuff to the comments
[12:25] <Mirv> moving to unity-mir next
[12:25] <popey> didrocks: 212 seems okay for clock/camera/audio/dialer (not fully dogfooded)
[12:25] <didrocks> popey: great, tell us if you see any crash impacting you
[12:26] <didrocks> thanks :)
[12:26] <didrocks> so, maybe we'll be able to promote an image once the camera+clock fix are in
[12:26] <popey> didrocks: will do, i have a couple of meetings but will dogfood properly in a bit
[12:26] <popey> and will update the sheet and ping you when done
[12:26] <didrocks> popey: I count on your breakage expertise! :)
[12:26] <didrocks> (take care of the phone glass though, not that kind of breakage :p)
[12:27]  * didrocks runs
[12:29] <sil2100> ;)
[12:30] <didrocks> no answer on the troll, even not a disdain "ahahah", so disappointing!
[12:30] <Mirv> sil2100: more precisely, do I need to switch some testing "unsuccessful" switch or is comment enough?
[12:31] <popey> :þ
[12:33] <sil2100> Mirv: comment and you can even switch the Tested field to No if needed ;)
[12:34] <Mirv> that's what I was wondering about. yep, I'll switch it so it's more clear it's not been (successfully) tested (by us)
[12:35] <sil2100> AH HA
[12:35] <sil2100> Good one
[12:35] <sil2100> I'm testing now address-book-app and wanted to check the testing guidelines to see if I'm doing it right
[12:35] <sil2100> I click the links and HA! Empty!
[12:36]  * Mirv updated unity-mir and has a black screen after reboot. is this bad? :)
[12:36] <sil2100> NOTREGRESSION
[12:36] <sil2100> ;D
[12:36] <sil2100> Just kidding
[12:36] <sil2100> Really?
[12:37] <Mirv> yeah. unity8 and maliit-server crashed, apport running.
[12:37] <Mirv> I'll need to do some reiterations downgrade/upgrade I guess first
[12:37] <davmor2> Mirv: is it a fresh flash or just added the unity8 stuff?
[12:37] <Mirv> davmor2: fresh flash + landing-011 (unity-mir) (and well also html5 update)
[12:38] <Mirv> hmm, another reboot and no crash
[12:39] <Mirv> have we had random unity8 crashes lately on the images?
[12:39] <popey> didrocks: terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >'
[12:39] <Mirv> maybe I pretend what happened didn't really happen and run unity8 tests and do a couple more reboots after that
[12:39] <popey> expecting that?
[12:41] <didrocks> popey: not really
[12:41] <didrocks> you do have a crash file?
[12:41] <popey> not a recent one
[12:43] <popey> didrocks: getting a few crashes
[12:43] <popey> I'm being a bit brutal with it
[12:43] <didrocks> ok, can you try to clean /var/crash and retry?
[12:43] <didrocks> to see if it's reproducible
[12:43] <popey> ya
[12:44] <popey> had one unity crash and a bunch of app crashes / oddities
[12:47] <Mirv> popey: so you too got unity8 crash on stock image (or whatever you're testing?)
[12:47] <Mirv> I'm retracing one unity8 crash file now on desktop (if it works) while running unity8 tests
[12:48] <popey> Mirv: this is stock 212
[12:49] <Mirv> I'm using 211 - landing-011
[12:53] <popey> bah, can't reproduce it now
[12:53] <popey> did exactly the same thing
[12:56] <didrocks> Mirv: don't retrace, just try to look at the address first
[12:56] <didrocks> if it's d8f8
[12:58] <Mirv> didrocks: how to look at the address?
[12:59] <Mirv> -> hangout, but AP should be soon ready and I did manual testing too already. if AP ok I'll do a couple of reboots more, and it should be ~ready
[12:59] <didrocks> Mirv: excellent! so it's what I pasted for psivaa this morning
[12:59] <didrocks> one sec, looking
[13:00] <didrocks> didrocks | psivaa: ok, so gallery_app is the v8 crash
[13:00] <didrocks> didrocks | psivaa: so, what I have done to quickly check
[13:00] <didrocks> didrocks | wget <crashfile>
[13:00] <didrocks> didrocks | apport-unpack <crashfile> foo
[13:00] <didrocks> didrocks | gdb gallery-app foo/CoreDump
[13:00] <didrocks> didrocks | then I'm seeing: #0  0x50b0d8f8 in ?? ()
[13:00] <didrocks> didrocks | (on the phone of course)
[13:00] <didrocks> Mirv: ^
[13:00] <Mirv> retrace is ready, though, will look tha to
[13:05] <asac> Mirv: so can we for the sake of testing back out the binary packag rename until we are ready?
[13:05] <asac> makes no sense to shoot ourselves in the foot
[13:05] <asac> imo
[13:06] <asac> Mirv: its very very important that we can test stuff without the apps getting rebuild
[13:06] <asac> all the apps that have no private headers and dont use qreal
[13:07] <asac> in API
[13:07] <Mirv> asac: it'd restart the building once again, but I guess it could be doable. but not without approval from slangasek who in the first place asked Debian to do the rename and Debian accepted it to help us
[13:07] <asac> Mirv: you are the man who preps stuff in the ppa
[13:07] <asac> you dont need slangasek approval for our testing
[13:07] <asac> really
[13:07] <asac> thats crazy. b
[13:07] <asac> we are not saying that we wont do the package rename for the landing. just for testing etc.
[13:07] <Mirv> asac: well it seems going back and forth with different solutions
[13:08] <asac> its not going back and forth. its just operationally we cant rename it right now
[13:08] <Mirv> asac: then for landing it would be another 1-2 weeks of rebuilds, if now the rename would temporarily removed
[13:08] <asac> we can do the rename before we do the push to archive
[13:08] <asac> Mirv: ok, what you can do is include a compatibilty package for the testing
[13:08] <asac> so we just need to drop that
[13:08] <Mirv> so I think it needs discussion before I remove the PPA
[13:08] <asac> and no rebuild after
[13:09] <didrocks> can we screw apt?
[13:09] <didrocks> and tell to --force-depends
[13:09] <didrocks> or something like that
[13:09] <asac> we can just shiup empty package named like old and depend on the new package
[13:09] <Mirv> didrocks: I think for testing purposes that would be possible and a more sensible path
[13:09] <asac> while we test
[13:09] <asac> whatever
[13:09] <asac> find a solution
[13:09] <Mirv> some dummy libqt5core5 package could work too
[13:09] <asac> without infrsatructure work
[13:10] <didrocks> I would prefer the dummy libqt5core5 package approach
[13:10] <Mirv> but now back to -> hangout
[13:10] <asac> please do the dummy one for the ifnal testing
[13:10] <asac> thanks. please upload that asap so we can do the testing we need
[13:15] <Mirv> didrocks: http://pastebin.ubuntu.com/7010279/ ?
[13:16] <didrocks> Mirv: should be arch:all
[13:16] <didrocks> section oldlibs
[13:16] <didrocks> (if we want to keep it)
[13:16] <didrocks> otherwise +1
[13:17] <Mirv> yeah this multi-tasking is quite hard
[13:26] <sil2100> Time for some lunch
[13:40] <didrocks> popey: if I install manually a click package, it should appear in installed, right?
[13:40] <popey> i tend to....
[13:40] <popey> adb push foo.click /tmp
[13:40] <didrocks> yeah
[13:41] <didrocks> then pkcon install-local <click_package>?
[13:41] <popey> adb shell then sudo -u phablet -i, then pkcon install-local /tmp/foo.click
[13:41] <popey> then search for it
[13:41] <didrocks> ah
[13:41] <didrocks> I'm dumb
[13:41] <didrocks> I was root
[13:41] <popey> ya, everyone does that
[13:41] <didrocks> ahah :)
[13:41] <didrocks> hum
[13:42] <didrocks> ok, black scren
[13:42] <didrocks> screen
[13:42] <popey> which app?
[13:42] <didrocks> I think it's because I need some permissions or whatever :p
[13:42] <didrocks> popey: a dummy test app, just generated for default qtcreator
[13:42] <popey> ah
[13:42] <didrocks> (weird we don't ship the correct manifest)
[13:42] <popey> I'd look in /home/phablet/.cache/upstart
[13:43] <popey> or dmesg -T | grep DEN
[13:43] <didrocks> libust[7388/7392]: Error: Error opening shm /lttng-ust-wait-5-32011 (in get_wait_shm() at lttng-ust-comm.c:881)
[13:43] <didrocks> no other error
[13:46] <didrocks> ok, it works from qtcreator
[13:47] <didrocks> popey: do you still have a device with Qt 5.2?
[13:48] <popey> didrocks: no
[13:48] <didrocks> do you have the instructions somewhere so that I can upgrade?
[13:49] <popey> ya
[13:49] <popey> https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-beta2
[13:49] <popey> == Updating on device ==
[13:49] <popey> obviously make it rw and reboot first
[13:49] <didrocks> oh! :)
[13:51] <didrocks> popey: ok, I'm dist-upgrading, seems that's all needed then, thanks ;)
[13:57] <Mirv> asac: I did a test build locally and now before switching hangouts uploading to PPA
[13:57] <Mirv> mhr3: line 14 ready for clean and merge
[13:58] <Mirv> didrocks: the EOD status is actually fully documented at http://pad.ubuntu.com/qt52-dependencies in case it'd be wanted that we go forward with recompilations, which I guess we won't be doing. but just in case, that doc has all the information landing team should need with Qt 5.2
[13:58] <asac> Mirv: thanks! ... remember to drop the transitional package for the final upload i guess - unless we want to go through the motion of talking to steve again
[13:58] <didrocks> Mirv: thanks a lot :)
[13:59] <Mirv> sil2100: so unity-mir and the scopes published
[14:02] <rsalveti> morning
[14:03]  * rsalveti reading backlog
[14:04] <popey> didrocks: what controls rotation in apps? I mean, which system component says "ok, we're 90 degrees from normal now, rotate!" ?
[14:04] <didrocks> popey: I would say qtubuntu-sensors, but TBH, I'm not 100% sure
[14:05] <popey> looks plausible
[14:05] <tvoss_> popey, right now, it's qtubuntu-sensors
[14:05] <tvoss_> popey, but that's soemthing that will change over time
[14:06] <popey> ok, i need to file a bug for qt5.2
[14:06] <popey> oh, no I don't i mean for image 212
[14:06] <popey> i didnt say 5.2, ignore that
[14:06] <didrocks> you did say it
[14:06] <didrocks> I read it!
[14:06]  * popey edits the logs
[14:06] <didrocks> heh :)
[14:06] <didrocks> and my memory as well?
[14:07]  * ogra didnt see 5.2 anywhere 
[14:07] <ogra> :P
[14:07] <popey> *** Problem in qtubuntu-sensors
[14:07] <popey> This is not an official Ubuntu package. Please remove any third party package and try again.
[14:07] <popey> dammit
[14:07] <ogra> but why is popey working with qt212
[14:07] <popey> oh, i have way too many devices
[14:17] <popey> didrocks: bug 1286150
[14:17] <popey> just nudging or tapping the phone causes it to try to rotate
[14:18] <didrocks> popey: hum, I don't see anything in qtubuntu-sensors that could have caused it
[14:18] <popey> could be android/hybris?
[14:18] <didrocks> rsalveti: any idea? ^
[14:18] <popey> it could well have arrived earlier than 212
[14:19] <rsalveti> I can check
[14:19] <didrocks> popey: let me flag 202 just in case
[14:20] <didrocks> popey: can you try 206 meanwhile?
[14:20] <didrocks> just to know if it's pre/post-android 4.4
[14:20] <popey> didrocks: does that need a 4.4 downgrade?
[14:21] <didrocks> popey: not for 206
[14:21] <popey> ok
[14:27] <didrocks> ugly recovery logo on 202 :p
[14:33] <didrocks> popey: I don't see real difference between 202 and 212
[14:33] <didrocks> on the titling
[14:33] <popey> bang the side of the phone
[14:33] <ogra> it was always very sensitive for me
[14:33] <didrocks> it's as sensitive
[14:33] <didrocks> as it was
[14:33] <didrocks> to me
[14:33] <didrocks> I can try 209
[14:33] <didrocks> to compare
[14:34] <ogra> (also i dont bang my phone))
[14:34] <popey> to simulate
[14:34] <popey> i mean, i notice it flip when i put it down on the desk, even on an incline
[14:34] <rsalveti> yeah, they were also sensitive here as well
[14:34] <ogra> i had that since ages
[14:34] <popey> hmm
[14:34] <popey> okay
[14:34] <popey> ignore me :D
[14:35] <ogra> pretty annoying if you put it down while reading a text
[14:35] <ogra> just to have your hands free
[14:35] <popey> text
[14:35] <popey> right
[14:35] <popey> ☻
[14:35] <didrocks> ogra: I'm trying 196
[14:35] <didrocks> (and you delay my break! ;))
[14:35] <ogra> i didnt claim it was broken !
[14:35] <ogra> blame popey
[14:35] <didrocks> argh
[14:35] <didrocks> popey: ^
[14:36] <popey> http://blamepopey.com/
[14:36] <didrocks> sorry "all the same" :)
[14:36] <ogra> ++
[14:36] <didrocks> popey: you lack blinking tags :)
[14:36] <popey> I apologise most sincerely from the bottom of my heart. Can you ever forgive me?
[14:37] <didrocks> popey: thanks, I just wanted you to feel guilty :)
[14:37] <popey> good luck with that
[14:37] <didrocks> roh
[14:39] <Mirv> didrocks: so ubuntu2 of qtbase compiling in the PPA. transitional package to be dropped for final release, and at the moment (after the meeting discussions) it does not seem anyone is actually going to investigate mixing of packages / ABI breakage right now. but the transitional package is now there for time being. I can remove it with ubuntu3 upload on Monday or something.
[14:40] <didrocks> Mirv: ok, so let's see… keep it until next week, yeah :)
[14:40] <seb128> do you guys know when l10 is planned to land?
[14:40] <seb128> the fixes for the concurrent checks of upgrades
[14:40] <Mirv> didrocks: sil2100: secondly, it would be "go ahead" about continuing now as listed at http://pad.ubuntu.com/qt52-dependencies for example by starting by giving CI Train the multimedia-touch link, then dee-qt/libqtdbus* etc in order. it's up to the landing team I guess to organize whether I'll do it alone or not.
[14:40] <seb128> we start having a stack of ubuntu-system-settings changes in the queue, one blocking toolkit changes
[14:41] <Mirv> the qtwebkit finished building, Qt is essentially done now in landing-006
[14:41] <didrocks> seb128: do you know what is "We want manual testing first"
[14:41] <didrocks> about?
[14:41] <seb128> didrocks, no, I want to know if anyone is actively working on making that happen
[14:41] <didrocks> Mirv: we are tha landing team :)
[14:41] <seb128> e.g ralsina_
[14:41] <seb128> ;-)
[14:42] <Mirv> didrocks: yes, so up to us/you to decide eg. in the evening meeting :)
[14:42] <Mirv> I'm EOD now, but the plan should be ~clear
[14:42] <Mirv> in the pad
[14:42] <didrocks> Mirv: right, depends on how much we need to land for the rest, I guess, but yeah, it's clear ;)
[14:42] <Mirv> yep
[14:42] <didrocks> seb128: yeah, we need him I guess to know on that one
[14:42] <ralsina_> seb128: yes? (/me reads backlog)
[14:42] <seb128> ralsina_, hey
[14:43] <seb128> ralsina_, I'm wondering when the fixes for the concurrent upgrade checks is going to land (l10), we have a mp for settings there and it's blocking any other setting work to get a slot
[14:43] <ralsina_> I am not really the right person to land system settings, my team only did a plugin for it. The "we want manual testing" was laney
[14:43]  * sil2100 prepares for testing unity8
[14:44] <didrocks> Laney: ? ^
[14:44] <sil2100> The u-d-m and ubuntu-system-settings one is a bit fishey
[14:44] <seb128> ralsina_, u-s-s is only a small part of that landing ask
[14:44] <ralsina_> right
[14:44] <sil2100> So I wait with that one still
[14:44] <didrocks> sil2100: what is fishy?
[14:44] <ralsina_> both barry and mandel have tested the other parts a lot
[14:44] <seb128> ok
[14:44] <seb128> I'm going to test that ppa on my n4 which is on 209
[14:45] <seb128> let's see how that goes
[14:45] <didrocks> seb128: if you +1 on that one, I'm happy that you publish it
[14:45] <didrocks> (with your testing)
[14:45] <seb128> didrocks, thanks
[14:45] <didrocks> popey: ok, same sensitivity here
[14:45] <didrocks> with 198
[14:46] <didrocks> sil2100: going for a run, once unity8 is tested, can you get (if you have packaging changes) other core-devs +1?
[14:46] <bfiller> asac: line 26 on sheet are build only changes for qt5.2. no functionality added/changed
[14:46] <didrocks> sil2100: so that we can start another image soon
[14:47] <bfiller> didrocks: any chance we could get a silo for line 20 today?
[14:47] <didrocks> bfiller: sounds legit, assigning now
[14:48] <bfiller> didrocks: thanks
[14:48] <sil2100> didrocks: sure
[14:48] <sil2100> didrocks: the upgrade part was fishy, I was getting some strange error when wanting to upgrade my image
[14:48] <sil2100> Not sure if it's caused by these changes (since I just reverted), but I guess unity8 is more important
[14:48] <didrocks> seb128: FYI ^
[14:48] <didrocks> sil2100: yeah
[14:49] <didrocks> bfiller: done
[14:50] <boiko> didrocks: bfiller: thanks, I'll build that
[14:50] <bfiller> boiko: just did :)
[14:51] <boiko> bfiller: ah ok, thanks then
[14:51] <bfiller> didrocks: and line 26 should be harmless, just some includes added so the packages would be correclty on both qt5.0 and 5.2
[14:51] <bfiller> build correctly that is
[14:51] <didrocks> bfiller: check with asac first though, seeing his comment
[14:52] <asac> dont worry
[14:52] <bfiller> asac: any objections there?
[14:52] <asac> didrocks: so given we gave up on the idea to do empirical data gathering we can just land qt5.2 changes
[14:52] <didrocks> bfiller: and telephony-service is already in line 20
[14:52] <bfiller> didrocks: ah right, I should have added it there (:
[14:52] <asac> bfiller: whats the exact question? had a reconnect :)
[14:52] <bfiller> asac: your comment in line 26
[14:52] <asac> if its about qt5.2 changes, we tried to not land those so we could test our binary compatibilty story
[14:53] <didrocks> bfiller: so, separate them, maybe? if you want the other part to land?
[14:53] <asac> but seems the damage is already done, so we have to figure how to do that different
[14:53] <bfiller> asac: this is just a build fix so it will compile under both, no compatibility issue at all
[14:54] <asac> bfiller: right. however, build fixes might have implicit runtime behaviour changes as well... but anyway, we gave up on the idea that we can use the pretransition state to check the binary compatibility story
[14:54] <bfiller> asac: so it's ok then to land?
[14:54] <asac> yep. removed the comment
[14:54] <asac> thx
[14:54] <bfiller> cheers
[14:55] <didrocks> bfiller: so, you separate telepathy-service from it? so that we can land
[14:55] <bfiller> didrocks: sure, one sec
[14:55]  * didrocks is waiting on bfiller to take his first break 9h after he started his day
[14:55] <bfiller> lol
[14:55] <didrocks> blame popey from my previous failed attempt!
[14:57] <didrocks> bfiller: silo 002 for you
[14:58] <didrocks> bfiller: if you need anything sil2100 is around (but validating unity8 for now)
[14:58] <bfiller> didrocks: thanks, I moved the telephony-service to it's own line for after line 20 biulds
[14:58] <didrocks> bfiller: yeah, sounds good ;) thanks.
[14:58]  * didrocks goes really for a run now
[15:03] <rsalveti> kgunn: are you preparing mir 1.6?
[15:03] <kgunn> rsalveti: i am
[15:03] <kgunn> getting all the mp's sorted...
[15:03] <kgunn> filling out the spreadsheet in moments
[15:03] <kgunn> is it ok ?
[15:03] <rsalveti> kgunn: great
[15:04] <kgunn> rsalveti: i'll probably suck in a few u-s-c & u-m MP's with it
[15:04] <rsalveti> sure, just to know because I'll try the x86 emulator image with your latest stuff, and nested should be working now
[15:04] <rsalveti> if the issue with unity-mir conflicting symbols with mir is already fixed in there
[15:04] <rsalveti> yeah, that's fine
[15:04] <rsalveti> wonder if might have another silo blocking you
[15:05] <kgunn> rsalveti: yeah...i need to pull that in as well
[15:05] <kgunn> https://code.launchpad.net/~gerboland/unity-mir/namespace-to-prevent-collision/+merge/208645
[15:05] <rsalveti> awesome
[15:05] <kgunn> gerry just warned me
[15:09] <sil2100> bfiller: what's up?
[15:10] <bfiller> sil2100: good for now
[15:25] <rsalveti> didrocks: can I get a silo for line 31?
[15:26] <sil2100> didrocks: lemme see
[15:30] <ogra> popey, could you try something on a 4.4l based mako ?
[15:30] <seb128> ralsina_, didrocks, sil2100, Laney: upgrade went without issue here (using the ppa-010, auto download on wifi, 209->212)
[15:31] <ogra> popey,  adb shell "dmesg | grep ACL"
[15:31] <seb128> I'm waiting for Laney to be back to check with him, but I would say +1 for landing that slot
[15:31] <ogra> popey, does that return any systemd-udevd messages for audio devices ?
[15:32] <rsalveti> I think it returns a bunch of messages for a bunch of devices
[15:32] <rsalveti> not sure why yet
[15:33] <ogra> rsalveti, right
[15:33] <popey> ogra: [   21.517747] Bluetooth: opening HCI-SMD channel :APPS_RIVA_BT_ACL
[15:33] <ogra> rsalveti, i see it on flo, but not on my mako with image 196 (4.2)
[15:33] <ogra> popey, thats all ?
[15:33] <popey> yes
[15:33] <ogra> great
[15:33] <ogra> rsalveti, so mako doesnt have it
[15:34] <ogra> even on 4.4
[15:34] <ogra> seems to be flo specific
[15:34] <rsalveti> all multimedia related
[15:34]  * ogra checks manta
[15:34] <cyphermox> ogra: popey: what's this? for bluetooth?
[15:34] <ogra> cyphermox, no idea, i was looking for alsa stuff :)
[15:35] <ogra> for bug 1286184
[15:35] <rsalveti> ogra: maybe because of the default permissions for them?
[15:35] <rsalveti> crw-rw---- 1 system video 81, 1 Feb 28 15:33 /dev/v4l-subdev0
[15:35] <Laney> seb128: Yeah indeed
[15:35] <Laney> are we allowed to do it?
[15:35] <cyphermox> ogra: oh okay
[15:35] <rsalveti> ogra: might might have it 664 or similar
[15:35] <ogra> hmm, perhaps
[15:36] <ogra> i'll check them
[15:36] <ogra> but udevd runs as root
[15:36] <seb128> Laney, didrocks said that if we did manual testing and it worked fine he would be fine with us publishing
[15:36] <ogra> it should be able to set the acls
[15:36] <Laney> seb128: ok cool, let me do that then
[15:36] <seb128> didrocks, confirming that we can land l10?
[15:36] <ogra> grrr
[15:36] <ogra> my manta is dead
[15:36] <Laney> sil2100 thinks it is 'fishy'
[15:36] <seb128> Laney, wait for didrocks to confirm
[15:36] <Laney> for what reason?
[15:37] <seb128> read backlog ;-)
[15:37] <Laney> I didn't see any clear explanation
[15:37] <seb128> sil2100, ^
[15:37] <seb128> I think he just hit issues, but he didn't give specific
[15:37] <seb128> so it could be anything
[15:37] <ogra> great
[15:38] <Laney> yes quite
[15:38] <ogra> manta doesnt have it either
[15:38] <Laney> it's not very helpful
[15:38] <rsalveti> Operation not supported
[15:38] <rsalveti> yeah, should be kernel related
[15:38] <rsalveti> missing config or such
[15:39] <ogra> right
[15:40] <sil2100> seb128, Laney: I'll double check that one, had some problems with system upgrade (had an error message), but didn't confirm if it didn't happen for me with the pacakges reverted
[15:40] <sil2100> As I'm dealing with unity8 now
[15:40] <seb128> sil2100, when do you think you can check?
[15:40] <Laney> what error and when did you do it?
[15:40] <kgunn> sil2100: ready for a mir silo whenever you get the chance
[15:40] <sil2100> seb128: in a few moments, unity8 tests just finishing their run
[15:40] <seb128> k
[15:40] <seb128> thanks
[15:41] <Laney> please file a bug or tell someone next time
[15:43] <rsalveti> ogra: it seems we're missing CONFIG_TMPFS_POSIX_ACL
[15:44] <ogra> rsalveti, fun, apw checked the config when we talked about it and told me it was on
[15:44] <ogra> (i didnt check myself though=
[15:44] <ogra> )
[15:44] <rsalveti> config/config.common.ubuntu:# CONFIG_TMPFS_POSIX_ACL is not set
[15:44] <ogra> yeah
[15:44] <rsalveti> I know config/enforce forces that
[15:44] <rsalveti> but not sure if it's indeed working
[15:44] <rsalveti> do we have /proc/config?
[15:44] <ogra> nope
[15:44] <ogra> not on flo at least
[15:44] <rsalveti> sadpanda
[15:45] <ogra> we should probably have it since we dont ship a config in boot
[15:45] <rsalveti> /boot/config should have it
[15:45] <rsalveti> ogra: yeah
[15:45] <ogra> if we would use the packages :)
[15:45] <rsalveti> sure, I mean, just for us to check
[15:45] <apw> rsalveti, in which tree
[15:46] <rsalveti> apw: flo
[15:46] <apw> i checked it in the one ogra was suggesting it was off in, mako
[15:46] <apw> well there you go
[15:46] <rsalveti> 2899 # CONFIG_TMPFS_POSIX_ACL is not set
[15:46] <rsalveti> yeah, disabled
[15:46] <ogra> rsalveti, added a note to the bug
[15:46] <rsalveti> apw: can you enable that for us?
[15:46] <ogra> apw, bug 1286184 has all info
[15:47] <ogra> please enable /proc/config.gz too
[15:47] <rsalveti> yeah
[15:47] <apw> you want the config built into the kernel, on devices the size of a peanut ?
[15:47] <ogra> (noted there as well, tell me if you need a separate bug)
[15:47] <ogra> apw, yes
[15:47] <apw> why?
[15:47] <apw> whats wrong with the one on disk
[15:47] <ogra> apw, to find out about options i have to pull the kernel source otherwise
[15:47] <rsalveti> we don't have the one on the disk
[15:47] <ogra> apw, there is none on disk
[15:48] <apw> well only cause you remove it to save space
[15:48] <ogra> apw, we nebvber install the kernel package in the rootfs
[15:48] <apw> it is in the package
[15:48] <sil2100> Publishing unity8 - packaging changes made by coredev (xnox), so auto-+1'ed
[15:48] <sil2100> ;)
[15:48] <rsalveti> sil2100: which silo?
[15:48] <ogra> apw, the zImage and modules only get pulled into the android boot.im at android package build time
[15:48] <apw> it still makes more sense to copy that file into the flash than it does to fill memory, actual ram with it
[15:48] <ogra> from the kernel .deb
[15:48] <rsalveti> right
[15:48] <ogra> android has it on by default
[15:49] <ogra> i dont think it does any harm
[15:49]  * ogra also wouldnt call 2G a peanut :) 
[15:50] <sil2100> rsalveti: assigned 003
[15:50] <sil2100> rsalveti: ah, you mean the unity8?
[15:50] <rsalveti> sil2100: oh, sorry, yeah, unity8
[15:50] <sil2100> Silo 008
[15:50] <rsalveti> cool
[15:51] <apw> ogra, if that is what you want ... i will note my objection h
[15:51] <apw> here, as the filesystem is the sensible place for it
[15:51] <ogra> apw,  we want to rip out all device specific bits from the fs
[15:51] <apw> there is a device specific tarball for this kind of thing right?
[15:51] <ogra> yes, of the android container
[15:52] <sil2100> seb128, Laney: ok, so I reverted the packages and I still see the problem, I see an error of the likes of "FileNotFoundError: [Errno 2] No such file or directory: '/android/cache/recovery'" in the updates panel of system settings
[15:52] <sil2100> Maybe it's caused by my infameous dual-boot?
[15:52] <rsalveti> we could try to make it available at /system/boot/
[15:52] <rsalveti> that would make everyone happy I guess
[15:52] <ogra> sil2100, err
[15:52] <apw> ogra, to me getting every user of the phone to waste memory cause you haven't got the git repo is also strange
[15:52] <seb128> sil2100, seems like something on your install is busted
[15:52] <ogra> sil2100, pretty please never use diual boot during *any* testing
[15:53] <ogra> sil2100, it cant do OTA
[15:53] <rsalveti> ogra: apw: let me change the packaging then to drop that at /system/boot or similar
[15:53] <rsalveti> the modules are already part of the android system image anyway
[15:53] <ogra> sil2100, the recovery img gets abused for the dual boot, you cant even download the files
[15:53] <ogra> its a hack, dont use it
[15:53] <Laney> I think we can disregard those results :-)
[15:53] <ogra> rsalveti, hmm, k
[15:53] <sil2100> Indeed!
[15:53] <Laney> however...
[15:54] <Laney> there should be a way to turn off the updates in that case
[15:54] <sil2100> Well, I think we need someone else to double-check the test results
[15:54] <sil2100> Laney: well, dual-boot is not official, so I don't think that's needed
[15:54] <Laney> Lots of people have tested it
[15:54] <ogra> Laney, yes, i added a whishlist bg for it ... seb128 told me there would be no developer time to fix it though
[15:54]  * sil2100 likes the dual-boot
[15:54] <ogra> sil2100, its a hack
[15:54] <Laney> ogra: Free software man
[15:54] <ogra> please never use it when testing anything official
[15:54] <Laney> Just because we won't work on it doesn't mean it shouldn't be there
[15:55] <ogra> Laney, indeed :)
[15:55] <ogra> Laney, its just that chances are low to get it fixed
[15:55] <sil2100> This way I can safely use my mako as my main phone - whenever something doesn't work on UT then I can switch to android and have it working again ;)
[15:55] <ogra> sil2100, again, please dont use it for any official testing
[15:55] <ogra> you can do whatever you want for personal use :)
[15:56] <ogra> but there are plenty of hacks in the install process of the dual boot that can easily taint your results
[15:56] <ogra> (we refuse to support it for a reason ... )
[16:09] <Laney> it was trumpeted at the time though
[16:12] <sil2100> geh
[16:12] <seb128> sil2100, so it's ok to land it?
[16:12] <sil2100> Thing keep bumming me out this week it seems
[16:13] <sil2100> seb128: I would still like someone to try upgrading his system with the packages from the silo
[16:13] <seb128> sil2100, I did that an hour ago
 ralsina_, didrocks, sil2100, Laney: upgrade went without issue here (using the ppa-010, auto download on wifi, 209->212)
[16:14] <seb128> I installed the ppa content on 209
[16:14] <seb128> rebooted
[16:14] <Laney> Many people have tried it
[16:14] <seb128> then upgraded to 212
[16:14] <Laney> me, barry, mandel
[16:14] <sil2100> Oh! Missed that ping :) THanks!
[16:15] <sil2100> Let me publish it then, the rest looks fine
[16:15] <seb128> ok to land then? ;-)
[16:15] <ogra> ++
[16:15] <Laney> I'm doing it
[16:15] <seb128> we can do the publishing
[16:15] <Laney> already have the page open :P
[16:15] <seb128> sil2100, ^
[16:15] <seb128> Laney, thanks
[16:15] <seb128> \o/
[16:15]  * Laney slaps 2fa
[16:15] <mandel> awesome! seb128, sil2100, Laney thx!
[16:15] <ogra> :)
[16:16] <Laney> http://162.213.34.102/job/landing-010-2-publish/16/console
[16:17] <seb128> Laney, SUCCESS
[16:17] <seb128> \o/
[16:17] <Laney> yeah friday uploads!
[16:17] <seb128> haha
[16:22] <sil2100> All these Friday uploads are planned uploads!
[16:24] <didrocks> rsalveti: what's this line 31? the pulseaudio fix wasn't enough? (just trying to gather info for the email ;))
[16:25] <didrocks> rsalveti: or is it for the camera fix?
[16:25] <rsalveti> didrocks: bug 1284731
[16:25] <rsalveti> didrocks: no, not camera yet
[16:25] <rsalveti> didrocks: not critical for pulse, but a good fix
[16:26] <rsalveti> so it can requests rt priority from rtkit
[16:26] <rsalveti> when doing voice calls
[16:26] <didrocks> rsalveti: oh yeah, indeed a good one :)
[16:26] <rsalveti> didrocks: camera is in progress
[16:26] <didrocks> rsalveti: thanks for the infos ;)
[16:27] <rsalveti> np
[16:27] <didrocks> sil2100: ogra: let's kick an image as soon as unity8 is in the release pocket
[16:27] <didrocks> (now that you can track it live on the spreadsheet :p)
[16:28] <didrocks> plars: hey, mind checking that all flaky tests are due to the crash on image 212 for the meeting?
[16:28] <ogra> didrocks, btw, i would like to land this one https://code.launchpad.net/~mterry/session-manager-touch/exec-usc/+merge/208636 (one liner, tested omn all devices, fixes an issue on shutdown) with a direct upload
[16:28] <didrocks> plars: and that the crash is the known one
[16:28] <ogra> (not urgent, but i dont want to forget about it over the weekend)
[16:29] <plars> didrocks: I'm trying to get flo/manta looking a bit better, but I guess you are talking about mako?
[16:29] <didrocks> ogra: sure, please do, but let's not delay this image on it
[16:29] <didrocks> plars: please focus on mako first
[16:29] <didrocks> plars: for now, forget manta :)
[16:29] <didrocks> plars: do you need a recipe to validate the .crash files?
[16:29] <didrocks> (I pasted one to psivaa)
[16:29] <plars> didrocks: no, I didn't
[16:29] <ogra> didrocks, yeah, doesnt matter if it gets into this image or the next one
[16:30] <didrocks> plars: ok, seems we have 5 crashes to validate :)
[16:30] <didrocks> plars: you think you will have that for the meeting?
[16:30] <ogra> didrocks, btw, i wrote some desktop tools to monitor images recently ... (one that rings an alarm if a build is done, another one wheer you can type in the image number and get the right changelog automatically) i'll push them to the pahblet-team ppa once i'm done, should be helpful for all image producers
[16:31] <didrocks> ogra: ahah, excellent!
[16:31] <ogra> (just some zenity with shell scripts)
[16:31] <didrocks> urgh zenity :p
[16:31] <ogra> yeah, will re-do in QML later :)
[16:32] <didrocks> ahah
[16:32] <plars> didrocks: I'll check them out
[16:35] <plars> didrocks: you are talking about the app crashes, not things like qmlscene right?
[16:40] <didrocks> plars: all crashers
[16:40] <didrocks> plars: it's 1 min per crash to see :)
[16:40] <rsalveti> ogra: cool, get us an irc bot as well :-)
[16:41] <ogra> rsalveti, working on that :)
[16:41] <rsalveti> I can pay in beers
[16:41] <ogra> haha
[16:41] <rsalveti> awesome
[16:49] <didrocks> unity8 in!
[16:49] <didrocks> let's kick an image
[16:50] <didrocks> hum, rmadison disagree :)
[16:50] <didrocks> my script is still relying on lp :p
[16:50] <seb128> wouut
[16:51] <seb128> Laney, upload on friday, and it's even to make into an image on friday :p
[16:51] <Laney> heh
[16:51] <Laney> didrocks: can you wait for ubuntu-download-manager and system-image?
[16:51] <seb128> how come u-s-s moved first?
[16:52] <didrocks> Laney: I would prefer not, any reason?
[16:52] <seb128> oh, the others ones have autopkgtests
[16:52] <didrocks> Laney: if we keep delaying on more and more components…
[16:52] <Laney> so that the fixes are in ...
[16:52] <seb128> didrocks, we got the u-s-s update without the other 2 from the same silo
[16:52] <didrocks> argh
[16:52] <didrocks> ok then :(
[16:52] <seb128> that's an untested mix
[16:52] <seb128> u-s-s went through but britney/autopkgtest are delaying the other ones
[16:53] <xnox> how are things looking? will ubuntu-ui-toolkit land today, or is it posponed till monday?
[16:53] <Laney> the tests all passed afaics
[16:53] <seb128> right
[16:53] <seb128> next publisher run
[16:59] <ogra> didrocks, it in, do you want to trigger the build or want me to do it ?
[16:59] <ogra> *it is
[16:59] <didrocks> ogra: even ubuntu-download-manager and system-image?
[16:59] <ogra> ah, only looked for unity8
[16:59] <didrocks> ogra: yeah, see ^ :(
[16:59] <didrocks> we have to wait now
[17:00] <ogra> yeah
[17:01] <seb128> it's not going to be long, the tests are done, next publisher run
[17:01] <seb128> likely less than 10min
[17:02] <didrocks> balloons: joining?
[17:05] <seb128> didrocks, ogra, Laney: system-image is in, looks like the download-manager is going to need another run
[17:05] <ogra> the source doesnt seem to have moved yet
[17:06] <ogra> ogra@anubis:~/Devel/branches/ubuntu-touch-session-0.104$ rmadison system-image|grep proposed
[17:06] <ogra>  system-image | 2.1-0ubuntu4   | trusty-proposed/universe | source
[17:06] <seb128> ogra, right, I was looking at the output page
[17:07] <Laney> it will
[17:07] <Laney> have faith
[17:07]  * ogra does ... just not in the timing
[17:07] <ogra> (except for rmadison)
[17:21] <robru-sick> rsalveti, i'm probably less busy than cyphermox if you need any help landing/testing
[17:21] <rsalveti> cool, thanks
[17:22] <ogra> robru-sick, still sick ?
[17:22] <robru-sick> ogra, yeah, it's quite bad, my throat is very scratchy & swollen. i'm lying in bed with laptop
[17:22] <ogra> oh man
[17:22] <ogra> hope you get better soon
[17:23] <ogra> thats going on a week already, isnt it ?
[17:23] <robru-sick> ogra, thanks. it's been two weeks now, i just wasn't complaining about it before.
[17:23] <ogra> oww
[17:24] <robru-sick> ogra, yeah, i got it right as I was moving. something about being in and out all day really weakened my immune system
[17:25] <Laney> udm is going over now
[17:25] <Laney> ogra: do you know wait-for-package on nusakan?
[17:25] <ogra> didrocks, want me to trigger the image ? i plan to work late today anyway
[17:25] <ogra> Laney, sure
[17:25] <ogra> i love it
[17:25] <didrocks> ogra: if you can, that would be awesome!
[17:25] <ogra> didrocks, fine then
[17:26] <Laney> you could use it in this case :-)
[17:26] <ogra> Laney, well, if i wouldnt hop between office and living room, yeah
[17:26] <Laney> screen?
[17:26] <didrocks> thanks ogra ;)
[17:26] <seb128> Laney, can you clean the silo? ;-)
[17:26]  * seb128 wants to put another u-s-s in
[17:26] <Laney> once rmadison has udm
[17:27] <ogra> Laney, ah, that modern stuff
[17:27] <seb128> the gdoc says they are in destination
[17:27] <seb128> is that not true.
[17:27] <seb128> ?
[17:28] <Laney> it should be, just not visible via rmadison yet
[17:28] <seb128> didrocks, where do you get the "packages are in destination" status from? not rmadison?
[17:28] <Laney> well, lp says it's gone over
[17:28] <didrocks> seb128: no, launchpad
[17:28] <seb128> k
[17:28] <Laney> probably gets it from the state there
[17:28] <Laney> I guess that's enough tbh
[17:28]  * Laney cleans
[17:28] <seb128> Laney, you are being overzealous :p
[17:29] <Laney> http://162.213.34.102/job/landing-010-3-merge-clean/11/console
[17:29] <seb128> thanks
[17:31] <robru-sick> bregma, ping me when line 33 is ready and I can assign you a silo.
[17:35] <ogra> [17:39] <bregma> robru-sick, I will, but it will probably be an hour or so while I test a last-minute FTBFS fix for ppc64le (said build is killing my local machine)
[17:39] <Laney> bregma: you should use a beefy cloud instance to build :-)
[17:42] <robru-sick> bregma, no worries, i'm around
[18:01] <xnox> ..
[18:01] <xnox> bzoltan pinged me to merge and resolve 3 branches that have conflicts between them.
[18:01] <xnox> I've now done so, in https://code.launchpad.net/~xnox/ubuntu-ui-toolkit/py32ap+listview-scroll_to_bottom+qmlapicheckverbose/+merge/208859
[18:01] <xnox> not sure what needed to happen next to get the three branches bundled correctly.
[18:01] <xnox> ..
[18:12] <bzoltan> xnox: I have replaced the MR with the non conflicting one, but the "build" does not pick it up ... maybe somebody from the landing team could help us.
[18:13] <bzoltan> robru-sick: ^^
[18:16] <bzoltan> cyphermox: ping
[18:16] <cyphermox> pong
[18:17] <bzoltan> cyphermox:  we have a situation with xnox ^^^
[18:17] <bzoltan> cyphermox: in silo 13
[18:18] <cyphermox> so yu want me to reconfigure and make it just xnox's branch?
[18:20] <ogra> cyphermox, can i get a silo for line 34 (and possibly some hand holding, i had a bootcamp but zero practical experiance)
[18:21] <cyphermox> ogra: sure, give me a minute I'm in lunch time, having a meeting with my game development team ;)
[18:21] <ogra> cyphermox, no hurry ...
[18:29] <robru-sick> ogra, i can do it
[18:29] <ogra> robru-sick, great
[18:30] <robru-sick> ogra, ok, you got silo 8. so you can click 'build' on the 'landing-008' tab of the spreadsheet
[18:31] <ogra> thanks !
[18:31] <robru-sick> ogra, you're welcome
[18:31] <robru-sick> bzoltan, did you get your reconfigure for silo 13? I can do it if not
[18:32] <ogra> bah, i get access denied on jenkins
[18:32] <ogra> "No permission for 'Job/Build' "
[18:32] <robru-sick> ogra, darn. you'll have to ask didier for permissions there. i can do it for today though
[18:32] <ogra> thanks again
[18:34] <robru-sick> no worries
[18:34] <robru-sick> seb128, you got silo 10, please build
[18:34] <seb128> robru-sick, thanks
[18:34] <robru-sick> you're welcome!
[18:35] <cyphermox> bzoltan: ping?
[18:36] <cyphermox> bzoltan: I'm still waiting for the confirmation that reconfiguring with just that one commit is indeed what you wanted me to do
[18:37] <robru-sick> ralsina_, please merge & clean silo 14
[18:37] <robru-sick> cgoldberg, please merge & clean silo 9
[18:37] <cgoldberg> robru-sick, will do now.. thanks
[18:37] <robru-sick> cgoldberg, thank you!
[18:37] <bzoltan> cyphermox: sorry I ost the connection
[18:38] <bzoltan> cyphermox: I woud need the new MR instead of the old from xnox
[18:38] <bzoltan> cyphermox:  but of course together with the other 12
[18:41] <cyphermox> bzoltan: could you update the spreadsheet to the correct list of MRs ?
[18:42] <bzoltan> cyphermox: in the pending page I have updated
[18:42] <cyphermox> ah, cool then :)
[18:45] <cyphermox> hrm, I see some conflicts still but I'll resolve them now
[18:45] <cyphermox> I think https://code.launchpad.net/~kalikiana/ubuntu-ui-toolkit/qmlapicheckverbose/+merge/187243 also shouldn't bethere sicne it would be included in xnox's branch
[18:45] <cyphermox> same for https://code.launchpad.net/~elopio/ubuntu-ui-toolkit/listview-scroll_to_bottom/+merge/202129
[18:46] <bzoltan> cyphermox: OK... so I remove these two
[18:47] <cyphermox> only if you agree with my assessment ;)
[18:47] <bzoltan> cyphermox: xnox said that he merged to his MR
[18:47] <cyphermox> yes
[18:48] <bzoltan> xnox: do you confirm?
[18:48] <ralsina_> robru-sick: done
[18:50] <cyphermox> ok it's running
[18:50] <cyphermox> bzoltan, I can see the merges in his commits so it's good
[18:50] <robru-sick> ralsina_, thanks
[18:51] <bzoltan> cyphermox:   Fantastic. Thanks a lot for your help!
[18:52]  * bzoltan opens a beer and drinks it for the CI team :D
[18:52] <bzoltan> it is 8pm for /me
[18:52] <bzoltan> errrr 9pm
[18:52] <cyphermox> bzoltan: it's ready to rebuild
[18:52] <ogra> you are exaggerating !
[18:52] <ogra> 7:52
[18:52] <ogra> :P
[18:52]  * cyphermox picks up a beer
[18:53] <cyphermox> hey, it's almost 2pm now here ;)
[18:53] <ogra> beer time :)
[18:53]  * cyphermox grabs lunch at the same time
[18:53] <cyphermox> too bad I don't actually have beer here
[18:54] <ogra> take a whisky then :)
[18:54] <ogra> will do as well
[19:09] <bzoltan> xnox: ping
[19:10] <ogra> [19:31] <bzoltan> cyphermox: those conflicts was just the top ... I puled off that MR from xnox. Let's first land the original 12 MR and then handle the one from xnox on a clean trunk
[19:32] <cyphermox> alright
[19:32] <bzoltan> cyphermox: would you please reconfigure the silo again
[19:33] <cyphermox> sure
[19:34] <bzoltan> cyphermox: thanks
[19:34] <cyphermox> as I mentioned befoe though you need to rebuild everything before it works, and I think you need to pass a parameter since you've had builds prior
[19:35] <bzoltan> cyphermox: sorry, what should I do?
[19:43] <cyphermox> bzoltan: ignore me, should be fine ;)
[19:43] <bzoltan> cyphermox: it looks better now
[19:43] <t1mp> bzoltan: you should open a second beer and watch the stuff land :)
[19:48] <bregma> hey robru-sick line 33 is ready and eager for a silo now
[19:48] <robru-sick> bregma, on it
[19:49] <bregma> oooh, I see a present for me in landing-008, too, goody goody goody
[19:51] <robru-sick> bregma, you got silo 9, please build
[19:51]  * bregma goes clicky clicky clicky
[19:51] <tvoss_> bregma, rofl
[20:18] <rsalveti> robru-sick: can I get a silo for line 36?
[20:27] <rsalveti> cyphermox: ^ maybe you as well, if you're around
[20:30] <robru-sick> rsalveti, on it
[20:30] <rsalveti> robru-sick: awesome, thanks
[20:31] <robru-sick> rsalveti, oh, i don't see an MP in the F column?
[20:31] <xnox> bzoltan1: cyphermox: i've merged the three branches together. i believe i was clear that that mega+ branch replaces the other three branches...
[20:31] <xnox> i'm away from keyboard now. long past EOD.
[20:32] <xnox> i thought, the three branches are removed, that mega one added and reconfigure =/ but i'm not silo/lander trained at all.
[20:32] <bfiller> robru-sick: silo-004 ready for release when you have a moment
[20:32] <robru-sick> rsalveti, can't do anything without an MP. are we not upstream of ofono?
[20:33] <rsalveti> robru-sick: package upload
[20:33] <robru-sick> bfiller, i notice your silo includes a fix for qt 5.2 build failures. will those fixes break if they land before qt 5.2?
[20:34] <bfiller> robru-sick: no they won't break
[20:34] <bfiller> robru-sick: tested agasint latest build
[20:34] <robru-sick> bfiller, ok
[20:35] <bzoltan1> xnox:  do not bother ... the MP is busted anyway :( I need kalikiana to help with it
[20:35] <xnox> bzoltan1: meh. ok.
[20:35] <robru-sick> rsalveti, if you want to release lp:ofono trunk, you need to submit a null merge against trunk. citrain works exclusively on MPs. no MP, no silo
[20:36] <robru-sick> rsalveti, is this the first release of lp:ofono?
[20:36] <rsalveti> robru-sick: right, we don't have a branch for it set-up at this point, so that's why I want to do just a package upload
[20:36] <rsalveti> I was always uploading to the archive by hand
[20:36] <rsalveti> so now I just want to go in a silo first
[20:36] <rsalveti> that's why we don't have a MR/branch for it now
[20:36] <robru-sick> rsalveti, i literally can't assign a silo unless there's an MP. so you need to make a null merge for me to build in a silo.
[20:37] <rsalveti> robru-sick: well, it is possible, I just have one like that (see 31)
[20:38] <rsalveti> 24 is another similar one
[20:39] <robru-sick> rsalveti, go figure, never seen that before. Ok, you got silo 11. but this approach doesn't make sense, you can use any PPA for this purpose. citrain only makes sense when you're building & merging MPs. by doing a manual upload of a single package to a PPA, you literally get none of the benefits of CItrain process
[20:40] <rsalveti> robru-sick: well, it's better still to just go with ci train, as we can coordinate the testing and so on
[20:40] <rsalveti> and automatically get the packages published as well
[20:40] <rsalveti> once we hit promote
[20:40] <rsalveti> and we also know we get a clean ppa
[20:40] <robru-sick> rsalveti, yeah, but if you have an MP, you get automatic release tagging, automatic uploads... now you have to prepare the upload manually anyway, only difference is you upload to one PPA instead of another.
[20:40] <rsalveti> that provides all the right builders and so on
[20:41] <rsalveti> robru-sick: yup, but that's what I wanted :-)
[20:41] <rsalveti> robru-sick: thanks!
[20:41] <robru-sick> ok
[20:46] <bfiller> robru-sick: silo-002 ready for release too, doesn't break qt5.0 either
[20:46] <robru-sick> bfiller, just want to confirm that you're really dropping this voicemail stuff? http://162.213.34.102/job/landing-004-2-publish/lastSuccessfulBuild/artifact/packaging_changes_dialer-app_0.1+14.04.20140228-0ubuntu1.diff
[20:47] <robru-sick> bfiller, oh i see from the changelog it got merged. no worries
[20:47] <bfiller> robru-sick: yup, should be good
[20:48] <robru-sick> bfiller, ok, published silo 4, looking at 2
[20:49] <robru-sick> bfiller, ok, both published, looking good
[20:49] <bfiller> robru-sick: thanks
[20:49] <robru-sick> bfiller, you're welcome!
[20:53] <boiko> robru-sick: do you by chance know what is going on on line 20 of the spreadsheet? is that an error or just an intermediate state?
[20:54] <robru-sick> boiko, intermediate state. it's telling you that your stuff is just in -proposed, not released yet. it'll turn green when it's ready to hit 'merge & clean'
[20:54] <boiko> robru-sick: nice! thanks!
[20:55] <robru-sick> boiko, you're welcome
[21:33] <bfiller> fginther: any chance you can get CI setup for lp:sync-monitor. It's a new project we need to get integrated into touch
[21:34] <fginther> bfiller, it's already setup, been there for a week or more
[21:34] <fginther> bfiller, is it not working?
[21:35] <bfiller> fginther: oh really, cool. renato ^^^
[21:43] <robru-sick> bfiller, hey what's going on on line 29? does that need a silo? i thought that was one of the ones i just published...
[21:43] <bfiller> robru-sick: looking
[21:44] <bfiller> robru-sick: you published line 26, line 29 are more qt5.2 fixes
[21:44] <robru-sick> bfiller, oh, silo 4 is on line 20, and silo 2 is on line 26, so it looks like this one does need a silo.
[21:44] <robru-sick> bfiller, ok, assigning
[21:45] <bfiller> robru-sick: thanks, the sheet is confusing
[21:45] <robru-sick> bfiller, yeah, there's a lot going on since the embargo ended ;-)
[21:45] <robru-sick> bfiller, oh, i need you to merge & clean silo 4 before I can assign line 29. also please merge silo 2 while you're at it ;-)
[21:47] <bzoltan1> robru-sick: would you please reconfigure the silo13? I ripped off one MR what can not get together with an other one
[21:47] <bfiller> robru-sick: done
[21:47] <robru-sick> bzoltan1, ok
[21:47] <robru-sick> bfiller, thanks
[21:47] <bzoltan1> robru-sick: thanks
[21:49] <robru-sick> bzoltan1, ok, silo 13 reconned, please rebuild
[21:53] <bzoltan1> robru-sick: sweet, thanks ...
[21:53] <rsalveti> ogra: no more acl errors
[21:53] <robru-sick> bzoltan1, you're welcome
[21:53] <rsalveti> \o/
[21:53] <ogra> yay !!!
[21:54] <ogra> rsalveti, i'm not even sure they caused any issues :)
[21:54] <rsalveti> probably not
[21:54] <rsalveti> but anyway :-)
[21:54] <ogra> but they filled dmesg
[21:54] <ogra> :)
[21:54] <ogra> i'm more interested if RT will gain us anything
[21:55] <rsalveti> yeah
[22:07] <robru-sick> bfiller, ok, you got silo 2, please build!
[22:27] <robru-sick> bregma, published silo 9, please merge & clean when it hits distro.
[22:28] <robru-sick> bfiller, do you need a silo for line 37 yet? it's not marked as ready but looks ready
[22:28] <bfiller> robru-sick: I'm waiting on one other MR that I wanted to add to it
[22:29] <bfiller> robru-sick: will keep you posted
[22:29] <robru-sick> bfiller, ok great
[22:32] <robru-sick> bfiller, ok you got silo 4 ;-)
[22:33] <bfiller> robru-sick: nice, I just added the other mr
[22:33] <bfiller> you're quick :)
[23:33] <bfiller> robru: silo-004 (line 36) ready to land
[23:33] <bfiller> robru: line 37 needs a silo
[23:33] <robru> bfiller, on it, thanks
[23:35] <robru> bfiller, ok, 4 published, and you got silo 14.
[23:36] <bfiller> robru: great, thanks
[23:36] <robru> bfiller, you're welcome