[07:29] <pitti> Good morning
[07:32] <ajmitch> hi pitti
[07:34] <pitti> hey ajmitch, how are you?
[07:34] <ajmitch> great, I'm at linux.conf.au this week :)
[07:34] <pitti> sweet, enjoy!
[07:35] <ajmitch> yeah, there are some great talks, and it's good to catch up with people again
[07:56] <baptistemm> good morning
[07:56] <didrocks> good morning
[08:00] <baptistemm> salut didrocks
[08:09] <pitti> bonjour didrocks
[08:11] <didrocks> hey pitti :)
[08:11] <pitti> didrocks: had a nice weekend?
[08:16] <didrocks> pitti: cold, but great, thanks :) and you, was it good to be back at home again? :)
[08:18] <pitti> didrocks: indeed it was; we went for some skiing, and lots of sleep
[08:18] <pitti> and some Waltz dancing on Friday night at the "Semperopernball"
[08:19] <didrocks> pitti: oh sweet :)
[08:20] <didrocks> I've switch from screen + irssi to bip + weechat as there were no "smart filtering" plugin on irssi and perl is not of my taste to learn just for one script
[08:20] <didrocks> I just have two issue with weechat:
[08:21] <didrocks> - buffer order which aren't correctly ordered once reconnected (I have to run /layout apply 3 times once conncted to get it again)
[08:21] <pitti> didrocks: ah, how long did it take to set up bip?
[08:22] <didrocks> hum, for the full bip + weechat + test, something like 3 hours (because bip version in intrepid is buggy)
[08:22] <pitti> didrocks: I get a random buffer order, too; I don't mind so much since I'm cycling through all of them in the morning anyway; however, there's a plugin for that
[08:22] <didrocks> but appart from the bug, I think in 1 hour, all should have been properly setup
[08:22] <didrocks> (bip was prepending "-" in backlog and "+" in each message, which made weechat and xchat a world of pain concerning hilighting)
[08:23] <didrocks> the time to figure out that was the cause, etc…
[08:23] <didrocks> the second issue is with the notification script. I've taken that one on the official website: http://www.weechat.org/files/scripts/notify.py
[08:24] <didrocks> the issue is: you're still notified when you are the notified channel (easy fixed with comparing current_buffer != buffer when the hl happenned)
[08:25] <didrocks> but I can't get the same think for private message as weechat.hook_signal doesn't give you the "guilty" buffer and so, you can't know if you are on it or not
[08:25] <pitti> didrocks: in lucid the notification script is shipped in the package already (also the other plugins which I  was using)
[08:25] <didrocks> oh?
[08:25] <pitti> didrocks: "when you are the notified channel"? I don't understand
[08:26] <pitti> didrocks: oh, I see what you mean; well, I actually want it that way, since I'm often on a different workspace
[08:26] <didrocks> pitti: for instance, if my current channel is #ubuntu-desktop and you hl me on it, I don't want to have a notification
[08:26] <pitti> but you could certainy change it to not notify if the channel is the current one
[08:26] <didrocks> that's was pretty easy and I've done it
[08:26] <didrocks> the only issue now is for private messaging
[08:27] <didrocks> if you speak with someone, you're spammed, right?
[08:27] <pitti> the only thing about the notifications that sucks for me is that I get a million of them in the morning right after switching on IRC :)
[08:27] <pitti> right, I am
[08:28] <didrocks> I'll first installed weechat-plugins package
[08:28] <didrocks> I've submit my first patch to upstream, but I really can't find in the API for fixing private message stuff
[09:05] <seb128> good morning desktopers
[09:06] <pitti> bonjour seb128
[09:06] <seb128> hey pitti
[09:06] <seb128> how are you?
[09:06] <seb128> did you have a good weekend?
[09:06] <pitti> I'm great, thanks! skiing was great yesterday
[09:07] <pitti> seb128: I've got another favour to ask, I'm afraid
[09:07] <seb128> oh nice
[09:07] <seb128> hey chrisccoulson
[09:07] <pitti> hey chrisccoulson
[09:07] <seb128> pitti, yes?
[09:07] <pitti> I need someone to commit two gpm patches upstream (https://bugzilla.gnome.org/show_bug.cgi?id=603470)
[09:07] <chrisccoulson> hey seb128 pitti
[09:07] <pitti> would you mind?
[09:07] <chrisccoulson> how are you?
[09:07] <seb128> pitti, sure no problem
[09:08] <pitti> chrisccoulson: I'm great, had a nice weekend; how about you?
[09:08] <seb128> pitti, you should really ask for git commit ;-)
[09:08] <seb128> pitti, not that it bothers me to do it but you commit enough to get it ;-)
[09:08] <didrocks> hey seb128
[09:08] <didrocks> morning chrisccoulson
[09:08] <chrisccoulson> pitti - yeah, my weekend was good, but i'm really tired this morning
[09:08] <chrisccoulson> hey didrocks
[09:08] <pitti> seb128: looking for the instructions how to apply now
[09:09] <seb128> lut didrocks
[09:09] <seb128> pitti, do you need the wiki page or do you have it?
[09:09] <seb128> chrisccoulson, being tired on monday = not good sign for the end of the week
[09:09] <pitti> seb128: looking; It can't be so hard to find :)
[09:10] <chrisccoulson> seb128 - yeah, it's going to be a long week ;)
[09:10] <pitti> seb128: got it
[09:10] <seb128> pitti, ok good
[09:11] <pitti> seb128: hm, is it just me or is https://mango.gnome.org/new_account.php currently down?
[09:12] <chrisccoulson> pitti - WFM, but i get an invalid certificate warning in firefox
[09:12] <pitti> ah, it's back
[09:13] <seb128> same there
[09:13] <chrisccoulson> mmmm, i like mango
[09:18] <chrisccoulson> seb128 - i did the g-s-d update last night (along with libxklavier and libgnomekbd)
[09:18] <chrisccoulson> i can't upload those though
[09:20] <seb128> chrisccoulson, ok, I will get coffee now and look at sponsoring those
[09:21] <chrisccoulson> seb128 - thanks
[09:30] <pitti> seb128: I sent my git commit application now
[09:30] <seb128> pitti, rock on!
[09:30] <chrisccoulson> yay pitti \o/
[09:31] <pitti> http://tinyurl.com/martinpitt-gnomepatches , that might be enough :)
[09:32] <chrisccoulson> pitti - that's a lot more than me, and i got git access
[09:32] <seb128> did anybody else got suspend broken?
[09:32] <pitti> works for me
[09:32] <seb128> bah
[09:32] <pitti> in fact, I got a suspend again during dist-upgrade
[09:32] <seb128> did you reboot since you upgraded?
[09:32] <pitti> xserver-xorg-evdev bug
[09:33] <seb128> it's broken on my laptop and mini configs
[09:33] <pitti> seb128: I upgraded yesterday, suspend works; I upgraded today again, and just got it during dist-upgrade
[09:33] <seb128> weird
[09:33] <pitti> seb128: broken how/
[09:33] <pitti> ?
[09:33] <seb128> it doesn't go to suspend
[09:33] <pitti> sudo pm-suspend?
[09:33] <pitti> does that work?
[09:33] <seb128> I get the screensaver unlock dialog
[09:33] <pitti> i. e. kernel or desktop integration?
[09:34] <seb128> let me boot the mini
[09:34] <seb128> I don't want to suspend my laptop now
[09:34] <chrisccoulson> seb128 - did you just upgrade consolekit?
[09:34] <seb128> chrisccoulson, the upgrade is from thursday night
[09:34] <pitti> the mini doesn't connect to (or even sees) my home's wifi, which sucks
[09:35] <seb128> pitti, sudo pm-suspend...still hanging on the command line
[09:35] <pitti> ah
[09:35] <seb128> ie it doesn't do anything visible
[09:35] <pitti> seb128: /var/log/pm-suspend.log -> anything?
[09:36] <seb128> 00powersave suspend suspend:success
[09:36] <seb128> 01PulseaAudio suspend suspend:
[09:37] <seb128> and that's the end of it
[09:37] <seb128> iz pulse bug?
[09:37] <pitti> a-ha
[09:37] <pitti> so, hanging in the pulse script?
[09:37] <seb128> seems so
[09:37] <pitti> /usr/lib/pm-utils/sleep.d/01PulseAudio suspend suspend:Welcome to PulseAudio! Us
[09:37] <pitti> e "help" for usage information.
[09:37] <pitti> >>> >>> Welcome to PulseAudio! Use "help" for usage information.
[09:37] <pitti> >>> >>> success.
[09:37] <pitti> thta doesn't look intended
[09:38] <pitti> seb128: try moving away /usr/lib/pm-utils/sleep.d/01PulseAudio ?
[09:39] <seb128> sudo pm-suspend doesn't hang now
[09:39] <seb128> but the box doesn't sleep either
[09:39] <seb128> let me look through logs again
[09:39] <seb128> oh in fact it works after reboot
[09:40] <seb128> pitti, thanks
[09:40] <seb128> there has been pulseaudio upgrades since, let me apply those and see if it fixes it too
[10:04] <seb128> urg
[10:04] <didrocks> how do I know which default compiler flags are enabled in buildd? I guess this page doesn't make any authority (https://wiki.ubuntu.com/CompilerFlags)?
[10:04] <seb128> chrisccoulson, now I understand why you are tired ;-)
[10:05] <seb128> ou did those libgnomekbd updates in middle of the night
[10:05] <seb128> didrocks, out of looking at the build log I don't know
[10:05] <chrisccoulson> seb128 - i did the libgnomekbd update on saturday i think, but i finished the g-s-d update at around 4am ;)
[10:05] <didrocks> seb128: ok, I'll just do that so
[10:12] <seb128> pitti, I just pushed your gpm changes if you want to close the bug
[10:12] <pitti> seb128: merci; will do
[10:12] <seb128> thanks!
[10:12] <seb128> chrisccoulson, libxklavier uploaded
[10:13] <chrisccoulson> seb128 - thanks :)
[10:13] <seb128> thank you for the work ;-)
[10:14] <geser> does somebody have an idea why indicator-applet-sessions looks on my desktop pc as "(') michael" (first the poweroff button then the username) and on my netbook it looks as "michael (')" (first the username then the poweroff button)?
[10:14] <seb128> no, that's a ted question
[10:15] <chrisccoulson> geser - i think some other users already reported a similar issue
[10:15] <chrisccoulson> with the 2 indicators appearing in the wrong order
[10:16] <chrisccoulson> geser - bug 507026
[10:17] <seb128> chrisccoulson, the libgnomekbd abi got broken without soname change apparently
[10:17] <geser> thanks
[10:19] <chrisccoulson> seb128 - oh no :( how do we normally handle issues like that?
[10:19] <seb128> we tell upstream
[10:19] <seb128> I pinged svu on IRC now
[10:20] <seb128> let's see what he replies
[10:20] <seb128> I would tend to ignore that for libgnomekbd
[10:20] <seb128> since the rdepends are limited and I doubt many things use those
[10:20] <seb128> gkbd_indicator_config_load_images gkbd_indicator_config_free_images gkbd_indicator_config_update_images
[10:20] <seb128> those
[10:21] <chrisccoulson> yeah, and the rdepends are smaller now gnome-applets doesn't use it too
[10:21] <seb128> $ apt-cache rdepends libgnomekbdui4

[10:21] <seb128> $
[10:21] <seb128> and libgnomekbd has 3 rdepends
[10:21] <seb128> g-s-d g-s g-c-c
[10:22] <seb128> I will quickly grep through those sources
[10:22] <seb128> and just upload if nothing use those api
[10:22] <chrisccoulson> cool, thanks
[10:23] <seb128> ok that was expected
[10:23] <seb128> none use it
[10:33] <seb128> pitti, ok, suspend fixed in current lucid
[10:33] <pitti> \o/
[10:33] <seb128> thanks for looking to the issue with me
[10:33] <seb128> I've learnt something
[10:33] <seb128> that pulseaudio not only can break sounds
[10:33] <seb128> but also suspend!
[10:33] <hyperair> huh?
[10:33] <seb128> what?
[10:33] <hyperair> pulseaudio can suspend?
[10:34] <seb128> no, it can break suspend
[10:34] <hyperair> aah
[10:34] <hyperair> i see
[10:34] <seb128> the pmutils hook was hanging
[10:34] <hyperair> was it?
[10:34] <hyperair> ouch
[10:34] <seb128> yes
[10:34]  * hyperair wrote that hook
[10:34] <hyperair> what went wrong?
[10:34] <seb128> dunno it was fixed meanwhile in the weekend updates
[10:35] <hyperair> probably pacmd/pactl hung
[10:35] <seb128> "  * debian/01PulseAudio: Rework pacmd bits (LP: #507941)"
[10:35] <seb128> I guess that one
[10:35] <hyperair> ah
[10:35]  * hyperair looks
[10:37] <hyperair> seb128: could you pastebin your 01PulseAudio from /usr/lib/pm-utils/sleep.d? i'm interested to know what changed.
[10:37]  * hyperair is on karmic
[10:37] <hyperair> and i can't seem to coax a debdiff out of launchpad
[10:38] <seb128> hyperair, wait
[10:38] <hyperair> k
[10:38] <seb128> hyperair, http://launchpadlibrarian.net/37960928/pulseaudio_1%3A0.9.22~0.9.21%2B341-g62bf-0ubuntu1_1%3A0.9.22~0.9.21%2Bstable-queue-24-gfa64-0ubuntu1.diff.gz
[10:38] <hyperair> thanks.
[10:39] <seb128> pitti, don't get surprised if gnome-panel is much less busy in charts, it's not quicker
[10:40] <seb128> pitti, I did change to build applets as normal applets
[10:40] <seb128> pitti, so they show as different processes now
[10:40] <seb128> ie clock, notification-area, etc
[10:40] <hyperair> aha. so pacmd finally got a more script-friendly interface.
[10:40] <seb128> vuntz asked for that to have details on crashes
[10:40] <pitti> seb128: ah, that's possible?
[10:40] <seb128> pitti, yes, it's a configure option
[10:40] <pitti> seb128: seems sensible, then it's also easier to see which applet causes load
[10:40] <seb128> indeed
[10:41] <seb128> it causes a bit extra memory usage
[10:41] <seb128> it causes a bit extra memory usage
[10:41] <seb128> ups
[10:41] <seb128> but I will turn it off again before lucid
[10:46] <seb128> chrisccoulson, libxklavier newed, I'm doing a small fix on libgnomekbd and will upload that one too
[10:46] <chrisccoulson> seb128 - thanks
[10:46] <seb128> (updating the shlibs)
[10:46] <seb128> libgnomekbdui got some new apis
[10:53] <bigon> seb128: could you have a look at that? https://bugs.edge.launchpad.net/ubuntu/+source/empathy/+bug/509081 plz
[10:54] <seb128> oh come on
[10:54] <seb128> (reaction on the bug title)
[10:54] <seb128> looking ;-)
[10:54] <seb128> I don't understand the issue I think
[10:55] <seb128> what is stealing a revision?
[10:55] <seb128> use a debian revision number?
[10:55] <seb128> dropping a debian revision?
[10:58] <bigon> seb128: well it use -1 without actually merging the changes
[10:59] <bigon> so I made a merge of the changes
[10:59] <seb128> oh ok, thanks
[10:59] <seb128> did debian did that many changes again?
[11:00] <bigon> not that much
[11:01] <bigon> btw I asked uplaod permission to this package (and others) but yesterday I tried and my upload was refused ;(
[11:01] <seb128> your diff is weird, is that current debian to merged debian?
[11:01] <seb128> current ubuntu I mean
[11:01] <seb128> like why does it change the 01_lpi ?
[11:01] <bigon> seb128: nope against current ubuntu
[11:01] <bigon> oh
[11:01] <seb128> I would expect this one to not change
[11:02] <bigon> because the last debian uplaod use source version 3 with quilt
[11:02] <bigon> and I refresh all the patches
[11:02] <seb128> ok
[11:02] <seb128> so lot of refreshing noise I guess
[11:02] <seb128> thanks
[11:02] <seb128> I will sponsor that in a bit
[11:02] <bigon> yeah the diff is a little too big for that
[11:02] <seb128> dunno why upload doesn't work
[11:03] <seb128> try asking cjwatson
[11:03] <seb128> I never looking properly how selected upload rights work
[11:06] <cassidy> all theses patches make my cry.... :(
[11:07] <bigon> :/
[11:08] <cassidy> are we a so unresponsive upstream that you didn't submit most of them?
[11:09] <seb128> cassidy, I will have a look but most of those are not upstream things
[11:09] <seb128> ie notify-osd, libindicate, launchpad integration
[11:09] <seb128> autotools update
[11:10] <bigon> there is 3 patches that I think could be merged upstram
[11:10] <cassidy> I don't mind merging libnotify patches if they are properly done (by checking server's caps)
[11:10] <cassidy> what's the autotools patch?
[11:10] <pitti> btw, notify-osd/libindicate are not inherently ubuntu specific; they are upstream projects/releases that just happen to be done by Canonical employees
[11:11] <seb128> cassidy, I will review our changes while sponsoring the upload
[11:11] <seb128> and talk to kenvandine about stopping pushing fixes without sending them upstream too
[11:11] <seb128> and talk to kenvandine about stopping pushing fixes without sending them upstream too
[11:11] <pitti> but of course they'd need to be in a proper detect-during-configure/fallback to standard GNOME componetns way
[11:11] <cassidy> pitti,  I agree. And said I was ready to consider to merge it once it's properly implemented
[11:11] <seb128> cassidy, the autotools one is just us running autoconf locally
[11:11] <seb128> we prefer to do it in a static way than on buildds
[11:12] <seb128> autotools behaviour can change depending on the version etc
[11:12] <pitti> cassidy: indeed; in fact, checking notify daemon server caps is a good thing in the first place (KDE is using the API as well now, IIRC, and there might be other implementations, too)
[11:12] <seb128> we need to run autoconf to pick the lpi depends in configure
[11:12] <cassidy> I see. So yeah that's really a packaging specific thing
[11:12] <bigon> yep
[11:12] <cassidy> pitti, we already have code parsing and checking caps upstream; so integrating your patch shouldn't be an issue
[11:12] <seb128> anyway I will make sure things which are not upstream yet will be this week
[11:13] <cassidy> thanks
[11:13] <seb128> np
[11:13] <cassidy> I'd like to avoid another libindicate patch fiasco :\
[11:14] <pitti> cassidy++
[11:15] <seb128> we try to be good citizen
[11:15] <seb128> but seems kenvandine try to do too many things sometime and forget about upstreaming some
[11:15] <seb128> I will talk to him when he's there
[11:42] <didrocks> bbl -> lunch
[11:42] <seb128> bigon, did you rework some changes?
[11:43] <seb128> bigon, 30_raise_not_toggle.patch got dropped
[11:43] <seb128> but it seems you changed the libindicate patch too
[11:43] <seb128> the changelog and the bug have no details though
[11:49] <tgpraveen1> does anyone know when gstreamer-bad will be back I did a partial upgrade which removed it when I upgraded to lucid from karmic today?
[11:50] <vish> tgpraveen1: you can install it again... ;)
[11:52] <vish> tgpraveen1: also , you need to read this > http://ubuntuforums.org/showthread.php?t=1343434
[11:52] <vish> tgpraveen1: dont just do partial upgrade because it is offered by update manager
[12:13] <chrisccoulson> seb128 - thanks for uploading those packages
[12:13] <bigon> seb128: yes I dropped 30_raise_not_toggle.patch since it was modifying code added by 20_libindicate
[12:13] <bigon> I merged the 2 patches
[12:13] <seb128> bigon, I figured and upload thank
[12:13] <seb128> uploaded
[12:13] <seb128> chrisccoulson, you're welcome
[12:13] <seb128> good work!
[12:13] <bigon> thx
[12:14] <seb128> the g-s-d update was not trivial apparently! ;-)
[12:22] <chrisccoulson> seb128 - yeah, the notify-osd patch needed updating, so i thought i'd rewrite it so i can copy most of it in to the g-p-m update i do later
[12:22] <seb128> good
[12:28] <tgpraveen> does anyone know when gstreamer-bad will be back I did a partial upgrade which removed it when I upgraded to lucid from karmic today?
[12:32] <vish> tgpraveen: you asked the same question and it was replied.. what's the doubt..? -bad is not removed
[12:32] <tgpraveen> vish: hmm I got disconnected hence didn't get the reply
[12:32] <tgpraveen> could you paste it
[12:33] <vish> tgpraveen:  you can install it again... ;) <vish> tgpraveen1: also , you need to read this > http://ubuntuforums.org/showthread.php?t=1343434    <vish> tgpraveen1: dont just do partial upgrade because it is offered by update manager
[12:41] <vuntz> seb128: thanks for the applet changes!
[12:42] <seb128> vuntz, you're welcome ;-)
[12:49] <didrocks> seb128: about wncksync, do I push the branch directly to ~ubuntu-desktop?
[12:49] <seb128> yes
[12:49] <seb128> it will make review easier
[12:49] <seb128> or do you want to use real source bzr?
[12:50] <seb128> ie ubuntu/wncksync/lucid
[12:50] <seb128> or whatever the naming is
[12:50] <seb128> it sort of makes sense for things which are full source in bzr
[12:50] <seb128> pitti, ^ opinion?
[12:50] <seb128> the source is small and maintainer in bzr
[12:52] <didrocks> seb128: I've made the same as notify-osd, so full source in bzr right now
[12:53] <didrocks> (diverging from upstream branch, so we just have to merge at each new release)
[12:53] <seb128> right, but we could as well use the standard location
[12:53] <seb128> no need to use the ubuntu-desktop team there
[12:53] <seb128> no?
[12:53]  * vuntz wonders what is wncksync, since it contains wnck
[12:53] <seb128> vuntz, something which does mapping between things on screen and the .desktop corresponding
[12:53] <pitti> didrocks, seb128: fine for me for pushing full source to lp:ubuntu/wncksync
[12:54] <pitti> if we have the source anyway, this should be the new canonical place
[12:54] <pitti> and ~ubuntu-desktop/project/ubuntu just for our packaging-only branches
[12:54] <didrocks> ok, so no bzr-vcs tag. Not sure to be allowed to push there so. ~didrocks as a temporary place?
[12:54] <didrocks> so that you can push it there and grant me access
[12:54] <vuntz> seb128, didrocks: ah, interesting. Would make sense to add this to libwnck ;-)
[12:55] <seb128> vuntz, https://launchpad.net/wncksync
[12:56] <pitti> didrocks: pushing is allowed for those people who can upload
[12:56] <pitti> didrocks: but the package needs to exist anywhere already (PPA is enough)
[12:56] <pitti> didrocks: so that LP recognizes the package name
[12:56] <seb128> pitti, do we still need packaging bzr somewhere else?
[12:56] <pitti> seb128: no, why?
[12:56] <seb128> I don' fully understand this new world
[12:56] <didrocks> pitti: oh ok, and I'm already granting to upload it?
[12:56] <seb128> pitti, " and ~ubuntu-desktop/project/ubuntu just for our packaging-only branches"
[12:56] <pitti> didrocks: just try it
[12:57] <seb128> pitti, I don't get why we need that one?
[12:57] <pitti> seb128: well, I mean we'll continue to use that style for packages where we don't want full source branches
[12:57] <seb128> pitti, can't we just do the packaging to ubuntu/wncksync?
[12:57] <seb128> oh ok
[12:57] <pitti> seb128: we don't need it for wncksync, but we still want to use them for e. g. gnome-pane
[12:57] <seb128> I though we were speaking about wncksync
[12:57] <seb128> yes sure
[12:57] <seb128> as said it makes sense for wncksync since it's in bzr upstream too
[12:58] <seb128> and small to fetch too
[12:58] <pitti> lp:ubuntu/wncksync is then a real branch from lp:wncksync which has our packaging and our delta
[12:58] <seb128> ok, that's what I though
[12:58] <didrocks> pitti: I've changed the source package name to be the same than upstream tarball
[12:58] <seb128> didrocks, ^ looks good to you?
[12:58] <didrocks> so, I get:
[12:58] <didrocks> bzr push lp:ubuntu/wncksyncdaemon
[12:58] <didrocks> bzr: ERROR: Invalid url supplied to transport: "lp:ubuntu/wncksyncdaemon": No such source package wncksyncdaemon.
[12:58] <seb128> njpatel_, could you reply to vuntz's "Would make sense to add this to libwnck ;-)"
[12:58] <didrocks> seb128: right
[12:59] <didrocks> pitti: upstream tarball is wncksyncdaemon, not wncksync
[12:59] <pitti> didrocks: so, just keep it locally for now
[12:59] <pitti> didrocks: upload the package to NEW, I'll review, and then we'll push it to the official place
[12:59] <seb128> I can review and upload
[12:59] <seb128> so pitti can NEW it
[12:59] <njpatel_> seb128, vuntz is right :)
[12:59] <pitti> didrocks should be able to upload, too
[13:00] <seb128> no
[13:00] <pitti> no?
[13:00] <seb128> NEW sources are not allowed
[13:00] <pitti> how so? didrocks is a MOTU?
[13:00] <seb128> he can only upload desktop set
[13:00] <seb128> urg
[13:00] <njpatel_> vuntz, it was a bit risky, hence we though we'd have a go at it as a stand-alone library first -- but it seems to work quite well
[13:00] <seb128> it's me getting confused now
[13:00] <seb128> pitti, sorry about that
[13:00] <pitti> erm, not a MOTU, but an ubuntu-dev
[13:00] <didrocks> but as a MOTU, I was able before to upload new sources
[13:00] <seb128> yes, sorry
[13:00] <didrocks> ok :)
[13:00] <seb128> I got the issue with other people who are not MOTU but team uploaders
[13:01] <seb128> I forgot you were MOTU now
[13:01] <didrocks> (it's almost a year now ;))
[13:01] <seb128> yes, I was thinking new world order
[13:01] <seb128> ie that you were ubuntu-desktop uploader
[13:01] <didrocks> oki
[13:02] <seb128> didrocks, njpatel_: why don't the project name and tarball name match there?
[13:02] <vuntz> njpatel_: oh, sure, I understand you want to test how it goes first. But if it works fine, it should be merged
[13:02]  * vuntz looks at the code
[13:03] <njpatel_> seb128, I'm not sure, would need to ask DBO
[13:03] <didrocks> pitti: I got some unwanted file in diff.tar.gz, this is due to bzr-builddeb merge mode and it's the same in notify-osd:
[13:03] <seb128> didrocks, can we sort that before upload?
[13:03] <didrocks> urg, pitti : http://pastebin.com/f60c8471b
[13:03] <didrocks> seb128: sure
[13:04] <seb128> thanks
[13:04] <pitti> didrocks: is the m4 stuff from autoreconf? but why *.patch?
[13:05] <didrocks> pitti: it's in upstream trunk and not in tarball.
[13:05] <didrocks> but bzr-builddeb is in merge mode to keep configure file
[13:05] <pitti> didrocks: ah, you packaged bzr head, not last release
[13:05] <pitti> didrocks: should be okay for now
[13:08] <didrocks> pitti: bzr released version branch has it (look at lp:wncksync/0.2 )
[13:47] <pitti> \o/
[13:48] <pitti> BEWARE! I can commit to gnome now
[13:48] <pitti> that was fast
[13:48] <didrocks> :)
[13:48] <didrocks> congrats pitti
[13:48] <pitti> seb128: should've listened to you months ago :)
[13:48] <seb128> hehe
[13:48] <seb128> pitti, well done!
[13:53] <vuntz> njpatel_: for wncksync: wouldn't it be better to set a hint on the window?
[13:55] <njpatel_> vuntz, yeah, definitely. We wnet with dbus initially so we could do quicker testing using python/mono. It's something that we may end up doing now that we know it works
[13:56] <vuntz> njpatel_: quicker? Heh, it looks more difficult to me, but well, you did the work ;-)
[13:57] <vuntz> anyway, it probably makes sense to start a thread on wm-spec-list to request a hint name
[13:57] <njpatel_> vuntz, Heh, not everyone likes doing X stuff like we do :) (or have learned to like it ;-)
[13:58] <njpatel_> vuntz, it's DBO's baby, he wanted to make it acceptable for gnome-shell, too, but I don't think he got traction (it's not really a problem most people want to tackle/see a need for). Maybe you and him could chat more about the implementation and how it could hopefully land in wnck?
[13:59] <didrocks> pitti: is liblauncher in desktop set, can I upload it?
[14:00] <seb128> didrocks, I can sponsor for you if you want
[14:00] <seb128> didrocks, try uploading and see if it works
[14:00] <seb128> it if doesn't ping me and I will upload
[14:01] <vuntz> njpatel_: I'm pretty sure that the gnome-shell people wanted something like this too
[14:01] <vuntz> njpatel_: and sure, I'm fine chatting with DBO
[14:03] <pitti> didrocks: ./edit_acl.py -s liblauncher query -> says yes
[14:04] <njpatel_> vuntz, awesome, thanks
[14:04] <seb128> pitti, where is this edit_acl?
[14:05] <pitti> lp:~ubuntu-archive/ubuntu-archive-tools/trunk/
[14:05] <pitti> I sent a mail about it the other day
[14:05] <seb128> ok thanks
[14:07] <chrisccoulson> pitti - have you seen bug 505972?
[14:07] <chrisccoulson> it seems to be related to your change for the keyboard layout handling
[14:08] <didrocks> seb128, pitti: seems to work, yeah, thanks :)
[14:08] <seb128> chrisccoulson, that's what I was thinking too
[14:08] <seb128> ;-)
[14:08] <seb128> I had it on my list of "ping people about"
[14:08] <seb128> didrocks, you're welcome
[14:08] <chrisccoulson> seb128 - i think i can see what the issue is already
[14:08] <seb128> login screen going away while callback are still waiting?
[14:09] <seb128> chrisccoulson, ignore the g-s-d build errors btw
[14:09] <seb128> chrisccoulson, I retried it now, it was libgnomekbd arch all any difference
[14:09] <seb128> (it just built fine on i386)
[14:10] <chrisccoulson> the XklEngine returned by xkl_engine_get_instance() is a singleton, so if you call get_system_default_layout() more than once, the XklEngine returned on the second time contains an invalid pointer to the Display that was closed on the first call (with XCloseDisplay)
[14:10] <pitti> chrisccoulson: I guess I experienced the crash as well, but haven't looked into it yet
[14:10] <chrisccoulson> pitti ^^ my last comment explains what i think the issue is
[14:11] <pitti> aah
[14:11] <pitti> chrisccoulson: that means it would need to be stored in a static variable?
[14:12] <chrisccoulson> pitti - quite possibly. if you look at g-s-d for example though, it just passes GDK_DISPLAY() as the second parameter to xkl_engine_get_instance(), rather than calling XOpenDisplay()
[14:13] <pitti> chrisccoulson: thanks for pointing out; I'll have a look at it now
[14:17] <pitti> chrisccoulson: gives me a chance to try out my new git commit privs :)
[14:23] <seb128> hey rickspencer3
[14:23] <rickspencer3> hi seb128
[14:23] <pitti> hey rickspencer3
[14:23] <seb128> how are you?
[14:24] <seb128> had a good trip back?
[14:24] <rickspencer3> seb128, yes it was fine
[14:24] <rickspencer3> how are you guys?
[14:24] <seb128> good thanks!
[14:25] <didrocks> hey rickspencer3, I'm fine, thanks!
[14:25] <rickspencer3> hi didrocks
[14:25] <rickspencer3> so, today is a holiday here, but I didn't realize that last week and I scheduled some stuff :(
[14:26] <seb128> oh :-(
[14:26] <seb128> we need to get holidays somewhat integrated in the calendar
[14:28] <rickspencer3> heh
[14:28] <rickspencer3> oh well
[14:28] <rickspencer3> didrocks, looks like some contributions to quickly came in, that 's nice
[14:29] <didrocks> rickspencer3: right, I've merged those into the trunk, just some debate on last one about naming :)
[14:32] <seb128> didrocks, why did you remove liblauncher simplepatchsys?
[14:32] <didrocks> seb128: just some cleanage, there is not patch currently
[14:32] <rickspencer3> seb128, what's the status the f-spot editing tweak? is it in yet?
[14:33] <seb128> didrocks, right, but you don't play adding and removing the build-depends, directory, rules target etc every time we add or drop a patch do you?
[14:33] <seb128> rickspencer3, no it's not, upstream did those changes with some refactoring which makes that non trivial to backport
[14:33] <rickspencer3> mmm
[14:34] <seb128> it's on my list but i didn't manage to work on it
[14:34] <rickspencer3> seb128, ack, ok
[14:34] <didrocks> seb128: no, but for me, this time was more like "first packaging" for it and I don't think we will add a lot of patches as upstream is closed. That's why I was thinking this will be better
[14:34] <seb128> didrocks, ok...
[14:34] <seb128> didrocks, I tend to let the rules on all desktop packages so it's trivial to add a patch if you need one
[14:34] <seb128> for quick testing, backport or anything
[14:34] <seb128> it doesn't cost anything either
[14:35] <seb128> otherwise you have to figure what is the include again, etc, not complicated but annoying
[14:35] <didrocks> seb128: ok, will do the first time we'll add a patch there. another question, do we enable --enable-gtk-doc generally?
[14:35] <seb128> no we don't
[14:35] <seb128> upstream ship html files usually
[14:36] <didrocks> ok, because it was on clutk, that's why I was beginning to wonder
[15:15] <pitti> yay, my first gnome git commit
[15:16] <chrisccoulson> yay pitti \o/
[15:16] <seb128> pitti, yay!
[15:16] <pitti> chrisccoulson: I fixed the gdm crash
[15:16] <pitti> http://git.gnome.org/browse/gdm/commit/?id=51669cb03613b36b0b1798b1f8d2bba85b3e2a49
[15:16] <seb128> pitti, did you get commit approval before commiting?
[15:17] <pitti> it was a followup fix for a previously approved/committed patch
[15:17] <seb128> ok good
[15:17] <pitti> I sent a followup comment to the bug
[15:17] <chrisccoulson> pitti - awesome, thanks!
[15:17] <pitti> asking to harass me if that was a wrong workflow
[15:17] <seb128> just making sure that commit right doesn't mean you can commit without asking the maintainer first there ;-)
[15:17] <pitti> yeah, in general I'll keep filing bugs with patches
[15:18] <pitti> hughsie asked me to commit simple fixes to gpm directly
[15:18] <pitti> not sure what the gdm guys think
[15:18] <mclasen> the daemon keeps an open x connection now ?
[15:18]  * mclasen likes this patch less and less...
[15:19] <pitti> it's just the greeter, not the continuously running daemon, is it?
[15:19] <pitti> i. e. the greeter would crash, restart from teh daemon, and then it worked again (since the xkl stuff got reinitialized)
[15:20] <mclasen> pitti: ok. I still don't like it :-)
[15:21] <pitti> mclasen: heh, that's alright :)
[15:21] <pitti> I mean, we could change it again to read it from udev
[15:21] <pitti> but then the solaris/BSD guys would complain again..
[15:21] <chrisccoulson> mclasen - i think anything that uses libxklavier keeps an open x connection doesn't it?
[15:21] <pitti> I'm a bit lost in what is the One True Way to get the system layout
[15:22] <chrisccoulson> pitti - me too
[15:22] <pitti> but since gdm definitively needs X, but not udev, this seems more elegant
[15:56] <seb128> ohhh
[15:56] <seb128> pitti, chrisccoulson: I think that crash was the same which breaks login as a different user
[15:56] <pitti> ah, good
[15:56] <seb128> nice to see it fixed I had that on my list to debug for today
[15:57] <seb128> it happened when selecting an user, doing esc and selecting again
[15:57] <seb128> or when trying to use "others" and typing an username
[15:57] <seb128> it crashed before asked for the password there
[16:05] <seb128> brb reboot after dist upgrade
[16:26] <seb128> re
[16:27] <seb128> so guest session still crashes xorg there
[16:27] <baptistemm> I just ordered a ssd disk, hope I'll have fun testing speed booting on ubuntu
[16:33] <fta> kenvandine, hi, after a few days of playing with it, the indicator-application is clearly a regression feature wise compared to the old rhythmbox tray applet :(
[16:33] <kenvandine> fta, what's missing?
[16:34] <kenvandine> fta, please file a bug so we can fix that
[16:34] <didrocks> seb128: clutk uploaded, you may have to NEW the libclutk-0.3-doc binary package
[16:34] <didrocks> hey kenvandine
[16:34] <kenvandine> hey didrocks
[16:34] <seb128> didrocks, ok
[16:34] <seb128> kenvandine, hey
[16:34]  * kenvandine isn't really here... holiday :)
[16:34] <fta> i used to raise/hide & play/pause with one click, have the title+cover on hover, etc.
[16:35] <seb128> kenvandine, could you upstream your empathy patches, we got upstream unhappy issues again today
[16:35] <didrocks> kenvandine: too late now, you spoke on the chan :p
[16:35] <seb128> kenvandine, could you make sure you do upstream your work to avoid use trouble too?
[16:35] <kenvandine> seb128, oh?
[16:35] <seb128> use -> us
[16:35] <kenvandine> seb128, which patches?
[16:35] <kenvandine> the papercut ones?
[16:35] <seb128> kenvandine, the ones you added some days ago
[16:35] <seb128> yes
[16:35] <kenvandine> yeah... i didn't get to that on friday :/
[16:36] <kenvandine> i'll get them tonight or in the morning
[16:36] <seb128> we should make sure to do that before uploading
[16:36] <seb128> we don't want to keep annoying upstream this way
[16:36] <seb128> thanks
[16:36] <kenvandine> which one in particular?
[16:36] <kenvandine> we did talk to them a bit about them
[16:38] <seb128> not sure, cassidy freaked out by the number of patch we have
[16:38] <seb128> he said the notify-osd one should be upstreamed
[16:38] <seb128> as should be the papercut ones
[16:38] <kenvandine> i think it is...
[16:38] <seb128> you also weirdly rebased on debian apparently
[16:38] <kenvandine> robert_ancell did that one agest ago and i am almost sure i saw a bz# for that at some point
[16:38] <seb128> we missed quite some debian changelog entries and changes
[16:39] <seb128> like no empathy-dbg in ubuntu
[16:39] <kenvandine> humm... ok
[16:39] <seb128> old manpages still installed etc
[16:39] <seb128> somebody fixed it, I've uploaded that today
[16:39] <kenvandine> humm... i might have rebased in the middle of some changes
[16:39] <cassidy> if I missed an upstream bug about one of your patch please ping me about it
[16:39] <seb128> anyway I don't want to bother you during an holiday day
[16:39] <seb128> enjoy your afternoon ;-)
[16:39] <kenvandine> cassidy, i will look into that one tomorrow
[16:39] <kenvandine> the notify-osd one
[16:40] <cassidy> thanks
[16:40] <kenvandine> cassidy, the patch for raising the window when lauched you aren't going to take, right?
[16:40] <kenvandine> cassidy, i think we agreed to have a delta there...
[16:40] <cassidy> humm, refresh my memory?
[16:41] <kenvandine> the papercut for what to do when you launch empathy yourself, out side of autostarting in session
[16:41] <seb128> pitti, https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/492392
[16:41] <seb128> pitti, just for information
[16:41] <pitti> nice, thanks
[16:41] <kenvandine> cassidy, you guys alway honor the last state
[16:41] <kenvandine> but we wanted it to always open, if you click on it
[16:42] <kenvandine> cassidy, we discussed that early last week i think
[16:42] <kenvandine> cassidy, anyway... i'll address them all tomorrow and ping you as necessary
[16:43] <kenvandine> time to go play with the kids outside... live this weather 60F and sunny :)
[16:43] <cassidy> oh you're right. Yeah I think that's wrong. I'm sure you'll have people complaining because they always start and use Empathy hidden
[16:43] <kenvandine> s/live/love
[16:43] <kenvandine> cassidy, yeah... we'll look at feedback from that
[16:43] <seb128> have fun kenvandine
[16:44] <seb128> cassidy, those who consider it a system service usually start it with the session rather
[16:44] <cassidy> yeah but, iiirc, with this patch it will be displayed when starting
[16:44] <seb128> it should not
[16:44] <seb128> the intend of the change is to display only when started manually not when in the session
[16:45] <cassidy> rly? How do you check that?
[16:50] <chrisccoulson> cassidy - checking for DESKTOP_STARTUP_ID in the environment
[16:50] <chrisccoulson> (which is set by gnome-session)
[16:50] <chrisccoulson> nautilus uses a similar method for woking out if it was autostarted
[16:51] <cassidy> interesting. I didn't know that. Thanks. I could be convinced to merge this patch but I'd like to get user feedback first
[16:52] <mclasen> chrisccoulson: gtk unsets that variable early on...
[16:55] <chrisccoulson> mclasen - thanks, i didn't realise that
[16:55] <chrisccoulson> i don't know how early kenvandine's patch checks it though
[16:56] <seb128> mclasen, did you notice issues similar to https://bugzilla.gnome.org/show_bug.cgi?id=607322 with gtk 2.19 too?
[16:57] <mclasen> seb128: no, but  I try not to pay too much attention to the file chooser anyway...
[16:58] <seb128> mclasen, it seems to not be specific to it, gtg has a similar issues on tasks
[16:58] <seb128> could be a gtklistview issue?
[16:59] <mvo> I saw it in software-center too, in the central listview
[17:00] <seb128> mclasen, it happens in the gtk-demo left pane too...
[17:01] <mclasen> seb128: talk to kris ? he did some changes to treeview event handling before xmas
[17:01] <seb128> mclasen, ok thanks
[17:01] <seb128> I was pointing it because I'm not sure how you milestone bugs
[17:01] <seb128> but that one should perhaps be on 2.20 list
[17:15] <hyperair> chrisccoulson: hurry up and get g-p-m uploaded to lucid already so i can do a sru for karmic =p (it's a rather high-impact issue with many users complaining)
[17:15] <seb128> you don't need to have the change to lucid to sru karmic
[17:16] <kklimonda> chrisccoulson, and when you are doing that get a new transmission - looks like no one touched it when I was away ;)
[17:23] <chrisccoulson> hyperair - i'm going to do g-p-m tonight
[17:24] <hyperair> chrisccoulson: yay.
[17:24] <chrisccoulson> sorry, i ran out of time at 4am this morning when i finished doing g-s-d ;)
[17:24] <hyperair> ah no problem. =p
[17:24] <chrisccoulson> i need at least 3 hours of sleep before i get up for work ;)
[17:24] <chrisccoulson> lol
[17:24] <chrisccoulson> anyway, home time!
[17:24] <chrisccoulson> bbl
[17:42] <seb128> pitti, confirmed, gdm crash fixed, good work!
[17:50] <Ng> kenvandine: fyi, xchat indicator appears to work very well, nice work :D
[17:50] <Ng> evolution less so, but I've not looked at why
[18:18] <chrisccoulson> awesome, new ISP tonight :)
[18:18] <chrisccoulson> lets hope my connection is a bit more reliable now
[18:32] <pitti> good night everyone
[18:45] <milanbv> kees: ping?
[18:47] <chrisccoulson> hey kklimonda - do you have a transmission upload ready as well then?
[20:07] <baptistemm> pitti, http://www.piware.de/workitems/desktop/lucid/versions.html returns a 404
[21:19] <seb128> re
[21:41] <chrisccoulson> hey seb128
[21:42] <seb128> hello chrisccoulson
[21:42] <chrisccoulson> how are you?
[21:42] <seb128> did you have a good day?
[21:42] <chrisccoulson> it wasn't too bad, but it felt like quite a long day
[21:42] <chrisccoulson> how was your day?
[21:43] <fagan> Is the nvidia and X bug fixed in lucid yet?
[21:43] <seb128> chrisccoulson, busy but good
[21:43] <seb128> busy in a productive way ;-)
[21:44] <chrisccoulson> busy and productive is good :)
[21:44] <seb128> yes ;-)
[21:50] <fagan> seb128: is this right? http://twitpic.com/ypdgl
[21:50] <fagan> The power management stuff is on the inside
[21:50] <fagan> and the messenger stuff on the outside
[21:50] <chrisccoulson> fagan - there's already a bug for that
[21:50] <fagan> Ah ok
[21:51] <seb128> tedg, ^
[21:52] <fagan> Actually I thouth it was ok there
[21:52] <tedg> Yes, it doesn't do ordering yet.
[21:52] <fagan> *thought
[21:52] <tedg> The order is based on when they're written to your disk right now.
[21:52] <tedg> :)
[21:52] <chrisccoulson> tedg - that's robust ;)
[21:52] <tedg> chrisccoulson: We call it an "advanced personalization feature" ;)
[21:53] <chrisccoulson> heh, at least its consistent once the files are written
[21:53] <fagan> Oh and anything I should be looking out for when im upgrade testing?
[21:53] <fagan> Im going to do it in 15 minutes
[21:53] <fagan> (From hardy to lucid)
[21:54] <geser> tedg: so when I touch the modules in the right order I can change the ordering inside the applet?
[21:54] <tedg> geser: I think you'd have to move them, as it'd be how the directory inode is written.
[22:51] <chrisccoulson> hey robert_ancell
[22:51] <robert_ancell> chrisccoulson, hey
[22:51] <chrisccoulson> how are you?
[22:51] <seb128> hey robert_ancell
[22:51] <robert_ancell> chrisccoulson, good. at LCA2010 hearing about LP translations
[22:51] <seb128> robert_ancell, do you need lpi sponsoring?
[22:51] <robert_ancell> seb128, hey
[22:52] <seb128> I've noticed the reject email you got
[22:52] <robert_ancell> seb128, yes or added to the ubuntu-desktop list
[22:52] <seb128> I don't know how those upload rights are handled
[22:52] <seb128> and I don't think I can change those
[22:52] <seb128> but I do the upload for you, where is it?
[22:52] <robert_ancell> seb128, ok, I'll push it to bzr and then come back to you
[22:52] <seb128> you should ping pitti or cjwatson abou tit
[22:53] <seb128> about it
[22:53] <robert_ancell> I've pinged pitti
[22:53] <seb128> robert_ancell, ok, feel free to move the bzr to ubuntu-desktop if you want
[22:53] <seb128> I think it's in a team you are not member of right now
[22:53] <robert_ancell> seb128, yup, mvo said it would be ok to do
[22:53] <robert_ancell> yeah it's core-dev
[22:53] <chrisccoulson> seb128 - basically, we can upload to anything in the ubuntu-desktop package set, which seems to only be packages that are used in ubuntu, and none of the derivatives
[22:53] <chrisccoulson> there seems to be a lot that we can't upload
[22:53] <seb128> I see you already talked to other guys ;-)
[22:53] <seb128> did you send an email I was Cced on
[22:53] <seb128> ?
[22:54] <robert_ancell> I must have
[22:54] <seb128> just checking you don't finish in my spam filter for some reason
[22:54] <seb128> since I already dropped an email from you some days ago
[22:54] <seb128> I will need to check that
[22:54] <robert_ancell> seb128,  hehe, I put you on a vent about how crap gdm was too
[22:54] <seb128> I replied to that today ;-)
[22:55] <robert_ancell> we have typically flaky conference internet access
[22:56] <seb128> hehe
[22:56] <seb128> how is the conference so far btw?
[22:57] <seb128> chrisccoulson, do you know how,where the set are defined?
[22:57] <seb128> chrisccoulson, I guess desktop is mostly GNOME desktop specific components?
[22:57] <seb128> ie nautilus, gnome-panel, gnome-session
[22:58] <robert_ancell> seb128, good, there seems less stuff today for me but yesterday had some good talks.  Tomorrow the mini-confs end and LCA starts proper
[22:59] <chrisccoulson> seb128 - i'm not too sure. i only know how to check what packages are in the set (edit_acl.py -P ubuntu-desktop -S lucid query)
[22:59] <chrisccoulson> seb128 - gnome-panel, gnome-session, g-s-d, gnome-control-center etc all belong to either "desktop-core" or "core", which we can't upload too
[22:59] <seb128> hum
[23:00] <seb128> that sucks
[23:00] <chrisccoulson> it does a little
[23:01] <seb128> well it's still a good start
[23:01] <chrisccoulson> perhaps i should consider applying for core-dev someday ;)
[23:01] <chrisccoulson> yeah, we can still upload quite a few components
[23:01] <seb128> you should yes ;-)
[23:01] <seb128> bah
[23:01] <seb128> somebody reopened a version update from warty time
[23:02] <robert_ancell> seb128, ok, please release from lp:launchpad-integration
[23:02] <seb128> to request the same source to be updated in lucid
[23:02] <seb128> robert_ancell, using upstream bzr?
[23:03] <robert_ancell> seb128, we are upstream!
[23:03] <chrisccoulson> seb128 - the packagesets seem to be in a state of flux somewhat. eg, i've just noticed that g-s-t, liboobs and system-tools-backends all appear in ubuntu-desktop now, and they didn't a couple of weeks ago
[23:03] <robert_ancell> lp:launchpad-integration points to lp:~ubuntu-desktop/launchpad-integration/ubuntu
[23:03] <chrisccoulson> i had to have them sponsored a couple of weeks back
[23:03] <seb128> robert_ancell, oh ok
[23:03] <seb128> chrisccoulson, weird
[23:04] <robert_ancell> seb128, I checked with the original author and mvo and they're ok with it
[23:05] <seb128> robert_ancell, original author being jamesh right?
[23:05] <seb128> robert_ancell, it makes sense anyway
[23:06] <robert_ancell> yup
[23:08] <seb128> hum
[23:09] <robert_ancell> hum? I dropped out there
[23:09] <seb128> robert_ancell, did you test build that?
[23:09] <seb128> robert_ancell,
[23:09] <seb128> checking for GTK_SHARP... configure: error: Package requirements (gtk-sharp-2.0 >= 2.12) were not met:
[23:09] <seb128> No package 'gtk-sharp-2.0' found
[23:09] <seb128>  
[23:09] <seb128> you need libgtk2.0-cil-dev I guess
[23:09] <seb128> I will fix that before uploading
[23:10] <robert_ancell> hmm indeed.  I swear it was compiling here...
[23:10] <robert_ancell> huats, hi
[23:11] <seb128> robert_ancell, you probably have libgtk2.0-cil-dev installed ;-)
[23:11] <seb128> dch -r
[23:11] <robert_ancell> ah
[23:11] <seb128> ups
[23:16] <seb128> robert_ancell, why did you change the setpackagename btw?
[23:16] <seb128> just curious
[23:16] <seb128> to do a free and strdup again
[23:16] <seb128> rather than using a static
[23:16] <robert_ancell> seb128, It assumes the memory is not going to be freed - in CLI the string value does not remain after the call and the pointer becomes invalid
[23:17] <robert_ancell> it's a very dangerous assumption...
[23:17] <seb128> ok
[23:17] <seb128> I was just surprised to see it in the same commit ;-)
[23:17] <seb128> I guess you do chunck of work locally until getting things working rather than small changes ;-)
[23:18] <seb128> good, it builds now
[23:18] <robert_ancell> yeah, I was going to comment on why I did that but I got lazy
[23:18] <seb128> I will fix bug # 477685 too while I'm on it
[23:20] <robert_ancell> cool, gtg (->lunch)
[23:20] <seb128> robert_ancell, enjoy
[23:26] <kklimonda> chrisccoulson, ping?
[23:27] <chrisccoulson> kklimonda, pong
[23:28] <kklimonda> chrisccoulson, can you upload new transmission? branch linked to bug 496503
[23:28] <chrisccoulson> kklimonda, i'll take a look at it later this evening if i get the change. i'm just doing some work on gnome-power-manager at the moment
[23:29] <kklimonda> k