[01:29] good morning, desktop developers, please help to give more comments on our packaging request at bug #1213998, thanks in advance. [01:29] Launchpad bug 1213998 in UbuntuKylin "[needs-packaging] youker-assistant" [High,New] https://launchpad.net/bugs/1213998 [04:48] Good morning [04:49] darkxst: you mean to the initial "if" check? [04:52] pitti, hi, I meant to add a tag like what is done for gnome3-staging [04:53] darkxst: http://paste.ubuntu.com/6027460/ ? [04:57] pitti, yeh thats good. thanks [04:57] ack, pushed [05:06] pitti: morning. two packaging 'ack's would be needed, platform-api http://pastebin.ubuntu.com/6027478/ + unity-scope-hoem http://pastebin.ubuntu.com/6027481/ [05:07] both seem ok to me [05:07] Mirv: first LGTM; second, the first hunk of control is in Conflicts:, right? [05:08] Mirv: ah, yes; so, +1 on both [05:08] pitti: yes. thanks! [05:22] bah, I can't publish unity stack anyhow since I don't know if anyone preNEWed unity-scope-mediascanner of if it was added to daily stack prematurely [05:23] no discussion here at least regarding it [05:57] xnox, ping [06:53] darkxst, do you know if g-s-d 3.8 changes the way the input sources keyboard shortcut works? [06:53] attente, yes slightly [06:54] it moves the keys, and they are now array string [06:54] gsettings keys [06:54] I patched g-c-c on ppa:darkxst/gsd38 to fix that [06:55] might need to be patched in indicator-keyboard as well though [06:55] i-keyboard shouldn't be affected, but after updating to your ppa, i wasn't able to get the switching working again [06:57] unless g-s-d also changes where the current input source is stored [06:57] attente, https://launchpadlibrarian.net/148298120/gnome-control-center_1%3A3.6.3-0ubuntu32~saucy2_1%3A3.6.3-0ubuntu32~saucy3.diff.gz [06:59] attente, they are now in org.gnome.desktop.wm.keybindings [06:59] and 'as' instead of 's' [07:01] but your g-c-c is still using the old media-keys plugin schema? [07:04] #define MEDIA_KEYS_SCHEMA_ID "org.gnome.desktop.wm.keybindings" [07:04] oh. sorry, i guess i didn't see that in the diff [07:15] jasoncwarner__: Are there any specific features for desktop that might be interesting to highlight on Doc's What's New? [07:15] http://bazaar.launchpad.net/~ubuntu-core-doc/ubuntu-docs/saucy/view/head:/ubuntu-help/C/whats-new.page [08:18] good morning desktopers [08:23] seb128: morning. do you happen to remember if sil2100's lp:unity-scope-mediascanner was preNEWed? I didn't publish unity stack since it was added there but I didn't find in the backlog any proof that it would have been preNEWed. [08:24] Mirv, hey, no idea if it was, check with sil2100 when he's around I guess [08:24] seb128: ok. I will, I'm just not sure if he's still sick or cured. [08:26] Mirv, I guess you can publish anyway, if it's not in the whitelist it's just not going to be uploaded? [08:27] seb128: I don't think it's that easy, since the whitelist = bzr pull done with the daily config, and it was pulled last week for the other packages. the problem here is adding packages to cu2d before it has been preNEWed, but that has now happened a couple of times since we don't have the process 100% polished yet [08:28] and since it has happened before, I can't be sure it didn't happen this time [08:28] drop it from the config until you can check? [08:28] seb128: ok, I'll do if sil2100 doesn't show up in 1.5h [08:28] ok [08:29] Mirv, I saw that you tried the appmenu qpa bug, is there any work currently happening on that? [08:30] seb128: I just set the priority "High" for the other target package as well. sil2100 was working on that on Thursday I think, but I didn't hear how it progressed. [08:30] ok [08:30] meanwhile I think I have the 5.1.1 CMake issue cured, at least so far it seems that way. one less blocker. [08:34] when do you plan tog et qt 5.1 uploaded? [08:35] seb128: I think that's what tomorrow's UDS session is for. so far I think these are blockers so cannot upload before they are fixed, unless our 'no regressions policy' is laxed a bit: https://bugs.launchpad.net/bugs/+bugs?field.tag=qt5.1 [08:35] ok, that makes sense [08:38] hello paris! [08:39] the land where it takes an hour to get out of the airport [08:39] the land where the people running the trains randomly section off areas of the station for no apparent reason and yell at people in french to go there and, no, go here instead [08:40] the land where people cut in front of you and go on the train when you were politely waiting for people to finish getting _off_ the train [08:40] the land where the ISPs have pre-chosen passwords for their wifi boxes that are comprised entirely of characters [0-9][A-F], but are not hexidecimal [08:41] lol [08:41] the land that i love....... to hate [08:41] desrt, good morning Canadians lost in France [08:41] hi :) [08:41] desrt, try china... [08:41] hey attente [08:41] hi seb128 :) [08:42] the entire time i was in germany i wasn't missing toronto at all. 2 hours of paris was enough to make me want to go home again :p [08:42] attente: they have weird wifi passwords in china as well? :) [08:42] lol [08:42] desrt, and you stay there for 10 days? [08:42] seb128: ya. maybe a side trip to england... we're still considering [08:42] CDG is a weird place [08:43] i always am aware of the fact that it is the worst-run airport in existence [08:43] but each time i go through it i remember _just_ _how_ _bad_ it is [08:43] so maybe i'll avoid any extra flying for the duration of this trip :) [08:43] lol [08:43] * seb128 things desrt actually enjoy being in France [08:43] we landed at 2G this time.... [08:44] gives him a reason to complain :p [08:44] you know the whole terminal 2E/2F badness in CDG, i'm sure.... everyone does [08:44] 2G is a whole new level of hilariousness [08:44] it is a building in the middle of nowhere that is connected to 2F, by bus, and nothing else [08:47] seb128: in any case, i may be up for TGV trips.... 10 days is already starting to seem like quite a lot [08:47] * desrt <3 TGV [08:47] desrt, if you want to go the u.k you can also do the eurostar, but that's less nice than a tgv [08:47] ya... we've been checking eurostar prices.... $500 :/ [08:48] urg [08:49] perhaps we will find some nice esperantists here :) [08:49] * desrt goes to have some coffee for now [08:50] desrt, enjoy! [08:59] Mirv, dialer-app/i386 unsatisfiable Depends: qtdeclarative5-ubuntu-history-plugin [08:59] Mirv, is that a known issue? [09:01] seb128: I'm not familiar with the dialer-app, but at least the history-service is not yet packaged [09:02] how come we landed stuff depending on it to the archive then? [09:02] I guess that's a sil2100 question? [09:02] seb128: it shouldn't have been, but yes [09:03] history-service is coming hopefully soon [09:16] Mirv, do you know why we got a new mir uploaded but not a new unity-system-compositor? is the compositor part of the unity stack? [09:16] Mirv, that's block mir to move to release... [09:16] Mirv, is sil2100 supposed to be there today? [09:20] seb128: unity-system-compositor is in mirslave stack, it should probably be forcefully rebuilt [09:20] on the stack status page it says also "Mir will be blocked in -proposed until RAOF uploads the new, rebuilt xorg-server to -proposed", but I'm not sure if that's then obsolete information [09:21] seb128: yes, he should be [09:21] Mirv: I uploaded *some* rebuilt xorg-server to -proposed [09:21] RAOF: ok [09:22] RAOF, hey, so that info is not current anymore? [09:22] I don't know the history of that, so I don't know if that's then enough or not [09:22] I think that info is indeed not current. [09:22] Mirv, we need a force rebuilt from mirslave then I guess [09:22] Morning! [09:22] I though didrocks made it so things would rebuild after every mir upload? [09:22] oh, sil2100 *is* working today [09:22] sil2100, hey, we were wondering if you had the day off [09:23] My alarm clock was off ;/ [09:23] sil2100: haha, hello hello! [09:23] I just jumped out of my bed, not sure why it was off but I was like really really shocked [09:24] waking up at 11am, not remembering what happened with the alarm clock during the W.E [09:24] sil2100, stop drinking that much on weekends! ;-) [09:24] It's nooot like thaaat! [09:24] sil2100: you can answer when you have time, but was unity-scope-mediascanner preNEWed? I now temporarily removed it from daily release since I didn't dare to publish unity with included. [09:25] Mirv: from what I know I think Didier pre-NEWed it already [09:27] sil2100: I searched the backlogs but I didn't find any chat of that, so I was unsure [09:27] sil2100: so if you think it can go into NEW queue, please deploy the current trunk unity.cfg again (I only deployed a local non-merged branch) to have it back [09:28] Let me try to refresh my mind again [09:30] Mirv: I'm pretty sure Didier ACKed the preNEWing review, but not sure if the whitelist got updated [09:30] seb128: do you know how to update the whitelists as Didier is doing always? [09:31] sil2100, yes, let me do that [09:31] seb128: thank you [09:32] sil2100, the steps are in https://wiki.ubuntu.com/DailyRelease/FAQ#Adding.2BAC8-removing_components_to_a_stack (in case you need to ping another archive admin about that some day) [09:34] sil2100, done [09:34] seb128: thanks! [09:35] Mirv: redeploying unity, the next tick should release unity-scope-mediascanner then [09:35] sil2100, Mirv: can any of you trigger the mirslave forced rebuild? [09:35] seb128: I also see that mmsd is in the NEW queue, are you free enough to look at it or could you maybe quickly point me to someone I could poke about this [09:36] sil2100, let me have a look [09:36] seb128: force rebuild? You mean, like now? [09:36] Since if we force rebuild it, we'll miss the next tick probably right now [09:36] sil2100, btw you landed messaging-app and phone-app but they are broken because then depends on history-service which is not in daily landing [09:36] As it will start in 24 minutes [09:36] seb128: so they're stuck in -proposed right now? [09:37] Mirv: how's work on history-service? [09:37] sil2100, that works, mir is stucked in proposed since friday since unity-system-compositor doesn't get rebuild [09:37] sil2100, we need u-s-c built with the current mir at some point, I wonder if the stacks are in the wrong order [09:37] sil2100, how come we have a .26 for mir but not for mirslave? [09:38] hmm, ok, then something is broken clearly, as mirslave should rebuild every time mir has a commit :o Let me take a look, but this is STRANGE [09:38] Mirv: if you're busy, I can try to prepare history-service for daily [09:38] sil2100: ok then [09:39] But first I check the mirslave issue [09:39] I already launched unity-system-compositor rebuild [09:39] it should be ready before the next tick [09:40] Mirv: any clue why it doesn't do that automatically? [09:42] sil2100: there was some LP hitch with mir so I relaunched it with foo - it may be that then mirslave didn't get another relaunch after that, simply [09:42] Mirv: but the process is set this way that it should automatically re-build everything whenever there's a change in mir [09:43] With the force-rebuild stanza [09:44] sil2100: I've had some weird experiences with force-rebuild lately, maybe it's connected [09:44] sil2100: like, nothing seems to happen at times or on some stacks [09:44] I mean, it launches but goes by without actually building [09:46] huh [09:57] seb128: can you approve sil2100's session https://blueprints.launchpad.net/ubuntu/+spec/client-1308-daily-release-process ? [09:57] Mirv, done [09:57] thanks! [09:58] sil2100, you got pings on several channels, you might want to check your IRC client [09:58] sil2100, some are pinging again due to the lack of pong ;-) [10:01] seb128: thanks for the info! ;) [10:01] sil2100, yw [10:01] sil2100, so, about messaging-app and phone-app ... how could we land stuff where their depends are missing? don't we have checks for that? [10:02] seb128: if you can ack http://10.97.0.1:8080/view/cu2d/view/Head/view/MirSlave/job/cu2d-mirslave-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity-system-compositor_0.0.1+13.10.20130826-0ubuntu1.diff I can publish the unity-system-compositor rebuild [10:03] Mirv, +1 [10:04] hmm, the tick just started, but I'll keep that +1 on mind until it's calm again [10:04] Mirv: I think you can publish it now anyway [10:05] sil2100: even though waitonstacks is running? [10:05] Mirv: since Didier made it so you can publish 'older, ready' packages till the moment the publishing job goes on again [10:05] Mirv: that was my understanding, yes [10:05] let's try [10:06] seb128: I think this is a problem here... [10:08] seb128: sorry for that, normally it's checked during integration tests which are required, but due to FF we 'passed' some packages without integration tests yet (but will have soon) - if a dep is not a build-dep, it will only fail when it's installed during integration testing [10:09] seb128: on Friday I thought that history-service was prepared, as Didier set to finish it by EOW [10:09] sil2100, I see ... no worry, well let's fix that then [10:09] seb128: I quickly do that today so that we unbreak those ;/ [10:09] sil2100, thanks [10:10] and nope, I didn't finish that history-service yet as mentioned on the task list. I've started on it today in-between other tasks [10:10] telephony-service would be fine from my part but needs approval, maybe sil2100 can do that? https://code.launchpad.net/~timo-jyrinki/telephony-service/packaging_fixes/+merge/181800 [10:13] Mirv: will review :) [10:14] Mirv: I'll take over history-service from you so that you can concentrate on other pending tasks! [10:14] sil2100: thanks! [10:14] sil2100: no need regarding history-service, I've already several commits, I'll just give you the MP when it's ready [10:14] sil2100: if anything, please try to have time for the QPA thing instead :) [10:15] Mirv: excellent then! So I'll review the T-S merge [10:15] Mirv, do we need to keep the -dbg in there (since we have the dbgsym)? otherwise looks fine to me === vrruiz_ is now known as rvr [10:17] seb128: maybe it's not needed after it gets to archives, and I should remove it from history-service too [10:17] sil2100: did any of your packages have -dbg left? [10:17] Mirv: I usually remove the -dbg packages [10:18] Mirv: along with the stanza in debian/rules - I only leave what's needed to build with debugging symbols [10:19] sil2100: I wonder if leaving -DCMAKE_BUILD_TYPE=Debug is still ok after removing the manual dh_strip -> package then? [10:19] Mirv: yes [10:27] Mirv: so, remove the -dbg and the dh_strip stanza [10:27] sil2100: yes, pushed already [10:28] Mirv: commented, could you also update the copyright file to copyright the asset files? CC-BY-SA-3.0 [10:29] sil2100: thanks. can you try building it? it built fine on Friday, now the tests are failing for me. [10:31] desrt: hey Ryan, how are you? [10:31] desrt: I stumbled over my "review Ryan's menu traversing demo, investigate whether it makes sense to generalize and integrate into/provide by autopilot-gtk" WI [10:32] desrt: do you have a pointer to that demo? [10:34] sil2100: CC-BY-SA changes pushed [10:36] Mirv: approved! Thanks :) [10:38] seb128: sorry for poking you that much, but besides looking at mmsd in the NEW queue, could you also do a preNEW review of https://code.launchpad.net/~phablet-team/content-hub/trunk packaging? [10:39] On Friday I made a packaging review and I was thinking of maybe ultimately starting daily-releasing that [10:39] brb [10:39] sil2100, can do [10:43] (ok telephony-services tests pass fine pbuilder) [10:46] hmmm [10:46] sil2100, mmsd NEWed [10:47] sil2100, oh, content-hub ... I already preNEWed that last week, I asked for the qml bindings package to be renamed [10:48] seb128: ah, I remember! Right, so it's ok now with all the changes I made I think [10:48] sil2100, yeah, just had anothing quick look, it's fine [10:48] seb128: thanks for everything ;) COuld you update the whitelist as the last thing related to this stuff? [10:48] sil2100, did you commit? (e.g do I only need to pull?) === Sweetsha1k is now known as Sweetshark [11:23] seb128: bzr branch lp:~timo-jyrinki/history-service/packagin_fixes (non-typo:) <- preNEW? [11:24] seb128: qtdeclarative5-ubuntu-content0.1 is not enough? [11:24] sil2100, enough what? [11:24] merge request at https://code.launchpad.net/~timo-jyrinki/history-service/packagin_fixes/+merge/182081 [11:25] seb128: about the QML bindings package renaming - I remember you mentioned that during the review and I changed the naming to qtdeclarative5-ubuntu-content0.1 [11:25] And that got merged [11:26] sil2100, right, what's the issue? [11:26] seb128: since you said 'did you commit' ;) [11:26] seb128: so I have been wondering if I need to modify something else [11:26] sil2100, that was about " COuld you update the whitelist" [11:26] Aaaaaa [11:27] AAAA [11:27] sil2100, I can pull on the server side, but please commit the change [11:28] Mirv, sil2100: so history-service gives us qtdeclarative5-ubuntu-history-plugin ... what gives us qtdeclarative5-ubuntu-telephony-plugin (that's also missing as a dialer-app depends) [11:30] Mirv, ok, small comment but it looks fine otherwise [11:30] Mirv, you removed the "# If you don't have commit rights to lp:history-service but need to upload..." text, not sure why? [11:31] seb128: the telephony-service you already looked at an hour ago [11:31] ok, great [11:31] seb128: although they are now both "0.1", not -plugin [11:31] seb128: ah, sorry, it's wrap-and-sort bug to remove it, I'll put the normal stanza back [11:31] that's fine, we just need to update dialer-app's depends [11:31] Mirv, thanks, then you can approve [11:32] seb128: ok, thanks [11:34] I got a strange issue, totally no idea's on how to debug it. When i'm playing music with Audacious, and then I open firefox and put my cursor for example in the search field, it keeps blinking. [11:35] If I stop audacious playback, it stops also [11:36] prolly because audacious triggers alot of window updates? [11:43] seb128, Mirv: sorry for the delay guys - https://code.launchpad.net/~sil2100/cupstream2distro-config/content-hub_enable/+merge/182083 [11:53] sil2100: approved. I've also https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/services_add_telephony_history/+merge/182069 [11:53] for you [11:53] but it will need syncing with yours [11:54] Mirv: re-enable unity-scope-mediascanner please ;) [11:55] sil2100: or do you think those two should stay in phone stack instead of the new services stack? [11:55] even though they are called -srevice :) [11:55] sil2100: oh ooops :) [11:55] same branch [12:01] Mirv: will approve once history-service is reviewed ;) [12:01] sil2100: it was [12:01] Ah [12:01] https://code.launchpad.net/~timo-jyrinki/history-service/packagin_fixes/+merge/182081 [12:01] Didn't see an Approve there [12:02] Let me browse through the changes and give a +1 [12:02] Mirv: I would propose some small modifications there still ;p But those are mostly nit-picks [12:02] LP is really slow late last week and now [12:03] Mirv: can I point out some small issues? You have a moment for fixing? [12:03] not only diff generation takes time, now even commit list updating takes time at times. I think that jenkins failure was from there. [12:03] sil2100: those are quick ones anyway, just shoot [12:07] Mirv: commented [12:08] Mirv: thanks! [12:12] Mirv: can you attend http://summit.ubuntu.com/uds-1308/meeting/21952/client-1308-daily-release-process/ ? [12:16] sil2100: I can, as luckily it's the first one of the day so "only" 6pm [12:16] ;) [12:16] sil2100, Mirv: be careful, the time/slots are not fixed yet [12:16] Mirv: I scheduled it for now so that it's closer to the beginning, like the Qt5 one [12:16] But yea, as seb128 said [12:16] sil2100, you have scheduling access? [12:17] seb128: yes [12:17] sil2100, do you host client1? [12:18] seb128: not sure, but I could [12:18] sil2100, Mirv: currently the qt 5.1 one is on the next slot, Mirv should probably attend that one as well [12:18] I see almost all the client meetings are clien1 [12:19] sil2100, right, we should load balance between client1/2 [12:19] seb128: who takes care of client2? And how does it look like, for instance Mirv will be able to host his Qt session or will I have to start it? [12:20] sil2100, I'm going to host one of the client track, so I guess 2 if you have 1 [12:20] sil2100, the "host" just needs to start the hangout, no need to lead the session [12:20] sil2100, e.g you can just turn off mic and video while hosting if you don't participate [12:21] but you need to keep it running and stop the recording at this end (it's a bit annoying to "block" on that, but that's the way it is :/) [12:21] Mirv, I guess you would prefer having the qt5.1 early on wednesday? [12:23] seb128: I don't mind which day it is as long as it's early. I guess we're already about quite sure we won't hit FF with qt5.1 (unless given the right to regress) so I guess it wouldn't hurt. [12:24] sil2100: unity-scope-mediascanner FTBFS btw [12:26] Mirv, sil2100: qt5.1 on wednesday at 2pm utc [12:26] sil2100, I tried to balance the sessions between the 2 tracks, let me know how that works for you [12:26] ok [12:27] seb128: thanks! Looking [12:28] sil2100, I let thursday mir sessions in your track, I don't think we can host 2 mir sessions in //, same people required in both, i'm going to put the next topic in client 2 to balance [12:30] tkamppeter__, do you have anything specific to discuss on https://blueprints.launchpad.net/ubuntu/+spec/client-1305-convertibles-and-touch-desktop at vUDS, I saw that you proposed for discussion again (we already had a session at previous vUDS I think) ... who is going to come to the session? [12:33] Ok [12:34] jasoncwarner__: hi! Guess you're not around right now, but do we have a session about the reverse dependencies of Mir and their maintainance? [12:36] I think I'll wait for Mike Terry regarding planning that [12:49] Mirv: looking into the FTBFS for services stack - it seems there's some problem with platform dependencies === psivaa is now known as psivaa-afk [13:00] seb128, I think we can remove the proposal, what has to be done is simply fixing all linked bugs. [13:00] tkamppeter__, ok, good, doing that then, thanks! === tkamppeter__ is now known as tkamppeter [13:15] Mirv: hm, I think maybe platform-api will need to be rebuilt [13:15] Mirv: since right now we have a conflict [13:15] Mirv: you can see by adding ppa:ubuntu-unity/daily-build for a moment, update and then try installing libubuntu-application-api-mirserver1 [13:17] Maybe the builds happened in some strange moments, hmm [13:18] Yeah... geh [13:18] seb128: I think we might have to drop the latest platform-api from -proposed [13:18] sil2100, why? [13:18] seb128: it's depending on a version of libmirserver1 that's not in the archive [13:18] seb128: libmirserver1 (= 0.0.9+13.10.20130825.1-0ubuntu1) [13:19] seb128: while the archive has only 0.0.9+13.10.20130822-0ubuntu1 and 0.0.10+13.10.20130826-0ubuntu1 (in -proposed) [13:19] sil2100, that's why we needed a rebuild [13:19] seb128: but we also need a rebuild of platform-api then [13:19] right [13:19] everything that depends libmir* [13:20] Ok, now I get it, since I didn't know what was the reason why mirslave needed a rebuild - it's all the consequence of some probable bug in cu2d, which doesn't force rebuild [13:20] Rebuilding then [13:21] sil2100, thanks [13:22] sil2100, sorry we discussed the issue this morning before you joined [13:22] seb128: no problem, it was my fault for over-sleeping! [13:22] ;) [13:25] mterry: hi! [13:28] mterry: I think we might need a session on UDS to consult the maintainance of Mir rdepends [13:31] seb128: could you approve https://blueprints.launchpad.net/ubuntu/+spec/client-s-1308-mir-qa-and-benchmarking ? [13:31] sil2100, it's already approved (you can see the uds-13.08 green checkmark) [13:32] seb128: ah, so it doesn't have to have the status changed to 'Approved'? [13:32] sil2100, not to show on the UDS schedule (I think) [13:33] sil2100, set as approved [13:33] Awesome, good to know [13:34] sil2100, in that session or a new one? [13:35] mterry: I'm wondering, since we already have 3-4 Mir sessions planned [13:38] tvoss: hi! Do you have a specific meeting schedule for the "Mir roadmap" meeting [13:39] sil2100, is issue of rdepends enough for a whole session? What are the issues from a QA point of view? [13:41] mterry: I don't know, I guess it's not that much so I'm looking for other sessions I could drop this into [13:41] mterry: for instance "Mir roadmap" seems ok [13:42] mterry: since this has to be discussed, as we have a lot of rdepends and if we want to have Mir 'in' we need those maintained [13:44] sil2100, ah I see, we want the team to either support or drop their depends [13:44] sil2100, and get them in a room until they do [13:44] sil2100, mir roadmap seems good yeah [14:06] mterry: I guess I'll try proposing that to Thomas as soon as he pops up [14:11] seb128: for getting the fixed platform-api we have to wait when this tick finishes... the last manual run failed on the check job, and there was not enough time to restart it or even push further [14:20] tvoss__ / tvoss: hi [14:22] sil2100, ok [14:28] darkxst: heya. [14:35] seb128: just in case, history-service and telephony are pre-NEWed? [14:35] Mirv: argh, you didn't top-approve the content-hub re-enabling ;/ [14:36] seb128: the content-hub re-addition to daily-release didn't yet get merged, but did you update the whitelist for the two I mentioned? [14:40] sil2100, history/telephony ... too many reviews, I reviewed some of those for Mirv, let me check which ones [14:40] sil2100, +1 for history [14:40] seb128: I guess yes, I think you reviewed those - jsut the whitelist then :) [14:41] And content-hub, once that guy gets merged... [14:41] I reviewed content-hub [14:41] Yes, but the whitelist I mean :) [14:44] sil2100, I pulled on the server side [14:50] shrug [14:50] jbicha, please don't start uploading GNOME 3.90 components without talking with us here before [14:52] pitti: oh this. i had almost forgotten. [14:52] pitti: didn't i send you some small .c file a long time ago? [14:53] desrt: not that I can remember [14:53] desrt, is your api to get the size of a folder still going to be in for this cycle? [14:53] desrt: well, I probably won't use the actual code anyway if we want to do that with autopilot, I was just interested in what you do/test there [14:53] seb128: yes. i will land it when i return. [14:54] seb128: i suppose i could land it now if you need it for something [14:54] pitti: my approach was as follows: run an app in a clean environment (no gsettings stuff, etc) [14:54] desrt, it's just that freezes are coming soon and I'm not sure how you handle that for glib [14:54] then find the GtkMenuBar in the toplevel window [14:54] then start iterating through the items. skip 'n' items, and activate the next one [14:55] run this the first time with n=0, then repeat until there are no items remaining [14:55] desrt: why "skip n"? [14:55] ah [14:55] each time starting new, from a clean environment [14:55] desrt: what do yo do with them, signal an activate and see that it doesn't crash? or something more elaborate? [14:55] my reason for doing it was a bit different, though: for each item i watched for a few seconds if any windows opened as a side effect and then captured text from all of the GtkLabel in the window [14:56] the idea here was to give some extra search terms for the hud [14:56] so if i search for "word wrap" and this is in preferences, for example, then the "preferences" menu item would match [14:56] webcrawler style, essentially [15:01] desrt: ah, ok; the iteration is straightforward with ap, I just wondered what to actually test [15:03] pitti: i only activated the menu items [15:03] there are two things here that i seem to think we were discussing [15:04] the first is that simply activating each menu item and ensuring the result is not a crash is probably a good way of finding some extremely embarassing data-loss bugs here and there [15:04] i've seen situations like this before... [15:04] *nod*, that would be an obvious one [15:04] the second is that having the CI framework that you've setup would be a good framework to use for getting these strings for the HUD [15:05] because otherwise we have to do it at package build time or something, which would just be exceedingly strange [15:05] for the second part, though.... i am no longer involved in the hud in any way === m_conley_away is now known as m_conley [15:05] and i don't know if anyone would still be interested in having this information [15:25] sil2100, I don't know. Yeah, check with mterry and get something scheduled if we don't. === ayan is now known as Guest73351 === ayan_ is now known as ayan === rickspencer3_ is now known as rickspencer3 [16:05] jasoncwarner__: I had a chat with tvoss__ just now, and we'll try making it part of the Mir roadmap session [16:05] jasoncwarner__: will have a chat with Olli tomorrow === jasoncwarner__ is now known as jasoncwarner [16:07] seb128: can I ask for a packaging ACK for services? The changes look sane, although a bit hacky - but I guess that's one way of doing it correctly: https://jenkins.qa.ubuntu.com/job/cu2d-services-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-keyboard_0.99.trunk.phablet2+13.10.20130826.4-0ubuntu1.diff [16:09] sil2100, you are sure that "python:any" is valid? we had to revert similar changes from doko before because they were buggy afaik [16:09] cyphermox: kenvandine: I'll handle this release tick if you don't mind [16:09] sil2100, e.g https://launchpad.net/ubuntu/saucy/+source/qtbase-opensource-src/5.0.2+dfsg1-7ubuntu5 [16:10] sil2100, http://launchpadlibrarian.net/147050152/qtbase-opensource-src_5.0.2%2Bdfsg1-7ubuntu4_5.0.2%2Bdfsg1-7ubuntu5.diff.gz [16:10] hm, didn't know it caused problems in the past [16:10] sil2100, please do... i have no time :/ [16:11] ;) [16:11] seb128: ok, if Didier reverted it I guess it's a valid concern ;p [16:13] seb128: I'll revert it and re-run the stack if we get it in [16:13] sil2100, thanks [16:15] seb128, greyback, veebers: https://code.launchpad.net/~sil2100/ubuntu-keyboard/python_any_revert/+merge/182151 [16:26] cyphermox, kenvandine: https://code.launchpad.net/~sil2100/cupstream2distro-config/new_dependency_chain_extra/+merge/182153 <- ? [16:28] seb128: hm, I also think the nvidia machine might be broken [16:28] :-( [16:28] At least the container ;/ [16:30] cyphermox, kenvandine: could you guys wait a moment? [16:31] ok [16:31] looks fine anyway [16:31] I'll add some additional extra deps... [16:31] ;/ [16:31] cyphermox: thanks! [16:32] nvidia machine broken> should I look into it or did you talk to QA to get it sorted? [16:35]