[12:14] <sivang> LaserJock: I hope this understanding will grow as the science advances
[12:15] <LaserJock> well, I think it will to some degree. However, totally new computational methods (i.e. quantum computing) will need to come about
[12:15] <fowlduck> figured it out, set it using 'gconftool-2 --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type <type> --set </path/to/whatever> <value>'
[12:15] <crimsun> ugh, long day.
[12:15] <crimsun> oh yay, merges.
[12:16] <zul> crimsun, you love it
[12:16] <crimsun> this 50-hr day keeps getting longer
[12:18] <LaserJock> crimsun: lol
[12:19] <LaserJock> dang it, now I've forgotten how to use cut
[12:39] <sivang> LaserJock: interesting, so you say quantum computing for example need to mature in order to help advance nanotech ?
[12:39] <sivang> it's almost ironic :)
[01:06] <LaserJock> sivang: well, I think we can do a lot of nanotech without quantum computing, but nano molecules are *huge* computationally
[01:07] <LaserJock> you can't do much computationally with them
[01:21] <imbrandon_> moins LaserJock
[01:21] <LaserJock> hi imbrandon_
[01:27] <mukund> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3404
[01:27] <mukund> gimp packagers should move to 2.2.12
[02:03] <crimsun> mukund: gimp (2.2.11-1ubuntu3.1) dapper-security; urgency=low  * SECURITY UPDATE: Arbitrary code execution with crafted XCF files.  * app/xcf/xcf-load.c: - Check num_axes for sanity to avoid buffer overflow with invalid values. - CVE-2006-3404 -- Martin Pitt <martin.pitt@ubuntu.com>  Mon, 10 Jul 2006 10:11:09 +0000
[02:09] <LaserJock> weird
[02:10] <LaserJock> so do you think if a package has the wrong overrides in the archive that ubuntu-archive should get the bug?
[02:11] <mukund> crimsun: great
[02:12] <zul> moral of the story always check the changelog
[02:13] <mukund> zul: i'm not an ubuntu user (yet)
[02:34] <LaserJock> interesting, I found 6 packages with wrong Section: and 2 packages in Multiverse that should be in Universe
[02:47] <fowlduck> interesting is trying to find libgconf2-ruby in the repositories
[02:47] <fowlduck> i'm dumbfounded
[03:28] <Hobbsee> hi all
[03:39] <fowlduck> hi Hobbsee
[03:40] <Hobbsee> hey fowlduck ;0
[03:47] <ajmitch> hi Hobbsee, bye Hobbsee
[03:47] <Hobbsee> hey ajmitch!
[03:47] <Hobbsee> ajmitch: you survived melbourne then?
[03:47] <ajmitch> I'm still alive, if that's what you mean?
[03:47] <Hobbsee> ajmitch: partly, yeah
[03:52] <ajmitch> ah, and now bddebian appears
[03:53] <bddebian> Hi ajmitch
[03:53] <bddebian> What'd I do now?
[03:53] <ajmitch> where do I start? :)
[03:54] <Hobbsee> ajmitch: thought you might
[03:54] <ajmitch> must go, will be back in a day or so (I hope)
[03:54] <Hobbsee> ajmitch: the plane will crash and you'll have to swim back.
[03:54] <ajmitch> probably
[03:54] <bddebian> later ajmitch
[03:54] <Hobbsee> heh
[03:55] <Hobbsee> ajmitch: but you still wont be able to tickle my feet, if your'e at the airport!  yay!
[03:58] <Hobbsee> ajmitch: did your home computer crash, btw?
[03:59] <zul> or row
[03:59] <Hobbsee> hmmm...true
[04:05] <LaserJock> bddebian: you got cernlib merged?
[04:08] <LaserJock> BTS and I are going to have a serious discussion
[04:09] <bddebian> LaserJock: Yes, done before I quit
[04:10] <Hobbsee> bddebian: why do you quit?
[04:10] <bddebian> Hobbsee: Becuase I have a 50+ hour work week, a wife, and three kids and all I catch is grief for what I try to contribute
[04:11] <Hobbsee> bddebian: :( ah
[04:12] <LaserJock> bddebian: don't worry, I appreciate your work, and I can understand your situation
[04:21] <bddebian> Thanks
[04:57] <lukaswayne9> Can I poke at a MOTU for some spare time to look at my two packages in the revu?
[05:06] <anibal> bddebian, "all I catch is grief for what I try to contribute" could be turned into a challenge to improve things next time around
[05:18] <bddebian> lukaswayne9: What packages?
[05:18] <lukaswayne9> bddebian: fceu-server and gfceu
[05:18] <lukaswayne9> bddebian: i wrote both of them
[05:24] <LaserJock> bddebian: lol, I think I found a MOTU Science package that wasn't uploaded by you or me ;-)
[05:24] <bddebian> LaserJock: Heh, which one?
[05:24] <LaserJock> geomview
[05:25] <bddebian> Yep, wasn't me :-)
[05:31] <bddebian> Isn't debian/copyright supposed to have the full text of the GPL license?
[05:32] <LaserJock> no
[05:32] <LaserJock> not for GPL
[05:32] <lukaswayne9> bddebian: i used to have it, but i took it out
[05:32] <lukaswayne9> bddebian: someone told me to just refer to /usr/doc/..$whatever
[05:32] <bddebian> OK
[05:33] <LaserJock> bddebian: if the full text is in /usr/share/common-licenses/ you don't have to do full text, just preamble and point to full text
[05:38] <lukaswayne9> What's this bs when I build gfceu? dpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends}   dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}
[05:41] <bddebian> I didn't get that building it now?
[05:41] <lukaswayne9> oh, that's good
[05:43] <LaserJock> lol, "The bddebian is a moron release" ?
[05:44] <bddebian> Heh, yeah, what package was that?
[05:44] <lukaswayne9> bddebian: how's it look?
[05:45] <lukaswayne9> gfceu
[05:45] <bddebian> lukaswayne9: Looks good
[05:45] <LaserJock> bddebian: lyx
[05:45] <lukaswayne9> both of them?
[05:46] <bddebian> lukaswayne9: Yep
[05:46] <lukaswayne9> great!
[05:46] <lukaswayne9> this is my first two real packages
[05:46] <lukaswayne9> these are*
[05:47] <lukaswayne9> bddebian: Hmm, net or games?
[05:47] <bddebian> I think games but I won't swear by it :-)
[05:48] <lukaswayne9> LaserJock: Got a minute?  Could you take a look at my two packages in the revu?
[05:48] <lukaswayne9> bddebian: thanks a lot for your time!
[05:48] <bddebian> NP
[06:08] <LaserJock> lukaswayne9: unfortunately I don't think I have time tonight for a proper review
[06:08] <lukaswayne9> LaserJock: Alright, that's fine.. If you could take a look at them when you have some free time it would be greatly appreciated!  I have been pushing to get these in universe for a week or two
[06:09] <LaserJock> I'll try
[06:09] <LaserJock> :-)
[06:10] <LaserJock> I need to review the new Python Policy
[06:10] <bddebian> Don't we all :-)
[06:10] <lukaswayne9> Does anyone have a link for it?
[06:11] <crimsun> http://www.debian.org/doc/packaging-manuals/python-policy/
[06:11] <LaserJock> I'm not sure if the one on www.debian.org/devel/ is current or not
[06:12] <LaserJock> I honestly don't know what the "offical" word is, I just came across some emails like "we'd like to change the Python Policy to ..."
[06:12] <LaserJock> and I don't keep up with debian enough to know when it's really offical or not
[06:13] <crimsun> I'm surprised the copyright address is outdated
[06:14] <crimsun> usually people are quick to point out and correct that
[06:15] <LaserJock> lol, that's funny
[06:16] <lukaswayne9> Woohoo! My package complies with the python policy
[06:17] <lukaswayne9> but don't take my word for it
[06:18] <crimsun> if it doesn't, I'd be very worried, as the new policy makes things much easier
[06:19] <lukaswayne9> is the new policy ubuntu specific?
[06:19] <crimsun> not at all. It synced into Ubuntu from Debian.
[06:19] <lukaswayne9> Oh, that's good
[06:19] <lukaswayne9> I was looking at the python spec, and I was worried about that
[06:20] <crimsun> hah, awesome, more bugs than I can shake a stick at
[06:20] <bddebian> Yeah, there are a shitload
[06:20] <lukaswayne9> in what?
[06:20] <LaserJock> everything
[06:20] <bddebian> lukaswayne9: crimsun is probably talking alsa stuff.  I am talking about Ubuntu in general :-(
[06:21] <lukaswayne9> oh
[06:21] <lukaswayne9> edgy is really buggy right now, and has REALLY poor performance, but that was kinda expected
[06:22] <LaserJock> do we need to keep dh_iconcache changes?
[06:23] <bddebian> LaserJock: I haven't heard otherwise, but we won't go there ;-)
[06:29] <bddebian> Ah well, gnight folks
[06:29] <lukaswayne9> thanks again bro!
[06:29] <LaserJock> cya bddebian
[06:29] <bddebian> You bet
[06:29] <bddebian> gnight LaserJock
[06:29] <bddebian> gnight crimsun :-)
[06:30] <lukaswayne9> One last shameless plug:  If anyone has a minute to check out my two revu packages, it would be greatly appreciated!
[06:30] <LaserJock> lukaswayne9: you should include the link to the revu pages when plugging ;-)
[06:32] <lukaswayne9> My two packages:   http://revu.tauware.de/details.py?upid=2606   http://revu.tauware.de/details.py?upid=2674
[07:57] <freeflying|away> any core-dev here, need sponsor upload. thx
[08:16] <Lathiat> freeflying|away: of?
[08:16] <freeflying|away> Lathiat: you can upload to main?
[08:16] <Lathiat> not to main
[08:16] <Lathiat> #ubuntu-devel is probably the better place to ask for themn
[08:16] <Lathiat> that
[08:16] <Lathiat> :)
[08:17] <freeflying|away> Lathiat: thx :)
[08:22] <Hobbsee> BOO!
[08:31] <imbrandon_> Hobbsee, HOO!
[08:33] <Hobbsee> imbrandon_: oh dear
[08:33] <Hobbsee> hi ogra
[08:46] <theBishop> can someone help me with NetworkManager?
[09:25] <Kagou> hi
[09:26] <Kagou> hi hub
[09:27] <Kagou> hub: ufraw work like a charm on edgy :) . i'v also added 3 propositions on https://wiki.ubuntu.com/MOTU/Teams/Photo
[09:28] <Lathiat> has anyone else noticed...
[09:28] <Lathiat> that in gnome in dapper lately
[09:28] <Lathiat> if you copy and paste out of gnome terminal
[09:28] <Lathiat> or gaim or some such
[09:28] <Lathiat> the newlines disappear?
[09:28] <Lathiat> for me at least when pasting to irssi
[09:45] <phanatic> morning motus
[09:47] <Toadstool> 'morning everybody
[09:51] <phanatic> hey Toadstool
[09:52] <zakame> heya phanatic Toadstool
[09:52] <phanatic> new packages can get into universe until universe freeze, right?
[09:52] <phanatic> hey zakame
[10:09] <dholbach> good morning everybody
[10:12] <Toadstool> hi dholbach, phanatic & zakame
[10:12] <dholbach> hey Toadstool
[10:18] <\sh> moins
[10:21] <Toadstool> hey \sh
[10:44] <phanatic> another try :)
 new packages can get into universe until universe freeze, right?
[10:45] <Toadstool> yep
[10:46] <phanatic> thanks :)
[10:46] <Toadstool> np ;)
[10:56] <cbx33> hi all
[11:09] <jsgotangco> hi
[11:10] <cbx33> should a lintian report saying source: native-package-with-dash-version be worrying?
[11:10] <cbx33> It's a package I have written for ubuntu
[11:10] <cbx33> i have called the source folder
[11:10] <cbx33> gisomount-1.0.1
[11:10] <cbx33> is that wrong?
[11:11] <netgrabber> cbx33: calling it gisomount_1.0.1 is better
[11:11] <netgrabber> the archive...
[11:11] <jsgotangco> _
[11:12] <cbx33> so switch the - for a _
[11:12] <netgrabber> hmm no
[11:12] <cbx33> oh i see
[11:12] <cbx33> actually calling the package 1.0.1
[11:12] <cbx33> ?
[11:13] <cbx33> or am I completely missing it?
[11:14] <netgrabber> I don't know... maybe its better to ask someone else
[11:14] <cbx33> ok
[11:14] <netgrabber> dholbach: :D
[11:14] <cbx33> indeed
[11:14] <cbx33> now theres a guy who knows his stuff :p
[11:15] <Gloubiboulga> hello
[11:15] <cbx33> I also get this : unknown substitution variable ${misc:Depends}
[11:16] <cbx33> but it seems a lot of packages on the net get that too and seem to ignore it
[11:16] <dholbach> native packages are mostly a sign of something done wrong :)
[11:17] <cbx33> grreeaattt !
[11:17] <dholbach> if you have an upstream tarball, unpack it, move it to   package_version.orig.tar.gz
[11:17] <dholbach> then copy your debian/ dir into the unpacked source
[11:17] <dholbach> then run    debuild -S -sa
[11:17] <cbx33> what's the sa option do?
[11:17] <dholbach> voil! nice source packagae with .diff.gz
[11:17] <cbx33> dholbach: I wrote the package
[11:17] <cbx33> I hold the source
[11:17] <cbx33> I'm creating the first deb of it
[11:17] <dholbach> oh ok, if you don't want to have a real source tarball, or want to ship the debian/ dir with the tarball, then that's fine
[11:18] <cbx33> hmm
[11:18] <cbx33> I would like a real source tarball
[11:18] <dholbach> the problem is just, that if you do a ubuntu revision with a change in debian/rules (for example), you will always have to upload a new tarball
[11:18] <cbx33> and indeed my .orig.tar.gz has no debian folder
[11:18] <jsgotangco> welcome to package management 101
[11:18] <dholbach> if you separate it like that, you get a .orig.tar.gz, a .diff.gz and a.dsc
[11:18] <dholbach> which is nice
[11:19] <dholbach> that's what   -sa   is for
[11:19] <cbx33> dholbach: yes that's what I want
[11:19] <cbx33> ah
[11:19] <cbx33> so I should be building with -sa
[11:19] <cbx33> instead of just -S
[11:19] <dholbach> if you do with -sa the .orig.tar.gz gets uploaded too
[11:19] <cbx33> -S -sa
[11:19] <cbx33> ah I see
[11:19] <dholbach> with -S you only upload the .diff.gz and .dsc
[11:19] <dholbach> (if the .orig.tar.gz is in the archive already)
[11:19] <cbx33> ok I'm going to just run it again now
[11:19] <cbx33> i get it
[11:19] <cbx33> i think
[11:19] <cbx33> what about the unknown substitution variable ${misc:Depends} ?
[11:19] <cbx33> is that anything to worry about?
[11:20] <cbx33> I think I've cleared almost all lintian warnings now! - though that one isn't a linitian warning
[11:21] <cbx33> dholbach: I still got W: gisomount source: native-package-with-dash-version when building the source package???
[11:21] <dholbach> did you rename the tarball to package_version.orig.tar.gz?
[11:22] <Toadstool> dholbach: leading a spontaneous motu-school session? :)
[11:22] <dholbach> package_upstreamversion.orig.tar.gz?
[11:22] <cbx33> it was already named that way
[11:22] <cbx33> ah
[11:22] <dholbach> what is the filename?
[11:22] <dholbach> ah ok
[11:22] <dholbach> Toadstool: not really
[11:22] <cbx33> it'sw named gisomount-1.0.1.tar.gz
[11:22] <cbx33> does it need to be _
[11:22] <dholbach> Toadstool: i'm quite busy with 35 new gnome tarballs
[11:22] <Toadstool> wow
[11:22] <dholbach> gisomount_1.0.1.orig.tar.gz
[11:22] <cbx33> yikes, I'll leave you alone :p
[11:22] <dholbach> don't worry
[11:23] <cbx33> :D
[11:23] <cbx33> ok so that's that error out the way
[11:23] <cbx33> thanks dholbach
[11:23] <dholbach> de rien
[11:23] <cbx33> what about the unknown substitution variable ${misc:Depends}
[11:23] <cbx33> should I worry about that dholbach ?
[11:24] <Gloubiboulga> cbx33, don't worry about that$
[11:24] <cbx33> ok excellent
[11:24] <Gloubiboulga> s/that$/that
[11:24] <Toadstool> hey Gloubiboulga
[11:24] <cbx33> then I declare gisomount officialy deb'd
[11:24] <Gloubiboulga> hi Toadstool
[11:24] <Toadstool> cbx33: cool :)
[11:24] <cbx33> I think LaserJock is goign to upload it to universe sometime soon
[11:25] <Toadstool> dholbach: good luck with gnome stuff
[11:25] <Gloubiboulga> cbx33, is this a NEW package in ubuntu?
[11:25] <cbx33> yes
[11:25] <jsgotangco> his personal pet project
[11:25] <cbx33> :D
[11:25] <cbx33> my first python app/first package :D
[11:26] <slomo> cbx33: where's your package?
[11:26] <cbx33> on my hdd at the moment :p
[11:26] <cbx33> just building it for the last time
[11:26] <cbx33> it's not 100% complete, needs a little tidying
[11:27] <cbx33> but ogra was keen to get it into universe early
[11:27] <slomo> http://wiki.debian.org/DebianPython/NewPolicy  <--- did you keep that in mind for packaging?
[11:27] <cbx33> yes i did
[11:27] <slomo> ok, perfect :)
[11:27] <cbx33> LaserJock is kind of co-writing the package with me....giving me guidence....
[11:27] <cbx33> he hasn;t actually written a line of code yet :D
[11:28] <cbx33> but has provided some great features
[11:28] <cbx33> :D package passes flying colours
[11:49] <cbx33> slomo: does that policy require that someone use setup.py ?
[11:49] <slomo> no
[11:49] <cbx33> good good
[11:50] <slomo> it requires nothing on the upstream side, only for packaging
[11:50] <cbx33> i have followed most of those
[11:50] <cbx33> slomo can i ask a questions
[11:50] <cbx33> in the updating your pacakges section
[11:50] <cbx33> number 3
[11:51] <cbx33> I'm a little confused?
[11:51] <slomo> probably not relevant for your package
[11:51] <cbx33> ok
[11:52] <cbx33> however I do have a seperate module
[11:52] <slomo> could it be used from something else?
[11:52] <cbx33> which i suppose would be classed as private seing as no one else is going to want it
[11:52] <slomo> ok, then don't care about 3.
[11:52] <cbx33> ok cool
[11:52] <cbx33> what about the byte compile
[11:52] <cbx33> I presume I should do that?
[11:52] <cbx33> item 7
[11:53] <cbx33> and my last question is about the Section: field in the control file?  -   what do I put in there?
[11:53] <slomo> yes, use dh_pycentral or dh_pysupport and dh_python
[11:54] <slomo> and section will get whatever section your package should go to :) what does it do?
[11:54] <cbx33> it's a gui mounter for isos
[11:54] <cbx33> its a utility
[11:54] <cbx33> utils?
[11:55] <AnAnt> what is the difference between current uploads & archived uploads ?
[11:55] <AnAnt> one of my recent uploads I found it under archived uploads.
[11:55] <slomo> cbx33: does it need gnome? does it need X?
[11:56] <slomo> first case: gnome, second case: x11, otherwise utils should be fine too
[12:00] <cbx33> whats the diff between pycentral and pysupport ??yes i need gnome and X
[12:01] <Gloubiboulga> AnAnt, which package isit?
[12:01] <slomo> cbx33: so make it section gnome
[12:02] <slomo> cbx33: and i have no idea what the real difference between both is ;) just use whatever you want :)
[12:02] <Gloubiboulga> we archive when the package has been uploaded to the repos
[12:05] <cbx33> slomo: it's knowing where to start
[12:06] <cbx33> i knew I'd have to use one or the other :p
[12:07] <cbx33> slomo: I presume we have to use a lightly modified debhelper version
[12:07] <cbx33> like 5.0.7
[12:07] <cbx33> as 5.0.37.2 isn't in ubuntu
[12:07] <slomo> it is
[12:07] <slomo> and you need it ;)
[12:08] <cbx33> oh
[12:08] <slomo> and i prefer python-central if that helps you :)
[12:08] <cbx33> :S
[12:08] <cbx33> ok cool I'll go with that
[12:08] <cbx33> I did a dpkg -l | grep debhelper
[12:08] <cbx33> and got 5.0.7
[12:08] <slomo> are you on edgy?
[12:08] <cbx33> ah no
[12:08] <cbx33> crap
[12:08] <slomo> ok ;)
[12:08] <cbx33> Grrrr
[12:09] <cbx33> I have a perfect pacakge for dapper :p
[12:10] <Toadstool> it won't be too hard to make it perfect for edgy then ;)
[12:10] <cbx33> nope
[12:13] <cbx33> ok guys, I think i cheated last time
[12:13] <cbx33> what's the proper way to ubild an edgy chroot
[12:13] <cbx33> when my debootstrap package doesn't have an edgy script
[12:13] <cbx33> last time I downloaded the source for the edgy debootstrap pacakge and nicked the script - what's the official way
[12:14] <Toadstool> build a dapper chroot and dist-upgrade it to edgy? :)
[12:14] <phanatic> cbx33: there is a tutorial in the wiki. build a dapper chroot, the upgrade it
[12:14] <phanatic> s/the/then
[12:14] <cbx33> phanatic: that makes perfect sense
[12:14] <Gloubiboulga> hello phanatic :)
[12:14] <phanatic> hey Gloubiboulga :)
[12:15] <slomo> cbx33: or simply copy the dapper script and s/dapper/edgy/
[12:15] <cbx33> will that work?
[12:15] <slomo> yes
[12:16] <cbx33> ok
[12:16] <slomo> unless is not bootstrapable atm ;)
[12:16] <tseng> we should put debootstrap in dapper-updates
[12:16] <tseng> a little lat enow
[12:16] <Toadstool> slomo: uh... i'm not sure s/dapper/edgy/ works...
[12:17] <slomo> Toadstool: it worked for me *shrug* :)
[12:18] <Toadstool> dapper -> gcc-4.0, edgy -> gcc-4.1, isn't it an issue for instance?
[12:18] <tseng> ?
[12:18] <Toadstool> (if you don't upgrade you chroot before using it)
[12:18] <imbrandon_> s/dapper/edgy works thats how i did my chroot
[12:19] <imbrandon_> Toadstool, why would that matter, if your dis-upgrading the chroot
[12:19] <imbrandon_> it will make it 4.1
[12:20] <imbrandon_> s/dis-/dist-
[12:22] <Toadstool> imbrandon_: yeah I dist-upgraded my dapper chroot too, but slomo was speaking about s/dapper/edgy/ in the debootstrap script and I was wondering whether it wouldn't lead to some glitches if you don't upgrade it before using it (which is more or less the same thing as dist-upgrading a dapper chroot :)
[12:23] <Hobbsee> hi again all
[12:23] <Toadstool> hey Hobbsee
[12:23] <imbrandon_> heya Hobbsee
[12:23] <Hobbsee> hey Toadstool :)  imbrandon_
[12:23] <imbrandon_> Toadstool, ahh i thought we was talking chroot not debootstrap, i got arround that by installing edgy debootstrap in dapper ;)
[12:24] <imbrandon_> may not be the "correct" way but it worked
[12:24] <cbx33> imbrandon_: yup
[12:24] <Toadstool> heh
[12:24] <cbx33> that's what I did last time
[12:26] <imbrandon_> btw Hobbsee i watched it and billie/rose doesnt die ;)
[12:26] <imbrandon_> ;)
[12:26] <Hobbsee> imbrandon_: oh good
[12:26] <imbrandon_> shhhhhh i dident say that
[12:27] <cbx33> ok this is strange
[12:27] <cbx33> the dapper script doesn't have the word dapper in it?
[12:27] <imbrandon_> it gets it from the pbuilderrc and/or from the -dapper in the script name ( not the top )
[12:27] <imbrandon_> s/not/note
[12:27] <cbx33> it does it by name :D
[12:28] <cbx33> yes i just realise
[12:28] <imbrandon_> made so you can make pbuilder-sid or pbuilder-breezy etc
[12:28] <imbrandon_> wb
[12:29] <Hobbsee> bleh.  kdesktop or something froze
[12:38] <AnAnt> Gloubiboulga: lftp
[12:38] <AnAnt> Gloubiboulga: sorry I was away
[12:38] <AnAnt> Gloubiboulga: and no, I don't find it in the edgy repos
[12:41] <cbx33> :(
[12:41] <cbx33> errors in installing some packages :(
[12:42] <cbx33> gnupg for one
[12:42] <Hobbsee> cbx33: edgy?
[12:42] <cbx33> which is gonna put a spanner in the works
[12:42] <cbx33> yes
[12:42] <cbx33> :D
[12:42] <cbx33> a second run through and we're all ok
[12:42] <Hobbsee> --> malone
[12:42] <Hobbsee> nothing's supposed to work.
[12:44] <cbx33> hehehe
[12:45] <Hobbsee> :P
[01:13] <cbx33> I'm getting a lintian error
[01:13] <cbx33> is this known about
[01:14] <cbx33> ???
[01:14] <cbx33>  /bin/pwd: couldn't find directory entry in `../../../..' with matching i-node Use of uninitialized value in string at /usr/share/lintian/checks/cruft line 67.Can't stat : No such file or directory
[01:17] <seaLne> has anyone come accros problems with "stack smashing detected" in programs is it default now?
[01:19] <seaLne> ah https://launchpad.net/distros/ubuntu/+spec/gcc-ssp :-/
[01:20] <seaLne> so anyone know what to do if a program in a package fails due to this
[02:01] <highvoltage> crimsun: hi there
[02:20] <\sh> highvoltage: congrats to your new business :)
[02:21] <jsgotangco> yes in a few years we will be sending our resumes to him
[02:33] <highvoltage> \sh: thanks!
[02:33] <highvoltage> jsgotangco: we can only hope ;)
[03:00] <Gloubiboulga> I thought that dist-upgrading would be more painful
[03:01] <Gloubiboulga> everything works, that's not funny :)
[03:47] <bddebian> Heya gang
[03:47] <Gloubiboulga> hi bddebian
[03:48] <bddebian> Heya Gloubiboulga
[04:13] <jsgotangco> goodnight
[04:13] <Hobbsee> night jsgotangco
[05:03] <Hobbsee> hey fowlduck
[05:04] <Hobbsee> hi sharms
[05:04] <tseng> he doesnt have a name
[05:04] <tseng> useful.
[05:04] <Hobbsee> ah
[05:04] <Hobbsee> hi tseng
[05:05] <tseng> [freenode]  -|-  ircname  : mindwarp
[05:05] <sharms> I am just a hopefully, nothing to see here
[05:05] <sharms> err hopeful
[05:05] <tseng> it would be helpful to have a real name in /whois
[05:05] <Hobbsee> sharms: bah.  you're still a person.  i just havent seen your nick around here much before
[05:05] <tseng> so we know who you are :)
[05:05] <sharms> tseng: will do
[05:06] <sharms> at any rate real name = Steven Harms
[05:07] <tseng> thanks.
[05:08] <Yagisan> fowlduck: I've actually *seen* her, outside of IRC. I can confirm that she is a she
[05:08] <Yagisan> and not one of the many impostors on the net
[05:09] <Yagisan> welcome to the Internet, were the men are men, the women are men, and little girls are FBI agents ;)
[05:10] <Hobbsee> fowlduck: hehe, a lot dont.  it's easier that way.
[05:10] <Hobbsee> Yagisan: hehe
[05:10] <Hobbsee> yeah, guess i have been seen now.  hmm.
[05:11] <linuxmonkey> Hobbsee:  ofcourse not your an A.S.I.S
[05:12] <Hobbsee> heh
[05:12] <linuxmonkey> your from australia
[05:12] <linuxmonkey> ?
[05:12] <Hobbsee> yes
[05:12] <linuxmonkey> http://www.asis.gov.au/
[05:13] <Yagisan> linuxmonkey: ASIS == Aussie CIA, You'd be thinking more of AFP instead
[05:13] <linuxmonkey> oh es
[05:13] <linuxmonkey> yes
[05:14] <Yagisan> although if memory serves, it's closer in function to MI6 in Britain
[05:14] <linuxmonkey> lol
[05:14] <sharms> I am from Michigan
[05:14] <sharms> we are getting a new google building supposedly
[05:15] <Yagisan> I had an interview with intelligence services once, they had men with machine guns pointed at me when I walked in the door =-O
[05:17] <Yagisan> I didn't get the job though. Some sort of ethics issue
[05:17] <Hobbsee> eek
[05:17] <Yagisan> should we trust him - he looks like he enjoys it too much
[05:17] <Yagisan> nah, lets give it to the older guy
[05:18] <Yagisan> it was helpdesk too. I mean WTF ? helpdesk.
[05:23] <sharms> that is odd
[05:24] <cbx33> :(
[05:24] <cbx33> my chroot won't connect to the outiside world now I'm home :(
[05:24] <cbx33> DNs resolution failure
[05:24] <cbx33> I've modified the resolv.conf
[05:24] <cbx33> what else could be wrong
[05:25] <cbx33> fixed :D
[05:28] <sharms> what was wrong?
[05:41] <bddebian> LaserJock!!
[05:41] <LaserJock> hi bddebian
[05:41] <bddebian> LaserJock: I just got an e-mail that they merged my .desktop file in polyxmass-bin :-(
[05:42] <LaserJock> bddebian: \o/
[05:42] <cbx33> hey LaserJock
[05:42] <bddebian> LaserJock: No, this is in Debian ;-P
[05:42] <cbx33> :( - package was done
[05:42] <cbx33> then I noticed some things I'd missed in the new debian policy for python docs
[05:42] <cbx33> now I'm stuck
[05:42] <cbx33> :(
[05:43] <LaserJock> haha
[05:43] <LaserJock> sorry, I was to go over that today myself
[05:43] <cbx33> it's ok
[05:43] <cbx33> I wanted to ask you
[05:43] <cbx33> our config module, is strictly for gisomount
[05:44] <cbx33> in that case, it's a private module right
[05:44] <cbx33> and in that case it shouldn't go in site-packages
[05:44] <cbx33> where should it go?
[05:45] <LaserJock> I asked myself that very same question last night, let me pull it up
[05:46] <cbx33> cool
[05:46] <cbx33> and also how familiar are you with py_central
[05:46] <cbx33> :p
[05:46] <LaserJock> I"m not, yet
[05:46] <cbx33> you're gonna have to be :p
[05:47] <LaserJock> looks like /usr/share/gisomount/
[05:47] <cbx33> ok that's cool
[05:47] <cbx33> it's looking more and more like we're going to have to use setup.py
[05:47] <LaserJock> I know, I need to get that package I maintain in debian up to speed
[05:47] <cbx33> because modules need to be byte compiled now for python
[05:48] <cbx33> I have a small problem with my edgy chroot too, but it's a linitian issue I'm not sure why
[05:49] <LaserJock> cbx33: the modules are automatically byte compiled with dh_python
[05:49] <cbx33> but is that assuming they are define in setup.py?
[05:50] <cbx33> how do i tell it :p
[05:50] <LaserJock> cbx33: no
[05:50] <cbx33> ok cool
[05:50] <cbx33> I just read man
[05:50] <cbx33> I'll give it a shot
[05:51] <LaserJock> maybe it's true, but I didn't think so
[05:52] <cbx33> hmmm
[05:52] <cbx33> LaserJock, are you busy?
[05:52] <cbx33> or is that a silly question
[05:52] <cbx33> :p
[05:52] <LaserJock> I've actually just woken up
[05:53] <cbx33> ok nm
[05:53] <LaserJock> so ask away before I'm busy ;-)
[05:53] <cbx33> can I send you a tar of everythin so you can take a quick look?
[05:53] <LaserJock> btw, the debian-python list is full of "Oh my gosh, what do I do now?" emails ;-)
[05:53] <cbx33> hahah
[05:54] <cbx33> good :p
[05:54] <bddebian> I'm sure
[05:54] <LaserJock> I'm guess we can find some stuff there
[05:54] <cbx33> I'm confused and I just had it all sorted
[05:54] <cbx33> I'm tarring my build dir now
[05:55] <LaserJock> I think this new policy will be good for us
[05:55] <LaserJock> but we just need to figure it out
[05:56] <bddebian> Aye
[05:58] <cbx33> yeh
[05:58] <cbx33> http://www.progbox.co.uk/gisomount-build2.tar.gz
[05:58] <cbx33> see what you think LaserJock
[06:01] <LaserJock> hmm, what's the *i386 stuff about?
[06:02] <cbx33> yeh
[06:03] <cbx33> that was when I was using any instead of all
[06:03] <cbx33> for the arch
[06:03] <cbx33> :D
[06:03] <cbx33> ignore it
[06:03] <cbx33> I havn't had a chance to clean up the dr yet
[06:04] <cbx33> if you do a dpkg -c on the deb
[06:04] <cbx33> you can see it's changing the directory that it wants to put it in
[06:04] <cbx33> and it's putting it in pycentral
[06:05] <cbx33> :S
[06:06] <LaserJock> interesting
[06:06] <cbx33> and I need to pull out the configure and stamp bits from rules
[06:06] <cbx33> I made the man page earlier to fix that linitian warning
[06:08] <cbx33> from the dh_pycentral man page "dh_pycentral is a debhelper program that will scan your package, detect public Python modules and move them in /usr/share/pycentral so that python-central can byte-compile those for all supported Python versions. Extensions are kept into the original installation location."
[06:08] <LaserJock> right
[06:08] <cbx33> but the the compiled versions don't show up in the dpkg -c ?
[06:08] <cbx33> should they?
[06:08] <LaserJock> no
[06:08] <cbx33> ok
[06:09] <cbx33> s/and/an
[06:09] <LaserJock> the .py will be compilled postinstall by pycentral on the users machine
[06:09] <cbx33> ok
[06:09] <cbx33> I can remove my prerm
[06:09] <cbx33> since dh_pycentral should take care of that now
[06:10] <LaserJock> postinst I would think as well
[06:10] <FunnyLookinHat> Hey guys....   Anyone care to comment on why MythTV version .19 isn't in the repos?
[06:10] <cbx33> i never had one of those
[06:11] <LaserJock> did you manual build in this dir
[06:11] <cbx33> nope
[06:11] <bddebian> Damnit, I can't get to my machine at home :-(
[06:11] <LaserJock> looks like it's got all the automatically added stuff
[06:11] <cbx33> it has
[06:11] <cbx33> :p
[06:11] <cbx33> I havn't cleaned it all up yet
[06:11] <LaserJock> bddebian: dang, I hate that
[06:12] <cbx33> ok LaserJock
[06:12] <cbx33> i need to put pygtk as a dependency
[06:12] <cbx33> manually?
[06:12] <cbx33> seeing as it didn;t pick that up
[06:12] <cbx33> and glade too
[06:14] <LaserJock> yep
[06:14] <cbx33> python-glade2 and python-gtk2 ---- I don;t need python2.4-glade2 or python2.4-gtk2 ?
[06:14] <cbx33> which do I use ?
[06:14] <LaserJock> python-glade2 and python-gtk2
[06:14] <cbx33> ok
[06:14] <cbx33> swat I thought
[06:15] <cbx33> shouldn't the depends script pick that up in the control file?
[06:16] <cbx33> LaserJock, how do you in a control file tell it to install those pacakges
[06:16] <cbx33> I get
[06:16] <cbx33>  gisomount depends on python-glade2; however:
[06:16] <cbx33>   Package python-glade2 is not installed.
[06:16] <cbx33>  gisomount depends on python-gtk2; however:
[06:16] <cbx33>   Package python-gtk2 is not installed.
[06:17] <LaserJock> what do you have installed?
[06:17] <cbx33> none
[06:17] <Amaranth> how do you not have those installed? kubuntu?
[06:17] <cbx33> it's the first time I installed gisomount in my new chroot
[06:17] <Amaranth> oh
[06:17] <cbx33> :p
[06:17] <cbx33> normally it will say I'm goingto install these as well
[06:17] <cbx33> how do I get it to do that?
[06:18] <LaserJock> apt-get -f install will grab deps
[06:18] <bluefoxicy> argh help I forgot the dpkg-buildpackage command again
[06:18] <cbx33> but it noramlly does that by default for most pacakges
[06:18] <bluefoxicy> -S -something -something -rfakeroot
[06:18] <LaserJock> bluefoxicy: debuild -S works
[06:18] <bluefoxicy> LaserJock:  last I used debuild it broke but I guess I can try again.
[06:18] <LaserJock> depends on what exactly you want to do :-)
[06:19] <bluefoxicy> trying to build a source package for revu
[06:19] <cbx33> do you know what I mean LaserJock
[06:19] <bluefoxicy> yeah
[06:19] <bluefoxicy> LaserJock:  debuild gets a fatal error still.
[06:19] <LaserJock> bluefoxicy: debuild -S -sa
[06:19] <LaserJock> bluefoxicy: wha?
[06:19] <LaserJock> somethings wrong then
[06:19] <bluefoxicy> gpg: problem with the agent - disabling agent use
[06:19] <bluefoxicy> debsign: gpg error occurred!  Aborting....
[06:20] <bluefoxicy> (oddly enough running dpkg-buildpackage brings up the agent)
[06:20] <LaserJock> oh, well that's your issue, not debuilds
[06:20] <bluefoxicy> well
[06:20] <LaserJock> odd
[06:20] <bluefoxicy> if I don't run or install seahorse it does the same thing.
[06:20] <LaserJock> can you debsign?
[06:20] <bluefoxicy> I actually installed seahorse to try and get it to listen
[06:20] <bluefoxicy> yeah debsign works
[06:20] <hub> Gloubiboulga: regarding http://revu.tauware.de/details.py?upid=2419, it is already for edgy
[06:20] <hub> Gloubiboulga: what is the problem?
[06:21] <LaserJock> odd, since debuild is a wrapper for dpkg-buildpackage+lintian+debsign
[06:21] <bluefoxicy> I know.
[06:21] <Hobbsee> hub: does it say edgy or dapper in the changelog?
[06:21] <bluefoxicy> it's very odd because debsign fails
[06:21] <LaserJock> bluefoxicy: well, whatever. you need -S -sa -rfakeroot
[06:21] <bluefoxicy> but if I run debsign on its own it works.
[06:21] <hub> Hobbsee: it does say edgy
[06:22] <LaserJock> bluefoxicy: I guess dbuild must be passing something bad to debsign
[06:22] <Hobbsee> hub: ah okay - i just took a guess, didnt dpkg-source it
[06:22] <Gloubiboulga> hub, I was talking about standars/debhelper compat actually
[06:22] <cbx33> LaserJock, so is there no way to make it automatically install the python pacakges unless
[06:22] <cbx33> unles we use -f?
[06:22] <Gloubiboulga> hub, but it wasn't obvious at all, I admit ;)
[06:22] <LaserJock> cbx33: what?
[06:22] <LaserJock> cbx33: it's looking good
[06:23] <cbx33> it's funny if you install compiz-gnome it automatically installs compiz
[06:23] <cbx33> can we do that for gisomount and the python deps
[06:23] <cbx33> so it doesn't fail
[06:23] <cbx33> but says I'm gonna install these for you?
[06:23] <LaserJock> cbx33: in Depends: in debian/control
[06:23] <hub> Gloubiboulga: what is the standard version exepcted?
[06:23] <cbx33> LaserJock, they are listed in my version
[06:24] <LaserJock> cbx33: then they will be installed :-)
[06:24] <LaserJock> hub: 2.7.2 I believe
[06:24] <cbx33> Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, python-glade2, python-gtk2
[06:24] <cbx33> is the line
[06:24] <LaserJock> great
[06:24] <hub> LaserJock: which is lower than 3.6.1
[06:24] <cbx33> but I get dpkg: dependency problems prevent configuration of gisomount:
[06:24] <cbx33>  gisomount depends on python-glade2; however:
[06:24] <cbx33>   Package python-glade2 is not installed.
[06:24] <cbx33>  gisomount depends on python-gtk2; however:
[06:24] <cbx33>   Package python-gtk2 is not installed.
[06:24] <cbx33> dpkg: error processing gisomount (--install):
[06:24] <hub> LaserJock: which is lower than 3.6.2
[06:24] <cbx33> sorry for the flood guys
[06:24] <LaserJock> hub: doh, sorry 3.7.2
[06:24] <hub> where is the list?
[06:25] <LaserJock> cbx33: right, that happens because you are using dpkg ;-)
[06:25] <LaserJock> hub: list of what?
[06:25] <cbx33> ah
[06:25] <cbx33> ok np
[06:25] <cbx33> thanks of course
[06:25] <cbx33> I'm so stupid
[06:25] <hub> LaserJock: standards version and compat
[06:25] <LaserJock> hub: look at the Debian changelog for debian-policy and debhelper respectively
[06:26] <hub> how would one guess?
[06:26] <Hobbsee> current compat is what?  5?
[06:26] <cbx33> LaserJock, I think we're getting there
[06:26] <cbx33> will python look in pycentral for modules by default?
[06:26] <Hobbsee> it's not 3, i know that much
[06:26] <Hobbsee> it's either 4 or 5
[06:26] <LaserJock> yeah, compat is 5 and standards version is 3.7.2
[06:26] <Gloubiboulga> 'apt-cache policy debian-policy' gives the Standards-Version
[06:27] <LaserJock> Gloubiboulga: only for your current system ;-)
[06:27] <Hobbsee> right
[06:27] <Gloubiboulga> LaserJock, right, but I'm on edgy ^^
[06:27] <hub> Gloubiboulga: given that I still build on dapper
[06:27] <Hobbsee> you can still get at all that thru pbuilder login
[06:28] <LaserJock> or look at the Debian changelog, it's not that hard folks ;-)
[06:28] <LaserJock> http://packages.qa.debian.org/d/debian-policy.html
[06:28] <hub> that does not talk about Edgy
[06:28] <hub> *sigh*
[06:28] <LaserJock> Edgy has nothing to do with it
[06:29] <LaserJock> Edgy uses the Debian unstable version
[06:29] <hub> given the request, it has
[06:29] <hub> "update for edgy" was the request
[06:29] <LaserJock> right
[06:29] <LaserJock> and edgy comes from Debian unstable
[06:29] <LaserJock> we don't change Debian's policy
[06:29] <hub> debian stable change every day
[06:30] <cbx33> LaserJock, it seems to sork
[06:30] <cbx33> s/sork/work
[06:30] <cbx33> :D
[06:30] <LaserJock> the point is, look towards Debian when you need Standards Version and compat
[06:30] <LaserJock> because they determine the policy for those
[06:31] <LaserJock> and we shouldn't be deviating from that
[06:31] <cbx33> LaserJock, will gisomount goto REVU ?
[06:31] <LaserJock> cbx33: if you upload it ;-)
[06:31] <cbx33> should it !
[06:31] <cbx33> s/!/?
[06:32] <Yagisan> cbx33: load it up
[06:32] <cbx33> nooooo...I'm scared
[06:32] <cbx33> got some cleaning up to do yet
[06:32] <LaserJock> cbx33: go for it, we can thrash it and then you can upload again
[06:32] <cbx33> as LaserJock can see
[06:32] <Yagisan> cbx33: who knows, maybe someone will actually look at it :-P
[06:32] <LaserJock> clean it up as well as you can, then upload it
[06:32] <cbx33> ok
[06:32] <cbx33> :S
[06:32] <Gloubiboulga> hub, I thought you was aware of the versions we use, that's why I've not commented much, sorry
[06:33] <Yagisan> cbx33: (I think they squeeze revu in, like 30 minutes before edgy closes)
[06:33] <cbx33> :p
[06:33] <LaserJock> Yagisan: bah, not always. don't be scarring contributors off like that ;-)
[06:33] <Yagisan> LaserJock: I'm one of the contributors!!
[06:33] <hub> Gloubiboulga: uploaded a new version
[06:33] <cbx33> not worth it :p
[06:34] <Yagisan> cbx33: don't be such as wuss, how can it be worse then mine ?
[06:34] <cbx33> LaserJock, all the conifugre and build stuff can go can't it?
[06:34] <cbx33> in the ruls file?
[06:34] <LaserJock> don't get rid of the rules themselves
[06:34] <LaserJock> just leave them empty
[06:34] <cbx33> just make them blank
[06:34] <cbx33> yeh sure
[06:35] <cbx33> but like build-stamp
[06:35] <cbx33> is that needed?
[06:35] <LaserJock> it helps make sure you don't try to build twice
[06:35] <azeem> only if you do real work in it
[06:35] <LaserJock> right
[06:35] <cbx33> ok
[06:37] <LaserJock> cbx33: wrt, " will python look in pycentral for modules by default?"
[06:37] <siretart> any kubuntu guy interested in having an updated xine? :P
[06:37] <siretart> s/guy/dev/
[06:37] <LaserJock> hehe, is that a hint siretart
[06:38] <LaserJock> cbx33: I believe pycentral will compile the module and install it in the right places
[06:38] <siretart> slomo: no. serious. I don't know if I will have time tomorrow to merge xine
[06:39] <siretart> and thu is the deadline :(
[06:39] <cbx33> LaserJock, yes it does
[06:39] <cbx33> :D
[06:39] <cbx33> do they have to have pycentral on their machine though?
[06:39] <siretart> if somebody else wants to merge it, I have a bzr branch with 1.1.2 xine for debian ready
[06:40] <LaserJock> cbx33: right
[06:41] <slomo> siretart: i don't have any time for it neither :( i'll write an exam tomorrow. did you already ask in #kubuntu-dev?
[06:42] <LaserJock> bbl
[06:42] <cbx33> ok
[06:42] <siretart> slomo: not yet, but need to run now
[06:42] <slomo> siretart: ok, i'll ask there
[06:42] <siretart> thanks
[06:43] <siretart> I'll see if I can come online later again, but no promises
[06:43] <cbx33> slomo, I think I'm getting there :p
[06:43] <cbx33> I think I conform to the New Policy now :D
[06:43] <cbx33> if we use pycentral, does that mean they have to have that instlaled on their machine to install tha package?
[06:44] <siretart> slomo: I have updated my branches on tauware, just in case you find someone ;)
[06:44] <slomo> cbx33: yes and you have it already installed on edgy anyway... together with python-support ;)
[06:45] <cbx33> ok excellent
[06:45] <cbx33> then it's all coming together nicely
[06:45] <cbx33> could have a pckage ready by the end of the day
[06:46] <cbx33> if I'm using gisomount.dirs and gisomount.install
[06:46] <cbx33> can i delete the dirs and files and docs files that the automatica process generated
[06:46] <cbx33> ?
[06:47] <cbx33> actually
[06:47] <cbx33> I think i need all but dirs
[06:48] <bluefoxicy> ........
[06:48] <bluefoxicy> synaptic says there is a new package "python-pyorbit-omg"
[06:48] <cbx33> it's ok I'm just going crazy
[06:48] <cbx33> heh
[06:48] <bluefoxicy> "OMG standard files"
[06:49] <slomo> bluefoxicy: so what? :)
[06:49] <bluefoxicy> slomo:  omg, I dunno wtf?
[06:49] <tseng> hah shut up bluefoxicy
[06:50] <slomo> bluefoxicy: www.omg.org :P
[06:50] <bluefoxicy> tseng omg hi :)
[06:51] <sharms> oh for a second I thought I was in #ubuntu by the "omg"'s
[07:05] <zul> http://www.sungate.co.uk/?p=256
[07:08] <sharms> nice article but the page design is bad
[07:35] <cbx33> hi all
[07:35] <cbx33> what does the dirs file do in the debian foldeR?
[07:37] <bddebian> Makes the dirs for your package
[07:38] <cbx33> if I have a package.dirs file
[07:38] <cbx33> do i need it?
[07:38] <bddebian> ?
[07:38] <cbx33> in my debian folder i have
[07:38] <cbx33> gisomount.dirs
[07:38] <cbx33> and gisomount.install
[07:39] <bddebian> One of the debhelper scripts (dh_install I think) uses them to create the dirs and files that go into the package
[07:39] <bddebian> I assume you also have a gisomount.files ?
[07:39] <cbx33> nope
[07:39] <bddebian> Oh, maybe it's just dh_installdirs that uses it?
[07:39] <bddebian> I don't have my machine handy to check :-(
[07:39] <Gloubiboulga> dh_installdirs create the dirs
[07:40] <Gloubiboulga> listed in package.dirs
[07:40] <cbx33> ok
[07:40] <bddebian> Gloubiboulga: thanks
[07:40] <cbx33> so i can remove the dirs folder
[07:40] <cbx33> file
[07:40] <bddebian> If you are creating the dirs and not using dh_installdirs, sure
[07:41] <cbx33> I'm using dh_installdirs, which uses the package.dirs file, so the single file called dirs can go
[07:41] <cbx33> ?
[07:42] <bddebian> Oooh, sorry I misunderstood you.  Yes, I think so
[07:42] <cbx33> hehe ok thanks
[08:31] <LaserJock> raphink: ping?
[08:32] <LaserJock> raphink: unping, sorry ;-)
[08:58] <LaserJock> and revu admins awake?
[08:58] <zul> mmmmm....xen....xen-headers-2.6.16-1_2.6.16-1_i386.deb
[09:00] <linuxmonkey> LaserJock: no I shot em all
[09:00] <LaserJock> doh
[09:01] <linuxmonkey> i shot em in the foot so they should be back soon
[09:02] <zul> amd then bddebian ate their babies
[09:03] <FunnyLookinHat> Anyone here in charge of MythTV ?
[09:04] <LaserJock> zul: ewww
[09:04] <zul> yeah...i thought so too
[09:08] <Yagisan> so, zul, you actually get bddebian on film eating those babies ?
[09:09] <LaserJock> I'm sure it's on a blog somewhere
[09:11] <Yagisan> only a blog ? but how am I supposed to kick back and watch while eating popcorn with two hands :(
[09:11] <zul> Yagisan: no but i bet its on youtube somewhere
[09:14] <LaserJock> lol, I did a google search for "bddebian eats babies"
[09:14] <LaserJock> and got "Did you mean: debian eats babies"
[09:14] <Yagisan> heh
[09:15] <cbx33> like that would give any better results
[10:07] <crimsun_> bockman: I've pinged the ftp admin several times, but he hasn't responded yet (probably due to being incredibly busy)
[10:09] <bockman> bureaucracy :\
[10:09] <lloydinho> crimsun: He is in the Community Council meeting right now.
[10:09] <lloydinho> It's not really that bureaucratic..
[10:10] <bockman> well this is taking as long as one, you'd think it would be
[10:11] <crimsun_> bockman: no, elmo's just incredibly busy. I've done all I can do, but I'll ask someone else to retry the upload with their own sig.
[10:12] <LaserJock> crimsun_: what's up?
[10:12] <tseng> afaik elmo doesnt do archive maintainance in ubuntu
[10:12] <tseng> keybuk and infinity do
[10:12] <bockman> well i know you've done your part in speedily taking care of this, crimsun_
[10:12] <bockman> i'm just kind of frustrated.
[10:12] <crimsun_> tseng: I think he still does for -security (at least I was directed to him by pitti)
[10:12] <bddebian> Ack WTF did I miss? :-)
[10:12] <tseng> bddebian: crying.
[10:13] <tseng> crimsun_: maybe old -security is still on the old infrastructure
[10:13] <tseng> for breezy and such
[10:13] <crimsun_> tseng: no idea, but this is a breezy-security upload, true
[10:14] <tseng> and only elmo can speak to that
[10:14] <tseng> or so we are led to believe
[10:14] <bddebian> tseng: Who is crying?
[10:15] <LaserJock> hehe
[10:15] <tseng> bddebian: you.
[10:15] <LaserJock> I'm tempted to say something related to zul's earlier comment, but I won;t
[10:16] <tseng> .
[10:16] <tseng> oops.
[10:16] <crimsun_> LaserJock: security fixes. Got a second to recreate a source package for me, sign it, and upload to security.upload.ubuntu.com?
[10:17] <crimsun_> fwiw bddebian also signed and uploaded it, and it mysteriously was blackholed for his u. Go figurepload
[10:18] <crimsun> wow, talk about crack termcap
[10:18] <LaserJock> crimsun_: I suppose I could, but I'd rather somebody more experienced *cough*tseng*cough* did it. ;-)
[10:18] <tseng> I could, but not here
[10:18] <tseng> I dont leave gpg keys lying around at work
[10:20] <cbx33> tseng, good plan
[10:20] <LaserJock> tseng: no?
[10:21] <tseng> LaserJock: not now, no
[10:21] <tseng> in a few hours maybe
[10:25] <LaserJock> hmm
[10:25] <LaserJock> I wonder where he went
[10:25] <tseng> "back to work."
[10:30] <bddebian> crimsun: ?
[10:31] <bddebian> Well another machine dead from trying to dist-upgrade to Edgy :'-(
[10:38] <bddebian> Anyone have an Edgy machine or Edgy chroot or pbuilder login handy?
[10:38] <rob> yes
[10:38] <bddebian> Would you mind doing an apt-cache madison on gcl and seeing if the -17 version is in the archive yet?
[10:38] <LaserJock> bddebian: not one that I want to give you as guinea pig for your sick plan to take over the world ;-)
[10:39] <Yagisan> rob: ?? you actually are here ?
[10:39] <bddebian> LaserJock: mwuhahaha
[10:40] <rob> sure :)
[10:41] <crimsun> bddebian: https://launchpad.net/distros/ubuntu/+source/gcl/2.6.7-17ubuntu1
[10:42] <LaserJock> ppc :(
[10:42] <bddebian> crimsun: I know it built successfully but it wasn't in the archive last night
[10:42] <rob>  (edgychroot)root@graybox:~# apt-cache madison gcl
[10:42] <rob>        gcl |   2.6.7-17 | http://archive.ubuntu.com edgy/universe Packages
[10:42] <rob>        gcl |   2.6.7-17 | http://archive.ubuntu.com edgy/universe Sources
[10:42] <bddebian> And all my machines are now dead or inaccessable at the moment :-(
[10:42] <bddebian> Thanks rob
[10:43] <crimsun> it's not a successful build.
[10:43] <rob> np
[10:43] <bddebian> Well on MY arch it is ;-P
[10:47] <bddebian> GBC is not enabled?  WTF is that? :)
[11:30] <Sp4rKy> bddebian, ping ?
[11:58] <LaserJock> bddebian: oh what ever
[11:59] <bddebian> Heh