[07:57]  * abogani waves
[07:57] <abogani> apw: Are you around?
[07:58] <RAOF> He's on holiday, isn't he?
[08:04] <jj-afk> yes he is on holiday this week
[08:06] <abogani> Ok Thanks!
[08:22] <diwic> this is just a long shot, but does anybody know if the latest lucid kernel upload (somewhere around 12 - 16 aug?) had something in it which could break ACL permissions? 
[08:41]  * smb yawns
[08:42] <ikepanhc> smb: good morning
[08:42] <smb> ikepanhc, good morning
[08:43] <smb> lamont, If you are around: pre6 finally seems one that loves us
[08:44] <ikepanhc> smb: last time we talk about if there are hardy proposed upload, then I can rebase netbook-lpia and wait for 1 week (normally) making sure no big regression..
[08:45] <ikepanhc> smb: I saw you have a security release on hardy last friday.. any suggestion for netbook-lpia branch?
[08:45] <smb> ikepanhc, I would wait with Hardy atm
[08:45] <ikepanhc> smb: atm?
[08:45] <smb> ikepanhc, We are currently (and maybe have by now) to resolve a regression that shows up when using xen
[08:45] <smb> at the moment
[08:46] <ikepanhc> smb: oh....
[08:46] <smb> ikepanhc, I had some proposed uploads there but let the be removed. I guess there will be another security upload to fix things
[09:02] <smb> ikepanhc, "rmadison -asource linux" would show you all versions currently in the archive of the linux source package
[09:02] <ikepanhc> smb: thanks, trying
[09:03] <smb> It can take more arguments for filtering even more, you would need to play around what is best
[09:03] <ikepanhc> smb: I can write a script to record the version string
[09:04] <ikepanhc> smb: if there is any update, I will have the notify
[09:04] <smb> right, that way you won't need to watch it yourself
[09:04] <ikepanhc> smb: great tool, thanks
[09:04] <smb> eh, np. :)
[09:06] <ikepanhc> smb: but it does not show the hardy-proposed, only hardy-update
[09:06] <smb> Because currently the proposed pocket is empty
[09:07] <ikepanhc> smb: oh
[09:07] <ikepanhc> smb: thanks
[09:07] <smb> If there is something in proposed it will show up
[09:07] <ikepanhc> smb: package in proposed will be remove after some time? (guess 1 or 2 weeks)
[09:13] <smb> I am not exactly sure how quickly this is but basically when it is moved to updates.
[11:25] <lamont> smb: pre6 is love. thank you.
[11:55] <lag> What #channel would it be best to ask about video editing?
[12:16] <amitk> lag: #ubuntu to start?
[12:19] <lag> amitk: Done
[12:22] <lag> amitk: It's going well 
[12:23]  * lag whistles 
[12:24] <amitk> lag: if they haven't kicked you out yet, then I guess it isn't a bad place to start ;)
[12:24] <lag> amitk: Why would they kick me out?
[12:25] <lag> amitk: They can't kick me out, "I am the law" :D
[12:25] <amitk> lag: for being offtopic or something... 
[12:25] <amitk> lol
[12:25]  * ogra thought you are the lag
[12:25] <amitk> lag is all the scheduler bugs we have :)
[12:27] <lag> ogra: You were told off for cracking rubbish jokes yesterday in the meeting room!
[12:27] <ogra> hey, i didnt pick your nick :P
[13:00] <lamont> smb: fwiw, osmium is back in the building game, running pre6.  how soon do we get a kernel-nami
[13:00] <lamont> ?
[13:00] <smb> kernel-nami?
[13:01] <lamont> long story.  how soon should we expect to see a new kernel in -updates or so?
[13:01] <amitk> multiple kernel build requests? :)
[13:02] <smb> lamont, That depends on some other tests that John wanted to do with ec2. But when we think this set is good I would assume this gets released as a security update
[13:02] <lamont> smb: cool.  eta on that? or is it "blocked on John, bug him not me"?
[13:04] <Akendo> HI
[13:04] <smb> lamont, Hard to say. Actually osmium being up again with that seems good enough to go forward. But in the end its the security teams call
[13:04] <smb> So probably today or tomorrow
[13:04] <lamont> \o/
[13:22] <jdstrand> smb, lamont: this should definitely go through -security. a -security update regressed xen, so a -security update should fix it. that said, if you want it to have wider testing, we can build it in such a way as to have it copyable to -security but go through -proposed first
[13:24] <jdstrand> smb: I've done boot and qrt tests for -generic and boot and xen tests on -xen for pre6, and it all seems good
[13:24] <lamont> jdstrand: I'm happy with it, osmium is happy with it, though I'd like to see it finish the current build and start a new one or 3 before going +1 all over it
[13:25] <smb> jdstrand, I think one of the ppa builders is a pretty good testing. The only thing we might want to find out is John mentioning some problems with ec2.  I also seem to fight something but that seems to be related to the phase of the sun, luck and using a desktop install on a laptop 
[13:26] <jdstrand> smb: what are you fighting? the network thing?
[13:27] <smb> jdstrand, That (though that was on .73 too) and that this afternoon the boot crashes again in unmap_vmas when doing some hald-addon-dell 
[13:27] <smb> Its the same pre6 kernel that seemed to boot yesterday
[13:28] <jdstrand> smb: hmm
[13:29] <jdstrand> smb: was the unmap_vmas crash with -generic or -xen?
[13:29] <smb> jdstrand, That is with xen (when trying to bring up dom0)
[13:30] <jdstrand> smb: but it isn't a reliable crash?
[13:31] <smb> At the moment it seems relatively reliable. Though one of the boots went past it to hang in graphics. I try to go back to .73 and do a few reboots there
[13:37] <smb> jdstrand, Phew, it seems at this time of day even the old .73 kernel crashes
[13:37] <jdstrand> I'll install ubuntu-desktop on my i386 too
[13:37] <jdstrand> oh, well, no regression :) I'd like to test locally too
[13:38] <smb> No it (luckily) seems not
[13:40] <jdstrand> smb: now, if we start building it soonish, I could maybe get it out today. I realize we want jj-afk's input, but we could start building assuming that he will ack it, with the understanding that we would pull it if he nak'd it. otherwise, it would likely be tomorrow. I'm fine with how you want to handle it
[13:42] <smb> jdstrand, I think we are at least quite positive (now that the old one crashes too) to have at least an improvement. I would say we should at least go ahead and initiate the build, even if we have to abort/throw away the builds.
[13:43] <smb> I will go ahead and make a source package for you
[13:44] <jdstrand> smb: that was my thinking. thanks
[13:56] <akgraner> apw, ping
[13:57] <tgardner> akgraner, he's on vacation for another week
[13:57] <ogra> tgardner, hey
[13:57] <akgraner> tgardner, ahhh ok  - my computer over heating again :-(  he told me to let him know if it keeps happening
[13:58] <tgardner> akgraner, hold it under the kitchen tap for awhile. that'll fix it.
[13:58] <tgardner> ogra, whats up?
[13:58] <smb> We normally suggest the fridge...
[13:58] <akgraner> tgardner, hehe I sure it will one way or another ...
[13:58] <ogra> tgardner, will we get the scurity fixes from kees into omap4 ?
[13:59] <ogra> (we discussed that in a call yesterday and i wasnt sure)
[13:59] <tgardner> ogra, I told kees I would do it when I get the 2.6.35 kernel from TI
[13:59] <akgraner> hehehe - I'll poke around with it some more and get everything documented and wait for apw to return them :-)   Thanks tgardner
[13:59] <ogra> ah, perfect
[13:59] <akgraner> s/them/then
[14:08] <smb> jdstrand, chinstrap:~smb/security has some files waiting for you :)
[14:08] <jdstrand> smb: thanks!
[14:11] <boing00> hi
[14:13] <boing00> is it somehow possible to bind all kernel processes to one core?
[14:13] <jk-> boing00: no, they're mostly per-CPU
[14:14] <boing00> yes I found some exist once per core
[14:14] <boing00> no way to not have that?
[14:15] <boing00> is there a realtime patch maybe?
[14:54] <manjo> sconklin, kiss tickets for the san antonio show in sept is around $300 ... pretty expensive 
[14:55] <sconklin> huh, I wonder if I could still get access. I know that once in the facility I can get to the dressing rooms, because they still have the same security guys and I know them
[15:16] <smb> jdstrand, So at least running a server install, I get no crash _and_ network. Maybe things there get confused by the fact that network is started by NetworkManager later and has no configuration in the usual places
[15:38] <jdstrand> smb: that sounds totally plausible
[15:38] <jdstrand> smb: so the kernel is building
[15:40] <smb> sounds good. Lets see how jj-afk gets along if he comes on and how lamont feels 
[15:47] <jdstrand> smb: also, what do you think about changing the permissions of ~smb/security on chinstrap? the directory is 755, I propse 750, but the group to use is not totally clear. perhaps some kernel-team group? ubuntu-security would need to be added to it though
[15:48] <smb> jdstrand, Doing 750 is simple. But i think that would be ok as none outside should be there
[15:53] <smb> jdstrand, So ok, I made it kernel_devs which you and kees are incidentally already members
[15:54] <jdstrand> smb: sounds perfect
[15:56] <tgardner> smb, sconklin: would one of you review my last Lucid LBM pull request (and get it uploaded). There are some folks waiting on it.
[15:56] <smb> tgardner, I might just have gained a bit of spare time
[15:57] <tgardner> smb, its a total hack (as is most of LBM), but it fixes the atl1c issue
[15:57] <smb> I think I read a bit on it just not the details. Latest atl1c was not recent enough
[15:57] <tgardner> nope
[15:58] <tgardner> bjf[afk], you around yet?
[15:59] <bjf> tgardner: sorry, yes i am
[15:59] <tgardner> we were gonna have a chat about stable stuff, right?
[16:00] <bjf> tgardner: yes, i think sconklin and i are ready
[16:00] <smb> tgardner, Looking only at the packaging change only this looks so much like custom-binaries. And I thought we would be rid of them when hardy goes... :-P
[16:00] <tgardner> smb, I know, ugly as hell
[16:22] <lamont> smb: fwiw, osmium has several builds under its belt at this point with pre6.  +1 from me
[17:08] <jjohansen> smb, jdstrand: when that isn't the networking problem I was having on ec2
[17:09] <smb> jjohansen, We were waiting for your results here, too. Did you have time to look at it again?
[17:09] <jjohansen> smb, jdstrand: I booted server based instances, and instances with the regular kernel would boot, but pre6 would get stuck when they tried to contact ec2-services
[17:09] <jjohansen> smb: not, yet it turned out to be more than a couple hours sleep :)
[17:10] <smb> jjohansen, My problem with network seemed to come from the desktop installation. The server install works good here
[17:10] <jjohansen> smb: I am bundling up the pre security fix kernel for a test now
[17:10] <jjohansen> smb: good to know
[17:10] <jdstrand> networking was solid here as well
[17:10] <smb> My guess is it needs /etc/network/interfaces set up sanely
[17:11] <smb> which is not the case with NetworkManager doing things later
[17:11]  * jjohansen wishes that they would fix network manager to work for console as well
[17:45] <lamont> jjohansen: servers shouldn't need network mangler
[17:46] <jjohansen> lamont: no they shouldn't, but there are cases where desktops fail and networking should just work from the console
[17:48] <lamont> yep
[17:48] <lamont> I would like it if the machine were at least usable remotely before the local user logs in
[17:50] <jjohansen> yeah that is another thing I would like
[17:50] <jjohansen> and I would like wireless to work properly from the console without login too
[18:27] <jjohansen> smb, jdstrand: so the .73 kernel on EC2 is hanging at the same place waiting for ec2-meta data
[18:27] <jjohansen> The kernel definitely boots to that point, and I don't believe the -pre6 kernel is the problem
[18:27] <jdstrand> jjohansen: thanks for testing. I think this means that .75 regressed no more than .77 would on ec2
[18:28] <smb> So again bad but no regresssion after .73
[18:28] <jjohansen> right
[18:28] <jjohansen> so its good to go
[18:28] <jdstrand> smb, jjohansen, lamont: are you guys ok for me to get .77 out then?
[18:28] <smb> ok
[18:28]  * jjohansen needs to figure out what is failing in hardy ec2
[18:28] <jjohansen> jdstrand: ack
[18:29]  * lamont is +1
[18:30] <smb> jdstrand, You, kees and me need probably take some time to think on dapper, jaunty, karmic and lucid (though lucid would get a change through upstream stable as it looks)
[18:32] <jdstrand> smb: sounds fine. kees is traveling today. like we said yesterday, maybe revisit for the next -security update?
[18:36] <smb> jdstrand, That sounds like a plan. We just need to make some decision about how to proceed. In Dapper we likely want the same patches as in Hardy. Lucid would get upstream changes through stable which also include a change to introduce double linked lists in vma structures. This sounds potentially dangerous for Karmic and Jaunty. So maybe we want something in between
[18:36] <jdstrand> smb: ack
[18:37] <jdstrand> I will test the actual builds for hardy after i386 is done. that is likely ~4 hours
[18:38] <lamont> 4 more hours?
[18:38] <smb> jdstrand, Sounds good. I probably will try to be eod at that point today
[18:38] <smb> lamont, Lots of kernels
[18:38] <jdstrand> lamont: there is a fairly good chance I won't get them published tonight do to i386 taking so long and 'real life'. that said, I can pocket copy them to ubuntu-security-proposed or otherwise make them available to you
[18:39] <lamont> jdstrand: I have access to where they're building
[18:39] <jdstrand> oh duh
[18:39] <lamont> being on the team and all
[18:39] <jdstrand> I forgot
[18:39] <jdstrand> hehe
[18:39] <smb> lamont, -rt, -openvz, -xen and the usual -386 and generic and server and virtual....
[18:39] <lamont> mostly as a lurker, to be fair
[18:39] <jdstrand> lamont: well, there you go then :)
[18:40] <jdstrand> smb: just so we are clear-- this was not an ABI bumper, correct?
[18:40] <lamont> jdstrand: you might find better happiness in the future if you manage to nudge the build onto roseapple instead of vernadsky/etc
[18:40] <smb> jdstrand, nope
[18:40] <jdstrand> lamont: I'm not sure how to do that
[18:40] <jdstrand> and by 'not sure' I mean "don't know"
[18:41] <lamont> jdstrand: it involves talking someone into putting i386 on manual and then scoring your build through the roof and then going back to auto
[18:41] <lamont> IOW, fugly pain
[18:42] <jdstrand> heh-- noted
[18:42] <lamont> and should probably only be done when you're totally behind the 8 ball
[18:43] <lamont> and having said that, roseapple joined the game today, after your build started.
[19:21] <slangasek> does anyone here know if the linux-fsl-imx51 kernel package should be kept around for maverick?
[19:21] <slangasek> AFAIK it's not being used for any images this cycle; I'm guessing it should be pruned
[19:22] <slangasek> (the subject has arisen because linux-linaro has just added an imx51 flavor to /its/ builds, and it's all getting to be a few too many kernels, I think)
[19:24] <slangasek> smb: you seem to be the ast uploader of this package (to lucid-security) - do you know or have an opinion?
[19:26] <smb> slangasek, I am not sure about any users here, I would probably ask in mobile and arm. But I would not cry too much if it goes
[19:26] <slangasek> bjf: actually, I see that your kernel meeting notes from yesterday mention fsl-imx51, but I'm not sure how to interpret what's written :)
[19:26] <slangasek> smb: ok
[19:27] <bjf> slangasek: i believe it's just Lucid, we don't have a topic branch for fsl in mav
[19:28] <bjf> slangasek: the meeting notes were referring to on going work in the Lucid fsl banch
[19:28] <bjf> s/banch/branch/
[19:28] <slangasek> bjf: right, the package is automatically carried over to maverick from when the archive opened - and in fact, the version in maverick is missing at least two security updates that are in lucid-updates
[19:28] <slangasek> bjf: oh - I misread the fsl-imx51 header as attached to the line above it, sorry
[19:28] <bjf> slangasek: consensus here seems to be it can be pruned
[19:28] <slangasek> bjf: I was trying to figure out how you would move the mvl-dove branch forward into maverick frsl-imx51! :)
[19:29] <slangasek> bjf: great; I'll double-check with #ubuntu-arm and then do the needful
[19:29] <bjf> slangasek: very carefully
[19:29] <slangasek> bjf, smb: thanks
[19:39]  * smb is out
[20:00]  * ogasawara lunch
[21:05]  * jjohansen -> lunch
[23:16] <lamont> woot!  kernel bulids finished.. <-- jdstrand 
[23:16] <lamont> even ia64 :-p
[23:18] <jdstrand> I unfortunately have to leave in 10 minutes...