[00:42] <slangasek> pitti: would there be a problem with me uploading gtk+2.0 tonight?  you and I both have staged changes in bzr now, and I'd like to get mine to the archive :)
[01:26] <psusi> TheMuso, ping
[08:51]  * c2tarun don't miss me too much ;) ♥
[08:51]  * c2tarun is back.
[08:51] <ion> eh
[14:01] <hyperair> so the launchpad bug acronym is LP:, and bugzilla.gnome.org is BGO, so is code.google.com CGC?
[14:14] <tumbleweed> hyperair: aren't google code bug numbers project-specific?
[14:14] <hyperair> oh whoops
[14:14] <hyperair> you're right.
[15:28] <petn-randall> Hello, I'm looking for what's needed to get ureadahead working with the vanilla kernel. To my knowledge it needs a kernel patch, but I can't find it on the launchpad page of ureadahead or the usual documentation. Can someone give me any pointers?
[15:29] <hyperair> petn-randall: if you download the source tarball, it's there.
[15:30] <hyperair> petn-randall: if you clone the zen-kernel git tree it's there in the ureadahead branch
[15:31] <petn-randall> hyperair: The source tarball of ureadahead? Yeah, I've seen the patch, but it has too much fuzz on recent kernels. I'll try the zen-kernel git tree, thanks.
[15:31] <hyperair> petn-randall: if you like, i can export the patch so you don't need to clone the entire tree
[15:31] <hyperair> zen-kernel's git is pretty slow
[15:32] <petn-randall> hyperair: that would be great, thanks
[15:32] <hyperair> http://paste.debian.net/109639/
[15:32] <hyperair> petn-randall: ^ that's it
[15:37] <petn-randall> hyperair: Hmm ... it has too much fuzz against linus' tree. I'll have to patch it in by hand if nobody has done that yet.
[15:38] <hyperair> petn-randall: really? i thought it worked.
[15:38] <hyperair> lemme check
[15:38] <hyperair> my kernel's 2.6.37 and has the patch applied
[15:39] <hyperair> petn-randall: oh sorry i think i generated the wrong patch
[15:40] <hyperair> petn-randall: http://paste.debian.net/109642/
[15:42] <petn-randall> hyperair: awesome. It works against the dev tree of 2.6.38+. Thanks!
[15:42] <hyperair> =)
[16:39] <Haegin> hi, would the retarded behaviour of rubygems installing to /var/lib/gems (which requires root) and then making the installed apps which are symlinked in /usr/bin only readable by the owner (which is, of course, root) be considered a bug?
[16:43] <Chipzz> Haegin: I would call the retarded behaviour of the ruby community as a whole a bug :P
[16:44] <Chipzz> Haegin: but I guess it depends wether you're talking about the packaged version of rubygems or not
[16:44] <Ampelbein> Haegin: there is debian bug 585838 but it has no further activity
[16:45] <Haegin> Chipzz: true, and yes, it's just the default rubygems with ubuntu that I'm using
[17:29] <stefwal1> QUESTION:I'm using ubuntu maverick meerkat and python 2.6  I am totally new to debugging and wanted to test something out.  in my directory  /usr/lib/python2.6/dist-packages/desktopcouch/records I had a link to a server.py file. Problem is I deleted de link. Can anyone give me the location to where the link was pointing??
[17:33] <beuno> stefwal1, I dont' have that dir, but desktop couch lives here for me: /usr/share/pyshared/desktopcouch/
[17:33] <beuno> and here, apparently: /usr/lib/pymodules/python2.6/desktopcouch/
[17:34] <beuno> which just points to /usr/share/pyshared/desktopcouch/
[17:34] <stefwal1> beuno: I think you saved my day.
[17:35] <beuno> good, I like easy wins  :)
[17:53] <stefwal1> QUESTION: book A byte of python from swaroop ch. In this book, there's written that import sys looks for a file called sys.py, how comes I don't find that file anywhere?
[17:58] <Chipzz> stefwal1: this is not the channel for such question (cfr topic)
[17:59] <Chipzz> stefwal1: and the answer to your question is likely that since sys is a wrapper around libc functions, the module is a .so instead of normal python code
[18:00] <stefwal1> Chipzz: thanks for the answer and sorry for the inconvenience.
[18:16] <aroman> hey, I'm trying to run `debuild -S -sa`, and it fails after a little bit saying that my secret key is not available. Why is this?
[18:17] <arand> aroman: Do you have your key in ~/.gnupg/ ?
[18:18] <aroman> arand: I think so, what file would I be looking for there?
[18:18] <Ampelbein> aroman: and the emailadress in the changelog must match one of the IDs of your key
[18:19] <Ampelbein> aroman: 'gpg --list-secret-keys'
[18:20] <aroman> wow
[18:20] <aroman> guess what, my name is actually "Avi Romanoff (Final PGP key)"
[18:20] <aroman> and it won't work unless I use exactly that string as my name :O
[18:21] <aroman> is there any way to change that to remove the stuff in the parenthesis without breaking things?
[18:21] <Ampelbein> aroman: you can use '-k KEYID' as argument
[18:21] <aroman> Ampelbein: what would that do?
[18:22] <aroman> the original command does work now, i just have to type in that silly name
[18:22] <Ampelbein> aroman: it gives debsign (called by debuild) the info on what key to use instead of comparing name/adress string
[18:22] <aroman> ahh
[18:22] <aroman> so then I could leave my name in `changelog` as I want?
[18:22] <Ampelbein> aroman: yeah
[18:23] <Ampelbein> aroman: you could also add a new user id to your key via seahorse (graphical) or gpg --edit-key KEYID
[18:24] <aroman> Ampelbein: right, and would that break anything that I've already signed with the old name with?
[18:24] <Ampelbein> aroman: no
[18:24] <aroman> alright then I think i'll do that
[18:26] <aroman> Ampelbein: alright, I added the new user id to seahorse, and it worked great. thanks a bunch! :)
[18:58] <aroman> the new elementary-wallpapers just finished building :D
[20:17] <dom0do> I read most of the Developers Week logs, and I just noticed a typo in a package description. How can I report this to Debian?
[20:18] <Ampelbein> dom0do: if there is a patch already in ubuntu, use 'submittodebian' from ubuntu-dev-tools
[20:18] <Ampelbein> dom0do: if there is no patch, you can use reportbug.
[20:19] <dom0do> Ampelbein: so I shouldn't report upstream first? okie
[20:20] <Ampelbein> dom0do: well, that depends. if there is no ubuntu changes yet, it isn't worth it to introduce a change just for a typo.