[04:12] <m4n1sh> does ubuntu have libgit2-glib packaged? I can't find so
[04:34] <pitti> Good morning
[06:22] <pitti> didrocks: bonjour! ça va ?
[06:23] <didrocks> pitti: ça va bien, et toi?
[06:23] <pitti> didrocks: ça va bien aussi
[06:23] <pitti> didrocks: I'm enjoying the PS autolanding machinery
[06:23] <pitti> it's effing awesome!
[06:23] <pitti> (the upstream parts for now)
[06:24] <pitti> i. e. the PS jenkins bot verifying my branches, and automerging them, and adjusting the bugs accordingly
[06:24] <pitti> ♪ it's a kind of maaa-giiiic ♫
[06:24] <pitti> didrocks: anyway, I'm currently fixing my ap-gtk tests for raring, and I stumbled over something odd
[06:25] <didrocks> heh :) excellent!
[06:25] <pitti> didrocks: in saucy, some programs reverted back to having an integrated menu, like gtimelog or my hello_color.py test program
[06:25] <didrocks> they were in some kind of backlist before?
[06:25] <pitti> didrocks: in raring they have a global menu, which makes the GtkMenuItem widgets not "really" appear
[06:25] <pitti> didrocks: so, do you know, is that a deliberate change, or is it a regression?
[06:25] <didrocks> yeah, now we are using unity-gtk3-module
[06:26] <didrocks> pitti: it's developped by attente
[06:26] <didrocks> feel free to ping him about it :)
[06:26] <didrocks> (and adding a test :p)
[06:26] <pitti> didrocks: it certainly feels like a regression to me, but I wasn't sure whether perhaps these days global menu is limited to GMenuModel
[06:26] <pitti> gtimelog and my hello program don't use that (I don't know how that works, TBH)
[06:26] <didrocks> pitti: this is why autopilot-gtk fails to build I guess, due to tests :)
[06:27] <didrocks> like https://launchpadlibrarian.net/143526534/buildlog_ubuntu-saucy-armhf.autopilot-gtk_1.3daily13.06.05bzr47saucy0_FAILEDTOBUILD.txt.gz
[06:27] <didrocks> pitti: no, it's merging both
[06:27] <didrocks> AFAIK
[06:27] <pitti> didrocks: no, like https://launchpad.net/~autopilot/+archive/ppa/+build/4748902/+files/buildlog_ubuntu-raring-i386.autopilot-gtk_1.3daily13.06.05bzr46raring0_FAILEDTOBUILD.txt.gz
[06:27] <darkxst> pitti, hi
[06:27] <pitti> didrocks: actually, not that either, that's just because raring's gnome-session-log is different
[06:27] <didrocks> well, similar to the FTBFS in the unity-build ppa
[06:27] <didrocks> ah?
[06:27] <didrocks> hey darkxst
[06:28] <pitti> didrocks: it only happens if you run the test under a full unity; the tests under xvfb are fine, as there you don't have a global menu
[06:28] <darkxst> hi didrocks
[06:28] <pitti> didrocks: oh, is that from a distro autolanding attempt?
[06:28] <pitti> hey darkxst
[06:28] <didrocks> pitti: right
[06:28] <didrocks> pitti: the QA stack is rejected because of this FTBFS
[06:28] <darkxst> pitti, any chance you can look into the retracer sometime soon?
[06:29] <pitti> didrocks: not sure what's wrong with that test; I never got a negative ID here (and it's certainly not a bug in the test)
[06:29] <pitti> didrocks: thanks for pointing out, let's see how the next attempt goes; today I'm landing actual fixes, not just tests
[06:30] <pitti> darkxst: argh, that; sorry, it keeps being pushed down in my list :/
[06:30] <pitti> didrocks: ah, I just got those FTBFS mails
[06:31] <didrocks> pitti: ok, let's see ;)
[06:32] <pitti> same on armhf
[06:33] <pitti> didrocks: they all pass all the time in the PS Jenkins bot runs; do you see a fundamental difference between those and the autopilot archive?
[06:33] <didrocks> pitti: they don't use a real PPA
[06:33] <pitti> didrocks: oh, of course -- the autopilot GTK potentially has newer/changed/broken dependencies?
[06:33] <didrocks> it's just a pbuilder
[06:33] <didrocks> pitti: also yeah
[06:33] <pitti> when I do my tests in sbuild, I only build autopilot-gtk on saucy
[06:34] <pitti> not on saucy + the autopilot PPA
[06:34] <didrocks> pitti: I don't know about the autopilot PPA
[06:34] <pitti> I bet/hope that's the difference
[06:34] <didrocks> I think it's stupid they are using it, but it's another story :
[06:34] <didrocks> :)
[06:34] <didrocks> (already told them, and they don't care)
[06:34] <didrocks> daily-build PPA has new QA stack content, right
[06:34] <didrocks> (the ~ubuntu-unity/daily-build)
[06:34] <pitti> well, I got https://launchpad.net/~autopilot/+archive/ppa/+build/4750560, that's similar to the build log you gave me, right?
[06:36] <didrocks> pitti: yeah, but TBH, I just care about the ppa I support to get into distro (maybe things didn't get build in the same order ;))
[06:36] <pitti> didrocks: ok, so this is not the distro autolanding, and won't block it?
[06:36] <pitti> didrocks: so, I'll try here with the autopilot PPA, this might point to a regression in trunk which hasn't landed in the distro yet
[06:37] <didrocks> pitti: we have the same failure (see my first log) in the daily-build ppa
[06:37] <pitti> didrocks: ah, ok
[06:37] <didrocks> pitti: so I guess it's a regression part from a part of the QA stack (maybe autopilot itself)
[06:38]  * pitti ♥ tests
[06:40] <darkxst> pitti, would be really useful! we still getting a lot of crash reports from raring+ppa which are most likely relevant to saucy
[07:04] <jibel> good morning
[07:12] <didrocks> salut jibel!
[07:13] <jibel> Salut didrocks , ça va?
[07:17] <didrocks> ça va bien, et toi? :)
[07:18]  * didrocks just finished cleaning a little bit lightdm
[07:19] <jibel> didrocks, pas mal, je continue avec l'autolanding sur touch, en esperant que le fix kernel arrivera aujourd'hui
[07:19] <didrocks> jibel: ah, cool! ils modifient la config donc?
[07:19] <didrocks> (pour grouper)
[07:20] <jibel> didrocks, yes, it has been fixed yesterday, next upload will have it.
[07:40] <seb128> hey desktopers
[07:40] <pitti> it's a seb, run!
[07:40]  * pitti donne une accolade à seb128, bonjour !
[07:42] <seb128> pitti, good morning freedom lover! ;-)
[07:42]  * seb128 donne une accolade à pitti en retour, ça va bien ?
[07:42] <pitti> seb128: oui, merci
[07:47] <pitti> didrocks: so wrt. the weird negative ID, I saw that in the autopilot PPA armhf build logs sometimes (but not always, e. g. the latest saucy build there worked fine)
[07:47] <pitti> didrocks: did you ever see this on non-armhf?
[07:47] <didrocks> pitti: weird, as you can see, it seems to happen everytime in the daily-build PPA (all archs)
[07:47] <didrocks> let me look, one sec
[07:47] <didrocks> salut seb128!
[07:47] <pitti> didrocks: oh, do you have a link to the PPA?
[07:47] <didrocks> https://launchpad.net/~ubuntu-unity/+archive/daily-build
[07:48] <didrocks> pitti: ah no, latest build :)
[07:48] <pitti> didrocks: I want 1.3+13.10.20130627-0ubuntu1 , not 0.4daily13.03.11-0ubuntu1 , right?
[07:48] <didrocks> I just did the autopilot-gtk ppa
[07:48] <didrocks> saw*
[07:48] <didrocks> pitti: yeah, so everything's fine here :)
[07:48] <pitti> didrocks: 7 hours ago, all pass
[07:49] <didrocks> pitti: yeah, getting too much random ppa by subscription emails
[07:49] <didrocks> I read the ones from the autopilot PPA as daily-build PPA, sorry :)
[07:49] <pitti> didrocks: I am currently running package builds in my i386 saucy sbuild with the autopilot PPA enabled, so far I got 2/2 passes
[07:49] <pitti> didrocks: ok, then we are on the same page
[07:49] <pitti> didrocks: some weirdness in the emulated armhf PPA builders then?
[07:50] <pitti> didrocks: so the next automatic daily build will pick up the fixes, add changelogs, and upload to saucy?
[07:50] <didrocks> pitti: seems so… yeah for not reliable environment :)
[07:50] <didrocks> pitti: this one should, let me see before sil2100 starts his day why QA didn't get published yet
[07:50] <pitti> didrocks: no hurry, I'm currently landing some more fixes
[07:51] <didrocks> pitti: manual publishing :)
[07:51] <pitti> didrocks: I guess I messed up the commit logs of my first two MPs a bit, as I added an (LP: #XXXX) into the commit message in the MP
[07:51] <didrocks> pitti: so tests pass, everything built, integration tests pass, it's just in manual publishing as there are packaging mode
[07:51] <pitti> didrocks: so I guess it'll end up there twice (but it's mostly cosmetic)
[07:51] <didrocks> pitti: so once sil2100 reviewed those, it will be published in distro
[07:51] <pitti> didrocks: sorry for all these questions, this is still a bit new to me
[07:51] <didrocks> hum, shoudln't be duplicated :)
[07:52] <didrocks> if you touch debian/changelog, in a MP, I don't readd the commit message
[07:52] <didrocks> pitti: see the generated changelog: http://paste.ubuntu.com/5803964/
[07:53] <didrocks> ah, you meant, you added the number into the commit message :)
[07:53] <pitti> didrocks: no, I added it to the "commit message" in the MP, not d/changelog
[07:53] <didrocks> pitti: nice test case to add to avoid that duplication
[07:53] <pitti> didrocks: right; so it appears twice there
[07:53] <pitti> didrocks: sorry about that, I won't add it in future MPs
[07:53] <didrocks> pitti: no worry, I'll handle that case ;) Most of people using that LP: # syntax does directly in debian/changelog
[07:54] <didrocks> so I didn't get that case, interesting one :)
[07:54] <didrocks> should be easy to fix, for future uploads, let me have a try
[07:55] <pitti> didrocks: if it didn't happen until now, don't worry; I won't do it again :)
[07:55] <didrocks> pitti: in fact, I don't reduplicate the bug if you listed it manually already, but in that case, both were injected at the same time :)
[07:56] <didrocks> I can fix that easily I guess, let me have a try later today
[08:00] <sil2100> didrocks: it's in manual publishing mode, checking what's up - I'll publish it once you ACK the packaging changes ;) http://10.97.0.1:8080/view/cu2d/view/Head/view/QA/job/cu2d-qa-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_autopilot-gtk_1.3+13.10.20130627-0ubuntu1.diff
[08:00] <sil2100> didrocks: btw. I think Thomi and Chris might be ignoring my e-mails!
[08:01] <didrocks> sil2100: I'm not sure I'll approve pitti's packaging changes :p
[08:01] <sil2100> didrocks: since I sent them like 2 e-mails about autopilot issues and they didn't answer me even once
[08:01] <didrocks> sil2100: but wait, there is a trailing comma after the deps! ok, let's +1 then :)
[08:01] <sil2100> thomi: veebers: ?
[08:01] <pitti> didrocks: haha
[08:01] <sil2100> hehe
[08:01]  * didrocks hugs pitti
[08:01] <seb128> hey sil2100
[08:01] <sil2100> Hey seb128
[08:01] <didrocks> sil2100: yeah, I know as well that some other people contacted them and no answer… do we still need them for anything?
[08:02] <pitti> sil2100, didrocks: btw, your last daily build only has the test suite, but none of the actual fixes (these just landed a few hours ago, and I'm currently working on the last bug fix)
[08:02] <pitti> so no hurry
[08:02] <didrocks> ok
[08:02] <sil2100> didrocks: there's that 'show_desktop' issue with autopilot still I see ;/ The indicators stack is haunted by that
[08:02] <seb128> didrocks, when is Mirv back? next week? do you know if landing  qtsystems to the archive is planned?
[08:02] <didrocks> seb128: he's back next week yeah. He has a task for qtsystems
[08:03] <Laney> morning!
[08:03] <didrocks> sil2100: argh, it's annoying… did you know about one commit showing that issue?
[08:03] <seb128> Laney, howdy
[08:03] <didrocks> sil2100: if so, we have given them enough time and we can revert it
[08:04] <seb128> Laney, https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1194123 ... look at the 2 most recent comments
[08:04] <ubot2`> Ubuntu bug 1194123 in gtk+3.0 (Ubuntu) "[gcc-linaro wrong-code regression] gcc 4.8.1-2ubuntu1 to 4.8.1-3ubuntu1 breaks gtk on armhf" [High,New]
[08:04] <sil2100> didrocks: not sure, but since I can't contact the AP guys, I'll look into that and try finding when it got broken, or maybe work-around it somehow
[08:04] <sil2100> didrocks: in the meantime: http://10.97.0.1:8080/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_platform-api_0.18.1+13.10.20130627-0ubuntu1.diff <- could you ACK? It's a risky change, but I guess it's necessary
[08:05] <didrocks> sil2100: yeah, let's first move on all the other stacks :)
[08:06] <didrocks> sil2100: we built with it until now, so reverting isn't risky (and it broke ABI for them), so +1
[08:09] <sil2100> didrocks: ok, published everything that I could - the media stack seems to have one flacky test that's failing on -ati all the time, I'll try fetching renato or Omer to look into that
[08:09] <sil2100> Since re-running the test suite didn't help
[08:10] <didrocks> sil2100: perfect! thanks :)
[08:10] <didrocks> sil2100: so everything is ok but indicators and unity, right?
[08:10] <didrocks> because of this AP thingy…
[08:11] <sil2100> Yes, and media - but I'll check why it's failing and maybe try publishing anyway if it's not anything obviously broken maybe
[08:12] <didrocks> sil2100: ok ;) and something else, seb128 asked to revert the oif stack
[08:12] <didrocks> sil2100: in raring
[08:12] <didrocks> sil2100: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1194714
[08:12] <ubot2`> Ubuntu bug 1194714 in eog (Ubuntu) "eog crashes on startup" [Undecided,New]
[08:12] <seb128> didrocks, infinity: infinity deleted the libgrip update from -proposed on my request
[08:12] <didrocks> sil2100: that's why the oif stack is in manual publishing mode (it rebuilt as there is a diff with the revert)
[08:13] <seb128> ups
[08:13] <seb128> sil2100, ^
[08:13] <seb128> infinity, sorry for the ping :p
[08:13] <didrocks> sil2100: do you mind reaching out bregma so that this is fixed?
[08:13] <sil2100> Ok ;)
[08:13] <didrocks> then, we can just publish that one
[08:47] <sil2100> didrocks: hm, the mediaplayer-app test failure makes no sense, looks like an autopilot issue - since the video shows all is ok
[08:47] <sil2100> didrocks: can I publish? (first normally then force?)
[08:47] <didrocks> sil2100: yeah, but please, email the guys about it :)
[08:54] <sil2100> didrocks: some packaging changes to ACK - I know those are OK since I approved the merges myself ;p : http://10.97.0.1:8080/view/cu2d/view/Head/view/Media/job/cu2d-media-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_qtubuntu-camera_0.3.3+13.10.20130627-0ubuntu1.diff and http://10.97.0.1:8080/view/cu2d/view/Head/view/Media/job/cu2d-media-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_qtubuntu-media_0.7.1
[08:54] <sil2100> didrocks: I already e-mailed renato and omer
[08:55] <Laney> mlankhorst: here?
[08:55] <mlankhorst> yeah
[08:55] <Laney> Could it be ...
[08:55] <Laney> that new X broke my custom volume up/down/mute keybindings that I set in gnome?
[08:55] <didrocks> sil2100: good for both :)
[08:59] <Laney> mlankhorst: ^ it certainly seems so (reverting got them back)
[08:59] <mlankhorst> hm
[09:00] <mlankhorst> bit busy with kernel fallout atm :P
[09:00] <Laney> jus' sayin
[09:02] <mlankhorst> can you try with xev?
[09:02] <Laney> the events seem ok
[09:02] <Laney> I can set the keys in the keyboard capplet
[09:03] <Laney> but then when I press them the action doesn't happen
[09:03]  * Laney unrevers
[09:03] <Laney> with speelig gud
[09:05] <seb128> Laney, can you run /usr/lib/gnome-settings-daemon/gsd-test-input-helper
[09:05] <seb128> Laney, with the broken and working xorg?
[09:05] <seb128> you should have a "Supports XInput2:			yes (opcode: 131)"
[09:06] <Laney> XInput2: no
[09:06] <seb128> that's the issue
[09:06] <Laney> with the new xorg
[09:07] <seb128> Laney, mlankhorst: http://paste.ubuntu.com/5804131/
[09:07] <seb128> is the test function
[09:08] <seb128> Laney, it might be easier to build g-s-d and play with plugins/common/test-input-helper.c
[09:09] <seb128> e.g test with the helper
[09:09] <seb128> plugins/common/gsd-input-helper.c has the helper code
[09:10] <seb128> Laney, can you try https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=14f92b1479aa065edf3f0aa86b87d4c4ff1fe2ba ?
[09:10] <Laney> yeah I just found that
[09:11] <seb128> mlankhorst, that doesn't give great confidence on how much you guys tested the new xorg during those months you have been testing it...
[09:19] <mlankhorst> it was not a bug in xorg though :p
[09:21] <seb128> mlankhorst, right, still the xorg update should break desktop functionalities...
[09:22] <Laney> still doesn't work
[09:22] <Laney> now ait
[09:22] <Laney> that time the bug was in me :P
[09:22] <Laney> does work :-)
[09:25] <seb128> Laney, great ... but I guess g-s-d with the patch doesn't work on xorg 1.13? e.g we need to group those updates?
[09:25] <Laney> trying
[09:25] <Laney> if not then mlankhorst can upload it to his ppa
[09:25] <mlankhorst> i guess it will work on x1.13
[09:25] <Laney> yeah seems fine
[09:25] <seb128> great
[09:25] <seb128> we should get that g-s-d patch in saucy then ;-)
[09:26]  * Laney uploads
[09:26] <seb128> Laney, thanks
[09:26] <Laney> looks like it would have been in 3.8 though
[09:27] <seb128> Laney, well, 3.8 has https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=b0cee1df30b
[09:27] <seb128> not sure how that will play out for us
[09:28] <mlankhorst> but that patch looks familiar somehow, or maybe it was the previous one that tested for xi22.
[09:28] <mlankhorst> xi2.2*
[09:28] <seb128> mlankhorst, https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=a249eb98818547fef4865382c6db2298d268b293 was the one we tested in precise for the lts backport stack
[09:29] <mlankhorst> ah no wonder
[09:29] <mlankhorst> :D
[09:29] <darkxst> Oh, I have seen that too...
[09:31] <darkxst> btw, still a WIP but I have g-s-d 3.8 working ok with 3.6, not withstanding ibus and wacom
[09:31] <Laney> want to test media keys on unity?
[09:31] <darkxst> Laney, I already fixed that a while back
[09:31] <Laney> ref that commit ^?
[09:32] <darkxst> Laney, its a patch in the package on gnome3-staging
[09:32] <darkxst> basically just reverted the upstream removal , with if_unity gaurds
[09:32] <Laney> k
[09:34] <darkxst> Laney, http://bazaar.launchpad.net/~gnome3-team/gnome-settings-daemon/ubuntu/view/head:/debian/patches/fix_media_keys_on_unity.patch
[09:35] <darkxst> and http://bazaar.launchpad.net/~gnome3-team/gnome-settings-daemon/ubuntu/view/head:/debian/patches/git_revert_gsd-keygrab.patch
[09:35] <darkxst> but the second is a straight git revert
[09:36] <Laney> What's the proper fix here?
[09:37] <darkxst> Laney, the proper fix, assuming you follow gnome style, is to move the keygrabber into unity
[09:37] <Laney> have unity do the key grabbing too
[09:38] <darkxst> yeh
[09:38] <Laney> I wonder how this plays out with Mir
[09:39] <darkxst> no idea
[09:40] <darkxst> but if Mir inteferes with the input events, you will have problems either way
[09:43] <sil2100> didrocks: btw.! The i915.semaphores=0 fix that popey mentioned seems to work in a way ;)
[09:44] <sil2100> didrocks: since I still get the "GPU hung" issues, but it doesn't crash compiz anymore ;p Now, whenever it hangs, I only have to switch to a different tty and back and my compiz is still running without problems!
[09:45] <didrocks> sil2100: ah, in fact, that's the kind of issue I have already
[09:45] <didrocks> would be nice to have the kernel team looking at those though
[09:45] <popey> +100
[09:46]  * didrocks takes a deep breath and try to build the mir stack
[10:32] <tsdgeos> hi guys, qgit complains it's not installed but it is installed
[10:32] <tsdgeos> i think it's because installs the binary to /usr/lib/x86_64-linux-gnu/qt4/bin/qgit instead of /usr/bin
[10:32] <tsdgeos> who do i complain to?
[10:33] <ogra_> dpkg -S /usr/lib/x86_64-linux-gnu/qt4/bin/qgit .... file a bug against the package that returns
[10:38] <xnox> didrocks: popey: +++
[10:41]  * didrocks just counted and we have 234 components daily releasing now \o/
[10:45] <seb128> didrocks, impressive (though component != source right? e.g if a same source release to 2 series you count 2
[10:50] <didrocks> seb128: yep, hence the world of component ;)
[10:50] <didrocks> seb128: can give you the status in head, just polishing my script
[10:52] <didrocks> argh, I had some ~1~
[10:52] <didrocks> let me clean that as well to not count more :p
[10:55] <didrocks> ok, "only" 133 :p
[10:58] <seb128> I'm glad I don't have to maintain "only" that number of packages :p
[11:02] <didrocks> this doesn't match, I think I can't +1 normally
[11:02] <didrocks> counting manually the number of projects I print, and there is more :p
[11:03] <didrocks> oh, a typo, here we go!
[11:03] <didrocks> I was just counting raring :p
[11:03]  * didrocks copies the fixed script to the branch with mir and unity8
[11:04] <didrocks> ah, this starts to make more sense :)
[11:05] <didrocks> so 234 was the right numbers :p
[11:05] <didrocks> I just made a booboo when copying that back between branches and changing path
[11:06] <didrocks> of those: 175 in head (saucy)
[11:06] <didrocks> and so 59 in raring
[11:06] <didrocks> let's commit the script in trunk, would be useful for the future :)
[11:08] <didrocks> ok, meanwhile the unity8 stack (minus unity8 itself for now) built and is in next
[11:08] <didrocks> mir stack is still building
[11:19] <seb128> darkxst, jbicha: in case you didn't see it: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1193018
[11:19] <ubot2`> Ubuntu bug 1193018 in evolution-data-server (Ubuntu) "GOA support not completely split" [High,New]
[11:19] <seb128> could one of you talk to upstream about it? (or we will have to turn goa off in the Ubuntu builds)
[13:58] <kgunn> mlankhorst: ping
[14:12] <mlankhorst> is it urgent?
[15:15] <sil2100> attente: ping!
[15:15] <attente> sil2100, pong
[15:15] <sil2100> attente: hi! Not sure if that's a known issue or just something broken on my system, but I noticed that GIMP menus are broken for me when using unity-gtk-module
[15:16] <attente> sil2100, seems to be fine for me. what issues are you running into?
[15:17] <sil2100> attente: hm, strangely I cannot reproduce those right now, but I noticed such things yesterday:
[15:18] <didrocks> attente: not only gimp, pitti mentionned some apps as well
[15:18] <didrocks> seb128: see, complains after all, but I agree, it took time! ^
[15:18] <sil2100> When I use GIMP for a while, menu states seem to get out-of-date, i.e. I for instance have an image opened, modify it but the 'Save' menu entries are grayed out
[15:18] <sil2100> attente: even though that when I right click to get the context menu, I see those menu entries enabled
[15:19] <sil2100> attente: basically I cannot use the panel then and have to perform all menu actions in the context menu of gimp
[15:19] <seb128> didrocks, oh, I've no doubt new code has bugs ... ;-)
[15:19] <seb128> didrocks, sil2100: do you guys have bug reports?
[15:19] <attente> sil2100, fascinating... i've never used gimp for extended periods of time
[15:19] <sil2100> seb128: will fill in a bug ;) I just noticed it recently
[15:20] <seb128> pitti, ^
[15:20] <sil2100> Ok, maybe I saw it previously, but thought it was because of my compiz crashing
[15:20] <didrocks> attente: you should raise the artistic part in you!
[15:20] <attente> didrocks, ;-)
[15:23] <Laney> that reminds me to file my unity-gtk-module bug
[15:23] <Laney> muhahaha
[15:28] <jbicha> chrisccoulson: aah, you guys changed the Firefox logo again in 23 http://www.nsaneforums.com/topic/175697-firefox-gets-new-logo/
[15:31] <chrisccoulson> jbicha, that wasn't anything to do with me ;)
[15:32] <chrisccoulson> i wonder why people are obsessed with making completely flat icons now? first chrome, now firefox...
[15:32] <chrisccoulson> i prefer the old one ;)
[15:32] <jbicha> chrisccoulson: I blame you for everything to do with Firefox ;)
[15:32] <chrisccoulson> lol
[15:33] <chrisccoulson> jbicha, technically, it's not my responsibility anymore. i don't do any work on it at all (other than the minimum required to just keep it up-to-date)
[15:33] <chrisccoulson> jbicha, do you know anyone who would like to maintain it?
[15:33] <jbicha> chrisccoulson: really? what do you do now then?
[15:34] <chrisccoulson> jbicha, i changed teams a while ago (i'm on the security team now)
[15:35] <jbicha> oh wow, congrats
[15:35]  * jdstrand hugs chrisccoulson :)
[15:35]  * chrisccoulson hugs jdstrand :)
[15:45] <ritz> mterry hi, pm.
[16:24] <ritz> seb128 hi, who works with compiz ?
[16:24] <seb128> ritz, with compiz? like as user? most Ubuntu users
[16:24] <seb128> unity is based on it
[16:24] <ritz> as in dev, a bug with clip redraw+nvidia prop driver
[16:25] <seb128> try asking on #ubuntu-unity, smspillaz and MCR
[16:25] <ritz> sweet, thanks :)
[16:36]  * didrocks waves good evening
[16:43] <seb128> jbicha, hey, did you see https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1193018 ? it would be nice if somebody upstream it, we either need to get that fixed or to turn goa off in the eds build
[16:43] <ubot2`> Ubuntu bug 1193018 in evolution-data-server (Ubuntu) "GOA support not completely split" [High,New]
[16:52] <Sweetshark> seb128: could you nominate bug 1194740 for precise? as it is already fixed in later series ...
[16:52] <ubot2`> Launchpad bug 1194740 in libreoffice (Ubuntu) "[precise] Saving xls files originally created in Excel 2003 causes considerable increase of file size" [Medium,New] https://launchpad.net/bugs/1194740
[16:53] <jbicha> seb128: I think it's a bit early to propose breaking goa...I'll look into it
[17:04] <Sweetshark> ^^ 450 people installed the libreoffice 4.1.0~rc1 prerelease from the ppa so far. thats pretty good for a rc that is claiming to eat your cat and kill your babies.
[17:37] <seb128> Sweetshark, done
[17:37] <Sweetshark> seb128: thanks
[17:39] <seb128> jbicha, thanks, and I'm not "proposed breaking goa", but you ship uoa anyway so account would just work ... and in any case I'm not wanting to break anything but it create practical issues for phone builds and we will need the issue resolved one way or another there... we could build without uoa on armhf only as a workaround
[17:39] <jbicha> seb128: UG doesn't include UOA in saucy
[17:40] <seb128> jbicha, oh, ok, I though you had both for some reason
[17:40] <jbicha> yeah, we'll pick one or the other but we're trying GOA for now :)
[17:42] <seb128> good luck, I'm not going to be verbose again about why I think that's going to be increasingly harder and that you should take uoa as a platform technology (similar to e.g upstart)
[17:42] <jbicha> it's not like we have a choice about upstart...
[17:42] <jbicha> I assume you recommend Mir too :)
[17:42] <seb128> well, as much as you have about uoa
[17:43] <seb128> lol, I don't recommend it
[17:43] <seb128> I just wouldn't like to be the one fighting against the stream
[17:43] <jbicha> no, the Foundations Team has blocked systemd as possible init from Ubuntu
[17:43] <seb128> you could have it in a ppa or something, but I guess you would stop having an official flavor for that...
[17:43] <jbicha> I think Kubuntu & Ubuntu GNOME would be crazy enough to go full systemd if we could...
[17:44] <seb128> desktop should perhaps block goa as possible online account to make your job easier :p
[17:44] <desrt> jbicha: why don't you work on making gnome in debian better?
[17:45] <jbicha> lol :)
[17:45] <desrt> no joke
[17:45] <desrt> they could use help with staying up to date, it seems
[17:45] <jbicha> desrt: I was laughing at seb, not you
[17:45] <seb128> desrt, GNOME on Debian is more uptodate that it is on Ubuntu nowadays
[17:46] <seb128> desrt, Collabora guys are throwing quite some time at it (I guess they use it a base for stuff they work on)
[17:46]  * desrt wonders what the point is, then....
[17:46] <jbicha> desrt: I think I do as much as I can in Debian without having upload rights and I don't care enough to go through the beauracracy to get them with everything else going on in my life these days
[17:46] <Sweetshark> seb128: also libreoffice 4.0.4 (not found) should be SRUed soonish for raring. Its seen 2140 raring, 2200 quantal and 14275 precise downloads from the generic ppa and 1192 raring, 1862 quantal and 5930 precise from the libreoffice-4-0 ppa without any desasters being reported.
[17:46] <desrt> jbicha: fair enough.... i just wonder why you keep banging your head on a brick wall
[17:47] <seb128> Sweetshark, sounds good to me
[17:47]  * desrt heads to lunch
[17:47] <jbicha> desrt: because I think GNOME is the best desktop and Ubuntu is the best foundation
[17:47] <Sweetshark> .oo(woha, that 27600 downloads from the ppa alone ...)
[18:14] <Sweetshark> seb128: so in the libreoffice 3.5 precise ppa we'll have a update soon that fixes bug 1194740, bug 628105 and bug 1176923. Does that warrant a SRU? Last SRU was on 2013-02-15 ...
[18:14] <ubot2`> Launchpad bug 1194740 in libreoffice (Ubuntu Precise) "[precise] Saving xls files originally created in Excel 2003 causes considerable increase of file size" [Medium,New] https://launchpad.net/bugs/1194740
[18:14] <ubot2`> Launchpad bug 628105 in libreoffice (Ubuntu Quantal) "[Upstream] Text not black in LibreOffice" [Undecided,In progress] https://launchpad.net/bugs/628105
[18:59] <seb128> Sweetshark, seems fine to SRU a fix if you have one for the issue
[19:14] <desrt> jbicha: ubuntu is like debian plus upstart... and now you want to remove upstart and add systemd :p
[19:19]  * Laney hugs jbicha - please keep banging on that foam wall ;-)
[19:19] <Guest8506> Hello i use ubuntu 10.04 with gnome 2.30.2 i would like have no icons in the main menu !?
[19:20] <seb128> desrt, don't forget the regular releases, the nice tools, etc ;-)
[19:20] <seb128> Guest8506, hey, try #ubuntu for user questions
[19:20] <Laney> the lack of maintainer lock :P
[19:20] <Guest8506> there iam right now too
[19:21] <jbicha> and a 6 month release cycle
[19:21] <Guest8506> do i need to compile the gnome-panel by myself?
[19:21] <Laney> this isn't the place to get help with that kind of thing, sorry
[19:21] <Guest8506> Laney, ok bye
[19:22] <jbicha> Guest8506: Ubuntu 10.04 is no longer supported except for servers anyway
[19:22] <Laney> if #ubuntu fails you try askubuntu.com
[19:22] <Guest8506> yes i know
[19:22] <Guest8506> thx
[19:22] <Guest8506> bye
[19:23] <ricotz> Sweetshark, btw dont trust stats of arch-all packages
[19:24] <ricotz> Sweetshark, how many 4.1 precise downloads?
[19:27] <Sweetshark> ricotz: why not trust arch-all?
[19:29] <Sweetshark> ricotz: I took libreoffice-common as base and assumed it to be the amd64 and i386 downloads combined (as in I did not double that number ;) )
[19:29] <ricotz> Sweetshark, look at the stats of e.g. the writer binary package and compare them
[19:29] <Sweetshark> ricotz: some ~420 precise downloads of 4.1.0 rc1 (vs. some 30 for saucy). Cowards! :)
[19:30] <Sweetshark> ricotz: people might not download writer, just calc?
[19:30] <Sweetshark> ricotz: if anything -core should be a comparison.
[19:31] <ricotz> ok, then compare that one
[19:34] <Sweetshark> ricotz: 4.0.4 in the main ppa on precise: 7292 -core and 14570 -common on amd64, 7199 -core and 14570 -common on i386. the two -cores add up to 14491 so reasonably close.
[19:34] <ricotz> Sweetshark, will try to look into the raring 4.1 failure tomorrow or weekend
[19:35] <ricotz> ok
[19:36] <seb128> ricotz, jbicha: did you guys look at the new zg dbus api changes and if anything in the archive use those interfaces?
[19:36] <Sweetshark> 0.5% aborts/connectivity issues/whatever do not seem too unreasonable ...
[19:38] <ricotz> seb128, i am running zg2 for some time and havent seen noticeable breakages (not running unity though)
[19:38] <ricotz> seb128, but i guess mhr3 would have complained already ;)
[19:38] <seb128> he didn't check it out yet apparently
[19:39] <seb128> and the new version was blocked in proposed due to alpha1
[19:39] <mhr3> ricotz, i'm blessfully using the distro zg :)
[19:39] <seb128> but e.g the file lens and the private panel use directly the dbus api
[19:39] <seb128> mhr3, well, ricotz update and TheMuso uploaded to saucy yesterday
[19:39] <seb128> but I guess neither of them checked the dbus api users
[19:39] <ricotz> mhr3, go upgrade then! ;)
[19:40] <mhr3> seb128, i think we keep the dbus api stable ;)
[19:40] <mhr3> ...these days anyway :)
[19:40] <seb128> mhr3, that's not what blog posts suggest
[19:40] <mhr3> ricotz, you mean to run S on my machine? eeek :P
[19:40] <seb128> 0.9 apparently breaks dbus and lib apis
[19:40] <mhr3> seb128, ehm?
[19:41] <mhr3> show me that blog post and i'll jump on someone
[19:41] <ricotz> mhr3, saucy runs fine with some kicks
[19:41] <mhr3> ricotz, see, /me no likey kicks
[19:42] <ricotz> hehe
[19:42] <jbicha> seb128: I assume there's still time to put a block in place if you want to verify zg2 is safe first
[19:43] <seb128> mhr3, hum, ignore that, quick googling confused me
[19:44] <seb128> jbicha, well, I'm not, I just hope that those who did the update did the checking ;-)
[19:44] <ricotz> Sweetshark, lo4.1:  29 saucy, 359 precise
[19:45] <ricotz> Sweetshark, you might got the aggregate of all ~ppaX revisions
[20:02] <Sweetshark> ricotz: lol, no -- just a typo ...
[20:05] <ricotz> Sweetshark, hehe, i am really surprise about the precise count though