[08:34] <huats> morning everyone
[08:36] <didrocks> morning huats
[08:38] <huats> morning seb128
[08:39] <seb128> lut huats
[08:39] <seb128> need to restart session brb
[08:39] <huats> seb128: do you want that I take care of the gnome-keyring update ?
[08:43] <seb128> huats: do you want to do the gnome-keyring update or are you busy?
[08:44] <huats> I just asked you before you left :)
[08:44] <didrocks> Hi seb128 :)
[08:44] <huats> I am officially not in my previous company :)
[08:44] <seb128> lut didrocks
[08:44] <huats> so I think I can deal it :)
[08:44] <seb128> huats: oh, congrats
[08:45] <didrocks> seb128: bugs #329800, #329832 (and don't forget #327933) :)
[08:45] <seb128> huats: well, I want this update today so just claim if you have time to do it today
[08:45] <huats> I'll take care of it right now
[08:45] <seb128> didrocks: thanks
[08:45] <seb128> huats: thanks
[08:45] <huats> seb128: I can also take care of gtksourceview2
[08:45] <seb128> huats: ok
[09:11] <soren> My wife's gnome-panel has recently begun freezing from time to time on her Hardy laptop..  Any idea what could have caused that?
[09:12] <soren> By "freezing" I mean she can't click on anything, the clock is frozen, the window list isn't updated... The rest of the desktop works fine.
[09:12] <seb128> soren: do you get the issue after clicking on the clock applet?
[09:13] <soren> seb128: Hm... It's possible.
[09:13] <seb128> there is some gnome-panel bugs about that
[09:13] <soren> seb128: I would have to ask her when she gets up.
[09:13] <soren> You know, we recently added a Google calendar feed to her Evolution, so that might very well be it.
[09:13] <seb128> you can get an hang stacktrace maybe?
[09:14] <seb128> right, that's a known issue (ie we got quite some bugs about google calendar leading to such hangs)
[09:14] <soren> seb128: I'll make sure to grab a dump next time it happens and then remove that feed.
[09:14] <soren> seb128: Thanks for the hint :)
[09:15] <seb128> you're welcome
[10:30] <seb128> huats: so how are the updates going? ;-)
[10:30] <huats> seb128: :)
[10:32] <huats> seb128: remind me that I would never have you as my boss :)
[10:32] <seb128> huats: lol
[10:33] <seb128> huats: I'm not asking too much usually but gnome-keyring ssh agent is broken right now and I get pinged by all the people who use svn, ie active contributors who can't get work done in a normal way
[10:33] <huats> yeah
[10:33] <huats> I understand
[10:33] <huats> it will be ready by 3pm
[10:33] <seb128> huats: that's what you get for claiming updates on basic components rather than let's say calculator ;-)
[10:33] <pitti> hey huats
[10:33] <seb128> huats: ok thanks
[10:33] <pitti> huats: congratulations to your MOTU badge!
[10:34] <huats> pitti: thanks !
[10:34] <huats> seb128: LOL
[10:36] <huats> seb128: I am creating my pbuilder env on my home computer (since I used to work on my office computer)
[10:36] <huats> and I start to build
[10:36] <seb128> huats: you should be running jaunty
[10:37] <huats> seb128: yeah...
[10:37] <huats> I am thinking of that
[10:37] <huats> but I have heard of problem with gnome-keyring :D
[10:38] <huats> (and my gf won't be really happy with jaunty so far I think)
[10:38] <pitti> huats: why not? your gf bullying you about breakage is 100% pure dogfooding :)
[10:38] <huats> :)
[11:13] <seb128> vuntz: hey
[11:13] <seb128> vuntz: gnome-session for you, it restarts automatically things which are in the session and exit which creates and interesting case when running nautilus with no draw_background set
[11:14] <seb128> vuntz: gnome-session keeps running nautilus which keeps exiting since there is nothing to do
[11:14] <seb128> is that a nautilus or a gnome-session issue?
[11:14] <seb128> should nautilus unregister by some way?
[11:15] <mpt> Would anyone like to attach before-and-after screenshots to bug 328954?
[11:16] <seb128> mpt: can you add a comment in the bug requesting for that? I guess whoever is suggesting the change can do that ;-)
[11:17] <mpt> fine fine
[11:17] <mpt> :-P
[11:30] <vuntz> seb128: why does nautilus exit?
[11:30] <vuntz> seb128: shouldn't it still run even if there's no background? (don't know)
[11:30] <seb128> vuntz: because there is no dialog open
[11:30] <seb128> vuntz: no
[11:30] <vuntz> hrm
[11:30] <seb128> vuntz: there is no server mode
[11:30] <seb128> vuntz: same if you try to nautilus --quit to debug
[11:30] <vuntz> gnome-session assumes that it should always run
[11:31] <seb128> wrong assumption
[11:31] <vuntz> seb128: that's the meaning of the thing in the .desktop file
[11:31] <vuntz> so nautilus bug
[11:31] <seb128> the autorestart?
[11:31] <vuntz> it should put that in .desktop file and it should directly control if it gets restarted
[11:31] <vuntz> yes
[11:31] <vuntz> the panel does this
[11:32] <seb128> well, it should autorestart when running
[11:32] <seb128> not when not running
[11:32] <vuntz> seb128: gnome-session starts nautilus. nautilus exits. Then gnome-session restarts it, as indicated by the .desktop file
[11:33] <seb128> vuntz: can you join #nautilus?
[11:46] <seb128> asac: gnome bug #571423 upstream is responsive but needs testing if you want to subscribe and maybe comment
[11:48] <asac> seb128: cool. i will test it asap
[11:48] <asac> hopefully before lunch
[11:48] <seb128> thanks
[11:54] <asac> ok running testcase now
[12:03] <asac> seb128: LOCK up ;)
[12:03] <seb128> asac: using the testcase?
[12:03] <asac> i also posted a more bad lockup to the bug
[12:03] <asac> seb128: yes
[12:03] <seb128> cool
[12:03] <asac> seb128: just try multiple times
[12:03] <seb128> thanks
[12:03] <asac> at some point you will end up in the deadlock grab situation
[12:04] <asac> seb128: as i posted i even get worse situations in combination with gtk-pinentry ... even ctrl-alt-F1 doesnt work
[12:04] <seb128> you need to stop gdm to fix it?
[12:04] <asac> yesterday i had to hit power button for two things
[12:04] <seb128> killing the testcase is not enough?
[12:04] <asac> seb128: well. i didnt try killing the testcase. i assume that works ... i can try
[12:05] <seb128> I will try later
[12:05] <seb128> now is lunch time and I don't want to have to restart my session now
[12:06] <pitti> . o O { Use the guest session, Luke! }
[12:07] <seb128> the box tends to freeze a few minutes after switching between xorg sessions
[12:07] <seb128> I didn't try since the sprint though maybe that's fixed now
[12:07] <pitti> hm, I get that effect after hibernate
[12:07] <seb128> but the previous time I used gdmflexiserver to start and another session and closed it the computer locked not too long after that
[12:08] <pitti> it gets locked on /dev/input/events0
[12:09] <asac> seb128: ok. so killling test binardy doesnt help
[12:09] <asac> seb128: updated bug with that info
[12:09] <asac> seems to be a stale lock in X somewhere i guess
[12:09] <seb128> weird bug
[12:15] <asac> it sounds a bit like the the grabbing requests are not cancelled in X even though the function returns with FALSE
[12:15] <asac> in that case its easy to understand why you end up in a deadlock
[12:16] <asac> e.g. gtk does a two staged grab for popup: 1st. mouse grab; 2nd keyboard grab
[12:16] <asac> so if someone grabs keyboard in between and then tries to grab mouse you will end up in a deadlock
[12:17] <asac> but since the gtk functions are supposed to not block it would be something in X that does that. but lets listen to upstream ideas ;
[12:20] <asac> anyone knows the IRC nick of "Marco d'Itri" (debian)?
[12:20]  * asac ponders db.debian.org
[12:21] <asac> ok seems like "Md"
[12:21] <asac> but isnt online
[12:47] <seb128_> vuntz: is "vertical gnome-panel displays only one notification area icon" a known issue?
[12:49] <vuntz> seb128: no
[12:50] <seb128> vuntz: ok, you will get bug then ;-)
[12:50] <vuntz> seb128: or rather "there might be a bug, but I didn't read it if it exists"
[12:50] <seb128> I've looked on bugzilla and didn't find one
[12:50] <vuntz> (too many panel bug mails)
[12:55] <pedro_> seb128: hey, looks like bug http://bugzilla.gnome.org/show_bug.cgi?id=531371
[12:55] <pedro_> seb128: it uses one line for all the icons on the notification area
[12:55] <pedro_> if you increase the size you'll see the others icons
[12:55] <seb128> ah ok
[12:56] <seb128> pedro_: bug #329537
[12:56] <pedro_> seb128: yup we have that one as well
[12:57] <pedro_> wait bug 322252
[12:58] <vuntz> seb128: btw, can you try...
[12:58] <vuntz> http://bugzilla.gnome.org/show_bug.cgi?id=571041
[12:58] <vuntz> there's a patch
[12:58] <vuntz> it might fix it
[12:59] <seb128> vuntz: would testing be useful to you?
[13:00] <seb128> ie I'm being lazy and will not test if that's not useful but if you want to know if that fixes it or I can do that
[13:02] <vuntz> seb128: well. If it avoids opening an upstream bug... ;-)
[13:03] <seb128> vuntz: do you intend to commit this change before rolling new tarballs today? ;-)
[13:03] <vuntz> seb128: the patch is good, so I'll likely commit it if chpe doesn't commit it
[13:03] <vuntz> seb128: so, deal: don't open the bug and wait for the new tarball?
[13:03] <vuntz> :-)
[13:03] <seb128> ok, so I will wait for the new tarball to try
[13:03] <seb128> ok
[13:03] <seb128> deal!
[13:17] <ember> pochu do we still need the procs change on tracker?
[14:01] <huats> seb128: I am a little late on my schedule
[14:01] <seb128> huats: I noticed!
[14:01] <huats> I am installing again my jaunty vm
[14:01] <huats> and once it is done, I can testrun the update..
[14:01] <seb128> is the update technically ready?
[14:01] <huats> yep
[14:01] <seb128> I can review and test it if you want
[14:02] <huats> sure
[14:02] <huats> seb128: let me put it somewhere
[14:02] <seb128> open a normal sponsoring bug?
[14:02] <huats> ok
[14:08] <TomJaeger> seb128, about bug #217908, I've responded to your concerns in the bug tracker.  I thought it might be easier to discuss this on IRC.
[14:08] <seb128> TomJaeger: hi, I was just reading your comment
[14:09] <seb128> TomJaeger: the issue is simple we don't want to carry changes when not really required, if that change is good is should go upstream if they have a reason to not want it we should probably not ship it either
[14:09] <seb128> TomJaeger: having distro diverting from upstream create distro specific bugs and tension with uostream and is usually not a good thing
[14:09] <TomJaeger> As I said, upstream can't ship the change yet, because they can't be sure the drivers are fixed at this point
[14:10] <seb128> how can we be sure if they are not?
[14:10] <TomJaeger> this is what this whole bug is about
[14:10] <seb128> no, that bug is about fixing the drivers we have control over
[14:11] <seb128> the freedesktop guys could clearly do the same
[14:12] <TomJaeger> Some projects are slow to respond to bug reports, but these changes are going to happen upstream eventually
[14:12] <seb128> and I would argue that this bug is open for almost a year and has no duplicate so it's not a real issue for our users and probably not worth carrying this delta for cairo
[14:12] <TomJaeger> I think it's an important issue.  The browser is one of the first programs any user is likely to use
[14:13] <seb128> well nobody seems to notice or care
[14:13] <seb128> I for one have no issue with the current rendering
[14:13] <TomJaeger> And people do notice that scaled images look fine on Windows and look like shit on ubuntu
[14:13] <TomJaeger> People do care
[14:13] <huats> seb128: bug 330096
[14:14] <seb128> huats: thanks
[14:14] <huats> no pb (sorry I have been on the phone...)
[14:14] <seb128> that's ok
[14:14] <huats> seb128: I don't want you to think that I need 10 minutes to put on LP :=)
[14:14] <huats> :)
[14:14] <TomJaeger> seb128, especially with high-resolution screens being more common on laptops these days
[14:15] <huats> I am not as slow than didrocks on mariokart :P
[14:15] <seb128> TomJaeger: ok, can we get an upstream bug where upstream state they agree with the changes and will apply those once drivers are fixed then?
[14:15] <seb128> huats: ;-)
[14:15] <TomJaeger> seb128, this is more or less what Carl stated in that intel driver commit message
[14:15] <seb128> TomJaeger: we already had unhappy upstream due to distro changes and I would like to avoid that if not required
[14:16] <TomJaeger> I'm sure upstream is going to appreciate the work we are doing here
[14:17] <seb128> the commit message has a "(due to various bugs and workarounds in cairo and pixman)" mentions
[14:17] <seb128> do you have details on that?
[14:17] <TomJaeger> the bug was in pixman, the workarounds are in cairo
[14:17] <seb128> have those issues been addressed in jaunty?
[14:18] <TomJaeger> The pixman issue was fixed here: http://cgit.freedesktop.org/pixman/commit/?id=2d9c7cd84b276ebe2ff72d03c34a2d7f4f98b9f9
[14:18] <TomJaeger> This is not in jaunty as I don't think EXTEND_REFLECT is very important
[14:20] <seb128> ok
[14:20] <seb128> you seem to know what you are doing let's keep things this way for now
[14:21] <TomJaeger> thanks
[14:21] <seb128> sorry for the trouble but I'm trying to avoid adding random changes because somebody stated that was a good idea
[14:22] <seb128> we got bitten by such things turning to be not so great idea and make upstream not happy with ubuntu for shipping those changes
[14:22] <seb128> so it's always good to have an upstream bug stating that agree with the change when possible ;-)
[14:23] <TomJaeger> I'm kind of interested now, what was that change that upstream was unhappy about?
[14:24] <seb128> that's not especially on cairo
[14:24] <seb128> they were unhappy with the lcdfilter changes we have though
[14:25] <seb128> brb trying the new gvfs version
[14:28] <seb128> ok, works correctly
[14:34] <TomJaeger> seb128, Thanks, I'll take another shot at getting the remaining driver fixes accepted upstream, and as soon as that has happened, I'll bring up the issue on the cairo mailing list again.
[14:34] <seb128> TomJaeger: thank you for your work and being responsive to my comments!
[14:35] <TomJaeger> You're welcome
[14:38] <seb128> huats: usually users enjoy reading the NEWS entry in the debian changelog if you can copy it there ;-)
[14:38] <huats> seb128: hum...
[14:38] <huats> that is true
[14:39] <seb128> just a detail but I mention it
[14:39] <huats> you are right
[14:39] <seb128> it's handy to close bugs and nice to read
[14:39] <didrocks> huats: I prefer doing better packages than playing mario kart :p
[14:40]  * didrocks needs a real revenge on MK :)
[14:40] <huats> seb128: can you imagine, that didrocks has willingly forgotten his nintendo DS at home during the fosdem, to avoid playing MK with me ???
[14:40] <pitti> oh, is that the current game? I still live in the  frozen bubble world
[14:40] <seb128> lol
[14:40] <didrocks> seb128: that's false. I had my DS, huats not :)
[14:41] <huats> well he forgot to tell me : bring your, I'll have mine...
[14:42] <didrocks> huats: that's pretty different from what you were saying ;)
[14:44] <seb128> pitti: maria kart is quite old game though they do new versions for new machines ;-)
[14:44] <seb128> I've not played it for 15 years or so
[14:45] <pochu> ember: do you mean the change from 0.6.6-1ubuntu4 ?
[14:47] <huats> :)
[14:47] <huats> seb128: come to toulouse to do a conference :)
[14:47] <huats> and you'll be able to play :)
[14:47] <seb128> lol
[14:48] <huats> ;)
[14:48] <ember> pochu yes
[14:48] <didrocks> seb128: I will be there an next ubuntu party in Toulouse, please come so that I feel not lonely when loosing :)
[14:48] <pochu> ember: no idea, kees did that change
[15:18] <seb128> huats: you need to update the libgcr0 shlibs too
[15:18] <huats> pfff
[15:18] <huats> I gave you the wrong stuff
[15:18] <seb128> lol
[15:18] <seb128> yeah yeah
[15:19] <huats> (yeah that sounds weird but I am on 2 computer this afternoon..)
[15:19] <huats> and I did the update on both
[15:19] <rickspencer3> pitti: ping
[15:23] <seb128> huats: the new gnome-keyring works correctly here
[15:23] <huats> ok
[15:23] <huats> great
[15:25] <seb128> huats: so you can update the changelog to list the change and close bugs and update the shlibs? then I can sponsor the upload ;-)
[15:25] <huats> ok
[15:25] <huats> no pb
[15:25] <huats> I'll
[15:26] <seb128> thanks
[15:54] <pitti> rickspencer3: pong
[16:01] <ember> Keybuk there?
[16:01] <Keybuk> yup
[16:01] <ember> i was talking with kees about a inotify change in tracker
[16:02] <ember> ubuntu as been using fs.inotify.max_user_watches = 524288
[16:02] <Keybuk> right
[16:02] <ember> debian added the change and increase to fs.inotify.max_user_watches = 65536
[16:02] <Keybuk> that's a tenth of our value?
[16:03] <ember> so i should keep the ubuntu change or drop it?
[16:07] <Keybuk> keep it
[16:07] <ember> ok, thanks.
[16:45] <jeromeg> hello guys
[16:46] <jeromeg> I packaged abiword 2.6.6 which fixes a lot of annoying bugs
[16:46] <jeromeg> I would like to get it in before feature freeze
[16:47] <jeromeg> could someone review my package attached to bug #318444 ?
[16:47] <pitti> jeromeg: can you please sub ubuntu-main-sponsorss?
[16:47] <pitti> jeromeg: btw, that doesn't sound like a FF issue, if it's mostly bug fixes
[16:47] <pitti> jeromeg: so we can get it in a bit later, but either way, we'll try to look at it ASAP
[16:47] <pitti> jeromeg: thanks a lot for the update!
[16:48] <jeromeg> pitti: unfortunately, I won't be available a lot in the next fex days, so I would have liked to have someone look at it today
[16:48] <jeromeg> so I can fix things if I made some stupid mistakes
[16:49] <pitti> jeromeg: understandable; I just have to leave in about 15 mins, and still working on something :(
[16:50] <jeromeg> pitti: ok, no problem
[16:50] <pitti> jeromeg: judging by the changelog it looks alright
[16:51] <pitti> jeromeg: btw, please don't attach orig.tar.gz's to bug reports, an URL to the upstream location suffices :)
[16:51] <pitti> (and we'll download that one anyway)
[16:51] <jeromeg> pitti: the tarball is repackaged
[16:51] <pitti> or did you repack the upstream tarball?
[16:51] <pitti> ah
[16:51] <pitti> what changes, out of interst?
[16:51] <jeromeg> I'm not the one who started this, debian does it too
[16:51] <jeromeg> pitti: it's a merge of four tarballs
[16:51] <pitti> right, I just don't remember why it's necessary - some nonfree bits?
[16:52] <pitti> ah, that
[16:52] <jeromeg> abiword, abiword-help, abiword-plugins, abiword-extras
[16:52] <pitti> jeromeg: does this have a debian/rules get-orig-source?
[16:52] <jeromeg> there is a README.source at the root of the tarball
[16:53] <jeromeg> pitti: I found 3 or 4 additionnal LP bugs closed by this upgrade, shall I update the changelog, or closing them by hand after the upload is ok ?
[16:54] <pitti> jeromeg: closing by changelog is always nice, for keeping a permanent cross-ref
[16:54] <jeromeg> ok, I'll attach the updated package then
[16:54] <pitti> jeromeg: awesome, thank you
[16:58] <seb128> huats: hello? ;-)
[17:06] <huats> seb128: I am here..
[17:06] <huats> seb128: I will put that in 5 minutes
[17:06] <huats> I was away
[17:07] <seb128> huats: ok, sorry for pinging on this one, I will be cool again on the next ones ;-)
[17:07] <huats> no pb
[17:08] <seb128> huats: you signed up for some responsability you get the pressure going with those ;-)
[17:08] <huats> I start to know how you are :)
[17:09] <pitti> huats: didn't know seb128's whip before? :-)
[17:09] <huats> nope
[17:09] <pitti> PHEAR
[17:09] <huats> ... i should have been more careful...
[17:09]  * pitti hugs seb128 and huats
[17:10] <huats> :)
[17:10] <seb128> pitti: I try to not scare them too early, now that they joined motu though ... ;-)
[17:10]  * seb128 hugs pitti
[17:10] <pitti> seb128: ... there's NO way back!!11!
[17:10]  * seb128 hugs huats
[17:11]  * huats hugs both seb128 and pitti
[17:12] <pitti> huats: seriously, the Ubuntu user crowd will appreciate your help
[17:12] <huats> :)
[17:12] <huats> for what ? getting whipped by seb128 :)
[17:13] <seb128> better you than them no? ;-)
[17:13] <seb128> ahahah ;-)
[17:13] <huats> ;)
[17:13] <seb128> see what happens when I get bored because contributors claims all upgrades but don't give me something to review ;-)
[17:15] <huats> seb128: I am having trouble to associate the various bug fixes to the elements of the NEWS file
[17:21] <seb128> huats: use https://bugs.launchpad.net/bugs/bugtrackers/gnome-bugs/nnnnn ?
[17:21] <ember> seb128 if you so bored there's a tomboy update awaiting to be sponsored :o
[17:21]  * ember hides
[17:21] <seb128> huats: where nnnn is the gnome bug number, it will give you the ubuntu bug if there is one
[17:21] <huats> ok
[17:22] <seb128> ember: I try not touching monon when I don't have to
[17:22] <huats> seb128: the thing is that all bug linked from LP are still not marked as resloved upstream
[17:22] <seb128> and I'm not really bored ;-) I might have a look to sponsoring when I'm done looking at some evolution changes though
[17:23] <huats> seb128: let's no close bugs automatically
[17:23] <seb128> huats: ok
[17:23] <huats> and I'll close them manually
[17:23] <huats> (I'd rather have an opened bug in LP instead than a false close one... well I think it is better)
[17:23] <ember> the only "monon" i touch is tomboy
[17:23] <huats> (but I might be wrong)
[17:24] <seb128> huats: right, I though they had fixed the fix commited bug before rolling the tarball but apparently not
[17:25] <seb128> brb
[17:27] <didrocks> you're crazy guys ;)
[17:30] <didrocks> huats: if you want, I think I can whip seb128 for sponsoring too. He owns me 3 :)
[17:31] <didrocks> huats: hum no… that's true that you are always putting my leg about mario kart, so I won't :p
[17:31] <seb128> didrocks: I'm doing sponsoring next
[17:31] <didrocks> seb128: just kidding, no emergency ^^
[17:32] <didrocks> as all those packages will have FFe, I think :)
[17:32] <seb128> I know there is no hurry, I would have sponsored those already otherwise ;-)
[17:32] <seb128> didrocks: right, there is no freeze for GNOME
[17:32] <didrocks> seb128: as huat's one, for instance? :p
[17:32] <seb128> yes
[17:32] <seb128> getting the ssh agent fixed would stop angry people who can't commit to svn due to that
[17:32] <seb128> or rather who have to type their password a zillion time a day
[17:33] <didrocks> it's understandable ^^
[17:34] <didrocks> btw, I have to ping ubuntu-server team to know why there is no ssh-agent by default on server (it can be sometimes useful)
[17:34] <huats> seb128: it is on LP
[17:35] <seb128> huats: thanks
[17:37] <seb128> didrocks: btw there is a new gnome-python-extras version for you
[17:37] <seb128> didrocks: and gnome-python-desktop too
[17:37] <didrocks> seb128: some work to do, so, I'm on it
[17:38] <didrocks> :)
[17:38] <seb128> ;-)
[17:38] <seb128> didrocks: there is also vino and vinagre if you want to do those
[17:38] <didrocks> seb128: I put them on my schedule too :)
[17:43] <didrocks> seb128: is it normal that gnome-python-desktop is not in bzr for ~desktop-team?
[17:43] <seb128> didrocks: it was supposed to be there? is there still a sponsoring request pending for it that I forgot about because it's not on the list?
[17:44] <didrocks> hum, let me check
[17:45] <seb128> huats: the shlibs to update is the libgcr0 one and not the libgnome-keyring one
[17:45] <huats> seb128: there is a shlibs for libgnome-keyring
[17:45] <didrocks> seb128: gnome-python-desktop was sponsored and I attached the bzr branch
[17:45] <seb128> huats: and now you need one for libgcr0
[17:46] <seb128> didrocks: ok so I didn't push it probably, where is it?
[17:47] <didrocks> seb128: https://code.edge.launchpad.net/~didrocks/+junk/gnome-python-desktop but you can push it next time :)
[17:47] <seb128> huats: no .shlibs means there is no version specified, which was correct for libgcr since that's a new lib
[17:47] <seb128> didrocks: ok, will do that then
[17:47] <didrocks> seb128: I used +junk because there is no gnome-python-desktop project in LP
[17:48] <seb128> didrocks: https://edge.launchpad.net/gnome-python-desktop ?
[17:49] <didrocks> that's strange, it refused it to me. I will try again to push the branch later
[17:49] <crevette> didrocks: I have the same problem for my packaging
[17:50] <didrocks> crevette: even with project that are on LP
[17:50] <crevette> I tried to push my own branch for obex-data-server but I wasn't allowed to, wo Ipushed to +junk
[17:50] <seb128> crevette: you need to have a product using the same name on launchpad, if your packaging is nautilus-sendto-universe that's normal
[17:50] <didrocks> seb128: it's ok now
[17:50] <crevette> seb128: no obex-data-server
[17:50] <didrocks> seb128: Registered
[17:50] <didrocks> 2009-01-27
[17:50] <didrocks> :)
[17:51] <huats> seb128: ok
[17:51] <seb128> didrocks: yes, I pinged jcastro recently about it I think
[17:51] <seb128> didrocks: but your request is not waiting for 3 weeks is it?
[17:51] <seb128> crevette: weird, https://edge.launchpad.net/obex-data-server
[17:51] <didrocks> seb128: I think I created the branch in ~didrocks before the creation
[17:51] <didrocks> of the project
[17:51] <seb128> ok
[17:52] <huats> seb128: (it is corrected)
[17:53] <huats> so if I understood you well
[17:54] <huats> there was no need for the 2.25.90 since the lib was new in that release, but now we need it, since there was a .shlibs in the package
[17:54] <huats> ?
[17:54] <seb128> huats: almost good, the libgnome-keyring shlibs doesn't need an update
[17:55] <seb128> just libgcr
[17:55] <seb128> the shlibs need to be updated when there is an api addition
[17:55] <seb128> libgcr was new so there was no api addition in a specific version so no need to specify one
[17:55] <seb128> now there is one
[17:55] <seb128> so you need to specify that
[17:56] <seb128> didrocks: you should talk to dholbach
[17:56] <seb128> didrocks: your bugs fail to be listed, probably because you have no comment
[17:56] <seb128> just guessing
[17:56] <seb128> I will add a thanks for your work on one to see ;-)
[17:57] <didrocks> seb128: oh? yes, try this and we will see :)
[17:57] <huats> seb128: ok
[17:57] <huats> I understand now
[18:02] <huats> seb128: better on LP ?
[18:04] <seb128> huats: yes ;-)
[18:04] <seb128> huats: sponsoring this one
[18:06] <seb128> ok, I'm away for dinner, I'll do some sponsoring after that
[18:06] <seb128> huats: you still have gtksourceview on your list, no hurry for this one
[18:06] <seb128> huats: you can do alacarte and bug-buddy next if you want
[18:06] <seb128> or work on the libgda update
[18:08] <huats> seb128: I will tackle gtksourceview (just need to test run it now)
[18:09] <huats> and I might give a chance to put it in bzr
[18:09] <huats> and then tomorrow we'll see what remains :)
[18:10] <vuntz> seb128: I'm sure you want to give me 10 minutes of your time
[18:10] <vuntz> :-)
[18:11] <huats> hey vuntz
[18:11] <pitti> bonsoir vuntz
[18:11] <vuntz> Guten Abend, Herr Pitt
[18:12] <vuntz> seb128: just wondering about /etc/gconf/2/path in ubuntu
[18:12] <pitti> comment vas-tu?
[18:12] <vuntz> seb128: why did you add gconf.xml.system instead of fixing the PK stuff upstream to use gconf.xml.defaults?
[18:13] <vuntz> pitti: es geht gut
[18:13]  * vuntz hopes pitti doesn't want to test the limits of his german ;-)
[18:14] <pitti> vuntz: don't worry, that's about the limit of my French :)
[18:14] <pitti> well, that, and a few phrases which aren't quite suitable here :)
[18:14] <vuntz> heh
[18:18] <seb128> vuntz: I've to go now but I will be back after dinner
[18:19] <seb128> vuntz: we did those changes way before the upstream changes you are speaking about
[18:19] <seb128> vuntz: we move the schemas default to var and have a debian tool to write distribution defaults
[18:19] <vuntz> seb128: nah, nah, nah. I'm talking about something else :-)
[18:19] <seb128> vuntz: the idea is that there is 3 set of settings, upstream, distro, systeadmin
[18:19] <vuntz> seb128: you added gconf.xml.system later
[18:20] <seb128> vuntz: I didn't do any packaing change when updating today
[18:20] <vuntz> don't know about today
[18:20] <vuntz> anyway
[18:20] <vuntz> just ping me back after dinner
[18:20] <seb128> vuntz: ah, mvo did that, ping him
[18:21] <seb128> vuntz: I think that's because he was getting an error while trying to set system defaults and assumed that's because the directory was not available or something
[18:21] <vuntz> mvo: my friend?
[18:21] <seb128> I've to go but I will be back after dinner ;-)
[18:21] <mvo> vuntz: I need to leave in 2min - what is the matter?
[18:21] <seb128> gconf (2.23.2-0ubuntu3) intrepid; urgency=low
[18:21] <seb128>   * create /etc/gconf/gconf.xml.system
[18:21] <seb128>   * include it in the default gconf path
[18:21] <seb128>  -- Michael Vogt <michael.vogt@ubuntu.com>  Thu, 11 Sep 2008 13:33:30 +0200
[18:21] <seb128> I guess that's this change
[18:22] <vuntz> mvo: just ping me back when you'll be back, then. Nothing urgent
[18:22] <mvo> vuntz: ok
[20:16] <Spinus> hi guys!...I'm trying to do a merge between Pidgin (ubuntu version) and the new debian version..could someone help me? :)
[21:31] <chrisccoulson> bryce - do you think it would be useful to have timestamps in Xorg log files?
[22:56] <seb128> asomething: there?
[23:44] <ember> seb128 mind if i do gnome-themes and gnome-terminal?
[23:45] <seb128> you can do those updates
[23:45] <ember> ok thanks.
[23:49] <asomething> seb128: i'm back
[23:49] <seb128> asomething: hello, want to do the e-d-s, evolution, evolution-exchange 2.25.91 updates?
[23:50] <asomething> seb128: sure thing
[23:50] <seb128> asomething: let me look at your evolution documentation split again, I looked quickly before and had some comments
[23:50] <asomething> seb128: Bug #272779
[23:50] <seb128> thanks for the bug number -;)
[23:51] <seb128> asomething: why did you add a documentation-common?
[23:52] <asomething> seb128: it's the C locale, should I just do a documentation-c
[23:52] <seb128> asomething: no, don't split this one, we want to keep one documentation always installed I think
[23:52] <seb128> just keep it where it's no, evolution-common?
[23:53] <seb128> asomething: otherwise I'm not sure the enhances evolution and recommends documentation-en are useful
[23:54] <seb128> recommends are installed by default, why installing the german translation should trigger the english one?
[23:54] <seb128> also you need to use replaces on evolution-common (<< 2.25.90-0ubuntu3)
[23:54] <seb128> since you move files between binaries
[23:55] <asomething> seb128: i assume that English will always be full, so I install it as a back up
[23:55] <seb128> isn't C there for that?
[23:56] <seb128> you might want to no split -en in this case
[23:58] <asomething> so leave C in evo-common and not recommend -en?
[23:59] <seb128> I'm not sure about the recommend
[23:59] <seb128> hum