[00:50] <Fjodor> apw: I will probably go to bed soon, but did you have any luck with getting working headers packages built for the daylies? And also, when do they get uploaded (relative to UTC)?
[08:40] <cdE|Woozy> I just noticed kernel 2.6.31-6 spitting out "ACPI Error", is this something to worry about?
[08:40] <cdE|Woozy> http://pastebin.ubuntu.com/256174/
[09:43] <soren> Does anyone know why CONFIG_GFS2_FS_LOCKING_DLM is disabled in Karmic?
[10:03] <apw> soren, i would guess it has its default value and noon has ever asked for it
[10:03] <soren> Consider yourself asked  :)
[10:04] <soren> It used to be enabled (in previous versions of Ubuntu)
[10:04] <apw> you sure, we didn't have gfs2 did we?
[10:05] <soren> We do have GFS2.
[10:05] <soren> ...and have had for quite a while.
[10:05] <soren> Without the DLM, it's not much fun.
[10:07] <apw> soren, yep seems to have gone away, strange
[10:07] <soren> i can haz it back, plz?
[10:07] <apw> file me a bug will ya, and assign it to apw
[10:18] <soren> apw: Sure.
[10:28] <apw> soren, and let me know the number here
[10:28] <apw> smb, damn these udebs are complex.  i think i 
[10:28] <apw> have it sorted out now.  will know in 10 mins
[10:29] <soren> apw: Sure.
[10:29]  * soren looks it up
[10:30] <smb> apw, I can believe. Just let me know if you have updated your patches, then I run those on the builds I have
[10:31] <apw> i'll let this build run, and if it works (and i think it will) then i'll push you a copy
[10:31] <smb> Ack
[10:31] <apw> man this would all be so easy but for kernel-wedge which is just a POS
[10:31] <apw> i know where stuff is la la la not listening
[10:32] <apw> its such a pain that udebs are dependant on binary-debs ... so it makes every damn thing
[10:32] <soren> apw: bug 416325
[10:32] <ubot3`> Malone bug 416325 in linux "Please reenable CONFIG_GFS2_FS_LOCKING_DLM" [Undecided,New] https://launchpad.net/bugs/416325
[10:34] <soren> apw: It's not like kernel-wedge is sacred. You can fix it if you like :)
[10:34] <apw> heh yeah ... i'd love to walk into the mine field.  could i have a blind fold?
[10:35] <apw> we are being mean to it, its not worth fixing it for this
[11:27] <ghostcube> hi
[11:31] <levonshe> Hello all, please simple question - linux_source-2.6.30  package is not anymore on ftp server, why? 
[11:36] <levonshe> The second simple question - to use compiled 2.6.31 kernel, it is required to install linux-libc-dev_2.6.31-6.25_i386.deb package ?
[12:18] <asac> some more ids for cdc_ether ... can we pick them to support more ericsson modems? http://www.spinics.net/lists/netdev/msg104788.html
[12:18] <asac> pgraner: ^^ ?
[12:24] <apw> levonshe, linux_source-2.6.30 has gone becuase we have moved on to 2.6.31 kernels in karmic
[12:24] <apw> the linux-libc-dev is a headers package for compiling programs, and necessarily is version locked with the kernel as it carries the headers from there kernel
[12:47] <levonshe> apw, first thank you, still I confused - say I want to use 2.6.30 on jaunty ( I am actually have it now) and syscalls do not supposed to change , so application (user space) programs do not require libc-devel ? (my programs srill works)
[12:48] <apw> though by that standard installing the updated libc headers wouldn't change anything either
[12:49] <apw> the packages are not designed for backport like that so its not supprising they are setup for normal use.  which is to have that package installed in parallel with the kernel
[12:58] <arand> I get a kernel panic on shutdown, I would like to know the easiest way to capture it for attaching to bug report? It does not show up anywhere in /var/log/*
[13:04] <smb> arand, Might happen after the devices are synced. Likely the best chance is to disable splash, set console to a small font and take a picture when you see the panic on the way down
[13:07] <levonshe> apw, can you comment - how /boot/abi file is used , because I am compiling upgrading kernel/modules/drivers and did not receive any complaints for ABI compatability ?
[13:08] <apw> the boot/abi files are used for abi comparisons between kerrnels, allowing us to detect such a change and handle it before a kernel release
[13:10] <arand> smb: okay, will do. I'm not sure if it's a panic/Oops but something locks and requires a REISUB, and what I see with splash disabled does look much like a panic... *looks into changin resolution.
[13:11] <smb> arand, https://wiki.ubuntu.com/KernelTeam/KernelDebuggingTricks might help
[13:13] <smb> arand, also /etc/default/console-setup
[13:19] <arand> smb: cheers
[13:29] <levonshe> apw, sorry to monopolize you , but couple of things I am thinking : the release notes for libc-devel describes all kind of changes in kernel, but I think they should state which new functionalities are available at user space, so where is the document  for application programmer?
[13:30] <apw> as far as i know there is none, the main thing is the ABI is meant to be backwards compatible
[13:30] <apw> so in theory you would only get newer interfaces specified
[13:31] <apw> where it is not you would be entering the land of needing to get the libc updates to match
[13:31] <apw> and likely beyond what is possible to expect to work well with both kernels
[14:02] <andresmujica1> hi, anyone nows if ogasawara use a template for kernelteam bugday wiki page? i want to update a little bit the launchpadlib section, but i'm not sure if there's a template for it or just modifying the last version would do it...
[14:23] <rtg> pgraner`, whats the story with DVB firmware? Are they all under Jockey control now?
[14:26] <pgraner`> rtg: not yet, pitti is on holiday once he gets back it will get flipped
[14:27] <rtg> pgraner`, k, just responding to a k-t email
[14:27] <smb> andresmujica1, I would guess she generates it somehow. But best ask directly in around two hrs
[14:28] <andresmujica1> smb: yeap, that's what i'll do.. tks 
[14:48] <rtg> apw, can you give me a quick review of the perl syntax for http://kernel.ubuntu.com/~rtg/0001-UBUNTU-SAUCE-Improve-error-reporting-in-postinst.patch ?
[14:50] <apw> rtg looks fine to me, $! in a string context is the error message translation of errno from the previous system call
[14:50] <apw> so he has added $! in each case into the error mesasge.
[14:50] <apw> ack from me
[14:51] <rtg> apw, thanks
[14:51] <rtg> I've not programmed perl in about 47 years
[14:52] <amitk> heh :)
[14:52] <apw> rtg a good plan indeed
[14:53] <rtg> apw, as the keeper of checkpatch, I assumed you were fresh on it :)
[14:53] <apw> sadly true
[14:54]  * apw collides with rtg :)
[14:54] <apw> i love that git slaps one
[14:55] <rtg> apw, a Karmic push?
[14:55] <apw> yeah, you just pushed that patch we were talking about
[14:55] <apw> and i was about to push the abstraction fixes
[14:55] <rtg> apw, seems like I should let 'em into the wild as soon as possible.
[14:55] <apw> it told me to stop and i ma rebasing them
[14:55] <apw> will push them in a few secs
[14:55] <rtg> copyright fix?
[14:56] <apw> that plus about 3 others
[14:56] <rtg> cool. I'll use 'em to fix my *&#$^!^* arm builds.
[14:56] <apw> copyright, empty udebs, fixing some bad links
[14:56] <apw> git just decided to gc itself ... grrr
[14:57] <rtg> apw, yeah, it rips on me about once a  day.
[14:57] <apw> first time i've seen it in ages... damnable thing
[14:58] <apw> always seem to do it when you have a disk hog runing so you notice it cause it takes ages
[14:59] <apw> 700k objects hrm ... thats dirty
[15:05] <apw> rtg ok i've pushed a pile to karmic, seems to work for me
[15:06] <rtg> apw, horking
[15:17] <rtg> devinheitmueller, you should hassle that slacker pgraner`about the xc5000 firmware. I don't think he's got enough to do.
[15:18] <devinheitmueller> rtg: heh.  I wasn't trying to get on anybody's back.  I just wanted to give a poke and make sure it didn't fall off the table.
[15:19] <rtg> devinheitmueller, I'll milestone the bug so that it doesn't accidentally get overlooked.
[15:19] <devinheitmueller> Thanks.
[15:19] <devinheitmueller> I spent months getting the licensing worked out with Xceive, and it would definitely help alot of users if this thing worked "out-of-the box"
[15:20] <rtg> devinheitmueller, ok, milestoned _and_ assigned to the boss :)
[15:21] <devinheitmueller> Thanks.  I appreciate it.
[15:27]  * devinheitmueller suddenly realizes that "rtg" is Tim Gardner.  Doh.
[15:27] <rtg> I'm infamous ?
[15:28] <devinheitmueller> Well, you're the same guy I'm talking to via email.  I just didn't make the connection.
[15:28] <devinheitmueller> But yes, you are infamous.  :-)
[15:28] <rtg> I'm just hiding behind and obscure nick :)
[15:28] <rtg> s/and/an/
[15:28] <devinheitmueller> Indeed.  If it had been "tg", I probably would have made the connection much faster.
[15:28] <devinheitmueller> The whole "tim is my middle name" thing threw me off.
[15:29] <devinheitmueller> Anyway, a pleasure to make your acquaintance.
[15:29] <rtg> hmm, can't help it. got stuck with that name years ago.
[15:31] <ogra> raving tim gardner ?
[15:31] <ogra> or is it rocking ?
[15:31] <rtg> raving suits me :)
[15:31] <devinheitmueller> ogra: I might have guessed  "ranting".
[15:31] <rtg> or ranting even.
[15:31] <ogra> lol
[16:19] <bjf> apw, are you mucking with my dove branch? (i have some patches to submit but can wait)
[16:19] <apw> i am not mucking with it, but it will be getting mucked with shortly
[16:21] <rtg> apw, do you get this lintian noise ? 'copyright-without-copyright-notice'
[16:22] <apw> rtg checkin
[16:22] <apw> g
[16:23] <rtg> seems harmless
[16:25] <apw> how does one find out what it even means
[16:28] <rtg> apw, dunno. perhaps solicit the expertize of a packaging expert. alternately, read the debian policy manual (ugh!) http://www.debian.org/doc/debian-policy/
[16:30] <apw> rtg if i run lintian on a karmic dsc i just built from master
[16:30] <apw> i get W: linux source: ancient-standards-version 3.6.1 (current is 3.8.2)
[16:30] <apw> E: linux source: build-depends-on-obsolete-package build-depends-indep: gs
[16:30] <apw> W: linux source: native-package-with-dash-version
[16:37] <Q-FUNK> lintian-info
[16:38] <Q-FUNK> which package still has 3.6.1 as its source standard?
[16:39] <apw> the kernel
[16:39] <Q-FUNK> rtg: on which package?
[16:39] <Q-FUNK> url to its dsc?
[16:40] <Q-FUNK> lemme see what I can do to overhaul that...  url please?
[16:41] <rtg> Q-FUNK, http://archive.ubuntu.com/ubuntu/pool/main/l/linux/linux_2.6.31-6.25.dsc
[16:41] <Q-FUNK> thanks.  fetching...
[16:44] <Q-FUNK> right. debian/control is indeed somewhat outdated
[16:47] <Q-FUNK> this has got to be one of the scariest build trees I've ever seen.
[16:50] <rtg> apw, I cleaned up 'UBUNTU: abstracted-debian -- drop the debian directories from headers part 2' and repushed. You left some changelog fuzz in the patch.
[16:56] <Q-FUNK> rtg: copyright with copyright:  it misses an actual (C)CCYY in there
[16:57] <rtg> Q-FUNK, send a patch ?
[17:00] <Q-FUNK> rtg: I'm letting the whole package build in background.  will send a patch afterwards with as many fixes as possible
[17:00] <rtg> apw, there was also a typo; prunt --> prune
[17:00] <Q-FUNK> I tend to be fairly good at fixing lintian errors
[17:00] <rtg> Q-FUNK, thanks, its takes someone with more knowledge of debian policy then I have
[17:40] <apw> rtg, sorry man, that was fail on my part.  it failed to cherry-pick from jaunty, so i hand applied it, badly
[17:41] <rtg> apw, its there now (I think)
[17:42] <apw> rtg ye looks correct now
[17:43] <apw> foolish me, i was doing two things at once in the same tree, the prerelease builder stepped on my toes...
[17:43] <apw> do one thing at once ...
[17:43] <rtg> apw, happens to me all the time.
[17:45] <rtg> apw, I _really_ like uploading from zinc :)
[17:46] <apw> i do all mine from chin, but yes the difference is astounding
[17:46] <rtg> apw, do you do your packaging on chin?
[17:46] <apw> no i mostly do it local, then push the blob to chin in the background
[17:46] <apw> as i often upload it to more than one ppa say
[17:47] <rtg> apw, with the git repo on zinc, its pretty straighforward to just do it from there
[17:47] <apw> are you doing your packaging as well on zinc
[17:47] <apw> yeah thats pertty sensible ... why don't i do that?
[17:47] <rtg> apw, yep, have karmic chroot now
[17:47] <apw> nice
[17:53] <smb> cd ..
[17:55]  * apw eyes a sierra nevada beer ...
[17:56]  * smb has a Baisinger special
[17:57] <smb> rtg, Analizing contents of common packages:
[17:57] <smb> \o/ seems all files are present
[17:57] <rtg> smb, cool.
[17:57] <smb> rtg, This was for jaunty-i386. I want to do amd64, lpia and amrel too and then repeat with a created source package
[17:58] <smb> rtg, but it looks so far quite good
[17:58] <rtg> apw, I'm thinking, that with sufficient care, most of the rules.d files for topic branches could be run directly from debian.master
[17:58] <apw> rtg that seems likely
[17:59] <rtg> smb, I breathlessly await your results. I'm chomping to get on with the LTS backports.
[17:59] <apw> rtg ... once smb is happy i am hoping he will squash the bug fixes so you will have a stack of about 4 patches you need
[17:59] <smb> rtg, I try to make quick. I wanted to go on with jaunty-arm too
[17:59] <apw> with the middle one being a scripted thing
[18:00]  * apw is waiting to do netbook
[18:00] <rtg> apw, I dunno if we'll ever be able to script it entirely. some of these branches are gonna be quite unique.
[18:00] <smb> apw, Maybe you can start of with squashing and sending a sort of pull/review to our list?
[18:01] <apw> smb sure ... 
[18:01] <apw> rtg i mean that there is a scripted way to may the base for a branch
[18:01] <apw> as in converting a branch to the method
[18:01] <apw> and a verbial script to make the first entries before customisation for a branch
[18:04] <smb> rtg, btw. I see a linux-mvl-dove_2.6.31-200.2_source.changes for binary NEW for karmic. Is that one you want to be eradicated too?
[18:04] <rtg> smb, yeah, I'm working on the next dove upload
[18:29] <apw> rtg does rfkill userspace remember anything and apply it on boot to your knowledge?
[18:29] <rtg> apw, nope, its possibly stored in BIOS NVRAM or something, but nothing in the driver or userspace
[19:40] <ameno> no vanilla build today?
[22:29] <fabbione> hi guys
[22:30] <fabbione> rtg: ping?