[15:59] <hallyn> \o
[15:59] <hallyn> (will start mtg in 2 mins)
[15:59] <Daviey> o/
[16:00] <smb> \o
[16:00] <smoser> o/
[16:01] <hallyn> all right, let's get going
[16:01] <hallyn> #startmeeting ubuntu-server-team
[16:01] <meetingology> Meeting started Tue Feb 26 16:01:04 2013 UTC.  The chair is hallyn. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:01] <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:01] <hggdh> ~ô~
[16:01] <jamespage> o/
[16:01] <hallyn> #topic Review ACTION points from previous meeting
[16:01] <hallyn> Daviey send call for alpha-2-ish testing
[16:01] <hallyn> didn't see this?
[16:02] <Daviey> Ugh. I thought we dropped that.
[16:02] <hallyn> Daviey: last week it was re-added.  should we drop it?
[16:02] <hallyn> wait for a beta to do CFT?
[16:02] <Daviey> hallyn: Yes please.. but i will gladly send a reminder to ask people to test
[16:02] <Daviey> matsurba has kidnly offered to help with dep-8 tests BTW.
[16:02] <Daviey> kindly*
[16:02] <hallyn> cool
[16:03] <hallyn> (i have 2 i'm still supposed tow rite)
[16:03] <jamespage> \o/
[16:03] <hallyn> moving on,
[16:03] <hallyn> jamespage to milesone documentation updates [carryover]
[16:03] <jamespage> hallyn, I need to refresh my memory as to what that means
[16:04] <jamespage> but please carryover for the time being
[16:04] <hallyn> jamespage: i think it meant going through blueprints looking for doc updates, and adding milestones to them?
[16:04] <hallyn> ok
[16:04] <jamespage> hallyn, yeah - I think so
[16:04] <hallyn> ACTION: jamespage to milesone documentation updates [carryover]
[16:04] <hallyn> jamespage: though it was in the context of server guide, so not sure
[16:04] <hallyn> jamespage discuss QA representation at Server TeamMeeting
[16:04] <jamespage> yes - hggdh is here today and plars will be attending from now onwards...
[16:04] <plars> hallyn: I'll be taking that over
[16:05] <jamespage> plars, welcome!
[16:05] <hallyn> cool, so i'll update that in the server meeting knowledgebase page
[16:05] <hggdh> and I am disconnecting from representing QA :-)
[16:05] <hallyn> #action serge update server meeting docs to reflect palrs representing qa
[16:05] <meetingology> ACTION: serge update server meeting docs to reflect palrs representing qa
[16:05] <hallyn> hggdh: :(
[16:06] <plars> s/palrs/plars
[16:06] <hallyn> plars: welcome :)
[16:06] <plars> thanks!
[16:06] <hallyn> plars: sorry, fingers cold, hard typing
[16:06] <arosales> yes hggdh :-(
[16:06] <arosales> but welcome plars :-)
[16:06] <hallyn> ok moving on,
[16:06] <hallyn> #topic Raring Development
[16:06] <hallyn> Release Tracking Bug Tasks - http://reports.qa.ubuntu.com/reports/rls-mgr/rls-r-tracking-bug-tasks.html#server
[16:06] <hallyn> jamespage: Daviey: one of you want to take th is, or should i go over them?
[16:07] <hallyn> well i'll start,
[16:07] <hallyn> bug 1092715
[16:07] <hallyn> the kvm bug *should* be worked around now,
[16:07] <hallyn> jamespage: can you confirm that?
[16:07] <jamespage> hallyn, I'll check
[16:07] <hallyn> or... is that only in 1.4.0 (which is still pending my pushing)
[16:07] <hallyn> jamespage: thanks
[16:07] <hallyn> bug 1044503
[16:08] <Daviey> hmm, i thought that was fixed now
[16:08] <hallyn> smoser: ?
[16:08] <hallyn> fixed in the project but not the package, looks like
[16:08] <Daviey> smoser: does bug 901600 not solve bug 1044503 ?
[16:09] <smoser> i think hally's assesment is correct wrt 1044503.
[16:09] <Daviey> Oh, duh.. the bug title confused me
[16:09] <hallyn> so that'll end up in the pkg before long?
[16:10] <hallyn> will assume so.  bug 1064527 - roaksoax ?
[16:10] <smoser> i'd hope we'll get something in raring... but most focus on maas has been on backport.
[16:10] <hallyn> smoser: thx
[16:10] <hallyn> roaksoax: around?
[16:10] <roaksoax> hallyn: here
[16:11] <hallyn> any progress on that bug?  seems to be stalled since october?
[16:11] <roaksoax> hallyn: well we haven't really found a way to do it.. so there's no progress
[16:12] <hallyn> ok, thanks...
[16:12] <hallyn> bug 1073463
[16:12] <hallyn> not owned by anyone,
[16:12] <hallyn> anyone want to volunteer to look at it?
[16:12] <roaksoax> i;ll take it
[16:13] <hallyn> cool, thanks
[16:13] <roaksoax> but I think that bug doesn't belong there
[16:13] <roaksoax> that belongs upstream
[16:13] <hallyn> ok - you can re-target?
[16:13] <roaksoax> hallyn: yes, I'll catch up with bigjools about it first
[16:14] <hallyn> great
[16:14] <hallyn> bug 1122206
[16:14] <hallyn> fix released in quantum project, not pkg...
[16:14] <hallyn> i assume we're jsut waiting - moving on unless someone shouts
[16:15] <hallyn> bug 1132302
[16:15] <hallyn> looks like rbasak has that handled :)  thanks rbasak
[16:15] <rbasak> np. Just waiting on the reporter to test, and if it's OK then we can upload
[16:15] <hallyn> two medium bugs, tempted to skip them,
[16:16] <hallyn> well there is bug 1100920 whic his fix committed,
[16:16] <hallyn> and then bug 1113821 - zul or i just needs to fix that in libvirt (same fix as in lxc)
[16:16] <hallyn> oh i own it :)
[16:16] <hallyn> tsk tsk
[16:17] <hallyn> ok, moving on,
[16:17] <hallyn> Blueprints - http://status.ubuntu.com/ubuntu-raring/group/topic-raring-servercloud-overview.html
[16:17] <hallyn> arosales: Daviey: did you want to say somethin gon blueprints?
[16:17] <Daviey> Only the usual :)
[16:17] <Daviey> Make sure they are accurate, we look a little behind where i think we actually *are*
[16:18] <Daviey> So everybody should check that bluepritns assigned to them are in accurate state
[16:18] <Daviey> (and talk with elither myself, or jamespage or smoser about defering thing)
[16:18] <hallyn> Daviey: meaning at this point we should talk to you before deferring anything,
[16:18] <hallyn> or ping you if we have questions?
[16:19] <Daviey> yeah.. ideally not just defer things.. disucss with me, or scott or james.. first
[16:19] <hallyn> ok
[16:19] <hallyn> moving on,
[16:19] <hallyn> #topic Ubuntu Server Team Events
[16:20] <hallyn> anything to mention here?
[16:20] <Daviey> none come to mind.
[16:20] <hallyn> #topic Weekly Updates & Questions for the QA Team (hggdh)
[16:20] <hallyn> three cheers for hggdh ?
[16:21] <hallyn> plars:
[16:21] <plars> Hi
[16:21] <hallyn> hey :)
[16:21] <plars> Just a couple of things
[16:22] <plars> 1. LXC failures
[16:22] <plars> https://bugs.launchpad.net/ubuntu-test-cases/+bug/1130029
[16:22] <plars> hallyn: you seem to have a mp for this at https://code.launchpad.net/~serge-hallyn/ubuntu-test-cases/server-lxc2/+merge/150491
[16:22] <hallyn> merge proposal is pending to fix that
[16:22] <hallyn> yup
[16:22] <hallyn> (though i'm still getting the hang of utah, still testing locally, might have more changes coming)
[16:23] <plars> If someone can get that reviewed and in soon, we'd like to test it out.  I was talking to psivaa this morning about it and he thinks there may be other issues lurking once we get past this one
[16:23] <hallyn> plars: who has the rights to review that?
[16:23] <plars> I'm not as well aware of what's going on with this bug, so if he or you want to discuss what further steps might be needed, that would be useful
[16:24] <plars> hallyn: it seems to be pointed at https://launchpad.net/~ubuntu-server-dev right now
[16:24] <hallyn> ?
[16:24] <hallyn> ok will fix that, thanks :)
[16:24] <plars> but as far as merging it, anyone in the https://launchpad.net/~ubuntu-test-case-dev group could do it
[16:24] <hallyn> no here it says lp:ubuntu-test-cases/server
[16:25] <hallyn> oh you mean reviewer
[16:25] <plars> hallyn: I'm talking about the reviewer
[16:25] <plars> right
[16:25] <hallyn> i just used the default
[16:25] <plars> ubuntu-server-dev is the default reviewer?
[16:25] <plars> odd
[16:25] <hallyn> is that something that should be changed in the ubuntu-test-case lp settings?
[16:25] <plars> perhaps
[16:25] <plars> I'll talk to others about it, but since it's a test for lxc, I figured it was something that you wanted reviewed by ubuntu-server-dev
[16:25] <hallyn> ok thanks we'll straighten the mp out - moving on?
[16:26] <plars> it made sense to me at least
[16:26] <plars> ok
[16:26] <hallyn> oh i see, ok
[16:26] <plars> only other thing I wanted to raise (and it's minor) is conffile failures
[16:26] <hallyn> no perhaps ubuntu-lxc
[16:26] <plars> ex. https://jenkins.qa.ubuntu.com/view/Raring/view/Smoke%20Testing/job/raring-upgrade-quantal-server/ARCH=amd64,LTS=non-lts,PROFILE=server-tasks,label=upgrade-test/lastSuccessfulBuild/artifact/results/obsolete_conffiles.log
[16:26] <hallyn> not ubuntu-server-dev
[16:26] <plars> These are no longer reported as individual bugs
[16:26] <plars> but we get a good log of them in the test runs that can be referred to
[16:27] <plars> We realize that they are low priority as bugs go, and in some cases they stack up to dozens that would need to be tracked against every daily test run indefinitely.  So if you have some cycles and want to clean them up, it would be useful
[16:27] <hallyn> these are confiles no longer used by cups in raring?
[16:28] <plars> apparently not
[16:28] <plars> or if they are, their location changed
[16:28] <hallyn> and so they should be handled by the packaging somehow.  k.  does someone go look at those log pages regularly?
[16:29] <hallyn> do they get emailed somewhere?
[16:29] <plars> hallyn: not currently, but they always end up in the same place, so they are pretty easy to find
[16:29] <plars> hallyn: the url I pointed to will take you to the lastSuccessfulBuild in jenkins and show you the current obsolete_conffiles log
[16:30] <hallyn> perhaps that url s hould be added to the server team knowledgebase weekly bug triaging section
[16:30] <hallyn> the url may be consistent, but if noone is in the habit of looking at it, bugs won't get raised...  course you're right about low prio,
[16:30] <plars> hallyn: that sounds reasonable - we were looking for a better way of dealing with these and nobody wanted spam about it, but I don't think it makes sense to ignore them entirely. So just making you aware
[16:30] <hallyn> ok, thanks
[16:31] <hallyn> #action serge consider putting the obsolete_conffiles.log url in weekly triaging knowledgebase section
[16:31] <meetingology> ACTION: serge consider putting the obsolete_conffiles.log url in weekly triaging knowledgebase section
[16:31] <plars> hallyn: the problem with bugs is it got to be quite a lot of overhead - in this case with one or 2 it's not so bad, but in others you're talking 30-40 bugs that have to be updated across each daily test run
[16:31] <plars> ...for something that just gets ignored
[16:31] <plars> sanity kicked in at some point
[16:31] <hallyn> plars: yup :)
[16:31] <plars> that's all from me
[16:31] <hallyn> plars: thanks
[16:31] <hallyn> moving on,
[16:31] <hallyn> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:32] <smb> Hello, I would like to take this opportunity to re-advertise for http://people.canonical.com/~smb/lucid-ec2-ng/ ... I know not very subtly but I am a developer and not a sales guy. :-P Otherwise raring kernel ddebs will be actually usable after next upload (in case anybody actually was wondering why the heck they were so small).
[16:32] <smb> Oh, one other thing: have not run into this myself but it seems
[16:32] <smb> that recent raring kvm/qemu packages are a bit insulted if
[16:32] <smb> post-install does not get /dev/kvm. This might not be the "normal"
[16:32] <smb> case but it is possible to have the kvm package installed and dual
[16:32] <smb> boot between xen and non-xen mode and its also possibleto do a
[16:32] <smb> dist-upgrade in xen dom0 which won't allow for /dev/kvm...
[16:32] <smb> Beside that, any questions? :)
[16:32] <smoser> smb, i'm confused about /dev/kvm
[16:33] <hallyn> smb: the /dev/kvm bit *should* be fixed, please shout at me if you see it again
[16:33] <smoser> right.
[16:33] <smb> hallyn, Ah ok, it was a few days ago
[16:33] <smoser> hallyn, that is bug 1103022 ?
[16:33] <hallyn> smoser: no
[16:33] <hallyn> smoser: it was a bug from my bad fixing of that one
[16:33] <hallyn> smoser: if /dev/kvm did not exist, getfacl failed, causing postinst to fail
[16:33] <smoser> ah. k.
[16:34] <smb> Ah ok, as said it wasn't me and it was probably last week
[16:35] <hallyn> smb: feb 20 the fix went up
[16:35] <hallyn> so yeah shout at me if you see it again.  thx
[16:35] <smb> hallyn, sure. will do :)
[16:35] <hallyn> lucid-ec2-ng - i assume the right folks know what that means :)
[16:35] <smb> hallyn, I suppose yes.
[16:35] <hallyn> thanks, smb.  moving on,
[16:35] <hallyn> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:36] <rbasak> Nothing new to report. Any questions for me?
[16:36] <hallyn> sounds like no, moving on,
[16:36] <hallyn> #topic Open Discussion
[16:37] <hallyn> anything to discuss?
[16:37] <hallyn> if not,
[16:38] <hallyn> hggdh: o/  see you around!
[16:38] <hallyn> #topic Announce next meeting date and time
[16:38] <hallyn> Next meeting will be same time, 16:00 UTC on March 5.
[16:38] <hallyn> thanks all,
[16:38] <hallyn> #endmeeting
[16:38] <meetingology> Meeting ended Tue Feb 26 16:38:30 2013 UTC.
[16:38] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-26-16.01.moin.txt
[16:38] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-26-16.01.html
[16:38] <Daviey> thanks
[16:40] <arosales> hallyn (looks like he already left) thanks for chairing
[17:00] <jsalisbury> #startmeeting
[17:00] <jsalisbury> ##
[17:00] <meetingology> Meeting started Tue Feb 26 17:00:36 2013 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> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/raring
[17:00] <jsalisbury> # Meeting Etiquette
[17:00] <jsalisbury> #
[17:00] <jsalisbury> # NOTE: '..' indicates that you are finished with your input.
[17:00] <jsalisbury> #       'o/' indicates you have something to add (please wait until you are recognized)
[17:00] <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
[17:00] <bjf> o/
[17:00] <ppisati> o/
[17:00] <smb> \o
[17:00] <cking> o/
[17:00] <henrix> o/
[17:01] <sconklin> o/
[17:01] <sforshee> o/
[17:01] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> R/master: upstream landed a patch for the ipv6 stack alignment problem - waiting
[17:01] <ppisati> for it to enter linux-next or stable before picking it up.
[17:01] <ppisati> Meanwhile i'm trying to make the binary pvr omap4 module to work with the
[17:01] <ppisati> upstream kernel (but so far i didn't succeed).
[17:01] <ppisati> ..
[17:02] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:02] <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
[17:02] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:02] <jsalisbury> ..
[17:02] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:02] <ogasawara> [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
[17:02] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-raring/canonical-kernel-distro-team.html
[17:02] <ogasawara> || apw       || hardware-r-kernel-config-review       || 1 work item  ||
[17:02] <ogasawara> ||           || hardware-r-delta-review               || 3 work items ||
[17:02] <ogasawara> ||           || foundations-r-secure-boot             || 1 work item  ||
[17:02] <ogasawara> ||           || foundations-r-aarch64                 || 1 work item  ||
[17:02] <ogasawara> ||           || foundations-r-upstart-user-session-enhancements || 1 work item ||
[17:02] <ogasawara> || ogasawara || hardware-r-kernel-config-review       || 2 work items ||
[17:03] <ogasawara> ||           || hardware-r-kernel-version-and-flavors || 2 work items ||
[17:03] <ogasawara> ||           || hardware-r-arm-kernel-maintenance     || 1 work item  ||
[17:03] <ogasawara> ||           || hardware-r-kernel-misc                || 1 work item  ||
[17:03] <ogasawara> || ppisati   || hardware-r-kernel-config-review       || 1 work item  ||
[17:03] <ogasawara> || smb       || servercloud-r-libvirt                 || 1 work item  ||
[17:03] <ogasawara> ||           || servercloud-r-xen                     || 2 work items ||
[17:03] <ogasawara> || rtg       || hardware-r-delta-review               || 1 work item  ||
[17:03] <ogasawara> The above summarizes the remaining work items owned by individuals on
[17:03] <ogasawara> our team for the rest of the cycle.
[17:03] <ogasawara> ..
[17:03] <jsalisbury> [TOPIC] Status: Raring Development Kernel (ogasawara)
[17:03] <ogasawara> We have recently uploaded the 3.8.0-7.16 Raring kernel.  This upload
[17:03] <ogasawara> contains a fix for CVE-2013-1763 and config updates following a full
[17:03] <ogasawara> v3.8 config review.
[17:03] <ogasawara> Important upcoming dates:
[17:03] <ogasawara>  * Raring:
[17:03] <ogasawara>   * Thurs Mar 07 - 13.04 Feature Freeze (~1 week)
[17:03] <ogasawara>   * Thurs Mar 21 - 13.04 Beta Freeze (~3 weeks)
[17:03] <ogasawara>   * Thurs Mar 28 - 13.04 Beta Release (~4 weeks)
[17:03] <ogasawara> ..
[17:04] <jsalisbury> [TOPIC] Status: CVE's (sconklin)
[17:04] <sconklin> == 2013-02-26 (weekly) ==
[17:04] <sconklin> Currently we have 36 CVEs on our radar, with 6 CVEs added and 5 CVEs retired this week.
[17:04] <sconklin> See the CVE matrix for the current list:
[17:04] <sconklin> [LINK] http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:04] <sconklin> Overall the backlog has decreased slightly this week:
[17:04] <sconklin> [LINK] http://people.canonical.com/~kernel/status/cve-metrics.txt
[17:04] <sconklin> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:04] <sconklin> ..
[17:04] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Quantal/Precise/Oneiric/Lucid/Hardy (bjf/henrix)
[17:05] <bjf> Status for the main kernels, until tiday (Feb. 26):
[17:05] <bjf>   *   Hardy - Nothing this cycle
[17:05] <bjf>   *   Lucid - In Prep; (2 commits)
[17:05] <bjf>   * Oneiric - In Prep; 4 upstream releases; (68 commits)
[17:05] <bjf>   * Precise - In Prep; 2 upstream releases; (197 commits)
[17:05] <bjf>   * Quantal - In Prep; 2 upstream releases; (175 commits)
[17:05] <bjf>     
[17:05] <bjf> Due to an high priority CVE, all the stable kernels are being respined this week.
[17:05] <bjf> Current opened tracking bugs details:
[17:05] <bjf>   * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:05] <bjf> For SRUs, SRU report is a good source of information:
[17:05] <bjf>   * http://people.canonical.com/~kernel/reports/sru-report.html
[17:05] <bjf> Future stable cadence cycles:
[17:05] <bjf>   * https://wiki.ubuntu.com/RaringRingtail/ReleaseInterlock
[17:05] <bjf>     
[17:05] <bjf> >>
[17:05] <bjf> >> Note: The week of March 28 is the week the last Hardy and Oneiric kernels may be built.
[17:05] <bjf> >>
[17:05] <bjf> ..
[17:05] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:06] <jsalisbury> Thanks everyone
[17:06] <jsalisbury> #endmeeting
[17:06] <meetingology> Meeting ended Tue Feb 26 17:06:11 2013 UTC.
[17:06] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-26-17.00.moin.txt
[17:06] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-26-17.00.html
[17:06] <sconklin> thanks Joe!