[02:19] <prompt32> highvoltage, does anyone knows if there is a way to run macchanger on my wlan0 interface, before wlan0 is up ?
[02:21] <sarnold> prompt32: you'll probably have better success in #ubuntu
[02:23] <prompt32> sarnold, i'll try, thanks
[05:36] <Mirv> didrocks: morning! it seems doko's attempt at increasing the amount of multi-arch in Qt (https://lists.ubuntu.com/archives/saucy-changes/2013-August/007559.html) is breaking builds
[05:36] <Mirv> for example https://launchpadlibrarian.net/147043226/buildlog_ubuntu-saucy-i386.ubuntu-ui-toolkit_0.1.46%2B13.10.20130808-0ubuntu1_FAILEDTOBUILD.txt.gz
[05:36] <Mirv> so I think revert would be needed
[05:37] <didrocks> Mirv: hey! this is not just an arch mismatch?
[05:37] <didrocks> (I just overlook, if you think we should revert, let's revert)
[05:37] <Mirv> didrocks: I don't exactly understand what's getting broken in there, can you?
[05:38] <Mirv> but it seems something got broken, whatever way it did
[05:38] <Mirv> and same for qtubuntu-camera https://launchpadlibrarian.net/147043988/buildlog_ubuntu-saucy-armhf.qtubuntu-camera_0.3.3%2B13.10.20130808-0ubuntu1_FAILEDTOBUILD.txt.gz
[05:39] <Mirv> the bug he's trying to address is https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1209239
[05:39] <ubot2`> Ubuntu bug 1209239 in qtchooser (Ubuntu) "MultiArch support for QT5 is insufficient for cross building" [Undecided,Confirmed]
[05:40] <didrocks> Mirv: hum, did you try to upgrade/install like qt5-qmake locally?
[05:40] <Mirv> it reads there "dependencies on qtbase5-dev-tools and qt5-qmake must have an :any suffix."
[05:40] <Mirv> didrocks: everything did update correctly this morning for me, so maybe it's those build-depends (on all packages)?
[05:41] <Mirv> it's a bit invasive change, even if it'd be correct technically
[05:42] <didrocks> hum
[05:43] <didrocks> Mirv: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[05:43] <didrocks> we can refind the same issue in what is blocking Qt5 in proposed
[05:44] <Mirv> ah, qtbase was uploaded as well
[05:44] <didrocks> this issue is clearly:
[05:44] <didrocks> qt5-default/i386 unsatisfiable Depends: qtchooser:any
[05:44]  * didrocks wonders why
[05:44] <didrocks> and then, all the cascades is because of that
[05:48] <didrocks> grrr, I don't understand
[05:52] <Mirv> yeah proposed qtbase update gives the error http://pastebin.ubuntu.com/5961461/
[05:52] <Mirv> goes above me as well
[05:53] <didrocks> so, why :any?
[05:53] <didrocks> -         qt5-qmake (= ${binary:Version}),
[05:53] <didrocks> -         qtbase5-dev-tools (= ${binary:Version}),
[05:53] <didrocks> -         qtchooser,
[05:53] <didrocks> +         qt5-qmake:any (= ${binary:Version}),
[05:53] <Mirv> downgrading qtchooser to 26-3ubuntu1 does not allow qtbase upgrade either
[05:53] <didrocks> +         qtbase5-dev-tools:any (= ${binary:Version}),
[05:53] <didrocks> +         qtchooser:any,
[05:53] <didrocks> argh
[05:54] <didrocks> but this is invalid…
[05:54] <didrocks> Mirv: yeah, the issue is in qt5
[05:54] <didrocks> Mirv: not sure what he wanted to do with :any
[05:54] <didrocks> let me remove that
[05:54] <didrocks> Mirv: was his change committed to any vcs?
[05:54] <Mirv> ok
[05:54] <Mirv> let me see
[05:54] <didrocks> or should I just apt-get source + upload?
[05:55] <Mirv> didrocks: no, does not seem to be in ubuntu branches nor in ~kubuntu-packagers
[05:56] <didrocks> Mirv: ok, let's do 2 things
[05:56] <didrocks> Mirv: for unblocking, I'm going to remove the dep on -proposed, ok?
[05:56] <didrocks> (build-dep)
[05:56] <didrocks> so that you can restart building everything
[05:56] <Mirv> didrocks: ok.
[05:56] <didrocks> and relaunching the stacks with foo
[05:56] <didrocks> just after that, I'm going to upload the fix for Qt
[05:58] <didrocks> Mirv: ok, please relaunch the builds
[05:58] <didrocks> Mirv: proposed disabled in the tests as well
[05:59]  * didrocks now goes to fix Qt5
[05:59] <Mirv> didrocks: ok
[06:00] <cyphermox> hey didrocks
[06:00] <didrocks> Mirv: then, do you want me or you to send an email to the ML?
[06:00] <didrocks> hey cyphermox
[06:05] <didrocks> Mirv: revert uploaded
[06:05] <didrocks> (not a full revert, just the :any thing)
[06:05] <Mirv> didrocks: I can, although which ML?
[06:05] <cyphermox> chrisccoulson: hey, you having issues with your funky bluetooth hid2hci keyboard thing on saucy?
[06:05] <didrocks> Mirv: the phone one
[06:05] <Mirv> ok, will do
[06:05] <cyphermox> chrisccoulson: seems to me like you should, the bluez udev rule looks to me like it should be just failing
[06:05] <didrocks> Mirv: just tell that dailies will be really delayed as we disabled proposed, but rebuild everything
[06:06] <didrocks> Mirv: we'll ask for an iso resping
[06:06] <didrocks> (do not hesitate to link to the 2 qt version, the faulty one and the fixed one ;))
[06:06] <didrocks> thanks Mirv!
[06:12] <didrocks> Mirv: does this looks good to you? https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dHFtUmlPOUtCRk8zR2dtaEpIbUVhMmc#gid=3
[06:15] <Mirv> didrocks: looks excellent, I think that has been longed for a lot
[06:16] <didrocks> Mirv: yeah, until we have an automatic dashboard, it's a good workaround :)
[06:16] <didrocks> Mirv: so, filing this in now? maybe let's wait from the rebuild without -proposed first
[06:16] <didrocks> Mirv: you are relaunching all stacks failing with "foo" (one you restarted the build)?
[06:16] <didrocks> can I help?
[06:18] <Mirv> didrocks: added tentative date until which osomon will be contacted instead of bfiller, based on yesterday's note that Bill is on holiday for "two weeks" (not sure which two weeks, but probably this and next)
[06:19] <Mirv> didrocks: filling in, yes, and relaunching the failed stacks - so far only media and sdk and now filling in the chart
[06:20] <didrocks> Mirv: yeah, I guess this one and next :)
[06:21] <didrocks> Mirv: just tell me if I can be of any help
[06:21] <Mirv> didrocks: open my head and grab some things from there :)
[06:21] <didrocks> ahah, that's part of the issue ;)
[06:22] <Mirv> didrocks: any idea how that thing that hit seb128 is now for unity? https://launchpadlibrarian.net/147049488/buildlog_ubuntu-saucy-armhf.unity_7.1.0%2B13.10.20130808-0ubuntu1_FAILEDTOBUILD.txt.gz /system/lib/libGLESv2.so' not found
[06:23] <Mirv> didrocks: I'm opening the 'head' job and clicking build now instead of the 'foo' method, which I thought would only run tests and not rebuild the pacakges
[06:23] <didrocks> Mirv: hum, previous qtbase brought hybris on the base image
[06:23] <didrocks> Mirv: it will force rebuilding the packages
[06:24] <Mirv> didrocks: and that's what failed, building the packages?
[06:24] <didrocks> as it's what intended by that
[06:24] <Mirv> ah, foo does that, if they haven't built?
[06:24] <didrocks> ok, basically, if you don't do anything, the build will:
[06:24] <didrocks> - scratch the current workspace
[06:24] <didrocks> - redownload everything
[06:24] <didrocks> - see if anything isn't in distro
[06:24] <didrocks> - build from that
[06:25] <didrocks> if you file "BUILD_ONLY"
[06:25] <didrocks> - it won't scratch the current workspace for that stack
[06:25] <didrocks> - it will remove all the components that match BUILD_ONLY list
[06:25] <didrocks> - and so, only compare if anything new available and upload that
[06:25] <didrocks> the whole stack is tested in both cases
[06:25] <didrocks> making sense?
[06:26] <didrocks> if you rebuild the whole stack, not a biggie anyway
[06:26] <didrocks> (just some CPU cycles lost ;))
[06:27] <didrocks> (doing apps)
[06:28] <Mirv> REBUILD_ONLY, you mean? yeah, it seemed to me that eg. in media the only package that had changes was also the only package that failed, so just plain 'build' seemed like doing the right thing except for of course the CPU cycles checking statuses :)
[06:28] <Mirv> didrocks: commenting out not working for -proposed: http://10.97.0.1:8080/job/autopilot-saucy-daily_release/814/label=autopilot-intel/console
[06:29] <Mirv> for tests
[06:29] <didrocks> Mirv: so plain rebuild is fine in that case, yeah ;)
[06:29] <didrocks> Mirv: oh, sorry, ok, let me remove the file one sec
[06:29] <didrocks> Mirv: done
[06:30] <didrocks> Mirv: in that case, for sdk, you can just use "foo" for REBUILD_ONLY, sdk doesn't need to be rebuild now, we're just interested in testing
[06:30]  * didrocks relaunches media with "foo"
[06:31] <Mirv> ok, thanks
[06:31] <didrocks> you're doing it for sdk?
[06:31] <Mirv> yes
[06:31] <Mirv> running
[06:31] <didrocks> rebuilding unity-webapps-qml for webapp
[06:32] <didrocks> ok, now, let's wait for the result and update the spreadsheet
[06:44] <Mirv> I'd hope someone at google would add the links possibility for pieces of text inside a field
[06:46] <didrocks> Mirv: you mean, like ellipsis and when you click on it, it expands?
[06:47] <Mirv> didrocks: I mean, if I've an URL in a field and other text, the URL would still act as a link
[06:47] <didrocks> oh right, sometimes it works, sometimes not
[06:47] <didrocks> I never understood the pattern
[06:47] <Mirv> oh it works sometimes? then there should be some trick. I know something worked at one point when I copy-pasted from elsewhere
[06:47] <didrocks> yeah, sometimes, it's recognized as a link
[06:48] <didrocks> that's really weird…
[06:48] <Mirv> I tried it now but it didn't help, ie. having clipboard content with html
[06:48] <Mirv> =hyperlink()
[06:49] <Mirv> or something.. trying
[06:50] <Mirv> ah, that's probably also something that only works alone
[06:52] <didrocks> right
[06:54] <Mirv> didrocks: should media be now able to publish itself automatically, as it depended (and halted) on SDK which now published successfully?
[06:55] <didrocks> Mirv: hum, interesting, maybe both were published at the same time?
[06:55] <didrocks> Mirv: let me fake SDK publishing
[06:55] <didrocks> Mirv: ah, it's because we build SDK after media
[06:56] <didrocks> Mirv: so for safety, there is no automatic publishing (like if there is an ABI break)
[06:56] <didrocks> not an issue with the sdk as it's a runtime dep
[06:56] <didrocks> and there is nothing in the pipe breaking, right?
[06:58] <Mirv> no
[06:59] <didrocks> ok, so let me fake a publish on sdk
[06:59] <didrocks> you will see that then media is running
[06:59] <Mirv> and just curious, since I noted that media had halted 20 mins ago because sdk failed to publish, and then 10 minutes ago sdk published successfully
[07:00] <didrocks> Mirv: right, so sdk was built after media
[07:00] <Mirv> yep, now it published media
[07:00] <didrocks> yeah:
[07:00] <didrocks> 2013-08-08 06:59:36,179 INFO Considering publishing: media (head)
[07:00] <didrocks> 2013-08-08 06:59:36,190 INFO media (head) may be publishable, trying it
[07:00] <didrocks> Mirv: basically, it's a safety net
[07:00] <didrocks> like imagine, you have indicators in manual publication because of HUD
[07:00] <Mirv> which is good
[07:01] <didrocks> then, you *rebuild* (not just publish) HUD
[07:01] <didrocks> maybe HUD has an ABI break
[07:01] <didrocks> and so if we publish HUD and indicators, things will go ugly :)
[07:02] <didrocks> so the automated publication is only rolled out if no rebuild was involved in the stack declenching the others
[07:02] <didrocks> sorry, not sure I'm clear…
[07:05] <Mirv> yes, makes sense
[07:10] <jibel> good morning
[07:10] <Mirv> didrocks: during the night there had been yet another packaging request from mhall119, added to the sheet. not really sure about anything else but the url (poppler-qml-plugin), but I assume it'd be wanted to saucy and sdk meta package
[07:10] <didrocks> salut jibel
[07:10] <didrocks> Mirv: right, sdk stack sounds good to you?
[07:11] <Mirv> didrocks: yes, I'm just not sure what has happened some of the other community apps sources, ie are they wanted in daily release or separately
[07:11] <Mirv> and has it been some other team uploading those
[07:11] <didrocks> I think for the apps, they are click packaging
[07:11] <didrocks> so not really in distro
[07:11] <Mirv> ah, right
[07:11] <didrocks> for the bindings, we are handling those
[07:12] <didrocks> (I can be fully wrong ;))
[07:12] <Mirv> so then I remember at least one file manager related QML plugin, I'd need to check where that is flying around
[07:12] <Mirv> but yes they should go to the saucy, if they're wanted to be part of the supported platform
[07:15] <didrocks> right
[07:15] <jibel> salut didrocks
[07:16] <didrocks> Mirv: waow, apps passed the tests!
[07:17] <didrocks> Mirv: I think there is nothing blocking on webapps, do you think we should publish it? (force the publication?)
[07:18] <jibel> didrocks, is there any stack left to release after phone and settings? I'd need to restart jenkins to increase the number of slots. It has not been done during the night.
[07:18] <didrocks> jibel: I think it will be fine, right Mirv? ^
[07:20] <didrocks> jibel: noooo
[07:20] <didrocks> jibel: if you do that publisher and so on won't work
[07:20] <didrocks> as it's a new job
[07:20]  * didrocks cancels
[07:21] <jibel> I canceled
[07:21] <Mirv> I don't have anything special ongoing there now
[07:22] <Mirv> didrocks: despite the webapps-qml failing tests?
[07:22] <Mirv> didrocks: I do know they assume it's a jenkins / test environment issue
[07:22] <didrocks> Mirv: yeah, I looked the commits since last release, the changes seems unrelated
[07:22] <Mirv> if that's fine, then yes would be great
[07:22] <didrocks> Mirv: just to be clear: I won't publish webapps-qml
[07:23] <didrocks> (the webapps stack)
[07:23] <didrocks> just the apps stack
[07:24] <Mirv> didrocks: yeah, I noticed you wrote that apps passed tests and then asked about publishing webapps, so I was unsure what you meant
[07:24] <didrocks> Mirv: yeah, the "it" was apps, not webapps, sorry ;)
[07:24] <Mirv> funny that gallery-app passed now
[07:25] <Mirv> well, Günter had made one commit
[07:25] <didrocks> yeah
[07:25] <didrocks> it was for that :)
[07:25] <didrocks> Mirv: ok, do you mind refreshing the status for all stack (but phone, as we are waiting for it), now?
[07:25] <didrocks> ah phone done!
[07:25] <didrocks> jibel: you can restart as soon as Mirv finishes to note the status
[07:26] <jibel> didrocks, k, I found another interesting hobby
[07:27] <Mirv> didrocks: ok
[07:29] <Mirv> didrocks: ok all seems at pause and stack status page up-to-date
[07:30] <didrocks> Mirv: \o/
[07:30] <didrocks> big thanks
[07:30] <didrocks> jibel: restartttttttt ^
[07:30] <didrocks> Mirv: oh, you should maybe mention the click package issue
[07:30] <didrocks> in the "not blocking release"
[07:31] <didrocks> the last commit wasn't merged?
[07:31] <Mirv> didrocks: yeah I was just about to ask about the click packages
[07:31] <Mirv> since I haven't glanced at it before
[07:32] <didrocks> "A version (0.1+13.10.20130808-0ubuntu1) is available at the destination for that component but is not in trunk which is still at 0.1+13.10.20130727-0ubuntu1. Ignoring that component for source: unity-scope-click, branch: lp:unity-scope-click, series: saucy.
[07:32] <Mirv> didrocks: ok marked it down for now, yes it seems
[07:32] <didrocks> "
[07:32] <Mirv> didrocks: I've been now trying to write this to you for 10 minutes but I'd need some review/thoughts on      lp:~timo-jyrinki/+junk/qtcreator-plugin-ubuntu-common
[07:32] <didrocks> Mirv: mention that latest MP isn't merged apparently
[07:32] <Mirv> :)
[07:32] <didrocks> Mirv: ahah, ok, let me give RAOF the ATI machine for testing Mir
[07:32] <didrocks> and then, I'm on it, ok?
[07:33] <Mirv> we tested and released Qt Creator update for precise, quantal and raring, and saucy archive upload would depend on getting the -common package in first
[07:33] <Mirv> didrocks: that's fine :)
[07:33] <didrocks> excellent!
[07:33] <didrocks> did we settled on having the source as qtcreator-plugin-ubuntu thought?
[07:33] <didrocks> or this is just the branch name being wrong?
[07:33] <Mirv> zoltan still hesitated on renaming the source without -common, but I can change that for saucy
[07:34] <didrocks> Mirv: yeah, please do, I think it makes sense to prepare for the future
[07:34] <Mirv> yeah, changing that
[07:34] <Mirv> at least we got rid of the -data binary packages now
[07:35] <didrocks> sweet!
[07:35] <didrocks> jibel: Mirv: I'm blocking the ati machine right now to have RAOF debugging Mir
[07:36] <Mirv> and now I go see about thomi's qtbase patch
[07:36] <Mirv> oh, or.. maybe a coffee break, to keep sanity which is usually beneficial
[07:38] <didrocks> heh ;)
[07:38] <didrocks> Mirv: enjoy!
[07:38] <didrocks> proposed reenabled FYI on both test machine and builders
[07:40] <jibel> didrocks, jenkins is bakc
[07:40] <jibel> back
[07:40] <didrocks> thanks jibel
[07:41] <seb128> good morning desktopers
[07:41] <jibel> didrocks, with 50 excutors on master which should be enough to trigger all the stacks, if it is not I'll increase it a bit more
[07:41] <jibel> I guess the side effect is only memory consumption
[07:41] <jibel> Salut seb128
[07:42] <seb128> lut jibel didrocks
[07:44] <didrocks> salut seb128!
[07:44] <didrocks> jibel: yeah, let's see how it goes
[07:45] <seb128> didrocks, Mirv: I've read the backlog on irclogs.u.c, I'm looking at the unity issue
[07:45] <didrocks> seb128: I think it's the same than the settings one
[07:45] <didrocks> seb128: FYI, I disabled proposed
[07:45] <seb128> didrocks, I guess some other packages got the libhybris shlibs depends by rebuilding with the broken mir yesterday
[07:46] <didrocks> during those builds
[07:46] <seb128> didrocks, no, it's not, unity7 doesn't build-depends on qt
[07:46] <didrocks> yeah, it's not the Qt issue for sure
[07:46] <didrocks> seb128: thanks for investigating, I'm already under the water :)
[07:53] <Mirv> seb128: yes, same error there, thank you for looking at i
[07:54] <Mirv> t
[07:57] <seb128> didrocks, Mirv: I'm not convinced that the "rebuild without proposed" is a good thing
[07:57] <didrocks> seb128: was the only way to get the thing unblocked timely
[07:57] <didrocks> seb128: see my followup email, it's enabled again
[07:57] <seb128> that's going to bring in your build the qtbase which depends on libhybris
[07:57] <seb128> and you might get extra libhybris depends through shlibs
[07:57] <seb128> we are never going to get out of it if we do that
[07:58] <didrocks> we can then do a new build today (with the new daemon)
[07:58] <didrocks> even forcing some if needed
[07:58] <seb128> I hope it's not going to add libhybris depends to extra components make things harder to untangle
[07:58] <didrocks> let's see, the set of components are quite limited
[07:58] <didrocks> so it's easy to look at them
[07:58] <seb128> ok
[07:59] <didrocks> I didn't want to again block everything for 5 hours for Qt
[07:59] <didrocks> especially as upstream is pressuring to get some stuff released
[07:59] <seb128> well, blocking is better than creating extra chaos which is going to take a week to sort out
[07:59] <seb128> but let's see
[07:59] <didrocks> seb128: I don't have time to argue on this. I agree, but then, it's not you taking the backfire :)
[07:59] <didrocks> see the discussions from yesterday when they want to publish even if tests fail…
[08:00] <seb128> well, you are going to take double backfire when hybris screw us for the next days
[08:01] <seb128> didrocks, shrug, the new https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/4859696/+files/qtdeclarative5-ubuntu-ui-toolkit-plugin_0.1.46%2B13.10.20130808.1-0ubuntu1_armhf.deb won a depends on libhybris
[08:01] <seb128> that's what I though
[08:01] <seb128> didrocks, we are putting ourselve down in a hole there :/
[08:02] <didrocks> seb128: you're welcome to retrigger a rebuild once my qtbase is built
[08:02] <didrocks> if only people were testing before uploading… Not having qt installable is a shame
[08:02] <seb128> it's going to play whack a mole to rebuild things in right order
[08:02] <seb128> right, I agree with that
[08:03] <didrocks> seb128: quite easy, let's wait for things being in the release pocket
[08:03] <didrocks> then, we can do an apt-cache rdepends
[08:04] <didrocks> and rebuild what's needed
[08:04] <didrocks> (even if there is no new commit)
[08:04] <seb128> ok
[08:04] <seb128> that's going to take some 6 hours
[08:04] <seb128> let's see this afternoon
[08:04] <didrocks> well, qtbase to build will take that time anyway :p
[08:04] <seb128> right, that's what I was saying
[08:04] <seb128> 6 hours of build + 1 publish cycle
[08:05] <didrocks> yep
[08:05] <didrocks> we're fine, because what's depending on those components are already in dailies
[08:05] <didrocks> so under our control to rebuild
[08:06] <didrocks> and we already had powerd and other stuff depending on it, for maybe no good reason
[08:06] <didrocks> so, it's time to clean that up
[08:11] <didrocks> seb128: but that doesn't explain the unity issue, right?
[08:13] <seb128> didrocks, no, I'm debugging that one next, that's why landing/rebuilding more stuff is making me nervous, new things get the depends
[08:14] <seb128> didrocks, powerd&co might be actually be using it to access android features
[08:14] <didrocks> seb128: yeah, I propose we make a list once everything is published in the release pocket
[08:15] <didrocks> and go one by one
[08:15] <didrocks> I see others which shouldn't already
[08:15] <didrocks> so let's take that as an opportunity to clean things up
[08:29] <seb128> Mirv, didrocks: the unity issue is because the compiz rebuild from xnox on monday caught the libhybris depends
[08:29] <seb128> we need to rebuild compiz
[08:32] <xnox> seb128: the rebuild was ages ago, but i guess armhf was stuck FTBFS whilst compiler was getting fixed.....
[08:33] <seb128> xnox, it got published on monday
[08:36] <xnox> yeah: amd64/i386/powerpc build on 2013-07-01|02 whilst armhf finally built on 2013-08-05.
[08:52] <xnox> seb128: locally on armhf I still see that libhybris-common1 is still installed. Is that ok?
[08:53] <seb128> xnox, yes, the -common is fine, it's libhybris itself that divers libelg
[08:54] <xnox> seb128: ok, uploaded a no change rebuild. As far as I remember compiz daily release was stuck, although i guess it would now need manual packaging merge from myself.
[08:55] <xnox> (the version number bumps at least)
[08:55] <xnox> Right so the "update-alternatives: using /usr/lib/arm-linux-gnueabihf/libhybris-egl/ld.so.conf to provide /etc/ld.so.conf.d/arm-linux-gnueabihf_EGL.conf (arm-linux-gnueabihf_egl_conf) in auto mode" is what we don't want =)
[08:55] <xnox> hopefully the new calxeda nodes should build compiz quickly =)
[08:57] <seb128> xnox, sorry, I just beat you at that no change rebuild I think :p
[08:57] <xnox> seb128: narf =)
[08:57] <xnox> seb128: bets on how long it will take to build?
[08:58] <seb128> xnox, qtbase took 2 hours instead of 6 before
[08:59] <xnox> firefox from 20h40 down to 5h40
[09:01] <seb128> ogra_, see, it happened :p
[09:03] <robru> didrocks, what's the deal with qmenumodel? I see it being daily released but it doesn't seem to be in distro yet?
[09:04] <ogra_> seb128, heh, yeah
[09:05] <robru> didrocks, nm, got confused by differeing source/binary package names
[09:31] <seb128> xnox, compiz build down to 37 min (from 1h35 on previous build)
[09:32] <xnox> \o/
[09:39] <Mirv> those speedups are awesome
[09:40] <Mirv> I wonder what qtwebkit will be
[10:03] <didrocks> Mirv: I relaunched what was depending on the wrong qtbase version
[10:03] <didrocks> Mirv: relaunched as well unity as per new compiz ^
[10:18] <Mirv> ok
[10:58] <seb128> Mirv, you should be able to retry unity build, compiz is in saucy
[10:59] <Mirv> seb128: ok, the previous one started 50 minutes ago will still result in armhf failure?
[11:00] <seb128> Mirv, let me check
[11:00] <Mirv> seb128: it seems to have just finished successfully https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/4860368
[11:00] <seb128> Mirv, great, it just start at the right time
[11:01] <seb128> started
[11:01] <Mirv> 13:03 < didrocks> Mirv: relaunched as well unity as per new compiz ^
[11:01] <Mirv> well it was the grand master who selected the timing
[11:01] <seb128> haha
[11:01] <seb128> subject: [ubuntu/saucy] compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu3
[11:01] <seb128> 	(Accepted)
[11:02] <seb128> Date: Thu, 08 Aug 2013 10:07:08 -0000
[11:02] <seb128> so timing was just right it seems
[11:02] <seb128> or didrocks was pulling on rmadison to see if compiz was in to push the button :p
[11:02] <didrocks> seb128: rmadison is my ennemy, I just checked at the right time I guess :)
[11:03] <seb128> ;-)
[11:03] <Mirv> but the ati tests failed a bit, so tests will need to be rerun
[11:03] <tsdgeos> seems you guys updated to poppler-0.24 in saucy, cool :-)
[11:04] <seb128> tsdgeos, yes, since we wanted the qt5 bindings ;-)
[11:04] <seb128> tsdgeos, and it's good to be on the current version
[11:05] <seb128> well, "current stable version" rather
[11:06] <tsdgeos> now i only need to convince you to link it against openjpeg and the hell will freeze :D
[11:06] <seb128> haha
[11:06] <seb128> that's doko/MIR team that needs to be convinced, but yeah, that would be nice
[11:07] <tsdgeos> tried that
[11:08] <tsdgeos> afair the security team blocked on the fact that openjpeg had more CVE than that jpeg2000 library noone uses and noone develops that we ship
[11:08] <tsdgeos> jasper
[11:08] <tsdgeos> that one
[11:08] <seb128> I don't think they block it on because it more or less than the other one
[11:09] <seb128> but the fact that it has a record of having security issues is a problem for them, since they have to support it
[11:09] <seb128> tsdgeos, I'm going to have a look at updating to 1.5
[11:09] <seb128> then when we can try asking the security guys again
[11:09] <tsdgeos> well, jasper does not have security issues because noone looks inot it :D
[11:09] <tsdgeos> seb128: but i have to agree openjpeg is less than stellar too
[11:10] <tsdgeos> i think poppler regressed with some of the 1.x randomly
[11:11] <seb128> ha, they have a 2.0 out for some time
[11:11] <tsdgeos> yeo
[11:12] <tsdgeos> that's api incompatible though afair
[11:12] <seb128> fedora is still on 1.5 it seems, I wonder if that's for a reason or if they just didn't get to do the update yet
[11:12] <tsdgeos> https://bugs.freedesktop.org/show_bug.cgi?id=58906
[11:12] <ubot2`> Freedesktop bug 58906 in general "0.22.0 does not find openjpeg-2.0.0" [Normal,New]
[11:13] <seb128> ok
[11:13] <seb128> better to go for 1.5 rather then
[11:13] <seb128> that's what fedora/debian experimental have
[12:07] <Mirv> ok, it seems sdk and settings are already rebuilding after the new qt got published
[12:07] <didrocks> Mirv: I ran them by hand
[12:08] <didrocks> Mirv: then, unfortunately, unity tests are not finished yet
[12:08] <didrocks> so we'll wait for the tests to finish
[12:08] <Mirv> yes, it'll take some time
[12:08] <Mirv> more autopilot machines wouldn't hurt
[12:10] <didrocks> ok, qtbase in the release pocket
[12:18] <didrocks> and no more libhybris in qtdeclarative5-ubuntu-ui-toolkit-plugin_0.1.46+13.10.20130808.2-0ubuntu1_armhf.deb \o/
[12:25] <seb128> didrocks, great!
[12:30] <didrocks> now, waiting on unity test to finish, I rebuilt manually all the rest in ppa, so just waiting for the tests
[12:46] <didrocks> robru: in addition to the new package, can you work on the webapps AP tests failure with upstream?
[12:46] <didrocks> as you can see on https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dHFtUmlPOUtCRk8zR2dtaEpIbUVhMmc#gid=3, there is a link
[12:46] <didrocks> it's blocking for quite few days
[12:47] <robru> didrocks, yeah, I pinged vrruiz about that already and he says he's been working on it. I think the problem is that it's alex's bug, but he's on vacation, so victor is struggling with incomplete info.
[12:47] <didrocks> robru: any ETA? Can you escalate that to Pat?
[12:48] <didrocks> robru: he asked to know everything when we are blocked (and he's the contact in the spreadsheet)
[12:48] <robru> didrocks, no idea. I can escalate if you want.
[12:48] <didrocks> robru: please do :)
[12:49] <didrocks> thanks!
[12:49] <robru> didrocks, you're talking about pat mcgowan, right?
[12:49] <didrocks> right
[12:49] <didrocks> (he isn't online yet apparently)
[12:49] <didrocks> robru: are the packages fixed? at least the cu2d part?
[12:49] <robru> didrocks, ok, I just pushed updated packages: lines for that MP. can you check that it is the way you want it?
[12:49] <didrocks> robru: as we are going to redeploy everything to add the new machine, would be nice to have the right config :)
[12:49] <didrocks> ok
[12:50] <didrocks> https://code.launchpad.net/~robru/cupstream2distro-config/qtdbus-in-qa/+merge/179159 right?
[12:51] <didrocks> robru: approved
[12:51] <robru> didrocks, sweeeeeete
[12:51] <robru> didrocks, should I redeploy or are you doing that?
[12:52] <didrocks> robru: jibel has to redeploy for the machines, so don't worry :)
[12:52] <didrocks> robru: I'm pulling on lillypilly as well
[12:52] <didrocks> for refreshing the whitelist
[12:53] <robru> ok
[12:54] <didrocks> robru: I'll let the first review on ubuntu-settings-components for cyphermox
[12:54] <robru> didrocks, ok
[12:56] <robru> didrocks, I'm leaving for prague in a few hours, anything you need done ASAP?
[12:57] <didrocks> robru: no, just ping pat today please :)
[12:57] <robru> right
[12:57] <didrocks> are you blocked on anything else?
[12:57] <didrocks> or workless? ;)
[12:57] <robru> gotta find a hotel with AC and then I'll be much more productive ;-)
[12:57] <didrocks> heh, that will help, indeed!
[12:57] <robru> didrocks, no, not workless. some branches are just waiting for review.
[12:57] <didrocks> 23 here today, that helps :)
[12:57] <didrocks> ok
[12:57] <robru> 37 today ;-)
[12:58] <didrocks> enjoy the plane/train AC if any :p
[13:00] <cyphermox> didrocks: robru: ok, I'll get to it in a minute, just finishing up testing something for libcolumbus
[13:01] <cyphermox> robru: if you could link me, that would be awesome. I'll looking at more than one computer at a time
[13:12] <Mirv> didrocks: unity tests failed once more, but I wouldn't retry them before all others have finished
[13:13] <Mirv> didrocks: earlier this week it was the third autopilot run that got acceptable results for unity7
[13:15] <didrocks> Mirv: can you ping upstream? maybe they would have an idea on what's wrong
[13:15] <Mirv> didrocks: ok, let's see if they could address any of the issues
[13:24] <didrocks> seb128: mind looking at the settings packaging changes?
[13:25] <didrocks> seb128: I didn't follow fully the -online ones
[13:25] <seb128> didrocks, looking
[13:25] <didrocks> thx
[13:27] <seb128> didrocks, the libs are not properly multiarched (e.g no fields in debian/control), but let's not block on that, online account is broken for some days and we need to fix it
[13:27] <seb128> didrocks, +1
[13:27] <seb128> didrocks, do you want me to publish?
[13:27] <didrocks> seb128: yes plese :)
[13:30] <seb128> didrocks, done
[13:31] <seb128> kenvandine, ^
[13:31] <kenvandine> hey
[13:31] <robru> cyphermox, https://code.launchpad.net/~robru/ubuntu-settings-components/packaging
[13:31] <seb128> kenvandine, hey
[13:31] <seb128> kenvandine, we finally got settings published ;-)
[13:31] <kenvandine> woot!
[13:32] <seb128> kenvandine, please make the new lib in online account use multi-arch infos/pre-depends on multiarch-support/dpkg
[13:32] <kenvandine> ah, sure ;)
[13:33] <didrocks> seb128: \o/
[13:33] <didrocks> only apps
[13:33] <didrocks> and we'll be fine
[13:34] <Mirv> didrocks: should we force unity release if we get stephen to ack the latest failed tests from the autopilot run?
[13:35] <didrocks> Mirv: what would it give compared to tomorrow?
[13:35] <didrocks> Mirv: the number of tests are quite high to force a release TBH
[13:35] <didrocks> we should get upstream fixing their tests rather than workaround
[13:37] <kenvandine> https://code.launchpad.net/~ken-vandine/ubuntu-system-settings-online-accounts/multiarch
[13:37] <kenvandine> seb128, ^^
[13:37] <kenvandine> seb128, mind reviewing that?
[13:37] <kenvandine> whoops
[13:37] <seb128> kenvandine, can you mp it?
[13:37] <kenvandine> hang on... forgot to propose it :)
[13:37] <seb128> ;-)
[13:38] <Mirv> didrocks: not much in the end. the test system is blamed, but should I file a bug to refer to about (some of the) tests that randomly pop up, to ask upstream to try to reduce the flakiness of the tests?
[13:38] <kenvandine> https://code.launchpad.net/~ken-vandine/ubuntu-system-settings-online-accounts/multiarch/+merge/179188
[13:38] <didrocks> Mirv: I think that would be cool, if you can list them yeah
[13:38] <kenvandine> seb128, ^^
[13:38]  * kenvandine hasn't had enough coffee :)
[13:38] <Mirv> ok
[13:40] <kenvandine> mpt, in the cellular settings panel, when you manually choose a carrier to register with, what should the success/failure feedback look like?
[13:42] <seb128> kenvandine, approved, I'm not sure the multi-arch: same is needed on the -dev but I don't think it hurts either
[13:42] <seb128> kenvandine, I can't change the mp status, you need to do it
[13:43] <kenvandine> will do
[13:43] <kenvandine> seb128, thx
[13:43] <seb128> yw!
[13:45] <kenvandine> i'm amazed how long registering with an operator takes... like 2 minutes before it fails
[13:45] <kenvandine> same on android... so not our stack :)
[13:45] <kenvandine> that's a long time staring at the screen waiting
[13:50] <Mirv> didrocks: not so easy actually, it seems to me that the test runs in themselves seem somehow flaky, in ways I don't comprehend. see for example http://10.97.0.1:8080/job/autopilot-saucy-daily_release/822/label=autopilot-intel/consoleText that marked intel green (ati failed still), but actually didn't run that many tests
[13:50] <didrocks> Mirv: maybe try to get some autopilot guys on board?
[13:51] <Mirv> didrocks: who are the current key autopilot people?
[13:52] <didrocks> Mirv: thomi
[13:52] <mpt> kenvandine, hmm, I hadn't thought about that. What kind of error messages might you get?
[13:52] <Mirv> thanks
[13:52] <kenvandine> mpt, so far all i've seen is "failed to register"
[13:53] <kenvandine> mpt, we should show an activity indicator and somehow show the error
[13:53] <kenvandine> mpt, and what about for success?  just go back to the previous page?
[13:54] <kenvandine> and a notification?
[13:54] <robru> cyphermox, didrocks: ok, I gotta hop on a train asap, will be on later to look more at this.
[13:54] <mhall119> Mirv: didrocks: the poppler qml plugin is just exposing the new upstream poppler qt5 support
[13:54] <didrocks> robru: ok, great!
[13:54] <robru> cyphermox, I commented on that mp
[13:55] <mhall119> it's in a branch, and we could do daily releases into the coreapps PPA, but it really seems like something that should go into the archives along with the poppler qt5 packages themselves
[14:01] <mpt> kenvandine, how long does registration usually take?
[14:02] <seb128> kenvandine, mpt: you guys are in an hangout and talking over IRC? :p
[14:02] <seb128> (yeah I do it as well :p)
[14:02] <kenvandine> mpt, seems pretty slow
[14:03] <kenvandine> mpt 30 seconds or so when it succeeds
[14:03] <mpt> Hmmm, that's long
[14:03] <kenvandine> yup
[14:03] <kenvandine> same on android, so it isn't us :)
[14:03] <mpt> too long for a spinner alone, really
[14:04] <mpt> kenvandine, do you get any partial feedback at all? Are there any stages in the process?
[14:04] <kenvandine> nope
[14:09] <seb128> kenvandine, mpt: I confirm that stuff is slow, I got a spinner for ages on my old non smart phone and my android one as well
[14:18] <attente> does file descriptor 9 have any special meaning?
[14:20] <larsu> attente: no.
[14:24] <mpt> kenvandine, is there a reasonable timeout? E.g. do you give up after 60 seconds, or 120, or what?
[14:25] <kenvandine> mpt, no, three doesn't appear to be a way to cancel a current registration process
[14:26] <kenvandine> mpt, so i can't make it timeout myself
[14:26] <kenvandine> in fact, if you try another attempt before the previous fails/succeeds you get an error saying there is a registration in process
[14:26] <mpt> kenvandine, what happens if you send the registration request, then turn off the phone? Might the registration complete while it is turned off?
[14:27] <kenvandine> i don't think so
[14:50] <mpt> kenvandine, if not, then turning off the cellular radio would also cancel the registration, right? And there's no harm from doing that if you're not on a carrier at the moment.
[14:50] <mpt> Ah, but you wouldn't know how long to turn it off for ... If you turned it off for five seconds and then back on, the registration might complete anyway?
[15:05] <cyphermox> fginther: https://code.launchpad.net/~robru/ubuntu-settings-components/packaging/+merge/178964
[15:05] <cyphermox> fginther: ^ I think we may want to add this to the ci, for robru
[15:05] <mpt> kenvandine, ooh, the toolkit people may hate me for this
[15:06] <fginther> cyphermox, ack, I can get it added
[15:07] <fginther> cyphermox, recommendations for a stack?
[15:07] <cyphermox> just a second, I'll take a look
[15:08] <kenvandine> mpt, :-D
[15:11] <mpt> kenvandine: "When you choose a carrier, the radio mark preceding the previous carrier (if any) should be replaced by a spinner preceding the selected carrier (as in [[MenuLayout#Horizontal_padding|menu layout]]), and the amount of time the registration has taken so far should be shown at the trailing end in the form “M:SS”. When registration completes, that duration should disappear, and the current carrier should regain its radio mark. If the current
[15:11] <mpt>  carrier is the previous one, because registration with the new one failed, an alert should appear with the title “Error”, text “Registration failed. Try again later, or contact the carrier.”, and an “OK” button."
[15:12] <mpt> Wondering if we should auto-navigate back if registration succeeded
[15:12] <mpt> I guess so, because the carrier value is shown on the previous screen.
[15:18] <mpt> kenvandine, https://wiki.ubuntu.com/Networking?action=diff&rev2=118&rev1=117 ... And let's have future discussions of that sort in #ubuntu-touch. :-)
[15:22] <kenvandine> mpt, thanks!
[15:37] <seb128> kenvandine, I've online accounts back \o/ ;-)
[15:38] <kenvandine> woot
[20:15] <fginther> cyphermox, how about adding ubuntu-settings-components to stacks/head/settings.cfg ?