=== BugMaN1 is now known as BugMaN [08:37] morning here ! [11:16] mvo: can you look at bug #271108? [11:16] Launchpad bug 271108 in gnome-control-center "http_proxy environment variable is not being updated" [Low,Incomplete] https://launchpad.net/bugs/271108 [11:19] seb128: sure, thanks [11:52] mvo: ping [11:53] i need some help with debian patches :-) === davmor2 is now known as davmor2-away [13:16] njpatel: hello! sure, I tell me more (I was at lunch) [13:16] mvo: hey, no probs -- I figured it out!!! [13:16] :-D [13:17] I was stuck with multiple patches which touch Makefiles, I couldn't get them to apply or unapply cleanly, but somehow I've fixed it now [13:18] ok [13:25] mvo: do you plan to do a gnome-control-center upload today? [13:26] seb128: very soon, hopefully with a fix for 271108 [13:26] bug #271108 [13:26] Launchpad bug 271108 in gnome-control-center "http_proxy environment variable is not being updated" [Medium,Triaged] https://launchpad.net/bugs/271108 [13:26] seb128: why? anything oyu need? [13:26] mvo: ok thanks [13:26] seb128: if its urgend, just go ahead, bzr is fine for upload [13:26] mvo: no, I just look daily at the sponsoring list and I would like to get the 2 gnome-control-center lines you commited to bzr to get cleaned ;-) [13:27] heh :) [13:27] ok [13:27] and one is a string change so better for translators to get the right string early [13:27] anyway nothing urgent, it's just pending upload for a while now so I was wondering [13:28] maybe I can add that as a reason to not like bzr :-p fixes are delayed ;-) === davmor2-away is now known as davmor2 [14:16] hey tedg [14:17] seb128, the new cairo now requires pixman >= 0.12.0 [14:17] Good morning seb128 [14:17] tedg: I've sponsored some of the updates waiting on your ppa [14:17] seb128, btw, thanks for fontconfig yesterday [14:17] seb128: Awesome, thanks, I haven't looked yet, but did the UIe get processed for FUSA? [14:17] fta: thank you for working on the change ;-) [14:18] fta: since when is this new pixman version available? [14:18] tedg: that was required? GNOME has a standing exception, I just uploaded ;-) [14:18] seb128, 2 days ago [14:18] seb128, want me to do it ? [14:19] seb128: :) Thank you. [14:19] fta: no, I'm pinging the debian guys, they usually prefer to be notified so they can do the update and ubuntu can stay in sync [14:19] ok [14:19] seb128, same for cairo ? [14:19] fta: btw is there still any change in cairo we need or can we sync on debian? [14:23] seb128: Did you do xscreensaver also? [14:23] tedg: no [14:24] seb128, still our freetype/fontconfig debps/build-deps versions that are higher [14:24] fta: that's not required, hardy or intrepid have the required versions [14:27] seb128, everything else is minor, i guess sync is ok. i'll stop my 1.7.6 update then. [14:28] btw, debian doesn't have it yet so there's nothing to sync at the moment [14:29] fta: you can still work on the cairo update if you want, not sure how reactive is the cairo debian maintainer at the moment [14:31] considering i need the new pixman, either i do both or i wait for debian [14:34] wait for debian [14:34] ok [14:38] mvo, hi, packagekit 0.3.3 freeze exception was approved. the packages are in the ppa. do you have got the time and willing to upload them? [14:39] mvo, https://edge.launchpad.net/~packagekit/+archive [14:39] mvo, https://bugs.edge.launchpad.net/ubuntu/+source/packagekit/+bug/268466 [14:39] Ubuntu bug 268466 in packagekit "Freeze Exception for PackageKit 0.3.2" [Undecided,Confirmed] [14:41] mvo, I have to leave now, since I am approaching my home town. See you. [14:54] hi everybody [14:54] just trawling the irc channels looking for some help on usb sticks and grub if anyone has the time? [14:55] discobiscuit: #ubuntu is a good start [14:58] yeah going to learn for the linux+ exam from it [15:14] re [15:15] mvo: did you do your quota of sponsoring for this week yet? ;-) [15:16] seb128: no, why [15:16] * seb128 is trying to dispatch some sponsoring work there ;-) [15:16] I'm currently reviewing/sponsoring packagekit [15:16] mvo: kwwii has some artwork packages to get sponsored, he pinged me about those yesterday because pitti which usually look at those is away for the week [15:16] but I have cycles I think [15:16] is there a bugrpeort for them? [15:17] but I did spent too much time on sponsoring today and it would be nice if somebody else could look at those [15:17] mvo: no, it's on his ppa on launchpad [15:17] mvo: maybe ping him on irc to confirm the list? [15:18] asac: could you look at the devhelp sponsor request? ;-) [15:18] hm, looks like he is not now currently [15:18] mvo: he's on #canonical, not sure why he's not hanging there though [15:21] seb128: ok, I /msged him [15:21] mvo: thank you [15:21] * seb128 is trying to get some GNOME work before the weekend, new version again on monday [16:42] seb128: I'm kinda confused. I changed the defaults of the FUSA schema file, but still seems like they're being used on a new account I created. Is there some other thing that needs to be done? [16:44] tedg: depending how/were you changed it you need to run update-gconf-defaults I think (but dh_gconf should take care of it) [16:45] tedg: how did you change those? [16:45] tedg: the usual way is to add a .gconf-defaults [16:45] mvo: Do I need a dh_gconf in the rules file? There isn't one there now. But gnome.mk is included. [16:45] if gnome.mk is being used no need no [16:45] seb128: I put it in a patch. [16:45] ok, thanks. gnome.mk should be enough [16:46] did you patch the schemas.in? [16:46] seb128: Yes. [16:46] usually you don't want to patch the schemas [16:46] but add a debian/binary.gconf-schemas which set those [16:47] I'm not sure what you're saying in the second line there. Is this a file or a line in my rules? [16:48] tedg: that's a file [16:48] And that has the whole schema, or just the diff? [16:48] tedg: locate .gconf-defaults [16:48] tedg: check /usr/share/gconf/defaults/10_compiz-gnome for a example [16:49] tedg: that's a debian think, if dh_gconf is used which is the case there you have nothing to do, just add a .gconf-defaults in the debian directory [16:50] Is there a difference between "gconf-defaults" and "gconf-schemas" ? [16:50] yes [16:50] Which should I use? [16:50] guys an ideas why the screen saver isn't kicking in? It starts to fade then almost immediately wakes again [16:50] the schemas are upstream gconf files to set defaults [16:50] the .gconf-defaults one are debian specific files to override upstream defaults without having to patch the schemas [16:51] Okay, so if I'm adding a GConf item, I should patch the schemas? And if I'm changing a value I should use the defaults in the packaging. Is that correct? [16:51] no [16:52] you can still use a .gconf-defaults in the new key case but it'll not have a description, etc [16:52] but right if you add upstream keys you can edit the schemas yes [16:53] just make sure to edit the right .in or .in.in so they are in the schemas after build [16:53] I've to run for a bit, bbl [16:53] Okay, I will those seem to be getting added more reliably. Value changes I think are getting caught up in the layers of settings. === asac_ is now known as asac