[02:36] <lamont> so when I run kvm -cdrom foo.iso, can I change foo.iso to a different iso without rebooting?
[02:43] <stgraber> lamont: yes, you need to use the qemu console for that, use ctrl+alt+2 to access the console ctrl+alt+1 to go back to the VM
[02:43] <stgraber> you can then eject and mount a new CD (don't remember the syntax but there is help included IIRC)
[02:45] <lamont> cool
[02:46] <lamont> and if the machine has never been defined in qemu, I can still talk to it (kvm cli instance) with the qemu console?
[02:48] <stgraber> yeah, kvm is using qemu so the ctrl+alt+X shortcuts should work (even with the other frontends like VNC)
[02:55] <lamont> coolness
[14:44] <CarlFK> I am trying to track down a memory leak.  the memory does not get freed when I exit the app.  someone suggested I look at /proc/meminfo
[14:45] <CarlFK> is there a tool that will show me those on a graph so I can look for deltas?
[14:47] <amitk> CarlFK: something like slabtop?
[14:48] <amitk> assuming you are looking at a kernel mem leak
[14:51] <CarlFK> amitk: not what I was hoping for (a graph) but I am open to suggestions - looking at ﻿slabtop
[14:54] <amitk> CarlFK: another one to look at might be sysstat
[14:54] <CarlFK> isag - Interactive System Activity Grapher for sysstat
[14:54] <CarlFK> that sounds like what I want 
[15:01] <CarlFK> amitk: um... how do I run sysstat?  "sysstat is already the newest version; -bash: sysstat: command not found; $ man sysstat; No manual entry for sysstat
[15:02] <_ruben> sysstat package has iostat and some other tools
[15:02] <CarlFK> ah - got it
[15:04] <rtg> mjg59: Does 'Input: atkbd - expand Latitude's force release quirk to other Dells' seem like a candidate for 2.6.27.y ?
[15:09] <mjg59> I don't see why not
[15:17] <BenC> rtg: is that related to eject key hang?
[15:17] <rtg> BenC: thats what I'm thinking.
[15:17] <BenC> rtg: definitely sounds like it
[15:18] <BenC> rtg: too bad my latitude doesn't have a cdrom or I would test that theory
[15:18] <rtg> BenC: I don't have the equipment back yet to test with, but shold by weeks end
[15:18] <mjg59> It is, yeah
[15:18] <mjg59> Since there's a keyboard grab for the eject key and it doesn't get released until the key gets released
[15:18] <BenC> good deal then
[15:19] <mjg59> Which it never does
[16:41] <asac> rtg: there?
[16:41] <rtg> asac: yep
[16:41] <asac> rtg: do you have an ipw 50XX chipset somewhere?
[16:41] <asac> apparently the thing that came after 4965
[16:42] <rtg> asac: Shirley Peak, iwlwifi  5K
[16:43] <rtg> asac: I have 2 of those
[16:47] <asac> rtg: are those identical?
[16:49] <rtg> asac: Model 512_AN, and Model 533_AN. don't know the differences between them since they are too big to fit any PCIe slots that I have.
[16:49] <asac> rtg: oh so you cannot test them?
[16:51] <rtg> asac: not easily.
[17:04] <asac> rtg: so. do you have any chipset at hand that doesnt connect with WPA in intrepid ;)?
[17:04] <asac> (and that connects properly with wpasupplicant manually)
[17:05] <rtg> asac: do you mean with a simple Open AP?
[17:05] <asac> no with WPA
[17:05] <asac> there are a bunch of regressions with iwl ... and other drivers
[17:05] <rtg> asac: oh, you are asking if there are any drivers that _fail_ to connect with WPA, right?
[17:05] <asac> rtg: and at best such chipsets that still work with wpasupplicant manually
[17:06] <rtg> I use iwl4965 and ath5k every day, connecting to a WPA/PSK/TKIP AP. I never have problems.
[17:06] <asac> rtg: with NM?
[17:07] <rtg> asac: always. in fact. I've never use wpa_supplicant manually.
[17:07] <asac> rtg: i think the biggest prob is the IPW 50XX chipset ... i have reports that that doesnt even work with PSK
[17:07] <asac> but works with supplicant alone
[17:07] <asac> all others have issues with enterprise network
[17:07] <rtg> stock 2.6.27, or LBM?
[17:07] <asac> only some users report that its just slow
[17:07] <asac> rtg: thats all stock i think.
[17:08] <rtg> asac: I'm not surprised that there are issues with the stock kernel. The wireless release was totally flubbed.
[17:09] <asac> rtg: maybe you have a setup where connecting with NM takes a bit longer than one want?
[17:09] <rtg> asac: 1-2 seconds, about what I'd expect.
[17:09] <asac> rtg: so how can we ensure better in future
[17:09] <asac> ?
[17:09] <asac> is there anyway to better deal with such "flubbed" wireless releases on our side
[17:09] <asac> ?
[17:10] <rtg> asac: since we aren't upstream developers for wireless, we pretty much get what we're given.
[17:12] <asac> rtg: who is upstream for iwl? just those intelliwireless folks?
[17:12] <rtg> asac: yep - I think we'll meet some of them at UDS.
[17:13] <asac> and who maintains the wireless stack in vanilla kernel?
[17:13] <rtg> linville and crew
[17:13] <asac> i mean most likely someone pulls in stuff from those intelli folks
[17:13] <asac> ok
[17:13] <asac> so redhat ;)
[17:13] <asac> or is that wrong?
[17:14] <rtg> I think John Linville is pretty distro agnostic.
[17:14] <asac> ok. thought he had a redhat address
[17:14] <asac> rtg: and atheros is done by atheros in-house and then pushed over the wall?
[17:16] <rtg> All of these wireless drivers are developed in the open using Linville as the maintainer. Subscribe to linux-wireless@vger.kernel.org
[17:17] <asac> ok thanks
[18:29] <NCommander> hey amitk & lamont 
[18:31] <lamont> morning
[18:32] <NCommander> how goes it lamont?
[18:32] <rtg> lamont: I'm getting complaints that LBM didn't fix the b44 problem.
[18:33] <lamont> rtg: last I looked it wasn't in the archive (as I saw it)... where should I go grab it from
[18:33] <lamont> ?
[18:33] <rtg> checking...
[18:34] <rtg> https://edge.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.27/2.6.27-7.5
[18:34] <rtg> lamont: does it need further stroking? Its marked DONE
[18:42] <NCommander> rtg, hi
[18:42] <lamont> rtg: no, it means I need to add intrepid-proposed to my list
[18:45] <rtg> lamont: doh :)
[18:46] <rtg> NCommander: need something?
[18:46] <NCommander> rtg, I'm trying to figure out who knows what I need to do to get a ports kernel release (and to get my branch blessed as the next offical tree). I have someone willing to sponsor to upload once the kernel team says its ok
[18:47] <rtg> smb_tp is the guy
[18:47] <smb_tp> huh?
[18:49] <smb_tp> NCommander, Ah sure. If you have updates, post a message to the kernel-team mailing list, stating where to get (ideally pull) the changes from
[18:50] <NCommander> smb_tp, I have a 2.6.27.4 tree, but its not based off the old tree (git rebase was never meant to go four releases, so I had to start from linus branch and cherry pick)
[18:50] <smb_tp> NCommander, are you working on a specific architecture?
[18:50] <NCommander> smb_tp, all of them, but PowerPC is my priority
[18:50] <NCommander> Its been test built on all architectures
[18:50] <NCommander> ANd smoke tested on x86 and powerpc. I'm looking for people to smoke test them on sparc, ia64, and hppa (qemu-system-sparc doesn't like my laptop, and I can't find a good ia64 or hppa emulator)
[18:51] <smb_tp> NCommander, I guess munkfish would have to be involved a bit (since he did a lot up to now)
[18:52] <NCommander> smb_tp, he already has been involved :-)
[18:53] <smb_tp> NCommander, Cool :) ia64 is a bit of a trouble. I only got access to a porter machine, so I can compile but not run a kernel
[18:53] <NCommander> smb_tp, yeah, same problem here
[18:53] <NCommander> smb_tp, but I did get permission to run daily runs on my ia64 porting box
[18:53] <smb_tp> rtg, Did you have such a beast or was that BenC 
[18:53] <NCommander> (my contact at HP is trying to get the same for HPPA)
[18:53] <NCommander> I'm handling powerpc dailies, and I'm using spooky for sparc
[18:54] <NCommander> I just need to throw dak or repopro somewhere
[18:54] <rtg> BenC has the ia64
[18:54] <NCommander> THe installer is hosed on ia64 (a lot of things that should be built as modules are compiled a y, but I don't know enough about the architecture to know what should and shouldn't even be built)
[18:55] <smb_tp> NCommander, sounds great. So maybe you just have to announce what you want on kernel-team mailing list and if there are no objections just let me know where your tree can be pulled from
[18:56] <NCommander> smb_tp, its on zinc already: mcasadevall\ubuntu-jaunty-ports :-)
[18:56] <smb_tp> NCommander, Yep same with me. I got it somewhat to compile but saw there were several module issues like that
[18:56] <smb_tp> NCommander, Great. :) So there were is done
[18:56] <NCommander> Someone with an ia64 is going to have to bash the kernel with a hammer. I found ski, but it needs a special kernel configuration to be usable, so I might add a flavor
[19:01] <smb_tp> NCommander, yeah, most likely. But otherwise you seem to have covered the ground well. The only thing left is some sort of announcement (if you didn't already and I missed that). Not that someone feels stepped onto...
[19:02] <NCommander> smb_tp, I also ported AppArmour to the port architectures ;-)
[19:02]  * NCommander was extremely busy
[19:02] <NCommander> It compiled without issue, its just testing it since there is no documentation that I could find :-/
[19:04] <smb_tp> NCommander, If it boots, its not too bad ;-)
[19:04]  * NCommander is working hard to make the port architecture be awesome again
[19:05] <smb_tp> NCommander, Thanks a lot for that
[19:06] <NCommander> Only doing what I do best :-)
[19:06]  * NCommander is a debian porter
[19:06] <NCommander> A part of me wants to port Ubuntu to the m68k ...
[19:07] <smb_tp> :)
[19:07] <NCommander> Although mips is much more realistic
[19:07] <sebner> A part of sebner only wants to support x86 and x86_64 :P
[19:07] <NCommander> Mostly because I know someone with suitable buildd hardware, and I have an interest in architecture
[21:02] <NCommander> infinity, ping
[21:02] <infinity> NCommander: Yeah?
[21:03] <NCommander> infinity, I need you to weigh in on a question about PPAs, and giving one to the ports kernel team that is non-virtualized. Cprov told me to ask the distro team for permission who passed me to the buildd admins :-)
[21:04] <NCommander> (building the ports kernel on x86 is sorta an exercise in futility)
[21:05] <infinity> NCommander: Ugh.  As much as I love ports (and would like the see the ports kernels stop sucking), there are some policy and security reasons for not allowing community PPAs to touch the non-virtual buildds.
[21:05]  * NCommander whacks head on the desk
[21:05] <NCommander> I was told an exception could be granted if I got an ack by the proper teams
[21:05] <NCommander> But I seem to be going around in a circle
[21:06] <NCommander> infinity, second BTW, I have a question about the powerpc builders (I'm told they have issues with Hardy, and I was hoping I could get more information so we could track down equivelent hardware and debug)
[21:07] <infinity> NCommander: If you can get your hands on some old Xserves, it becomes pretty self-evident under load.
[21:07] <infinity> NCommander: Repeated OOPSing until you get a hard lock.
[21:07] <NCommander> infinity, oh, its an issue under load?
[21:07] <NCommander> Damn it, thats anonying
[21:08] <NCommander> THe kernel post hardy hasn't been touched until about two weeks ago
[21:08] <infinity> NCommander: I tihnk we have some dumps somewhere of the OOPSes.  I'm a bit swamped right now to go hunting, though. :)
[21:08] <NCommander> IF you could get me the specific model of Xserve
[21:08] <NCommander> I can try and track one down before the next LTS
[21:08] <NCommander> (or issue a SRU for hardy to fix it if I can track it down)
[21:08] <infinity> NCommander: Yeah, I can dig up some info.  I just can't do so right this instant.
[21:08] <NCommander> SUre, no rush, we still have two years to fix it ;-)
[21:10] <infinity> Well, I'd *love* to see it fixed in an SRU.
[21:10] <infinity> Having the PPC buildds on an ancient release is not my idea of good times.
[21:10] <NCommander> No kidding
[21:10] <NCommander> OUr glibc build has about five hacks to disable parts of the test suite
[21:11] <NCommander> ITs no just PPC team member has an xserve
[21:11] <infinity> I know.
[21:11] <infinity> Yeah, I don't either.
[21:11] <NCommander> (a few IBM servers, and a small army of G4/G5s :-))
[21:11] <infinity> My main PPC devel machines are a 32-bit G3, and an IBM PowerStation.
[21:11] <NCommander> You will be happy to know jaunty will be sporting a 2.6.27.4 kernel
[21:11] <NCommander> (and I'm seeing if I can get the TB to approve a backport of the kernel as linux-ports-backport to intrepid so we have parity on that distribution)
[21:12] <infinity> Which also reminds me, I need to make our yaboot love my Powerstation.
[21:12] <NCommander> ugh
[21:12] <NCommander> I don't even want to think the last time yaboot was touched
[21:12] <infinity> Unless someone feels like finding YDL's patches and doing so for me.  *hint*
[21:12]  * NCommander adds it to the TODO for today
[21:12] <NCommander> infinity, if you care to sponsor, and help ACK making my kernel branch the offical jaunty ports one ;-)
[21:13] <infinity> Given that it came with YDL installed, I know they have patches.  They weren't kind enough to send me a source CD, though, and I've not had a chance to go hunting.
[21:13] <NCommander> I don't have the same hardware, but I'll post a source package to my PPA (at least THAT works), and then point you to it to test
[21:14] <infinity> But, yeah.  Regarding non-virtual PPAs... We'll need to discuss precisely who and how many people would be able to upload to it, and then perhaps see if we'd need any formal paperwork, or if we're happy with our trust level with those people, etc.
[21:14] <NCommander> infinity, personally, I would just want it to be snapshots of our git tree
[21:15] <NCommander> No direct uploads would be necessary
[21:15] <infinity> The general problem with PPAs is that they're much lower exposure than the archive itself, so it leaves much longer windows of opportunity for people doing Very Bad Things to those machines through PPA uploads.
[21:15] <NCommander> Right
[21:15] <NCommander> I have managed to get approval to run sbuld and friends on four of the five port architectures
[21:15] <NCommander> so if I can't get a non-virtual PPA
[21:15] <NCommander> I'll cobble something together
[21:15] <infinity> Which are you missing?
[21:16] <NCommander> HPPA
[21:16] <infinity> I can do that.
[21:16] <NCommander> Cool
[21:16] <NCommander> HP provided the itantic
[21:16] <NCommander> I have a (slow) PPC
[21:16] <infinity> I have some very fast PPC hardware too.
[21:16] <NCommander> And sistpoty already blessed using spooky (aka REVU) as the sparc builder
[21:16] <NCommander> I need people to smoke test kernels
[21:16] <NCommander> I don't have physical access to any of these machines
[21:17] <NCommander> and someone has to beat the ia64 installer w/ a hammer of pain
[21:17] <infinity> So, yeah.  If we don't want to be bothered too much with the possibility of red tape involved in abusing LP for this, I can certainly help with daily builds.
[21:17] <NCommander> infinity, I need a place to setup dak and wanna-build ... (I've done it before; back when I was an archive manager briefly for the m68k port ;-))
[21:18] <infinity> You worked in Debian 68k?
[21:18] <infinity> Must have been after I stepped down.
[21:18] <NCommander> and ARM
[21:18] <NCommander> And MIPS
[21:18] <NCommander> I ran four buildds
[21:18] <NCommander> and our w-b after we got kicked off buildd.d.o before moving to d-ports.org
[21:18] <infinity> Yeah, that's way after my time.
[21:19] <infinity> I kinda gave up around the time we became a non-release arch.
[21:19] <infinity> Lost motivation.
[21:19] <NCommander> Actually, we got a new glibc now
[21:19] <NCommander> FreeScale did the enginneering work
[21:19] <NCommander> Which means its likely we will return in squeeze
[21:19] <infinity> NPTL?
[21:19] <NCommander> NPTL
[21:19] <NCommander> :-)
[21:20] <infinity> Nice.  I wonder how much of my groundwork got included in that.
[21:20]  * infinity shrugs.
[21:20] <NCommander> One of the cool things about coldfire and m68k being nearly the same architecture
[21:20]  * NCommander also did work bootstrapping coldfire debian
[21:20] <NCommander> Sadly, I got the board with a hardware fault on it
[21:20] <infinity> They are the same, module a few instructions.
[21:20] <infinity> No one ever claims that i386 and i686 aren't the same arch, so why split hairs? :)
[21:20] <NCommander> infinity, well, that's why we have lpia
[21:20] <NCommander> For better or worse
[21:20] <infinity> My ColdFire board is very dusty these days.
[21:20] <NCommander> infinity, I got my from Stephan
[21:21] <NCommander> infinity, I actually got as far as a native GCC bootstrap, and booting from flash directly
[21:27] <NCommander> infinity, actually, I think our yaboot problem is simply we're a year behind on the last current release
[21:28] <infinity> NCommander: That's possible.  Given that YDL's Powerstation release is actually a completely seperate CD from their "normal" PPC release, though, I'm assuming there's either a custom yaboot, custom kernel, or (likely) both on there.
[21:28] <NCommander> There are issues with the kernel when you compile in support for multiple platforms
[21:28] <NCommander> It crashed and burned when I tried to add anything beyond CHRP and NewWorld
[21:29] <infinity> They can get more than one kernel on a CD, mind you.
[21:29] <infinity> But, yeah, that might be beyond YDL.
[21:29] <infinity> They have some great technical people, but when it comes to user-friendly, they fail.
[21:29] <NCommander> infinity, what happens when you try and boot on the powerstation?
[21:30] <infinity> I almost audibly cried when I saw their default desktop.  It's... It's why most people think UNIX is terrible.
[21:30] <NCommander> Its based off Red Hat
[21:30] <NCommander> What do you expert?
[21:30] <infinity> And, to be honest, I don't recall what exactly happens.  Dies in yaboot land, though.
[21:30]  * NCommander is trying to find their SRPMs
[21:30] <infinity> No, RedHat's default desktop is a pretty clean and friendly place.
[21:30] <NCommander> Not in the 6.x days which YDL was based off of
[21:31] <infinity> YDL's reminds me of CDE, circa 1993.
[21:31] <NCommander> infinity, what version of yellow dog are we talking about?
[21:31] <infinity> Booted, and was like, "Oh hai, IRIX, I've missed you!"
[21:32] <NCommander> IRIX was my first UNIX ever ;.;
[21:32] <infinity> NCommander: The "latest", I imagine... Whatever shipped with my Powerstation.  Let me find the DVD.
[21:32] <infinity> DVD claims it's "Version 6".
[21:32] <NCommander> Ok
[21:32] <infinity> "Powerstation Edition"
[21:32] <NCommander> so there are no yaboot differences between powerstation and regular
[21:32] <NCommander> X11 and the kernel is where the changes are
[21:34] <NCommander> infinity, ok, YDL ships with yaboot 1.3.13 with specific changes
[21:34] <NCommander> so its a just matter of diffing
[21:36] <NCommander> o_o; wow, lot of patches
[21:36] <NCommander> and no patch system in the deban packaging
[21:36] <NCommander> nice
[21:37] <TheMuso> NCommander: Yeah I know, kinda annoying.
[21:37] <NCommander> nothing powerstation specific here
[21:38] <NCommander> Wait
[21:39] <NCommander> who makes powerstations?
[21:39] <infinity> IBM does, but they're unbranded.
[21:39] <infinity> http://www.terrasoftsolutions.com/products/powerstation/
[21:39] <NCommander> There are a whole bunch of amiga, and pegasos patches
[21:39] <infinity> Every part inside is IBM, but the box just says "YDL Powerstation".
[21:39] <NCommander> and one ppc64 intrd patch
[21:40] <infinity> Anyhow, I have lots of work to do, sadly.
[21:40] <NCommander> infinity, I'll ping you if/when I h ot test
[21:40] <infinity> I'd love to take a weekend and figure out the most minimal way to make Hardy support this machine, though.
[21:40] <NCommander> infinity, if you however figure out what the error is, it can isolate which patches I need to merge
[21:40] <infinity> NCommander: Ping me on Friday?
[21:41]  * NCommander shall do so
[21:41] <NCommander> That will be after the jaunty kernel lands I hope
[21:41] <infinity> NCommander: I'm taking Fridays off work for a while, so I might have some "community fiddling time".
[21:41] <NCommander> very awesome
[21:41] <NCommander> speaking of community fiddling
[21:41] <NCommander> TheMuso, feel like uploading something?
[21:41] <TheMuso> NCommander: Sure. What may that be?
[21:41] <NCommander> a kernel
[21:41] <NCommander> *hears a gunshot*
[21:41] <TheMuso> um... Shouldn't the kernel team bless that?
[21:42] <infinity> The kernel team has almost entirely washed their hands of ports.
[21:42] <NCommander> ^- infinity 
[21:42] <TheMuso> I'm not willing to touch it unless the kernel team really don't want to worry about uploading ports kernels.
[21:43] <infinity> TheMuso: You have my blessing to sponsor any ports kernel uploads.  Assuming you have the know-how to do the usual sponsorship vetting/review.
[21:43] <infinity> TheMuso: The primary kernel team has almost no interest in them, hence the split. :/
[21:44] <infinity> I'm just glad the split happened after Hardy, so the hardy kernels are at least somewhat homogenous.
[21:44] <NCommander> infinity, the only reason they support lpia is because its not that hard to keep it building
[21:44] <infinity> Intrepid ports kernels are a mess. :/
[21:44] <NCommander> infinity, yeah, it took most of the cycle to clean that up. We only got it fully working towards final freeze (and the installer is still an absolute trainwreck)
[21:44] <TheMuso> infinity: Yeah the sponsoring is no problem. NCommander Alright, what git tree am I working with, your ports tree?
[21:45] <NCommander> TheMuso, that would be mine, but the changelog isn't up to date (you need to call the proper rules to make the changelog be generated correctly)
[21:45] <infinity> NCommander: Are there plans to keep ports kernels based on the non-ports git from here on it?
[21:45] <infinity> s/it/in/
[21:45] <TheMuso> NCommander: I understand that.
[21:45] <NCommander> infinity, unless a port because offically supported again, yeah
[21:45] <infinity> NCommander: Having different kernel versions, slightly different patchset, etc, between ports is... Terribad.
[21:45] <NCommander> infinity, not for jaunty
[21:46] <NCommander> infinity, we're actually half a revision higher than the mainline :-)
[21:46] <NCommander> (mainline is .2 with cherry picking, ports is .4)
[21:46] <infinity> That still feels icky, to a man who has many different arches at home.
[21:46] <NCommander> Same here
[21:46] <TheMuso> Agreed.
[21:46] <NCommander> How abotu I add amd64 and i386-generic support to ports
[21:46] <infinity> I like all my systems to be predictably similar.
[21:46] <NCommander> Then you can run the same kernel across the board ;-)
[21:47]  * NCommander actually did his inital cherry picking patch work on amd64, and then removed those files before committing
[21:47]  * NCommander makes sure the ports tree is up to do
[21:47] <NCommander> *date
[21:47] <NCommander> TheMuso, you do know how to do a kernel release, right?
[21:48] <TheMuso> NCommander: Yeah there are docs on the wiki. I'll take care of it once I've processed my morning email and taken care of some other things, but it is on my TODO for today.
[21:49] <NCommander> Ok, I'll generate all the ABI files in the meantime, and then add them to the tree once 1.1 is uploaded so we have a constant ABI to base against
[21:49] <TheMuso> Right.
[21:49] <NCommander> TheMuso, since I have done some work in linux-ports-lrm ;-)
[21:49] <TheMuso> NCommander: Ok cool.
[21:49] <NCommander> (its just madwifi, but I figure its worth having)
[21:49] <NCommander> linux-rt will need an upload, but thats multiverse, and I need to clear it by its maintainer anyway
[22:00] <TheMuso> NCommander: I see you posted to the kernel list re this kernel. Are you still waiting for a response to that before we go ahead?
[22:00] <NCommander> Thats more moving my tree to ubuntu-jaunty-ports.git
[22:00] <TheMuso> NCommander: Right.
[22:00] <NCommander> I personally want the kernel to hit jaunty so people can test the damn thing
[22:00] <NCommander> (its only been smoke tested on powerpc)
[22:01] <NCommander> also, not having a kernel package available has blocked work on linux-rt on powerpc, and linux-ports-lrm (its hardware to work against packages that only exist on 127.0.0.1 ;-))
[22:01] <NCommander> s/hardware/harder
[22:02] <TheMuso> Right.
[22:03] <NCommander> We probably should look at linux-ports-lbm as well, but I first rather just make sure the kernel is usable (since I can probably find a PS3 or two user willing to test jaunty)
[22:04] <NCommander> also, once this kernel is uploaded, the next ports daily image will tell us if the installer is completely broken
[22:04] <NCommander> TheMuso, second BTW< please leave my name on the changelog so if a build FTBFS, I can get direct notification of it
[22:04] <TheMuso> Well the installer still needs to have some udebs added. Once Colin has merged d-i, I'll add them.
[22:05] <NCommander> TheMuso, I added them to the d-i files in the kernel
[22:05] <TheMuso> NCommander: Ok.
[22:05] <TheMuso> NCommander: But work needs doing on the d-i side as well.
[22:05] <NCommander> ok, well, at least this is progress ;-)
[22:05] <NCommander> brb, dinner
[23:53] <TheMuso> NCommander: hrm when attempting to isnert the change in the changelog using your ports tree, I get the following error. Looks like there may be a tag missing or some such:
[23:53] <TheMuso> fatal: ambiguous argument 'Ubuntu-2.6.27-0.0..HEAD': unknown revision or path not in the working tree.
[23:53] <TheMuso> Use '--' to separate paths from revisions
[23:53] <TheMuso> NCommander: I think you missed something.
[23:53] <NCommander> o_o;
[23:54] <NCommander> Its possible the repo needs to be tagged 1.1
[23:54]  * NCommander hasn't done this before
[23:54] <TheMuso> Right, and I think the tag is used to display changes between the last upload and head.
[23:54] <NCommander> So what do I need to do to fix the tree?
[23:55] <TheMuso> NCommander: I am not entirely sure.
[23:55] <NCommander> Let me see if I can tag and get it to work here
[23:55] <NCommander> What was the command you used?
[23:57] <TheMuso> NCommander: ./debian/rules insertchanges
[23:57] <NCommander> Worked fine here
[23:58] <TheMuso> hrm.
[23:58] <NCommander> I'm going to tag it ubuntu-ports-2.6.27-1.1 (we can't overlap with the main kernel, or it will break remotes)
[23:58] <NCommander> TheMuso, I'll just tag and commit with the changelog generated and all that
[23:58] <TheMuso> Well my copy of your tree has no tags.
[23:58] <NCommander> My tree has no tags
[23:58] <TheMuso> NCommander: hrm ok.
[23:59] <NCommander> wel
[23:59] <NCommander> I do have tags from remotes
[23:59] <NCommander> Very strange
[23:59] <NCommander> I think its because I restarted the branch things broke
[23:59] <NCommander> If it does this again next upload, we'll investiage futher
[23:59] <TheMuso> NCommander: have a look at this page for instructinos: https://wiki.ubuntu.com/KernelMaintenance