=== gnomefre1k is now known as gnomefreak [06:43] good morning [08:58] morning everyone [13:08] hey [16:03] lool: thanks for the Vinagre upload :) [16:03] seb128: could you please sync vinagre 2.23.2-1 from incoming.d.o? [16:04] 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] pochu: you package 2.23 for debian already? [16:05] seb128: yup :) [16:05] seb128: but that's for experimental [16:06] good luck handling the bug load going with early unstable versions ;-) [16:06] .2 fixes a bug for which there's a request to get it into Hardy (and has a debdiff attached) [16:07] the one somebody asked you about it because it introduces a couple of strings [16:07] heh, thanks, but it's in experimental so hopefully not many people uses it :) [16:10] the ctrl-alt-del menu item bug? [16:11] seb128: yup [16:12] pochu: did you work on an hardy update for this one? [16:12] bug 199116 [16:12] Launchpad bug 199116 in vinagre "Can not send 'Ctrl+Alt+Del'" [Low,Fix committed] https://launchpad.net/bugs/199116 [16:12] seb128: no, but someone else did and attached a debdiff to the report [16:13] seb128: BTW, 2.23.2 needs gtk-vnc 0.3.6 which needs to go though binary NEW [16:13] ok, good [16:13] ok [16:13] I'm still focusing on hardy but I'll start looking at the GNOME merges and updates after uds I think [16:13] slangasek asked in the bug report to fix it in Intrepid first, so with this sync we should be done [16:16] 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] I think I got the bug fixed, but couldn't check it [16:17] 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] I even tried building Vinagre 0.5 and other things and they all failed [16:18] seb128: I've got a question: https://bugs.edge.launchpad.net/ubuntu/+source/gdm/+bug/229866/comments/4 [16:18] 'dpkg -L libgtk' completes to 'dpkg -L libgtk^[\[m^[\[K^[\[m^[\[K' [16:18] Launchpad bug 229866 in gdm "2.20.6 stable update" [Wishlist,Confirmed] [16:19] 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] seb128: (added a further comment) [16:20] pitti: looking [16:23] pitti: the commit log on http://svn.gnome.org/viewvc/gdm?view=revision&revision=6167 has some details [16:24] pitti: http://bugzilla.gnome.org/show_bug.cgi?id=509141 comment #15 too [16:24] Gnome bug 509141 in general "GDM does not honor LC_DATE" [Normal,Unconfirmed] [16:24] seb128: right, I saw that; I mean the G_BROKEN_FILENAMES removal [16:25] ah, that was the same commit [16:26] seb128: right, so they suggest that we set this in our distro specific Xsession.common? [16:26] pitti: G_BROKEN_FILENAMES is something to set when you don't use an utf-8 locale [16:26] seb128: which is not our default, but many people still have that (unfortunately) [16:26] well, I've rebooted with the new version [16:26] but this one should not be set on systems using an UTF-8 locale [16:27] I'm wondering if that was really set [16:27] do you have it defined? [16:27] seb128: would that be in /etc/gdm/Xsession ? [16:27] seb128: The new vinagre versions don't seem that disruptive [16:28] pochu: Could you comment on that ::1/localhost bug? I tried reproducing it, but I couldn't with the latest vinagre [16:28] seb128: ok, grep -r G_BROKEN_FILE /etc doesn't deliver anything [16:28] (I could connect to localhost and to ::1 just fine) [16:28] pitti: we install debian/Xsession [16:28] seb128: when you install the new .deb, do you actually get a 'installing new conffile' note? [16:28] seb128: aah [16:29] pitti: so the change doesn't make a difference for us [16:29] seb128: alright then, thank you! [16:30] pitti: thank *you* for being careful when checking uploads ;-) [16:33] 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] lool: wait, let me check it [16:38] lool: reproduced here [16:38] lool: in Hardy, BTW [16:38] (vinagre 0.5.1) [16:44] lool: but that should be a vino bug [17:00] pochu do you have an example of a simple python package not using the default setup.py on install? === ember_ is now known as ember [17:02] ember: decibel-audio-player uses a simple Makefile, and scribes uses autotools. Are any of them ok? [17:05] well this one just uses "python install.py" for installing [17:14] ember: is install.py a distutils script? [17:15] if so, you can point to it in debian/rules (if using CDBS) with 'DEB_PYTHON_SETUP_CMD := install.py' [17:15] (https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml) [17:16] no, is just a .py to check modules and with os.system("cp") to install py [17:17] heh [17:17] you can call it in the install rule [17:20] hmm i'm gonna try packaging this one === gnomefre1k is now known as gnomefreak [17:44] what a wonderful day. [17:44] hey mneptok [17:44] heya seb [17:45] 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] 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] niiice [17:46] thanks mneptok :-) [17:46] no promises, as i haven't talked to Zaid about watching GNOME. [17:47] mneptok: could you give an hint of what keys should not be trusted for those who are not security wizards there? ;-) [17:47] but then i can guess the sabdfl's wishes, i think. [17:47] if you are 100% absolutely certain you generated your SSH key on a Dapper or prior Ubuntu installation, do nothing. [17:48] otherwise, you'll want to replace all your SSH keys, wherever they live. [17:49] the updates today will check host-wide keys and re-generate them. expect hostkey change warnings from ~/.ssh/known_hosts [17:50] but the packages do nothing vis-a-vis personal keys. please re-generate and get those to GNOME first. ;) [18:05] 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: Error: Could not parse data returned by Debian: timed out [18:05] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414798 [18:05] * pochu tries to build pygobject now [18:05] pochu: Error: Could not parse data returned by Debian: timed out [19:15] bah, I'm too stupid to be able to run autoreconf on pygobject [19:16] or pygobject is too b0rked [19:18] * jdavies hugs poor pochu [19:18] :-) [19:19] seb128: I guess we still want 61_dont_use_setwakeupfd.patch in pygobject? that's our last diff [19:20] 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:20] Gnome bug 471528 in general "m4 macros needed to rebuild configure aren't shipped with 2.13.x" [Minor,Unconfirmed] [19:36] awalton__: check e-mail please [19:37] mneptok, thanks for the quick response! [19:37] everybody visualize happy upstreams ... [19:41] awalton__: give things 90m to populate [19:42] no problem. just have to figure out everywhere else I was using that key.. terrible memory :-/ [19:55] pochu: upstream fixed the issue I think, would be nice to get the fix rather [19:55] nice [19:56] * pochu hopes it doesn't touch autotools :) [19:59] 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] pochu: http://bugzilla.gnome.org/show_bug.cgi?id=481569 [19:59] Gnome bug 481569 in gtk "Calling gobject.threads_init() causes a lot of wakeups" [Normal,Reopened] [19:59] ah, right, thanks [20:00] pochu: looks like they didn't commit the change yet [20:00] so either backport those or still use the change [20:00] I'll try to latest patch [20:00] s/to/the/ === crd1b is now known as crdlb [21:32] pochu: I have --color=auto [22:19] 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] ..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] soren: I've seen many packages FTBFS because of this, but didn't look deeper into this [22:49] geser: Ok, thanks. [23:24] awalton__: back in the game? [23:25] I should be, I need to check in a bit [23:25] my internet's acting really flaky [23:44] soren: I'm looking into that. Guess I should file a bug report [23:46] 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] pochu: Ah, great. [23:46] I hope to get it ready for upload by tomorrow... [23:47] It's late here :) [23:47] Yeah, same here :)