[03:39] <lostlamb> greetings, I apologise if this is the wrong channel to be asking such a question, but I'm trying to install potent poinsettia or something like that to my alienware laptop.  The issue I'm running into is that it's not detecting my graphics card drivers. cont-
[03:39] <lostlamb> this is to be expected, but the screen is locking up after I tell it to use low settings and won't respond to anything save powering the system down.  Is there any way to get into the main OS to grab the drivers online?
[03:47] <lostlamb> Sorry again, I appear to be in the wrong place
[03:47] <lostlamb> !quit
[03:47] <lostlamb> #quit
[05:10] <veebers> Saviq: When you're online, I'm keen to get this MR merged:https://code.launchpad.net/~veebers/unity8/ap_make_use_of_helpers_in_tests/+merge/191575
[05:10] <veebers> oh, there is also this one :-) https://code.launchpad.net/~veebers/unity8/update_ap_tests_ready_for_py3/+merge/194655
[06:48] <Mirv> Saviq: interestingly unity8 has now built against Qt 5.2 on x86 but still failed on armhf https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-beta2/+sourcepub/3668605/+listing-archive-extra
[06:48] <Mirv> commented that on the bug
[09:20] <Saviq> Mirv, hmm, has Qt changed there? like did you pick up changes from the release branch?
[09:22] <tsdgeos> Saviq: ping
[09:22] <Saviq> tsdgeos, pong
[09:22] <tsdgeos> Saviq: the issue we're having in arm
[09:22] <tsdgeos> i can repro here
[09:22] <tsdgeos> doesn't seem to handle expcetions nicely
[09:22] <tsdgeos> http://paste.ubuntu.com/6441838/ makes it crash
[09:22] <tsdgeos> on the phone
[09:22] <tsdgeos> not on desktop
[09:22] <Mirv> Saviq: no changes
[09:23] <Saviq> tsdgeos, sounds bad
[09:23] <tsdgeos> Saviq: the "good" news is that we're really not using that Time.js anywhere, so we can kill the test+file that is testing since noone is using it and get unity8 to build
[09:23] <tsdgeos> Saviq: still i think we should pursue this working
[09:23] <Saviq> tsdgeos, +1
[09:23] <tsdgeos> Saviq: so i wonder if we want to remove the time.js at this stage to unblock the build or not
[09:24] <Saviq> tsdgeos, yeah, let's - let's find more fuckups in v4
[09:24] <Saviq> earlier rather than later
[09:24] <tsdgeos> he he
[09:24] <tsdgeos> ok, so i'll remove the code altogether, open a bug in qt about it and try to find out who can point me in the correct decision to fix it
[09:24] <tsdgeos> Saviq: sounds right?
[09:25] <Saviq> tsdgeos, yup
[09:25] <tsdgeos> dednick: i remerged https://code.launchpad.net/~aacid/unity8/lvwph_bad_header_position_1245824 can you re-review/re-approve?
[09:26] <tsdgeos> Mirv: can you confirm exactly which packages we are using in that ppa?
[09:27] <Saviq> tsdgeos, can you explain why the other tests passed suddenly? the ones with singleton, I mean?
[09:27] <Saviq> tsdgeos, other than "we must've pulled new code"?
[09:27] <tsdgeos> there was a new upstream release that Mirv packaged¿?
[09:27] <tsdgeos> that's the only reason i can think of :D
[09:28] <Saviq> yeah, but Mirv says there wasn't ;)
[09:28] <tsdgeos> let me apt-get source
[09:28] <Saviq> or, he didn't ;)
[09:28] <tsdgeos> gah i can't apt-source in the phone since unity8 is not starting i have no interwebs
[09:29] <Mirv> tsdgeos: in which way exactly? 5.2 beta1, qtdeclarative did have recently added one of the patches that was pointed out by you
[09:29] <Saviq> tsdgeos, nmcli d wifi connect $ssid password $password
[09:29] <Saviq> Mirv, ah that explains it, yeah :)
[09:29] <Mirv> the qtbug-34617.patch one
[09:29] <mhr3> sil2100, while you're on upstream merger, one for lp:unity-scopes-shell too pls :)
[09:30] <didrocks> sil2100: hey! btw, if we can release that one, please feel free (I can help reviewing/NEWing it if needed)
[09:30] <Mirv> Saviq: tsdgeos: then other recent changes are new modules like qtsvg qtgraphicaleffects and qtmultimedia added there, but they are not in build-deps of unity8
[09:30] <Saviq> Mirv, no, the patch is the one that fixed unity8 building
[09:30] <sil2100> mhr3: will do as well ;) But I need Francis around for that, so later ;p
[09:31] <sil2100> didrocks: ok! I made a preliminary packaging review yesterday of unity-scopes-api, I'll poke you a bit later about preNEWing that ;)
[09:31] <Mirv> Saviq: ah, right.
[09:31] <Saviq> tsdgeos, did you look into qtubuntu failing to build in the end? it's failing due to missing setEventDispatcher
[09:32] <didrocks> sil2100: while you are at it, there is ubuntu-settings-components as well :)
[09:32] <tsdgeos> Saviq: is it failing to build?¿
[09:32] <tsdgeos> Saviq: i didn't know it was failing :D
[09:32] <tsdgeos> so no i didn't
[09:32] <didrocks> sil2100: not sure if seb128 has some time for reviewing/preNEWing them, but that would help in getting you ppu rights ;)
[09:33] <Saviq> tsdgeos, https://bugs.launchpad.net/qtubuntu/+bug/1246498
[09:33] <seb128> didrocks, sil2100: I can help doing reviews
[09:33] <tsdgeos> Saviq: Error: NetworkManager is not running. :D (for the nmcli thing)
[09:33] <Saviq> tsdgeos, https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-beta2/+sourcepub/3668316/+listing-archive-extra
[09:33] <Saviq> tsdgeos, initctl start network-manager I think
[09:34] <Saviq> tsdgeos, yeah
[09:34] <mhr3> sil2100, k, thx
[09:34] <tsdgeos> Saviq: now i need to make it know my network is there, i'll play with nmcli, tx
[09:34] <Saviq> Mirv, oh, you should put lp:unity-mir to build under Qt 5.2
[09:35] <tsdgeos> Saviq: ah
[09:35] <tsdgeos> Saviq: my branch hasn't been merged, obviously it doesn't build yet
[09:36] <Saviq> tsdgeos, ah to qtubuntu?
[09:36]  * Saviq reviews
[09:36] <tsdgeos> Saviq: yep
[09:36] <tsdgeos> gerry found an issue yesterday
[09:36] <sil2100> seb128, didrocks: I'll prepare the packaging for those and poke you guys for preNEW reviews ;)
[09:36] <tsdgeos> was waiting to throw it to him
[09:36] <tsdgeos> Saviq: but be my guest :-)
[09:36] <didrocks> thanks!
[09:36] <Saviq> tsdgeos, like it how you didn't know anything about it, but still fixed it ;D
[09:37] <dednick> tsdgeos: done
[09:37] <tsdgeos> Saviq: misunderstanding, i did know the "old" qtubuntu didn't build, i thought you were mentioning after my branch had been merged that is impossible because it had not been merged again
[09:37] <tsdgeos> basically my brain broke for a sec
[09:37] <Saviq> tsdgeos, no worries :)
[09:37] <tsdgeos> Saviq: branch is https://code.launchpad.net/~aacid/qtubuntu/event_dispatcher_52/+merge/194128 fwiw
[09:38] <Saviq> tsdgeos, yeah, building now
[09:39] <tsdgeos> dednick: i've been pulled to more qml/qtquick brokeness with 5.2, will not be able to have a look at the deleteLater stuff (at least not this morning)
[09:40] <Mirv> Saviq: ok, I'm adding a recipe for unity-mir also
[09:40] <dednick> tsdgeos: ok, no worries.
[09:43] <Mirv> Saviq: tsdgeos: can you btw attend https://blueprints.launchpad.net/ubuntu/+spec/client-1311-stateofqt5 tomorrow? I believe you might have more wise words to say how's it looking than I do, besides packaging and release schedule
[09:44] <Saviq> Mirv, I think I've a conflict there, let me ses
[09:44] <Saviq> see
[09:44] <tsdgeos> i think i said somewhere i'd be attending
[09:44] <Mirv> it's currently scheduled to be the first session of Wed, ie 14:00 UTC
[09:44] <tsdgeos> this uds thing is a bit confusing
[09:44] <Saviq> tsdgeos, yeah you did http://summit.ubuntu.com/uds-1311/meeting/22090/client-1311-stateofqt5/
[09:45]  * Saviq wanted to go to http://summit.ubuntu.com/uds-1311/meeting/21991/core-1311-cross-compilation/ that's at the same time
[09:45] <Saviq> I might leave you to it, tsdgeos
[09:45] <Saviq> you know everything I know there anyway
[09:45] <tsdgeos> sure
[09:46] <tsdgeos> there's the desktop thing that i don't know much though
[09:46] <tsdgeos> was sil2100 workking on the appmenu thing? how did it end up?
[09:49] <sil2100> Yes
[09:49] <Saviq> tsdgeos, hmm qtubuntu fails to build with your patch here: http://pastebin.ubuntu.com/6441942/ ideas?
[09:49] <sil2100> It's working, packaged, but requires a Qt5 with small patches
[09:49] <sil2100> And, of course, it's dependent on the Qt5 version used
[09:50] <tsdgeos> sil2100: so we're carrying those patches? or can they be upstreamed?
[09:50] <tsdgeos> Saviq: phone or desktop?
[09:50] <Saviq> tsdgeos, desktop
[09:50] <sil2100> tsdgeos: I'll try to get one of them upstreamed, but I guess the other one 'one-liner' won't be upstreamed so easily
[09:51] <tsdgeos> sil2100: oki
[09:51] <sil2100> tsdgeos: let me share those patches with you later on for comment, before I propose those upstream
[09:51] <tsdgeos> sil2100: ok!
[09:51] <tsdgeos> Saviq: let me rebuild it here
[09:52]  * Saviq needs to charge manta to build armhf
[09:54] <tsdgeos> Saviq: now that i re-read the topic of http://summit.ubuntu.com/uds-1311/meeting/22084/unity8-shell-discussion/ is it worth me attend it?
[09:54] <Saviq> tsdgeos, prolly not
[09:55] <tsdgeos> ok
[09:55] <tsdgeos> might still attend
[09:55] <Saviq> tsdgeos, unless you want to learn about apport- maybe, something about sbuild, cross-building
[09:55] <tsdgeos> Saviq: https://code.launchpad.net/~aacid/unity8/notime.js/+merge/195733
[09:55] <Saviq> nothing you couldn't learn by yourself from a wiki, or by buggin me
[09:56] <tsdgeos> he he
[09:56] <tsdgeos> ok
[09:59] <tsdgeos> Saviq: that build failure you have is against 5.2 or 5.0 ?
[09:59] <Saviq> tsdgeos, 5.2
[10:00] <Saviq> tsdgeos, 5.0 builds fine
[10:00] <tsdgeos> ok
[10:00] <tsdgeos> Saviq: any clue what causes stuff like https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-trusty/753/?#showFailuresLink ?
[10:00] <Saviq> tsdgeos, bug #1252386
[10:00] <tsdgeos> ah that one
[10:01] <tsdgeos> right
[10:02] <Saviq> tsdgeos, basically slow network...
[10:08] <Saviq> tsdgeos, unity-mir, too :/ https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-beta2/+sourcepub/3669443/+listing-archive-extra
[10:08] <Saviq> qqmlabstracturlinterceptor.h: No such file or directory
[10:09] <tsdgeos> Saviq: ok, writing that one down
[10:25] <nic-doffay> mzanetti, if you're looking into this: https://bugs.launchpad.net/unity8/+bug/1169258
[10:25] <mzanetti> nic-doffay: yes, I am
[10:38] <tsdgeos> Saviq: qtubuntu builds for me on the phone and on the desktop (on the desktop using my Qt)
[10:38] <tsdgeos> Saviq: can you do this
[10:38] <tsdgeos> nm -C /usr/lib/x86_64-linux-gnu/libQt5PlatformSupport.a | grep -i q_configFromGLFormat
[10:38] <tsdgeos> assuming you're on 64bits
[10:39] <Saviq> tsdgeos, came up empty
[10:39] <tsdgeos> that's kind of bad :D
[10:39] <tsdgeos> Mirv: can it be that we are not building egl support for the desktop on the 5.2 betas?
[10:39] <Saviq> must be
[10:39] <Saviq> /food
[10:43] <Mirv> tsdgeos: it can. there was a question about it at https://bugs.launchpad.net/qtubuntu/+bug/1215374 where I tinkered it a bit, so it comes down to using -opengl desktop most probably on x86
[10:46] <tsdgeos> Mirv: hmmm let me see
[10:46] <Cimi> there's a grid view 'delegateCreationBegin' and end property, I cannot find where it comes from
[10:46] <Cimi> it's not in the docs of gridview
[10:46] <Cimi> who as qt source code handy fora grep?
[10:46] <Cimi> tsdgeos, ^ ?
[10:47] <tsdgeos> Cimi: it's in our patches
[10:48] <Cimi> tsdgeos, which type is that?
[10:48] <Cimi> tsdgeos, I'd ike to add it to DashRenderer
[10:49] <tsdgeos> Cimi: qreal
[10:49] <Cimi> ok
[10:54] <Cimi> tsdgeos, and what's that?
[10:55] <Cimi> tsdgeos, for a dummy value for carousel
[11:01] <tsdgeos>     Add the possibility of specifying the delegate creation range
[11:01] <tsdgeos>     For itemviews that are inside itemviews using the contentY/height of the
[11:01] <tsdgeos>     itemview is not a good idea since it means you create all the items at
[11:01] <tsdgeos>     once. This adds two new properties that let you specify the
[11:01] <tsdgeos>     range where delegate creation should happen
[11:01] <tsdgeos> Cimi: undefined
[11:06] <mzanetti> tsdgeos: are .qtt tests still supported?
[11:06] <mzanetti> I couldn't find a qtsystemtest repo any more at least
[11:07] <tsdgeos> mzanetti: no clue what .qtt is :D
[11:07] <mzanetti> tsdgeos: pretty much my reaction when om26er asked me
[11:07] <mzanetti> tsdgeos: http://paste.ubuntu.com/6442222/
[11:09] <mzanetti> altough reading through this it somewhat looks like a definition for manual tests
[11:09] <mzanetti> om26er: ^
[11:09] <om26er> mzanetti, tsdgeos this branch https://code.launchpad.net/~ubuntu-branches/ubuntu/trusty/qtmultimedia-opensource-src-touch/trusty have a lot of those
[11:09] <tsdgeos> never seen one of those :/
[11:29] <Mirv> tsdgeos: Saviq: you might be interested also in tonight's http://summit.ubuntu.com/uds-1311/meeting/21986/core-1311-qt5-versions-in-ubuntu/
[11:29] <Mirv> ie. what to do when Touch + Kubuntu would theoretically need different Qt versions or other delta
[11:30] <Mirv> it's at a tough time slot for me, I'm still not 100% sure if I can make it myself
[11:30] <dandrader> Saviq, ping
[11:32] <Saviq> dandrader, pong
[11:33] <dandrader> Saviq, so, how do I solve problems with "quilt push". I was expecting to get something like a failed git cherry-pick or bzr merge but "bzr diff" shows that the tree is unaltered :/
[11:34] <dandrader> Saviq, so I should try out and solve the patch issues before adding it to quilt?
[11:34] <Saviq> dandrader, quilt push -f
[11:34] <Saviq> dandrader, that will drop .rej files
[11:34] <Saviq> dandrader, resolve the issues, and then quilt refresh
[11:51] <Saviq> tsdgeos, where do we stand with the egl issue?
[11:52] <tsdgeos> we stand
[11:52] <tsdgeos> :D
[11:53] <tsdgeos> Saviq: so basically qt 5.2 disable "egl support" if you enable opengl desktop support
[11:53] <tsdgeos> which given the *very* limited egl support on desktop support kind of makes sense
[11:53] <Saviq> tsdgeos, so we need to fix qtubuntu
[11:54] <tsdgeos> Saviq: now i can patch 5.2 to build both
[11:54] <tsdgeos> and it builds
[11:54] <tsdgeos> and qtubuntu builds too
[11:54] <tsdgeos> of course it doesn't run
[11:54] <tsdgeos> but it's something that didn'thappen before either
[11:54] <tsdgeos> greyback is working on that
[11:54] <tsdgeos> Saviq: we nede egl for mir afaik
[11:55] <greyback> it's odd, Qt installs the eglconvenience headers, but doesn't compile the code
[11:55] <greyback> hence the missing symbols
[11:55] <greyback> on desktop, I just copied the contents of eglconvenience.cpp into qtubuntu to get it to "work"
[11:55] <tsdgeos> so not sure where we want to go atm
[11:55] <tsdgeos> i can propose my patch to Qt
[11:56] <tsdgeos> but given we can't really proof it's of use to us at the moment is a bit of a problem :D
[11:56] <Saviq> and is it really something we want, in the long run...
[11:58] <dandrader> Saviq, I'm a bit confused by this branch path: lp:ubuntu/qtdeclarative-opensource-src. What path do I used when pushing my candidate branch? I normally do lp:~dandrader/{project-name}/{my-branch-name}. But that convention doesn't match with this guy...
[12:00] <Saviq> dandrader, yeah, that'd be: lp:~dandrader/ubuntu/trusty/qtdeclarative-opensource-src/foo
[12:00] <dandrader> wow
[12:01] <Saviq> dandrader, that means it's a branch directed at ubuntu trusty for project qtdeclarative-opensource-src
[12:01] <Saviq> dandrader, 'cause there isn't an "upstream" project for that in launchpad
[12:02] <Saviq> *for source package qtdeclarative-opensource-src
[12:02] <Saviq> I should say
[12:12] <dandrader> Saviq, ok. made the mp. Should I ping Timo Jyrinki to review it or he will eventually get to it?
[12:12] <Saviq> dandrader, ping him to make sure he knows :)
[12:28] <dandrader> tsdgeos, have you ever cross-compiled qt for arm?
[12:28] <tsdgeos> nope
[12:30] <tsdgeos> Saviq: about the exceptions thing lars is probably fixed after beta1
[12:30] <tsdgeos> still need to compile and test
[12:30] <Saviq> tsdgeos, ah awesome
[12:30] <tsdgeos> but it's good news
[12:31] <Saviq> tsdgeos, do we have a potential change id to distro patch?
[12:31] <tsdgeos> Saviq: can't we just update to rc1 that is going to be released *now-ish* ?
[12:31] <Saviq> tsdgeos, sure we can, as soon as *now-ish* is now ;)
[12:31] <tsdgeos> he he
[12:32] <Saviq> tsdgeos, didn't know it's just around the corner
[12:32] <tsdgeos> no i don't have the change id
[12:32] <Saviq> tsdgeos, i.e. unless there's a tarball, there's no real way we can update
[12:32] <tsdgeos> Saviq: yeah there's been a few mails to the qt-list saying "sorry we failed to release it again, we promise to do it asap", some integration stuff
[12:32] <tsdgeos> let me re-read it
[12:32] <Saviq> tsdgeos, ok
[12:33] <tsdgeos> "Unfortunately this all means we cannot release Qt 5.2 RC1 tomorrow. I am hoping we could do it later this week but it can be seen only after we manage to get packages with new content under testing."
[12:33] <tsdgeos> that yes yesterday
[12:33] <Saviq> ok, so hopefully this week
[12:33] <Saviq> seeing as we've UDS now, that's probably fine
[12:34] <Saviq> dandrader, which package in particular would you like to cross-build? I could check what's possible and what's not
[12:35] <dandrader> Saviq, qtdeclarative. but that's not a "must have". I was just googling qt cross-compilation yesterday and it seems that they have decent support for it, so it shouldn't be hard
[12:36] <Saviq> dandrader, yeah, except... we're multi-arch
[12:36] <Saviq> dandrader, which is not the same concept as a cross-build toolchain
[12:36] <dandrader> Saviq, but that means also cross-compiling qtbase, qtxmlpatterns and likely something else I forgot
[12:37] <Saviq> dandrader, but well, target (for this cycle) is to be able to just go "sbuild --host=armhf" to cross-build packages in a chroot
[12:38] <dandrader> Saviq, which makes me wonder how does our build machinery builds all those ubuntu arm packages?
[12:38] <dandrader> in a qemu chroot? (slow as hell)
[12:39] <Saviq> dandrader, no, we have an armfarm
[12:39] <Saviq> ;)
[12:40] <Saviq> dandrader, we've a (two or so) high density Calxeda arm boxes
[12:40] <Saviq> dandrader, and we're building natively on them
[12:40] <Saviq> dandrader, like 128 nodes in 10 units or so
[12:42] <dandrader> ah, cool
[12:42] <Saviq> dandrader, PPAs generally build virtualized, unless they're switched to nonvirt
[12:42] <Saviq> which they are for our projects
[13:22] <greyback> anyone else finding ports.ubuntu.com slow these days?
[13:59] <tsdgeos> uds!
[13:59] <Saviq> yup :)
[13:59] <Saviq> dandrader, one caveat: [13:59] <Saviq> dandrader, should not add that file
[14:01] <dandrader> dandrader, why? I noticed that this .pc is already full of stuff so I just added whatever quilt puts there
[14:02] <dandrader> Saviq, I actually don't know why do we have (or need) this .pc in the first place...
[14:02] <Saviq> dandrader, it's quilt's internals
[14:02] <Saviq> dandrader, id needs it for refreshing the patches etc.
[14:03] <Saviq> dandrader, OTOH you could just pop all the patches and let it handle them build-time
[14:04] <Saviq> dandrader, I've seen other packaging doing that, the difference is obviously that when you look through the code when branched, it's already applied in the branch, not only when you quilt push -a
[14:04] <Saviq> dandrader, I don't know if there's a guideline for/against either
[14:46] <nic-doffay> Saviq, mind taking a look at this? https://code.launchpad.net/~nicolas-doffay/unity8/category-transition-speed-fix/+merge/195203
[14:47] <Saviq> nic-doffay, not today, full-uds mode here
[14:48] <nic-doffay> Saviq, cool np
[14:48] <nic-doffay> tsdgeos, merged trunk so this should be good now: https://code.launchpad.net/~nicolas-doffay/unity8/search-history-persist/+merge/193935
[14:48] <Cimi> nic-doffay, Saviq I can have a look later maybe
[14:49] <nic-doffay> tsdgeos, if you wouldn't mind taking a look at this too https://code.launchpad.net/~nicolas-doffay/unity8/home-scope-app-search-fix/+merge/195791 it's a little related.
[14:49] <nic-doffay> Cimi, or maybe you if you're free for a review? ^
[14:49] <Saviq> Cimi, sure, if you do - make sure both of the cases I mentioned in the comment there are solved
[14:49] <Cimi> nic-doffay, I want to follow some sessions
[14:49] <Cimi> but bot as busy as Saviq
[14:50] <tsdgeos> nic-doffay: https://code.launchpad.net/~nicolas-doffay/unity8/search-history-persist/+merge/193935 looks good, let's wait for CI to approve and i'll top approve
[14:51] <tsdgeos> https://code.launchpad.net/~nicolas-doffay/unity8/home-scope-app-search-fix/+merge/195791 not sure it's correct as Saviq says
[14:51] <nic-doffay> tsdgeos, cool
[14:52] <nic-doffay> tsdgeos, I tried searching for apps and it appeared to work. I'm unsure if it's the correct approach though.
[14:52] <Saviq> nic-doffay, not on the phone you didn't
[14:53] <nic-doffay> Saviq, I didn't I assumed search for apps on the desktop would be enough?
[14:53] <Saviq> nic-doffay, it's not
[14:53] <nic-doffay> Saviq, right then. I'll get back to you about this after UDS.
[14:53] <Saviq> nic-doffay, it's not a bug we can solve, really
[14:54] <Saviq> nic-doffay, there's no scope backend doing that on the phone yet
[14:54] <nic-doffay> Saviq, add it to the task list? Or is it more complicated than that?
[14:54] <Saviq> nic-doffay, not us - we need a backend service to do that
[14:55] <nic-doffay> Saviq, k.
[16:02] <Saviq> mzanetti, greyback either of you going to "Responsive design"?
[16:03] <greyback> Saviq: dinner just been laid out, but will try
[16:04] <Saviq> greyback, no worries, enjoy
[16:06] <tsdgeos> Saviq: fwiw https://codereview.qt-project.org/#change,71717 and https://bugreports.qt-project.org/browse/QTBUG-34949
[16:07] <mzanetti> Saviq: Im there
[16:30] <tsdgeos> Saviq: Mirv: do we have a ticket for the unity-mir building problem shown at https://launchpadlibrarian.net/156909072/buildlog_ubuntu-trusty-amd64.unity-mir_1%3A0.1%2B14.04.20131028-0%2B201311190950~143~ubuntu14.04.1_FAILEDTOBUILD.txt.gz ?
[16:30] <Saviq> tsdgeos, https://bugs.launchpad.net/unity-mir/+bug/1246498
[16:31] <Saviq> tsdgeos, I just hijacked the same bug
[16:31] <tsdgeos> ah
[16:31] <tsdgeos> ok
[16:31] <Mirv> aha, thanks Saviq
[16:34] <tsdgeos> Mirv: Saviq: https://bugs.launchpad.net/qtubuntu/+bug/1246498/comments/2
[16:35] <Saviq> tsdgeos, so it's effectively moved to private?
[16:36] <tsdgeos> Saviq: it was private, moved to public and moved back during the cycle
[16:36] <tsdgeos> Saviq: we never were using it
[16:36] <tsdgeos> it's just that something was borked in the QtQml mega-header
[16:36] <tsdgeos> which we should not be using anyway
[16:36] <Saviq> tsdgeos, ah ok
[16:36]  * tsdgeos kills the use of the QtQml header
[16:37] <kgunn> tsdgeos: sounds like that was an enjoyable killing
[16:37] <tsdgeos> :-)
[16:38] <Mirv> tsdgeos: ok, the patch does not apply directly on top of qtdeclarative when added to the series file (two failures, probably small ones). then again rc1 should be out this week still (should have been today but was postponed)
[16:38] <tsdgeos> Mirv: yep, ignore it then
[16:45] <tsdgeos> Saviq: greyback: https://code.launchpad.net/~aacid/unity-mir/nomegaheader/+merge/195823
[16:46] <Saviq> tsdgeos, there's probably more places where that needs to happen?
[16:47] <tsdgeos> not in unity-mir
[16:47] <tsdgeos> i'll grep the rest of my checkouts
[16:48] <tsdgeos> but afair i did some of this cleanups a while ago
[16:55] <tsdgeos> Saviq: actually there's a few more, i'll create a few more merges
[16:55] <nic-doffay> tsdgeos, any idea if jenkins is slower than usual atm?
[16:55] <tsdgeos> nic-doffay: no, but i was wondering the same
[16:55] <Saviq> nic-doffay, queued up probably, yes
[16:56] <nic-doffay> Saviq, I'm assuming there's still some backlog?
[16:56] <Saviq> nic-doffay, yeah, and not all devices are back up yet
[16:57] <Saviq> there's only one x86 test runner http://s-jenkins.ubuntu-ci:8080/job/autopilot-testrunner-otto-trusty/
[17:02] <tsdgeos> Saviq: another one https://code.launchpad.net/~aacid/unity8/noQtQmlHeader/+merge/195825
[17:12] <Saviq> tsdgeos, and why not QQmlExtensionPlugin as in unity-mir?
[17:12] <tsdgeos> different needs
[17:12] <tsdgeos> different uses
[17:12] <tsdgeos> QtQml is include *.h
[17:12] <Saviq> tsdgeos, ok
[17:13] <Saviq> tsdgeos, unity8 did compile though, so maybe <QtQml> != <QtQml/QtQml>?
[17:14] <tsdgeos> Saviq: that's a good question, but afaics no, they're the same header
[17:14] <tsdgeos> i.e. in /usr/include/qt5 there's a single QtQml file
[17:14] <tsdgeos> and two folders
[17:14] <tsdgeos> so it can only be that file
[17:15] <Saviq> tsdgeos, wonder why unity8 did compile and unity-mir didn't
[17:15] <tsdgeos> yeah :-(
[17:15] <tsdgeos> still this is more optimal
[17:15] <tsdgeos> gives us faster compiling
[17:15] <Saviq> sure
[17:15] <tsdgeos> including QtQml includes all of QtCore all of QtNetwork and all of QtQml
[17:15] <tsdgeos> D:
[17:26] <Mirv> Saviq: if you didn't yet, you may want to check the list of topics in today's Qt session like the qreal == double, use of private headers
[17:28]  * sil2100 has no other way than using private headers
[17:30] <Mirv> sil2100: private headers that are needed by other modules are "fine", eg. I believe qtbase5-private-dev will still be there.
[17:48] <Saviq> Mirv, yeah, will do
[18:20] <om26er> Can I run qmltestrunner directly on the phone ?
[18:20] <om26er> mzanetti, ^
[18:20] <om26er> there are integration tests on for QtMultmedia that I would like to run on the phone but I get:
[18:20] <om26er> QUbuntu: Could not create application instance
[18:20] <om26er> Aborted (core dumped)
[18:33] <mzanetti> om26er: yes, you can
[18:34] <om26er> mzanetti, I get that error. it works fine with SF
[18:34] <mzanetti> om26er: you need to pass --desktop_file_hint=... tho
[18:34] <om26er> mzanetti, for anything random ?
[18:34] <mzanetti> yeah.
[18:35] <mzanetti> greyback: do you think we could allow running stuff withouth it and just group them as "unknown application" or something?
[18:35] <mzanetti> greyback: having to pass that uber long argument to *everything* is quite annoying indeed
[18:37] <greyback> mzanetti: would be do-able, but I was told to be strict and not allow that
[18:37] <mzanetti> mhm... too bad
[18:37] <mzanetti> this is really annoying for running tests and doing app development
[18:38] <greyback> mzanetti: +1 on needing some app launch that's better than --desktop_file_hint=...
[18:38] <mzanetti> yes
[18:40] <om26er> mzanetti, greyback for this specific case tests are run through a python script so we can't really give that cmd arguments. and I would really not want to change the QtMultimedia and just run its tests directly.
[18:41] <mzanetti> yeah... I agree
[18:41] <mzanetti> greyback: who told you to be super strict
[18:41] <mzanetti> ?
[18:41] <greyback> mzanetti: mostly Saviq
[18:41] <mzanetti> ok
[18:42] <mzanetti> om26er: I'll have a chat with him to see if we can relax that policy a bit
[18:42] <om26er> mzanetti, ack, thanks
[19:15] <sil2100> Saviq: ping
[19:15] <Saviq> sil2100, pong
[19:15] <sil2100> Saviq: can you join the Qt session?