=== Aww is now known as AWW
=== AWW is now known as Aww
prompt32highvoltage, does anyone knows if there is a way to run macchanger on my wlan0 interface, before wlan0 is up ?02:19
sarnoldprompt32: you'll probably have better success in #ubuntu02:21
prompt32sarnold, i'll try, thanks02:23
Mirvdidrocks: 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 builds05:36
Mirvfor example https://launchpadlibrarian.net/147043226/buildlog_ubuntu-saucy-i386.ubuntu-ui-toolkit_0.1.46%2B13.10.20130808-0ubuntu1_FAILEDTOBUILD.txt.gz05:36
Mirvso I think revert would be needed05:36
didrocksMirv: 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
Mirvdidrocks: I don't exactly understand what's getting broken in there, can you?05:37
Mirvbut it seems something got broken, whatever way it did05:38
Mirvand same for qtubuntu-camera https://launchpadlibrarian.net/147043988/buildlog_ubuntu-saucy-armhf.qtubuntu-camera_0.3.3%2B13.10.20130808-0ubuntu1_FAILEDTOBUILD.txt.gz05:38
Mirvthe bug he's trying to address is https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/120923905:39
ubot2`Ubuntu bug 1209239 in qtchooser (Ubuntu) "MultiArch support for QT5 is insufficient for cross building" [Undecided,Confirmed]05:39
didrocksMirv: hum, did you try to upgrade/install like qt5-qmake locally?05:40
Mirvit reads there "dependencies on qtbase5-dev-tools and qt5-qmake must have an :any suffix."05:40
Mirvdidrocks: everything did update correctly this morning for me, so maybe it's those build-depends (on all packages)?05:40
Mirvit's a bit invasive change, even if it'd be correct technically05:41
didrocksMirv: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html05:43
didrockswe can refind the same issue in what is blocking Qt5 in proposed05:43
Mirvah, qtbase was uploaded as well05:44
didrocksthis issue is clearly:05:44
didrocksqt5-default/i386 unsatisfiable Depends: qtchooser:any05:44
* didrocks wonders why05:44
didrocksand then, all the cascades is because of that05:44
didrocksgrrr, I don't understand05:48
Mirvyeah proposed qtbase update gives the error http://pastebin.ubuntu.com/5961461/05:52
Mirvgoes above me as well05:52
didrocksso, 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
Mirvdowngrading qtchooser to 26-3ubuntu1 does not allow qtbase upgrade either05:53
didrocks+         qtbase5-dev-tools:any (= ${binary:Version}),05:53
didrocks+         qtchooser:any,05:53
didrocksbut this is invalid…05:54
didrocksMirv: yeah, the issue is in qt505:54
didrocksMirv: not sure what he wanted to do with :any05:54
didrockslet me remove that05:54
didrocksMirv: was his change committed to any vcs?05:54
Mirvlet me see05:54
didrocksor should I just apt-get source + upload?05:54
Mirvdidrocks: no, does not seem to be in ubuntu branches nor in ~kubuntu-packagers05:55
didrocksMirv: ok, let's do 2 things05:56
didrocksMirv: for unblocking, I'm going to remove the dep on -proposed, ok?05:56
didrocksso that you can restart building everything05:56
Mirvdidrocks: ok.05:56
didrocksand relaunching the stacks with foo05:56
didrocksjust after that, I'm going to upload the fix for Qt05:56
didrocksMirv: ok, please relaunch the builds05:58
didrocksMirv: proposed disabled in the tests as well05:58
* didrocks now goes to fix Qt505:59
Mirvdidrocks: ok05:59
cyphermoxhey didrocks06:00
didrocksMirv: then, do you want me or you to send an email to the ML?06:00
didrockshey cyphermox06:00
didrocksMirv: revert uploaded06:05
didrocks(not a full revert, just the :any thing)06:05
Mirvdidrocks: I can, although which ML?06:05
cyphermoxchrisccoulson: hey, you having issues with your funky bluetooth hid2hci keyboard thing on saucy?06:05
didrocksMirv: the phone one06:05
Mirvok, will do06:05
cyphermoxchrisccoulson: seems to me like you should, the bluez udev rule looks to me like it should be just failing06:05
didrocksMirv: just tell that dailies will be really delayed as we disabled proposed, but rebuild everything06:05
didrocksMirv: we'll ask for an iso resping06:06
didrocks(do not hesitate to link to the 2 qt version, the faulty one and the fixed one ;))06:06
didrocksthanks Mirv!06:06
didrocksMirv: does this looks good to you? https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dHFtUmlPOUtCRk8zR2dtaEpIbUVhMmc#gid=306:12
Mirvdidrocks: looks excellent, I think that has been longed for a lot06:15
didrocksMirv: yeah, until we have an automatic dashboard, it's a good workaround :)06:16
didrocksMirv: so, filing this in now? maybe let's wait from the rebuild without -proposed first06:16
didrocksMirv: you are relaunching all stacks failing with "foo" (one you restarted the build)?06:16
didrockscan I help?06:16
Mirvdidrocks: 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:18
Mirvdidrocks: filling in, yes, and relaunching the failed stacks - so far only media and sdk and now filling in the chart06:19
didrocksMirv: yeah, I guess this one and next :)06:20
didrocksMirv: just tell me if I can be of any help06:21
Mirvdidrocks: open my head and grab some things from there :)06:21
didrocksahah, that's part of the issue ;)06:21
Mirvdidrocks: 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 found06:22
Mirvdidrocks: 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 pacakges06:23
didrocksMirv: hum, previous qtbase brought hybris on the base image06:23
didrocksMirv: it will force rebuilding the packages06:23
Mirvdidrocks: and that's what failed, building the packages?06:24
didrocksas it's what intended by that06:24
Mirvah, foo does that, if they haven't built?06:24
didrocksok, basically, if you don't do anything, the build will:06:24
didrocks- scratch the current workspace06:24
didrocks- redownload everything06:24
didrocks- see if anything isn't in distro06:24
didrocks- build from that06:24
didrocksif you file "BUILD_ONLY"06:25
didrocks- it won't scratch the current workspace for that stack06:25
didrocks- it will remove all the components that match BUILD_ONLY list06:25
didrocks- and so, only compare if anything new available and upload that06:25
didrocksthe whole stack is tested in both cases06:25
didrocksmaking sense?06:25
didrocksif you rebuild the whole stack, not a biggie anyway06:26
didrocks(just some CPU cycles lost ;))06:26
didrocks(doing apps)06:27
MirvREBUILD_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
Mirvdidrocks: commenting out not working for -proposed:
Mirvfor tests06:29
didrocksMirv: so plain rebuild is fine in that case, yeah ;)06:29
didrocksMirv: oh, sorry, ok, let me remove the file one sec06:29
didrocksMirv: done06:29
didrocksMirv: 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 testing06:30
* didrocks relaunches media with "foo"06:30
Mirvok, thanks06:31
didrocksyou're doing it for sdk?06:31
didrocksrebuilding unity-webapps-qml for webapp06:31
didrocksok, now, let's wait for the result and update the spreadsheet06:32
MirvI'd hope someone at google would add the links possibility for pieces of text inside a field06:44
didrocksMirv: you mean, like ellipsis and when you click on it, it expands?06:46
Mirvdidrocks: I mean, if I've an URL in a field and other text, the URL would still act as a link06:47
didrocksoh right, sometimes it works, sometimes not06:47
didrocksI never understood the pattern06:47
Mirvoh it works sometimes? then there should be some trick. I know something worked at one point when I copy-pasted from elsewhere06:47
didrocksyeah, sometimes, it's recognized as a link06:47
didrocksthat's really weird…06:48
MirvI tried it now but it didn't help, ie. having clipboard content with html06:48
Mirvor something.. trying06:49
Mirvah, that's probably also something that only works alone06:50
Mirvdidrocks: should media be now able to publish itself automatically, as it depended (and halted) on SDK which now published successfully?06:54
didrocksMirv: hum, interesting, maybe both were published at the same time?06:55
didrocksMirv: let me fake SDK publishing06:55
didrocksMirv: ah, it's because we build SDK after media06:55
didrocksMirv: so for safety, there is no automatic publishing (like if there is an ABI break)06:56
didrocksnot an issue with the sdk as it's a runtime dep06:56
didrocksand there is nothing in the pipe breaking, right?06:56
didrocksok, so let me fake a publish on sdk06:59
didrocksyou will see that then media is running06:59
Mirvand just curious, since I noted that media had halted 20 mins ago because sdk failed to publish, and then 10 minutes ago sdk published successfully06:59
didrocksMirv: right, so sdk was built after media07:00
Mirvyep, now it published media07:00
didrocks2013-08-08 06:59:36,179 INFO Considering publishing: media (head)07:00
didrocks2013-08-08 06:59:36,190 INFO media (head) may be publishable, trying it07:00
didrocksMirv: basically, it's a safety net07:00
didrockslike imagine, you have indicators in manual publication because of HUD07:00
Mirvwhich is good07:00
didrocksthen, you *rebuild* (not just publish) HUD07:01
didrocksmaybe HUD has an ABI break07:01
didrocksand so if we publish HUD and indicators, things will go ugly :)07:01
didrocksso the automated publication is only rolled out if no rebuild was involved in the stack declenching the others07:02
didrockssorry, not sure I'm clear…07:02
Mirvyes, makes sense07:05
jibelgood morning07:10
Mirvdidrocks: 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 package07:10
didrockssalut jibel07:10
didrocksMirv: right, sdk stack sounds good to you?07:10
Mirvdidrocks: yes, I'm just not sure what has happened some of the other community apps sources, ie are they wanted in daily release or separately07:11
Mirvand has it been some other team uploading those07:11
didrocksI think for the apps, they are click packaging07:11
didrocksso not really in distro07:11
Mirvah, right07:11
didrocksfor the bindings, we are handling those07:11
didrocks(I can be fully wrong ;))07:12
Mirvso then I remember at least one file manager related QML plugin, I'd need to check where that is flying around07:12
Mirvbut yes they should go to the saucy, if they're wanted to be part of the supported platform07:12
jibelsalut didrocks07:15
didrocksMirv: waow, apps passed the tests!07:16
didrocksMirv: I think there is nothing blocking on webapps, do you think we should publish it? (force the publication?)07:17
jibeldidrocks, 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
didrocksjibel: I think it will be fine, right Mirv? ^07:18
didrocksjibel: noooo07:20
didrocksjibel: if you do that publisher and so on won't work07:20
didrocksas it's a new job07:20
* didrocks cancels07:20
jibelI canceled07:21
MirvI don't have anything special ongoing there now07:21
Mirvdidrocks: despite the webapps-qml failing tests?07:22
Mirvdidrocks: I do know they assume it's a jenkins / test environment issue07:22
didrocksMirv: yeah, I looked the commits since last release, the changes seems unrelated07:22
Mirvif that's fine, then yes would be great07:22
didrocksMirv: just to be clear: I won't publish webapps-qml07:22
didrocks(the webapps stack)07:23
didrocksjust the apps stack07:23
Mirvdidrocks: yeah, I noticed you wrote that apps passed tests and then asked about publishing webapps, so I was unsure what you meant07:24
didrocksMirv: yeah, the "it" was apps, not webapps, sorry ;)07:24
Mirvfunny that gallery-app passed now07:24
Mirvwell, Günter had made one commit07:25
didrocksit was for that :)07:25
didrocksMirv: ok, do you mind refreshing the status for all stack (but phone, as we are waiting for it), now?07:25
didrocksah phone done!07:25
didrocksjibel: you can restart as soon as Mirv finishes to note the status07:25
jibeldidrocks, k, I found another interesting hobby07:26
Mirvdidrocks: ok07:27
Mirvdidrocks: ok all seems at pause and stack status page up-to-date07:29
didrocksMirv: \o/07:30
didrocksbig thanks07:30
didrocksjibel: restartttttttt ^07:30
didrocksMirv: oh, you should maybe mention the click package issue07:30
didrocksin the "not blocking release"07:30
didrocksthe last commit wasn't merged?07:31
Mirvdidrocks: yeah I was just about to ask about the click packages07:31
Mirvsince I haven't glanced at it before07:31
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
Mirvdidrocks: ok marked it down for now, yes it seems07:32
Mirvdidrocks: 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-common07:32
didrocksMirv: mention that latest MP isn't merged apparently07:32
didrocksMirv: ahah, ok, let me give RAOF the ATI machine for testing Mir07:32
didrocksand then, I'm on it, ok?07:32
Mirvwe tested and released Qt Creator update for precise, quantal and raring, and saucy archive upload would depend on getting the -common package in first07:33
Mirvdidrocks: that's fine :)07:33
didrocksdid we settled on having the source as qtcreator-plugin-ubuntu thought?07:33
didrocksor this is just the branch name being wrong?07:33
Mirvzoltan still hesitated on renaming the source without -common, but I can change that for saucy07:33
didrocksMirv: yeah, please do, I think it makes sense to prepare for the future07:34
Mirvyeah, changing that07:34
Mirvat least we got rid of the -data binary packages now07:34
didrocksjibel: Mirv: I'm blocking the ati machine right now to have RAOF debugging Mir07:35
Mirvand now I go see about thomi's qtbase patch07:36
Mirvoh, or.. maybe a coffee break, to keep sanity which is usually beneficial07:36
didrocksheh ;)07:38
didrocksMirv: enjoy!07:38
didrocksproposed reenabled FYI on both test machine and builders07:38
jibeldidrocks, jenkins is bakc07:40
didrocksthanks jibel07:40
seb128good morning desktopers07:41
jibeldidrocks, with 50 excutors on master which should be enough to trigger all the stacks, if it is not I'll increase it a bit more07:41
jibelI guess the side effect is only memory consumption07:41
jibelSalut seb12807:41
seb128lut jibel didrocks07:42
didrockssalut seb128!07:44
didrocksjibel: yeah, let's see how it goes07:44
seb128didrocks, Mirv: I've read the backlog on irclogs.u.c, I'm looking at the unity issue07:45
didrocksseb128: I think it's the same than the settings one07:45
didrocksseb128: FYI, I disabled proposed07:45
seb128didrocks, I guess some other packages got the libhybris shlibs depends by rebuilding with the broken mir yesterday07:45
didrocksduring those builds07:46
seb128didrocks, no, it's not, unity7 doesn't build-depends on qt07:46
didrocksyeah, it's not the Qt issue for sure07:46
didrocksseb128: thanks for investigating, I'm already under the water :)07:46
Mirvseb128: yes, same error there, thank you for looking at i07:53
seb128didrocks, Mirv: I'm not convinced that the "rebuild without proposed" is a good thing07:57
didrocksseb128: was the only way to get the thing unblocked timely07:57
didrocksseb128: see my followup email, it's enabled again07:57
seb128that's going to bring in your build the qtbase which depends on libhybris07:57
seb128and you might get extra libhybris depends through shlibs07:57
seb128we are never going to get out of it if we do that07:57
didrockswe can then do a new build today (with the new daemon)07:58
didrockseven forcing some if needed07:58
seb128I hope it's not going to add libhybris depends to extra components make things harder to untangle07:58
didrockslet's see, the set of components are quite limited07:58
didrocksso it's easy to look at them07:58
didrocksI didn't want to again block everything for 5 hours for Qt07:59
didrocksespecially as upstream is pressuring to get some stuff released07:59
seb128well, blocking is better than creating extra chaos which is going to take a week to sort out07:59
seb128but let's see07:59
didrocksseb128: I don't have time to argue on this. I agree, but then, it's not you taking the backfire :)07:59
didrockssee the discussions from yesterday when they want to publish even if tests fail…07:59
seb128well, you are going to take double backfire when hybris screw us for the next days08:00
seb128didrocks, 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 libhybris08:01
seb128that's what I though08:01
seb128didrocks, we are putting ourselve down in a hole there :/08:01
didrocksseb128: you're welcome to retrigger a rebuild once my qtbase is built08:02
didrocksif only people were testing before uploading… Not having qt installable is a shame08:02
seb128it's going to play whack a mole to rebuild things in right order08:02
seb128right, I agree with that08:02
didrocksseb128: quite easy, let's wait for things being in the release pocket08:03
didrocksthen, we can do an apt-cache rdepends08:03
didrocksand rebuild what's needed08:04
didrocks(even if there is no new commit)08:04
seb128that's going to take some 6 hours08:04
seb128let's see this afternoon08:04
didrockswell, qtbase to build will take that time anyway :p08:04
seb128right, that's what I was saying08:04
seb1286 hours of build + 1 publish cycle08:04
didrockswe're fine, because what's depending on those components are already in dailies08:05
didrocksso under our control to rebuild08:05
didrocksand we already had powerd and other stuff depending on it, for maybe no good reason08:06
didrocksso, it's time to clean that up08:06
didrocksseb128: but that doesn't explain the unity issue, right?08:11
seb128didrocks, no, I'm debugging that one next, that's why landing/rebuilding more stuff is making me nervous, new things get the depends08:13
seb128didrocks, powerd&co might be actually be using it to access android features08:14
didrocksseb128: yeah, I propose we make a list once everything is published in the release pocket08:14
didrocksand go one by one08:15
didrocksI see others which shouldn't already08:15
didrocksso let's take that as an opportunity to clean things up08:15
seb128Mirv, didrocks: the unity issue is because the compiz rebuild from xnox on monday caught the libhybris depends08:29
seb128we need to rebuild compiz08:29
xnoxseb128: the rebuild was ages ago, but i guess armhf was stuck FTBFS whilst compiler was getting fixed.....08:32
seb128xnox, it got published on monday08:33
xnoxyeah: amd64/i386/powerpc build on 2013-07-01|02 whilst armhf finally built on 2013-08-05.08:36
xnoxseb128: locally on armhf I still see that libhybris-common1 is still installed. Is that ok?08:52
seb128xnox, yes, the -common is fine, it's libhybris itself that divers libelg08:53
xnoxseb128: 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:54
xnox(the version number bumps at least)08:55
xnoxRight 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
xnoxhopefully the new calxeda nodes should build compiz quickly =)08:55
seb128xnox, sorry, I just beat you at that no change rebuild I think :p08:57
xnoxseb128: narf =)08:57
xnoxseb128: bets on how long it will take to build?08:57
seb128xnox, qtbase took 2 hours instead of 6 before08:58
xnoxfirefox from 20h40 down to 5h4008:59
seb128ogra_, see, it happened :p09:01
robrudidrocks, what's the deal with qmenumodel? I see it being daily released but it doesn't seem to be in distro yet?09:03
ogra_seb128, heh, yeah09:04
robrudidrocks, nm, got confused by differeing source/binary package names09:05
seb128xnox, compiz build down to 37 min (from 1h35 on previous build)09:31
Mirvthose speedups are awesome09:39
MirvI wonder what qtwebkit will be09:40
didrocksMirv: I relaunched what was depending on the wrong qtbase version10:03
didrocksMirv: relaunched as well unity as per new compiz ^10:03
seb128Mirv, you should be able to retry unity build, compiz is in saucy10:58
Mirvseb128: ok, the previous one started 50 minutes ago will still result in armhf failure?10:59
seb128Mirv, let me check11:00
Mirvseb128: it seems to have just finished successfully https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/486036811:00
seb128Mirv, great, it just start at the right time11:00
Mirv13:03 < didrocks> Mirv: relaunched as well unity as per new compiz ^11:01
Mirvwell it was the grand master who selected the timing11:01
seb128subject: [ubuntu/saucy] compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu311:01
seb128Date: Thu, 08 Aug 2013 10:07:08 -000011:02
seb128so timing was just right it seems11:02
seb128or didrocks was pulling on rmadison to see if compiz was in to push the button :p11:02
didrocksseb128: rmadison is my ennemy, I just checked at the right time I guess :)11:02
Mirvbut the ati tests failed a bit, so tests will need to be rerun11:03
tsdgeosseems you guys updated to poppler-0.24 in saucy, cool :-)11:03
seb128tsdgeos, yes, since we wanted the qt5 bindings ;-)11:04
seb128tsdgeos, and it's good to be on the current version11:04
seb128well, "current stable version" rather11:05
tsdgeosnow i only need to convince you to link it against openjpeg and the hell will freeze :D11:06
seb128that's doko/MIR team that needs to be convinced, but yeah, that would be nice11:06
tsdgeostried that11:07
tsdgeosafair the security team blocked on the fact that openjpeg had more CVE than that jpeg2000 library noone uses and noone develops that we ship11:08
tsdgeosthat one11:08
seb128I don't think they block it on because it more or less than the other one11:08
seb128but the fact that it has a record of having security issues is a problem for them, since they have to support it11:09
seb128tsdgeos, I'm going to have a look at updating to 1.511:09
seb128then when we can try asking the security guys again11:09
tsdgeoswell, jasper does not have security issues because noone looks inot it :D11:09
tsdgeosseb128: but i have to agree openjpeg is less than stellar too11:09
tsdgeosi think poppler regressed with some of the 1.x randomly11:10
seb128ha, they have a 2.0 out for some time11:11
tsdgeosthat's api incompatible though afair11:12
seb128fedora 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 yet11:12
ubot2`Freedesktop bug 58906 in general "0.22.0 does not find openjpeg-2.0.0" [Normal,New]11:12
seb128better to go for 1.5 rather then11:13
seb128that's what fedora/debian experimental have11:13
=== MacSlow is now known as MacSlow|lunch
Mirvok, it seems sdk and settings are already rebuilding after the new qt got published12:07
didrocksMirv: I ran them by hand12:07
didrocksMirv: then, unfortunately, unity tests are not finished yet12:08
didrocksso we'll wait for the tests to finish12:08
Mirvyes, it'll take some time12:08
Mirvmore autopilot machines wouldn't hurt12:08
didrocksok, qtbase in the release pocket12:10
didrocksand no more libhybris in qtdeclarative5-ubuntu-ui-toolkit-plugin_0.1.46+13.10.20130808.2-0ubuntu1_armhf.deb \o/12:18
seb128didrocks, great!12:25
=== MacSlow|lunch is now known as MacSlow
didrocksnow, waiting on unity test to finish, I rebuilt manually all the rest in ppa, so just waiting for the tests12:30
didrocksrobru: in addition to the new package, can you work on the webapps AP tests failure with upstream?12:46
didrocksas you can see on https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dHFtUmlPOUtCRk8zR2dtaEpIbUVhMmc#gid=3, there is a link12:46
didrocksit's blocking for quite few days12:46
robrudidrocks, 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
didrocksrobru: any ETA? Can you escalate that to Pat?12:47
didrocksrobru: he asked to know everything when we are blocked (and he's the contact in the spreadsheet)12:48
robrudidrocks, no idea. I can escalate if you want.12:48
didrocksrobru: please do :)12:48
robrudidrocks, you're talking about pat mcgowan, right?12:49
didrocks(he isn't online yet apparently)12:49
didrocksrobru: are the packages fixed? at least the cu2d part?12:49
robrudidrocks, ok, I just pushed updated packages: lines for that MP. can you check that it is the way you want it?12:49
didrocksrobru: as we are going to redeploy everything to add the new machine, would be nice to have the right config :)12:49
didrockshttps://code.launchpad.net/~robru/cupstream2distro-config/qtdbus-in-qa/+merge/179159 right?12:50
didrocksrobru: approved12:51
robrudidrocks, sweeeeeete12:51
robrudidrocks, should I redeploy or are you doing that?12:51
didrocksrobru: jibel has to redeploy for the machines, so don't worry :)12:52
didrocksrobru: I'm pulling on lillypilly as well12:52
didrocksfor refreshing the whitelist12:52
didrocksrobru: I'll let the first review on ubuntu-settings-components for cyphermox12:54
robrudidrocks, ok12:54
robrudidrocks, I'm leaving for prague in a few hours, anything you need done ASAP?12:56
didrocksrobru: no, just ping pat today please :)12:57
didrocksare you blocked on anything else?12:57
didrocksor workless? ;)12:57
robrugotta find a hotel with AC and then I'll be much more productive ;-)12:57
didrocksheh, that will help, indeed!12:57
robrudidrocks, no, not workless. some branches are just waiting for review.12:57
didrocks23 here today, that helps :)12:57
robru37 today ;-)12:57
didrocksenjoy the plane/train AC if any :p12:58
cyphermoxdidrocks: robru: ok, I'll get to it in a minute, just finishing up testing something for libcolumbus13:00
cyphermoxrobru: if you could link me, that would be awesome. I'll looking at more than one computer at a time13:01
Mirvdidrocks: unity tests failed once more, but I wouldn't retry them before all others have finished13:12
Mirvdidrocks: earlier this week it was the third autopilot run that got acceptable results for unity713:13
didrocksMirv: can you ping upstream? maybe they would have an idea on what's wrong13:15
Mirvdidrocks: ok, let's see if they could address any of the issues13:15
didrocksseb128: mind looking at the settings packaging changes?13:24
didrocksseb128: I didn't follow fully the -online ones13:25
seb128didrocks, looking13:25
seb128didrocks, 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 it13:27
seb128didrocks, +113:27
seb128didrocks, do you want me to publish?13:27
didrocksseb128: yes plese :)13:27
seb128didrocks, done13:30
seb128kenvandine, ^13:31
robrucyphermox, https://code.launchpad.net/~robru/ubuntu-settings-components/packaging13:31
seb128kenvandine, hey13:31
seb128kenvandine, we finally got settings published ;-)13:31
seb128kenvandine, please make the new lib in online account use multi-arch infos/pre-depends on multiarch-support/dpkg13:32
kenvandineah, sure ;)13:32
didrocksseb128: \o/13:33
didrocksonly apps13:33
didrocksand we'll be fine13:33
Mirvdidrocks: should we force unity release if we get stephen to ack the latest failed tests from the autopilot run?13:34
didrocksMirv: what would it give compared to tomorrow?13:35
didrocksMirv: the number of tests are quite high to force a release TBH13:35
didrockswe should get upstream fixing their tests rather than workaround13:35
kenvandineseb128, ^^13:37
kenvandineseb128, mind reviewing that?13:37
seb128kenvandine, can you mp it?13:37
kenvandinehang on... forgot to propose it :)13:37
Mirvdidrocks: 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
didrocksMirv: I think that would be cool, if you can list them yeah13:38
kenvandineseb128, ^^13:38
* kenvandine hasn't had enough coffee :)13:38
kenvandinempt, in the cellular settings panel, when you manually choose a carrier to register with, what should the success/failure feedback look like?13:40
seb128kenvandine, approved, I'm not sure the multi-arch: same is needed on the -dev but I don't think it hurts either13:42
seb128kenvandine, I can't change the mp status, you need to do it13:42
kenvandinewill do13:43
kenvandineseb128, thx13:43
kenvandinei'm amazed how long registering with an operator takes... like 2 minutes before it fails13:45
kenvandinesame on android... so not our stack :)13:45
kenvandinethat's a long time staring at the screen waiting13:45
Mirvdidrocks: 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 that marked intel green (ati failed still), but actually didn't run that many tests13:50
didrocksMirv: maybe try to get some autopilot guys on board?13:50
Mirvdidrocks: who are the current key autopilot people?13:51
didrocksMirv: thomi13:52
mptkenvandine, hmm, I hadn't thought about that. What kind of error messages might you get?13:52
kenvandinempt, so far all i've seen is "failed to register"13:52
kenvandinempt, we should show an activity indicator and somehow show the error13:53
kenvandinempt, and what about for success?  just go back to the previous page?13:53
kenvandineand a notification?13:54
robrucyphermox, didrocks: ok, I gotta hop on a train asap, will be on later to look more at this.13:54
mhall119Mirv: didrocks: the poppler qml plugin is just exposing the new upstream poppler qt5 support13:54
didrocksrobru: ok, great!13:54
robrucyphermox, I commented on that mp13:54
mhall119it'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 themselves13:55
=== greyback_ is now known as greyback|latelun
mptkenvandine, how long does registration usually take?14:01
seb128kenvandine, mpt: you guys are in an hangout and talking over IRC? :p14:02
seb128(yeah I do it as well :p)14:02
kenvandinempt, seems pretty slow14:02
kenvandinempt 30 seconds or so when it succeeds14:03
mptHmmm, that's long14:03
kenvandinesame on android, so it isn't us :)14:03
mpttoo long for a spinner alone, really14:03
mptkenvandine, do you get any partial feedback at all? Are there any stages in the process?14:04
seb128kenvandine, mpt: I confirm that stuff is slow, I got a spinner for ages on my old non smart phone and my android one as well14:09
=== jhernand1z is now known as jhernandez
attentedoes file descriptor 9 have any special meaning?14:18
larsuattente: no.14:20
mptkenvandine, is there a reasonable timeout? E.g. do you give up after 60 seconds, or 120, or what?14:24
kenvandinempt, no, three doesn't appear to be a way to cancel a current registration process14:25
kenvandinempt, so i can't make it timeout myself14:26
kenvandinein fact, if you try another attempt before the previous fails/succeeds you get an error saying there is a registration in process14:26
mptkenvandine, what happens if you send the registration request, then turn off the phone? Might the registration complete while it is turned off?14:26
kenvandinei don't think so14:27
=== tkamppeter__ is now known as tkamppeter
mptkenvandine, 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
mptAh, 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?14:50
cyphermoxfginther: https://code.launchpad.net/~robru/ubuntu-settings-components/packaging/+merge/17896415:05
cyphermoxfginther: ^ I think we may want to add this to the ci, for robru15:05
mptkenvandine, ooh, the toolkit people may hate me for this15:05
fginthercyphermox, ack, I can get it added15:06
fginthercyphermox, recommendations for a stack?15:07
cyphermoxjust a second, I'll take a look15:07
kenvandinempt, :-D15:08
mptkenvandine: "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 current15: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:11
mptWondering if we should auto-navigate back if registration succeeded15:12
mptI guess so, because the carrier value is shown on the previous screen.15:12
mptkenvandine, https://wiki.ubuntu.com/Networking?action=diff&rev2=118&rev1=117 ... And let's have future discussions of that sort in #ubuntu-touch. :-)15:18
kenvandinempt, thanks!15:22
=== greyback|latelun is now known as greyback
seb128kenvandine, I've online accounts back \o/ ;-)15:37
=== om26er is now known as om26er|away
=== Guest79504 is now known as amithkk
=== greyback is now known as greyback|dinner
=== om26er|away is now known as om26er
=== greyback|dinner is now known as greyback
fginthercyphermox, how about adding ubuntu-settings-components to stacks/head/settings.cfg ?20:15
=== ivanka_ is now known as ivanka_train
=== jbicha is now known as Guest66961
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!