[04:01] <pitti> Bonjour tout le monde !
[04:02] <pitti> RAOF, robert_ancell: hey Chris, hey Robert, how are you?
[04:02] <robert_ancell> pitti, hello!
[04:02] <RAOF> pitti: Aloha!
[04:03] <pitti> robert_ancell, RAOF: one question: what's the plan wrt. multi-monitor config under MIR? will xserver-xmir be taught to understand proper xrandr, or g-s-d be taught to apply .config/monitors.xml the MIR way?
[04:04] <pitti> and is there a workaround to disable the internal LVDS and drive the external monitor (on the dock) with full resolution?
[04:04] <RAOF> xserver-xmir will be taught to understand xrandr.
[04:04] <pitti> ah, sweet
[04:05] <pitti> i. e. that should apply to gnome, kde, etc. then
[04:05] <RAOF> There'll be a call for testing shortly :)
[04:05] <RAOF> Yeah.
[04:06] <pitti> (I tried it yesterday to debug something for sabdfl, but I don't want to run it like that all day, hence my question for a workaround)
[04:12] <Sarvatt> RAOF: awesome
[04:12] <RAOF> Yeah, having actual multihead support is pretty important :)
[05:18] <didrocks> morning
[05:18] <pitti> bonjour didrocks
[05:22] <Mirv> robru: can you approve https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/unity_add_indicator-keyboard/+merge/181458 ?
[05:24] <Mirv> ah, canceling that one, already in robru's branch as of around the exact same time :)
[05:25] <didrocks> salut pitti!
[05:25] <didrocks> hey Mirv
[05:26] <Mirv> hey didrocks
[05:30] <robru> hi didrocks, Mirv, pitti! ;-)
[05:30] <pitti> hey robru, how are you?
[05:31] <robru> pitti, not bad. thinking about that pygobject help() introspection issue.
[05:31] <didrocks> hey robru!
[05:31] <robru> didrocks, hi!
[05:31] <didrocks> robru: how was your travel? back home?
[05:31] <robru> didrocks, almost home! I am just a short 2hr boat ride away! ;-)
[05:31] <didrocks> heh :)
[05:32] <robru> didrocks, but the train was really nice. I got a sleeper cabin and had a shower on the train! so comfortable! I can never ride economy class ever again ;-)
[05:32] <didrocks> waow, excellent, indeed!
[05:32] <Mirv> didrocks: I'd ask http://10.97.0.1:8080/view/cu2d/view/Head/view/Friends/job/cu2d-friends-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_qml-friends_0.2.0+13.10.20130821-0ubuntu1.diff but it's missing Replaces
[05:33] <robru> the shower was so nice! the drain was a direct hole in the bottom of the train, I could see the ground flying by as we went
[05:33] <robru> Mirv, oh, good catch
[05:35] <didrocks> Mirv: indeed, good catch :)
[05:35] <didrocks> robru: 2 hours is enough to fix it? :p
[05:35] <didrocks> do you mind?
[05:35] <didrocks> robru: ah, the water was directly going on the rails?
[05:36] <robru> didrocks, haha, yes and yes
[05:46] <Mirv> didrocks: can you approve a libunity-dev b-d version bump? http://10.97.0.1:8080/view/cu2d/view/Head/view/Unity8/job/cu2d-unity8-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity8_7.81.3+13.10.20130821.2-0ubuntu1.diff
[05:47] <Mirv> I'll hold from rerunning more stacks since a scheduled rerun is 15mins away
[05:47] <didrocks> Mirv: yeah +1 ;)
[05:47] <didrocks> Mirv: right, better to wait now
[05:48] <didrocks> let's hope leann's team will give us support soon on the intel kernel pb
[05:48] <robru> didrocks, https://code.launchpad.net/~robru/qml-friends/fix-replaces/+merge/181462 please approve this packaging change to better handle this rename transition
[05:48] <Mirv> argh, I'm doing five things at the same time now, this is not healthy for brain
[05:49] <Mirv> debugging qtwebkit, watching stacks, testing qtdeclarative patch on device, patching/building qtcreator and testing raring/quantal/precise qtcreator updates
[05:49] <Mirv> :D
[05:50] <didrocks> robru: can you just add one package name per line and add trailing comma please?
[05:50] <didrocks> robru: just in nitpick mode, but it's better to see what rename changed and so on ;)
[05:51] <didrocks> (and consistency between sources)
[05:51] <didrocks> Mirv: heh, welcome to my world every single day!
[05:51] <didrocks> Mirv: maybe that explains to you why I'm nuts :p
[05:54] <Mirv> didrocks: I can feel it :)
[05:56] <didrocks> heh
[06:00] <didrocks> we lost a robru :)
[06:01] <robru> sorry, was busy
[06:01] <didrocks> next tick is soonish
[06:01] <didrocks> I would rather not miss it
[06:01] <robru> ok
[06:02] <robru> nitpick mode: ON! `wrap-and-sort -a -t` you guys are gonna love this ;-)
[06:02] <robru> approve now please ;-)
[06:03] <robru> oh, look at that! qtdeclarative5-test-plugin was included in the deps twice. this fixes that.
[06:04] <didrocks> (approved with hate :p)
[06:04] <robru> hahahahAHHAHAHAH
[06:05] <robru> can we somehow make `wrap-and-sort -a -t` a commit hook so that nobody can ever commit unsorted dep lists ever again?
[06:06] <robru> like just make jenkins do it automatically during the merge or something.
[06:06] <didrocks> robru: that's a nice idea in fact
[06:06] <didrocks> doing that automatically as part of the MP
[06:06] <didrocks> robru: mind noting it down somewhere?
[06:07] <robru> the only trick is that wrap-and-sort likes to drop our little comment about the packaging team. So we'd need to fix that bug in order to automate it.
[06:07] <didrocks> (I still hate wrap-and-sort, don't mislead :p)
[06:07] <didrocks> yeah, it's just a bug that can be fixed, indeed
[06:07] <robru> didrocks, I'll file a bug for this, what package should I use?
[06:08] <robru> didrocks, https://bugs.launchpad.net/cupstream2distro perhaps here?
[06:08] <didrocks> robru: there is no package for the upstream merger, just file against cupstream2distro, it's where I'm looking anyway
[06:08] <didrocks> yep ;)
[07:19] <didrocks> hey dpm!
[07:19] <didrocks> dpm: how are you?
[07:24] <dpm> morning didrocks, doing well, and you?
[07:36]  * Mirv practices on getting core-dev acks on #ubuntu-devel
[07:40] <didrocks> Mirv: heh, great!
[07:41] <didrocks> dpm: I'm good thanks! I wonder if you had any chance to have qreator fixes uploaded
[07:41] <didrocks> or is it stuck on a queue sponsoring?
[07:41] <didrocks> IIRC, I gave a conditional ack on some additional fixes
[07:43] <dpm> didrocks, I haven't had a chance, but I filed the bug and milestoned it for the release I'm preparing, probably this weekend if I've got the time -> bug 1210408
[07:43] <ubot2`> Launchpad bug 1210408 in Qreator "Fix packaging issues" [Medium,Triaged] https://launchpad.net/bugs/1210408
[07:43] <didrocks> dpm: ok, thanks
[07:49] <dholbach> hiya
[07:49] <dholbach> can somebody have a second look at https://bugs.launchpad.net/ubuntu/+bug/1213998?
[07:49] <ubot2`> Launchpad bug 1213998 in UbuntuKylin "[needs-packaging] youker-assistant" [High,New]
[07:49] <dholbach> it looks like the kylin folks are still waiting for a review there
[07:55] <sil2100> Morning
[07:55] <sil2100> A bit late, but had to deal with the internet in this new flat
[08:01] <Mirv> morning sil2100!
[08:05] <dholbach> salut seb128
[08:06] <dholbach> seb128, tu sais quelqu'un qui peut réviser bug 1213998?
[08:06] <ubot2`> Launchpad bug 1213998 in UbuntuKylin "[needs-packaging] youker-assistant" [High,New] https://launchpad.net/bugs/1213998
[08:07] <seb128> dholbach, salut, je peux le faire
[08:07] <seb128> good morning desktopers!
[08:07] <dholbach> très bien
[08:07] <dholbach> merci beaucoup
[08:07] <Laney> morning
[08:09] <seb128> Laney, hey, good morning! how are you?
[08:09] <Laney> good thanks!
[08:09] <Laney> you?
[08:10] <pitti> salut seb128, hey Laney
[08:10]  * pitti hugs dholbach
[08:11] <Laney> guten morgen pitti
[08:11] <mlankhorst> wie gehts
[08:11] <seb128> Laney, I'm good thanks
[08:11] <Laney> ooh patch piloting this afternoon, how exciting
[08:11] <seb128> pitti, salut!
[08:18] <Mirv> robru: friends published, see #ubuntu-devel for the ack discussio
[08:18]  * dholbach hugs pitti back
[08:23] <seb128> pitti, I confirmed that your upower fix works btw
[08:26] <pitti> seb128: très bien
[08:26] <seb128> pitti, I've other upower issues...
[08:27] <seb128> pitti, the history datas tend to have buggy charge=0.000 around suspend/resume, do you think it would make sense for upower to filter them out? or should I filter them out on client-side?
[08:27] <seb128> pitti, I'm going to do "if [n-1] > 1 && n = 0, then ignore"
[08:28] <seb128> in practice I doubt we often hit 0% charge anyway
[08:28] <pitti> seb128: these are status "unknown", not "charging" or "discharging", right?
[08:28] <pitti> seb128: yes, you need to filter out "unknown"; the test suite does that as well, I'm not sure what this means
[08:29] <seb128> pitti, I do that already, but some are "empty"
[08:29] <seb128> 1376926716	46.000	discharging
[08:29] <seb128> 1376939036	0.000	empty
[08:29] <seb128> 1376939037	0.000	unknown
[08:29] <seb128> 1376939037	43.000	discharging
[08:31] <seb128> pitti, I'm just going to do what I said, filter out the 0 if previous point is > 1
[08:31] <seb128> in practice I doubt we ever have 0 on charge curves
[08:32] <seb128> or if we do we should get there by being at 1% before (if the device doesn't go flat while suspended)
[08:33] <Mirv> sil2100: compiz+unity would be "ready" and even autopilot succeeded, but you know better what to do with that transition..
[08:34] <sil2100> Mirv: thanks! Looking
[08:36] <sil2100> Mirv: ohshit
[08:36] <sil2100> Mirv: you saw the changelog?
[08:37] <Mirv> sil2100: big, lots of text, that one?-)
[08:37] <sil2100> Mirv: you think hm, is that acceptable ;p ? Yea
[08:37] <sil2100> Mirv: I mean, good they put those descriptive commit messages
[08:37] <sil2100> But COME ON
[08:37] <seb128> haha
[08:39] <darkxst> pitti, seb128 hi
[08:39] <seb128> darkxst, hey
[08:39] <darkxst> seb128, so we can start on g-s-d now?
[08:39] <seb128> darkxst, to be honest I don't think we are going to have the spare cycles for that before feature freeze
[08:41] <darkxst> well its basically ready
[08:41] <Mirv> sil2100: I think those are ok. well, huge, but still it seems it's their habit and it wouldn't be so bad if it wasn't the whole commits for several months
[08:41] <darkxst> and was a lot of work getting it to the point
[08:41] <seb128> darkxst, yeah, things always seem ready, until you figure out that they have bugs and you need to deal with those
[08:41] <seb128> darkxst, even reviewing the work is going to take time and we are all overworked over crazy
[08:41] <sil2100> Indeed
[08:42] <seb128> darkxst, and fixing e-d-s goa/uoa is higher on my list than getting a new g-s-d in if I find spare cycle in the next week
[08:42] <sil2100> Mirv: anyway, we need someone to ACK at least the compiz changes
[08:42] <seb128> sil2100, Mirv: are we getting an unity landing today?
[08:42] <sil2100> Mirv: so someone that has some more time on his hands, as the diff is pretty big
[08:42] <sil2100> seb128: yes, with the new compiz, but we need an ACK
[08:43] <seb128> sil2100, packaging ack?
[08:43] <sil2100> seb128: while the new compiz has a BIG diff
[08:43] <seb128> packaging diff or code diff?
[08:43] <sil2100> seb128: packaging diff
[08:43] <seb128> nobody is going to be able to review the code diff
[08:43] <seb128> oh, how so?
[08:43] <seb128> shot me the url
[08:43] <seb128> I can try to have a look...
[08:43] <seb128> or run away :p
[08:43] <sil2100> https://jenkins.qa.ubuntu.com/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_compiz_1%3A0.9.10+13.10.20130822-0ubuntu1.diff
[08:44] <sil2100> seb128: most of it is a biiiig changelog ;p But well, it hasn't been released for a looong time
[08:44] <Laney> darkxst: got it in a ppa?
[08:44] <Laney> I'll try running it for a bit
[08:44] <darkxst> Laney, ppa:darkxst/gsd38
[08:44] <sil2100> seb128: there's not much actual packaging changes though, so it should be easy to review - although the big diff can scare a bit
[08:44] <Laney> k
[08:44] <Laney> maybe mail the desktop list too
[08:44] <Mirv> in addition to that compiz ack, unity itself needs ack http://pastebin.ubuntu.com/6013267/
[08:46] <seb128> sil2100, Mirv: compiz looks fine, but somebody should check that the grid.xml.in and expo.xml.in changes are fine
[08:46] <seb128> +-		    <default>&lt;Control&gt;&lt;Alt&gt;KP_4</default>
[08:46] <seb128> ++		    <default>&lt;Control&gt;&lt;Super&gt;Left</default>
[08:47] <seb128> eg
[08:47] <seb128> do we overwrite those values somewhere else?
[08:47] <seb128> sil2100, Mirv: e.g please check that the grid keybindings are still the same after update
[08:47] <seb128> otherwise +1 on the other changes
[08:47] <seb128> Mirv, unity is +1
[08:48] <sil2100> seb128: thank you! Will check
[08:48] <seb128> yw
[08:48] <seb128> sil2100, Mirv: do you want me to update/run those updates to see if they are alright?
[08:50] <sil2100> seb128: I'm upgrading now as well
[08:50] <Mirv> seb128: I think that'd be welcome
[08:50] <Mirv> me too
[08:50] <darkxst> Laney, ok, guess I need to remerge the g-c-c in that ppa first though
[08:50] <Mirv> say what you want about CLI, I like synaptic for package management
[08:58] <Laney> darkxst: the gsettings override is specifying some keys that don't exist any more
[08:58] <sil2100> Mirv: seb128: working fine here after upgrade, at least my keybindings are the same now, so it looks ok here
[08:59] <darkxst> Laney, they are in ubuntu-settings packages though arent they?
[09:00] <Laney> no it comes from gsd
[09:01] <Laney> for the media keys plugin
[09:01] <Mirv> basic smoke test of new compiz + unity alright
[09:07] <sil2100> Let's publish
[09:07] <sil2100> Mirv: should I?
[09:10] <darkxst> Laney, ok will remove them
[09:15] <sil2100> Mirv: publishing
[09:17] <Mirv> sil2100: +1 for 4 months newer compiz :)
[09:18] <sil2100> \o/ Now it would be nice to get indicators + HUD released as well
[09:18] <Mirv> yeah, I updated the bug to tell that the fix didn't fix either at least completely
[09:19] <Mirv> and pinged wellark regarding hud, ted is obviously not awake yet. other pings welcome.
[09:19] <Mirv> (did not ping ted either)
[09:24] <seb128> Mirv, did you get a pong from Wellark?
[09:29] <attente> seb128, do you have time to take a quick look at https://code.launchpad.net/~attente/indicator-keyboard/gvfs/+merge/181503 ?
[09:30] <Mirv> seb128: no
[09:30] <Mirv> seb128: now did
[09:32] <seb128> Laney, hey, please review https://code.launchpad.net/~seb128/ubuntu-system-settings/battery-charge-tweaks/+merge/181505 (load the webpage, I put review comments that you are not going to get via email)
[09:32] <Laney> will do
[09:33] <Laney> trying to find a solution to this i18n.tr thing
[09:33] <seb128> Laney, please don't spend a day on that, nothing is broken atm and we have bigger issues than making code look nicer...
[09:34] <seb128> attente, approved
[09:34] <Laney> i'm not spending a day on it ...
[09:34] <attente> seb128, thanks!
[09:34] <seb128> attente, I merged your accountsservice changes btw, going to review your indicator-keyboard patch to use that next
[09:34] <mhr3_> larsu, could you pls answer the qmenumodel question in https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/unity-theme-icon-provider/+merge/180805/comments/410625 ?
[09:34] <seb128> Laney, ok, I'm just saying, you were already on it when I left for exercice yesterday evening ;-)
[09:34] <Laney> no
[09:34] <Laney> I tried to use the documented function
[09:34] <Laney> then I saw that it didn't work
[09:35] <Laney> then I left
[09:35] <attente> seb128, ah, that's great, thanks!
[09:35] <Sweetshark> moin!
[09:35] <seb128> Laney, ok, all good then ;-)
[09:37] <Laney> ok, got it
[09:37] <Laney> i18n.tr("1 minute", "%1 minutes".arg(n), n)
[09:43] <larsu> mhr3_: will do
[09:43] <larsu> mhr3_: holy shit, why did setSchemeSearchPaths get added?!
[09:43] <larsu> mhr3_: thanks for the catch ;)
[09:48] <seb128> larsu, can a GActionGroup be casted in a GActionMap?
[09:48] <seb128> larsu, or said differently, can you review https://code.launchpad.net/~indicator-applet-developers/hud/g_action_map_lookup_action/+merge/181508 ?
[09:49] <larsu> seb128: no, not every actiongroup is an actionmap (GSimpleActionGroup is both, though)
[09:49] <larsu> seb128: I'll review it ;)
[09:49] <seb128> larsu, danke
[09:50] <Sweetshark> I seems like launchpad tried to import the LibreOffice repository again. Launchpad not sits not in a corner and whimpers. Poor thing, it always ends like that.
[09:50] <seb128> larsu, indicator stack is blocked because of that (indicators fail to build on deprecation warnings and we got a new glib that deprecates -g_simple_action_group_lookup)
[09:50] <seb128> Mirv, ^
[09:51] <larsu> seb128: that patch is correct. Approving.
[09:52] <seb128> larsu, thanks
[09:52] <larsu> waiting for jenkins before top-approving
[10:03] <sil2100> Mirv, didrocks: https://code.launchpad.net/~sil2100/cupstream2distro-config/remove_deprecated_scopes/+merge/181512
[10:03] <sil2100> Mirv, didrocks, pstolowski: there's also this for deprecation - https://code.launchpad.net/~sil2100/unity-scope-home/replace_deprecated_scopes/+merge/181511
[10:20] <seb128> Laney, not sure if you noted the other day, but I've a "location" subpanel on my disk (at least the UI)
[10:20] <Laney> yes I remember you saying
[10:20] <Laney> should be easy to hook it in
[10:20] <seb128> Laney, going to review your security&privacy now and then propose that subpanel on top
[10:20] <seb128> Laney, right, I just wanted to make sure you don't start on it/dup work
[10:21] <Laney> should we add gsettings keys for these settings?
[10:22] <seb128> which ones?
[10:22] <Laney> most of the security-privacy ones
[10:22] <Laney> or does something exist already
[10:23] <seb128> Laney, on that topic
[10:23] <seb128> bug #1207854
[10:23] <ubot2`> Launchpad bug 1207854 in Unity 8 "[greeter] should provide launcher/camera/notes options" [Undecided,New] https://launchpad.net/bugs/1207854
[10:23] <seb128> bug #1207857
[10:23] <ubot2`> Launchpad bug 1207857 in Unity 8 "[greeter] should provide options for stats/messages on welcome screen" [Undecided,New] https://launchpad.net/bugs/1207857
[10:23] <seb128> bug #1208418
[10:23] <ubot2`> Launchpad bug 1208418 in Unity 8 "[greeter] should provide a "lock sound" option" [Undecided,New] https://launchpad.net/bugs/1208418
[10:23] <seb128> Laney, I opened that a few weeks ago
[10:23] <seb128> Laney, it would be worth talking to mterry about it again, he said he wanted to use accountsservice for some of the stuff
[10:24] <seb128> grrr
[10:24]  * seb128 wtf at indicator-datetime
[10:24] <seb128> make check fails on
[10:24] <seb128> The following files contain translations and are currently not in use. Please
[10:24] <seb128> consider adding these to the POTFILES.in file, located in the po/ directory.
[10:24] <seb128> debian/indicator-datetime/usr/share/indicator-datetime/datetime-dialog.ui
[10:25] <Laney> heh
[10:25] <seb128> I'm adding that to POTFILES.in but I don't get why that's happening
[10:25] <Laney> adding a file in the debian/ build tree?
[10:25] <seb128> no, I was going to add po/POTFILES.skip to the upstream source
[10:25] <seb128> but that seems wrong
[10:26] <seb128> I wonder what changed that this just started
[10:26] <Mirv> sil2100: approved
[10:26] <sil2100> Mirv: sankyu!
[10:26] <Sweetshark> seb128: any opinion on the phantom fix for 3.5.7 issue? Just remove it from changelog?
[10:27] <seb128> Sweetshark, sorry I didn't have time to look at your email yet
[10:27] <seb128> Sweetshark, let me have a look
[10:27] <seb128> sil2100, Mirv, didrocks: do you know if anything changed on the upstream CI side that makes make check run where it was not before?
[10:28] <didrocks> seb128: I don't know about it
[10:28] <Laney> it's running some extra test now
[10:28] <seb128> k :/
[10:28] <Laney> I: user script /var/cache/pbuilder/build//4040/tmp/hooks/B09googletests starting
[10:28] <sil2100> seb128: same here, not really sure what changed - I think we'll need Francis around
[10:28] <Mirv> nope here too
[10:28] <Laney> compare https://jenkins.qa.ubuntu.com/job/indicator-datetime-saucy-amd64-ci/32/console and https://jenkins.qa.ubuntu.com/job/indicator-datetime-saucy-amd64-ci/33/console
[10:29] <Mirv> seb128: hey. did the powerpc trick you did on Tuesday for signon work? since libhud-qt is also stuck, and it also already has i386 amd64 armhf defined instead of any
[10:29] <Mirv> or the removal of packages
[10:29] <seb128> Mirv, yes, it worked
[10:29] <seb128> Laney, right, that B09googletests broke things
[10:31] <Sweetshark> seb128: story is: guy prepared a patch, explicitly asked for inclusion in SRU, I applied the patch and asked if he would be happy with it and promised to include it, if its tested on the ppa for 1-2 weeks.
[10:31] <Sweetshark> seb128: He reported back that he is happy with the fix -- although the patches are not in patches/series, so they are never applied. :/ My proposal is to not apply the patches for this SRU (as they have seen no testing in the PPA), but keep them and test them in the PPA for the next SRU. So the only change for the SRU would be removing them from changelog.
[10:33] <sil2100> didrocks: I know I asked that before, but do we have a common license that we use for assets for Canonical upstream projects?
[10:33] <sil2100> What CC was that?
[10:34]  * sil2100 should probably ask management
[10:34] <didrocks> sil2100: look on the canonical wiki
[10:34] <Mirv> seb128: excuses page says libhud-qt-doc on powerpc is outdated, so removing that powerpc binary would apparently unlock the proposed migration
[10:34] <seb128> Sweetshark, seems fair enough, +1
[10:34] <seb128> Mirv, ok, let me have a look
[10:35] <seb128> Laney, is indicator-datetime just hitting segfault for everyone with the new glib?
[10:35] <Laney> probably everyone with eds enabled
[10:35] <seb128> Laney, hum, quite a gotcha, we already got a stack of dups
[10:35] <seb128> Laney, can you manually upload your fix to saucy?
[10:36] <Laney> even though it's still in proposed?
[10:36] <Sweetshark> pitti: ^^ -- I will tweak the changelog for 3.5.7 and ping you when its done.
[10:36] <seb128> Laney, I would rather get that fix sooner than later
[10:36] <seb128> Laney, see bug #1215003 the dups
[10:36] <ubot2`> Launchpad bug 1215003 in indicator-datetime (Ubuntu) "indicator-datetime-service crashed with SIGSEGV in g_date_time_to_unix()" [High,In progress] https://launchpad.net/bugs/1215003
[10:36] <Laney> huh, ok
[10:36] <Laney> give me a minute then
[10:36] <seb128> Laney, thanks
[10:36] <seb128> Laney, we need integration tests to make sure than glib updates don't break indicators/unity ;-)
[10:45] <Laney> uploaded
[10:46] <seb128> Laney, thanks!
[10:46] <Laney> i don't really understand the bug though
[10:46] <Laney> it's something to do with the .ui file only
[10:46] <Laney> otherwise it would list all of the files
[10:47] <seb128> Laney, the issue is that they run "make check" after the dh_install steps
[10:47] <seb128> Laney, intltool is looking for sources files
[10:47] <seb128> in debian/tmp you will get only binaries/datas
[10:47] <seb128> not source
[10:47] <seb128> the .ui is the only "source" there
[10:47] <seb128> but it's enough to make it looks like there is a source in the tree not listed by POTFILES
[10:47] <Laney> so it can't see that the file is already translated
[10:48] <seb128> Laney, it's not translated
[10:48] <seb128> translations are in the .mo
[10:50] <Laney> OK, that it's the same as a file that is listed in POTFILES.in then
[10:50] <Laney> i.e. that it's a copy in the build tree of a file that was already listed for translation
[10:52] <Laney> anyway, guess this check gets to be rethought :P
[10:53] <Laney> I guess it could write a potfiles.skip to ignore debian/ itself
[10:53] <Laney> oh bums, it's failing to build
[10:54] <Laney> args, because I disabled proposed in my chroot yesterday
[11:01] <sil2100> Mirv, didrocks, seb128: https://code.launchpad.net/~sil2100/dialer-app/packaging_review/+merge/181520
[11:01] <didrocks> sil2100: I let you and Mirv deal with the first pass maybe? Then seb128 or I would do the preNEWing
[11:01] <sil2100> Mirv, didrocks, seb128: as mentioned in the description, there's one thing I need to still consult with upstream, but they're not around
[11:02] <sil2100> k
[11:02] <didrocks> sil2100: at worse, ask bill if you can't get upstream
[11:02] <seb128> Laney, don't workaround it, it's going to bite any source, we just need the CI guys to fix their config
[11:02] <seb128> sil2100, looking
[11:05] <Laney> seb128: I'm not
[11:06] <seb128> Laney, k
[11:06] <Laney> larsu: can you confirm/deny this please: https://code.launchpad.net/~laney/indicator-datetime/use_g_action_map/+merge/181522
[11:06] <seb128> Laney, can you mp the changelog of your manual upload back to trunk?
[11:07] <seb128> Laney, the daily release stuff is going to be unhappy otherwise
[11:07] <larsu> Laney: is p->actions a GSimpleActionGroup?
[11:07] <Laney> larsu: yes; g_simple_action_group_new ();
[11:08] <larsu> Laney: looks good to me then, approving
[11:08] <Laney> seb128: really? won't it regenerate the changelog anyway from the proper MPs?
[11:08] <Laney> larsu: cheers, uploading too
[11:09] <seb128> Laney, well, there is a manual upload, so it's going to block "wait, there is an upload in Ubuntu that we don't have in trunk, let's block to have somebody confirm that we don't override a direct distro upload"
[11:09] <Laney> yeah I get that part
[11:09] <Laney> I just thought you could say "OK, that's fine" and then carry on rather than needing to merge the changelog back in
[11:09] <Laney> can just add it to the action map MP though
[11:10] <seb128> Laney, hum, I think didrocks added support for that but I'm unsure now, I don't find it in the FAQ
[11:11] <seb128> Laney, it might just work in fact, it used to not
[11:12] <Laney> I'll leave it and see ;-)
[11:12] <Laney> easy to put it in otherwise
[11:12] <seb128> didrocks, if distro has a changelog entry with no change compared to trunk, is that going to work or do we still need to changelog entry to be merged back?
[11:12] <seb128> Laney, right
[11:13] <seb128> sil2100, dialer-app ... can it be arch: any rather than hardcoding the archs?
[11:14] <sil2100> I changed that, right?
[11:14] <sil2100> seb128: +Architecture: any
[11:14] <sil2100> seb128: or maybe you're asking if it's safe?
[11:15] <seb128> sil2100, sorry, too many pings, I branched lp:dialer-app to do the preNEW review, not your branch
[11:16] <sil2100> ;)
[11:16] <sil2100> No problem!
[11:17] <seb128> sil2100, do we need 2 autopilot packages?
[11:19] <sil2100> seb128: that's something that I need to ask upstream exactly
[11:19] <sil2100> seb128: besides, both have different deps
[11:19] <sil2100> Conflicting deps
[11:19] <seb128> oh ok
[11:19] <seb128> if they have conflicting deps it makes sense I guess
[11:21] <sil2100> I'm just wondering why
[11:28] <didrocks> seb128: need to force the rebuild
[11:28] <didrocks> (sorry this channel was focused, so didn't get the notifications)
[11:29] <seb128> didrocks, no worry, less notifications is good ;-)
[11:29] <didrocks> seb128: there is a "skip check" not exposed for now on the command line
[11:29] <seb128> k
[11:29] <seb128> sil2100, ^ please, use the skip check for indicator-datetime later on, we did a manual archive upload for it
[11:29] <seb128> sil2100, I reviewed https://code.launchpad.net/~sil2100/dialer-app/packaging_review/+merge/181520 ... good for preNEW, I just added a small nitpick, you have extra build-depends there that seem not needed
[11:35] <seb128> Laney, looking to your privacy work, I guess you can already do the phone locking subscreen/values (look to battery if you want, there is a pretty similar "%1 minutes" picker/subscreen for the suspend time)
[11:35] <seb128> Laney, looks like that one would make sense as a gsettings key (at least for v1 with one user, not sure with multiusers)
[11:39] <Laney> seb128: ah, yeah, hmm, I wonder how those settings interact
[11:44] <seb128> Mirv, hud build fix merged in
[11:48] <Mirv> seb128: ok, rerunning
[11:49] <Mirv> then someons should still fix indicator-messages as well
[11:50] <seb128> Mirv, what's the issue with it?
[11:51] <Mirv> seb128: similar to hud, same bug report as well bug #1215180
[11:51] <ubot2`> Launchpad bug 1215180 in indicator-messages (Ubuntu) "Deprecated method call causes failing quaternourly release." [Critical,In progress] https://launchpad.net/bugs/1215180
[11:51] <seb128> larsu, ^ can you do that?
[11:52] <seb128> larsu, https://launchpadlibrarian.net/148154412/buildlog_ubuntu-saucy-i386.indicator-messages_13.10.1%2B13.10.20130822.1-0ubuntu1_FAILEDTOBUILD.txt.gz
[11:52] <seb128> larsu: same glib deprecation on gaction issues
[11:59] <Mirv> seb128: thanks if you have a chance to check the libhud-qt powerpc at some point
[11:59] <Mirv> (or libhud-qt-doc to be precise)
[12:02] <seb128> Mirv, sorry, today is another of those crazy pings days, doing that now
[12:03] <Mirv> seb128: yes, no hurry, that was both a thanks and a gentle reminder :)
[12:07] <Mirv> sil2100: part two https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/remove_obsolete_scopes_from_packages/+merge/181535
[12:26] <larsu> seb128: will fix right away (coming from lunch)
[12:27] <larsu> seb128: the real fix is to specify the glib version number, so that we don't get those warnings
[12:27] <larsu> and to diable -Werror *cough*
[12:28] <seb128> larsu, thanks, the new glib is in saucy-proposed if you need it
[12:28] <seb128> larsu, yeah, I still think having Werror and include deprecation warnings doesn't make sense
[12:28] <seb128> it's good to know about deprecations
[12:28] <seb128> but that should "stop the production line"
[12:28] <seb128> shouldn't*
[12:29] <larsu> seb128: exactly. GLib has macros for that (if you say you use 2.30, you won't get warnings about deprectations in 2.32)
[12:29] <larsu> I'll add them to indicator-messages
[12:30] <seb128> larsu, I've no strong opinion, is the intend to say "I targetted that version/verified with it"? it seems that's something that forces you to revisit the macro use every cycle
[12:30] <seb128> larsu, where most of the time things just work even on newer glib
[12:31] <seb128> I would rather go for "don't use the macro, don't stop build on deprecations, but report bugs when the CI find those warnings"
[12:32] <seb128> Mirv, libhud-qt moved to release
[12:32] <larsu> seb128: https://developer.gnome.org/glib/stable/glib-compiling.html shows all the possibilities (search for MIN_REQUIRED)
[12:33] <seb128> larsu, right, I'm not convinced it's useful, it seems like we want to get warnings about those so we know we need to update our code, just not stop build on them
[12:34] <seb128> larsu, oh well, I've no strong opinion either way either, so just do whatever feels right to you ;-)
[12:37] <larsu> seb128: I agree, but ted doesn't like turning off -Werror...
[12:38] <larsu> so either you convince him, or I'll just use MIN_REQUIRED and MAX_ALLOWED :P
[12:38] <seb128> larsu, or you could port the code to the current apis :p
[12:40] <seb128> larsu, did you guys talk about doing -Wno-error=deprecated-declarations ?
[12:41] <larsu> seb128: ya, ovbiously this is only so that this doesn't happen again in the future
[12:41] <larsu> seb128: no, that might be a viable alternative. Good idea.
[12:41] <seb128> larsu, let me talk to ted about that when he gets online
[12:41] <seb128> larsu, -Werror -Wno-error=deprecated-declarations seems like it should make everybody happy
[12:43] <Mirv> seb128: awesome!
[12:48] <seb128> larsu, https://code.launchpad.net/~seb128/indicator-messages/dont-werror-on-deprecated-declarations/+merge/181546 ... let's see when ted gets in
[12:49] <larsu> seb128: ah thanks :)
[12:51] <larsu> bbiab
[13:21] <tkamppeter> The package gksu has been removed from the standard installation of Ubuntu recently. Which package should I use as replacement? Or should I pull in gksu by a dependency?
[13:22] <tkamppeter> seb128, ^^
[13:22] <tkamppeter> seb128, bug 1209246
[13:22] <ubot2`> Launchpad bug 1209246 in hplip (Ubuntu) "HPlip gui doesn't handle authentication properly" [Undecided,New] https://launchpad.net/bugs/1209246
[13:23] <seb128> tkamppeter, we use pkexec instead
[13:27] <tkamppeter> seb128, how can I get a password window being popped up instead of a console password prompt?
[13:29] <seb128> tkamppeter, "pkexec <command>" should give you a graphical ui
[13:35] <tkamppeter> seb128, yes, what I did wrong is to run "pkexec <command>" in a terminal where I was SSHed into another machine. In a terminal on the local machine I get the GUI.
[13:35] <tkamppeter> seb128, thank you very much.
[13:35] <seb128> tkamppeter, yw!
[13:38] <Mirv> drafted https://blueprints.launchpad.net/ubuntu/+spec/client-1308-qt51 , not sure how to move forward as I don't know who's the Client track lead
[13:38] <seb128> Laney, how crazy is your afternoon? would you fancy updating ubuntu-wallpapers with the new images selected for 13.10? (you can consider that as sponsoring I guess :p)
[13:38] <Laney> i moved that to tomorrow
[13:38] <seb128> Mirv, I can accept it
[13:38] <Laney> but i could do something like that
[13:38] <seb128> Laney, question stands ;-)
[13:38] <seb128> Laney, ok, fwding you the email, thanks
[13:38] <Laney> i want to get some gsettings into security-privacy first though
[13:39] <Laney> let me tell you which ones i'm planning on doing and you can see if they make sense
[13:39] <Mirv> seb128: ok.
[13:40] <Laney> lock method, phone locking timeout (not lock on idle), sleep locks immediately, encryption, stats on welcome screen, messages on welcome screen
[13:44] <Laney> in lieu of accountsservice handling them ...
[13:45] <seb128> mterry, hey
[13:45] <seb128> Laney, let's get mterry in that discussion
[13:45] <mterry> seb128, hello!
[13:45] <seb128> mterry, how are you?
[13:45] <seb128> mterry, Laney is looking at the security-privacy settings and they have the greeter options we discussed some weeks ago
[13:45] <mterry> seb128, that's a question guaranteed to make me wary  :)
[13:45] <Laney> muhahaha
[13:45] <seb128> ;-)
[13:45] <Laney> basically we want to know where to store the settings
[13:46] <didrocks> Mirv: sil2100: kenvandine: cyphermox: robru: FYI, intel machine updated to latest kernel and rebooted on kernel's team demand
[13:46] <didrocks> let's hope :)
[13:46] <Laney> gsettings would be really easy but we heard you think it's best in accountsservice
[13:46] <cyphermox> ack
[13:46] <seb128> mterry, I guess we could do gsettings for v1, but I'm not sure how things are going to work the day we go multiuser
[13:47] <mterry> seb128, Laney: well.  If we store in gsettings, it's tricky to get them to the lightdm user
[13:48] <mterry> seb128, Laney: accountsservice solves that at least.  What's the problems you're considering with it?
[13:48] <seb128> mterry, I was wondering if we could use polkit to write to a system gsettings
[13:49] <seb128> mterry, I don't think we have problems/strong opinion, it's just that writting to gsettings is one line of qml :p
[13:49] <mterry> seb128, I'm not super familiar with system gsettings.  Is that just user-less settings?
[13:49] <mterry> seb128, with a plugin.  So is AccountsService  ;)
[13:49] <seb128> mterry, there is no "user less", but I guess we could write through polkit to the lightdm user config
[13:49] <seb128> mterry, do we have accountsservice qml bindings?
[13:49] <mterry> seb128, oh, didn't know if gsettings grew a capability
[13:49] <Laney> no qml
[13:49] <mterry> seb128, in a unity8 branch we do, not really a public module
[13:50] <Laney> but I don't think accountsservice has key-value stuff does it
[13:50] <seb128> mterry, we have gsettings qml bindings
[13:50] <mterry> Laney yeah it does these days
[13:50] <Laney> I don't really mind writing some cpp
[13:50] <Laney> oh really?
[13:50] <mterry> seb128, right
[13:50] <Laney> I still see a load of SetBlah methods
[13:50] <mterry> seb128, you'd need a daemon to do the writing to the lightdm gsettings, right?
[13:51] <Laney> accountsservice would be preferable to that imho
[13:51] <mterry> Laney, hold on...  let me link you to a branch that adds a key for unity8 edge-demo purposes
[13:51] <seb128> mterry, yeah, that would be code as well
[13:51] <seb128> accountsservice might make sense
[13:51] <mterry> Laney, https://code.launchpad.net/~mterry/unity8/demo/+merge/177923
[13:51] <Laney> what's that stuff desrt was talking about re: accountsservice?
[13:51] <mterry> Laney, that's a branch I'm working on for unity8.  It shows how to talk to accountsservice, and how to register new key/value pairs with AS
[13:52] <mterry> Laney, that's the stuff desrt was talking about
[13:52] <desrt> mterry: thanks for working on this :)
[13:52] <mterry> Laney: notice the changes to the plugins/Accountsservice directory
[13:52]  * mterry waves at desrt
[13:52] <seb128> Laney, that was added in https://launchpad.net/ubuntu/+source/accountsservice/0.6.34-0ubuntu1
[13:53] <seb128> hey desrt ;-)
[13:53] <desrt> hey
[13:54] <Laney> mterry: want to make this module public? ;-)
[13:55] <mterry> Laney, I'm not confident it's amazing enough.  Where do we put public modules like this?
[13:56] <Laney> not sure ...
[13:56] <mterry> Would need to change the API a bit too, to handle custom interfaces, instead of hardcoding
[14:00] <Laney> yeah
[14:01] <Laney> ok I'll copy it for now :P
[14:01] <Laney> mterry: have you defined the names of the properties for these things?
[14:02] <mterry> Laney, hm?  You mean like hte com.canonical.unity.AccountsService.xml file?
[14:02] <Laney> I don't know, do I?
[14:02] <mterry> Laney, so the important new files, besides the stuff to talk to dbus are:
[14:02] <mterry> com.canonical.unity.AccountsService.xml - defines new properties
[14:03] <Laney> I didn't know if it was just done dynamically
[14:03] <Laney> where can I get that file then?
[14:03] <mterry> com.canonical.unity.AccountsService.policy - defines who can access them
[14:03] <Laney> in unity8?
[14:03] <mterry> Laney, it's in my branch.  You make it for your stuff
[14:03] <Laney> but it needs to cooperate with the greeter
[14:03] <mterry> Laney, so you define your own interface, drop it in the right directory, and AS will pick it up and add it as a dynamic property
[14:03] <NikTh> Hello,
[14:04] <mterry> Laney, I don't know if you want to put it in unity8 or not.  This sounded more like a system-settings thing, r ight?
[14:04] <Laney> well s-s will set and unity8 will read
[14:04] <NikTh> Where is the 12.04.3 release announcement ? Expected 14 hours ago ...
[14:04] <Laney> guess it doesn't matter
[14:04] <Laney> NikTh: not out yet
[14:05] <Laney> there is no 'expected' time
[14:05] <NikTh> Laney: Do you know when ?
[14:05] <Laney> no, when it's ready
[14:05] <mterry> Laney, so sure.  s-s or whatever can drop that file in and greeter could just use dbus
[14:05] <NikTh> Laney: Yes there is.. https://launchpad.net/ubuntu/+milestone/ubuntu-12.04.3
[14:05] <Laney> mterry: right, so I shall just invent the names
[14:06] <Laney> NikTh: that is just the start of the UTC day, ignore it
[14:06] <mterry> Laney, keep in mind that while AS here is very useful, it has limited customization potential for system builders.  Like no default-overrides or lock-down support...  So if you need those, maybe a combo of AS and gsettings or something may help
[14:06] <Laney> you'll find no release has ever happened at that time
[14:06] <NikTh> Laney: Hah, right. UTC.
[14:07] <Laney> mterry: well, /I/ don't but who knows what OEM people will want?
[14:08] <Laney> hmm, that's kind of tough
[14:08] <Laney> I suppose it would be possible to dpkg-divert the interface file out of the way to install your own
[14:09] <mterry> Laney, OEM people always *could* do a dpkg divert yeah
[14:09] <mterry> Laney, :)
[14:09] <Laney> but then s-s will probably blow up
[14:09] <mterry> Laney, so that solves OEM, but not admins.
[14:09] <mterry> Laney, why would s-s blow up?  As long as OEM was only changing default values
[14:09] <Laney> as long as that, but if something's changed to read-only
[14:09] <mterry> Although, I hear dpkg diver was originally for admins, not packagers
[14:10] <Laney> yes
[14:10] <NikTh> Laney: When its ready, is not applicable in Ubuntu. Ubuntu has scheduled release dates : https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule
[14:10] <Laney> NikTh: when it's ready within the specified day
[14:10] <mterry> Laney, I think it's rare that people actually want to lock things down
[14:10] <NikTh> Laney: Thanks :-)
[14:10] <Laney> mterry: happy not to worry about that for now anyway
[14:11] <mterry> Laney, :)
[14:11] <Laney> there will still be ways for admins to do what they want
[14:11] <Laney> just might not be as easy as it could be
[14:11] <mterry> true
[14:12] <Laney> ok, let me propose some more UI and then work on this
[14:14] <Laney> ah, a thunderstorm
[14:14] <Laney> lovely
[14:14]  * didrocks sees blue sky with no cloud
[14:15] <mlankhorst> it's just damned hot here
[14:23] <tkamppeter> seb128, can you hel the HP guys with pkexec on bug 1209246? Thanks.
[14:23] <ubot2`> Launchpad bug 1209246 in hplip (Ubuntu) "HPLIP GUI doesn't handle authentication properly" [Undecided,Confirmed] https://launchpad.net/bugs/1209246
[14:23] <seb128> tkamppeter, what sort of help do they need?
[14:33] <NikTh> join #ubuntu-gr
[14:33] <NikTh> forgot the backslash :-P
[14:37] <tkamppeter> seb128, abou the correct call of pkexec, it seems that for the HP guy it asks for the root password and not for the password of the sudo user.
[14:38] <tkamppeter> seb128, I seeno that he broke out of the bug thread and only mailed my all in privacy. he wrote
[14:38] <tkamppeter> In Ubuntu root user won't be created by default and user will be having SUDO permissions. Whereas pkexec requires root password instead of Sudoers password.
[14:38] <tkamppeter> However, this can be achieved by "pkexec --user<USER> <command>".
[14:39] <Laney> I bet he enabled his root account or something
[14:39] <Laney> it asks for my user password here
[14:41] <seb128> tkamppeter, see https://code.launchpad.net/~mterry/update-notifier/pkexec/+merge/146003 as an example
[14:41] <tkamppeter> seb128, for me it works correctly when running in a terminal, asking for the user password, as with Laney.
[14:41] <Laney> ask for his hplip WIP and see what happens for you
[14:41] <seb128> tkamppeter, right, we don't have root on Ubuntu, they probably hacked their config
[14:42] <jbicha_> sabdfl has root on Ubuntu though ;)
[14:42] <seb128> ;-)
[14:42] <seb128> jbicha_, hey
[14:45] <tkamppeter> seb128, or the HP guy wants to pop up a window from a UDEV-triggered process which is running as root. This process would have to find out which user is currently logged in on the desktop and then set the DISPLY and XAUTHORITY variables and run the "pkexec <commmand>" as the appropriate user.
[14:46] <seb128> tkamppeter, sorry, I don't know more about that and I've ton of others things I need to get done today, maybe ask on #ubuntu-devel
[14:47] <tkamppeter> seb128, sorry, that I asked you, should I perhpas better ask the X guys?
[14:48] <seb128> it's not an X thing
[14:48] <seb128> try asking mdeslaur/security team
[14:53] <xnox> tkamppeter: I had usb-creator-gtk popping up on the default user desktop using upstart job file. it has been removed but an example should be in history.
[14:54] <xnox> (when a flashable nexus7 was attached)
[14:55] <xnox> tkamppeter:
[14:55] <xnox> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/usb-creator/saucy/view/72/debian/usb-creator-gtk.upstart
[14:55] <xnox> adjust a UDEV event & the bits to execute.
[14:56] <Laney> would be quite limited in its scope though
[14:56] <xnox> tkamppeter: you cannot do this from udev.rules, because udev rules have timeouts and your process will be killed.
[14:56] <xnox> (10seconds ?!)
[14:57] <xnox> Laney: well, the udev rule can executed "start --no-wait launch-user-program PROG=foo" and the launch-user-program.conf is wrapper to find current user and execute $PROG to make it more generic.
[14:58] <xnox> tkamppeter: you can't launch graphical programs using pkexec, without adding policykit files to allow that. And pkfile will need paths as to which commands you are executing...... so stick to sudo.
[15:00] <sil2100> seb128: thanks for the review
[15:00] <seb128> sil2100, yw
[15:00] <seb128> cyphermox, Mirv, sil2100: indicator-messages build fix is in, can we get the indicator stack retried?
[15:00] <sil2100> seb128: I saw some build-depends unneeded, like the libicu, but well
[15:01] <sil2100> seb128: let me take care of that in a moment then
[15:01] <seb128> thanks
[15:10] <sil2100> seb128: pushed the removal of unused build-deps - if you could approve, I will approve globally
[15:12] <seb128> sil2100, done
[15:16] <sil2100> seb128: thanks!
[15:17] <tkamppeter> xnox, is there a replacement for the getXconsole() function of /usr/share/acpi-support/power-funcs? I have another place whwere I wantr a system process to determine which user is currently logged in on the desktop.
[15:18] <Laney> logind knows the display
[15:18] <xnox> tkamppeter: it was the best I could find, which is also widely available. Of course that may not be true in the future with Mir, etc. And my script was before logind api was in place.
[15:19] <tkamppeter> xnox, the file /usr/share/acpi-support/power-funcs has gone away in Saucy, therefore I am asking for a replacement. Or is it a general security risk for system processes to know the user who is currently logged in?
[15:21] <xnox> tkamppeter: i guess you should use logind, but that will not work on precise..raring though. You are root already, so I don't see what security risk there is to launch an app in front of the user.
[15:22] <xnox> (preferably with dropped priviliges down to the user, don't just launch root apps to the user & thus opening root account for the user just because something got plugged in)
[15:23] <xnox> tkamppeter: i raise my security questions on #ubuntu-hardened and usually get sensible replies =)
[15:24] <tkamppeter> xnox, do we have both systemd and Upstart in Saucy now?
[15:24] <xnox> tkamppeter: no, we do not have systemd. We have upstart, and we have logind.
[15:25] <xnox> tkamppeter: we dropped consolekit in favor of logind.
[15:26] <xnox> "systemd" is "systemd init" and myriad of other daemons (udev, logind, syslogd, datetimed, and so on and so forth)
[15:59] <seb128> sil2100, did you say you would retry the indicator stack? how is that going?
[16:00] <sil2100> seb128: oh, I see some red and yellow, let me check that
[16:01] <sil2100> seb128: in the meantime - did almost the same changes for another package, needs review: https://code.launchpad.net/~sil2100/messaging-app/packaging_review/+merge/181600
[16:01] <sil2100> I look at indicators
[16:03] <sil2100> seb128: looks like a failing unit test now... https://launchpadlibrarian.net/148175184/buildlog_ubuntu-saucy-i386.indicator-messages_13.10.1%2B13.10.20130822.3-0ubuntu1_FAILEDTOBUILD.txt.gz
[16:04] <sil2100> tedg: ^
[16:05] <tedg> sil2100, Yes, that should go away when seb128's patch lands
[16:05] <sil2100> seb128: eh, there also seem to have been direct pushes to the archive of indicator-datetime, the trunk needs to be synced
[16:05] <robru> kenvandine, can I get you to approve this quickly? it's quite trivial https://code.launchpad.net/~robru/friends/disable-contacts-sync/+merge/181386
[16:06] <tedg> sil2100, Unfortuantely that was probably after the run started
[16:06] <sil2100> tedg: hm, I re-ran the stack, so I thought that it's in already
[16:06] <tedg> sil2100, Can we kick it off again manually?
[16:06] <sil2100> tedg: I'll just fix up indicator-datetime and let's re-run
[16:07] <tedg> sil2100, Can I see what revision?
[16:07] <didrocks> seb128: https://code.launchpad.net/~didrocks/ubuntu-system-settings/daemon-api-update-and-visual-refresh/+merge/181605
[16:07] <sil2100> tedg: it seems to have seb128's change in already, as the changelog says: * don't error out on deprecated declarations.
[16:08] <sil2100> tedg: and it passed on all besides i386
[16:08] <didrocks> hum
[16:08] <sil2100> Maybe some flacky test?
[16:08] <didrocks> thanks lp-propsoe :/
[16:08] <tedg> Hmm, that's odd
[16:08] <didrocks> fixed
[16:08] <tedg> sil2100, I bet it's because it's not a cpp flag
[16:08] <tedg> :-/
[16:09] <sil2100> https://launchpadlibrarian.net/148173982/indicator-messages_13.10.1%2B13.10.20130822.2-0ubuntu1_13.10.1%2B13.10.20130822.3-0ubuntu1.diff.gz <- this is the diff of the last revision, so looks ok
[16:09] <sil2100> seb128: ^
[16:12] <seb128> sil2100, yes
[16:12] <seb128> sil2100, -datetime, didrocks said there was a command line flag to override that and publish anyway
[16:13] <didrocks> s/publish/build/
[16:13] <seb128> tedg, ?
[16:13] <sil2100> seb128: so no need of adding that manually in the changelog?
[16:13] <seb128> tedg, my fix works, I verified locally, that build failed in "FAIL: test-client.py"
[16:13] <sil2100> Since I think it would be good to have
[16:13] <seb128> sil2100, your call
[16:13] <tedg> seb128, Oops, misread.
[16:13] <Laney> the daily release will have it in the changelog anyway
[16:13] <Laney> I wouldn't bother
[16:13] <seb128> tedg, I wish we didn't hide the output of tests by default though :/
[16:15] <sil2100> Laney: but I guess the 12.10.3+13.10.20130731-0ubuntu3  entry will be missing
[16:15] <Laney> yes
[16:15] <Laney> just saying that I wouldn't care about that if I were you
[16:15] <sil2100> And 12.10.3+13.10.20130731-0ubuntu2, which might anger the daily-release bot
[16:15] <Laney> we often lose changelog entries while rebasing
[16:15] <seb128> sil2100, didrocks said you can override the angry bot
[16:15] <seb128> sil2100, but as said, your call
[16:16] <sil2100> didrocks: green flag for SKIP_PREPARE_CHECKS in this case?
[16:17] <didrocks> sil2100: wfm
[16:17] <seb128> tedg, just got make check to fail locally on the same test: http://paste.ubuntu.com/6014566/
[16:17] <didrocks> sil2100: don't do it on the whole stack
[16:17] <didrocks> sil2100: just on the that one
[16:17] <sil2100> Right, just on one component
[16:17] <didrocks> yep
[16:17] <seb128> tedg, fails this way 1 every 5 run
[16:17] <didrocks> this is the seb128's option :p
[16:18] <sil2100> ;)
[16:18] <seb128> ;-)
[16:18] <sil2100> seb128, tedg: I might do a re-run and publish anyway if it's just a flacky test - would be semi-nice, but at least the release would happen
[16:18] <tkamppeter> xnox, thank you very much. loginctl works great.
[16:18] <sil2100> By re-run I mean re-build in PPA
[16:18] <seb128> sil2100, right, please try a re-run
[16:18] <didrocks> sil2100: you are the first one to use it, I hope it will work :)
[16:19] <xnox> tkamppeter: well, thank Laney =)
[16:19] <sil2100> ;p
[16:19] <Laney> tkamppeter: you're parsing loginctl? you know it has a d-bus api right?
[16:19] <sil2100> seb128: ACK, will tell you how it goes
[16:19]  * Laney wonders what QtCreator does to eat up his compose key
[16:23] <didrocks> sil2100: can you please ensure you run it now, like NOW? I will be busy/leaving soon ;)
[16:24] <tkamppeter> Laney, I am parsing it for a shell script, can I access D-Bus APIs also easily out of a shell script?
[16:24] <sil2100> didrocks: ACK! ;) Wanted to wait for -messaging to finish
[16:24] <didrocks> sil2100: hum, why? it will pick it up where it is, right?
[16:25] <sil2100> Well, if the build fails again then the build step will fail again
[16:25] <sil2100> And another re-run would be needed ;)
[16:25]  * sil2100 launches
[16:26] <seb128> Laney, updated your mp again, I've no strong opinion on the button, for the plural form see the tab in http://doc.qt.digia.com/qq/qq19-plurals.html
[16:26] <seb128> Laney, examples are better ;-)
[16:26] <Laney> they are
[16:26] <Laney> let me see that
[16:26] <seb128> Laney, see polish, you can't have 1 translations for the plural
[16:26] <seb128> it depends of the count value
[16:26] <Laney> does i18n.tr get this right?
[16:27] <seb128> yes, it goes through gettext
[16:27] <Laney> right, let's use that then
[16:28] <sil2100> didrocks: I guess it worked!
[16:28] <sil2100> didrocks: 2013-08-22 16:25:46,384 INFO Skip destination version and conditional checking requested. Will overwrite even if destination has a newer version or the (optional) condition isn't met.
[16:28] <didrocks> sil2100: \o/
[16:28] <sil2100> \o/
[16:29] <didrocks> I should have written "bye bye changelog (seb128)" ;)
[16:32] <kenvandine> robru, done
[16:34] <seb128> kenvandine, robru: is /usr/share/session-migration/scripts/install-default-webapps-in-launcher.py hitting
[16:34] <seb128> GLib-GIO-ERROR **: The mapping function given to g_settings_get_mapped() for key 'favorites' in schema 'com.canonical.Unity.Launcher' returned FALSE when given a NULL value.
[16:34] <seb128> known?
[16:34] <seb128> that happens at every guest session start here, it's annoying
[16:41] <tedg> seb128, Is there a reason that glib 2.37.6 is still in proposed?
[16:41] <tedg> seb128, Surprised that I can't get it easily.
[16:41] <seb128> tedg, buggy britney/autopkgtests
[16:41] <seb128> and cjwatson and jibel are on holidays
[16:41] <tedg> seb128, Just to be curious, how do you know that?
[16:41] <seb128> Laney, maybe you should force it in?
[16:41] <Laney> i'll force it
[16:41] <Laney> lolz
[16:42] <seb128> tedg, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[16:42] <Laney> been distracted by other things
[16:42] <seb128> Laney, thanks ;-)
[16:42] <seb128> tedg, look for glib on there
[16:42] <tedg> Wow, that's a bigger list than I imagined...
[16:43] <seb128> tedg, that's step 1 of the migration, those which are valid candidates can be blocked on transitions, that's http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt
[16:43] <seb128> tedg, https://wiki.ubuntu.com/ProposedMigration has the details
[16:44]  * tedg didn't expect to learn this much today
[16:49] <Laney> seb128: pushed again, check now
[16:50] <Laney> I get a file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/ListItems/ValueSelector.qml:174: Unable to assign [undefined] to QString
[16:50] <Laney> in battery, not sure if that was there before
[16:50] <Laney> can't see what is wrong though
[16:55] <Laney> glib2.0 has slid on down into release
[16:56] <seb128> Laney, I wonder if that's due to the buggy upower, I've been adapting my code for pitti's fix that didn't land yet
[16:58] <Laney> could be
[16:58] <didrocks> kenvandine: some of the phone apps are listed in the spreadsheet, do not hesiate to update it
[16:59]  * didrocks waves good evening
[17:00] <seb128> didrocks, 'night
[17:00] <Laney> see you didrocks
[17:00] <didrocks> seb128: thanks! good luck to you ;)
[17:00] <seb128> didrocks, I'm about to submit your mp with some needs fixing, I guess for tomorrow
[17:00] <didrocks> seb128: don't comment too much on my MP :p
[17:00] <Laney> DELETE IT ALL AND START AGAIN
[17:00] <didrocks> bye Laney ;)
[17:00] <seb128> didrocks, hehe, I've already quite some comments, and I'm just doing a quick reading
[17:00] <didrocks> Laney: buttttt :p
[17:00] <seb128> it's hard to review that much changes :/
[17:01] <didrocks> seb128: let's see how it can get better tomorrow morning ;)
[17:01] <seb128> didrocks, sure
[17:01] <seb128> have a nice evening!
[17:01] <didrocks> thanks, you too!
[17:02]  * Laney sniggers at seeing a screenshot on G+ of touch with the snail wallpaper
[17:03] <seb128> haha
[17:03] <Laney> my plan for slimy world domination begins
[17:03] <seb128> Laney, hum
[17:04] <seb128> Laney, how much do you hate me if I ask you to do the battery plural form in another mr? ;-)
[17:04]  * Laney moans
[17:05] <seb128> Laney, I'm also not sure why you do "After %1 minute".arg(10)" rather than "After 10 minutes"
[17:05] <Laney> so that you only get the string once to translate
[17:05] <seb128> oh, that might actual work ;-)
[17:05] <seb128> clever
[17:06] <Laney> i just thought i'd stop making assumptions like "oh, 10 will never be singular" and do the same thing to all of them
[17:06] <Laney> let me revert battery then :(
[17:06] <seb128> Laney, don't bother
[17:07] <seb128> Laney, but next time please split different logical changes in different mrs
[17:07] <Laney> yeah i should have
[17:07] <Laney> i was thinking in "fixing plural" mode not "security-panel-ui" mode
[17:07] <robru> kenvandine, thanks!
[17:07] <seb128> Laney, I also note you didn't like my idea of the disabled button to show non implemented bits :p
[17:08] <Laney> hum?
[17:08] <Laney> I did do that didn't i?
[17:08] <seb128> doh
[17:08] <seb128> Laney, I got confused by the fact that put all the changes in 1 commit
[17:08] <Laney> maybe I failed to push
[17:08] <seb128> Laney, no, it's there
[17:09] <seb128> the commit says "
[17:09] <seb128>     Use plural translations (hopefully) correctly
[17:09] <seb128>     and minor other fixes
[17:09] <seb128> "
[17:09] <seb128> and it's one commit
[17:09] <Laney> oh yeah
[17:09] <Laney> does bzr have something like bzr add -p?
[17:09] <Laney> to let you pick bits to commit
[17:09] <seb128> what would that do?
[17:09] <seb128> I think there is bzr shelve to do similar stuff, but I never tried it
[17:10] <Laney> in git it interactively asks you which hunks to stage
[17:10] <Laney> quite convenient
[17:10] <seb128> http://doc.bazaar.canonical.com/latest/en/user-guide/shelving_changes.html
[17:10] <seb128> seems similar
[17:11] <robru> seb128, re: that python bug, the fix for that landed in trunk, but it seems to be stuck in -proposed for some reason.
[17:11] <seb128> robru, what package is that?
[17:11] <Laney> seb128: let me fix those commits
[17:11] <Laney> you made me feel naughty now
[17:11] <robru> seb128, webapps-applications
[17:11] <seb128> Laney, haha, put it back to needs review then :p
[17:12] <seb128> robru, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt
[17:12] <seb128> robru,
[17:12] <seb128> skipped: webapps-applications (69 <- 1)
[17:12] <seb128>     got: 91+0: i-91
[17:12] <seb128>     * i386: unity-webapps-angrybirds, unity-webapps-cuttherope, unity-webapps-lordofultima, unity-webapps-tiberiumalliances
[17:12] <seb128> robru, the update is making the binaries listed there non installable
[17:12] <seb128> that's why
[17:13] <robru> seb128, yes... that's on purpose. those packages are no longer supported and we changed the packaging to force-uninstall them
[17:13] <seb128> robru, so you should request them to be removed from the archive
[17:13] <robru> I'm pretty sure I did that already.
[17:13] <seb128> https://bugs.launchpad.net/ubuntu/+source/unity-webapps-angrybirds has no open bug
[17:13] <seb128> well one about icon, no removal request
[17:13] <seb128> do you have the number?
[17:15] <Laney> ok, pushed again with --overwrite
[17:16] <robru> seb128, buh, I can't find it. i swear i filed bugs about these and some archive admin told me to ensure I had Breaks: lines in the packaging...
[17:16] <robru> seb128, I gotta run but I'll file new bugs for those when I get back from lunch. sorry!
[17:17] <seb128> robru, bug #1198285 you mean?
[17:17] <ubot2`> Launchpad bug 1198285 in unity-webapps-googlereader (Ubuntu Saucy) "Google Reader has shut down; please remove this from the archive." [Medium,Fix released] https://launchpad.net/bugs/1198285
[17:17] <seb128> robru, you didn't do it for the others afaik
[17:17] <seb128> robru, thanks, and no problem
[17:17] <robru> seb128, i was pretty sure I did but I guess i'm hallucinating. ok bbl
[17:20] <tkamppeter> sarnold, hi
[17:21] <sarnold> hello tkamppeter :)
[17:22] <tkamppeter> sarnold, did you already have a look into bug 711061? openjpeg needs to go into main for Ghostscript 9.09 to get into the release.
[17:22] <ubot2`> Launchpad bug 711061 in openjpeg (Ubuntu) "[MIR] libopenjpeg2" [High,Confirmed] https://launchpad.net/bugs/711061
[17:22] <sarnold> tkamppeter: not yet, sorry, but it is not forgotten.
[17:27] <tkamppeter> sarnold, OK, thanks, I only wanted to know whether it gets done before FF.
[17:42] <seb128> sil2100, can we block indicators to be published somehow?
[17:42] <seb128> cyphermox, ^
[17:43] <sil2100> What do you mean blocked?
[17:43] <sil2100> i.e. not publishing anymore?
[17:44] <sil2100> Or you want it to be set to manual publishing all the time?
[17:44] <seb128> sil2100, ignore that, I saw https://code.launchpad.net/~sergiusens/indicator-messages/phablet_epoch/+merge/181604 and I went wth
[17:44] <seb128> but it's on their ppa only
[17:45] <sil2100> Right, phablet
[17:45] <sil2100> ;)
[17:45] <sil2100> Ok guys, need to jump out now, but I'll be back for a moment in ~1 hour
[17:45] <seb128> sil2100, btw what happened to indicators being published?
[17:46] <seb128> some people are going to get really unhappy if the converged indicator-messages doesn't land
[17:46] <sil2100> seb128: ah, check job failed, shit... extra packages
[17:46] <sil2100> I can *force* a publishing if you want, but that won't be too nice
[17:47] <seb128> sil2100, can you look at fixing it properly in 1h or hand it over to cyphermox?
[17:47] <sil2100> I can fix it properly now, but it would have to be released on the next tick then
[17:47] <sil2100> Or we'll miss this tick now
[17:47] <seb128> that's ok
[17:49] <sil2100> Ah, I get it what's wrong now
[17:50] <sil2100> seb128: I'll make sure the next tick publishes indicators
[17:51] <sil2100> bbl
[19:19] <tedg> fginther, I'm a bit confused on this error: https://jenkins.qa.ubuntu.com/job/cu2d-indicators-head-1.1prepare-indicator-appmenu/417/console
[19:19] <tedg> Networking hickup?
[19:20] <fginther> tedg, looking
[19:21] <fginther> tedg, that would be my guess, I see several other builds with a similar stacktrace
[19:24] <tedg> fginther, Is it just a "kick it again" thing then?
[19:25] <fginther> tedg, I think so, I can't do it, but cyphermox, kenvandine, mterry may be able to
[19:27] <tedg> If they all kick it as the same time does it work better?  :-)
[19:45] <Sweetshark> pitti: are you all set for the raring/precise SRUs or do you still miss something?
[20:08] <Sweetshark> hmmm, virtualbox not starting machines on saucy because of some network foo. known issue or workarounds?
[20:24] <howefield> Sweetshark: are you using bridged adapter ? if so change it to NAT
[20:29] <Sweetshark> howefield: thanks, just try-n-errored that myself ;)
[20:29] <sil2100> Damn, what happened to indicators?
[20:30] <howefield> started a few days ago after an update.
[20:32] <Sweetshark> howefield: same here -- it worked yesterday for me