[12:18] <ScottK> xtknight: So I confirmed the bug.  Please mark it fix released if you find out it's resolved.
[12:18] <xtknight> k
[12:19] <ScottK> xtknight: You can mark your bip bug fix released whever you feel like it.  It's built.  Congrats again.
[12:20] <xtknight> ScottK, cool. it will be included in Feisty release?
[12:21] <xtknight> also i submitted it to debian
[12:21] <ScottK> Yes.  It is in Feisty now.
[12:21] <xtknight> but i didnt see you had modified it a bit.  it didnt work with it because it 'hadnt been synced' ?
[12:21] <xtknight> i sent my original fix to debian
[12:21] <xtknight> so i dunno
[12:22] <ScottK> xtknight: there was some trouble getting your patch to apply (which had to do with the naming, not the content) and I played with it a bit.  Technically your patch was fine.
[12:22] <xtknight> ahh because the path was too long
[12:22] <ScottK> Debian won't apply the patch directly, so they'll be OK>
[12:23] <xtknight> yeah
[12:23] <ScottK> Something like that.  I still have trouble with patch naming sometimes.
[12:23] <xtknight> i figured they didnt want MOTU in their pkg status
[12:23] <xtknight> but i just gave them it all anyway
[12:23] <ScottK> No, they don't
[12:23] <xtknight> wow didnt realize it would be that quick
[12:24] <ScottK> Pretty cool, huh?  You may want to go ahead and join https://launchpad.net/~ubuntu-universe-contributors/ so that if you want to package something new, you'll be able to upload entire packages for review in Feisty+1.
[12:24] <xtknight> interesting
[12:25] <xtknight> i got an email back from Arnaud already
[12:25] <xtknight> "This should be ENABLED=1 for the user's convenience, since this is undocumented behavior."
[12:25] <xtknight> >>"This is the point, because an unconfigured bip should not be started.
[12:25] <xtknight> Documenting would do no harm though."
[12:25] <xtknight> hmm
[12:26] <xtknight> ( this is from the one i submitted to debian, i think )
[12:26] <xtknight> well doesnt matter to me what Debian does to it
[12:26] <xtknight> :P
[12:27] <ScottK> Either fixing the docs or fixing the code is a valid solution.  Seems unlikely someone would install something they don't want to run though.
[12:27] <xtknight> yea silly.  besides the default config works
[12:27] <xtknight> though it should be documented
[12:28] <ScottK> Gotta run.  Go find some more bugs to fix in universe...
[12:28] <xtknight> sure thing
[12:44] <TheMuso> danohuiginn: Do you happen to have an updated debdiff for bug 103507 yet?
[12:44] <ubotu> Malone bug 103507 in om "Script 'launchomsynth' brings up two instances of om_gtk" [Undecided,In progress]  https://launchpad.net/bugs/103507
[01:01] <ScottK> xtknight: Did you find a bug to work on yet?
[01:01] <xtknight> ScottK, going to try and start on this one https://bugs.launchpad.net/ubuntu/+source/slab/+bug/105333
[01:01] <ubotu> Malone bug 105333 in slab "The More Applications window takes far too long to come up" [Undecided,Unconfirmed]  
[01:02] <ScottK> xtknight: So you're a Gnome person then?
[01:02] <xtknight> ScottK, it looked like something i could debug
[01:03] <ScottK> Ah.  Well another you might look at that I know needs some serious attention is a series of sigsegv on klamav.
[01:03] <xtknight> ah
[01:03] <xtknight> well actually i just dealt with a sigsegv the other night
[01:03] <xtknight> i'd like to finish work on that bug
[01:03] <ScottK> It's a recent upgrade that was required because clamav was upgraded.
[01:04] <ScottK> As you like, you're a volunteer.
[01:04] <xtknight> bug 104978
[01:04] <ubotu> Malone bug 104978 in xrandr "[apport]  xrandr crashed with SIGSEGV in XRRGetScreenInfo()" [Medium,Confirmed]  https://launchpad.net/bugs/104978
[01:04] <xtknight> see my comments there
[01:04] <xtknight> i'm not sure the next step to take relaly
[01:04] <xtknight> i don't know enough about how libXext works to be modifying it
[01:05] <Fujitsu> That's in main, so not a good one to fix.
[01:05] <xtknight> ahh
[01:05] <ScottK> Ah.  Good point.
[01:06] <xtknight> so this is the place for universe..
[01:06] <xtknight> what's the place or main?
[01:06] <xtknight> -bugs?
[01:06] <Fujitsu> #ubuntu-devel
[01:06] <ScottK> The thing is main is already frozen.
[01:06] <xtknight> ah ok
[01:06] <Fujitsu> Yes, and we will be in a few hours :(
[01:06] <xtknight> i'll take a look at the klamav stuff
[01:06] <danohuiginn> TheMuso: just attached it
[01:06] <xtknight> i dont even know how to set slab up
[01:07] <TheMuso> danohuiginn: Thanks./
[01:08] <xtknight> bug 96090
[01:08] <ubotu> Malone bug 96090 in klamav "[apport]  klamav crashed with SIGSEGV" [Undecided,Unconfirmed]  https://launchpad.net/bugs/96090
[01:08] <xtknight> ugh klamav doesn't even install without error on my system
[01:10] <xtknight> try 'sudo apt-get install klamav' 
[01:10] <xtknight> fail for anyone else?
[01:10] <Fujitsu> That was fixed a couple of weeks ago.
[01:10] <xtknight> pretty easy to fix (install clamav-freshclam afterwards) but odd
[01:10] <Fujitsu> What error does it give?
[01:10] <xtknight> well i'm fully updated
[01:10] <xtknight> i'll paste bin it
[01:10] <Fujitsu> Oh, that one... Isn't that one of yours, ScottK?
[01:11] <xtknight> http://paste.ubuntu-nl.org/14975/
[01:11] <xtknight> ( on $ sudo apt-get install klamav )
[01:12] <Fujitsu> Somebody was working on that problem.
[01:14] <xtknight> i'm not having much luck getting klamav to sigsegv
[01:17] <xtknight> oooh
[01:17] <xtknight> got it
[01:17] <xtknight> try Upgrade and boom
[01:31] <ScottK> Fujitsu: I was trying to entice people to work on it, but didn't have any sign of success.
[01:31] <ScottK> Oh.  That one.  Darn, I thought it was fixed.
[01:33] <ScottK> Bug #33921
[01:33] <ubotu> Malone bug 33921 in clamav "Unable to install clamav-daemon" [Medium,Confirmed]  https://launchpad.net/bugs/33921
[01:34] <Fujitsu> That be the one.
[01:40] <xtknight> ah
[01:40] <xtknight> back to bug fixing
[01:40] <xtknight> now klamav appears to have a builtin upgrade feature
[01:40] <xtknight> what's that all about?
[01:40] <xtknight> isn't synaptic supposed to deliver updates/is it even supposed to exist there?
[01:40] <xtknight> s/synaptic/update-manager
[02:12] <xtknight> hey ScottK you around/ready to fix another one?
[02:12] <xtknight> bug 105341
[02:12] <ubotu> Malone bug 105341 in hostap-driver "hostap-source fails to build" [Undecided,Unconfirmed]  https://launchpad.net/bugs/105341
[02:12] <xtknight> half of the package seems to be missing
[02:20] <Fujitsu> xtknight: That package should probably be removed. It's included in modern kernels.
[02:21] <xtknight> yea just found that out and commented
[02:24] <xtknight> off to investigate Bug 105345
[02:24] <ubotu> Malone bug 105345 in restricted-manager "restricted-manager installs nVidia and ATi drivers with the wrong resolution on wide screens" [Undecided,Confirmed]  https://launchpad.net/bugs/105345
[02:26] <xtknight> Fujitsu, who should i talk about regarding Bug 105341 (hostap)?  who should i tell to remove it besides just making a comment?
[02:26] <ubotu> Malone bug 105341 in hostap-driver "hostap-source fails to build" [Undecided,Unconfirmed]  https://launchpad.net/bugs/105341
[02:26] <xtknight> shouldnt be needed on any Feisty kernel so it shouldn't be in Feisty
[02:27] <Fujitsu> You need to retitle it to be something like `Remove hostap-source from the archive', get a MOTU to ack it, and subscribe ubuntu-archive. The archive team will then remove it.
[02:27] <jmg> what about people using hostap-source with nonstandard kernels
[02:27] <jmg> eg, xen
[02:27] <xtknight> hrmm
[02:28] <gnomefreak> did feisty lose the nvidia 9755 for any reason?
[02:28] <gnomefreak> other than to fix the geforce4 cards
[02:29] <Jucato> oh wow I never noticed that O.o
[02:30] <gnomefreak> Jucato: i did early this morning
[02:30] <Jucato> hm... this is going to get so confusing :P
[02:31] <Jucato> ah no! :)
[02:31] <gnomefreak> it seems they dropped everyone to 96xx
[02:31] <Jucato> gnomefreak: nvidia-glx-new
[02:31] <gnomefreak> huh? thats legacy no?
[02:31] <Jucato> nope
[02:31] <gnomefreak> oh i see what they did :)
[02:31] <gnomefreak> good move 
[02:31] <Jucato> yay!
[02:32] <Fujitsu> So we have nvidia-glx{,-{legacy,new}}?
[02:32] <Jucato> yesh. all thanks to nvidia
[02:32] <gnomefreak> thats what it seems like
[02:32] <Jucato> :/
[02:33] <gnomefreak> now everyone that grabbed -legacy +-100 people now need to know that :(
[02:33] <Jucato> kinda...
[02:34] <TheMuso> Bring on Bring on nouveau I say!
[02:34] <Fujitsu> -100 people need to know it? Impressive.
[02:34] <Fujitsu> How's that going?
[02:34] <xtknight> lol
[02:36] <TheMuso> heh
[02:36] <gnomefreak> + or -
[02:36] <Jucato> +/- 100 people :P
[02:36] <gnomefreak> i just made announcment in #ubuntu+1
[02:37] <TheMuso> i.e I have an ATI radeon here with 128MB video ram, but I pretty much never use all of that.
[02:50] <bddebian> Heya gang
[02:51] <ScottK> Heya bddebian
[02:51] <welshbyte> ello bddebian 
[02:51] <bddebian> Heya ScottK, welshbyte
[02:53] <Administrator> hello bddebian 
[02:53] <bddebian> Hmm, hello Administrator
[02:56] <Administrator> bddebian: /win la
[02:56] <Administrator> bah
[02:56] <Administrator> bddebian: this is joejaxx
[02:56] <Administrator> :)
[02:57] <bddebian> heh
[02:57] <Administrator> this is a temporary client
[02:57] <Administrator> my server is being ddos'd :P
[02:57] <bddebian> joy
[02:58] <Administrator> yeah
[03:00] <Administrator> looks like they stopped
[03:57] <RAOF> Ok.  So, to finish fixing democracyplayer, I need to work out how to (1) make it load the gtkembdedmoz.so from /usr/lib/firefox and (2) Make one of its extension modules link to libpython2.5.  Trouble is, I don't really have any idea how to do this, other than a wrapper which sets the LD_PATH and LD_PRELOADs libpython.  Can anyone point me towards a cleaner solution?
[03:58] <xtknight> bug #?
[03:58] <Fujitsu> RAOF: Yep. Remove democracyplayer :P
[03:59] <RAOF> bug #81798
[03:59] <ubotu> Malone bug 81798 in democracyplayer "[apport]  democracyplayer crashed with TypeError in __new__()" [High,Confirmed]  https://launchpad.net/bugs/81798
[04:01] <xtknight> hrmm
[04:02] <xtknight> RAOF, the gtkembed/python are related to the startup carsh?
[04:02] <xtknight> crash*
[04:03] <xtknight> i'm on the verge of falling asleep right now but i'll help as much as i can
[04:07] <RAOF> Bah, sorry.  Network-manager update killed my network.
[04:07] <xtknight> ya same happened here
 RAOF, the gtkembed/python are related to the startup crash?
 i'm on the verge of falling asleep right now but i'll help as much as i can
[04:08] <RAOF> The gtkembed is the cause of the crash on startup.
[04:08] <RAOF> Well, once you've fixed their use of removed DBUS api.
[04:08] <RAOF> And without linking to libpython, the database extension module will fail to import (on AMD64, at least), so the database won't work.
[04:08] <ScottK> Anyone in UUS up for a simple python bug fix (one liner)?  Bug #104637 is ready for upload.
[04:08] <ubotu> Malone bug 104637 in pyparsing "pyparsing 1.4.5 released in dec 06" [Low,Confirmed]  https://launchpad.net/bugs/104637
[04:09] <ScottK> Despite the title of the bug I just pulled the one fix out of the new upstream release.
[04:11] <TheMuso> ScottK: I'll have a look at it.
[04:12] <ScottK> TheMuso: Thanks.
[04:13] <RAOF> Alternatively, what *other* packages link to/use gtkembedmoz?  I could try to work out how to do it from there?
[04:17] <TheMuso> ScottK: You might want to make sure that changelog entries fit onto an 80 column line. So the lines probably shouldn't be any longer than the header/footer for the changelog entry.
[04:17] <ScottK> Oops.  I usually do that.  Ugh.
[04:17] <TheMuso> ScottK: Have a look at the other entries for an example.
[04:18] <ScottK> Want me to do it over?
[04:18] <TheMuso> Please.
[04:19] <ScottK> I'll have it for you again in a moment.
[04:19] <TheMuso> Sure.
[04:20] <TheMuso> ScottK: actually, hold on a sec.
[04:20] <ScottK> Argh.  82 characters.  Missed it by THAT much.
[04:20] <TheMuso> THis package doesn't appear to have any previous patches applied to it, either in a patch system or in the .diff.gz. So since you are patching a package file, please set up a patch system and use a patch in debian/patches.
[04:21] <TheMuso> The package uses cdbs, so you can use simple-patchsys.
[04:21] <ScottK> OK.  What I had been told before was that if there was no existing patch system and it was a simple fix, changing the source was OK...
[04:22] <TheMuso> ScottK: Read up on cdbs-edit-patch
[04:22] <TheMuso> RAOF: +1
[04:23] <TheMuso> ScottK: Even for simple fixes, its better to use patches, as if ever the package has to be updated/merged for any reason, its one less potential conflict that is solved before the package is even unpacked.
[04:23] <TheMuso> And there is also a chance that the new upstream file has changed significantly enough that the patch won't apply any more.
[04:24] <TheMuso> SO having it in debian/patches allows for easy removal/addition of the patch, and any others that may be needed.
[04:24] <RAOF> Also, it's nice an easy to send upstream, too.
[04:24] <ScottK> The most likely scenario in this particular case is Debian gets a new upstream that already has this fix in it and we synch over it.
[04:24] <ScottK> This is already fixed upstream
[04:28] <xtknight> cool
[04:28] <xtknight> it's in there? :P
[04:29] <TheMuso> xtknight: SOunds like it.
[04:29] <ScottK> xtknight: It didn't change the directory permissions because bip was running.  Looks like it need a preinst to make sure it's stopped before the upgrade.
[04:30] <ScottK> But it's done now, so off to the joy's of patching systems.
[04:30] <ScottK> TheMuso: It was his first bug fix he got uploaded.
[04:30] <TheMuso> ScottK: They aren't all that bad. Cdbs-edit-patch makes it very easy.
[04:30] <TheMuso> Thanks to pitti for that one.
[04:33] <crimsun> TheMuso: are you handling 104637?
[04:33] <TheMuso> crimsun: Yeah.
[04:33] <crimsun> ok
[04:33] <ScottK> No he's not, he's torturing me.
[04:33] <ScottK> ;-)
[04:34] <crimsun> good thing I asked before dput :)
[04:34] <RAOF> So, anyone with ideas for how to fix the linking issues?  Or even other packages using gtkembedmoz?  Or how to find them (firefox-dev's rdepends don't have anyhthing interesting)
[04:34] <TheMuso> crimsun: Whats your view on small fixes and patch systems, i.e for the bug in question?
[04:37] <ScottK> I know I'm complaining BTW, but this is actually good as I'm learning stuff I need to know.
[04:37] <crimsun> TheMuso: it doesn't have an existing patch management system, so I wouldn't add one (which has been the historical approach we've taken)
[04:37] <xtknight> RAOF, back to business
[04:37] <crimsun> TheMuso: we'd filterdiff out everything else save the relevant hunk(s) in the diff.gz, then attach that to a Debian BTS entry
[04:38] <xtknight> you want to know other packages that use gtkembedmoz?  it's definitely a mozilla thing (moz)
[04:38] <RAOF> Yes, that'd be nice.
[04:38] <TheMuso> crimsun: Ah ok.
[04:38] <RAOF> Yes, it's in /usr/lib/firefox, and the firefox-dev package.
[04:38] <TheMuso> ScottK: Sorry dude, don't need to worry about it then. Just the changelog fixup is fine.
[04:38] <ScottK> Well I've already got the patch made now...
[04:39] <xtknight> RAOF, well i believe it's only in firefox
[04:39] <xtknight> RAOF, democrplayer is based off firefox, isnt it?
[04:39] <xtknight> Depends: firefox
[04:39] <xtknight> for it
[04:39] <RAOF> Well, kinda.
[04:40] <RAOF> I don't think it's XUL, though.
[04:40] <xtknight> but why is it crashing?
[04:40] <RAOF> Because it's not linking to libgtkembedmoz correctly.
[04:40] <xtknight> would statically compiling it be an option?
[04:41] <RAOF> Running it with LD_PATH=/usr/lib/firefox democracyplayer works.
[04:41] <RAOF> xtknight: Colour firefox .so only.  No static linking available, it seems.
[04:41] <xtknight> add it to ld.so.conf and do ldconfig
[04:41] <RAOF> xtknight: Yes, well that also works.
[04:41] <xtknight> it doesnt start for me, though
[04:41] <xtknight>  LD_PATH=/usr/lib/firefox democracyplayer
[04:41] <xtknight> doesnt work
[04:41] <jmg> there is no data
[04:42] <RAOF> xtknight: Yeah, you need to patch it first.
[04:43] <xtknight> well anything quick i miht be able to answer?  gotta run
[04:43] <xtknight> probably be here later
[04:43] <RAOF> Only how to get it to not need the ld.so.conf addition :)
[04:44] <xtknight> only option is statically linking it.  otherwise it needs to be pointing to the library, i suppose.  make a script for it (a la firefox32).  democracyplayer=script, and inside do LD_PATH= ... 
[04:44] <xtknight> i dont see a problem with that
[04:44] <xtknight> 99% have firefox, 99% have it in that location, and democracy will start
[04:44] <RAOF> Hm.  But how does *yelp* do it correctly, then?
[04:44] <xtknight> hrm? yelp=?
[04:45] <xtknight> ohh
[04:45] <xtknight> well ltrace it; )
[04:45] <xtknight> same as epiphany and other firefox apps i guess
[04:47] <xtknight>     libgtkembedmoz.so => /usr/lib/firefox/libgtkembedmoz.so (0xb7613000)
[04:47] <xtknight> weird
[04:47] <RAOF> Indeedy do.
[04:47] <xtknight> well democracy player *is* statically linked
[04:48] <xtknight> oh nm
[04:48] <xtknight> i was using the script
[04:48] <xtknight> never mind that, it's python
[04:48] <xtknight> heck
[04:48] <RAOF> Hm, maybe that particular library *isn't* the problem, because ldd on its mozilla extension also shows /usr/lib/firefox/libgtk....
[04:48] <ScottK> TheMuso: If I don't have /usr/share/cdbs/1/class/simple-patchsys.mk on my system, what do I need to install?
[04:49] <TheMuso> ScottK: ScottK Wrong dir. Its in rules.
[04:49] <ScottK> Ah.
[04:49] <xtknight> RAOF, /usr/lib/python-support/democracyplayer/python2.5/democracy/...
[04:49] <xtknight> whats this dir
[04:49] <ScottK> Yep.  There it is.  Thanks TheMuso
[04:49] <RAOF> That's the dir containing all the python extension modules.
[04:52] <RAOF> Hm, failing actually knowing how to fix it properly, is a wrapper script solution acceptable?
[04:52] <xtknight> sure it seems like it
[04:55] <xtknight> it doesn't seem like a horrible hack to me
[04:55] <xtknight> the cpu sure doesnt care...the user doesnt care either ;)
[04:55] <xtknight> not sure what's at stake
[04:56] <xtknight> there dont seem to be any performance or security conerns
[04:56] <xtknight> make it depend on firefox so there are no missing library problems
[04:56] <xtknight> yelp isnt a python program either...so maybe that's why it works
[04:56] <RAOF> Maybe.
[05:04] <ScottK> TheMuso: Bug #104637 is ready again...
[05:04] <ubotu> Malone bug 104637 in pyparsing "pyparsing 1.4.5 released in dec 06" [Low,Confirmed]  https://launchpad.net/bugs/104637
[05:04] <TheMuso> ScottK: Thanks.
[05:12] <ScottK> TheMuso: Do you know if it's OK yet?  It's late here and I need to get to bed.
[05:12] <TheMuso> ScottK: Looks good, just sanity checking the resulting deb.
[05:14] <ScottK> TheMuso: I'm off to bed.  If that doesn't work out for some reason, I'd appreciate it if you'd just shorten the one line from the first patch and upload that.  Good night and thanks for the help.
[05:14] <TheMuso> Sure.
[05:15] <TheMuso> ScottK: Uploaded.
[05:15] <ScottK> Ah.  Great.  Thanks again.
[05:43] <xtknight> bug 105374
[06:24] <jodas> Can anyone here help me with qtparted?
[06:29] <ajmitch> impatient people
[06:30] <RAOF> Also, asking questions in the wrong places.
[06:44] <RAOF> Is there any better way to fix democracyplayer, other than to use a wrapper that launches it with LD_LIBRARY_PATH=/usr/lib/firefox?  I really don't know enough about the dynamic loader :)
[07:07] <gpocentek> morning/evening
[07:07] <ajmitch> hi gpocentek 
[07:07] <crimsun> 'lo
[07:09] <gpocentek> hello ajmitch, hello crimsun :)
[07:09] <imbrandon> moins ajmitch crimsun gpocentek 
[07:09] <imbrandon> mmmm mac and cheese for breakfast
[07:10] <ajmitch> ugh
[07:12] <TheMuso> lovely
[07:12] <ajmitch> for an example of a demanding user: bug 105378
[07:12] <ubotu> Malone bug 105378 in postfix "SASL authentication failure Ubuntu 6.10" [Undecided,Unconfirmed]  https://launchpad.net/bugs/105378
[07:13] <ajmitch> "I consider this bug to be grave, needs a fix at least within 72 hours. Immediatly if it is really not an end user issue."
[07:13] <Fujitsu> Nice, ajmitch.
[07:14] <Fujitsu> `3. Follow the postfix 6.10 guide.'
[07:14] <ajmitch> Fujitsu: I doubt that 'latest updates' broke it, somehow
[07:14] <ajmitch> yeah
[07:14] <Fujitsu> Wow, Postfix has had a few releases lately.
[07:14] <ajmitch> like howtoforge.com
[07:15] <ajmitch> maybe the ubuntu wiki
[07:15] <Fujitsu> Even worse.
[07:16] <ajmitch> hint: there have been no updates to sasl or postfix in dapper for a year
[07:17] <Fujitsu> I noticed.
[07:17] <Fujitsu> He does say Edgy, though.
[07:17] <Fujitsu> But I don't notice any there either.
[07:17] <ajmitch> right, sorry, I saw dapper further down
[07:18] <crimsun> ajmitch: aww, that bug report calls for my advisor's inkwell stamp - a bull taking a crap
[07:18] <crimsun> best stamp I've ever seen
[07:18] <ajmitch> haha
[07:18] <Fujitsu> crimsun: I want one.
[07:18] <ajmitch> most likely cause - he's trying to use chrooted postfix
[07:18] <Fujitsu> Probably, yes... Reject it before it spreads.
[07:18] <jmg> crimsun: pics.
[07:46] <RAOF> Alright!  Who'd like to look at the debdiff for bug #81798
[07:46] <ubotu> Malone bug 81798 in democracyplayer "[apport]  democracyplayer crashed with TypeError in __new__()" [High,Confirmed]  https://launchpad.net/bugs/81798
[07:47] <superm1> RAOF, you've got it all fixed up? :) :)
[07:47] <RAOF> Yup.  Kinda.
[07:47] <RAOF> I don't like the solution, but it works.
[07:47] <superm1> nice job dude.  record time with just starting last night
[07:47] <superm1> you used some LD_PRELOAD business right?
[07:47] <RAOF> Actually, that's only needed for the new upstream version it seems
[07:48] <RAOF> The current version only needs LD_LIBRARY_PATH :-/
[07:48] <superm1> hehe
[07:48] <RAOF> Also, I've been looking at this for a little bit longer than just last night.
[07:48] <RAOF> :)
[08:19] <nrg88> morning
[08:19] <nrg88> do you guys know reportbug-ng?
[08:20] <imbrandon> we know of it yes, its debian ng bug reporter
[08:20] <imbrandon> why?
[08:21] <nrg88> it would be excelent to extend apport to do such things
[08:21] <imbrandon> tis open source , grab it and run young padiwan
[08:21] <nrg88> as i've seen it, apport just collects info, and fills a new bugreport, doesn't i?
[08:21] <imbrandon> :)
[08:21] <nrg88> *it
[08:22] <nrg88> well, it has to communicate with launchpad
[08:22] <nrg88> i can't experiment with launchpad :D
[08:22] <imbrandon> why ?
[08:23] <nrg88> i'll get my ass kicked for creating "white" bugreports, and doing stuff just for experimenting
[08:23] <RAOF> The screencast on the homepage makes it look quite a lot like it's trying to make up for the lack of the Debian BTS's web-interface
[08:24] <nrg88> the apport makers and launchpad integrators know how launchpad works
[08:24] <imbrandon> nrg88, there is a interface you can do that in, ask in #launchpad
[08:24] <nrg88> ok
[08:24] <nrg88> thanks
[08:24] <nrg88> maybe it will become a feisty+1 feature :)
[08:26] <Fujitsu> nrg88: staging.launchpad.net is on a database designed for stuffing around in.
[08:26] <Fujitsu> nrg88: staging
[08:26] <Fujitsu> *staging's DB is copied from the normal one daily, so is good to work with.
[08:28] <imbrandon> heya Fujitsu 
[08:28] <Fujitsu> Hi imbrandon.
[08:28] <nrg88> thanks, i'll download the reportbug-ng source, and see what i can do with sub-minimal C knolege ;)
[08:28] <imbrandon> its python and gtk iirc
[08:28] <imbrandon> not C
[08:29] <nrg88> hm, it's in QT3
[08:30] <nrg88> "Some features I'm planning to implement: Porting R-NG from qt3 to qt4..."
[08:32] <superm1> hey imbrandon there was some chatter earlier regarding regular 0.20-fixes updates for myth in the interim.  i'm mocking together a script that will hopefully sit on your mythbuntu server and run weekly to rebuild debs automatically from a checkout
[08:32] <superm1> like between feisty and feisty+1 release for those that wanted it
[08:33] <imbrandon> nice
[08:33] <imbrandon> sounds like the script i'm working on for kde4 snapshots
[08:34] <imbrandon> and koffice2 and konversation snapshots
[08:34] <superm1> its pretty straightforward thus far, svn co, copy over the debian directory, increment versions, build source packages, clean up, and kick off the work into pbuilder
[08:34] <superm1> only thing is, can gpg-agent work off this for signing them?
[08:35] <imbrandon> if its an auto build you probably dont wanna sign it with your own key
[08:35] <TheMuso> Where can one find out more info about staging?
[08:35] <imbrandon> like the autobuilds me and seveas use we use a seperate key
[08:36] <superm1> k
[08:36] <imbrandon> TheMuso, there really isnt much info aobut it other than #launchpad
[08:36] <superm1> but the passphrase for the key is cacheable?
[08:36] <TheMuso> imbrandon: righto
[08:36] <superm1> even when ran from cron jobs
[08:36] <imbrandon> superm1, the auto key dosent have a passphrase since its not trusted
[08:36] <superm1> ah
[08:38] <imbrandon> sides you realy dont have to sign the debs at all, just build with -us -uc and sign the repo ( with like falcon )
[08:38] <superm1> is it the same key that you sign the falcon repo with too then, or you just use yours for that instead?
[08:38] <superm1> i guess i'm overly accustomed to signing debs now :)
[08:39] <imbrandon> well since its automated you realy dont want it to be 100% "trusted" anyhow
[08:39] <imbrandon> :)
[08:39] <superm1> good point
[08:40] <superm1> to that effect, any news with regarding to connection to the server as of yet?
[08:40] <imbrandon> yea its just a matter of us getting time at work to put the new switch in , get a core drop done and power run to the new rack
[08:40] <imbrandon> the servers are all ready, infact i put the last one in place tonight
[08:41] <superm1> cool, vg
[08:41] <Fujitsu> Which new servers are these?
[08:41] <imbrandon> Fujitsu, one is for ubuntuwire.com ( the ldap server ) one is for mythbuntu that i promised them
[08:41] <Fujitsu> Ah.
[08:42] <imbrandon> and there is now room for a amd64 and a sparc localy
[08:42] <imbrandon> :)
[08:42] <RAOF> Huzzah!  More people checking AMD64 builds!
[08:44] <Fujitsu> Huzzah, ability to debug AMD64 stuff!
[08:45] <Fujitsu> Although I probably should get myself a new machine soon, especially with the large reduction in Athlon X2 prices recently.
[08:46] <TheMuso> Fujitsu: Core2 duo doesn't appeal?
[08:46] <Fujitsu> Can't say I ever really liked Intel.
[08:46] <Fujitsu> Aren't that somewhat more expensive, too?
[08:46] <Fujitsu> \
[08:46] <TheMuso> Ah ok.
[08:46] <TheMuso> Dunno. Haven't been keeping up with prices.
[08:46] <RAOF> Not on the price/performance ratio, from memory.
[08:47] <superm1> Fujitsu, the Core2's are mighty fast from all the reviews i've been reading.  and worth their buck
[08:48] <Fujitsu> Seems I should be looking at them instead, then.
[08:48] <superm1> something along the lines of a 1.67 Core2 having >= performance of a 2.0 Core
[08:49] <imbrandon> right now the for the price the intels are the way to go, and they are out preforming the amds
[08:50] <TheMuso> The only reason why I'd get a new CPU atm is for 64-bit dev work, which I can't entirely justify. The hardware I have at present does me fine for what I do.
[08:50] <imbrandon> i have some pent-d dual core 3.0 ghz boxen at home that smoke the amd64 4200+ i have upstairs
[08:51] <imbrandon> i mean the intels litterly get up off the desk and run circles arround the amd's
[08:51] <imbrandon> :)
[08:52] <superm1> which doesn't bode well for AMD.  they're already in the dog house for me with all this ATI business....
[08:52] <imbrandon> i used to be a amd fanboi , untill about 6 months ago
[08:53] <superm1> what changed it for you?
[08:53] <imbrandon> then i re-examined the landscape
[08:54] <imbrandon> superm1, pure preformance, i payed $100 for the dual core 3.0ghz pentium-d's and it littlerly smoked the hell out of the two "better" amd's i had
[08:54] <TheMuso> imbrandon: The core2s are better than that CPU though aren't they?
[08:54] <superm1> TheMuso, much better
[08:54] <imbrandon> pent-d and core2 == about the same , both > core
[08:54] <superm1> imbrandon, you sure?
[08:54] <imbrandon> yes
[08:55] <TheMuso> I thought core2 was less power hungry.
[08:55] <superm1> thats what i heard too
[08:55] <imbrandon> TheMuso, yea i'm talkin preformance
[08:55] <TheMuso> Right.
[08:55] <imbrandon> not power
[08:55] <imbrandon> i could honestly care less about power consumption personaly
[08:56] <superm1> http://www.bcchardware.com/index.php?option=com_content&task=view&id=2869&Itemid=40
[08:56] <superm1> thats one that comes to mind
[08:57] <imbrandon> superm1, thats quite old comparing to the 805, i have a pent-d 930 and thats the bottom now
[08:57] <superm1> ah yes, that is Aug 2006
[08:57] <imbrandon> but as i said anyhow "about the same" , and both are still much better than the plain "core"
[08:58] <imbrandon> and TONS TONS better than the amd64s
[08:58] <imbrandon> gnight
[08:58] <TheMuso> Night superm1.
[09:01] <Fujitsu> Intel has some nice affordable processors, like the QX6700. The RRP of that is only AU$2,029.00.
[09:51] <RAOF> Anyone feel like checking a debdiff that should fix a high importance bug with 70 duplicates?  It's attached to bug #81798
[09:51] <ubotu> Malone bug 81798 in democracyplayer "[apport]  democracyplayer crashed with TypeError in __new__()" [High,Confirmed]  https://launchpad.net/bugs/81798
[09:53] <KenSentMe> RAOF, it's a feisty bug is it
[09:53] <RAOF> Yup.
[09:53] <KenSentMe> I'm waiting for the backport to be fixed on edgy, i don't run feisty yet
[09:53] <RAOF> It's not broken on edgy, is it?
[09:54] <KenSentMe> RAOF, the backport is. At least on my system
[09:54] <RAOF> It shouldn't be, it's the python2.5 transition (and the DBUS api) that breaks it.
[09:54] <RAOF> KenSentMe: Hm.  Does running "LD_LIBRARY_PATH=/usr/bin/firefox democracyplayer" work?
[09:55] <KenSentMe> i'll try
[09:56] <jml> RAOF: is that a known bug in Python 2.4?
[09:56] <jml> or DBUS or wherever?
[09:56] <RAOF> No, it's not a bug in DBUS.  They were using non-public API that got deprecated, then removed
[09:57] <dholbach> good morning
[09:57] <RAOF> Good evening :)
[09:58] <KenSentMe> RAOF, nope, doesn't work. Here is the backport along with the bug report
[09:58] <KenSentMe> https://bugs.launchpad.net/edgy-backports/+bug/80237
[09:58] <ubotu> Malone bug 80237 in edgy-backports "Please backport Democracy TV to Edgy" [Undecided,Fix released]  
[09:58] <dholbach> hey RAOF
[09:58] <jml> RAOF: segfaulting on older Python doesn't sound like a packaging bug to me.
[09:59] <RAOF> jml: What segfaulting on older python?  It doesn't properly link to the firefox libs, and segfaults on whatever version of python you want to run it on.
[09:59] <jml> ahh.
[09:59] <RAOF> Unless you have /usr/lib/firefox in your LDPATH
[09:59] <jml> "spawn subprocesses with python2.5 rather than python2.4, since
[09:59] <jml> +      libboost-python will segfault with anything else"
[09:59] <RAOF> Oh, that bit.
[10:00] <RAOF> Yeah, libboost-python is *only* built for python2.5, but doesn't fail to import in python2.4, it just segfaults.
[10:00] <jml> that sucks.
[10:00] <RAOF> Oh, yes.  There's probably a bug to be filed there.
[10:05] <jml> anyway, that's the first debdiff I've looked at. interesting.
[10:06] <RAOF> Now, be a MOTU and upload it :)
[10:09] <KenSentMe> RAOF, i want to test the debdiff in a vm, but that install hasn't been updated for a while. Sadly i don't want to take up all the bandwith here. Do i need to update other packages than the python 2.4 and 2.5 ?
[10:09] <RAOF> Um, it needs firefox-dev, I'm not sure whether that's in Edgy or not.
[10:10] <RAOF> I don't know if it requires anything else.
[10:10] <KenSentMe> I run feisty in VMWare
[10:12] <RAOF> If you run Feisty, it shouldn't require you to update anything at all.
[10:16] <KenSentMe> RAOF, sorry for the nooby questions, but how do i run/use the debdiff
[10:16] <RAOF> Let me grab the wiki...
[10:16] <RAOF> KenSentMe: https://wiki.ubuntu.com/UbuntuPackagingGuide/BuildFromDebdiff?highlight=%28debdiff%29
[10:17] <KenSentMe> Ok, i'll have a look
[10:24] <KenSentMe> The network here isn't all that. Installing build-essential etc. takes me more than 10 mins
[11:05] <\sh> moins
[11:06] <Fujitsu> Hi \sh.
[11:22] <danohuiginn> I'm trying to make a python module work with python2.5
[11:22] <danohuiginn> do I need to add python2.5-modulename to provides/conflicts/replaces?
[11:23] <danohuiginn> or is that just if there was once a version-specific module
[11:23] <Fujitsu> Are you following the new Python policy?
[11:23] <danohuiginn> Fujitsu: I'm not sure. Should I be?
[11:24] <Fujitsu> Definitely, otherwise the package has no chance of being accepted.
[11:24] <danohuiginn> Fujitsu: it's an existing package I'm fixing
[11:24] <Fujitsu> Ah.
[11:24] <Fujitsu> Which?
[11:25] <danohuiginn> elementtree. bug 104184
[11:25] <ubotu> Malone bug 104184 in elementtree "please build elementtree for python2.5" [Undecided,In progress]  https://launchpad.net/bugs/104184
[11:26] <geser> isn't either python-support or python-central adding the versioned python-modules in p/c/r?
[11:27] <Fujitsu> Bah, how nice of them to make it our problem as of 15 hours ago.
[11:27] <Fujitsu> There's a fixed bug on the Debian package about the policy transition, but it seems to have not been done properly.
[11:27] <Fujitsu> Oh, I see that it's rather special.
[11:29] <Fujitsu> That should be properly fixed for Feisty+1 (ie. the dependents should be modified)
[11:31] <Fujitsu> danohuiginn: You won't need the extra Provides/Conflicts/Replaces.
[11:31] <danohuiginn> thanks, Fujitsu
[11:32] <Fujitsu> That'll make it a one character change, won't it? (excluding changelog/maintainer changes)
[11:32] <danohuiginn> also, you think I should set the maintainer to MOTU? or as core until it's actually moved to universe?
[11:33] <Fujitsu> It is in universe now.
[11:33] <Fujitsu> It was moved there about 15 hours ago.
[11:33] <danohuiginn> ah, OK
[12:07] <KenSentMe> RAOF, i tried the debdiff and it works fine
[12:08] <RAOF> Ta, thanks for the comment.
[12:13] <sacater> imbrandon: on this council meeting, shall i bring irc convos of people ive helped into it?
[12:16] <geser> sacater: if you have a fan base bring them to the cc meeting
[12:17] <sacater> geser: well, this is more of a newbie i helped with a few file permissions
[12:17] <sacater> i have 2 for a fanclub
[12:17] <sacater> atm
[12:27] <geser> can somebody reproduce bug #99470?
[12:27] <ubotu> Malone bug 99470 in apache "I could not install apache" [Undecided,Unconfirmed]  https://launchpad.net/bugs/99470
[12:28] <geser> it seems to kill the build of libembperl-perl on i386 and amd64
[12:28] <geser> but the package builds fine in my amd64 pbuilder
[12:32] <imbrandon> sacater, nah i wouldent worry about irc logs
[12:33] <imbrandon> just your fan club
[12:33] <imbrandon> when is the meeting ?
[12:35] <sacater> erm
[12:35] <sacater> 17th
[12:35] <sacater> at 8
[12:35] <sacater> pm
[12:35] <imbrandon> CST ?
[12:35] <sacater> UTC
[12:35] <imbrandon> ahh ok
[12:35] <sacater> you still coming
[12:36] <imbrandon> i'll try may darndest, if i cant make it i'll send an email to the CC
[12:36] <sacater> ?
[12:36] <sacater> okies
[12:36] <sacater> thanks
[12:45] <Mez> how can i make it so when I upgrade It keeps a package at the version It's currently at ? 
[12:45] <Mez> (I had to re-build it for jack support)
[12:45] <ajmitch> man apt_preferences
[12:45] <Mez> I thought you could only pin against distros with thaT?
[12:45] <ajmitch> nope
[12:46] <ajmitch> examples show otherwise
[12:46] <ajmitch> you could do aptitude hold, but apt-get ignores those
[12:49] <TheMuso> Mez: What package?
[12:50] <geser> ajmitch: what abould dpkg --set-selections? does apt-get ignore them too?
[12:51] <ajmitch> geser: I haven't tried
[12:57] <Mez> TheMuso, libasound2-plugins
[01:11] <danohuiginn> thanks for the upload, geser
[01:13] <TheMuso> Mez: Oh ok
[02:16] <DarkSun88> Hi all
[02:16] <TheMuso> Hey DarkSun88.
[02:17] <DarkSun88> TheMuso: Hi :)
[02:17] <TheMuso> Ooo debian unstable is going to have tetex breakage.
[02:17] <TheMuso> Which means we are likely to also get it.
[02:17] <DarkMageZ> mmhmm. going to be fun.
[02:18] <TheMuso> Oh yeah.
[02:18] <shawarma> What sort of breakage?
[02:19] <DarkMageZ> they're moving to tetex-live right?
[02:19] <TheMuso> DarkSun88: SOmething like that.
[02:19] <shawarma> We've already done most of that.
[02:19] <TheMuso> sorry, DarkMageZ 
[02:19] <Fujitsu> tetex-live? Nice hybrid.
[02:19] <shawarma> Most things depending on tetex-* now depends on tetex-* | texlive-*
[02:19] <Fujitsu> Is tetex going to be removed?
[02:20] <shawarma> Fujitsu: Hopefully. :-)
[02:20] <Fujitsu> Good, good.
[02:20] <StevenK> Why?
[02:20] <Fujitsu> Not too much stuff exclusively depends on it.
[02:20] <shawarma> 1) It's crap 2) it's unmaintained crap 3) it's crap
[02:20] <Fujitsu> tetex has been dead upstream for a while.
[02:20] <shawarma> did I mention it's crap?
[02:21] <shawarma> contex? wtf?
[02:21] <Fujitsu> contex? I've dealt with texlive, miktex, tetex, but not contex.
[02:21] <StevenK> Oops, it's context
[02:22] <ScottK> TheMuso: Thanks again for the patch system lesson last night.  I've also sent the patch to Debian.
[02:23] <TheMuso> ScottK: Cool.
[02:29] <ScottK> xtknight: Nevermind what I said last night about your bip fix not being complete.  I don't know what I was thinking.  It worked just fine.
[02:54] <jekil> hello
[02:56] <Hobbsee> hiya
[02:56] <imbrandon> ello
[02:56] <zul> has anyone noticed that the motu council meeting and the development team meeting is on at the same time?
[02:56] <zul> hi by the way
[02:57] <imbrandon> zul, iirc the MC meetings are cancled in favor of just MOTU meetings
[02:57] <Adri2000> there is no MC meeting planned
[02:58] <Adri2000> 12 Apr 20:00: MOTU | 12 Apr 20:00: Development Team | 12 Apr 21:00: Ubuntu Development Team
[02:58] <Adri2000> but there is something wrong with the devel team meeting
[02:59] <zul> imbrandon: cool according to the topic on #u-meeting is at the same time
[03:00] <geser> didn't the dev meeting got moved to 19:00 utc?
[03:01] <zul> maybe im just confused and out of date with other priorities *shrug*
[03:02] <geser> argh, the tb meeting was going be one hour earlier
[03:08] <AnAnt> Hello, which package is responsible for scancodes ?
[03:08] <ScottK> AnAnt: Universe packages are maintained by the whole MOTU team.  What's your question.
[03:09] <AnAnt> ScottK: I ran showkey -m now on both Edgy & Feisty
[03:09] <AnAnt> ScottK: I found that some key combinations (for example CTRL+ALT+O) have different scan codes on Edgy & Feisty
[03:09] <AnAnt> ScottK: on Edgy it gives: keycode 7 release, on Feisty it gives:
[03:09] <AnAnt> keycode  66 release
[03:09] <AnAnt> keycode  32 release
[03:10] <AnAnt> ScottK: I wanted to know why is that 
[03:10] <ScottK> What locale are you using?
[03:10] <AnAnt> ScottK: en_US.UTF-8
[03:13] <AnAnt> Hello, which package is responsible for scancodes ? I ran showkey -m now on both Edgy & Feisty, I found that some key combinations (for example CTRL+ALT+O) have different scan codes on Edgy & Feisty
[03:13] <AnAnt> oops
[03:13] <AnAnt> sorry
[03:14] <ScottK> AnAnt: I think it's langpack-locales
[03:14] <TheMuso> AnAnt: I would advise you to not ask/post any thing in -devel unless it is related to the feisty rc release/final release.
[03:14] <StevenK> AnAnt: For Ctrl-Alt-O I get 27/15 on both Edgy and Feisty.
[03:14] <TheMuso> How do you test for this kind of stuff?
[03:15] <StevenK> TheMuso: showkeys
[03:15] <AnAnt> TheMuso: showkey -m
[03:15] <ScottK> IIRC AnAnt has a broken universe package he's hoping to fix.
[03:15] <ScottK> AnAnt: ^^^  These guys know way more than I do.
[03:15] <TheMuso> AnAnt: I don't know. Please keep our response in the same channel that I talked to you.
[03:15] <AnAnt> TheMuso: sorry, I got mixed up
[03:16] <AnAnt> ScottK: you still remember ;)
[03:17] <AnAnt> StevenK: acon
[03:18] <AnAnt> ok, I'll try playing with /etc/default/console-setup
[03:18] <AnAnt> br
[03:18] <AnAnt> brb
[03:20] <AnAnt> ok, SOLVED !
[03:21] <ScottK> ?
[03:22] <AnAnt> changed CHARMAP="ISO-8859-1" in /etc/default/console-setup
[03:22] <AnAnt> so acon is working after all !
[04:10] <bddebian> Heya gang
[04:10] <xtknight> hey
[04:10] <xtknight> ready to triage/fix more bugs today..
[04:13] <bddebian> xtknight: Nah, I don't do anything :-(
[04:15] <geser> Hi bddebian
[04:16] <geser> xtknight: don't believe him, he only needs good poking
 need more coffee
[04:17] <bddebian> Heya geser
[04:41] <shawarma> I forget. do universe uploads "just work" right now or do I need to poke Mithrandir?
[04:44] <geser> they are on manual
[04:44] <geser> you need to poke an archive admin
[04:45] <bddebian> Doh
[04:46] <crimsun> I've just been uploading and letting them filter through at the admins' discretion
[04:46] <crimsun> I'm not terribly worried, since feisty+1's due to open $soon
[04:48] <bddebian> Gabby Goat?
[04:48] <bddebian> :-)
[04:48] <bddebian> Grumpy Gnu, boy would that be funny!
[04:54] <joejaxx> bddebian: lol haha
[04:57] <ScottK> Golden Gopher
[04:58] <xtknight> grizzly gorilla
[04:58] <crimsun> the land of 10k lakes. I worked for a spell in MN.
[04:58] <shawarma> Gassy gerbil
[04:58] <crimsun> fun times
[04:58] <xtknight> lol
[04:59] <joejaxx> lol
[05:00] <joejaxx> Graceful Gazelle
[05:00] <xtknight> too touchy feely
[05:01] <xtknight> only animal i know that starts with G is gorilla though so bleh
[05:01] <joejaxx> <something here> Gazelle
[05:01] <joejaxx> :P
[05:01] <xtknight> Growly Gazelle
[05:02] <xtknight> kind of paradoxical 
[05:02] <xtknight> maybe it implies that the impossible will happen
[05:02] <lupine_85> Goggled Gimp ?
[05:02] <joejaxx> Gallant Gazelle
[05:02] <nixternal> Gentle Giraffe - but don't tell anyone that I told you
[05:02] <xtknight> hah ugh
[05:03] <nixternal> haha
[05:03] <joejaxx> nixternal: its in the logs now :Phaha
[05:03] <nixternal> it has to be an animal that can't defend itself on its own, but only with its community
[05:03] <xtknight> Growly Gremlin
[05:03] <joejaxx> a gazelle :)
[05:03] <highvoltage> Gray Giraffe?
[05:04] <nixternal> actually, a Warthog could defend itself, and depending on the type of badger it could also defend itself
[05:04] <joejaxx> nixternal: but a fawn could not
[05:04] <xtknight> a feisty one could
[05:04] <Nafallo> lol
[05:04] <joejaxx> xtknight: lol
[05:04] <nixternal> joejaxx: but the fawns community could help keep it safe
[05:04] <Nafallo> it's this time again :-)
[05:04] <joejaxx> nixternal: yes
[05:05] <xtknight> feisty+2=howling hyena
[05:06] <geser> isn't G already used for Grumpy Groundhog?
[05:06] <ScottK> OK, if you must.... hiccuping horsefly
[05:06] <joejaxx> geser: yeah
[05:06] <nixternal> hahaha
[05:06] <nixternal> ScottK: I love it!
[05:06] <nixternal> hurry up and send that mdz and sabdfl
[05:06] <joejaxx> lol imagine that
[05:06] <joejaxx> download the new ubuntu release: Hiccuping Horesefly
[05:06] <joejaxx> Horsefly*
[05:06] <ScottK> nixternal: Go ahead and send it.  Don't feel like you have to credit me.
[05:07] <Nafallo> no, I DON'T want to upload to hiccuping :-)
[05:07] <Nafallo> more than a bit to obscure :-P
[05:07] <joejaxx> nixternal: you actually send it to them?
[05:07] <lupine_85> not happy hippo ?
[05:07] <bddebian> Hungry Hungry Hippo
[05:07] <joejaxx> Hungry Hippos?
[05:07] <lupine_85> that too :D. great game
[05:08] <zul> i think hungry hippos is copyrighted
[05:08] <geser> "crispy calamari" if we were at 'C'
[05:08] <bddebian> I've made an executive decision and it's going to be Grumpy Gnu damnit!
[05:08] <joejaxx> Lol
[05:09] <joejaxx> who do you send the names to?
[05:09] <tsmithe> bddebian, who put you in charge?
[05:09] <xtknight>  /dev/null
[05:09] <tsmithe> someone run !names
[05:09] <tsmithe> i'm banned
[05:09] <bddebian> tsmithe: I did :)
[05:09] <xtknight> secret hack in ubuntu
[05:09] <tsmithe> joejaxx, look in the link in there
[05:09] <tsmithe> xtknight, hah
[05:09] <bddebian> !names
[05:09] <ubotu> Sorry, I don't know anything about names - try searching on http://bots.ubuntulinux.nl/factoids.cgi
[05:09] <tsmithe> !name maybe
[05:09] <bddebian> !name
[05:09] <ubotu> Ubuntu has awesome release codenames. See http://wiki.ubuntu.com/DevelopmentCodeNames for more
[05:09] <xtknight> what if feisty+2 had "Human" in it
[05:09] <xtknight> scary
[05:09] <tsmithe> yep :)
[05:10] <bddebian> Horny Human?
[05:10] <joejaxx> Hopeful Human
[05:10] <xtknight> Hiccuping Human..
[05:10] <joejaxx> Hopeful Humanity
[05:10] <tsmithe> Human Human
[05:10] <xtknight> Homeless Human
[05:10] <danohuiginn> Human Horse?
[05:11] <lupine_85> hairy human!
[05:11] <tsmithe> and anyway, it's going to be I... I...
[05:11] <bddebian> Hopeless Humans
[05:11] <tsmithe> Hoary took I
You send 'em, we'll consider 'em.</quote>
[05:12] <joejaxx> send them where? lol
[05:12] <tsmithe> to the page
[05:12] <tsmithe> mailto:wiki.ubuntu.com/DevelopmentCodeNames
[05:12] <tsmithe> duh!
[05:12] <xtknight> Immune Iguana ? 
[05:12] <Nafallo> gaah
[05:13] <Nafallo> how many releases are you guys planning? :-)
[05:13] <xtknight> what happened to ubuntu 1.00?
[05:13] <tsmithe> there is no month 00
[05:13] <joejaxx> xtknight: it is based on the year and month
[05:13] <tsmithe> nor did ubuntu exist in 2001
[05:13] <xtknight>  ahh
[05:31] <Lutin> hi there
[05:36] <Lutin> I've noticed that wxgtk2.4 was still built using python2.4 instead of python2.5. do you think it's worth updating it and 5-6 packages that depends on it, or do we just let it as it is ?
[05:38] <ScottK> At this point it sounds scary either way to me.
[05:39] <Lutin> ScottK: heh :/
[05:40] <ScottK> I'd tend to leave it if no one has complained/filed bugs.
[05:40] <Lutin> that's what I'd do as well
[05:42] <Hobbsee> heh, crispy calamari
[05:42] <Hobbsee> i'd leave it by now, too
[05:43] <Nafallo> c is a LONG way :-)
[05:48] <Nafallo> :-)
[05:49] <pygi> siretart, there is a pending discussion (AFAIK) of including libburn+cdrskin as part of cdrkit =)
[05:50] <siretart> sound even better. I haven't noticed any discussion about this on debburn-devel, though
[05:50] <pygi> I know :P
[05:51] <pygi> ofcourse libburn+cdrskin would remain upstream to cdrkit
[05:51] <pygi> me & thomas also have a pending petition to LKML for locking issue
[05:52] <siretart> this has debburn-devel cc'ed, so I noticed that thread
[05:52] <pygi> you'll see =)
[05:52] <pygi> the petition is not there yet
[05:53] <siretart> pygi: I'd strongly recommend to have some releasable libburn ready early in the feisty+1 cycle. I think we both agree that we want to ship it in the next release
[05:54] <pygi> siretart, we do already have a releasable libburn? :)
[05:54] <pygi> However we did agree on releasing 0.3.5 over the weekend?
[05:54] <pygi> perhaps I can backport some patches from current svn, and fix the soname
[05:55] <siretart> atm, I'd say no, there isn't a releasable upstream tarball. I don't have a say on you releasing 0.3.5 this weekend, I remember you promised that release weeks ago ;)
[05:55] <pygi> how come there is no releaseable tarball? :P
[05:55] <pygi> what did I miss? :)
[05:55] <pygi> true, true =)
[05:55] <pygi> siretart, but that's why I've got java bindings for libisofs & libburn :P
[05:55] <siretart> the current tarballs has soname 4, and you told me that you want to change that to soname 3 in the next version
[05:56] <pygi> siretart, yup, in .5
[05:56] <pygi> will do that =)
[05:56] <siretart> this makes it a perfect non-candidate for uploading it anywhere
[05:56] <dholbach> why to 3?
[05:56] <pygi> dholbach, 0.3.x
[05:56] <pygi> dholbach, I guess :P
[05:56] <siretart> dholbach: because the bump was an accident and not intended
[05:56] <dholbach> aha
[05:57] <siretart> I could change it locally though, but that would confuse ppl even harder
[05:57] <pygi> dholbach, aka /me not too familiar with autotools :P
[05:57] <dholbach> normally people bump the soname if interfaces break
[05:57] <siretart> and pygi promised me a quick 0.3.5 release very short after the 0.3.4 release
[05:57] <pygi> well, interfaces break all the time :-/
[05:57] <pygi> I can promise stable api only after 1.0
[05:57] <dholbach> and don't go from 4 back to 3 again because it matches the tarball version number
[05:58] <dholbach> but oh well, I can live with that :)
[05:58] <siretart> pygi: err, I think we do miscommunicate here
[05:58] <siretart> pygi: did you change ABI/API from 0.3.4 to 0.3.5?
[05:58] <pygi> siretart, exactly nothing will be changed between 0.3.4 and 0.3.5 except the soname
[05:59] <siretart> and how about 0.3.3 to 0.3.4? has there been any ABI or API breakage?
[05:59] <siretart> or other way round: do we need to ensure that applications need to be recompiled?
[05:59] <pygi> there was 0.3.2 --> 0.3.4 ... probably some, yes
[06:00] <siretart> aha, so you have no choice, and you MUST bump the soname
[06:00] <pygi> nobody used that stuff anyway :P
[06:00] <siretart> sorry, that's no excuse
[06:01] <pygi> I know
[06:01] <siretart> you're a very difficult upstream, you know?
[06:01] <pygi> heh
[06:04] <pygi> siretart, joerg is easier? :)
[06:04] <siretart> which one?
[06:05] <pygi> well, the cdrecord one or any other :p
[06:05] <pygi> But basically I get the point, I should be quiet =)
[06:06] <siretart> being quite doesn't make things easier
[06:06] <siretart> I knew that I should touch any cd-writing tools :/
[06:06] <siretart> that I shouldn't touch, that is
[06:06] <pygi> heh, that bad?
[06:17] <pwnguin> so my LUG had an idea and im not sure where best to bring it up. they were thinking about leaving an ubuntu disc in every dorm room before the freshmen class arrived
[06:25] <ScottK> pwnguin: Probably #ubuntu-marketing
[06:26] <pwnguin> good idea
[06:33] <tsmithe> does debian sync new packages from ubuntu?
[06:37] <tonyyarusso> tsmithe: Sometimes they take bugfixes etc back from Ubuntu, but as I understand it, they have their own new package inclusion process, which is linked to from the Ubuntu Packaging Guide or somewhere - hold on
[06:37] <tsmithe> tonyyarusso, but we auto-sync from them... why can't they sync from us? maybe it would stop some of the complaints of giving back work...
[06:38] <tonyyarusso> tsmithe:  I don't know why they don't - I just don't think they do.
[06:38] <tsmithe> it's silly if they don't
[06:39] <poningru> no wai
[06:39] <ScottK> They are upstream.  We are downstream.  Any Ubuntu specific package is going to have to be modified for Debian.  Sync back up wouldn't work.
[06:39] <poningru> but the purity of debian will be ruined
[06:40] <tsmithe> ScottK, why wouldn't it work?
[06:40] <ScottK> Note that Ubuntu is upstream for a number of distros and doesn't sync from them either.
[06:40] <tsmithe> what if the packager just preferred working for ubuntu, and there's not necessarily anything ubuntu-specific in it
[06:40] <tsmithe> ?
[06:40] <ScottK> MEPIS for one.
[06:41] <ScottK> tsmithe: Debian has rules about who and how to contribute.
[06:41] <tonyyarusso> tsmithe: https://wiki.ubuntu.com/ContributingToDebian?highlight=%28CategoryMOTU%29
[06:41] <tsmithe> yes i know they do
[06:41] <ScottK> There are ways for non-DD to contribute.
[06:41] <ScottK> See mentors.debian.org.
[06:41] <tsmithe> i know that too
[06:41] <tsmithe> it's just silly when they could do it automagically
[06:42] <ScottK> Is it silly that they have an approval process for who can have access to their repositories?
[06:42] <tsmithe> no
[06:42] <tsmithe> is it silly we sync from debian?
[06:42] <tsmithe> no
[06:42] <tsmithe> cos not all DDs are Ubuntu-devs
[06:43] <tsmithe> but, yes, they are upstream, indeed
[06:43] <ScottK> No, but they have a lot broader concerns that Ubuntu does.  Go look at how many archs Debian supports.
[06:43] <tsmithe> true, true
[06:43] <tsmithe> anyhow, i'm going out now - thanks for the answers :)
[06:44] <lupine_85> wow. Launchpad got ugly.
[06:44] <bddebian> Yep :-)
[06:45] <ScottK> Ugly and still slow.  Ugly and fast I'd be good with.
[06:46] <bddebian> heh
[07:01] <Nafallo> anyone know where nvu went? :-)
[07:02] <Adri2000> /dev/null
[07:03] <jdong> Nafallo: </nvu>
[07:03] <ScottK> Nafallo: Abandoned upstream and removed from Debian - this is the why for what Adri2000 said.
[07:03] <Nafallo> ah, thanks :-)
[07:29] <tonyyarusso> !nvu | Nafallo, jdong, ScottK 
[07:29] <ubotu> Nafallo, jdong, ScottK: nvu is a WYSIWYG and code dual-function HTML editor for easily creating web pages.  The original developer is working on a full rewrite; meanwhile, another is doing bugfixes.  It is not the Ubuntu repos for Feisty Fawn, but ping tonyyarusso to inquire about packages.  See also !html.
[07:29] <jdong> :)
[07:30] <tonyyarusso> There will be packages of nvu built, either under the Nvu or KompoZer names.
[07:30] <Nafallo> :-)
[07:30] <Nafallo> KompoZer? KDE?
[07:31] <tonyyarusso> Nafallo: Nope, just a play on "Composer"
[07:31] <Nafallo> :-)
[07:31] <jdong>  Nafallo: no, that's for ZDE... which is an abstraction over many desktop environments....
[07:31] <jdong> also known as KDE5
[07:32] <Nafallo> *shrugs*
[07:49] <tonyyarusso> Ahem, I am hereby making noise about bug 105614 - any ideas?
[07:49] <ubotu> Malone bug 105614 in Ubuntu "[feisty]  Flash site only partially loads" [Undecided,Unconfirmed]  https://launchpad.net/bugs/105614
[07:50] <ScottK> tonyyarusso: Don't use Flash because it's evil?
[07:51] <tonyyarusso> ScottK: Not my web site.  Given the choice, I agree :)
[07:51] <Nafallo> tonyyarusso: webmaster@... ;-)
[07:52] <tonyyarusso> Nafallo: I can't browse the site to find a contact link if one exists...
[07:52] <ScottK> tonyyarusso: Just send to webmaster@ the domain.  It should, in theory, work (RFC something or other).
[07:53] <tonyyarusso> probably
[07:53] <Nafallo> if it doesn't DDOS THEM!
[07:53] <Nafallo> ;-)
[07:53] <tonyyarusso> anyone want to check out http://www.specialized.com/ and see if it has a nice contact thingy?
[07:53] <tonyyarusso> Meanwhile, someone fix my issue in Ubuntu :P
[08:00] <DarkSun88> Any universe sponsor?
[08:04] <dholbach> DarkSun88: https://wiki.ubuntu.com/SponsorshipProcess
[08:05] <ScottK> tonyyarusso: Couldn't find one.
[08:07] <DarkSun88> dholbach: Thank you.
[08:07] <dholbach> np
[08:07] <DarkSun88> dholbach: Can you so kind to check this bug? https://bugs.launchpad.net/ubuntu/+source/libphp-phplayersmenu/+bug/96376
[08:07] <ubotu> Malone bug 96376 in libphp-phplayersmenu "[UNMETDEPS]  libphp-phplayersmenu has unmet dependencies" [Undecided,Confirmed]  
[08:08] <dholbach> i'd prefer if you'd ask somebody else - I'm testing release candidate CDs and looking into fixing a bug
[08:09] <DarkSun88> Ah ok, thanks
[08:10] <Joe_CoT> get-orig-source rule for debian/rules. Anyone done it before?
[08:19] <tonyyarusso> ScottK: 'k
[08:29] <danohuiginn> DarkSun88: do you know that the package works OK with php5?
[08:31] <DarkSun88> danohuiginn: I check the packages and are ok
[08:49] <xtknight> why was this bug closed?  bug 105263
[08:49] <ubotu> Malone bug 105263 in kvm "[feisty]  kvm depends of kvm-api-9 but that package is uninstallable" [Undecided,In progress]  https://launchpad.net/bugs/105263
[08:49] <xtknight> the last comment doesnt even make any sense
[08:50] <xtknight> never mind, guess my email hadnt been updated
[08:50] <xtknight> they marked it open again
[08:51] <cypherbios> hi all
[08:51] <cypherbios> Someone could tell me if is the Universe in freeze right now?
[08:51] <xtknight> tomorrow
[08:53] <cypherbios> Is it described somewhere?
[08:54] <cypherbios> https://wiki.ubuntu.com/FeistyReleaseSchedule >> There is no mention here, I guess
[08:54] <xtknight> not sure that's what i've heard
[08:54] <xtknight> !\ ReleaseCandidate, /!\ LanguagePackTranslationDeadline 
[08:54] <xtknight> i think it's the same day as that
[08:55] <cypherbios> and after the RC, will universe still in freeze until the Final Release?
[08:55] <Adri2000> yes
[08:55] <gnomefreak> universe freeze was a while ago i thought
[08:56] <Adri2000> UVF and FF yes
[08:56] <Adri2000> RC freeze is tomorrow
[08:56] <gnomefreak> ~1 month or so ago
[08:56] <gnomefreak> yep
[08:56] <gnomefreak> no
[08:57] <gnomefreak> we have been frozen for rc for a week now since 6 was cancelled
[08:57] <cypherbios> so nobody (with common permission) can upload anything to universe right now?
[08:57] <gnomefreak> cypherbios: needs a manual push once uploaded
[08:57] <xtknight> hm well i know some fixes were uploaded to universe just yesterday
[08:57] <xtknight> ahh
[08:59] <cypherbios> Seems I need to file a bug https://launchpad.net/~motu-uvf/+assignedbugs is it correct?
[08:59] <Adri2000> cypherbios: you want a new upstream version?
[09:01] <cypherbios> Adri2000: is from a 0.1-RC-0ubuntu1 to 0.1-0ubuntu1
[09:01] <pygi> mvo, I could use you at #duplicate-resolution at slashnet. LH needs a word with you (or any mentor for that purpose)
[09:01] <Adri2000> cypher1: too late
[09:02] <Adri2000> sorry, cypherbios ^
[09:02] <mvo> pygi: ok - timing is not ideal, I'm in the middle of heavy testing
[09:02] <mvo> pygi: slashnet.net? 
[09:02] <pygi> mvo, yup
[09:03] <pygi> mvo, ergh , .org
[09:03] <pygi> mvo, well, I can't catch any other mentor
[09:04] <giskard> hi pygi 
[09:04] <pygi> giskard!!
[09:04] <cypherbios> Adri2000: and if it was just a 0ubuntu1 to 0ubuntu2?
[09:05] <Adri2000> not too late until tomorrow
[09:05] <cypherbios> some important bug fixes have been made in this package/application that must be on universe until the final release
[09:40] <geser> cypherbios: which package is it?
[09:40] <cypherbios> geser: aptoncd is the package
[09:41] <geser> how big is the diff?
[09:43] <cypherbios> geser: since the last upload... not so much, but the fixes it incorporates and translations updates (~10 complete languages since the last upload) I consider important to ubuntu users get with the Feisty's final release
[09:44] <cypherbios> geser: I'm talking with mvo right now, who will sponsor the upload if allowed
[09:44] <pygi> mr_pouit, poke
[09:45] <mr_pouit> pygi: yes?
[09:45] <pygi> mr_pouit, I'll need you for the weekend, will you be available? We need to draft the plan of tackling the cdrecording issues
[09:45] <pygi> mr_pouit, plan is to get rid of 75% of bugs by october
[09:46] <mr_pouit> pygi: I think I'll ba available
[09:46] <mr_pouit> be*
[09:47] <pygi> mr_pouit, that's great =) We'll need to see what can be reproduced, what can't, close bugs, and write patches
[09:47] <pygi> I estimate 90% of current cdrecord bugs will be closed by one package upload :)
[09:47] <pygi> guess which one :P
[09:47] <mr_pouit> ;p
[09:47] <mr_pouit> I've done this for brasero only at the moment :] 
[09:48] <pygi> you've done what? :P
[09:48] <pygi> brasero supports new libburn so it has no bugs =)
[09:48] <pygi> well, svn version at least :P
[09:48] <mr_pouit> pygi: reproducing/forwarding bugs ^^
[09:49] <pygi> ah!
[09:49] <pygi> right =)
[09:49] <mr_pouit> that's too late for feisty though... =)
[09:49] <pygi> well, feisty+1 :)
[09:49] <pygi> patience ;)
[09:50] <mr_pouit> ^^
[09:59] <cypherbios> geser: any chance?
[10:06] <ajmitch> morning
[10:06] <ScottK> Morning.
[10:07] <ScottK> Got backups?
[10:07] <ajmitch> not really
[10:07] <ajmitch> it takes a bit to backup a few hundred GB
[10:08] <ScottK> This does not sound like the road to happiness...
[10:08] <ajmitch> no
[10:08] <ajmitch> true, the most important stuff is on RAID 5
[10:08] <ajmitch> but that'll only survive 1 disk failing
[10:08] <ajmitch> (out of 3 that I have)
[10:09] <pygi> ajmitch, use libburn =)
[10:11] <ajmitch> pygi: no thanks
[10:11] <pygi> ehm, ...
[10:13] <ScottK> ajmitch: http://ars.userfriendly.org/cartoons/?id=20070411
[10:14] <ajmitch> haha
[10:14] <ScottK> ajmitch: Also, the MOTU/Python team wiki says to contact you to join.  I'm interested in joining.
[10:14] <ajmitch> ScottK: ok, I dub thee as a member, congrats
[10:14] <ajmitch> that's it ;)
[10:14] <ScottK> OK.  I guess I get to add myself to the wiki then...
[10:14] <ajmitch> there's no real team
[10:15] <crimsun> pfft, I'd have expected some sort of hazing at least
[10:15] <ajmitch> especially as everyone works on python stuff anyway
[10:15] <ajmitch> crimsun: if you want to do the honours?
[10:15] <crimsun> I don't think a non-member is supposed to do the hazing ;)
[10:15] <ajmitch> crimsun: I dub thee as an honourary member, not get hazing
[10:16] <ajmitch> s/not/now/
[10:16] <crimsun> :)
[10:16] <crimsun> let me just conjure hobbsee and her stick
[10:16] <ajmitch> she's hopefully asleep
[10:24] <ajmitch> nice, 500GB drives at a reasonable price
[10:24] <ScottK> ajmitch: What brand?
[10:24] <ajmitch> samsung
[10:25] <ScottK> I always warn away from Western Digital (dunno if you get those there).  Every hard drive I've had fail in normal use was a Western Digital.
[10:25] <ajmitch> yep
[10:25] <ajmitch> I've probably got a small stack of dead WD drives :)
[10:26] <ajmitch> last hard drive I had die (160GB) was WD
[10:33] <welp> what version control system does ubuntu use?
[10:33] <geser> bzr
[10:33] <pygi> bzr
[10:33] <pygi> :)
[10:33] <welp> 'k
[10:34] <Nafallo> bazaar
[10:34] <Nafallo> :-)
[10:34] <welp> hmm, ubuntu's weird... not keeping stats on cia
[10:34] <welp> :P
[10:36] <welp> do you actually keep stats anywhere?
[10:37] <phanatic> welp: launchpad
[10:38] <welp> hmmmmmmmmk
[10:38] <welp> sacater: i expect to see you on the top contributors page one day.
[10:52] <ajmitch> hm, I can probably safely remove stuff now, like the hoary chroot 
[10:53] <sacater> welp: i expect you will
[10:53] <ajmitch> which I used when I was running sid
[10:53] <bddebian> no way man..
[10:53] <sacater> welp: im going for membership first
[10:53] <ScottK> When is end of support for Breezy?  There are a couple of bugs I'm waiting to close...
[10:53] <welp> bddebian: no way man at what? sacater in the top contributors on launchpad? :P
[10:54] <ajmitch> ScottK: a few days, I expect
[10:54] <bddebian> welp: No, that was for ajmitch removing his hoary chroot 
[10:55] <ajmitch> ScottK: april 13th :)
[10:55] <ScottK> Of course.
[10:55] <ajmitch> so Real Soon Now
[10:55] <sacater> welp: i am?
[10:55] <sacater> welp: link me?
[10:55] <sacater> oh
[10:55] <sacater> i heareby do accept this great honour etc etc
[10:55] <sacater> :P
[10:56] <welp> sacater: no you're nto
[10:56] <crimsun> visibility is a good thing.
[10:56] <sacater> hmm
[10:56] <welp> *not
[10:56] <sacater> what where who>?
[10:56] <sacater> why the link welp?
[10:56] <bddebian> ajmitch: You are the top contributor honey :-)
[10:56] <ajmitch> bddebian: no, I don't think I'm on that page
[10:56] <crimsun> I'm not in the top contributors, and that's ok!
[10:56] <welp> sacater: i'm one of todays top committers :P
[10:57] <welp> sacater: take a look at the "most active authors today" section
[10:57] <sacater> welp: oh, so it does pick me up then
[10:58] <welp> sacater: it doesn't pick up on you as it doesn't watch ubuntu stuff
[10:58] <sacater> oh
[10:58] <sacater> then what was all that about top contributors?
[11:00] <ajmitch> hey stratus 
[11:00] <stratus> ajmitch: howdy?
[11:01] <ajmitch> how's it going?
[11:01] <stratus> really weird week
[11:01] <welp> sacater: *sigh* https://launchpad.net/ubuntu/+topcontributors
[11:02] <sacater> welp: i cant see my name?
[11:02] <welp> no you can't
[11:02] <jmg> hey my karma got reset to 0
[11:02] <welp> i never said i could
[11:02] <welp> poor jmg 
[11:02] <jmg> *sniff*
[11:03] <zorglu_> this page doesnt seems to load on konqueror
[11:04] <zorglu_> oh now it does, just take more than 30sexc
[11:04] <sacater> welp: how does karma work in gentoo land?
[11:04] <welp> it doesn't
[11:04] <welp> :P
[11:04] <sacater> oh
[11:04] <sacater> ive got 1417
[11:05] <sacater> or more
[11:05] <sacater> methinks
[11:05] <zorglu_> i read the blog of alan pope and his 'secret' is to answer a lot of question in the forum :)
[11:06] <sacater> thats true
[11:06] <sacater> and i d
[11:06] <sacater> do*
[11:06] <sacater> got 1000 karma in less than a week
[11:07] <sacater> eh
[11:07] <sacater> is that welp or someone else
[11:07] <sacater> messing with teh welp!
[11:07] <ThEmAsTeRhUgGeR> 'tis moi :o
[11:07] <sacater> why change name
[11:09] <sinisterguy> i'm having a problem with the python-parallel package, when i try to use it, it complains that /dev/parport0 does not exist, but when i modprobe parport, not parport device is created
[11:09] <welp> sacater: because i'm totally cool and random
[11:11] <sacater> im gonna get some Q+A karma
[11:11] <welp> do you know what QA means?
[11:17] <sacater> hmm
[11:51] <Seveas> welp, Q+A isn't QA
[11:52] <welp> what Q+A are you referring to?
[11:52] <welp> i'm thinking of quality assurance
[11:52] <bddebian> Q+A == Question and Answer
[11:52] <welp> aaaah, ok
[11:53] <Seveas> :)