[02:32] <phillw> skaet: I hope that email is okay, please feel free to add information to it and correct any inaccuracies.
[02:33] <phillw> oops, wrong channel
[16:00] <Daviey> Hola!
[16:00] <jimbaker> hi!
[16:00] <Daviey> Ursinha: are you chairing ?
[16:01] <arosales> Hello
[16:01] <smb> \p
[16:01] <jamespage> o/
[16:01] <Daviey> Did Ursinha chair last week?
[16:01] <jimbaker> m_3_ chaired last week
[16:02] <m_3_> hi
[16:02]  * m_3_ finger on tip of nose
[16:03] <arosales> Ursinha: you available to chair this week?
[16:03] <Daviey> Seems she is AWOL.  jimbaker looks like it might be you
[16:03] <Daviey> is that ok?
[16:03] <jimbaker> Daviey, oh sure, if someone wants to guide me
[16:04] <arosales> jimbaker: commands to follow are at https://wiki.ubuntu.com/ServerTeam/Meeting/IRCCommands
[16:04] <jimbaker> where's the guide to chairing?
[16:04] <Daviey> https://wiki.ubuntu.com/ServerTeam/Meeting <- agenda
[16:04] <arosales> we'll be glad to help with content :-)
[16:04] <jimbaker> ok... well here it goes
[16:04] <jimbaker> #startmeeting ubuntu-server-team
[16:04] <meetingology> Meeting started Tue Sep 25 16:04:44 2012 UTC.  The chair is jimbaker. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:04] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:04] <adam_g> o/
[16:05] <jimbaker> #topic Review ACTION points from previous meeting
[16:05] <Daviey> (m_3, were there any actions last week?)
[16:06] <jimbaker> jamespage, you were to look into aligning release team and server team trackign reports?
[16:06] <arosales> our logs are looking a little behind https://wiki.ubuntu.com/MeetingLogs/Server
[16:06] <jamespage> still looking at two reports - that can be dropped
[16:06] <jimbaker> (i'm just following ye old cut & paste here...)
[16:06] <arosales> jimbaker: thats the right direction :-)
[16:07] <jimbaker> were there any other action points i should be aware of?
[16:07] <jimbaker> seeing none...
[16:07] <zul> heylo
[16:08] <jimbaker> #topic Quantal Development
[16:08] <m_3_> Daviey: yes... don't know where they are though
[16:08] <jimbaker> arosales, you're right, the logs are not there from the last 2 meetings
[16:09] <arosales> logs from previous meeting are at http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-09-18-16.07.html
[16:09] <m_3_> did the meeting chair need to do something to make that happen?  #fail
[16:09] <arosales> or http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-09-18-16.07.moin.txt
[16:09] <rbasak> We need a checklist for meeting chairs to follow
[16:09] <arosales> jamespage look into running server with no elbow-room
[16:09] <rbasak> At the moment I get the impression that everyone does something slightly different
[16:09] <hallyn> we have one
[16:09] <arosales> https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#Team_policy under "IRC"
[16:09] <m_3_> it was great copy/paste command cheatsheet (thanks serge!)
[16:10] <arosales> rbasak: ^
[16:10] <rbasak> Aha. thanks!
[16:10] <jimbaker> rbasak, that's the listing i'm following
[16:10] <arosales> so to back up one minute before quantal development
[16:10] <Daviey> Anyone would think this is the first time we've done this....
[16:10] <arosales> I think we covered jamespage to look into aligning release team and server team trackign reports
[16:10]  * m_3_ whistles innocently
[16:10] <arosales> jamespage: any update on running server with no elbow-room
[16:11] <arosales> and investigate minimum memory requirements for i386 and amd64 server installs
[16:11] <jamespage> arosales, lots of analysis of actuall install sizes - things have def grown
[16:11] <jamespage> I'm going to request a document update that they propose we discuss the size targets at UDS
[16:11] <jamespage> that/then
[16:12] <jamespage> did any of that make sense?
[16:12] <jimbaker> jamespage, made eminent sense to me
[16:12] <jamespage> 1. Update docs to align with current size of installs
[16:12] <jamespage> 2. discuss at UDS if this needs attention
[16:13] <arosales> jamespage: do we need to continue investigating min memory for server installs?
[16:13] <jamespage> arosales, I think cjwatson is looking at that
[16:13] <jamespage> again I don't really have any objection to increasing the mins in the docs
[16:14] <jimbaker> jamespage, ok. what about bug 1049582?
[16:14] <arosales> jamespage: ok so perhaps tie that into the doc BP.
[16:14] <jamespage> testing a fix ATM
[16:14] <cjwatson> jamespage: yeah, got a kanban card for that which has pretty much risen to the top of my stack
[16:14] <cjwatson> probably won't fit into b2
[16:15] <jamespage> cjwatson, I don't think thats an issue
[16:15] <jamespage> (that it won't fit in b2)
[16:15] <cjwatson> I have an objection to increasing the minima in the docs before I've had a chance to review and adjust the limits in the software
[16:15] <cjwatson> fwiw
[16:15] <cjwatson> because the latter will likely affect the former
[16:15] <Daviey> cjwatson: Do you have an ETA?
[16:16] <cjwatson> this week
[16:16] <cjwatson> (since I anticipate lots of interruptions from b2)
[16:16] <Daviey> super
[16:16] <Daviey> thanks
[16:17] <jimbaker> any other updates on quantal dev? (i will go next otherwise on juju bugs)
[16:18] <jimbaker> so we have 3 critical bugs in progress on juju, https://bugs.launchpad.net/juju, that i'm working on
[16:19] <SpamapS> https://launchpad.net/juju/+milestone/0.6 gives a nice overall picture of the target release we have
[16:19] <jimbaker> i have identified the underlying problem for 2 out of 3 (openstack token expiry, relation state not found) and the third looks similar to a bug i fixed in juju in the past
[16:19] <SpamapS> (which, btw, was due yesterday)
[16:19] <SpamapS> jimbaker: can you mark those as In Progress if you are indeed working on them?
[16:20] <SpamapS> I plan to start dropping anything not In Progress tomorrow.
[16:20] <jimbaker> SpamapS, in the sense of, i'm working on too many things, yes :)
[16:20] <jimbaker> but i will reprioritize them so we can hit that deadline, nothing is big
[16:22] <SpamapS> jimbaker: we already missed the deadline.. we need to land and ship now and also apply for a FFE for quantal
[16:23] <jimbaker> SpamapS, understood
[16:23] <jimbaker> any other release bugs we should be considering at this time?
[16:24] <hallyn> qxl driver
[16:24] <hallyn> don't think a bug has been opened yet, but i'll work on it this afternoon (after meeting)
[16:24] <hallyn> stgraber found that qxl drive is not working right in quantal dvd image
[16:24] <SpamapS> there's a really nasty bug in lxc
[16:24] <hallyn> oh?
[16:24] <SpamapS> we talked about it yesterday
[16:25] <SpamapS> NS refcount thing
[16:25] <hallyn> oh.  that's not in lxc
[16:25] <SpamapS> when it hits, you are screwed, LXC no longer works and you can't even properly reboot
[16:25] <hallyn> smb is helping coolonely to look into it
[16:25] <SpamapS> sorry
[16:25] <SpamapS> kernel
[16:25] <smb> SpamapS, yep
[16:25] <hallyn> we can hopefully get an update ina few mins :)
[16:25]  * SpamapS considers it LXC since LXC is what makes it happen
[16:25] <hallyn> so would vsftpd
[16:26] <smb> hallyn, Yes insofar that I cannot say more right now as I just started to think about it today
[16:26] <jimbaker> good to know we are finding root causes :)
[16:26] <hallyn> smb: ok
[16:27] <jimbaker> hallyn, so maybe action item you will file the qxl bug?
[16:27] <hallyn> jimbaker: k with me
[16:28] <hallyn> and hopefully resolve it too :)
[16:28] <jimbaker> #action hallyn files and ideally resolves qxl bug... all in the same day!
[16:28] <meetingology> ACTION: hallyn files and ideally resolves qxl bug... all in the same day!
[16:29] <hallyn> me and my big mouth
[16:29] <jimbaker> SpamapS, same with the lxc bug, so we know it's linked to the namespace (i take it) refcounting?
[16:29] <hallyn> jimbaker: that has open bug already, on kernel team's hotlist
[16:29] <smb> bug There are currently (at least) two design/technical decisions which have a quite bad impact on running Ubuntu desktop in a virtual machine:
[16:29] <smb> 1) Dropping unity2d in favour of unity+llvmpipe. Since there is no way (at least none that is easy to find) to disable playful effects this puts a considerable stress on the emulated cpu(s). On my desktop, which may not be state of the art but used to be usable for running unity2d desktops in VMs, doing even simple tasks is painfully slow. For example it takes about 3s(!) from when a window begins to fade in until it can be used. And the same
[16:29] <smb>  when minimizing. On that machine I also see a lot of X crashes which might be related to overwhelming the cpus (bug 1056080) since a faster machine does not seem to suffer that badly.
[16:29] <smb> 2) Adding the Amazon search to the dash search (again without any reasonably easy way to disable this). This further puts stress on the cpu(s) and on the same desktop every keypress is delayed about one second (at least). It also adds to network usage (not to mention any privacy or potential parental control issues).
[16:29] <smb> Those together currently make my experience rather bad. To get anything done within the desktop vm I seem to drag my feet through a pool of mud. And that is just one VM running. Anybody hosting virtual desktops will rip out lots of hair and likely leave for at least the ubuntu-gnome-desktop (classic unaccelerated) which would be rather sad and completely unhelpful in those cases where the ubuntu desktop was used in a VM for testing.
[16:29] <smb> I can understand that getting rid of a duplicated desktop framework will help to focus on the main unity project. But I think in that case there really should be options that allow to reduce the graphical overhead and the amount of feature overhead in a more user-friendly way.
[16:29] <smb> oops
[16:29] <smb> damn multi buffers
[16:30] <smb> bug 1021471
[16:30] <jimbaker> smb, thanks for the link. actually i was thinking that SpamapS might put it in as a juju lxc provider bug since that's where we are observing it, so we can track as being impacted
[16:31] <SpamapS> smb: thanks for sharing tho!
[16:31] <utlemming> smb: I have follow-up on the cloud images
[16:31] <smb> no worries... sorry for the oversharing
[16:31] <SpamapS> jimbaker: nah, its all in the kernel.. I don't think we need to track it.
[16:31] <Daviey> a problem shared is a problem halved
[16:31] <utlemming> from last week -- about Unity working on the Desktop Images
[16:31] <jimbaker> SpamapS, cool
[16:32] <utlemming> short story: the Desktop Cloud images haven't had a desktop sharing solution since Oneiric. And Unity does not work on the desktop images.
[16:32] <utlemming> er -- unity does not work on the Desktop Cloud Images
[16:32] <jimbaker> utlemming, is this something actionable as a quantal release bug?
[16:33] <utlemming> jimbaker: no. The desktop cloud images are not supported. And for R, we're going to have a discussion about them.
[16:33] <smb> utlemming, As you probably noted from the involuntary ranting above I got somewhat depressed about the current situation running in a VM.
[16:33] <utlemming> smb: I noticed :)
[16:33] <jimbaker> utlemming, ok, just checking
[16:34] <jimbaker> any other bugs to discuss before blueprints subtopic?
[16:34] <jimbaker> ...
[16:34] <jimbaker> #subtopic Blueprints
[16:34] <jimbaker> #link http://status.ubuntu.com/ubuntu-quantal/ubuntu-server.html
[16:35] <Daviey> gah, wrong link - try http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-servercloud-overview.html
[16:37] <jimbaker> Daviey, thanks...
[16:38] <jimbaker> zul, any updates on https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-openstack-qa ?
[16:38] <zul> jimbaker: no
[16:39] <jimbaker> m_3_, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices ?
[16:39] <jamespage> zul, adam_g: suggest we get together and decide what is going to happen for this cycle
[16:39] <zul> jamespage: sounds like a plan
[16:39] <jimbaker> m_3_, seems like there has been been some good mailing list activity re best practices
[16:39] <m_3_> looks good afaik
[16:39] <jimbaker> as well as documenting in the spreadsheet that jcastro put together
[16:40] <m_3_> some local container bugs outstanding (they'll be postponed most likely)
[16:40] <jimbaker> m_3_, right, just looks like this bp might need some corresponding updating
[16:40] <m_3_> ack
[16:41] <jimbaker> rbasak, any updates on https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-arm-deployment ?
[16:41] <rbasak> No updates. I'm still working on MAAS
[16:42] <jimbaker> rbasak, understood
[16:43] <jimbaker> SpamapS, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charmstore-maintenance, maintainer assignment is more or less done in place right?
[16:43] <SpamapS> Yes
[16:44] <SpamapS> updating
[16:44] <jimbaker> SpamapS, thanks!
[16:44] <jimbaker> i'm just looking at the clock and your novice chair is seriously running out of time here. everyone else, please see if you can update your BPs
[16:45] <jimbaker> any other BPs that should be discussed at this time? otherwise... moving on
[16:45] <jimbaker> #topic Ubuntu Server Team Events
[16:46] <jimbaker> so i had a good presentation at the boulder big data user meetup - http://www.meetup.com/Boulder-Denver-Big-Data/events/81123992/
[16:46] <jimbaker> 75 people or so showed up, something like 4 hours all together including presentation and questions before, after
[16:47] <arosales> Surge coming up on the 27th
[16:47] <jimbaker> arosales, who will be at surge?
[16:47] <SpamapS> hazmat
[16:47] <Daviey> Oct 15 -> 18. Many Ubuntu Server dev's will be at ODS - http://www.openstack.org/summit/san-diego-2012/
[16:48] <SpamapS> Right, come to san diego, enjoy the beer. :)
[16:48] <jimbaker> SpamapS, it sounds like a very good plan :)
[16:48] <Daviey> Oct 29 -> 1st Nov.. UDS in Copenhagen.. Many Openstack dev's attending.
[16:48] <Daviey> (see what i did there? :)
[16:48] <zul> surge?
[16:49] <jimbaker> http://omniti.com/surge/2012
[16:49]  * Daviey googles on behalf of zul
[16:49] <Daviey> http://omniti.com/surge/2012
[16:49] <hallyn> we need a 'tech conference' lens in the dash
[16:49] <smb> not more lenses... o_O
[16:49] <jimbaker> oh sure, http://lmgtfy.com/?q=surge :)
[16:50] <Daviey> jimbaker: can you action hallyn to make a lens ?
[16:50] <hallyn> NO
[16:50] <jimbaker> Daviey, i could in fact do that... it would be very cruel however
[16:50] <hallyn> s'ok i can delegate with the best of em
[16:50] <jimbaker> maybe what we really want a lens connected to http://lmgtfy.com/
[16:50] <Daviey> meh, logs can be edited to add it regardless.
[16:51] <hallyn> eh that looks nice
[16:51] <jimbaker> #topic Weekly Updates & Questions for the QA Team (hggdh)
[16:51] <hallyn> oh no it wants js, nm
[16:51] <hggdh> hello
[16:51] <hggdh> only thing to note is... it is beta2 week, so help testing is very welcome :-)
[16:52] <jimbaker> hggdh, thanks for that update
[16:52] <jimbaker> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:52] <smb> Yo!
[16:52] <smb> * I had been looking at bug 1023755. While I can see one potential
[16:52] <smb>   problem, I could not reproduce the issue with the provided method.
[16:52] <smb> * Trying to also look into bug 1021471 this week. But wanted to
[16:52] <smb>   complete other tasks before.
[16:52] <smb>   Eric Biederman indicated two (inline) functions to check for
[16:52] <smb>   balancing. Unfortunately those are "inline" so I need to build
[16:52] <smb>   myself a debug kernel to do so.
[16:52] <smb> * About bug 1038055: it looks like right now the way to go is to
[16:52] <smb>   disable the drm qemu driver and go back to have X run by the
[16:52] <smb>   cirrus driver (and hope it and llvm-pipe go together not too badly).
[16:52] <smb>   Recent testing showed at least the initial startup crash been gone.
[16:52] <smb> * While trying to pry some useful data from a Xen dump I pulled a few
[16:52] <smb>   patches to crash from the Xen mailing list and prepared an updated
[16:52] <smb>   package: bug 1054200. Though that needs some sponsor/reviewer.
[16:53] <smb> and last but not least...
[16:53] <Daviey> drumroll
[16:53] <smb> * A certain person on the server team (starting with a capital D)
[16:53] <smb>   has been cc'ed on a mail in the past that was asking for some
[16:53] <smb>   patches pulled into the Xen package. While I may volunteer to
[16:53] <smb>   do the dirty work, I am less inclined to do anything without the
[16:53] <smb>   backing that this is acceptable at this stage (since some of the
[16:53] <smb>   patches are introducing features). So as long as afore mentioned
[16:53] <smb>   person remains silent on this mail exchange, I won't do anything. ;)
[16:53] <smb> ..
[16:53] <Daviey> smb: is that me?
[16:53] <smb> Yessir!
[16:53] <Daviey> smb: Subject?
[16:54]  * smb wispers
[16:55] <Daviey> Ah, LP:1009098 AMD 12.10 Feature: Xen Recommended Patches
[16:55] <Daviey> thanks
[16:55] <jimbaker> cool, we are running quite late, so any bug followup with smb should happen outside of this channel
[16:55] <jimbaker> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:56] <jimbaker> rbasak, any updates here?
[16:56] <rbasak> Nothing new to report. I'm continuing to work on landing ARM support in MAAS trunk and it is going well. Any questions for me?
[16:56] <jimbaker> rbasak, sounds good to me, let's just follow up in #ubuntu-server
[16:56] <jimbaker> #topic Open Discussion
[16:58] <jimbaker> #topic Next meeting will be at the same time next week on Oct 2
[16:58] <arosales> Tuesday 2012-10-02 at 1600 UTC
[16:58] <jimbaker> arosales, thanks for the utc
[16:58] <arosales> jimbaker: Thanks for chairing :-)
[16:58] <Daviey> thanks jimbaker, great effort
[16:59] <jimbaker> thanks everyone, i really just can't wait to do it again ;)
[16:59] <arosales> :-)
[16:59] <jimbaker> but i believe the previous chair gets to reserve the right to pick the next one, right?
[16:59] <hallyn> a new permanent chair!
[16:59] <jamespage> ta jimbaker
[16:59] <jimbaker> #action jimbaker picks chair for next meeting on the fly next week!
[16:59] <meetingology> ACTION: jimbaker picks chair for next meeting on the fly next week!
[17:00] <arosales> jimbaker: it just goes down the list on the wiki
[17:00] <jimbaker> #endmeeting
[17:00] <meetingology> Meeting ended Tue Sep 25 17:00:20 2012 UTC.
[17:00] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-09-25-16.04.moin.txt
[17:00] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-09-25-16.04.html
[17:00] <arosales> jimbaker: make sure to follow https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#Team_policy under "IRC meeting"
[17:00] <arosales> thanks again
[17:00] <jsalisbury> #startmeeting
[17:00] <jimbaker> arosales, thanks
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <meetingology> Meeting started Tue Sep 25 17:00:49 2012 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Quantal
[17:00] <jsalisbury> # Meeting Etiquette
[17:00] <jsalisbury> #
[17:00] <jsalisbury> # NOTE: '..' indicates that you are finished with your input.
[17:01] <jsalisbury> #       'o/' indicates you have something to add (please wait until you are recognized)
[17:01] <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
[17:01] <rtg> o/
[17:01] <herton> o/
[17:01] <kamal> o/
[17:01] <smb> \o
[17:01] <henrix> o/
[17:01] <ppisati> o/
[17:01] <sconklin_> o/
[17:01] <ogasawara> o/
[17:01] <cking> o/
[17:01] <sforshee> o/
[17:01] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> Q/omap4: a new Q/omap4 3.5 kernel is out (3.5.0-211.18) and it contains:
[17:01] <ppisati> * fixes for /dev/rtc
[17:01] <ppisati> * an updated kernel rebased on Ubuntu-3.5.0-15.22
[17:01] <ppisati> /dev/rtc was the last item on my todo list: we are feature complete and
[17:01] <ppisati> work is concentrating on squashing bugs and closing tickets from now on.
[17:01] <ppisati> ..
[17:01] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:01] <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
[17:01] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <jsalisbury> ..
[17:01] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:02] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-quantal/canonical-kernel-distro-team-ubuntu-12.10-beta-2.html
[17:02] <ogasawara> || apw         || hardware-q-kernel-config-review || 3 work item  ||
[17:02] <ogasawara> ||             || hardware-q-kernel-delta-review  || 2 work items ||
[17:02] <ogasawara> ||             || hardware-q-kernel-misc          || 1 work item  ||
[17:02] <ogasawara> || ogasawara   || hardware-q-kernel-misc          || 1 work item  ||
[17:02] <ogasawara> If your name is in the above table, please review your Beta-2 work items.
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: Quantal Development Kernel (ogasawara)
[17:02] <ogasawara> We have uploaded the 3.5.0-15.23 Quantal kernel.  This upload most
[17:02] <ogasawara> notably reverts some problematic i915 backlight patches.  This is the
[17:02] <ogasawara> kernel which we intend to ship with Beta-2.  This has also been uploaded
[17:02] <ogasawara> to the q-lts-backport [1] PPA to help facilitate testing of the 12.10
[17:02] <ogasawara> kernel in 12.04.  We welcome anyone to please install, test, and let us
[17:02] <ogasawara> know your feedback.
[17:02] <ogasawara> [1] https://launchpad.net/~ubuntu-x-swat/+archive/q-lts-backport
[17:02] <ogasawara> Important upcoming dates:
[17:02] <ogasawara>  * Thurs Sept 27 - Beta 2 (~2 days)
[17:02] <ogasawara>  * Thurs Oct 4 - Kernel Freeze (~1 week)
[17:02] <ogasawara>  * Thurs Oct 9 - Final Freeze (~2 weeks)
[17:02] <ogasawara>  * Thurs Oct 18 - 12.10 Final (~3 weeks)
[17:02] <ogasawara> ..
[17:03] <jsalisbury> [TOPIC] Status: CVE's (sconklin)
[17:03] <sconklin_> == 2012-09-25 (weekly) ==
[17:03] <sconklin_> Currently we have 42 CVEs on our radar, with 1 CVE retired this week.
[17:03] <sconklin_> See the CVE matrix for the current list:
[17:03] <sconklin_> [LINK] http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:03] <sconklin_> Overall the backlog has decreased slightly this week:
[17:03] <sconklin_> [LINK] http://people.canonical.com/~kernel/status/cve-metrics.txt
[17:03] <sconklin_> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:03] <sconklin_> ..
[17:03] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Precise/Oneiric/Natty/Lucid/Hardy (bjf/herton/henrix)
[17:03] <henrix> Here is the status for the main kernels, until today (September 25):
[17:03] <henrix>  * Hardy - In Preparation; 1 CVEs; (1 commits)
[17:03] <henrix>  * Lucid - In Preparation; 3 CVEs; (12 commits)
[17:03] <henrix>  * Oneiric - In Preparation; 2 CVEs; 1 upstream stable release(s); (54 commits)
[17:03] <henrix>  * Precise - In Preparation; 1 CVEs; 2 upstream stable release(s); (234 commits)
[17:03] <henrix> Current opened tracking bugs details:
[17:03] <henrix>  * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:03] <henrix> For SRUs, SRU report is a good source of information:
[17:03] <henrix>  * http://people.canonical.com/~kernel/reports/sru-report.html
[17:03] <henrix> Future stable cadence cycles:
[17:03] <henrix>  * https://wiki.ubuntu.com/QuantalQuetzal/ReleaseInterlock
[17:03] <henrix> ..
[17:04] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:05] <jsalisbury> Thanks everyone
[17:05] <jsalisbury> #endmeeting
[17:05] <meetingology> Meeting ended Tue Sep 25 17:05:37 2012 UTC.
[17:05] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-09-25-17.00.moin.txt
[17:05] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-09-25-17.00.html
[17:05] <kamal> thanks jsalisbury!
[21:08] <m0nster> hello... im looking for some help
[21:08] <IdleOne> m0nster: with?
[21:08] <m0nster> keyboard and mouse not working when i install ubuntu using wubi
[21:09] <LordOfTime> m0nster, you may want to ask in #ubuntu then
[21:09] <IdleOne> best place to ask would be #ubuntu
[21:09] <m0nster> ok thanks
[21:10] <spineaker> wubi c'est notre ami, il faut l'aimer aussi
[21:10] <spineaker> (ou pas)
[21:11] <IdleOne> wubi c'est comme un tattoo, vas grand ou vas tant chez vous :P
[21:11]  * genii-around tries to understand with his cereal-box french capabilities
[21:12] <IdleOne> genii-around: care for a translation?
[21:13] <IdleOne> spineaker said: wubi is our friend, we have to care for it (or not)
[21:13] <genii-around> IdleOne: My basic take is: wubi is your friend something-something also love
[21:13] <IdleOne> I said: wubi is like a tattoo, go big or go home :P
[21:13] <genii-around> Heh