[12:46] <kylem> shit.
[01:02] <ajmitch> oh, another willing victom for the xen team?
[01:06] <infinity> "victom"? :)
[01:07] <ajmitch> I just got back from lunch.. I'm not normally *that* sloppy :)
[01:28] <ajmitch> infinity: can a package build be given back for a single arch?
[01:29] <infinity> Of course.
[01:29] <infinity> Which'un?
[01:29] <ajmitch> libofx, and then gnucash once it's published
[01:29] <ajmitch> seeing errors like 'no space left on device' in build logs is fun
[01:30] <infinity> Fun for me too...
[01:30] <infinity> Which host?
[01:30] <ajmitch> ross
[01:30] <infinity> Ngh.
[01:30] <ajmitch> build log is from 2 weeks ago
[01:30] <infinity> Oh, I may well have fixed that, then.
[01:45] <zul> damn you peekvid sucking up so much of my time
[03:39] <kylem> motherfucker.
[04:37] <kylem> ok, got all the CVEs now...
[12:58] <gnomefreak> ebnyou around. i have a question about the -6 kernel in feisty. i have someone getting bios errors and pci errors and kernel fails to boot with them.
[12:59] <gnomefreak> ack
[12:59] <gnomefreak> BenC: that was for you
[12:59] <fabbione> file a bug in launchpad with details
[12:59] <fabbione> details are NOT optional
[12:59] <gnomefreak> lol
[12:59] <fabbione> and we have been down this road already once
[01:00] <gnomefreak> yes i know but he doesnt have much details
[01:00] <gnomefreak> thats why i didnt send him there yet. he gave me a couple of lines of output
[01:00] <fabbione> and what does make you think that we can even guess those 2 lines?
[01:02] <gnomefreak> ##### PCI: BIOS BUG: MCFG AREA AT E00000 IS NOT 6820-RESERVED ##### PCI: NOT USING MMCONFIG ###### DRIVERS/USB/INPUT/HID-CORE.C:V2.6:USB HID CORE DRIVER
[01:02] <gnomefreak> those are exact to what he gave me
[01:02] <fabbione> BIOS BUG: <- tell him to upgrade his bios
[01:02] <gnomefreak> im hoping bios bug doesnt mean that
[01:03] <gnomefreak> he didnt wait around :(
[01:03] <gnomefreak> he said hed file a bug so ill let him know if i see him
[01:04] <mjg59> gnomefreak: Those messages are harmless
[01:04] <gnomefreak> thats all he said he was getting
[01:05] <gnomefreak> i believe he said he was on a realtek (mobo im assuming)
[01:06] <mjg59> As I said, those messages are harmless. Disabling mmconfig isn't going to cause problems.
[02:01] <mjg59> Is there any way for a userspace application to get a notification when a hardware interrupt is fired?
[02:29] <kylem> yes.
[02:32] <mjg59> kylem: How?
[02:35] <kylem> the canonical way would be to have it block on a read of a device node until the interrupt hits.
[02:36] <kylem> assuming i get what you mean... you might be able to send a signal if you know the tasks pid too.
[02:37] <mjg59> Oh
[02:38] <mjg59> No, I want a userspace app to be woken up when a specific hardware interrupt is fired
[02:38] <mjg59> Like select, but a mask of IRQs rather than fds
[02:38] <kylem> oh. gross.
[02:39] <kylem> pity you can't inotify on /proc/interrupts... ;-)
[02:39] <mjg59> Polling /proc/interrupts is presumably fairly lightweight
[03:07] <zul_> hey
[04:04] <zul> er...why cant i clone ubuntu-edgy-updates
[07:02] <pitti> hi guys
[07:03] <pitti> BenC, zul, kylem: ping
[07:03] <BenC> pitti: pong
[07:03] <zul> pitti: pong
[07:03] <keescook> mornin'
[07:03] <zul> hey keescook 
[07:04] <keescook> hi zul :)
[07:04] <pitti> BenC: With kylem onboard, do you have new assignees for stable kernel updates?
[07:04] <BenC> pitti: it's zul->breezy, kylem->dapper, me->edgy
[07:04] <pitti> we have a couple of pending issues, including the one I mailed you about yesterday
[07:05] <pitti> so I'd like to have a new batch rolled out next week, if that's possible
[07:05] <zul> is the kernel-sec svn updated?
[07:05] <pitti> BenC: ah, great
[07:05] <pitti> zul: svn contains everything I know about that has patches available
[07:05] <zul> ok cool
[07:05] <pitti> there are some more recent CVEs, but unpatched
[07:06] <pitti> (mostly from the 'Month of kernel bugs', the fs fuzzer)
[07:06] <pitti> zul, BenC: you should have gotten one more issue in you mailbox; I still need to send it to kylem
[07:06] <pitti> (I can't put that into the svn yet)
[07:07] <zul> when did you send it
[07:07] <pitti> yesterday
[07:07] <BenC> I got it
[07:08] <pitti> BenC: bah, I didn't encrypt it to myself; can you please forward it to Kyle?
[07:08] <zul> what was the subject? i might have missed it
[07:09] <zul> okie dokie
[07:10] <zul> so when next week?
[07:11] <BenC> shows how much I use pgp encrypt
[07:11] <BenC> what's the lp keyserver?
[07:11] <Mithrandir> BenC: keyserver.ubuntu.com, iirc
[07:11] <keescook> Mithrandir: yup.
[07:12] <pitti> not before Tuesday
[07:12] <pitti> I'd target Wed or Thu
[07:12] <BenC> hkp:// or ldap://?
[07:12] <zul> ok thats fine with me
[07:22] <BenC> pitti: evo isn't cooperating with me for doing an encrypted email
[07:23] <pitti> BenC: ok, nevermind; I'll forward it to him
[07:23] <zul> pitti: got it will be included
[07:23] <zul> BenC: maybe you should use console ;)
[07:27] <zul> nice xen 3.0.4 in december
[07:27] <BenC> stupid stupid stupid
[07:27] <zul> hehe
[07:31] <pitti> BenC: I mailed Kyle
[07:40] <kylem> is this the embargoed one? (haven't checked email yet)
[07:46] <pitti> hi kylem 
[07:47] <pitti> kylem: yes, I sent you mail about it
[07:47] <kylem> ok.
[07:47] <kylem> i assume i shouldn't put a fix into my git tree until tuesday then?
[07:47] <pitti> kylem: right
[07:48] <pitti> kylem: if you need to git commit before preparing the package, then please do it on Tuesday as the last patch
[07:48] <kylem> ok.
[07:49] <kylem> someone else will need to upload until i get approved for core-dev, it should be ready to upload on tuesday as soon as the embargo is lifted.
[07:49] <pitti> kylem: are you an ubuntu-dev?
[07:50] <zul> i doubt he is
[07:51] <kylem> pitti, nope.
[07:51] <pitti> kylem: ok, I can do the upload for you, if you can put it on chinstrap?
[07:52] <kylem> ok.
[07:53] <kylem> i'll add @canonical.com to my gpg key.
[08:05] <kylem> ok, i've already got everything from kernel-sec in dapper.
[08:17] <kylem> BenC, i can probably take care of edgy security too, if you want
[08:48] <BenC> kylem: Sure, that'd be great...mainly you should be able to just pull from dapper (that's what I've been doing)
[09:02] <juliux> evening, does somebody know why wlanconfig, for madwifi is not in edgy?
[09:03] <siretart> juliux: it is in a package called 'madwifi-tools', in universe, IIRC
[09:03] <juliux> siretart, not in edgy:(
[09:03] <juliux> siretart, in june was madwifi_new released
[09:04] <pitti> madwifi-tools | 1:0.9.2+dfsg-1 | http://de.archive.ubuntu.com feisty/universe Packages
[09:04] <pitti> madwifi-tools | 1:0.9.2+dfsg-1 | http://de.archive.ubuntu.com feisty/universe Sources
[09:04] <pitti> so maybe that was too late for edgy?
[09:04] <siretart> woah. that's really sad
[09:04] <juliux> 27.6 was to late??
[09:04] <juliux> that was the release of madwifi 0.9.2
[09:04] <mjg59> The release date is irrelevant
[09:05] <juliux> there is also the madwifi-ng modules in edgy but not the tools
[09:05] <mjg59> Most of the developers don't use madwifi, let alone ad-hoc mode
[09:05] <mjg59> So the absence wasn't noted
[09:05] <siretart> hm. can we get madwifi-tools into edgy-updates?
[09:05] <siretart> or at least edgy-backports. but -updates would be nicer..
[09:06] <pitti> siretart: no, not -updates
[09:07] <siretart> hm. -backports then..
[09:08] <juliux> https://launchpad.net/distros/ubuntu/+source/linux-restricted-modules-2.6.15/+bug/53489 there is a bugreport about this