[15:00] <cjwatson> #startmeeting
[15:00] <MootBot> Meeting started at 09:00. The chair is cjwatson.
[15:00]  * pitti waves
[15:00] <kees> \o
[15:00] <cjwatson> no Keybuk (we should really rearrange the meeting time; what's that blocked on)?
[15:00] <sabdfl> hello folks
[15:00] <sabdfl> i'm unexpectedly present
[15:01] <cjwatson> sabdfl: oh, hello, can you chair then? :)
[15:01] <sabdfl> but only briefly :-(
[15:01] <kees> neat
[15:01] <kees> oh
[15:01] <sabdfl> weeeeeell
[15:01] <cjwatson> maybe not, if only briefly
[15:01] <sabdfl> can chair the first 30 minutes, not sure that's good enough
[15:01] <mdz> cjwatson, I can if it's not convenient for you
[15:01] <kees> sabdfl: if only briefly, we should cover meeting time change and bug 374900 at the front
[15:02] <mdz> sounds good to me
[15:02] <sabdfl> i don't have much to add to the time change
[15:02] <sabdfl> if it's good for mdz, it's good for me
[15:02] <pitti> what was the doodle URL again?
[15:02] <cjwatson> [TOPIC] Meeting times
[15:02] <MootBot> New Topic:  Meeting times
[15:02] <kees> http://www.doodle.com/44mg7x3e84qtqahw
[15:02] <pitti> ah, http://www.doodle.com/44mg7x3e84qtqahw
[15:02] <MootBot> LINK received:  http://www.doodle.com/44mg7x3e84qtqahw
[15:03] <cjwatson> sorry, I need to fill that in
[15:03] <cjwatson> if sabdfl can take over chairing, I can do that right now
[15:03] <sabdfl> sure
[15:03] <cjwatson> #endmeeting
[15:03] <MootBot> Meeting finished at 09:03.
[15:03] <cjwatson> thanks
[15:03] <kees> cjwatson: if you can do UTC 1800 on thursday, we can short-circuit it.
[15:04] <sabdfl> #startmeeting
[15:04] <MootBot> Meeting started at 09:04. The chair is sabdfl.
[15:04] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:04] <sabdfl> [TOPIC]  Meeting times
[15:04] <MootBot> New Topic:   Meeting times
[15:04] <pitti> right, that seems to be the only time where all of us have no red
[15:06] <cjwatson> argh, how do I provide a name on that doodle?
[15:06] <sabdfl> "Your name"?
[15:06] <cjwatson> oh yes, hidden off to the left :)
[15:07] <cjwatson> submitted mine.  1800 on Thu is kind of sucky but tolerable.
[15:07] <kees> I think it's literally the only non-red time.
[15:07] <sabdfl> ok, proposal: Thurs 8pm UTC
[15:07] <cjwatson> 8pm is worse for me
[15:07] <kees> mdz: but you need to change the alternating week?
[15:07] <mdz> sabdfl, that is significantly worse according to the doodle
[15:07] <kees> sabdfl: 6pm not 8pm. 1800
[15:08] <sabdfl> [VOTE] Proposal: Thursday 1800 UTC
[15:08] <MootBot> Please vote on:  Proposal: Thursday 1800 UTC.
[15:08] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[15:08] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[15:08] <mdz> kees, 1800 UTC is fine for me
[15:08] <mdz> +1
[15:08] <MootBot> +1 received from mdz. 1 for, 0 against. 0 have abstained. Count is now 1
[15:08] <pitti> +1
[15:08] <kees> +1
[15:08] <MootBot> +1 received from pitti. 2 for, 0 against. 0 have abstained. Count is now 2
[15:08] <MootBot> +1 received from kees. 3 for, 0 against. 0 have abstained. Count is now 3
[15:08] <cjwatson> +1
[15:08] <MootBot> +1 received from cjwatson. 4 for, 0 against. 0 have abstained. Count is now 4
[15:08] <sabdfl> (sorry, i was looking at South African times)
[15:08] <sabdfl> +1
[15:08] <MootBot> +1 received from sabdfl. 5 for, 0 against. 0 have abstained. Count is now 5
[15:08] <sabdfl> [/VOTE]
[15:08] <sabdfl> [ENDVOTE]
[15:08] <MootBot> Final result is 5 for, 0 against. 0 abstained. Total: 5
[15:08] <sabdfl> [AGREED] Thursday 1800 UTC
[15:08] <MootBot> AGREED received:  Thursday 1800 UTC
[15:08] <mdz> someone needs an action to update the calendar etc.
[15:09] <soren> So this is just until DST starts kicking in, right?
[15:09] <kees> soren: 1800 UTC. no DST
[15:09] <mdz> last I checked it was pinned to UTC
[15:09] <sabdfl> it kicks in differently in different places
[15:09] <soren> sabdfl: Exactly my concern.
[15:09] <mdz> it's marginally less confusing that way
[15:09] <kees> soren: that's why we moved it to UTC a few months back.
[15:09] <cjwatson> and the UK is currently talking about moving to CET :-/
[15:10] <kees> mdz: who has access to the calendar?
[15:10] <mdz> kees, I think all of us except scott
[15:10] <mdz> yep
[15:11] <kees> I'll take it then to learn where it is.
[15:11] <soren> I understand it's less confusing.  Once everyone's clock moves by an hour..
[15:11] <soren> But I guess that's a problem for a couple of months from now :)
[15:12] <mdz> [action] kees to update the calendar with the new meeting time
[15:12] <sabdfl> they can't possibly move to CET. I just concessioned a coconut farm because it was on UTC!
[15:12] <sabdfl> [action] kees to update the calendar with the new meeting time
[15:12] <MootBot> ACTION received:  kees to update the calendar with the new meeting time
[15:12] <pitti> cjwatson: we have become good at providing tzdata updates.. :)
[15:12] <sabdfl> next topic? the bug?
[15:13] <mdz> y
[15:13] <sabdfl> [TOPIC] Launchpad bug 374900 in faac (Ubuntu) "Libfaac not LGPL"
[15:13] <MootBot> New Topic:  Launchpad bug 374900 in faac (Ubuntu) "Libfaac not LGPL"
[15:14] <kees> (soren: it's only red for mdz, afaict the time would just move later not earlier, yes?)
[15:14] <soren> kees: Yes, you're right.
[15:15] <mdz> so as of the last meeting, it seemed like the status was that kees felt there was likely an issue
[15:15] <mdz> "it looks pretty clearly like the encoder package need to be removed"
[15:15] <kees> based on the bug, year
[15:15] <kees> er, yeah
[15:15] <mdz> Colin had the ball, but has had higher priority work and hadn't gotten to it yet
[15:16] <cjwatson> I originally took an action for this, but sunk into a pit of despair; it's one of those where users are clamouring for it, but I saw mails (which I can't find now) from copyright holders of LGPLed code saying they felt it to be an infringement
[15:16] <mdz> the bug really needs a summary update
[15:16] <cjwatson> and I got stuck in "oh god I don't want to deal with this", for which I apologise
[15:17] <cjwatson> the bug is full of confusion between redistributability and software-patents
[15:17] <mdz> well, one could argue that this is not a technical issue, but I don't know who we'd give it to
[15:17] <sabdfl> i can relate! but if we tease out the patent issues, is there a genuine licensing issue?
[15:18] <mdz> if a copyright holder feels there is, then likely yes
[15:18] <cjwatson> my understanding is that there is a licensing issue for anything GPLed that links to ffmpeg
[15:18] <cjwatson> I'm not sure about for ffmpeg itself in isolation
[15:19] <cjwatson> AFAICS there shouldn't be a problem with linking code under that licence with LGPLed code
[15:19] <mdz> the license at the top of tns.c is rather ambiguous
[15:20] <mdz> if you could even call it a license
[15:20] <cjwatson> in comment 13, james_w says "due to the conflict between the LGPL and this license"
[15:20] <cjwatson> I can't see the conflict; you can link LGPLed code with practically anything, by design
[15:20] <cjwatson> unless I'm misunderstandidng
[15:21] <mdz> "The original developer retains
[15:21] <mdz> full right to use the code for his/her own purpose, assign or donate
[15:21] <mdz> the code to a third party and to inhibit third party from using the
[15:21] <mdz> code"
[15:21] <mdz> that last bit about inhibiting third parties from using the code doesn't sound ideal
[15:21] <cjwatson> it certainly can't go to main/universe with that licence
[15:21] <mdz> right, but it's already in multiverse
[15:22] <sabdfl> no, but then we haven't heard from the developer, and every indication is that they have no objection to its use in conforming products
[15:22] <mdz> the conflict is attributed to "#gnu"
[15:22] <cjwatson> (certainly can't> field of endeavour restriction)
[15:23] <sabdfl> you can understand why they would write something like that, after shallow analysis "we are making this available to help further the standard not fragment it"
[15:23] <cjwatson> I can understand it but that doesn't mean it meets our guidelines for main/universe :)
[15:23] <mdz> so the claimed issue is that libfaac may be GPL-incompatible?
[15:23] <mdz> not LGPL-incompatible
[15:23] <sabdfl> cjwatson: agreed
[15:23] <cjwatson> I don't think that's the *claimed* issue in the bug, but that's the only one I can tease out
[15:24] <cjwatson> which suggests to me that libfaac should remain in multiverse and we should audit to ensure that nothing under the GPL links to it
[15:24] <mdz> I think the initial "LGPL-incompatible" may be a typo; I don't see any supporting evidence
[15:24] <cjwatson> ?
[15:24] <mdz> cjwatson, that's my preliminary assessment
[15:25] <mdz> cjwatson, also, the copyright file may be wrong
[15:25] <mdz> yes, the copyright file is wrong
[15:25] <mdz> (incomplete)
[15:25] <mdz> it says GPL
[15:26] <mdz> but COPYING is the LGPL
[15:26] <mdz> and some files have other licenses as shown in the bug
[15:26] <mdz> I don't know if there is actually any GPL code in it
[15:26] <mdz> so:
[15:26] <mdz> - stays in universe
[15:26] <mdz> - copyright file gets fixed
[15:26] <cjwatson> *stays in multiverse
[15:26] <mdz> cjwatson, yes, sorry
[15:26] <mdz> and
[15:26] <mdz> - handled as GPL-incompatible
[15:27] <mdz> does that cover it?
[15:27] <kees> sounds reasonable to me
[15:27] <cjwatson> I think so
[15:29] <sabdfl> i don't think we need to vote
[15:29] <sabdfl> can i document that as agreed?
[15:29] <mdz> let's put it in the bug and see if anything comes back
[15:30] <mdz> since we're not entirely sure that we understood the whole issue
[15:30] <sabdfl> [ACTION] mdz to update the bug with a proposed handling
[15:30] <MootBot> ACTION received:  mdz to update the bug with a proposed handling
[15:30] <sabdfl> [TOPIC] Any other business?
[15:30] <MootBot> New Topic:  Any other business?
[15:30] <Laney> can someone action the DMB changes?
[15:31] <mdz> sabdfl, there are outstanding actions from the last meeting which were skipped over to get to the meeting time discussion early
[15:32] <pitti> Laney: which ones?
[15:32] <sabdfl> ok. can I hand over to another chair?
[15:32] <sabdfl> rather than ending and restarting the meeting, we could trade nicks ;-)
[15:32] <mdz> that would be more confusing
[15:32]  * cjwatson doesn't want sabdfl's private messages :-P
[15:32] <sabdfl> but entertaining :-)
[15:32] <Laney> pitti: there was an election, and now are new members that need adding to the team
[15:32] <sabdfl> [ENDMEETING]
[15:32] <sabdfl> thanks all
[15:32] <cjwatson> sabdfl: "#endmeeting"
[15:32] <sabdfl> #endmeeting
[15:32] <MootBot> Meeting finished at 09:32.
[15:32] <sabdfl> thanks again :-)
[15:32] <cjwatson> #startmeeting
[15:32] <MootBot> Meeting started at 09:32. The chair is cjwatson.
[15:32] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:32] <cjwatson> I'll take over then
[15:33]  * kees hopes that mootbot looks at more than just nick
[15:33] <cjwatson> so yes, there was a DMB election; I'll just dig up the log
[15:33] <cjwatson> http://irclogs.ubuntu.com/2011/02/14/%23ubuntu-meeting.html#t12:16
[15:33] <MootBot> LINK received:  http://irclogs.ubuntu.com/2011/02/14/%23ubuntu-meeting.html#t12:16
[15:34] <cjwatson> the effect of this is that Iain Lane and Mackenzie Morgan replace Soren Hansen and Colin Watson
[15:34] <cjwatson> [TOPIC] DMB changes
[15:34] <MootBot> New Topic:  DMB changes
[15:35] <cjwatson> if there are no objections, I can make those changes to the LP team
[15:35] <cjwatson> oh, there are expired members too; Emmet Hikory, Michael Bienia, Stéphane Graber, and Cody Somerville should be reinstated
[15:36] <pitti> I thought their memberships were temporarily extended
[15:37] <mdz> cjwatson, my action above is done: https://bugs.launchpad.net/ubuntu-community/+bug/374900/comments/39
[15:38] <cjwatson> pitti: they were, until the last DMB meeting :)
[15:38] <kees> mdz: oh, you meant the canonical calendar? what about the fridge?
[15:38] <mdz> kees, it's on the Ubuntu Engineering calendar, with an invitation extended to the fridge calendar (so it's the same event)
[15:39] <mdz> CIVS results are at http://www.cs.cornell.edu/w8/~andru/cgi-perl/civs/results.pl?id=E_924ef5b8e9f6d03b
[15:39] <mdz> I see no reason why cjwatson should not go ahead and update LP with those results
[15:40] <cjwatson> [ACTION] cjwatson to update LP in light of DMB election
[15:40] <MootBot> ACTION received:  cjwatson to update LP in light of DMB election
[15:40] <cjwatson> [TOPIC] Action review
[15:40] <MootBot> New Topic:  Action review
[15:40] <cjwatson> mdz - Review ubuntu-drivers membership and make sure it includes (only) people who need to manage blueprints
[15:40] <mdz> so the members are:
[15:40] <mdz> Alexander Sack
[15:40] <mdz> Canonical Ubuntu QA Team
[15:40] <mdz> Colin Watson
[15:40] <mdz> David Barth
[15:40] <mdz> David Mandala
[15:40] <mdz> Joshua Hoover
[15:40] <mdz> Kate Stewart
[15:40] <mdz> Mark Shuttleworth
[15:40] <mdz> Pete Graner
[15:40] <mdz> Robbie Williamson
[15:40] <mdz> Sebastien Bacher
[15:40] <mdz> Steve Langasek
[15:40] <mdz> Ubuntu Technical Board
[15:40] <mdz> UDS Organizers
[15:40] <mdz> the only one which looks out of place to me is the QA team
[15:41] <mdz> removing the QA team will have the side effect that they will no longer be able to change the bug reporting guidelines for Ubuntu as a whole
[15:41] <mdz> (though they will continue to be able to update package-specific guidelines)
[15:41] <kees> mdz: I don't have permissions to change that calendar. "You can: See all event details"
[15:41] <mdz> the bug for that is apparently https://bugs.launchpad.net/launchpad/+bug/703002
[15:41] <mdz> kees, fixed
[15:42] <mdz> the last time I asked bdmurray, he said it would probably be best if we didn't do it until that is fixed
[15:42] <mdz> some of the memberships are redundant and could be cleaned up, e.g. Colin and Mark are in TB
[15:43] <pitti> mdz: "didn't do" -> "keep CQA team"? I agree
[15:43] <mdz> pitti, right
[15:43] <pitti> mdz: I'd rather keep them in explicitly
[15:43] <pitti> in case Colin ever loses his TB hat, he'd still be an ubuntu-driver due to him being a tech lead
[15:43] <cjwatson> I also generally feel that it should be explicit that some people have those privileges in their own right
[15:44] <cjwatson> (why doesn't pitti have that hat, incidentally?)
[15:44] <pitti> I'm in uds-organizers, I think
[15:44] <cjwatson> ah
[15:44] <pitti> as I prepared the karmic and lucid UDS desktop bits
[15:45] <mdz> most engineering managers are members via uds-organizers as well
[15:45] <mdz> anyway I think this action is as done as it can be
[15:45] <pitti> I think so, too; it looks reasonable enough to me, modulo some minor inconsistency/redundancy
[15:46] <mdz> cjwatson, given we already made the other changes and nobody has complained of breakage, I think we can skip the announcement
[15:46] <cjwatson> ok
[15:46] <cjwatson> well, skaet had one complaint
[15:46] <cjwatson> she can't edit milestones in stable releases (any more?)
[15:46] <cjwatson> but this is blocked on getting that LP bug fixed
[15:47] <kees> (cjwatson: I've updated the calendar entry now, so that can be marked as "done")
[15:47] <mdz> cjwatson, which releases?
[15:47] <mdz> can't we just make sure the release manager is set appropriately for those series?
[15:47] <cjwatson> lucid.  no, because that would remove the ability of ubuntu-core-dev to target bugs to that release, until such time as that LP bug is fixed.
[15:47] <cjwatson> kees: thanks
[15:48] <mdz> cjwatson, which LP bug?
[15:48] <cjwatson> I don't have it to hand; it should be in the records of our discussion in Dallas
[15:48] <bdmurray> actually the problem with removing the CQA team from ubuntu-drivers is that we wouldn't be able to approve bug nominations for releases
[15:48] <cjwatson> so that's the same bug
[15:49] <cjwatson> we identified it in Dallas and raised it through Jono Lange
[15:49] <pitti> bug 451390 I think
[15:49] <cjwatson> thanks, that's the one
[15:49] <pitti> mdz: https://wiki.ubuntu.com/LaunchpadPermissions has the summary, FYI
[15:49] <mdz> pitti, yeah, i was just looking at that
[15:50] <mdz> series RM = ubuntu-core-dev doesn't sound right, since that excludes skaet
[15:50] <cjwatson> mdz: it's a workaround for bug 451390
[15:50] <cjwatson> essentially
[15:50] <cjwatson> that series RM setting dates back a long way, and was to ensure that core-dev could target bugs
[15:50] <pitti> mdz: that's what "what we would like to do" changes
[15:51] <pitti> mdz: indeed it's not right
[15:51] <mdz> pitti, can you reference 451390 in 174375?
[15:51] <cjwatson> once core-dev can target bugs via their upload privileges, we will no longer need that workaround
[15:51] <cjwatson> until then, we need it
[15:51] <mdz> pitti, oh right
[15:51] <mdz> so 174375 just needs a comment to that effect and then we are back to wait mode
[15:51] <pitti> mdz: will do
[15:51] <cjwatson> 451390 is not the CQA problem, although it's sort of similar
[15:51] <mdz> pitti, thanks much
[15:51] <cjwatson> bdmurray: is there a bug for giving CQA that access without requiring them to be in ubuntu-drivers?
[15:52] <mdz> cjwatson, I understood bug 703002 to be that bug, though it is not at all obvious by looking at it
[15:52] <mdz> this is based on the logs from the last meeting where bdmurray pointed to that bug
[15:53] <bdmurray> cjwatson: no, my thought has been that there would be a release-manager team set as the release-manager and CQA would be part of that team
[15:53] <mdz> 08-02-2011 15:51:46 <<EMAIL_ADDRESS>its bug 703002
[15:53] <mdz> 08-02-2011 15:51:47 < kees!~kees@ubuntu/member/keescook: bdmurray: ah, excellent. that was my memory too; do you have the bug # handy?
[15:53] <pitti> mdz: (done)
[15:53] <bdmurray> mdz: that bug 703002 is something that can't happen now that the owner of Ubuntu was set to the tech board
[15:53] <mdz> bdmurray, gah, so I've confused things further in the bug
[15:54] <cjwatson> ok, we could add CQA to ubuntu-release, I expect
[15:54] <cjwatson> once 451390 is fixed so that we can actually use ubuntu-release in that slot
[15:54] <cjwatson> so that means that 451390 really is the blocker for everything
[15:55] <bdmurray> I agree - 703002 is just rather inconvenient
[15:56] <mdz> ok, someone who understands what's going on please update the bug. I am obviously hopeless
[15:58] <cjwatson> done
[15:58] <cjwatson> let's move on
[15:58] <cjwatson> Action: pitti to update g-s-t for new ntp pool
[15:58] <pitti> done
[15:58] <pitti> jdstrand's part as well
[15:59] <pitti> the Narwhal has a better watch now
[15:59] <kees> heh
[15:59] <cjwatson> gotta have a funny-shaped watch
[15:59] <cjwatson> [TOPIC] Scan the mailing list archive for anything we missed (standing item)
[15:59] <MootBot> New Topic:  Scan the mailing list archive for anything we missed (standing item)
[15:59] <cjwatson> I looked, didn't see anything we haven't already covered
[15:59] <cjwatson> [TOPIC] Check up on community bugs (standing item)
[15:59] <MootBot> New Topic:  Check up on community bugs (standing item)
[15:59] <cjwatson> only the two we've covered
[15:59] <cjwatson> [TOPIC] AOB
[16:00] <MootBot> New Topic:  AOB
[16:00]  * mdz starts dialing into his next meeting
[16:00] <cjwatson> I've applied the DMB changes to LP now
[16:00] <cjwatson> https://launchpad.net/~developer-membership-board/+members
[16:00]  * cjwatson is freeeeeeeee
[16:01] <kees> haha
[16:01] <SpamapS> o/
[16:01] <cjwatson> next chair?
[16:01] <kees> cjwatson: keybuk?
[16:01] <cjwatson> either me (if this one didn't count), or kees by nick rotation, or Keybuk by frequency
[16:02] <cjwatson> perhaps Keybuk with the new meeting time
[16:02] <pitti> the last ones rotated between kees, cjwatson, and me, so I'll be fallback if Keybuk can't
[16:02] <cjwatson> let's ask Keybuk in the minutes
[16:02] <kees> sounds good
[16:02] <cjwatson> #endmeeting
[16:02] <MootBot> Meeting finished at 10:02.
[16:02] <kirkland> o/
[16:02] <cjwatson> getting out of the server team's way
[16:02] <cjwatson> thanks all
[16:02] <pitti> thanks everyone
[16:02] <zul> hi
[16:02] <ttx> \o
[16:02] <kirkland> #startmeeting
[16:02] <Laney> cjwatson: can you approve my DMB ML subscription too?
[16:02] <MootBot> Meeting started at 10:02. The chair is kirkland.
[16:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:03] <smoser> o/
[16:03] <kirkland> howdy all
[16:03] <kirkland> [TOPIC] Review ACTION points from previous meeting
[16:03] <MootBot> New Topic:  Review ACTION points from previous meeting
[16:03] <smb> evening
[16:03] <cjwatson> Laney: no, I passed the keys for that to persia
[16:03] <Daviey> o/
[16:03] <kirkland>  * zul to send e-mail to ubuntu-server ML requesting help for testing 10.04.2 ISOs
[16:03] <jamespage> o/
[16:03] <hggdh> sorry for the delay, latests natty updates killed my laptop
[16:04] <kirkland> hggdh: no worries, just getting started now
[16:04] <zul> not done...it had to be kind of adhoc
[16:04] <kirkland> zul: ?
[16:04] <kirkland> zul: okay, no point in carrying though
[16:04] <kirkland> zul: as 10.04.2 is out
[16:04] <kirkland> zul: unless you want to get a headstart on asking for 10.04.3 testing?  :-)
[16:04] <zul> meh
[16:04] <Daviey> lol
[16:05] <kirkland> hrm
[16:05] <kirkland> looks like RoAkSoAx has not updated the agenda ....
[16:05]  * kirkland will need to wing it
[16:05] <kirkland> [TOPIC] Natty Development
[16:05] <kirkland> robbiew: ?
[16:05] <MootBot> New Topic:  Natty Development
[16:06] <robbiew> burn downs look good...bug count is fine
[16:06] <robbiew> forge ahead
[16:06] <robbiew> ;)
[16:06] <SpamapS> FF on Thursday right?
[16:06] <robbiew> yup
[16:06] <robbiew> if you think you need an FFE...talk to skaet
[16:06] <SpamapS> What features have we added this go 'round? I think we've done a lot in universe
[16:07] <Daviey> We are actually looking pretty good on upstream versions we care about i think
[16:07] <hggdh> warwarning to the adventurous: current ISO will not install
[16:07] <Daviey> The two i was watching was libvirt and multipath-tools
[16:07] <robbiew> https://wiki.ubuntu.com/ServerTeam/ReleaseStatus/Natty
[16:07] <Daviey> hallyn is cracking them out.
[16:07] <hallyn> yup
[16:07]  * zul is doing a couple of merges today
[16:08]  * SpamapS may attempt to finish an erlang merge today or tomorrow
[16:08] <zul> php5/apache/mysql
[16:08] <SpamapS> zul: want to review/sponsor that for me tomorrow?
[16:08] <kirkland> cool
[16:08] <zul> SpamapS: sure
[16:08] <kirkland> anything else related to natty, or FeatureFreeze?
[16:09] <zul> i have a couple of reviews that people want me to do on the list as well
[16:09] <Daviey> Hmm
[16:09] <Daviey> Currently daily, is not good.
[16:09] <Daviey> cjwatson is on the case AIUI.
[16:09] <hggdh> bug 723148
[16:09] <Daviey> thassim
[16:10] <Daviey> for us, i think we can consider it transitional
[16:10] <hggdh> yes, should (I hope) be resolved today
[16:10] <kirkland> cool
[16:10] <kirkland> so moving along ...
[16:11] <kirkland> [TOPIC] Ubuntu Server Team Events
[16:11] <MootBot> New Topic:  Ubuntu Server Team Events
[16:11] <kirkland> repeating last week:
[16:11] <kirkland> SCALE9x - Feb 25 - 27, Los Angeles (ClintByrum attending, DustinKirkland presenting)
[16:11] <kirkland> UKUUG Spring Conference - 22-24 March, ttx attending, talking OpenStack (and Ubuntu Server).
[16:11] <kirkland> anything else new to mention?
[16:11] <kirkland> perhaps UDS-O in Budapest?
[16:11] <SpamapS> I had a talk accepted at the MySQL UC in April.. but thats eons away
[16:11] <zul> oooh about what?
[16:11] <SpamapS> "Run Drizzle on Your Narwhal"
[16:11] <kirkland> May 9-13
[16:11] <kirkland> Sp4rKy: that's cool
[16:12] <kirkland> okay
[16:12] <SpamapS> < 3 months to figure out O .. which should be the alpha for server-P ;)
[16:12] <kirkland> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[16:12] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[16:12] <kirkland> hggdh: howdy, sir
[16:13] <hggdh> last two weeks have been sort of weird, with kernel SRU tests, and 10.04.2 (also tests)
[16:13] <hggdh> so not much on the front
[16:13] <hggdh> except that Hudson -- er, Jenkins -- is cranking pretty good
[16:13] <RoAkSoAx> hggdh: you putting together the test-rig today for euca/powernap thingy?
[16:14] <kirkland> hggdh: great to hear about Hudkins
[16:14] <hggdh> RoAkSoAx: I will try, but I am not sure I can install anything there, no ISO will install
[16:14] <SpamapS> hggdh: jhunt and I want to add some automated tests to the list for testing upstart job interaction.. I think we'll have to wait for UDS to fully spec it out tho
[16:14] <SpamapS> Hudkins.. lol
[16:14] <jamespage> nice
[16:14] <hggdh> SpamapS: this would be marvelous. I think, right now, my official laptop is dead on an upstart issue
[16:14] <Daviey> hggdh, please don't touch the two boxes with short m names without pinging me.
[16:15] <RoAkSoAx> hggdh: no worries, just let me know whenever its ready. I'm pretty sure what are the issues if they are powernap's side
[16:15] <hggdh> RoAkSoAx: fantastic, and willco
[16:15] <kirkland> hggdh: anything else?
[16:15] <hggdh> kirkland: no, this is it
[16:15] <kirkland> thanks
[16:15] <kirkland> [TOPIC] Weekly Updates & Questions for the Kernel Team (smb)
[16:16] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (smb)
[16:16] <kirkland> smb: howdy, sir
[16:16] <smb> kirkland, Hello sir
[16:16] <smb> Well actually not much newish from my side
[16:16] <kirkland> smb: anything worth mentioning?
[16:16] <kirkland> or, does anyone have questions for the kernel team?
[16:16] <smb> Currently trying to check up on some xfs regression
[16:17] <smb> Otherwise the things from last week wait for confirmation or me getting back to them
[16:17] <hallyn> xfs regressions?  is there a bug#?
[16:17] <smb> bug 692848
[16:18] <smb> possibly affects older releases as well
[16:18] <smb> but I failed on re-creating the failure
[16:18] <hallyn> thx
[16:18] <smb> so it is a bit hard to say
[16:18] <SpamapS> smb: did we give up on reproducing the NFS issue?
[16:19] <smb> SpamapS, Which of the many?
[16:19] <SpamapS> bug 661294
[16:19] <smb> We had failures on receiving large files, sending large files and I think other as well.
[16:19] <SpamapS> bug does seem a bit stalled as those affected have worked around it by bandwidth limiting their connections
[16:19] <smb> SpamapS, I think I asked in that bug about experience on a test kernel
[16:20] <SpamapS> Oh right :)
[16:20] <SpamapS> ok .. carry on.
[16:20] <kirkland> smb: cool, thanks, anything else?
[16:20]  * smb is done. :)
[16:20] <kirkland> thanks
[16:20] <kirkland> [TOPIC] Weekly Updates & Questions for the Documentation Team (sommer)
[16:20] <kirkland> doesn't look like sommer is around
[16:20] <MootBot> New Topic:  Weekly Updates & Questions for the Documentation Team (sommer)
[16:20] <kirkland> [TOPIC] Weekly Updates & Questions from the Ubuntu Community
[16:21] <MootBot> New Topic:  Weekly Updates & Questions from the Ubuntu Community
[16:21] <kirkland> anything here?
[16:21] <kim0> hey
[16:21] <kirkland> kim0: howdy
[16:21] <kim0> We've got two new contributing members
[16:21] <Daviey> \o/
[16:21] <kim0> following the JEos
[16:21] <SpamapS> \o/
[16:21] <kirkland> kim0: cool
[16:21] <Daviey> kim0, names?
[16:21] <kim0> QA needs
[16:22] <kim0> um, I forwarded to robbiew and marjo
[16:22] <kim0> I can get the names later
[16:22]  * Daviey drinks the jeos
[16:22] <kim0> hehe
[16:22] <Daviey> kim0, Oh aye, thanks!
[16:22] <kim0> also we've kickstarted a project
[16:22] <kim0> for migrating UEC images
[16:22] <kim0> across AWS regions
[16:22] <kim0> that's being driven by a community member
[16:22] <Daviey> kim0, were they are result of you blogging?
[16:22] <kim0> let me get a quick link
[16:23] <kim0> yes
[16:23] <Daviey> super
[16:23] <Daviey> So blogging seems more successful than the mailing list, perhaps
[16:23] <kim0> https://code.launchpad.net/~abd4lla/ec2-migrate-ebs-ami/ec2-migrate-ebs-ami
[16:23] <kim0> I'm shuffling "https://help.ubuntu.com/community/UEC/Images#preview" as we speak
[16:24] <kim0> to make it easier on the eye
[16:24] <smoser> kim0, woot!
[16:24] <kim0> that's mostly it
[16:24] <kim0> smoser: let me know if it looks better now .. still needs more polish though
[16:24] <smoser> well, it certainliy could'nt look worse, now could it
[16:24] <kim0> tried grouping by what the user wants to do
[16:24] <kim0> public cloud
[16:24] <kim0> private cloud
[16:24] <kim0> local hypervisor
[16:24] <kim0> make your own images
[16:25] <kim0> and split too advanced usage
[16:25] <kim0> on their own pages
[16:25] <kim0> let me know if you think it needs siginificant restructuring
[16:25] <kim0> otherwise .. I'll polish it some more
[16:25] <kirkland> sweet
[16:25] <kim0> for instance that huge graphic needs to be resized :)
[16:25] <kirkland> kim0: anything else?
[16:25] <kim0> nope thnx
[16:26] <kirkland> cool
[16:26] <kirkland> [TOPIC] Open Discussion
[16:26] <MootBot> New Topic:  Open Discussion
[16:26] <kirkland> let's have it
[16:26] <Daviey> nothing here
[16:26] <SpamapS> Keep on rockin in the free world :)
[16:27]  * RoAkSoAx wondering if anyone has any solutions for dual external monitors
[16:27] <kirkland> sweet
[16:27] <kirkland> [TOPIC] Announce next meeting date and time
[16:27] <MootBot> New Topic:  Announce next meeting date and time
[16:28] <kirkland>     Tuesday, March 1 2011 16:00 UTC
[16:28] <kirkland> #endmeeting
[16:28] <MootBot> Meeting finished at 10:28.
[16:28] <smb> kirkland, efficient driving :)
[16:28] <SpamapS> kirkland: thanks!
[16:28] <kirkland> smb: heh
[16:59] <JFo> o/
[16:59] <flag> o/
[16:59] <kamal> o/
[17:00] <smb> \o
[17:00] <bjf> #startmeeting
[17:00] <MootBot> Meeting started at 11:00. The chair is bjf.
[17:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[17:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty
[17:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty
[17:00] <bjf> # Meeting Etiquette
[17:00] <bjf> #
[17:00] <bjf> # NOTE: '..' indicates that you are finished with your input.
[17:00] <bjf> #       'o/' indicates you have something you'd like to add (wait until you are recognized)
[17:00] <bjf> #
[17:00] <bjf> [TOPIC] Release Metrics (JFo)
[17:00] <MootBot> New Topic:  Release Metrics (JFo)
[17:00] <JFo> Release Meeting Bugs (8 bugs, 10 Blueprints)
[17:00] <JFo> [17:00] <JFo>  * 4 linux kernel bugs (up 1)
[17:00] <JFo>  * 0 linux-ti-omap bugs (no change)
[17:00] <JFo>  * 0 linux-meta-ti-omap bug (no change)
[17:00] <JFo> [17:00] <JFo>  * 23 linux kernel bugs (up 1)
[17:00] <JFo>  * 0 linux-ti-omap bugs (no change)
[17:00] <JFo>  * 0 linux-meta-ti-omap bug (no change)
[17:00] <JFo> [17:01] <JFo>  * 7 blueprints (Including HWE Blueprints)
[17:01] <JFo> [17:01] <JFo>  * 72 Linux Bugs (up 17)
[17:01] <JFo> [17:01] <JFo>  * 94 Linux Bugs (up 1)
[17:01] <JFo> [17:01] <JFo>  * [[https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on | Bugs with Patches]]
[17:01] <JFo>  * [[http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/ | Breakdown by status]]
[17:01] <JFo> ..
[17:01] <bjf> [TOPIC] Blueprints: Natty Bug Handling (JFo)
[17:01] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling
[17:01] <MootBot> New Topic:  Blueprints: Natty Bug Handling (JFo)
[17:01] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling
[17:01] <JFo> nothing current to report
[17:01] <bjf> [TOPIC] Blueprints: Enhancements to the firmware test suite (cking)
[17:01] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-firmware-test-suite-enhancements
[17:01] <MootBot> New Topic:  Blueprints: Enhancements to the firmware test suite (cking)
[17:01] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-firmware-test-suite-enhancements
[17:02] <cking> Lots of tidying up
[17:02] <cking> 0.22.00 now in Natty universe
[17:02] <cking> ..
[17:02] <bjf> [TOPIC] Blueprints: Review of the Stable Maintenance Process (sconklin / bjf)
[17:02] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-process-review
[17:02] <MootBot> New Topic:  Blueprints: Review of the Stable Maintenance Process (sconklin / bjf)
[17:02] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-process-review
[17:02] <bjf> The Kernel Team's SRU report has moved out to a more publicly accessible location: http://kernel.ubuntu.com/~kernel-ppa/reports/sru-report.html
[17:02] <bjf> ..
[17:02] <sconklin> ||
[17:02] <sconklin> || Last week all open fixes for all kernels were verified. This means that we're now
[17:02] <sconklin> || in the Testing phase of the kernel SRU process. There are two reported regressions
[17:02] <sconklin> || in Maverick which are being investigated. They are:
[17:02] <sconklin> || https://bugs.launchpad.net/ubuntu/+source/linux/+bug/721213
[17:02] <sconklin> || https://bugs.launchpad.net/ubuntu/+source/linux/+bug/722747
[17:02] <sconklin> ||
[17:02] <sconklin> || Lucid and Maverick will receive testing from Certification and QA. We need testing from users
[17:02] <sconklin> || for all other kernels, to at least insure that they boot and run. If you boot any of these kernels,
[17:02] <sconklin> || please update the tracking bug for that kernel with the results. Tracking bugs can be found here:
[17:02] <sconklin> ||
[17:02] <sconklin> || http://kernel.ubuntu.com/~kernel-ppa/reports/sru-report.html
[17:02] <sconklin> ||
[17:02] <sconklin> ..
[17:03] <bjf> [TOPIC] Status: Cert. Team  (ara)
[17:03] <MootBot> New Topic:  Status: Cert. Team  (ara)
[17:03] <ara> o/
[17:03] <ara> We will be starting testing this week (tomorrow) the kernels for Maverick and Lucid
[17:03] <ara> We will finish and report back before March 1st
[17:03] <ara> ..
[17:04] <bjf> [TOPIC] Status: Ecryptfs (jj)
[17:04] <MootBot> New Topic:  Status: Ecryptfs (jj)
[17:05] <bjf> [TOPIC] Status: Ecryptfs (jj)
[17:05] <MootBot> New Topic:  Status: Ecryptfs (jj)
[17:05] <jjohansen> - took a bit of a detour last week with tyler exploring compression of filenames
[17:05] <jjohansen> still waiting on full review
[17:06] <jjohansen> ..
[17:06] <tgardner> o/
[17:06] <bjf> tgardner, go
[17:06] <tgardner> we've definitely decided to postpoone long file names until after 11.04 ?
[17:07] <jjohansen> tgardner: I believe so, dustin thinks its the way to go too
[17:07] <tgardner> apw, not sure if I saw that in the wiki page updates
[17:07] <apw> tgardner, will check into it
[17:07] <tgardner> ..
[17:08] <bjf> [TOPIC] Status: Natty (apw)
[17:08] <MootBot> New Topic:  Status: Natty (apw)
[17:08] <jjohansen> tgardner: I believe it was left open pending upstream review, in case it did happen
[17:08] <apw> The natty kernel is now at v2.6.38-4.31 (v2.6.38-rc5 based).  We have just rebased to v2.6.38-rc6 and uploaded, this should be in the archive before feature freeze. Overall we have most of our development out of the way, with just the ecryptfs long filename work ongoing.  We are currently concentrating on bug squashing for Natty.
[17:08] <apw> ..
[17:08] <bjf> [TOPIC] Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf)
[17:08] <MootBot> New Topic:  Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf)
[17:08] <sconklin> || Package                                    || Upd/Sec              || Proposed             ||  TiP || Verified ||
[17:08] <sconklin> ||                                            ||                      ||                      ||      ||          ||
[17:08] <sconklin> || dapper   linux-source-2.6.15               || 2.6.15-55.91         || 2.6.15-55.93         ||    0 ||        0 ||
[17:08] <sconklin> ||                                            ||                      ||                      ||      ||          ||
[17:08] <sconklin> || hardy    linux                             || 2.6.24-28.81         || 2.6.24-28.86         ||    0 ||        0 ||
[17:09] <sconklin> ||                                            ||                      ||                      ||      ||          ||
[17:09] <sconklin> || karmic   linux-fsl-imx51                   || 2.6.31-112.28        || 2.6.31-112.30        ||    1 ||        1 ||
[17:09] <sconklin> || ---      linux-ec2                         || 2.6.31-307.23        || 2.6.31-307.27        ||    0 ||        0 ||
[17:09] <sconklin> || ---      linux                             || 2.6.31-22.70         || 2.6.31-22.73         ||    0 ||        0 ||
[17:09] <sconklin> ||                                            ||                      ||                      ||      ||          ||
[17:09] <sconklin> || lucid    linux-ec2                         || 2.6.32-312.24        || 2.6.32-313.26        ||    8 ||        6 ||
[17:09] <sconklin> || ---      linux-ports-meta                  || <IP_ADDRESS>.21         || <IP_ADDRESS>.22         ||    0 ||        0 ||
[17:09] <sconklin> || ---      linux-mvl-dove                    || 2.6.32-211.27        || 2.6.32-214.30        ||    6 ||        6 ||
[17:09] <sconklin> || ---      linux-meta-mvl-dove               || <IP_ADDRESS>.12        || <IP_ADDRESS>.15        ||    0 ||        0 ||
[17:09] <sconklin> || ---      linux-lts-backport-maverick       || 2.6.35-23.41~lucid1  || 2.6.35-25.44~lucid1  ||    0 ||        0 ||
[17:09] <sconklin> || ---      linux-meta                        || <IP_ADDRESS>.32         || <IP_ADDRESS>.34         ||    0 ||        0 ||
[17:09] <sconklin> || ---      linux-firmware                    || 1.34.3               || 1.34.4               ||    0 ||        0 ||
[17:09] <sconklin> || ---      linux                             || 2.6.32-28.55         || 2.6.32-29.58         ||    6 ||        6 ||
[17:09] <sconklin> || ---      linux-fsl-imx51                   || 2.6.31-608.20        || 2.6.31-608.22        ||    1 ||        1 ||
[17:09] <sconklin> || ---      linux-backports-modules-2.6.32    || 2.6.32-28.27         || 2.6.32-29.28         ||    0 ||        0 ||
[17:09] <sconklin> || ---      linux-meta-ec2                    || <IP_ADDRESS>2.13        || <IP_ADDRESS>3.14        ||    0 ||        0 ||
[17:09] <sconklin> ||                                            ||                      ||                      ||      ||          ||
[17:09] <sconklin> || maverick linux-ports-meta                  || <IP_ADDRESS>.19         || <IP_ADDRESS>.21         ||    0 ||        0 ||
[17:09] <sconklin> || ---      linux-mvl-dove                    ||                      || 2.6.32-414.30        ||    4 ||        4 ||
[17:09] <sconklin> || ---      linux-meta-mvl-dove               ||                      || <IP_ADDRESS>4.4         ||    0 ||        0 ||
[17:09] <sconklin> || ---      linux-firmware                    || 1.38.3               || 1.38.4               ||    1 ||        1 ||
[17:09] <sconklin> || ---      linux                             || 2.6.35-25.44         || 2.6.35-27.47         ||   13 ||       13 ||
[17:09] <sconklin> || ---      linux-backports-modules-2.6.35    || 2.6.35-25.16         || 2.6.35-27.18         ||    0 ||        0 ||
[17:09] <sconklin> || ---      linux-meta                        || <IP_ADDRESS>.32         || <IP_ADDRESS>.34         ||    0 ||        0 ||
[17:09] <sconklin> ||                                            ||                      ||                      ||      ||          ||
[17:09] <sconklin> ..
[17:10] <bjf> [TOPIC] Incoming Bugs: Regressions (JFo)
[17:10] <MootBot> New Topic:  Incoming Bugs: Regressions (JFo)
[17:10] <JFo> Incoming Bugs
[17:10] <JFo>  180 Natty Bugs (up 11)
[17:10] <JFo>  1185 Maverick Bugs (up 33)
[17:10] <JFo>  1019 Lucid Bugs (up 6)
[17:10] <JFo> Current regression stats (broken down by release):
[17:10] <JFo> [17:10] <JFo>   * 39 maverick bugs (no change)
[17:10] <JFo>   * 77 lucid bugs (no change)
[17:10] <JFo>   * 7 karmic bugs (no change)
[17:10] <JFo>   * 0 hardy bugs (no change)
[17:10] <JFo> [17:10] <JFo>   * 70 natty bugs (not tracked yet)
[17:10] <JFo>   * 237 maverick bugs (up 9)
[17:10] <JFo>   * 208 lucid bugs (no change)
[17:10] <JFo>   * 38 karmic bugs (no change)
[17:11] <JFo>   * 2 hardy bugs (no change)
[17:11] <JFo> [17:11] <JFo>   * 1 natty bugs (down 2)
[17:11] <JFo>   * 2 maverick bugs (down 4)
[17:11] <JFo>   * 0 lucid bugs (no change)
[17:11] <JFo>   * 0 karmic bug (no change)
[17:11] <JFo> ..
[17:11] <bjf> [TOPIC] Incoming Bugs: Bug day report (JFo)
[17:11] <MootBot> New Topic:  Incoming Bugs: Bug day report (JFo)
[17:11] <JFo> Today is Bug Day. We are looking at bugs in the new state. I'd like to ae another Bug Day next week covering Confirmed bugs. I'll post details to the mailing lists and our voices blog. I've also added twitter notices to my list of announcements for Bug Days, so far we have had a more positive response to this than I expected.
[17:11] <JFo> ..
[17:11] <bjf> [TOPIC] Triage Status (JFo)
[17:11] <MootBot> New Topic:  Triage Status (JFo)
[17:11] <JFo> nothing to report.
[17:11] <JFo> ..
[17:11] <bjf> [TOPIC] Open Discussion or Questions: Raise your hand to be recognized (o/)
[17:11] <MootBot> New Topic:  Open Discussion or Questions: Raise your hand to be recognized (o/)
[17:12] <bjf> thanks everyone
[17:12] <bjf> #endmeeting
[17:12] <MootBot> Meeting finished at 11:12.
[17:12] <JFo> thanks bjf :)
[17:12] <kamal> thanks bjf - lightning quick :-)
[22:12] <jdstrand> o/
[22:12] <micahg> o/
[22:13] <nxvl> o/
[22:13] <jdstrand> the ubuntu-security team (and friends) is going to have a quick meeting to make up for yesterday
[22:13] <jdstrand> #startmeeting
[22:13] <MootBot> Meeting started at 16:13. The chair is jdstrand.
[22:13] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[22:13] <sbeattie> o/
[22:13] <jdstrand> The meeting agenda can be found at:
[22:13] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[22:13] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/Meeting
[22:14] <mdeslaur> o/
[22:14] <jdstrand> [TOPIC] Review of any previous action items
[22:14] <MootBot> New Topic:  Review of any previous action items
[22:14] <jdstrand> We didn't have any specific ones. I know sbeattie has been working on apparmor upstream releases and they are basically done
[22:14] <jdstrand> (that was a previous action item)
[22:14] <mdeslaur> kees keyword highlight bomb: security hack rootkit virus
[22:14] <jdstrand> \o/
[22:14] <jdstrand> [TOPIC] Weekly stand-up report
[22:14] <MootBot> New Topic:  Weekly stand-up report
[22:14] <jdstrand> I'll go first
[22:15] <jdstrand> I tested amd64 builds of firefox and xul this week already
[22:15] <jdstrand> planning on helping sbeattie with the apparmor upload for natty FF
[22:15] <jdstrand> also am working with hallyn on the libvirt merge
[22:16] <jdstrand> and since someone pointed out ufw is using the wrong preferred python packaging, I fixed that and am fixing up a few other little packaging things there
[22:16] <jdstrand> I am in the happy place, and am basically trying to help get things into shape for FF
[22:17] <jdstrand> I figure there is going to be a lot of archive admin work as a result
[22:17] <jdstrand> I'm done
[22:17] <jdstrand> mdeslaur: you'r eup
[22:17] <mdeslaur> I just pushed my mailman USN out
[22:17] <mdeslaur> and am waiting for the lucid fuse -proposed package to release, and then I'll push fuse
[22:17] <mdeslaur> I am working on an embargoed issue
[22:18] <mdeslaur> and am currently looking at bind9 issues
[22:18] <mdeslaur> (need to figure out what to do with bind9...)
[22:18] <mdeslaur> and would like to poke with gnome-screensaver to fix the automatic login/reboot issue
[22:18] <mdeslaur> and thursday I'm on patchpiloting
[22:18] <mdeslaur> that's it for me
[22:19] <jdstrand> sbeattie: you're up
[22:21] <sbeattie> I'm working on an openjdk-6 update; I hit build issues caused by upstream, and was hoping for input from doko.
[22:21] <sbeattie> I'll be releasing apparmor 2.6.0 final this week and also working to push that into natty before FF.
[22:22] <sbeattie> I'm on triage as well.
[22:22] <sbeattie> I think that's all for me.
[22:23] <jdstrand> micahg: you're up
[22:23] <micahg> jdstrand: upcoming week, right?
[22:23] <jdstrand> micahg: yeah, or stuff you've been working on that is affecting your work this week
[22:23] <jdstrand> micahg: or blockers
[22:24] <micahg> need to get new build of thunderbird uploaded to mozilla-security PPA
[22:24] <micahg> test Firefox/Thunderbird i386
[22:24]  * jdstrand will test tbird/amd64
[22:24] <micahg> I volunteered to patch pilot to clear out things for FF
[22:25] <micahg> also, still getting stuff setup (local mirror, sbuild)
[22:25] <micahg> that's it for me
[22:25] <jdstrand> we'll skip kees
[22:26] <jdstrand> jjohansen: is there anything you need from us for natty outside of the apparmor 2.6 userspace work sbeattie is working on?
[22:27] <jjohansen> jdstrand: hrmm no I don't think so, everything I have has either moved to future versions or bugs
[22:27] <jdstrand> jjohansen: ok
[22:27] <jdstrand> [TOPIC] Miscellaneous and Questions
[22:27] <MootBot> New Topic:  Miscellaneous and Questions
[22:27] <jjohansen> uh well unless you want to thin the thicket of papers I am working through
[22:27] <jdstrand> fyi, I've added prepare_source() in testlib for in build tests in QRT
[22:28] <jdstrand> there is some documentation in there for how to use it
[22:28] <jdstrand> it is useful when you find a test suite in the source, but it isn't enabled in the build
[22:28] <jdstrand> it helps you setup things to download and unpack the source, then patch
[22:28] <jdstrand> and how to clean up
[22:29] <jdstrand> test-telepathy-gabble.py and test-dbus.py both use it
[22:29] <jdstrand> test-apparmor.py needs to be converted to it
[22:29] <sbeattie> jjohansen: papers?
[22:29] <jdstrand> I've been using this method instead of checking things into build_results
[22:30] <jdstrand> anyhoo, fyi
[22:30] <jdstrand> I don't have anything else
[22:30] <jjohansen> sbeattie: fsa and maximal spanning tree type stuff
[22:30] <jdstrand> jjohansen: heh, I won't be touching those :P
[22:30] <jjohansen> I am trying to work through references
[22:30] <jdstrand> jjohansen: that said, I could proofread for you
[22:30] <sbeattie> jdstrand: great! I've been meaning to do something like that for a mythical test-core-utils
[22:31] <jjohansen> jdstrand: I do have some writing I was planning on kicking your way
[22:31] <jdstrand> sbeattie: there are probably some warts, but it is a start
[22:31] <jdstrand> jjohansen: cool
[22:31] <jdstrand> does anyone have any other questions or items to discuss?
[22:32]  * jdstrand takes that as a 'no'
[22:32] <mdeslaur> nope
[22:32] <jdstrand> thanks everyone! :)
[22:32] <jdstrand> #endmeeting
[22:32] <MootBot> Meeting finished at 16:32.
[22:34] <kees> man, I perfectly timed that


[17:49] <Pendulum> AlanBell: charlie-tca you two have both tried Natty, right?
[17:50] <charlie-tca> yes
[17:50] <charlie-tca> I have
[17:50] <charlie-tca> I try a fresh installation about three times a week
[17:50] <Pendulum> charlie-tca: how bad is it? I'm trying to decide if I should try upgrading my mini to just use it as a test machine
[17:51] <charlie-tca> Not too bad, just can't find any keyboard shortcuts most days
[17:51] <charlie-tca> It requires the mouse, still
[17:51] <Pendulum> do they exist yet?
[17:51] <charlie-tca> not yet
[17:51] <Pendulum> TheMuso: do we have any ETA on the keyboard shortcuts at this point?
[17:52] <Pendulum> I'm in the middle of the doc team meeting where they're trying to decide how to manage docs since they'll need things for gnome2 and Unity
[17:52] <charlie-tca> That should be fun ;-)
[17:52] <Pendulum> to make it more fun a lot of the docs team is not happy about doing unity docs because of the copyright issue (don't blame 'em on that)
[17:53] <charlie-tca> I think they are still hoping for shortcut keys for alpha2
[17:53] <Pendulum> they were supposed to be in alpha1 which is why I'm hoping Luke has more info
[17:55] <charlie-tca> They got bumped on the blueprint for unity
[17:55] <Pendulum> I know
[17:56] <Pendulum> but they got bumped really last minute
[17:56] <Pendulum> and I'd rather know now if they won't make alpha2!
[18:24] <AlanBell> I have tried natty
[18:25] <AlanBell> the installer was broken so I installed Maverick and upgraded


[02:33] <riiot232> hello
[14:16] <coreycb> bdmurray: thanks for helping move bug 1809454 along. would you be able to take a look at bionic today?
[14:39] <cpaelzer> coreycb: is the 18.04.2 freeze lifted already ?
[14:39] <coreycb> cpaelzer: ahh, maybe not.
[15:01] <coreycb> cpaelzer: do you think we can re-evaluate this MIR? https://bugs.launchpad.net/ubuntu/+source/placement/+bug/1805691
[15:02] <coreycb> the security team ACKed it I believe
[15:02] <coreycb> i don't think nova is going to drop their placement support until train (corresponds to Ubuntu E release) but it would be nice if we could move forward with charm changes
[15:16] <cpaelzer> coreycb: yes and done
[15:16] <coreycb> thanks very much cpaelzer
[15:23] <seb128> if some wonder why retracing are failing recently in disco, bug #1815774
[15:24] <seb128> doko, ^
[15:44] <riiot232> hello
[15:44] <riiot232> is some one there.....?
[15:47] <LtWorf> riiot232: no :P
[15:48] <riiot232> :l
[15:48] <riiot232> why?
[15:48] <riiot232> where is every one at?
[15:48] <LtWorf> (i was kidding)
[15:48] <riiot232> ok.
[15:48] <riiot232> so are u dev?
[15:48] <LtWorf> anyway i'm more active on debian, which is oftc rather than freenode
[15:49] <riiot232> ok
[15:50] <bdmurray> seb128: How did you find bug 1815774? Were you manually retracing something or looking at logs / failures to retrace?
[15:51] <LtWorf> riiot232: very minor contributions in debian, that then end up in ubuntu
[15:51] <seb128> bdmurray, I wondered why we got a few bugs invalidated by the retracers so I decided to try to sigsegv g-c-c locally and see what was the problem
[15:51] <riiot232> LtWorf ok
[15:51] <riiot232> how do I say ur name?
[15:51] <seb128> bdmurray, which gave me the warnings described in the bug, which I google for, found thar arch bug...
[15:52] <bdmurray> seb128: Hmm, I thought I was subscribed to apport-failed-retrace but didn't notice anything. I'll have to dig.
[15:52] <seb128> bdmurray, https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1815703
[15:52] <seb128> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1815704
[15:52] <seb128> if you want some examples
[15:52] <bdmurray> seb128: cool, thanks
[15:53] <seb128> bdmurray, they didn't got tagged apport-failed-retrace it looks like, just untagged
[15:53] <bdmurray> what's up with that ascii art?
[15:53] <seb128> so maybe an apport bug there
[15:53] <seb128> lol, good question :)
[15:53] <bdmurray> ah, well then
[15:54] <bdmurray> wow, pretty colors too
[15:55] <chiluk> So I discovered today that my ubuntu one login has 2fa enabled, but since I'm no longer at Canonical, I'm no longer in the correct groups that tell Ubuntu One I need to see 2fa configuration pages... Seems like we should auto-enroll all members of ex-canonical in sso-2f-testers  *(or maybe some other group)..  The strangest thing was that I was able to log in to ubuntu one using only my user/pass, but when trying to enable
[15:55] <chiluk> livepatch it required my 2fa ..
[15:57] <chiluk> who owns ubuntu sso / one login now?
[15:57] <cjwatson> the snap store team
[15:58] <cjwatson> What you describe is interesting; I've heard people with this problem before but not the specifics about logging into login.u.c directly vs. via something like livepatch
[15:58] <cjwatson> Though it's possibly related to the same kind of thing that caused https://bugs.launchpad.net/canonical-identity-provider/+bug/1073074
[15:59] <chiluk> Cool I'll move conversation to that bug..
[15:59] <cjwatson> I'm not certain it's the same thing, so I'd suggest a new bug
[15:59] <cjwatson> Can always be duped later
[15:59] <chiluk> Yeah I'll proceed with due diligence.
[15:59] <cjwatson> I don't think auto-adding people to a team is the solution
[16:00] <chiluk> I'm not sure what the right answer is either.. nor do I have the power any more.
[16:00] <cjwatson> Well, it seems that if a user is set to require 2FA then we should show them 2FA ...
[16:01] <cjwatson> (which is what I thought the behaviour was, but the difference between direct login and via livepatch suggests maybe not on all code paths)
[16:03] <chiluk> right..
[16:03] <chiluk> also explains why I haven't noticed till now..
[16:05] <cjwatson> chiluk: livepatch via CLI or OpenID?
[16:05] <chiluk> It was via the "Software & Updates" application...  I forget what the actual runtime is for that.
[16:06] <cjwatson> chiluk: OK, worth also trying something that's definitely OpenID, e.g. open a private browser window and try to sign into LP using it
[16:06] <chiluk> although I think I hit this via cli before as well when following the livepatch instructions.
[16:06] <cjwatson> I have to go out shortly though
[16:07] <chiluk> now I'm really confused.. via a private browser it required 2fa..
[16:07] <chiluk> so it could likely be the same issue.
[16:18] <cjwatson> chiluk: And double-check direct login to login.u.c via a private browser?
[16:20] <chiluk> yeah also requires 2fa..
[16:20] <cjwatson> so I'm not sure what you mean by "I was able to log in to ubuntu one using only my user/pass"
[16:20] <chiluk> I was just added to https://launchpad.net/~sso-2f-testers ... and can now configure the 2fa devices..
[16:20] <cjwatson> oh
[16:20] <cjwatson> in that case all tests after the point when you were added to that team should be flagged as uninteresting for the purpose of this bug
[16:20] <cjwatson> evidence now invalid
[16:20] <chiluk> yeah.
[16:21] <chiluk> I'm not sure when that exactly happened.
[16:21] <cjwatson> LP should have the timestamp
[16:21] <chiluk> right but I dont' have timestamps on my browsers.
[16:21] <cjwatson> ah
[16:22] <cjwatson> well, it happened at 15:53:25
[16:22] <cjwatson> which was a couple of minutes before you asked about it here
[16:22] <cjwatson> so anything you did in response to my questions can't be useful evidence
[16:22] <chiluk> yeah.
[16:22] <cjwatson> oh well
[16:23] <chiluk> cjwatson want to remove me from sso-2f-testers  to retest?
[16:23] <chiluk> does it matter?
[16:23] <chiluk> I'm willing to help out for a few minutes if you are intrigued.
[16:23] <chiluk> I figure you getting removed from canonical might be more prohibitive for testing.
[16:24] <cjwatson> (a) I can't do that since I'm not an admin of sso-2f-testers, (b) we can set up a similar situation with a local SSO deployment, (c) I have to go out
[16:25] <cjwatson> so thanks but we should be able to manage :)
[16:25] <chiluk> sure thing..
[16:25] <chiluk> it's been nice seeing an old-familiar nic...
[16:25] <chiluk> I haven't played here in far too long.
[16:26] <roadmr> chiluk: hey, I enabled your 2fa group membership, so maybe I can help, but give me a few because I'm busy atm
[16:27] <chiluk> yeah my day is pretty busy too..
[16:27] <cjwatson> ah, roadmr is likely in a better position to help with this than I am anyway, excellent
[16:35] <chiluk> roadmr: I described what I was seeing here : https://bugs.launchpad.net/canonical-identity-provider/+bug/1073074    I think the two are probably the same.
[16:37] <roadmr> chiluk: ok, reading the bug now and I checked the backlog as well
[16:41] <roadmr> chiluk: ok so to summarize, as an ex-canonicaler, you saw different 2fa requirements for API (i.e. gnome-software) vs. web (login.ubuntu.com) ?
[16:41] <roadmr> chiluk: the code does have custom logic for how to decide 2fa-ness for someone in canonical vs. someone in ~sso-2f-testers
[16:42] <roadmr> so that's where I'd start looking but it does look like a bug. I'll investigate!
[16:42] <roadmr> chiluk: and to be clear, are things working well for you now?
[16:46] <chiluk> Yeah things are fine now.
[16:46] <chiluk> the weirdest thing is that openid/web login seemed to work fine and did not require 2fa...
[16:47] <roadmr> yes, that's weird
[16:47] <chiluk> and I'm positive of this because I've been using launchpad for years without my yubikey..
[16:47] <chiluk> today I had to go grab my old yubikey that I had previously had linked.
[16:47] <chiluk> all my devices were still configured.
[16:47] <roadmr> chiluk: which email address do you use to log in these days? (you can pm it to me if you don't want to expose it here)
[16:48] <roadmr> this is so I can look you up and check your account setup, so I can then trace how the logic handles your login attempts via api vs. web
[16:48] <chiluk> Including my old @canonical authenticator app. *(I actually wonder if that is a mini security hole)...
[16:49] <chiluk> is there a better channel for this?  no need to spam everyone here.
[17:01] <roaksoax> ~/win 4
[17:20] <sparr> is there an appropriate channel for support-in-investigating-and-filing-a-bug-report in a mainline kernel package?
[17:22] <rbasak> sparr: mainline as in upstream? Or Ubuntu?
[17:22] <rbasak> For Ubuntu, #ubuntu-kernel
[17:29] <sparr> thanks
[17:50] <roaksoax> /win/win 4
[23:05] <seb128> wgrant, cjwatson, hey, can we open disco for translations?
[23:10] <wgrant> seb128: I believe it's just blocked on UTC turning it on
[23:11] <wgrant> Oh, or maybe not
[23:11] <wgrant> Hm
[23:11] <wgrant> Apparently we never initialised it
[23:11] <wgrant> Things are a bit on fire atm, may be able to look later.
[23:13] <seb128> wgrant, no hurry, thx


[00:33] -queuebot:#ubuntu-release- Unapproved: rejected openssl [sync] (xenial-proposed) [1.0.2g-1ubuntu4.20]
[00:40] -queuebot:#ubuntu-release- Unapproved: accepted openssl [sync] (xenial-proposed) [1.0.2g-1ubuntu4.20]
[00:44] <vorlon> rbasak: seems that despite the board being public I can't make comments to cards on https://trello.com/b/XgBxtrZ9/sru can that be changed?
[11:20] -queuebot:#ubuntu-release- Unapproved: gnome-shell-extension-desktop-icons (hirsute-proposed/universe) [20.04.0+git20200908-5ubuntu0.1 => 20.04.0+git20200908-5ubuntu0.2] (ubuntu-desktop)
[11:23] -queuebot:#ubuntu-release- Unapproved: gnome-shell-extension-desktop-icons (focal-proposed/main) [20.04.0-3~ubuntu20.04.2 => 20.04.0-3~ubuntu20.04.3] (ubuntu-desktop)
[12:25] <rbasak> vorlon: I sent you an invite link privately. Not sure if it should be SRU team change permission only, or everyone.
[16:19] <vorlon> rbasak: thanks