[01:04] <RAOF> apw: Would you like me to update linux-backports-modules-nouveau to 2.6.33, add the ctxprog generator, and do a little spring-cleaning in there?
[01:41] <RAOF> Would someone kindly run git update-server on http://kernel.ubuntu.com/git-repos/ubuntu/ubuntu-lucid-lbm.git ?  Cloning over http is failing.
[02:12] <lifeless> RAOF: lolol.
[02:12] <lifeless> RAOF: :P
[02:13] <RAOF> lifeless: I don't think anyone is unaware of how sucky git's push is.
[02:13] <lifeless> RAOF: oh, I think some folk are :)
[02:14] <lifeless> RAOF: ... the ones that like it
[02:16] <RAOF> While I'm ragging on VCSs... would you kindly make bzr not silently trap everything I branch in 2a? :P
[02:18] <lifeless> RAOF: its doing that because you told it to
[02:19] <RAOF> Well, it's doing that because at some point in the past I bzr init-repo'd a directory somewhere above the directory I'm branching into.
[02:20] <RAOF> The different repository formats are the only major source of friction I have in using bzr; it'd be nice if you could go back in time and make everything just 2a.
[02:26] <lifeless> RAOF: it would be :)
[02:52] <eggonlea> ericm: Morning!
[02:53] <eggonlea> Do you know why OABI is enabled in ARM kernel?
[02:54] <eggonlea> We prefer to disabling it if it's not necessary because this may cause unexpected issues (which has been found on Dove before).
[02:55] <eggonlea> Karmic is EABI already, and Lucid should be as well, right?
[03:56] <RAOF> apw: Bug #528190
[03:56] <ubot3> Malone bug 528190 in linux-backports-modules-2.6.32 "Update to linux 2.6.33, Incorporate upstream's ctxprog generator" [Undecided,New] https://launchpad.net/bugs/528190
[14:39] <cnd> apw, smb: although he hasn't stated such yet in bug 516777, bdmurray confirmed that the two wacom commits I added give him touchscreen functionality, and smb and tjaalton confirmed that it hasn't hurt their older wacom products
[14:39] <ubot3> Malone bug 516777 in linux "HP Touchsmart tm2 requires newer wacom driver" [Low,In progress] https://launchpad.net/bugs/516777
[14:39] <cnd> what do you suggest we do? pull it into lucid ourselves? put it in lbm or some dkms package?
[14:44] <smb> cnd, Those were upstream, right?
[14:45] <cnd> smb, yes in .33
[14:45] <cnd> I can also submit to -stable if you think there's any chance they'll be accepted
[14:45] <smb> cnd, We might consider it as bugfix in that case and pull it into the kernel directly (sort of pre-stable). I think apw was thinking along that line. But the final call would be his
[14:46] <smb> cnd, It looks a bit big for general stable. So it might or might not work out to get it accepted. Might be worth contacting the maintainer of the wacom driver and ask about his feeling.
[14:47] <cnd> smb, does it hurt to just submit to -stable and hope?
[14:47] <cnd> or is it worthwhile to contact the maintainer first to get them on board?
[14:48] <smb> There was one case with the interleaved ALPS/PS2 protocol which was also big. But the maintainer said it would help a lot of cases and had been upstream without any reports and so on. Much better to get with maintainer.
[14:49] <smb> If you just send it to stable (you would need to cc the maintainer there, as well) you will need maintainer support anyway because its quite big
[14:49] <cnd> ok
[14:50] <cnd> smb, then I'll work with the maintainer about -stable inclusion, but should we wait on that before considering whether we throw it into lucid as a pre-stable?
[14:52] <smb> cnd, Probably depends on how quickly we hear back. If it takes too long, we might go ahead based on our testing and because its harder after release.
[14:52] <cnd> ok
[15:03] <cnd> smb, if the wacom guy wants to support us pushing this upstream, what be the result? Are we asking him to push it himself? Or just a confirmation that we can add "This request is supported by the wacom driver maintainer"?
[15:11] <smb> cnd, It could be either him or us. When you push things, I would add a cover mail saying that we had found that issues, talken with the maintainer, he thinks it good too, bla. And send it with cc the maintainer. Sort of we think it makes sense in stable though it is a bigger one. And then see what Greg says
[15:11] <cnd> ok
[16:18] <rackerhacker> anyone know why drbd is disabled in linux-ec2 for lucid?
[16:19] <smb> Drbd is supposed to be a dkms package now (it was before but the kernel had an aditional moddule)
[16:22] <rackerhacker> ah, okay, that makes sense
[16:22] <rackerhacker> i was digging through the git logs and couldn't find it
[16:23] <rackerhacker> thanks, smb 
[16:24] <cnd> rackerhacker: the drbd module that was in the linux-image package was old anyways
[16:25] <rackerhacker> cnd: yeah, i noticed that as well :/
[17:39] <apw> rackerhacker, its gone now
[17:39] <apw> in the main branch, and will go in the others as they track it
[17:57] <rackerhacker> thanks apw 
[17:59] <rackerhacker> i'm trying to dig up the patchset that adjusted hvc0 -> tty1 in linux-ec2
[18:02] <rackerhacker> disregard - found it
[18:04] <apw> RAOF, thanks for all those fixes.  I had done the update to t
[18:05] <apw> the .33 but the other bits are good finds ... i'll pull that diff appart and pull them into the package git.  thanks
[18:59] <apw> RAOF, although your changelog entries include changes to Conflicts/Replaces I cannot see any changes which implement those in the diff??
[21:39] <RAOF> apw: You're quite right!  I don't know where those changes got dropped.
[22:05] <dyek> Hi! Where can I find pv-grub? Is there a package that contains this (Xen?) utility?
[23:03] <apw> RAOF, i uploaded the rest of it .... in the git tree i did it as a bunch of patches... thanks for the bits, if you get me the missing bit i can get that up in the next one ...
[23:04] <RAOF> apw: Is the git tree clonable?  When I tried (over http), git complained that git-update-server hadn't been run.
[23:04] <RAOF> If you could make it clonable, I'll make the next (set of) patch(es) against git, rather than the archive.
[23:04] <apw> hrm, should be, but perhaps something got lost in the config for that repo.  it should clone over git as thats how i get it
[23:04] <apw> its late here, but i'll try and look at it tommorrow
[23:05] <RAOF> You probably clone over git+ssh?  And I don't think I've got ssh access there.
[23:05] <apw> we have git: as well
[23:05] <RAOF> I tried cloning over git, but maybe not hard enough.
[23:05] <apw> git://kernel.ubuntu.com/ubuntu/ubuntu-lucid-lbm.git
[23:05] <apw> it should be
[23:06] <RAOF> Oh, and now of course it works!
[23:06] <RAOF> I wonder what I was doing previously?  Oh, I probably had the kernel-team path component in there.
[23:07] <apw> yeah, its not the same on http: as git: for some reason
[23:07] <apw> RAOF, cool the update is built and published
[23:08] <apw> i've also pulled in your two novueau commits over the top of my drm backport
[23:08] <apw> which is in my 'red' PPA: https://edge.launchpad.net/~apw/+archive/red/+packages ... when it finished building
[23:09] <apw> something else for your keen testing
[23:09]  * apw wanders off
[23:09] <RAOF> I'll give it a whirl.
[23:09] <RAOF> Have a good evening!
[23:09] <apw> RAOF, thanks ... any feedback appreciated ... its bed for me
[23:21] <Ng> if one has a git checkout of the ubuntu lucid kernel, where would one find the config file that is going to be used to build an amd64 server kernel?
[23:22] <lifeless> in debian/
[23:22] <lifeless> IIRC
[23:27] <Ng> aha debian.master/config/ looks relevant to my interests