[06:58] <pitti> asac: I wouldn't like to update the entire NM post-release, but certainly we can cherrypick fixes
[06:58] <pitti> asac: so I guess it depends whether the beta/rc snapshots are stable enough
[08:58] <seb128> hello
[09:03] <pitti> hey seb128
[09:03] <seb128> hey pitti!
[09:03] <pitti> seb128: enjoying the last GCDS day?
[09:03] <seb128> pitti, enjoying being back home rather ;-)
[09:04] <pitti> ooh
[09:04] <seb128> pitti, I did travel back yesterday evening
[09:05] <seb128> how was the week for you?
[09:05] <seb128> thanks for fighting the new gdm issues
[09:07] <seb128> pitti, congrats for your gvfs changes being commited ;-)
[09:07] <pitti> seb128: week> in between fixing gdm and fixing p-distutils-extra :)
[09:07] <pitti> seb128: thanks; I'm sure I can get the gphoto bits in as well
[09:16] <pitti> seb128: gdm> bug 396226 is still a pain
[09:17] <pitti> my preferred solution is to fix getty to exit if it sees that vt1 is already taken
[09:17] <pitti> I'll look into that now
[09:17] <seb128> is that specific to the changes you did?
[09:17] <seb128> because I never had the issue and I'm running the new gdm on 2 boxes every now and then since jaunty
[09:18] <pitti> seb128: not particularly to "my" changes, it's just what gdm does
[09:18] <pitti> gdm starts before getty, so X takes the first available tty, which is 1
[09:18] <seb128> well it's weird that nobody noticed before the karmic upload while it was in the ppa
[09:18] <pitti> later, getty comes along and also listens to tty1, eventually times out, closes the vt, and takes X with it
[09:19] <seb128> I'm still running 0ubuntu1 and didn't get the issue either
[09:19] <pitti> seb128: are you running with usplash?
[09:19] <seb128> yes
[09:20] <pitti> seb128: does gdm start at vt1 initially?
[09:23] <seb128> pitti, how do I know? I asked you yesterday but got disconnected I think
[09:23] <seb128> I'm using autologin so I've no gdm greeter running
[09:23] <pitti> seb128: boot, and then do ctrl+alt+f2
[09:23] <pitti> and ctrl+alt+f1
[09:23] <pitti> oh
[09:23] <pitti> that might change things, yes
[09:24] <pitti> seb128: but still ctrl+alt+fn shows you which console X is running on
[09:24] <seb128> it's running on vt7
[09:24] <seb128> my session is I mean
[09:24] <pitti> okay
[09:24] <pitti> so anyway, I'll look into this now
[09:25] <seb128> thanks
[09:32] <chrisccoulson> good morning everyone
[09:33] <pitti> hey chrisccoulson
[09:33] <chrisccoulson> hi pitti
[09:59] <asac_> pitti: cherry picking fixes wont work
[09:59] <asac_> well it does
[10:00] <asac_> its just a post release bump
[10:00] <asac_> if we cant do that i wont do it
[10:00] <asac_> we would end up in the same situation as with NM in intrepid
[10:01] <asac_> point is that F12 releases a few weeks after us
[10:02] <pitti> asac_: ok, so we could give it a lot of testing then
[10:02] <asac_> yes.
[10:02] <pitti> so, either it works well enough to not produce "critical" bug reports, then we can just leave it as it is
[10:02] <asac_> yeah of course
[10:02] <pitti> or we do get them, then we have people who can test the new version
[10:03] <pitti> it becomes tricky if the final version relies on a newer kernel, or newer driver versions
[10:03] <asac_> pitti: no thats not what will happen
[10:03] <pitti> i. e. if they do things like iw->cfg80211 in between our snapshot and final
[10:03] <seb128> hey chrisccoulson
[10:03] <seb128> hey asac
[10:04] <chrisccoulson> hi seb128
[10:04] <asac> pitti: no... i am sure i can confince dan to not do that
[10:04] <asac> pitti: same for not changing ABI/API
[10:04] <asac> et al
[10:04] <asac> seb128: hi
[10:04] <pitti> asac: so it seems that it'd be best to get it in early?
[10:04] <asac> yeah
[10:04] <chrisccoulson> seb128 - i got to the bottom of the metacity respawning issue. it was a metacity bug in the end rather than a gnome-session bug
[10:05] <asac> ill talk today again with dan... otherwise check if if there are problems with any rdepends and if htere is nothing upload
[10:05] <asac> sounds good
[10:06] <asac> seb128: still on the beach ;)?
[10:07] <seb128> chrisccoulson, yeah I read your comments by email, good job there
[10:08] <seb128> asac, no, back to rainy germany yesterday evening ;-)
[10:09] <chrisccoulson> seb128 - is there any way of starting a failsafe xterm from the new GDM? it's quite useful when debugging issues like that
[10:09] <asac> seb128: germany? or elsaß ;)?
[10:10] <seb128> asac, neither of those but my part of france which is not elsaß ;-)
[10:10] <asac> hehe
[10:29] <mvo> hey seb128, welcome back \o/
[10:29] <seb128> hey mvo!
[10:29]  * seb128 hugs mvo
[10:29] <seb128> good to have some working internet again ;-)
[10:29] <mvo> :)
[10:30] <seb128> mvo, while I'm still thinking about it, I don't think we conclude on the cron discussion the other day
[10:30] <mvo> seb128: I have not added it, but I think its fine to do
[10:31] <seb128> the xapian things eating my battery at conference, do you consider is as a cron issue?
[10:31] <mvo> personally I think cron.weekly / monstly should not run on battery
[10:31] <mvo> its usually heavy stuff
[10:32] <seb128> yeah, after stopping xapian I had updatedb
[11:01] <seb128> mvo, how come that synaptic is outdated in ubuntu, aren't you upstream for it? ;-)
[11:05] <mvo> seb128: version-numbers ... *pfff*
[11:05] <seb128> mvo, it's red on http://people.ubuntu.com/~seb128/versions.html
[11:06] <mvo> well, its just a version, they are slightly different in both distros
[11:06] <mvo> but I can do a merge :)
[11:07] <mvo> btw, is there a way to see how well the buildds for ddebs.ubuntu.com doing? I'm waiting for a updated kernel debug package
[12:34] <seb128> re
[12:34] <seb128> grrrr karmic crashing while being away
[12:34] <seb128> if somebody wrote something for me during lunch time please do it again
[12:42] <chrisccoulson> seb128 - i don't think you missed anything. it's been pretty quiet for a little while now
[12:43] <seb128> ok thanks
[12:56] <geser> seb128: as you uploaded gnome-shell, do you know where gjs-dev is as it depwaits on it?
[12:56] <seb128> geser, the gnome-shell upload was a mistake it was supposed to be a ppa upload
[12:57] <seb128> dunno who accepted it but it's going to stay in this not building state for a few weeks
[12:57] <seb128> it requires git versions or random components and new depends
[12:57] <geser> ok
[14:08]  * asac break
[14:13]  * lool repairs asac 
[14:19] <seb128> lool!!!
[14:19] <seb128> lool, bien rentré ?
[14:21] <pitti> asac: is bug 220628 really a hardy issue in libxcb?
[14:23] <rickspencer3> seb128: lool: are you still enjoying GC?
[14:25] <seb128> rickspencer3, hey, had a nice trip back?
[14:25] <rickspencer3> seb128: long, but fine
[14:25] <seb128> rickspencer3, I was flying back yesterday evening, I'm enjoy working internet in rainy weather today
[14:25] <rickspencer3> lol
[14:25] <seb128> ;-)
[14:26] <rickspencer3> it's really rainy here to
[14:26] <pitti> hey rickspencer3
[14:26] <pitti> rickspencer3: back as well, or still at GC?
[14:27] <rickspencer3> yes, I am enjoying two days off .. but of course woke up incredibly early this morning
[14:27] <pitti> ah, the usual westwards syndrome
[14:28] <rickspencer3> seb128: lool: I was thinking that perhaps next week the three of us could cuddle so you could advise me on the best way we could help GNOME with GNOME 3
[14:28] <rickspencer3> oops
[14:28] <rickspencer3> I meant huddle, not cuddle
[14:28]  * rickspencer3 notes that the trip was not *that* team building
[14:29] <seb128> lol
[14:29] <seb128> rickspencer3, yes sure
[14:30] <rickspencer3> seb128: thanks ... I think I should be a bit more rational after a few days off ;)
[14:32] <seb128> np, taking some time for thinking is often a good idea ;-)
[14:47] <lool> seb128: Return was fine yeah
[14:49] <lool> rickspencer3: That sounds good (cuddling and chatting around GNOME 3)
[14:51] <rickspencer3> lol
[14:56] <dobey> james_w: ping. why didn't you use cdbs with python-oauth?
[14:57] <james_w> because I didn't want to?
[14:59] <james_w> I find it to be a net loss of time in the long run
[15:01] <praveen1> is there any blueprint or list of things being done to reduce power consumption in karmic?
[15:01] <seb128> praveen1, try asking on #ubuntu-devel that's not really desktopish
[15:01] <praveen1> k
[15:09] <asac> pitti: the one left is not yet understood
[15:09] <asac> pitti: but its not a regression
[15:09] <asac> e.g. the bug itself is fixed, what is left is another bug
[15:15] <dobey> james_w: how so? isn't typing "include blahblahblah.mk" faster than writing out all the build rules? :)
[15:18] <didrocks> hey
[15:18] <seb128> lut didrocks
[15:18] <didrocks> seb128: hey o/ To answer to your question, it's better today, but the organization is not so good
[15:22] <james_w> dobey: but *reading* blahblahblah.mk is a different matter
[15:23] <seb128> let's not troll on cdbs or not
[15:24] <seb128> for weird packages when you need to take special action it might be less handy
[15:24] <seb128> in common cases it just works
[15:25] <james_w> yup
[15:25] <dobey> james_w: i don't want to read it, i want it to work :)
[15:25] <james_w> we can all dream :-)
[15:31] <asac> pitti: did you remove the verification-done tag because the libxcb update was rolled out or because you think its not verified? Bug 220628
[15:31] <asac> i think the problem reported is really a different bug ... just related and was previously hidden because the other just happened sooner
[15:31] <asac> it shouldnt hold back the roll out if libxcb wasnt rolled yet.
[15:31] <asac> at least from what i read everybody agreed that its better with that new libxcb?
[15:40] <dobey> james_w: well it works for python-oauth... i had to switch it over to be able to build it on hardy :)
[15:40] <james_w> dobey: shouldn't have
[15:41] <dobey> james_w: i wouldn't have touched rules if it had Just Worked (TM) :)
[15:42] <dobey> james_w: but --install-layout wasn't a valid option
[15:42] <james_w> ah
[15:42] <james_w> well, let's fix that
[15:44] <dobey> james_w: bug #397431 if you please then :)
[15:44] <dobey> james_w: i also filed bug #397197 requesting a backport to jaunty, and the karmic package rebuilt as-is
[15:58] <james_w> dobey: done
[16:02] <dobey> james_w: hooray and hugs!
[16:23] <jcastro> seb128: are people supposed to not report bugs on -shell?
[16:23] <seb128> jcastro, why?
[16:24] <jcastro> seb128: I guess you invalided a bunch of bugs from forum users
[16:24] <seb128> jcastro, gnome-shell is not in ubuntu proper but in a ppa, I've asked users to report bugs directly upstream for it yes
[16:24] <jcastro> ok, I will go tell them that.
[16:25] <seb128> jcastro, we can't track git builds bugs mixed with ubuntu bugs and there is no ppa bug tracker
[16:25] <seb128> jcastro, thanks!
[16:25] <jcastro> yeah that's kind of a bummer
[16:25] <seb128> the ppa not having a bug tracker is annoying
[16:26] <seb128> but flooding the ubuntu components with upstream git bugs is not a good way either
[16:28] <seb128> jcastro, how did the couchdb presentation go yesterday?
[16:28] <jcastro> it went pretty awesome
[16:28] <jcastro> everything worked, even got applause a bunch of times
[16:29] <jcastro> the pitivi presentation was pretty exciting too, it's all working! didn't even crash.
[16:29] <seb128> cool!
[16:30] <jcastro> they are going to try to do gstreamer 1.0, jokosher 1.0, and pitivi 1.0 all in time for gnome 3
[16:31] <seb128> nice to see things aligning around GNOME3
[17:51] <pitti> good night everyone
[17:51] <pitti> have to go now
[17:58] <seb128> 'night pitti
[21:16] <chrisccoulson> nearly the weekend:)