[01:34] <dg6e74> can someone point me to the correct channel where i can get help with kubuntu networking
[01:39] <infinity> dg6e74: I would assume either #kubuntu or #ubuntu
[01:54] <BenC> infinity: 4.4 seems to be chugging along
[02:39] <srwalter> so what's the story on bug https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.17/+bug/63134
[02:45] <BenC> srwalter: It will be addressed on the first -proposed kernel upload I do
[02:45] <BenC> but with feisty opening, and UDS next week, it wont be any time soon
[02:46] <srwalter> that's encouraging
[02:46] <srwalter> I may as well poke you about https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/57625 while I have your attention
[02:57] <BenC> infinity: yay, sparc and ppc built
[02:58] <BenC> srwalter: I'm more likely to update to the latest atmel driver than accept that patch
[02:58] <BenC> srwalter: Latest driver uses correct firmware loading and seems to better support current kernels
[02:59] <srwalter> that solves the bug just as well as my patch
[03:00] <BenC> srwalter: feisty has latest atmel in 2.6.19 if you want to test it
[03:00] <BenC> I can just backport from feisty
[03:01] <srwalter> sounds good
[03:06] <infinity> BenC: I saw.  Thanks. :)
[03:06] <BenC> I'm just waiting got i386 to fail to spite me
[03:07] <infinity> Seems unlikely.
[03:07] <BenC> infinity: I wont hide it either, I added "sparc64" to prefix the make-kpkg commands to fix sparc
[03:07] <infinity> Anyhow, even if it does, it doesn't matter for the toolchain bootstrap, since we already have a linux-libc-dev from 2.6.19 on i386.
[03:07] <BenC> I'll figure it out later when you guys aren't blocking on me
[03:07] <infinity> BenC: Yeah, I saw the fix. :)
[03:07] <infinity> BenC: Better a dirty hack than being blocked so, yes, thanks again. :)
[03:08] <BenC> one week into feisty, and I'm already at abi 4 :)
[03:11] <infinity> Should have been using a magic 0.X scheme for "effin' broken ABI, don't count on it working" or something. :)
[03:12] <infinity> (Still could, since nothing yet depends on the ABI)
[03:12] <infinity> Then you could go back to 1, 2, 3, 4 again later. :)
[03:12] <BenC> yeah, would require logic changes all in the build setup though
[03:13] <BenC> I've already had to close two bug reports on 2.6.19 because people expect it to work every already, even though it's known that a lot of external modules are still missing
[03:13] <infinity> Yeah, s'pose so.  Though using 0.X for test kernels would mean that we wouldn't have to shove every new kernel upload through NEW. :)
[03:13] <BenC> good point
[03:14] <infinity> Something to think about for feisty+1's kernel, perhaps.
[03:14] <BenC> I'm tracking ABI now, since we'll have built ABI files on all arches this time
[03:14] <BenC> the mad-patch-rush in 2.6.19 git is over, so there wont be huge sweeping changes
[03:15] <infinity> Excellent.
[03:15] <infinity> Alright, I'm off to run some pre-UDS errands.
[03:15] <infinity> Have about 5 days of "real life" and another 5 days of ork to attend to in the next... 2.5 days.  Should prove interesting.
[03:15] <infinity> s/ork/work/
[04:44] <test> where can I get 2.6.19? I want to use it for bootstrapping mondoarchive . Mondo archive is a backup my workstation to dvd or other media.
[04:48] <BenC> test: It's in feisty, but I wouldn't suggest using it
[04:49] <test> let me tell you the deal here. I'm on a deadline delivering 1500+ ubuntu desktop pc's.
[04:50] <test> I'm in the final stages, which is creating a recovery cd. 2.6.17 generic is crashing on my via chipsets
[04:51] <test> so I used the workarround to boot it, however, when mondoarchive is creating the filesystems and is about to recover the data the kernel says the machine runs out of mem.
[04:52] <test> this 2.6.17 generic just doesn't feel right with this via chipset. 
[04:52] <crimsun> does 2.6.15 not work?
[04:52] <test> 2.6.15 is not availble in edgy repositorys as far as i know.
[04:52] <crimsun> right, I mean "using Dapper"
[04:53] <crimsun> if you're rolling out 1500+ desktops, I'd think that an LTS release is the more likely choice
[04:54] <test> we use software that only works correct on edgy, for example the oem-config-prepare and some systems contain sis chipsets, and the 2.6.15 doesn't work with the sis audo chipset.
[04:54] <test> so I'm stuck with 2.6.17.
[04:54] <crimsun> audo or audio?
[04:54] <test> audio
[04:54] <crimsun> what in particular?
[04:54] <crimsun> dapper and edgy have nearly identical alsa
[04:55] <crimsun> there are only a handful of differences (across isa and older pci drivers)
[04:55] <crimsun> (don't pay any attention to the alsa version string)
[04:55] <test> sis964 if i'm not mistaking
[04:56] <test> hmm. let me see what the 2.6.15 can achieve
[04:58] <BenC> I have to agree with crimsun...rolling out that many, I suspect you want dapper
[04:59] <test> re-installing and re-configuring everything, is going to take to much time... 
[05:19] <test> about te toest 2.6.15-27-6868
[07:05] <hughsie> BenC: why is 2.6.19rc4 only useful for bootstrapping?
[07:05] <hughsie> I want to do some OLPC work...
[07:06] <fabbione> hughsie: totally untested, not finished, missing a lot of stuff from edgy
[07:06] <mjg59_> It's there so we can bootstrap glibc and so on
[07:06] <hughsie> fabbione: you mean it might boot, but my wireless wont work, or it just wont boot?
[07:06] <mjg59_> Once they're sorted, we'll be looking at doing a proper upload
[07:06] <fabbione> without which we can't do what mjg59_ wrote and open feisty
[07:06] <mjg59_> Ought to boot. Ought to support a compilation environment. Beyond that, you're on your own
[07:07] <hughsie> mjg59_: ahh, gotcha
[07:07] <fabbione> hughsie: it might eat your data, it might boot and work wonderful.. you are on your own
[07:07] <hughsie> when is feisty going to see some kernel upload lovin'?
[07:07] <hughsie> days/weeks?
[07:08] <hughsie> i.e. do i go compile my own kernel.org kernel.... :-)
[07:08] <fabbione> we usually delay 2 weeks each time somebody come here and ask
[07:08] <fabbione> so we are about at mid January now
[07:08] <zul> lol
[07:08] <hughsie> fabbione: lol, thanks. :-)
[07:08] <fabbione> hughsie: when we are ready there will be a kernel
[07:08] <fabbione> and it will become the default automatically
[07:09] <hughsie> fabbione: that's what my mother used to say, well, replace kernel with "cake"
[07:09] <fabbione> (assuming you are upgrading from edgy and you have the meta packages installed)
[07:09] <hughsie> sure, i'm guessing feisty is pretty empty now
[07:09] <fabbione> food time
[07:09] <hughsie> but the kernel in edgy is just too old to work with the olpc patches
[07:10] <hughsie> i might have to fire up fedora.... :-)
[10:04] <pitti> Hi
[10:05] <pitti> zul, BenC: do you have time for another kernel security update?