[00:19] <plars> join #ubuntu-testing
[15:34] <henkjan> !schedule
[15:59] <kirkland> o/
[15:59] <kirkland> o\
[15:59] <sommer> yo
[15:59] <nijaba> \o
[16:00]  * mathiaz waves
[16:00] <nealmcb> \o
[16:01] <ScottK> o\
[16:01] <mathiaz> let's get the server team meeting started
[16:01] <mathiaz> #startmeeting
[16:01] <MootBot> Meeting started at 10:01. The chair is mathiaz.
[16:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:01] <Koon> o~
[16:01] <nijaba> ~o~
[16:01] <soren> !"#¤
[16:01] <mathiaz> once everyone stopped dancing we can proceed to today's agenda: https://wiki.ubuntu.com/ServerTeam/Meeting
[16:02] <mathiaz> Last week minutes: https://wiki.ubuntu.com/MeetingLogs/Server/20090210
[16:02] <mathiaz> [TOPIC] Update ServerGuide for Jaunty
[16:03] <MootBot> New Topic:  Update ServerGuide for Jaunty
[16:03] <mathiaz> sommer: how is doc.ubuntu.com going?
[16:04] <sommer> mathiaz: well, most of the new sections are done
[16:04] <sommer> mathiaz: and most of the bugs are fixed
[16:04] <sommer> some reviews would be cool :)
[16:05] <sommer> mathiaz: I did have a question about the OpenLDAP DIT?
[16:05] <mathiaz> sommer: https://wiki.ubuntu.com/JauntyServerGuide lists all the sections that needs review
[16:05] <sommer> yep
[16:06] <mathiaz> sommer: what's your question about the DIT?
[16:06] <sommer> mathiaz: is it going to be part of the slapd package?  or I guess how is the base going to be setup?
[16:06] <mathiaz> sommer: for jaunty nothing changes
[16:07] <sommer> mathiaz: because I think it should simplify the ldap section
[16:07] <mathiaz> sommer: I'll try to get a new upstream version of openldap uploaded before FF
[16:07] <sommer> mathiaz: oh, I thought there was going to be something
[16:07] <mathiaz> sommer: well - nothing more than what was already there
[16:07] <mathiaz> sommer: ie a very basic tree structure.
[16:08] <sommer> mathiaz: I see, that works... answers my question, thanks
[16:09] <mathiaz> sommer: great. Anything else apart asking for reviews of the new sections?
[16:09] <sommer> mathiaz: nope, that should be it
[16:10] <mathiaz> sommer: oh - is doc.ubuntu.com up-to-date?
[16:10] <sommer> mathiaz: ah, I don't think it is yet, but I did hear back from mdke and he's working on it
[16:10] <mathiaz> sommer: ok great.
[16:10] <mathiaz> let's move on.
[16:11] <mathiaz> [TOPIC] Postfix and Dovecot integration
[16:11] <MootBot> New Topic:  Postfix and Dovecot integration
[16:11] <ivoks> right on time :)
[16:11] <mathiaz> ivoks: good work on that one.
[16:11] <lamont> \o/
[16:11] <ivoks> mathiaz: it's not done yet :)
[16:11] <mathiaz> ivoks: there are still some things to be fixed
[16:11] <ivoks> mathiaz: we have one bug and couple of issues
[16:11] <mathiaz> A post on the ubuntuserver blog has been published: http://ubuntuserver.wordpress.com/2009/02/13/an-improved-mail-server-stack-in-jaunty-dovecot-and-postfix-integration/
[16:11] <ivoks> i've prepared a debdiff, but i would like a review on it, since this is my first binary-indep package
[16:12] <mathiaz> lamont: ScottK: do you have comments on the new dovecot-postfix package?
[16:12] <ScottK> mathiaz: I haven't had a chance to really look at it.
[16:12] <lamont> ditto
[16:12] <ivoks> don't, untill new version is uploaded :)
[16:12] <mathiaz> ivoks: attach it to a bug, and subscribe ubuntu-main-sponsor to ask for sponsorship
[16:13] <ivoks> will do
[16:13] <mathiaz> ivoks: apart from testing is there anything else to be done on this topic for jaunty?
[16:14] <ivoks> not really
[16:14] <ivoks> there are plans for jaunty+1, but that's another story
[16:14] <ivoks> since we are in FF
[16:14] <mathiaz> ivoks: sure - where are these plan kept?
[16:14] <ivoks> nowhere atm
[16:14] <mathiaz> ivoks: is there a wiki page somehwere?
[16:14] <ivoks> not yet
[16:15] <ivoks> basicaly, integrating amavis with these two
[16:15] <ivoks> and myabe having a 'supported' webmail infrastructure
[16:15] <mathiaz> ivoks: ok - it may be worth creating a wiki page under w.u.c/ServerTeam/MailServer
[16:16] <ivoks> good idea
[16:16] <mathiaz> ivoks: as a braindump page to keep track of interesting ideas
[16:16] <mathiaz> ivoks: just bullet points - the interesting ideas can then be turned into specs for the next cycle
[16:16] <ivoks> right
[16:17] <mathiaz> [ACTION] ivoks to create a wiki page for ideas about improving the mail server task
[16:17] <MootBot> ACTION received:  ivoks to create a wiki page for ideas about improving the mail server task
[16:17] <mathiaz> ivoks: ScottK: anything else to report in the mail server area for Jaunty?
[16:17] <ivoks> it will rock.
[16:18] <ivoks> :)
[16:18] <ScottK> It might be worth a mention that dkim-milter now uses unbound for DNS.
[16:19] <ScottK> Unbound is a relatively new DNS library that supports DNSSEC.
[16:19] <ScottK> Also just as a warning, clamav 0.95 is due out soon.
[16:19] <ScottK> It, of course, breaks all the rdepends.
[16:20] <mathiaz> ScottK: hare you blogged about it? IIRC I saw something mentioning about it
[16:20] <ScottK> Yes
[16:20] <mathiaz> ScottK: it may have been in the changelog though.
[16:20] <ScottK> They promised though that this is the one true interface redesign and they won't have to do it again.
[16:20] <ScottK> They've never promised this before.
[16:20] <ScottK> So expect some post-FF fun with this one.
[16:20] <mathiaz> ScottK: ok - we'll see how things will turn out.
[16:21] <mathiaz> anything else to add on this front?
[16:21] <ScottK> In related news clamav 0.94.2 is now available in hardy-backports
[16:21] <ScottK> We're about ready to push it to dapper-backports too.
[16:21] <ScottK> That's it.
[16:21] <mathiaz> ScottK: great - thanks for the good work!
[16:21] <mathiaz> ivoks: ^^ !
[16:21] <mathiaz> [TOPIC] Power management
[16:21] <MootBot> New Topic:  Power management
[16:21] <mathiaz> kirkland: anything new on this front?
[16:24] <mathiaz> ok - kirkland seems to have lost power
[16:24] <mathiaz> let's move on
[16:24] <mathiaz> [TOPIC] virtualization
[16:24] <MootBot> New Topic:  virtualization
[16:24] <soren> \o/
[16:24] <mathiaz> soren: what's new there?
[16:25] <soren> Lots of stuff going on. We've got a very fresh kvm, libvirt, virt-manager (currently uninstallable due to old virtinst... working on it)..
[16:25] <Brazen> yippee
[16:25] <soren> ...I'm working on some updates for VMBuilder. Among the new things is support for VMWare ESXi.
[16:25] <soren> ..I hope to manage to rework a few things that need some love before FF. One thing I'd like to do is to make it able to build for multiple hypervisors in the same run.
[16:26] <soren> Also, we've been pushing a lot of cloud computing stuff.
[16:26] <soren> A month ago (or thereabouts), I uploaded OpenNebula, and we're currently working hard to get Eucalyptus uploaded before FeatureFreeze.
[16:27] <mathiaz> soren: are there plans to blog about all this new things?
[16:27] <soren> Eucalyptus has a lot of Java dependencies, so it has been a bit of a rough ride, but upstream is very happy to work with us and are making excellent progress.
[16:27] <soren> mathiaz: Just after featurefreeze, yes.
[16:27] <mathiaz> soren: or give an overview about all these new things?
[16:27] <soren> Yes.
[16:28] <soren> I want people to test all of this much more, so I'll be posting about clever ways you can use OpenNebula for testing (I'd like to work with you on that).
[16:28] <mathiaz> soren: awesome - we'll have to wait for next week to get all details then:)
[16:28] <soren> I've been a bit hesitant to blog about Eucalyptus, since it's still vapourware.
[16:28] <soren> But eucalyptus is in the archive now..
[16:29] <soren> Most of it's build-dependencies are, too, so we're inches away from a usable package :)
[16:29] <soren> Koon is doing fantastic work on the Java dependencies.
[16:29]  * soren hugs Koon
[16:29] <soren> s/it's/its/ a few lines ago..
[16:30] <soren> Hmm... I think that's all for now. I'll be blogging about stuff as it becomes available.
[16:30]  * ivoks claps
[16:31] <mathiaz> soren: awesome. Thanks for giving this short status update.
[16:31] <soren> Certainly
[16:31] <nealmcb> wow
[16:31] <sommer> soren: should we have info in the serverguide about the cloud stuff, or is it mainly ec2 at this point?
[16:32] <kirkland> mathiaz: sorry, my network dropped;  back now
[16:33] <soren> sommer: We definitely should.
[16:33] <zul> we cant mention the ec2-ami-tools in the eucalpytus stuff though
[16:33] <soren> sommer: Things should be stabilizing enough within the next week for it to actually make sense to start writing docs for it :)
[16:34] <sommer> soren: sounds good, I'll be patient
[16:35] <mathiaz> ok - let's move on then
[16:35] <sommer> zul: gotcha, we'll just make it generic
[16:35] <mathiaz> since we'll have to wait for FF to get a good overview of the new virtualization features in jaunty :)
[16:35] <mathiaz> [TOPIC] Power management
[16:35] <MootBot> New Topic:  Power management
[16:35] <mathiaz> kirkland: now that you're back - any news on this front?
[16:36] <kirkland> mathiaz: i have pwrkap and powerman are two new packages, added to the archive today
[16:36] <kirkland> mathiaz: powernowd has been added to the server seed, to enable cpu freq scaling by default on ubuntu servers
[16:37] <kirkland> mathiaz: pm-utils and ethtool have been added to the server-ship seed, which are what's needed for suspend/hibernate and resume by WoL
[16:37] <kirkland> mathiaz: as well as wakeonlan, promoted to main, and on the server-ship seed
[16:37] <kirkland> mathiaz: i need to write up some instructions on how to test this
[16:37] <kirkland> mathiaz: i'm interested in feedback on hardware where suspend/hibernate can be verified as working
[16:38] <kirkland> mathiaz: hw which is *not* working, i'm interested in that too... but we probably won't focus on fixing those until next cycle
[16:38] <mathiaz> kirkland: great - so the current plan for jaunty is to have powernowd installed by default and all the other suspend/hibernate components available from the cd?
[16:38] <kirkland> mathiaz: correct
[16:38] <kirkland> mathiaz: suspend is really cool, btw.
[16:39] <kirkland> mathiaz: for my home network, i created a ssh wrapper, which pings first to see if alive
[16:39] <kirkland> mathiaz: if not, sends a wakeonlan, waits 3 seconds, and ssh's again
[16:39] <kirkland> mathiaz: my machines wake from suspend when i need them :-)
[16:39] <nealmcb> sweet
[16:39] <kirkland> mathiaz: and it only takes about 3 seconds for them to wake up which is lot faster than ~60seconds to boot
[16:40] <kirkland> mathiaz: i put a power meter on them too
[16:40] <mathiaz> kirkland: awesome!
[16:40] <kirkland> mathiaz: running, they're about 50W-80W (depending on cpu freq, load, hd, cd, etc)
[16:40] <kirkland> mathiaz: suspended, they're at about 11w
[16:41] <mathiaz> kirkland: that seems like a good topic for a blog post
[16:41] <mathiaz> kirkland: a good use case for supsend/resume for servers
[16:41] <kirkland> mathiaz: cool, will do.
[16:42] <mathiaz> [ACTION] kirkland to blog about using suspend/resume for servers
[16:42] <MootBot> ACTION received:  kirkland to blog about using suspend/resume for servers
[16:42] <nealmcb> ubuntu - saving energy and the climate!
[16:42] <kirkland> penguins
[16:42] <nealmcb> lol
[16:42] <Brazen> I don't suspend, but I do set hdparm to power down the harddrives...
[16:43] <ivoks> my server doesn't do suspend :(
[16:43] <mathiaz> ivoks: did you report it to kirkland ?
[16:43] <ivoks> kirkland: fix it
[16:43] <ivoks> mathiaz: just did :)
[16:44] <kirkland> ivoks: let me set up a wiki page to track this
[16:44] <mathiaz> kirkland: how do you keep track which hw is works/doesn't?
[16:44] <kirkland> ivoks: i'll ping you to fill in your info
[16:44] <ivoks> kirkland: sure
[16:44] <kirkland> mathiaz: i'm going to do it by wiki, for starters
[16:44] <mathiaz> kirkland: ok - one wiki page seems a good place to start.
[16:44] <kirkland> mathiaz: i'll link off of the laptop suspend page
[16:45] <mathiaz> kirkland: ah ok - there is a suspend page for laptop already.
[16:45] <ivoks> another way of waking up server is IPMI
[16:45] <Brazen> There's also multi-core power savings: 'echo 1 > /sys/devices/system/cpu/sched_mc_power_savings'
[16:45] <ivoks> any chance to see ipmitool in main?
[16:45] <Brazen> and laptop-mode, which I do use on my server: 'echo 5 > /proc/sys/vm/laptop_mode'
[16:46] <kirkland> ivoks: i'm not too familiar with ipmi
[16:46] <ivoks> dell servers support ipmi; i'm not sure about wake on lan
[16:46] <mathiaz> ivoks: ipmitools aren't part of openipmi?
[16:46] <ivoks> mathiaz: no, ipmitool can use openipmi, but doesn't depend on it (it can use real hardware)
[16:46] <mathiaz> apparently no
[16:47] <ivoks> openipmi is just support for ipmi on local machine
[16:47] <mathiaz> ivoks: does ipmitool provide cmd lines that openipmi can't?
[16:47] <ivoks> ipmitool can be used to connect to other machines
[16:47] <ivoks> mathiaz: yes; serial over lan, for example
[16:48] <mathiaz> nijaba: would ipmitool be useful in main?
[16:48] <ivoks> with openipmi you can't do anything outside local machine
[16:48] <ivoks> they don't exclude each other
[16:48] <nijaba> mathiaz: i would definitely think so
[16:49] <mathiaz> ok - we can always move ipmitool to main after FF
[16:49] <mathiaz> to get started, a MainInclusionReport has to be written
[16:49] <ivoks> right, but it's not being developed for 2 years :/
[16:50] <mathiaz> ivoks: hm - right.
[16:50] <mathiaz> ivoks: if upstream is not very active it may not be worth
[16:50] <mathiaz> ivoks: and we can't really do anything about it :/
[16:50] <ivoks> true
[16:50] <ivoks> sorry, my bad
[16:50] <ivoks> there are new releases
[16:50] <ivoks> http://sourceforge.net/projects/ipmitool/
[16:50] <MootBot> LINK received:  http://sourceforge.net/projects/ipmitool/
[16:50] <mathiaz> ivoks: anyway - we can always think about it after FF
[16:50] <ivoks> ok
[16:51] <mathiaz> [TOPIC] Open Discussion
[16:51] <MootBot> New Topic:  Open Discussion
[16:51] <mathiaz> anything else to add?
[16:52] <sommer> mathiaz: there was that reply about an Ubuntu Directory Service
[16:53] <mathiaz> sommer: right - I was going to reply to point out to the ubuntu-directory@ ml list and LP team
[16:53] <sommer> ah, that works :)
[16:53] <mathiaz> sommer: and also mention that we're about to enter FF so now is not the most appropriate time to start a discussion for jaunty
[16:55] <sommer> true... I didn't have anything else
[16:56] <mathiaz> ok - let's move on to the last item on the agenda:
[16:57] <mathiaz> [TOPIC] Agree on next meeting date and time
[16:57] <MootBot> New Topic:  Agree on next meeting date and time
[16:57] <mathiaz> next week, same time, same place?
[16:57] <ivoks> +
[16:57] <sommer> sure
[16:59] <mathiaz> ok - then.
[16:59] <mathiaz> see you all next week, same time, same place
[16:59] <mathiaz> get ready for FF and make jaunty rock!
[16:59] <mathiaz> #endmeeting
[16:59] <MootBot> Meeting finished at 10:59.
[16:59] <nijaba> thanks for hosting mathiaz
[17:00] <sommer> later all
[17:01]  * smb_tp settles down
[17:01] <pgraner> Hello All! Time for the kernel team meeting
[17:01] <pgraner> #startmeeting
[17:01] <MootBot> Meeting started at 11:01. The chair is pgraner.
[17:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[17:01]  * rtg_ waves
[17:01]  * apw phases in ...
[17:02]  * lieb here
[17:02]  * amitk arriveth
[17:02] <pgraner> [TOPIC] Security & bugfix kernels
[17:02] <MootBot> New Topic:  Security & bugfix kernels
[17:02] <smb_tp> Greg keeps me busy.
[17:02] <pgraner> Intrepid ....
[17:02] <pgraner> smb_tp: how are we looking?
[17:03] <smb_tp> Anyhow, for Intrepid I am done with .17 and try to get this uploaded next day before Greg comes with .18
[17:03] <pgraner> smb_tp: when do we hit the 4 month cutoff for Intrepid?
[17:04] <smb_tp> End of this month
[17:04] <smb_tp> I'd say.
[17:04] <pgraner> smb_tp: ok, so .18 might not make it then...?
[17:04]  * rtg_ agrees
[17:04] <apw> i think we mooted by beta freeze
[17:04] <smb_tp> Not completely no. Depends on the time scale
[17:04] <pgraner> smb_tp: how does Hardy look?
[17:05] <smb_tp> Also near upload. I added a few things including some xen patches and the vmware tsc updates
[17:05] <smb_tp> So this time both hardy and intrepid will bump abi
[17:05] <cking> sorry, running late
[17:05] <smb_tp> Intrepid again
[17:06] <smb_tp> Unfortunately I am still fighting to catch the Aspire bug on Hardy, but this will have to get in after that. Actually by the nature of it it might just resolve itself
[17:06] <pgraner> Anythings else for this topic?
[17:07] <pgraner> [TOPIC] Jaunty
[17:07] <MootBot> New Topic:  Jaunty
[17:07] <pgraner> Reminder Feature Freeze is the 19th (this week)
[17:08] <pgraner> I'd like to do a quick rundown of the big features to see where we are:
[17:08] <pgraner> lieb: kerneloops & crashdump?
[17:08] <lieb> have to test running non-root.  no one else does that config.
[17:09] <lieb> crashdump, its a bigger problem req updates to 3 packages
[17:09] <lieb> turns out the kexec kernel also oom panics
[17:09] <lieb> ;(
[17:10] <pgraner> lieb: status of MIR?
[17:10] <apw> how big is the 'crash dump window' by default?
[17:10] <lieb> pgraner, awaiting my test results +debdiff
[17:11] <lieb> apw, I'd have to check.
[17:11] <pgraner> lieb: we are coming down to the wire, we need to get this locked up ASAP. This should be your #1 priority
[17:11] <pgraner> lieb: do you need help?
[17:11] <lieb> it is.  the kexec stuff will probably not make it due to too many packages
[17:12] <lieb> the kerneloops stuff should be settled today once I do web sumit testting to confirm
[17:12] <pgraner> lieb: what packages specifically needs to be updated?
[17:13] <lieb> no more code, just re-working the debian package to ubuntu (init scripts) cuz they don't do it either
[17:13] <pgraner> lieb: is that something we can get the foundations team to help with?
[17:13] <lieb> wrt kerneloops, just the one.  wrt kexec, the kernel (or whatever configs the kdump image), makedump
[17:13] <lieb> crash, and (possibly) kexec-tools
[17:14] <lieb> pgraner, maybe but what is really needed is per the uds topic, these tools/daemons need closer proj mgmt coupling w/ the kernel
[17:15] <lieb> I mentioned that at the sprint but I haven't had time to compose the web page yet
[17:15] <apw> we arn't going to change the coupling at this late stage in the jaunty cycle i don't recon
[17:15] <pgraner> lieb: I'm having a hard time understanding why this is so difficult, we can take this offline\
[17:15] <lieb> apw, that is true.
[17:15] <lieb> pgraner, ok
[17:16] <pgraner> apw: how are we on suspend/resume?
[17:16] <apw> we are starting to get some real user reports now
[17:16] <apw> i am monitoring those separatly from the normal bugs
[17:17] <apw> and trying to get some feedback to every one
[17:17] <apw> there is a bunch of people who are reporting things because apport
[17:17] <apw> woke up, but who don't really know what it means.  not sure
[17:17] <apw> how we will handle the ones where they arn't capable of helping us yet
[17:17] <pgraner> did you notice an uptick once it hit planet.ubuntu?
[17:17] <apw> was that what it wa
[17:18] <apw> was, i am also seeing people sliding over to jaunty
[17:18] <apw> in general and triggering the reports
[17:18] <apw> so far its about 5 a day
[17:18] <pgraner> good deal
[17:18] <apw> i'll have a better feel by the end of the week
[17:18] <apw> we have done some more work on the apport support
[17:18] <apw> to get more information from the users system without needing
[17:19] <apw> to talk to them, and also helping make the reports easier to sift
[17:19] <pgraner> apw: great for next week can you give us a rundown of what the prob look like and how many etc...?
[17:19] <apw> ogasawara, i should note that the bugs now have apport-kerneloops, resume and _one_of_ suspend or hibernate now
[17:19] <apw> pgraner, sure thing, most right now are getting a cut-n-paste response
[17:19] <ogasawara> apw:  good, that'll make searching easier
[17:19] <apw> as they have 0 information on what they were doing.  whenwe have interacted with a few
[17:20] <apw> more we'll know better
[17:20] <pgraner> apw: ack, good deal
[17:20] <cking> apw, you capturing hibernate issues - i thought it was just suspend/resume?
[17:20] <apw> the testing stuff is just suspend, but the apport stuff detects both
[17:20] <apw> and differentiates them in the bugs as reported (now)
[17:20] <cking> ahah
[17:20] <pgraner> apw: one more... vanilla kernel builds... what the status, and how are we on ppa hosting?
[17:20] <apw> i am seeing an uptick in those reports
[17:21] <apw> vanilla builds are now up to date, latest of each tree is built
[17:21] <rtg_> we never planned to PPA host them.
[17:21] <apw> in the ~apw version on kernel.  the old one on people now points there
[17:21] <pgraner> rtg_: sabdfl wants them in a ppa
[17:21] <apw> rtg is now testing the more official kernel-ppa user for them
[17:21] <pgraner> rtg_: for the ease of end user testing
[17:21] <apw> i haven't had time to test loading them into a PPA yet
[17:22] <rtg_> hmm
[17:22] <apw> but the thought there was to see if we could keep just the latest of each in a PPA
[17:22] <apw> not try anything clever to get them all in
[17:22] <rtg_> apw: in order to do so, we have to upload a source package
[17:22] <apw> but that is not started yet
[17:22] <apw> rtg_ yeah, but with the lpia experience under my belt, i think i know waht needs twiddling
[17:23] <apw> to get at least one of each into a ppa.  anyhow, we committed to trying it and i have that on my todo
[17:23] <apw> hope to be able to report on that next week
[17:23] <rtg_> its the package namig thats gonna be  PITA
[17:23] <apw> yes.  i think as long as we only keep the latest per release
[17:23] <apw> ie a .24 in hardy, a .27 in intrepid and a .28 in jaunty
[17:23] <apw> then we may be able to shove them all into a ppa
[17:24] <apw> beyond that, you know what you are doing and can install a .deb
[17:24] <apw> from the kernel-ppa web site
[17:24] <rtg_> k
[17:24] <apw> as i say its got to be investigated, and it may be
[17:24] <apw> 'to do that we need these 3 things from a PPA please'
[17:25] <apw> so it may be a KK think
[17:25] <apw> thing
[17:26] <rtg_> apw: we're also gonna have to get some storage exceptions. these kernels start to eat a lot of space
[17:26] <pgraner> [TOPIC] Jaunty Bugs
[17:26] <MootBot> New Topic:  Jaunty Bugs
[17:26] <pgraner> ogasawara: what are the top ones this week?
[17:26] <apw> rtg_, yeah speacially as we have had to keep the source
[17:26] <ogasawara> so the majority are from previous weeks . . .
[17:27] <ogasawara> from last week bug 326891, bug 255886, and bug 323256 - all got feedback
[17:27] <apw> we didn't make much dent in the previous 2 weeks worth which dropped week-1
[17:28] <smb_tp> The e1000e is looked after by inter and can be worked around
[17:28] <smb_tp> intel, even
[17:29] <ogasawara> there are some older ones marked as High:
[17:29] <ogasawara> bug 323134
[17:29] <ogasawara> ogra confirmed though that if he disabled CONFIG_BLK_DEV_SR oops went away
[17:29] <pgraner> ogasawara: are we tagging the arm bugs differently?
[17:30] <ogasawara> pgraner: I haven't been but can start
[17:30] <apw> i do think it would helpful to have them marked
[17:30] <pgraner> ogasawara: amitk would that help you?
[17:30] <ogra> ogasawara, thats fixed partially, amitk made it a module  ... though now it oopses if the module is loaded
[17:30] <ogra> so i think we need to drop it completely
[17:30] <amitk> pgraner: yes it would help to have arm bugs tagged separately
[17:31] <amitk> ogra: noted
[17:31] <apw> ogasawara, could we colour them different or something for background
[17:31] <ogasawara> apw: yup, am planning on coloring regressions already, so would be a similar change
[17:31] <apw> always one step ahead of me
[17:31] <amitk> or editing the summary to add [arm]?
[17:32] <ogasawara> amitk: I'll edit the summary/title and tag them "arm"
[17:32] <amitk> ogasawara: thanks
[17:32] <ogasawara> listing just a few other bugs . . . bug 322879 is another 2.6.27-11 regression
[17:32] <ogra> amitk, you shouldnt say [noted] .... you should say ogra you goddamn slacker, get your ass up and write that in the bug :P
[17:33] <ogasawara> along with bug 319840 (hardy regression)
[17:33] <amitk> ogra: whatever you said ^^^^
[17:33] <amitk> :)
[17:33] <ogra> :)
[17:34] <pgraner> ogasawara: are the bugs assigned to individuals are still with kernel-team?
[17:34] <apw> i wonder if there is milage to keeping the regressions in a new list with the this weeks ones, or always keep them on 'this week'
[17:34] <apw> so they don't slide down and get lost
[17:34] <apw> keeping them on 'this week regardless of week might work nicly
[17:35] <pgraner> apw: good point
[17:35] <ogasawara> pgraner: bugs are no longer assigned to kernel-team, and is currently the devs responsibility to take ownership (is assign it to themselves)
[17:35] <ogasawara> apw: I was thinking it would be better to pull regressions out into their own section
[17:35]  * pgraner passes on ogasawara's reminder to take ownership of the ones she put out today :-)
[17:35] <apw> ogasawara, that would work just as well as long its at the top
[17:36] <apw> they are the most important bugs for smb_tp and his kin
[17:36]  * ogasawara nods
[17:36]  * smb_tp agrees
[17:36] <pgraner> ogasawara: Anything else on bugs?
[17:36] <ogasawara> pgraner: there are few other high ones but I want to get them to test latest Jaunty first.  I'll raise them in next weeks meeting if necessary.
[17:37] <pgraner> ogasawara: ack, thanks
[17:37] <pgraner> Moving on then
[17:37] <pgraner> Since sconklin is out today we will skip LPIA, if anyone has questions or issues take it to the list pls...
[17:37] <pgraner> amitk: armel ... how goes it?
[17:38] <pgraner> [TOPIC] armel
[17:38] <MootBot> New Topic:  armel
[17:38] <amitk> versatile and iop4xx (slug) are now working
[17:38] <amitk> ogra beat me into fixing the kernels for both
[17:38] <pgraner> amitk, ogra: do we have instructions for loading the image up anywhere? I have a few slugs I could test
[17:39] <amitk> I've left iop32x and orion5x flavours as 'don't cares' for now since there isn't a whole lot of community
[17:39] <pgraner> amitk: ACK
[17:39] <amitk> pgraner: ogra is doing final testing now and should write up a wiki page soon
[17:39] <amitk> that's it from me
[17:40] <pgraner> ogra: let me know when you have it done :-)
[17:40] <pgraner> amitk: great thanks
[17:40] <pgraner>  [TOPIC] Open discussion
[17:40] <pgraner> [TOPIC] Open discussion
[17:40] <MootBot> New Topic:  Open discussion
[17:40] <rtg_> CRDA will start appearing with the latest linux-meta upload. Everyone should whine if their wireless croaks.
[17:40] <pgraner> rtg_: brace for impact :-)
[17:40] <rtg_> no, bend over and spread 'em
[17:41] <ogra> pgraner, prob is that OOM kicks in midway through the installer
[17:41] <pgraner> ogra: ouch
[17:41] <ogra> the kernels boot though, but iÄm still trying to determine how to make d-i work in 30M
[17:41] <rtg_> ogra: use less memory.
[17:41] <ogra> or how debian even does it
[17:42] <ogra> rtg_, :P
[17:42] <pgraner> ogra: just put it on a diet
[17:42] <pgraner> Anything else?
[17:42] <pgraner> I'll take the silence as a no... in that case...
[17:43] <pgraner> apw: both rtg & I will be traveling next Tues can you run the meeting?
[17:43] <apw> sure
[17:43] <pgraner> [ACTION]apw to run next meeting
[17:43] <MootBot> ACTION received: apw to run next meeting
[17:44] <pgraner> In that case same day, time & channel next week.
[17:44] <pgraner> Thanks everyone!
[17:44] <apw> tll then
[17:44] <amitk> bye
[17:44] <pgraner> #endmeeting
[17:44] <MootBot> Meeting finished at 11:44.