[06:43] <dholbach> good morning
[08:58] <huats> morning everyone
[13:08] <ember> hey
[16:03] <pochu> lool: thanks for the Vinagre upload :)
[16:03] <pochu> seb128: could you please sync vinagre 2.23.2-1 from incoming.d.o?
[16:04] <seb128> pochu: I'm too lazy to do incoming syncing, will do that later when it's available on the mirrors, there is no hurry ;-)
[16:05] <seb128> pochu: you package 2.23 for debian already?
[16:05] <pochu> seb128: yup :)
[16:05] <pochu> seb128: but that's for experimental
[16:06] <seb128> good luck handling the bug load going with early unstable versions ;-)
[16:06] <pochu> .2 fixes a bug for which there's a request to get it into Hardy (and has a debdiff attached)
[16:07] <pochu> the one somebody asked you about it because it introduces a couple of strings
[16:07] <pochu> heh, thanks, but it's in experimental so hopefully not many people uses it :)
[16:10] <seb128> the ctrl-alt-del menu item bug?
[16:11] <pochu> seb128: yup
[16:12] <seb128> pochu: did you work on an hardy update for this one?
[16:12] <pochu> bug 199116
[16:12] <pochu> seb128: no, but someone else did and attached a debdiff to the report
[16:13] <pochu> seb128: BTW, 2.23.2 needs gtk-vnc 0.3.6 which needs to go though binary NEW
[16:13] <seb128> ok, good
[16:13] <seb128> ok
[16:13] <seb128> I'm still focusing on hardy but I'll start looking at the GNOME merges and updates after uds I think
[16:13] <pochu> slangasek asked in the bug report to fix it in Intrepid first, so with this sync we should be done
[16:16] <pochu> I was looking at pygobject FTBFS yesterday, and spent about 2 hours on it, and I finally realize it was still failing to build because of a bug in my shell...
[16:16] <pochu> I think I got the bug fixed, but couldn't check it
[16:17] <pochu> has someone noticed that bash-completion doesn't work properly for some cases? I think that was related as the build failures where syntax issues
[16:17] <pochu> I even tried building Vinagre 0.5 and other things and they all failed
[16:18] <pitti> seb128: I've got a question: https://bugs.edge.launchpad.net/ubuntu/+source/gdm/+bug/229866/comments/4
[16:18] <pochu> 'dpkg -L libgtk<tab>' completes to 'dpkg -L libgtk^[\[m^[\[K^[\[m^[\[K'
[16:19] <pochu> it could also be that I've messed up my .bashrc or something like that... I'll try with a new user and see if that's still happening
[16:19] <pitti> seb128: (added a further comment)
[16:20] <seb128> pitti: looking
[16:23] <seb128> pitti: the commit log on http://svn.gnome.org/viewvc/gdm?view=revision&revision=6167 has some details
[16:24] <seb128> pitti: http://bugzilla.gnome.org/show_bug.cgi?id=509141 comment #15 too
[16:24] <pitti> seb128: right, I saw that; I mean the G_BROKEN_FILENAMES removal
[16:25] <pitti> ah, that was the same commit
[16:26] <pitti> seb128: right, so they suggest that we set this in our distro specific Xsession.common?
[16:26] <seb128> pitti: G_BROKEN_FILENAMES is something to set when you don't use an utf-8 locale
[16:26] <pitti> seb128: which is not our default, but many people still have that (unfortunately)
[16:26] <seb128> well, I've rebooted with the new version
[16:26] <seb128> but this one should not be set on systems using an UTF-8 locale
[16:27] <seb128> I'm wondering if that was really set
[16:27] <seb128> do you have it defined?
[16:27] <pitti> seb128: would that be in /etc/gdm/Xsession ?
[16:27] <lool> seb128: The new vinagre versions don't seem that disruptive
[16:28] <lool> pochu: Could you comment on that ::1/localhost bug?  I tried reproducing it, but I couldn't with the latest vinagre
[16:28] <pitti> seb128: ok, grep -r G_BROKEN_FILE /etc doesn't deliver anything
[16:28] <lool> (I could connect to localhost and to ::1 just fine)
[16:28] <seb128> pitti: we install debian/Xsession
[16:28] <pitti> seb128: when you install the new .deb, do you actually get a 'installing new conffile' note?
[16:28] <pitti> seb128: aah
[16:29] <seb128> pitti: so the change doesn't make a difference for us
[16:29] <pitti> seb128: alright then, thank you!
[16:30] <seb128> pitti: thank *you* for being careful when checking uploads ;-)
[16:33] <pochu> lool: I don't know anything about IPv6, but I asked jwendell (upstream of both vino and vinagre) and he told me that was a known issue and that it will be fixed in 2.24
[16:34] <pochu> lool: wait, let me check it
[16:38] <pochu> lool: reproduced here
[16:38] <pochu> lool: in Hardy, BTW
[16:38] <pochu> (vinagre 0.5.1)
[16:44] <pochu> lool: but that should be a vino bug
[17:00] <ember_> pochu do you have an example of a simple python package not using the default setup.py on install?
[17:02] <pochu> ember: decibel-audio-player uses a simple Makefile, and scribes uses autotools. Are any of them ok?
[17:05] <ember> well this one just uses "python install.py" for installing
[17:14] <pochu> ember: is install.py a distutils script?
[17:15] <pochu> if so, you can point to it in debian/rules (if using CDBS) with 'DEB_PYTHON_SETUP_CMD := install.py'
[17:15] <pochu> (https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml)
[17:16] <ember> no, is just a .py to check modules and with os.system("cp") to install py
[17:17] <pochu> heh
[17:17] <pochu> you can call it in the install rule
[17:20] <ember> hmm i'm gonna try packaging this one
[17:44] <mneptok> what a wonderful day.
[17:44] <seb128> hey mneptok
[17:44] <mneptok> heya seb
[17:45] <mneptok> for those with GNOME access and personal keys they no longer trust, please update your system, re-generate keys, and send mail to accounts@gnome.org with the subject "replace Debian/Ubuntu key"
[17:46] <mneptok> my day is going to suck, but i'll try to stay on top of key change requests @gnome.org caused by this.
[17:46]  * seb128 hugs mneptok ;-)
[17:46] <pedro_> niiice
[17:46] <pedro_> thanks mneptok :-)
[17:46] <mneptok> no promises, as i haven't talked to Zaid about watching GNOME.
[17:47] <seb128> mneptok: could you give an hint of what keys should not be trusted for those who are not security wizards there? ;-)
[17:47] <mneptok> but then i can guess the sabdfl's wishes, i think.
[17:47] <mneptok> if you are 100% absolutely certain you generated your SSH key on a Dapper or prior Ubuntu installation, do nothing.
[17:48] <mneptok> otherwise, you'll want to replace all your SSH keys, wherever they live.
[17:49] <mneptok> the updates today will check host-wide keys and re-generate them. expect hostkey change warnings from ~/.ssh/known_hosts
[17:50] <mneptok> but the packages do nothing vis-a-vis personal keys. please re-generate and get those to GNOME first. ;)
[18:05] <pochu> lool: I've tracked it down to GREP_OPTIONS="--color=always", with --color=auto (or without it) my shell works fine again. Seems to be Debian bug #414798
[18:05] <pochu> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414798
[18:05]  * pochu tries to build pygobject now
[19:15] <pochu> bah, I'm too stupid to be able to run autoreconf on pygobject
[19:16] <pochu> or pygobject is too b0rked
[19:18]  * jdavies hugs poor pochu 
[19:18] <pochu> :-)
[19:19] <pochu> seb128: I guess we still want 61_dont_use_setwakeupfd.patch in pygobject? that's our last diff
[19:20] <pochu> There's at least http://bugzilla.gnome.org/show_bug.cgi?id=471528 and http://bugzilla.gnome.org/show_bug.cgi?id=471559 making it hard to run autoreconf there
[19:36] <mneptok> awalton__: check e-mail please
[19:37] <awalton__> mneptok, thanks for the quick response!
[19:37] <mneptok> everybody visualize happy upstreams ...
[19:41] <mneptok> awalton__: give things 90m to populate
[19:42] <awalton__> no problem. just have to figure out everywhere else I was using that key.. terrible memory :-/
[19:55] <seb128> pochu: upstream fixed the issue I think, would be nice to get the fix rather
[19:55] <pochu> nice
[19:56]  * pochu hopes it doesn't touch autotools :)
[19:59] <pochu> seb128: do you know what commit or a bug# ? looking at http://svn.gnome.org/viewvc/pygobject/trunk/?view=log the last commit mentioning that is 4 months old
[19:59] <seb128> pochu: http://bugzilla.gnome.org/show_bug.cgi?id=481569
[19:59] <pochu> ah, right, thanks
[20:00] <seb128> pochu: looks like they didn't commit the change yet
[20:00] <seb128> so either backport those or still use the change
[20:00] <pochu> I'll try to latest patch
[20:00] <pochu> s/to/the/
[21:32] <lool> pochu: I have --color=auto
[22:19] <soren> python-gtk2-dev seems to be uninstallable on the intrepid buildd's. Is this known? There's no bug about it, but I'd be rather surprised if I was the first to hit it.
[22:20] <soren> ..or is there perhaps something I need to change in my package? (build log: http://launchpadlibrarian.net/14502657/buildlog_ubuntu-intrepid-amd64.virt-manager_0.5.4-1ubuntu1_FAILEDTOBUILD.txt.gz )
[22:32] <geser> soren: I've seen many packages FTBFS because of this, but didn't look deeper into this
[22:49] <soren> geser: Ok, thanks.
[23:24] <mneptok> awalton__: back in the game?
[23:25] <awalton__> I should be, I need to check in a bit
[23:25] <awalton__> my internet's acting really flaky
[23:44] <pochu> soren: I'm looking into that. Guess I should file a bug report
[23:46] <pochu> soren: that's because libffi4 was removed. Rebuilding it against latest pygobject will make the libffi dependency to dissapear. But pygobject FTBFS. I'm working on that
[23:46] <soren> pochu: Ah, great.
[23:46] <pochu> I hope to get it ready for upload by tomorrow...
[23:47] <pochu> It's late here :)
[23:47] <soren> Yeah, same here :)