[02:05] <robbmunson> be back in just a few minutes, gotta restart kde
[09:44] <elkbuntu> hmm.. must be the not-now week
[15:01] <cjwatson> Keybuk: around?
[15:01] <cjwatson> Keybuk: clan says Matt and Mark won't be
[15:02] <Keybuk> yup
[15:02] <Keybuk> badly timed typing break
[15:03] <cjwatson> I don't see a whole lot of business, though
[15:03] <cjwatson> patent policy from mdz, presumably in abeyance until next week
[15:03] <Keybuk> I think we have to do your swearing in :)
[15:04] <cjwatson> you can approve my subscription to technical-board@ if you like ;-)
[15:05] <cjwatson> I swear to faithfully preserve, protect, and defend the code of conduct ... oh wait, that's the community council
[15:05] <Keybuk> ok, ML subscription approved
[15:05] <Keybuk> welcome aboard
[15:06] <cjwatson> ta muchly
[15:07] <Keybuk> dholbach: are there any outstanding nominations we should consider?
[15:07] <dholbach> Keybuk: which were the last ones that you processed?
[15:07] <dholbach> Keybuk: I'll check the archives, hang on
[15:07] <cjwatson> did we process the request for selective upload for Stefan Bader?
[15:08] <cjwatson> s/we/you/
[15:08] <dholbach> Keybuk: Dustin was the last one
[15:08] <Keybuk> dholbach: Dustin Kirkland, Stephan Graber (LTSP)
[15:08] <dholbach> ah yes, Stephane too
[15:08] <Keybuk> cjwatson: we did, that was approved
[15:08] <dholbach> then it's all resolved now
[15:09] <cjwatson> I'm curious as to which applications are in the MC pipeline
[15:09] <Keybuk>  * Open Applications: Nick Ellery (UUC), Jonathan Thomas (MOTU),
[15:09] <Keybuk> Michael Casadevall (core-dev), Alessio Treglia (MOTU)
[15:09] <dholbach> they're all in process still and we plan to have them resolved soon (before we hold our meetings and move to the new process)
[15:09] <dholbach> some are lacking votes, some are lacking input from sponsors
[15:10] <Keybuk> *nods* the new process looked good
[15:10] <dholbach> thanks for the flowers
[15:10] <dholbach> :)
[15:10] <Keybuk> I don't see anything from the other outstanding issues that is ready for discussion yet
[15:11] <Keybuk> ok, any business from anyone today?
[15:12] <cjwatson> has the calendar stuff from last meeting been resolved?
[15:12] <cjwatson> it seems that we just need to invite the appropriate magic address
[15:12] <cjwatson> I can do that now, if folks would like
[15:12] <Keybuk> matt recorded an action to follow up with the news team, but I don't know whether that has been done
[15:12] <james_w> https://wiki.ubuntu.com/Fridge/Calendar
[15:13] <Keybuk> the technical board meeting still doesn't appear there
[15:13] <cjwatson> let me try
[15:13] <james_w> they are now using google calendar, and the drupal calendar is abandoned
[15:13] <cjwatson> there it is
[15:14] <cjwatson> that should be the whole series added now
[15:14] <cjwatson> and indeed http://fridge.ubuntu.com/calendar is now correct
[15:14] <Keybuk> heh, did we both do that ?
[15:14] <cjwatson> maybe :)
[15:14] <Keybuk> well, it seems that google figured it out anyway ;)
[15:15] <Keybuk> that should be paired with the event our calendars, right?  so if we move it, it'll move on the fridge
[15:16] <cjwatson> I *think* so
[15:17] <cjwatson> Daniel asked if we could look at the per-package uploader proposal
[15:17] <cjwatson> https://lists.ubuntu.com/mailman/private/technical-board/2009-January/002892.html
[15:18] <Keybuk> good idea
[15:18] <dholbach> persia, soren, nixternal: around?
[15:19] <Keybuk> http://pastebin.com/m2ea34e91
[15:19] <Keybuk> ^ public viewable copy
[15:19] <dholbach> thanks Keybuk
[15:19] <soren> dholbach: hm?
[15:19] <cjwatson> my main concern, on a quick reading, is that ditching the expectation of social integration with the larger team altogether seems to invite problems
[15:20] <cjwatson> I agree that per-package uploaders don't need to be quite so plugged into the development community as generalist developers
[15:20] <dholbach> soren: talking about "per package upload" requirements
[15:20] <Keybuk> cjwatson: this has been my general concern as well; I still feel it's important that per-package uploaders still consider themselves to be Ubuntu Developers and participate in the wider community
[15:20] <Keybuk> also that the MOTU team, as it currently stands, seems most effective at supporting its own members and potential members
[15:20] <cjwatson> but we have talked recently about single-package-only uploaders having TB voting rights and generally being considered Ubuntu developers, which seems to point towards some degree of social cohesion
[15:20] <Keybuk> and I'm not sure how per-package uploaders would get support for problems they encounter
[15:21] <dholbach> is there specific portion of the text that you'd like to be changed or something else to be added?
[15:21] <cjwatson> I'm offering hopefully-constructive criticism rather than a patch :-)
[15:22] <Keybuk>   1) There is no expectation that the applicant meets the requirements
[15:22] <Keybuk>   of Ubuntu Membership, so the prior demonstration of significant and
[15:22] <Keybuk>   sustained contribution to Ubuntu is waived.
[15:22] <Keybuk> as I understand it, we are explicitly talking about granting ubuntu membership rights to such uploaders
[15:22] <dholbach> cjwatson: OK, I'm not asking you to write it, but what do you feel is the specific expectation that you'd have in that regard :-)
[15:22] <cjwatson> I'd sort of like the proposal to incorporate the notion that the candidate should be working with other Ubuntu developers rather than against them
[15:22] <Keybuk> therefore it seems alien to me that the requirements would be waived
[15:23] <nixternal> yo yo
[15:23] <Keybuk> cjwatson: indeed, this goes on to specifically say that per-package uploaders need not be expected to work on the team or be integrated with it
[15:23] <cjwatson> I have a concern that we might be approving developers who have an entirely different mindset about how the system should work, and might proceed to make their package conform to their view of the world, without regard for wider integration
[15:23] <nixternal> dholbach: what's up?
[15:24] <cjwatson> this kind of thing, indeed, *has* been a problem, and the fact that we expect developers to work as part of a team is very important in mitigating it
[15:24] <dholbach> I'm all for per-package uploaders working with the community and understanding that there's no "lock". And that they demonstrate that they have worked with others beforehand.
[15:24] <Keybuk> otoh, where this has worked so far has been in the kernel team
[15:24] <Keybuk> where there's explicitly an expectation that they do work with that team
[15:25] <Keybuk> and they are being granted upload rights *because* they work closely with that team, and to avoid them having to rely on their team-mates for sponsorship
[15:25] <cjwatson> I would be happier if the proposal said "There is a reduced expectation that the applicant is socially integrated ..." rather than "no expectation"
[15:25] <dholbach> Still they might have worked with a smaller set of sponsors and the expectations on a technical level are different from what we expect from applicants now.
[15:25] <Keybuk> cjwatson: I'm not sure I'd even be happy with a reduced expectation
[15:25] <Keybuk> somebody who can upload to Ubuntu should see themselves as a fully socially integrated member of the Ubuntu Developer team
[15:26] <Keybuk> I would rather the distinction was simply viewed as a technical one
[15:26] <cjwatson> dholbach: sure, they don't have to work with everyone on the planet, but I don't agree that we should be laying out criteria that allow for a per-package developer to work in their own little corner and disregard what else is happening
[15:26] <cjwatson> or, at least, criteria that suggest that that's OK
[15:26] <Keybuk> a per-package uploader is somebody with a specific skill set that uploads a package they are familar with
[15:26] <cjwatson> (obviously it's not put that way right now, I'm elaborating)
[15:26] <Keybuk> a MOTU member is somebody who's skill set is wide and varied
[15:26] <dholbach> cjwatson: I definitely agree with what you're saying and will work with the MC to make it clearer in the proposal
[15:27] <persia> I'm happy with the idea of requiring all developers to be members: that proposal was written some time ago.
[15:27] <cjwatson> Keybuk: yeah, that matches my expectation more closely, I must say: narrow skills, broad openness to integration
[15:27] <cjwatson> dholbach: I certainly agree that the technical expectations are very different; no argument there
[15:28] <dholbach> Keybuk: what interests me most is cases where people really just care about one or two package, have worked with one or two sponsors (through the process, understanding our processes and stuff), but have merely added a patch or two or packaged new upstream version, but on the other hand demonstrated that tey deeply care about the package and have an excellent bug story and an excellent upstream story to tell
[15:28] <cjwatson> the "does not grant sole-maintainership" bit in Emmet's proposal is good
[15:28] <Keybuk> dholbach: those are the cases that worry me most
[15:28] <Keybuk> because I forsee those people being so attached to their package that, if they are not also socially integrated with Ubuntu, will lead to difficulties
[15:29] <Keybuk> they might revert patches other Ubuntu developers make to their package
[15:29] <Keybuk> they might fail to participate in transitions or large-scale work that affects their package
[15:29] <cody-somerville> The barrier to MOTU is not overly high. Why even allow per-package uploader rights to not-motu?
[15:29] <cody-somerville> *non-motu
[15:29] <Keybuk> (and I would claim that this already happens)
[15:29] <dholbach> cody-somerville: because it's very hard to judge in cases like the one I described above
[15:29] <cjwatson> cody-somerville: because, at the moment, the MOTU barrier involves demonstrating an ability and interest in general contributions
[15:29] <persia> I'd rather expect single-package-uploaders to fail to participate in transitions or other large-scale work, just from lack of notification, if nothing else.
[15:30] <Keybuk> cody-somerville: MOTU has general upload access to the entire universe component, and as such, applicants are expected to be technically diverse in their skills
[15:30] <cjwatson> cody-somerville: (and this is expected to evolve with archive-reorganisation)
[15:30] <cjwatson> persia: and I think that's OK, it's clearly not their interest
[15:30] <Keybuk> I guess what'd I expect from per-package uploaders is somebody who meets all the social requirements of MOTU
[15:30] <cody-somerville> That doesn't seem to be the case. I see a lot of applicants get approved base on a sub-set of interest.
[15:30] <persia> Right.
[15:30] <Keybuk> and has made a sustained contribution
[15:30] <cjwatson> persia: as long as they don't block it
[15:30] <Keybuk> but only in a small subset of area
[15:30] <cjwatson> cody-somerville: it has been a practical problem in a number of specific cases
[15:31] <cjwatson> cody-somerville: cf. the kernel developers who are only interested in hacking on the kernel and so don't build up the packaging experience needed for MOTU
[15:31] <Keybuk> Matthew East is a good example here, he has had a single package sponsored for a long time now, and is well integrated into Ubuntu
[15:31] <dholbach> Keybuk: you said that these cases worried you the most - what would ease your fears there, what kind of story would you like to see first?
[15:31] <Keybuk> he would seem to be an obvious choice, even though he is not a MOTU member
[15:31] <Keybuk> dholbach: I think we go back to "why can't they be members of MOTU" ?
[15:31] <cjwatson> dholbach: the warning bell for me is when they start off by saying that Ubuntu's doing it all wrong :-)
[15:31] <cjwatson> (which can be OK, obviously there are some things we *are* doing wrong, but it can also be a sign of somebody with a very fixed agenda)
[15:32] <dholbach> cjwatson: I'll make a note to check archives and Google for instances of them saying that before sending in my +1 :-)
[15:32] <persia> Keybuk, Could I ask you to please not use the phrase "MOTU Member"?  It's somewhat confusing, and has been misused by others.  Would just "MOTU" work for your meaning?
[15:32] <cjwatson> perhaps we could say "generalist developer" ;-)
[15:32] <persia> That might be even better, as it looks towards archive reorganisation.
[15:32] <Keybuk> ok, let me a little more specific
[15:33] <dholbach> Keybuk: being MOTU would not help mdke
[15:33] <cjwatson> dholbach: I think personally I'd like to see examples of them working with other Ubuntu developers to at least some extent, even if that's just constructive engagement with their bug reports
[15:33] <cjwatson> mdke would pass that with flying colours
[15:33] <dholbach> cjwatson: sounds good
[15:33] <Keybuk> If somebody wishes upload rights to a package, why would we not simply require that they join the development team that maintains that component and provides upload rights as part of the team permissions?
[15:34] <cjwatson> well, because many packages aren't in any team smaller than "Ubuntu developers"
[15:34] <dholbach> Keybuk: how do you judge that if they just touched one package (and did it well), but their main contribution was liaising with users, upstreams and other distro maintainers?
[15:34] <persia> Keybuk, What if there exists no such specialised team, and they are the only one who wants to work on that specific package?
[15:34] <Keybuk> dholbach: let me pick up on a point there already
[15:35] <Keybuk> you suggest that they should already have been touching that package in Ubuntu
[15:35] <Keybuk> assumedly through sponsorship
[15:35] <Keybuk> I agree wholeheartedly
[15:35] <dholbach> *nod*
[15:35] <Keybuk> that they are liasing with users, upstreams and other distro maintainers suggests that they are using Launchpad and the Ubuntu Mailing lists already
[15:36] <Keybuk> the only difference to my mind:
[15:36] <Keybuk> - if they have contributed to a wide variety of different packages, they are suitable for a generalist team membership
[15:36] <Keybuk> - if their contribution has been to a narrow set of packages (or even just one), they are suitable for per-package upload rights
[15:36] <Keybuk> all other requirements should be the same
[15:37] <persia> I think there's three categories.
[15:37] <persia> There's generalist developers
[15:37] <Keybuk> Generalist UBUNTU Developers
[15:37] <Keybuk> Ubuntu developers who are generalists
[15:37] <persia> There's specialist developers in a given interest area (e.g. Xubuntu, Games, etc.)
[15:37] <Keybuk> Specialist UBUNTU Developers ;)
[15:37] <persia> And there's people who want to work on *one* package.
[15:38] <persia> Yes, s//Ubuntu/ in all lines above.
[15:38] <Keybuk> I see the one package as a very narrow interest area
[15:38] <dholbach> that sounds good, the only trouble is: if the "packaging skills demonstrated" merely consist of "just" packaging a new upstream release or "just" adding an upstream patch, the requirements ARE different :)
[15:38] <cody-somerville> Keybuk, SUPER Specialist UBUNTU Developer?
[15:38] <cody-somerville> ;]
[15:38] <dholbach> please don't get caught up into nomenclature again :-)
[15:38] <Keybuk> dholbach: does MOTU not already have this problem?
[15:38] <persia> Keybuk, Is it worth creating the infrastructure of a layer for one person for one package?
[15:38] <Keybuk> what if a prospective applicant has had a very large number of sponsored uploads, all of which have been just packaging a new upstream release or just adding a new upstream patch?
[15:39] <cjwatson> I don't think you should infer technical infrastructure (layers) from social structure (interest areas)
[15:39] <dholbach> Keybuk: it's a lot easier to judge when somebody demonstrated their abilities on a variety of packages and did "packaging changes that were necessary"
[15:39] <cjwatson> (and no, it isn't worth it)
[15:39] <Keybuk> dholbach: I think it's easier to judge someone's skills as a generalist
[15:39] <Keybuk> but not much more
[15:39] <persia> cjwatson, Well, fair, but I'm thinking in terms of implementation.  I'd rather that those with a narrow interest (in an entire layer) have a slightly different process than those with interest only in a specific package.
[15:39] <dholbach> Keybuk: I still think we should make that clear in the expectations we set
[15:40] <Keybuk> questions I might ask a prospective per-package uploader:
[15:40] <Keybuk> 1. there's a new upstream version available; what's changed? why is it not packaged?
[15:40] <cjwatson> persia: I don't see a reason to create a separate layer for individual packages, and it would result in more work for archive admins for little gain
[15:40] <Keybuk> 2. you're not a bug contact for this package, why not?  (and -200 points)
[15:40] <Keybuk> 3. there's several bugs that haven't yet been triaged in Launchpad, have you looked at these?
[15:40] <Keybuk> 4. what are your thoughts on the open High priority bug #nnnn ?
[15:41] <cjwatson> persia: as Mark said on the phone a week or two ago, packages and package sets (a.k.a. layers) should be like people and teams - you can use either in place of the other
[15:41] <cjwatson> at least as far as the access controls go
[15:41] <Keybuk> 5. package foo is quite similar, and uploads have been made by Ubuntu developer X - have you talked to them?
[15:41] <cjwatson> (now, obviously that's a bit down the line in terms of actual LP implementation, but)
[15:41] <persia> cjwatson, Agreed.  Similarly, I think we want slightly different requirements for per-package uploaders and uploaders to a layer.
[15:41] <cjwatson> persia: absolutely
[15:41] <dholbach> Keybuk: I'm very happy with the questions you ask and I'll make sure I'll massage that into the proposal.
[15:42] <Keybuk> where a layer is aligned with a team, I'm actually less nervous because that developer is clearly joining an existing team
[15:42] <persia> And presumably, is welcomed by the existing members of the team, who can provide support, mentoring, guidance, etc.
[15:42] <Keybuk> it's the lone developer that worries me
[15:43] <Keybuk> assumedly on a crusade to champion the cause of the innocent, the helpless, the powerless, in a world of...no, wait
[15:43] <persia> That's different :)
[15:43] <cjwatson> let's put it as "likely to require additional assistance", shall we? :)
[15:43] <dholbach> Keybuk, cjwatson: before we move the topic to Archive Reorg, is there anything else you would like to see covered in a new proposal that was not raised yet? :)
[15:43] <persia> cjwatson, Well, maybe.  Again, the handy example is Matthew East.
[15:44] <dholbach> I'll be moving the existing proposal back to the drawing-board. :-)
[15:44] <dholbach> Thanks a bunch for your input
[15:44] <cjwatson> persia: well, he's a likely-to-pass candidate, not a dubious candidate, surely
[15:45] <Keybuk> of the existing three candidates for specific upload rights, two seem to me to demonstrate that they consider themselves Ubuntu developers with a specialist interest in a package
[15:45] <Keybuk> the other seems to be to be a developer who just wants to upload his package, and has not demonstrated a contribution to Ubuntu thus far
[15:45] <Keybuk> (avoiding names since it's unfair if they're not here)
[15:46] <Keybuk> I think that the policy, as worded, does not encapsulate that difference - and in some ways seems to deliberately try and get rid of it
[15:46] <persia> If we add the requirement of Ubuntu Membership, as previously discussed, it makes the line much easier to draw.
[15:47] <persia> The current proposal specifically doesn't require this, but that's simple to change, and provides protection in the sense that we select from those who already identify with Ubuntu.
[15:48] <Keybuk> I think I would agree with that
[15:49] <Keybuk> persia: will you take the action to redraft the proposal and resubmit it to the TB?
[15:49] <persia> Keybuk, Sure.  Am I just changing the Membership, or is there more? (I'll review the meeting log for details if the latter)
[15:50] <cjwatson> I think it's a bit more than that; review the log
[15:50] <persia> OK.  I saw a few things, and wanted to check :)
[15:51] <cjwatson> I can give a brief update on the state of play with archive reorg
[15:51] <Keybuk> let's hold the issue of the candidates in abeyance until we agree on the policy
[15:51] <Keybuk> cjwatson: please do
[15:51] <Keybuk> we have ~9 minutes
[15:51] <cjwatson> I've introduced the notion of restricted layers into the spec
[15:52] <cjwatson> I've added sections on how the ogre model will work, and on some anticipated community factors
[15:52] <cjwatson> I've changed the proposed permissioning around to encapsulate what I believe to be current consensus
[15:52] <cjwatson> the permissioning has one rather curious feature
[15:53] <cjwatson> it has a "core" layer, which remains necessary for the ogre model and for partial mirrors
[15:53] <cjwatson> but the permissions on the "core" layer are simply "Ubuntu [generalist] developers", the same as for all packages in no layers
[15:53] <cjwatson> I think this is actually OK, and explain why I think that in the spec, but it does look a bit curious :)
[15:54] <Keybuk> oh?
[15:54] <cjwatson> I've explicitly introduced the term "general developers" (should probably change that to generalist)
[15:54] <cjwatson> "(It looks a little odd to have this require the same level of access as the "core" layer, but the different layers are required in order to preserve things like ogre model and the ability to produce working partial mirrors, and in practice this models the "broad and shallow" type of developer quite well.)"
[15:55] <Keybuk> sounds fair
[15:55] <Keybuk> I'll re-read the spec ;)
[15:55] <cjwatson> my next steps are: to prepare a rough set of requirements for the Soyuz team (including a transition plan of sorts); and to start work on an example layerised archive
[15:56] <cjwatson> I want to have something on people.ubuntu.com that you can point experimental versions of apt and friends at in order to see what the new world order would look like
[15:56] <persia> One note is that members of MOTU belong to the ~motu team, rather than ~ubuntu-dev.  ~ubuntu-dev contains both ~ubuntu-core-dev and ~motu.
[15:56] <cjwatson> this will both afford us the opportunity to test the tool changes, and let us work on the layer migration itself
[15:56] <cjwatson> persia: noted, will adjust
[15:57] <cjwatson> though of course ubuntu-dev is appropriate at some places in that spec where we're really talking about the union (e.g. "ability to upload to current universe" -> ubuntu-dev)
[15:58] <cjwatson> having an example layerised archive will let people play about and answer quite a few questions, I think
[15:58] <cjwatson> that will have to come with some basic tools to sync up with the current archive overrides
[15:58] <persia> Also, as a suggestion for the conflict between "Ubuntu Developer" being the term for merged core-dev and MOTU vs. "Ubuntu Developer" being the term for all Ubuntu Developers in the new model, it may be best to merge the current teams separately, and then add any new developer teams to ~ubuntu-dev
[15:59] <cjwatson> I suspect that the resolution there is to call the merged one "Ubuntu Generalist Developer" or something
[15:59] <cjwatson> but I've been holding off on that because, frankly, it sounds clunky :-/
[15:59] <persia> That seems sensible.
[15:59] <cjwatson> I don't have a better suggestion at the moment
[15:59] <cjwatson> anyway, that's all from me for the moment - there'll be a call with the Soyuz team next week
[15:59] <Keybuk> ok, we're about to run into the server team meeting ...
[15:59] <Keybuk> do we have any other business?
[16:00] <cjwatson> (once Mark is back from gallivanting)
[16:00] <cjwatson> nothing from me
[16:01] <Keybuk> ok, adjourned then
[16:01] <Keybuk> thanks all
[16:01] <nijaba> o/
[16:01] <nealmcb> \o
[16:01] <Koon> \o/
[16:01]  * mathiaz waves
[16:02] <mathiaz> Let's get the Ubuntu Server Team started
[16:02] <mathiaz> #startmeeting
[16:02] <MootBot> Meeting started at 10:02. The chair is mathiaz.
[16:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:02] <mathiaz> Today's agenda: https://wiki.ubuntu.com/ServerTeam/Meeting
[16:02] <zul> hi ho neighborarinos
[16:02] <soren> o/
[16:02] <sommer> hey all
[16:02] <mathiaz> what a busy agenda! let's get moving
[16:03] <mathiaz> Last week minutes: https://wiki.ubuntu.com/MeetingLogs/Server/20090120
[16:03] <mathiaz> [TOPIC] SRU for ebox
[16:03] <MootBot> New Topic:  SRU for ebox
[16:03] <mathiaz> so I've uploaded ebox 0.12 to the new jaunty archive
[16:03] <mathiaz> sommer: that means the SRU process for intrepid can move on.
[16:04] <sommer> mathiaz: great, thanks
[16:04] <mathiaz> sommer: do you have the three bug numbers?
[16:04] <sommer> one sec
[16:05] <mathiaz> sommer: https://bugs.launchpad.net/ubuntu/+source/ebox/+bug/273486
[16:06] <mathiaz> sommer: ok - I don't find the others
[16:06] <sommer> bug 255368
[16:07] <sommer> and the dbug gconf one
[16:07] <mathiaz> sommer: is there a bug number for the latter?
[16:08] <sommer> mathiaz: bug 314606
[16:08] <sommer> that's them :)
[16:08] <mathiaz> sommer: ok - I've just mark bug 273484 fix released
[16:08] <mathiaz> sommer: https://bugs.launchpad.net/ubuntu/+source/ebox/+bug/273486
[16:09] <mathiaz> sommer: all the three bugs are fixed in jaunty and the intrepid SRU can move along.
[16:09] <sommer> mathiaz: I'll get with foolano and whip up some new debdiffs
[16:10] <mathiaz> sommer: the next step is to get the debdiff for the sru prepared, ACKed by the sru team and then sponsored to intrepid-proposed
[16:10] <mathiaz> [ACTION] sommer to prepare new debdiff for the ebox intrepid SRU
[16:10] <MootBot> ACTION received:  sommer to prepare new debdiff for the ebox intrepid SRU
[16:10] <mathiaz> [TOPIC] ACL by default
[16:10] <MootBot> New Topic:  ACL by default
[16:11] <mathiaz> ivoks: ^^ did you create a wiki page?
[16:11] <ivoks> mathiaz: nope :/
[16:11] <ivoks> mathiaz: probably tomorrow
[16:11] <mathiaz> ivoks: anything else to report on this topic?
[16:11] <ivoks> no
[16:11] <mathiaz> [ACTION] ivoks to create wiki page to keep track of ACL support in packages
[16:11] <MootBot> ACTION received:  ivoks to create wiki page to keep track of ACL support in packages
[16:11] <mathiaz> [TOPIC] DRBD in jaunty
[16:11] <MootBot> New Topic:  DRBD in jaunty
[16:11] <ivoks> drbd is uploaded
[16:11] <mathiaz> ivoks: ^^ ? is dbd working in jaunty?
[16:11] <ivoks> yes
[16:11] <mathiaz> *drbd*
[16:12] <mathiaz> ivoks: what kind of test did you conduct?
[16:12] <ivoks> mathiaz: two vritualized machines
[16:12] <ivoks> i'll do upgrade tests too during this week
[16:12] <mathiaz> ivoks: could you write down some test instructions?
[16:12] <ivoks> sure
[16:13] <mathiaz> ivoks: so that they can be put in a wiki page and other can also help out in testing
[16:13] <ivoks> of course... but in two-three days
[16:14] <mathiaz> ivoks: I'd suggest to create a subpage under https://wiki.ubuntu.com/Testing/Cases/
[16:14] <ivoks> ok
[16:14] <mathiaz> [ACTION] ivoks to write a wiki page for conducting DRBD testing under https://wiki.ubuntu.com/Testing/Cases/
[16:14] <MootBot> ACTION received:  ivoks to write a wiki page for conducting DRBD testing under https://wiki.ubuntu.com/Testing/Cases/
[16:15] <mathiaz> [TOPIC] Screen profiles
[16:15] <MootBot> New Topic:  Screen profiles
[16:15] <mathiaz> kirkland: what's the state of screen and screen-profiles now?
[16:15] <kirkland> mathiaz: screen-profiles is in main
[16:15] <kirkland> mathiaz: screen recommends screen-profiles
[16:16] <nijaba> and it kicks asses
[16:16] <kirkland> nijaba: yes, multiple asses :-)
[16:16] <sommer> heeeh
[16:16] <kirkland> mathiaz: so here's my question for the Ubuntu Server team .....
[16:16]  * mathiaz plays the drums
[16:16] <kirkland> mathiaz: what could/should we do with the default /etc/screenrc ?
[16:16] <cjwatson> conffiles and alternatives are unlikely to be friends; I recommend not using alternatives (as suggested in the agenda)
[16:16] <ivoks> i'm for vanilla /etc/screenrc
[16:17] <kirkland> cjwatson: okay, so not update-alternatives .....
[16:17] <ivoks> just because most of the people expect that
[16:17] <mathiaz> kirkland: how many different screen profiles are there now?
[16:18] <nijaba> ivoks: a lot of people expect linux desktop to be command line only, if we go that direction...
[16:18] <kirkland> ivoks: i agree that that's been the traditional screen profile, but i think we've created something cool, and very Ubuntu-unique ... could be a nice advantage of using the Ubuntu Server
[16:18] <kirkland> mathiaz: for Ubuntu, 3 basically....  the plain vanilla one, ubuntu-light, and ubuntu-dark
[16:18] <ivoks> nijaba: that's correct, but i was thinking more about people who do know how to use cli and screen
[16:18] <kirkland> mathiaz: we also have profiles for debian, etc, but those are not installed on ubuntu
[16:19] <kirkland> ivoks: they won't be using screen then
[16:19] <nijaba> ivoks: run a test, and ask how many admin DO know about screen, you'll be surprised
[16:19] <kirkland> cjwatson: do you have any other suggestion, if not alternatives?
[16:19] <cjwatson> I haven't looked into it at all; I was just raising a warning flag rather than purporting to have an alternative :)
[16:20] <kirkland> cjwatson: thanks
[16:20] <mathiaz> kirkland: what are you trying to accomplish actually?
[16:20] <cjwatson> although I would say, why is this a root-only thing?
[16:20] <mathiaz> kirkland: IIUC you're asking what we should put in /etc/screenrc
[16:20] <kirkland> cjwatson: its not at all a root-only thing
[16:20] <cjwatson> alternatives and other solutions that involve moving things around in /etc are root-only
[16:20] <mathiaz> kirkland: and we have 3 choices
[16:20] <kirkland> cjwatson: any user can have this profile, if they run 'select-screen-profile'
[16:20] <cjwatson> if you aren't focusing on root-only, you should be thinking about options that users can easily set
[16:20] <nijaba> kirkland: what about it being installed by default with ubuntu-standard?  it is quite easy to put back to default
[16:20] <cjwatson> ah, well, who cares about what's in /etc then
[16:21] <ivoks> here's an idea...
[16:21] <ivoks> default screen prompts text, that nobody reads
[16:21] <kirkland> cjwatson: b/c that's what you get if you don't (know to) run 'select-screen-profile'
[16:21] <ivoks> is it possible to put a list of profiles there?
[16:22] <ivoks> that would be selectable? :)
[16:22] <ivoks> just an idea...
[16:22] <nijaba> ivoks: in "select-screen-profiles" ?  that's alreay the case
[16:22] <kirkland> ivoks: ah that's an idea, perhaps .... on that screen we could say "run 'select-screen-profile' if you'd like some advanced features, etc."
[16:22] <nijaba> and once screen is launched, you can change it using the screen profile helper
[16:22] <ivoks> kirkland: no... you would run select-screen-profile
[16:22] <mathiaz> kirkland: how does the sensible-editor selection work?
[16:22] <ivoks> kirkland: and, on first run, let people choose
[16:23] <kirkland> ivoks: i like that, choose on first run
[16:23] <ivoks> kirkland: people that want plain screen, wouldn't notice anything
[16:23] <ivoks> kirkland: they would just hit enter
[16:23] <kirkland> mathiaz: that's sort of how select-editor works
[16:23] <ivoks> kirkland: people who run it for the first time, they would be 'wow, look at that...'
[16:23] <kirkland> mathiaz: ivoks: cool, i think that's a plan
[16:23] <Koon> melikes ivoks plan
[16:24] <mathiaz> kirkland: seems like we could try a similar workflow for screen profiles selection
[16:24] <cjwatson> sounds appropriate
[16:24] <mathiaz> kirkland: do you have an idea on how to do that?
[16:24] <ivoks> right, just as select-editor
[16:24] <kirkland> mathiaz: cheers.  thank you brilliant community
[16:24] <Koon> especially as usual screen users are trained to ignore that screen anyway
[16:24] <mathiaz> kirkland: are you planning to work on that?
[16:25] <kirkland> mathiaz: i think /usr/bin/screen becomes a wrapper script to see if you've selected a profile;  if so, just launch screen.  if not, run select-screen-profile, then launch screen
[16:25] <kirkland> mathiaz: i'll have it done by the end of today ;-)
[16:25] <nijaba> \o/
[16:25] <ivoks> nice
[16:25] <mathiaz> [ACTION] kirkland to implement screen-profiles selection tool
[16:25] <nealmcb> kirkland: the "home page" for this is listed as https://launchpad.net/screen-profiles on launchpad - is that right?  I want to know where to point people from https://help.ubuntu.com/community/ServerGUI
[16:25] <MootBot> ACTION received:  kirkland to implement screen-profiles selection tool
[16:25] <ivoks> good job kirkland
[16:26] <kirkland> nealmcb: correct
[16:26] <nealmcb> will do :)
[16:26] <mathiaz> let's move on
[16:26] <mathiaz> [TOPIC] EtcUnderRevisionControl status
[16:26] <MootBot> New Topic:  EtcUnderRevisionControl status
[16:26] <mathiaz> Koon: ^^ what's going on there?
[16:26] <Koon> Just a quick update on that project, which you may have heard (with the epic delay) at UDS
[16:27] <ivoks> i'm sorry, but i have to leave... bbl
[16:27] <Koon> The design is finalized, it's heavily relying on etckeeper
[16:27] <Koon> everything should be implemented directly into etckeeper
[16:28] <Koon> The idea is to improve etckeeper and its bzr plugin to be a little more user-friendly
[16:28] <mathiaz> Koon: is there anything to test?
[16:28] <Koon> mathiaz: not yet. I created a project and a team on launchpad
[16:29] <Koon> interested people are welcomed to join, I already have Jelmer Vernooij (author of current bzr etckeeper featured) in
[16:29] <mathiaz> Koon: is the spec up-to-date wrt to the implementation plan?
[16:29] <Koon> the spec is up to date, ready to be accepted
[16:29] <mathiaz> Koon: what are the names of the team and project in LP?
[16:29] <jdstrand> Koon: what's the project name in LP?
[16:29] <Koon> project: etckeeper
[16:30] <Koon> team: etckeeper
[16:30] <jdstrand> gee, I could have guessed that...
[16:30] <Koon> it's manually synced with the GIT tree
[16:30] <Koon> at upstream
[16:30] <Koon> and we have Ubuntu branches in there
[16:30] <mathiaz> Koon: so you're waiting for the Spec to approved?
[16:30] <Koon> mathiaz: yes.
[16:31] <Koon> Joey Hess (upstream) has been quite open to intergating more advanced features
[16:31] <Koon> so they should find their way back into core
[16:31] <mathiaz> Koon: great. You should ping dendrobates about aproving the spec
[16:32] <Koon> he is pinged already
[16:32] <jdstrand> Koon: I haven't followed the spec closely since UDS. will this require changes to bzr as well?
[16:32] <Koon> jdstrand: it /could/ use a few more hooks
[16:32] <dendrobates> Koon: he already did.
[16:32] <dendrobates> er mathiaz
[16:33] <Koon> jdstrand: especially to catch all permissions-upsdating corner cases
[16:33] <jdstrand> Koon: not that it should be a factor in your devel work, but I was curious how easy it would be to backport to hardy
[16:34] <jdstrand> Koon: IIRC, the hooks cannot be done via bzr plugins-- is that accurate?
[16:34] <mathiaz> dendrobates: are you planning to review the blueprint soon?
[16:34] <dendrobates> mathiaz: yes.
[16:34] <Koon> jdstrand: hooks usually are in bzr core, and plugins use them
[16:34]  * jdstrand nods
[16:35] <Koon> but you could theorically add a hook by plugin, it just doesn't make much sense in the common scenario
[16:35] <mathiaz> [ACTION] dendrobates to review the etc-under-revision-control blueprint
[16:35] <MootBot> ACTION received:  dendrobates to review the etc-under-revision-control blueprint
[16:35] <mathiaz> ok - let's move on.
[16:35] <mathiaz> [TOPIC] Server Team Bug Days
[16:35] <MootBot> New Topic:  Server Team Bug Days
[16:35] <mathiaz> zul: what's your idea?
[16:36] <zul> yeah so I was thinking that other teams have similar things where they hang out on the bugs channel and get people to help fixing bugs, i believe its a good way to get people involved
[16:37] <mathiaz> right. We had one bug day organized by the bug team
[16:37] <mathiaz> that was about 1 3/4 years ago
[16:37] <zul> well we should have another one organized soonish
[16:37] <mathiaz> so I'd suggest to ask the Bug team about it
[16:38] <mathiaz> they'd be more than happy to help out and we'd reach much more people
[16:38] <mathiaz> than just organizing a Server Bug day in the server team.
[16:38] <mathiaz> bdmurray: what should we do to get a Server Team Bug day organized?
[16:38] <zul> well thats what I was thinking as well we need someone to approach them
[16:40] <dendrobates> mathiaz zul: I am arranging a discussion between all of us at the sprint.
[16:40] <zul> thats it from me :)
[16:40] <zul> dendrobates: nifty
[16:40] <mathiaz> dendrobates: ok. We'll talk about this topic next week then.
[16:40] <mathiaz> let's move on
[16:41] <mathiaz> [TOPIC] ncrypted private/home with filename encryption available
[16:41] <MootBot> New Topic:  ncrypted private/home with filename encryption available
[16:41] <kirkland> \o/
[16:41] <mathiaz> kirkland: what did you do?
[16:41] <kirkland> i uploaded a new ecryptfs-utils-69 package that enables filename encryption, if your kernel supports it
[16:41] <kirkland> rtg on the kernel team backported ecryptfs filename encryption from 2.6.29 to 2.6.28
[16:42] <kirkland> and i completed the userspace bits this weekend to make this work with encrypted home and encrypted private
[16:42] <mathiaz> kirkland: awesome.
[16:42] <kirkland> so, if you were to use ecryptfs-setup-private on an up-to-date jaunty system, you would see that your filenames are now encrypted as well, in your underlying .Private dir
[16:42] <kirkland> and transparently decrypted for your in Private
[16:42] <kirkland> same goes for encrypted home
[16:43] <mathiaz> kirkland: so upgrade are automatically handled?
[16:43] <kirkland> mathiaz: dammit with the hard questions!
[16:43] <kirkland> mathiaz: :-)
[16:43] <kirkland> i still have some work to do on "live migration"
[16:43] <kirkland> with some help from jdstrand, we came up with a theoretical design to solve this
[16:43] <mathiaz> kirkland: ok - so you get filename encryption on new installs only.
[16:44] <mathiaz> kirkland: for now
[16:44] <kirkland> i'm flying to Germany tomorrow;  i hope to hack that live migration script then
[16:44] <kirkland> mathiaz: right
[16:44] <kirkland> mathiaz: if you wanted to take advantage of this, you should backup your cleartext data elsewhere
[16:44] <mathiaz> kirkland: ok - do you have specific instructions for testing this?
[16:44] <kirkland> mathiaz: then do a new ecryptfs-setup-private (fresh, empty dir)
[16:44] <kirkland> mathiaz: and then rsync your data back in
[16:45] <kirkland> mathiaz: i will blog about it this week
[16:45] <cjwatson> note that the desktop CD's still busted, this is server/alternate install CD only still
[16:45] <mathiaz> kirkland: great.
[16:45] <kirkland> cjwatson <- is right
[16:45] <kirkland> but i think we  (evand, cjwatson) mostly know whats wrong there
[16:46] <mathiaz> [ACTION] kirkland to make a call for testing filename encryption
[16:46] <MootBot> ACTION received:  kirkland to make a call for testing filename encryption
[16:46] <kirkland> cjwatson: i have set ecryptfs-setup-private to automatically use filename encryption, if possible
[16:46] <kirkland> cjwatson: so no further changes in that respect should be required from you dudes
[16:47] <mathiaz> excellent news kirkland !
[16:47] <mathiaz> kirkland: is there anything else to add on this topic?
[16:48] <mathiaz> kirkland: once the installer has support for this is there anything else left to be done for jaunty?
[16:48] <kirkland> mathiaz: encrypted swap
[16:49] <kirkland> mathiaz: i *strongly* believe that any user using encrypted home or encrypted private should really be using encrypted swap
[16:49] <mathiaz> kirkland: ok - that's a different (but related) topic
[16:49] <mathiaz> kirkland: for encrypted directories I meant
[16:49] <kirkland> mathiaz: in such cases, all of the encrypted data lives as cleartext in memory
[16:49] <kirkland> mathiaz: should that memory get swapped to disk, it's swapped to disk in the clear, unless swap too is encrypted
[16:49] <mathiaz> kirkland: is this something targeted for jaunty?
[16:50] <kirkland> mathiaz: in the very worst case, i plan on adding a script to ecryptfs-utils that would attempt to setup your system for encrypted swap
[16:50] <kirkland> mathiaz: to be run at the user's discretion after installation
[16:50] <kirkland> i'm guessing that this item probably won't make the installer at this point
[16:50] <mathiaz> kirkland: ok. seems like a good first step.
[16:50] <kirkland> i hope to talk to the foundations team about this next week
[16:51] <mathiaz> kirkland: FYI FeatureFreeze is in 3 weeks
[16:51] <kirkland> mathiaz: and the live migration scripts
[16:51] <kirkland> mathiaz: right
[16:51]  * kirkland is looking forward to FF :-)
[16:51]  * kirkland <--- late nights
[16:51] <mathiaz> ok - let's move on.
[16:52] <mathiaz> [TOPIC] Open Discussion
[16:52] <MootBot> New Topic:  Open Discussion
[16:52] <nealmcb> I updated https://help.ubuntu.com/community/ServerGUI to note the latest info on screen and screen-profiles.  feel free to jump in
[16:52] <sommer> I have a quick question about the installer.  are we going to be using lvm by default, there was some talk about it at UDS?
[16:52] <soren> sommer: Noone's been working on it, AFAIK.
[16:53] <nealmcb> !screen
[16:53] <nealmcb> I'll update that factoid also - input welcome
[16:53] <sommer> soren: okay, I just was wondering for documentation reasons
[16:53] <mathiaz> nealmcb: great - thanks.
[16:53] <mathiaz> [ACTION] nealmcb to update the screen factoids
[16:53] <MootBot> ACTION received:  nealmcb to update the screen factoids
[16:55] <mathiaz> anything else?
[16:55] <jdstrand> I might mention that ufw now has debconf/preseeding support
[16:55] <cjwatson> kirkland: I think you'll be lucky to get encrypted swap by default
[16:56] <kirkland> cjwatson: not "by default"  ... i've abandoned that
[16:56] <cjwatson> sommer: I saw that there had been a requirement mentioned for it, but nobody wrote up the UDS session *at all*
[16:56] <kirkland> cjwatson: but "when encrypted home is selected", would be ideal
[16:56] <cjwatson> i.e. there's a server-installer-partitioning spec that doesn't even have a wiki link set
[16:56] <cjwatson> kirkland: I doubt that's feasible for jaunty. Sorry
[16:56] <kirkland> cjwatson: right
[16:56] <sommer> cjwatson: ah, well maybe for jaunty+1
[16:56] <cjwatson> does anyone care enough to watch the UDS videos corresponding to server-installer-partitioning and write it up so that I have some clue what the design is supposed to be?
[16:57] <cjwatson> I understood that it had got demoted in priority, which is why I haven't been making too much noise about it
[16:57] <kirkland> cjwatson: let's discuss contingency plans next week.  i'm thinking now about an ecryptfs-utils provided script that would do the magic for you, in some constrained cases.  and then document/warn that it needs to be run, for more security
[16:58] <cjwatson> kirkland: it's already on the foundations agenda for next week
[16:59] <nealmcb> I think the encrypted swap session was at noon on the 11th: http://videos.ubuntu.com/uds/jaunty/Server/2008-12-11/morning-post-break/
[16:59] <sommer> cjwatson: from my UDS notes and memory, it was only mentioned during the server raid discussion, as sort of a sidebar
[16:59] <kirkland> cjwatson: awesome, i'll be there with bells on :-)
[16:59] <sommer> cjwatson: err the lvm discussion
[16:59] <mathiaz> ok - let's move on
[16:59] <mathiaz> [TOPIC] Agree on next meeting date and time
[16:59] <MootBot> New Topic:  Agree on next meeting date and time
[17:00] <mathiaz> same place, same time, next week?
[17:00] <kirkland> k
[17:00] <sommer> works for me :)
[17:00] <cjwatson> sommer: ok, that doesn't make it very easy to have a clue on what to implement, given that there are known problems with the post-installation tools
[17:00] <dendrobates> cjwatson: I think it was not actually help to allow for even more cloud discussions/
[17:00] <dendrobates> cjwatson: I'll review what I have, though.
[17:01] <mathiaz> ok - see you all next week
[17:01] <mathiaz> same time same place here.
[17:01] <mathiaz> #endmeeting
[17:01] <MootBot> Meeting finished at 11:01.
[17:01] <pgraner> Hello Everyone.... Time for the Kernel Team Weekly Meeting... yay!
[17:01] <Koon> \o/
[17:01]  * apw is here
[17:01]  * cking too
[17:01] <pgraner> #startmeeting
[17:01] <MootBot> Meeting started at 11:01. The chair is pgraner.
[17:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[17:02]  * smb_tp as well
[17:02] <nealmcb> Hey - what about next week?  Maybe at the same time?
[17:02]  * nealmcb oops
[17:02]  * rtg is messing with encrypted file names.
[17:02] <pgraner> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:02] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[17:02] <pgraner> That is the agenda
[17:03] <pgraner> [TOPIC] Security & bugfix kernels
[17:03] <MootBot> New Topic:  Security & bugfix kernels
[17:03] <smb_tp> Ok
[17:03] <pgraner> smb_tp: whats new in your world?
[17:03] <smb_tp> Security is waiting just for the upload for dapper to intrepid
[17:04] <smb_tp> intrepid is a special upload as it is identical to the last proposed and hopefully very soon -updates kernel
[17:04] <smb_tp> (just a little test away)
[17:04] <pgraner> why so "special"?
[17:04] <smb_tp> It diff only on the changelog
[17:04] <rtg> I didn't understand why pitti required a special upload
[17:05] <smb_tp> rtg, not pitty kees
[17:05] <BenC> So the -security kernel is just the same as the -proposed kernel?
[17:05] <smb_tp> He wanted to have the CVE visible
[17:05] <rtg> I think we need to talk about this stuff next week
[17:05] <smb_tp> BenC, correct
[17:05] <smb_tp> rtg, Agreed :)
[17:05] <BenC> smb_tp: so did the cve get uploaded to -proposed before it was sent to -security?
[17:05] <smb_tp> But with the current queue of intrepid I did not want to argue
[17:06] <smb_tp> BenC, The CVE's (on the current list) just were included in previous uploads already
[17:06] <BenC> smb_tp: Ah, makes more sense then
[17:06] <pgraner> [ACTION] smb_tp to hold sidebar as sprint on this latest upload case
[17:06] <MootBot> ACTION received:  smb_tp to hold sidebar as sprint on this latest upload case
[17:06] <pgraner> s/as/at/
[17:07] <smb_tp> Ok
[17:07] <smb_tp> So, currently backing a bigger intrepid next-proposed
[17:07] <pgraner> smb_tp: how are the upstream stable updates looking. I see there are a ton of them
[17:07] <smb_tp> We got two -stable updates there
[17:07] <pgraner> :-)
[17:08] <smb_tp> Yeah, a few look important and scary, so I like to have them tested well
[17:08] <smb_tp> Scary in the sense that the muck around in mm
[17:08] <cking> that's unpleasant
[17:08] <pgraner> yea I saw that
[17:08] <rtg> they're pretty straightforward
[17:08] <smb_tp> And four of those patches are changing the AI
[17:09] <smb_tp> err ABI
[17:09] <pgraner> smb_tp: any other things we should know about?
[17:10] <smb_tp> Lemme thin
[17:10] <smb_tp> Hardy will have to be reloaded after security
[17:10] <smb_tp> The request is to include there some vmware patches as well
[17:11] <smb_tp> Since they are bumping ABI I am abit reluctant there
[17:11]  * pgraner nods
[17:11] <smb_tp> Probably queueing them until there is another reason
[17:11]  * rtg is in favour of ABI bumps between major updates
[17:12] <smb_tp> We might do. The point release is done by now
[17:12] <pgraner> smb_tp: anything else?
[17:13] <rtg> which is why I'd like to see an ABI bump
[17:13] <smb_tp> cking, Is doing some test with them. So if he finds them useful it might be more reason
[17:13] <smb_tp> No, thats all I can think of
[17:13] <cking> smb_tp, they did not address the issue
[17:13] <rtg> frankly, the vmware patches alone are enough reason.
[17:13] <smb_tp> rtg, We beer it out next week
[17:13] <pgraner> Great... moving on to everyones favorite topic....
[17:13] <pgraner> [TOPIC] Jaunty Status
[17:14] <MootBot> New Topic:  Jaunty Status
[17:14] <pgraner> We have alpha 4 next thurs...
[17:14] <pgraner> and a few actions according to the calendar
[17:15] <pgraner> * Finalize the compiled in modules and online docs
[17:15] <pgraner> * Finalize the removal of lrm and creation of DKMS pkgs
[17:15] <rtg> I think the list of built in modules is stable
[17:16] <rtg> wrt LRM: probably ain't gonna happen for Jaunty
[17:16] <pgraner> * Document what we turned on from the /staging directory publicly
[17:16] <pgraner> * Reduce grub timeout
[17:16] <rtg> staging: rt2860/2870
[17:16] <BenC> grub timeout done
[17:16] <cking> reduce grub timeout even further?
[17:17] <cking> ah
[17:17] <pgraner> cking: no that was the overall task needed to be complete
[17:17] <pgraner> cking: I know it was hurting you the other day...
[17:17] <rtg> I uploaded <IP_ADDRESS> -stable Sunday, it just got NEWed an hour ago.
[17:18] <rtg> apw has submitted patches for vanilla kernel build, still reviewing
[17:18] <pgraner> rtg: wrt to LRM then we need to move it off to Jaunty+1, what was the reason?
[17:19] <rtg> because of wl mostly. it is still required by default in some cases.
[17:19] <pgraner> rtg: ok
[17:20] <pgraner> rtg: on staging... those are the only drivers we enabled out of all the crap?
[17:20] <rtg> so far.
[17:20] <BenC> rtg: wlan-ng/prism wasn't enabled?
[17:20] <BenC> I thought we switched out everything that was duped in ubuntu/
[17:20] <rtg> I've not had any requests
[17:20] <rtg> I also need to check for dupes.
[17:21] <pgraner> [ACTION] rtg to check for /staging /ubuntu dupes...
[17:21] <MootBot> ACTION received:  rtg to check for /staging /ubuntu dupes...
[17:21] <BenC> debian/config/i386/config:CONFIG_PRISM2_USB=m
[17:21] <BenC> rtg: wlan-ng is enabled
[17:21] <BenC> in staging
[17:21] <rtg> BenC: but thats still under the ubuntu directory
[17:22] <BenC> rtg: ew...then we have ambiguous config options enabled
[17:23] <rtg> it only looks taht way, but in truth it won't compile unless you DTRT
[17:23] <apw> we'll get both i assume
[17:23] <BenC> rtg: the one in staging is getting build...not the one in ubuntu
[17:23] <BenC>  /lib/modules/2.6.28-5-generic/kernel/drivers/staging/wlan-ng/prism2_usb.ko
[17:23] <rtg> hmm, thats unexpected,.
[17:23] <apw> would we not get both
[17:23] <apw> BenC, do you have the ubuntu one?
[17:24] <rtg> even if we get both, the driver in staging is the one that gets loaded first. but, we need to weed out the dups
[17:24] <BenC> apw: nope, just the staging one is in -5
[17:25] <pgraner> apw: how are we looking for this round of suspend/resume?
[17:25] <apw> the final bit for apport has been merged and uploaded
[17:25] <apw> we have gotten a couple of reports back, so it is working (the automation)
[17:26] <pgraner> apw: were they usefull?
[17:26] <apw> one was a battery run flat the others seem real
[17:26] <pgraner> s/usefull/useful/
[17:26] <apw> the only confusion is the users always seem confused and put
[17:26] <apw> "i don't know why this poped up, so i have no idea what occured"
[17:26] <apw> where they might have told us something useful
[17:27] <ogasawara> apw: yah, I've seen a few like that
[17:27] <apw> that may be because its is saying crash in the output
[17:27] <sconklin> that's good information - pitti and I discussed adding a new class of apport report for these, which would let us customize the presentation to the user
[17:28] <apw> i also don'tknow why it asks for the description
[17:28] <apw> as they really have no information at that point to put in the one liner
[17:28] <apw> and appport knows its a suspend error
[17:28] <sconklin> apport thinks it's a kerneloops
[17:28] <sconklin> That was the most reasonable error type to report it under
[17:28] <pgraner> sconklin: apport need some schooling
[17:29] <apw> yeah but even for a kernel opps, popping up a box saying "summary of your bug"
[17:29] <sconklin> Yes, I'll talk with pitti about it again
[17:29] <apw> when the user has no clue whats in the report, isn't helpful
[17:29] <pgraner> ogasawara: When is the next/updated call for testing going out?
[17:30] <pgraner> apw: do we need any docs changes on the wiki for the changes that were made since A3?
[17:30] <ogasawara> pgraner: I can send it whenever we're ready, but I'd just assumed around Alpha4
[17:30] <apw> pgraner, not sure there is anything specific to that, but more review is needed overall
[17:31] <lieb> sconklin, add me to the conversation w/ Martin
[17:31] <pgraner> ogasawara: fine by me :-)
[17:31] <sconklin> lieb: ok
[17:31] <pgraner> lieb: how crashdump/kernel oops going?
[17:31] <lieb> have a patchset for new kerneloops
[17:31] <lieb> crashdump next
[17:32] <lieb> I'll send it around after meeting
[17:32] <pgraner> lieb: will it be in a4 or a5?
[17:32] <lieb> testing today, packaging this week
[17:33] <pgraner> lieb: so I take it A4...
[17:33] <lieb> how long the pipeliine after that I don' tknow
[17:33] <apw> i note kerneloops is not installed by default, are we planning on making it a default install
[17:34] <amitk> apw: mdz has agreed to it in principle
[17:34] <lieb> Martin sent me something about nominations and inclusion meetings...
[17:34] <pgraner> apw: we need to talk to the foundations guys on that, lieb I'd ping robbiew and see what he says
[17:34] <amitk> we just need to check if it still runs as root or drops privilegs
[17:34] <lieb> ok
[17:35] <pgraner> BenC: how did we make out with the removal of the ACPI suspend bits...?
[17:35] <BenC> pgraner: acpi support is making use of dbus-pm and dbus-hal by default
[17:36] <lieb> amitk, k-oops keeps root. it reopens /dev/dmesg each time
[17:36] <BenC> pgraner: so it's mostly unused, unless the user switches it manually in the config file
[17:36] <apw> lieb, what does it use /dev/dmesg for?
[17:37] <apw> something that running dmesg cannot do?
[17:37] <lieb> tries that first, then /var/log/messages
[17:37] <pgraner> BenC: the task was to get rid of all but the one method of suspend...
[17:37] <amitk> lieb: that might be an objection to installing it by default.
[17:37] <BenC> pgraner: and it in affect is
[17:37] <BenC> pgraner: dbus-pm is the default...dbus-hal is the fallback
[17:38] <BenC> they are essentially the same method
[17:38] <pgraner> BenC: the problem in the past was users were reading on the web to use acpi supsend and would turn it on or use the /etc/acpi/*.sh scripts, and complicate the bug reports...
[17:38] <pgraner> BenC: are the scripts gone?
[17:39] <BenC> pgraner: No, I can easily remove it though...I must have misunderstood the reasoning behind it
[17:40] <pgraner> BenC: ok, we are trying to present one unified way to suspend and keep the confusion down to a min
[17:40] <BenC> pgraner: understood
[17:40] <pgraner> [ACTION] BenC to remove /etc/acpi/*.sh scripts
[17:40] <MootBot> ACTION received:  BenC to remove /etc/acpi/*.sh scripts
[17:40] <pgraner> [TOPIC] Vanilla Kernel Builds
[17:40] <MootBot> New Topic:  Vanilla Kernel Builds
[17:40] <pgraner> rtg, apw: sup with $TOPIC?
[17:41] <rtg> apw has presented some patches, still reviewing
[17:41] <rtg> I think we'll work it out next week
[17:41] <pgraner> rtg: I raised the priority on the RT ticket for the git stuff
[17:41] <pgraner> rtg: let me know if it stalls out and I'll escalate
[17:41] <apw> yeah we have some scripts which seem to make workable kernels.  so we need to get the environment to run them sorted out
[17:41] <rtg> thanks, it'll be required to fully implement vanilla builds
[17:42] <pgraner> rtg: s/escalate/beg/g
[17:42] <rtg> pgraner: I'm sure the key folks that I need will be in Berlin
[17:42] <pgraner> rtg: ack on that
[17:43] <pgraner> rtg: what do estimate as a ETA for this?
[17:43] <rtg> sometime after A4
[17:43] <pgraner> rtg: thanks
[17:43] <pgraner> [TOPIC] ARM
[17:43] <MootBot> New Topic:  ARM
[17:43] <pgraner> amitk: anything to report? Welcome back from holiday :-D
[17:44] <amitk> thanks
[17:44] <rtg> where are the ARM porter machines?
[17:45] <amitk> I am finishing up changes to our build system to allows us to cross compile arm on our intel boxes
[17:45] <amitk> something like: debuild -b -eARCH=armel -eCROSS_MPILE=arm-linux-
[17:45] <pgraner> rtg: I have the RT # and its still not complete
[17:45] <amitk> this should speed up kernel build testing quite a bit
[17:45] <rtg> amitk: that would be outstanding.
[17:46] <rtg> is there a cross compile tools package
[17:46] <rtg> ?
[17:46]  * apw cheers for that idea
[17:46] <cking> ..and where is all this documented?
[17:46] <amitk> no. But I'll post instructions on how to get a tar ball and set up an environment
[17:46] <rtg> wfm
[17:47] <apw> tarball yeeks
[17:47] <amitk> perhaps we can nudge doko to provide a cross-compile toolchain in berlin over beer
[17:47] <apw> yeah i'd contribute a beer to the pot for that one
[17:47] <rtg> hey, I can live with tarballs. ANYTHING to speed up the builds.
[17:47] <amitk> besides this I am working through the OEM boards and patches
[17:48] <pgraner> amitk: thanks...
[17:48] <amitk> over...
[17:48] <pgraner> [TOPIC] LPIA
[17:48] <MootBot> New Topic:  LPIA
[17:48] <ogra> any news on the linux-omap merge ?
[17:48]  * pgraner pauses
[17:48] <pgraner> amitk: ^^^^^^^^^^^^^
[17:48] <amitk> ogra: still working with the maintainer to get a set of base patches
[17:49] <ogra> we'd like to somehow involve the community ... most of them have beagle boards, so having omap packages (at least for that) would gain us a lot user help
[17:49]  * amitk agrees
[17:49] <ogra> additionally we have a lot of n8x0 users
[17:49] <amitk> but merging the tree in its current state will cause a heavy maintenance burden
[17:50] <ogra> though thats not as pressing since the boot setup requires some tinkering anyway
[17:50] <ogra> yeah, indeed i dont want to push you into something like that :)
[17:50] <amitk> unfortunately I can't give a date. Only promise that it will happen :)
[17:51] <ogra> the current HW we support in the kernel doesnt really gain us much is the prob ... nobody will run ubuntu-desktop on his nslu2 :)
[17:51] <pgraner> [TOPIC] LPIA
[17:51] <MootBot> New Topic:  LPIA
[17:51] <ogra> but thanks for the info so far
[17:51] <pgraner> sconklin: how is that hairball?
[17:52] <rtg> aack, phpht
[17:52] <sconklin> I have a handle on the differences between the netbook tree and ours - but
[17:52] <pgraner> always a "but"
[17:52] <sconklin> Just discovered that there is a separate branch in the netbook tree with some commits that are needed, so I'm looking at that
[17:53] <cking> it's quite a hairball
[17:53] <sconklin> and then next week we can discuss how to manage this moving forward
[17:53] <lool> i'd like to know about the hardy patches
[17:53] <lool> Not the one from the netbook tree, the ones in the hardy official tree
[17:53] <lool> Living as lpia specific patches
[17:54] <lool> It seems these are missing for proper support of some lpia devices both in intrepid and jaunty
[17:54] <sconklin> can you provide some examples?
[17:54] <rtg> how about moving thios to the mailing list?
[17:54] <sconklin> cool
[17:54] <lool> debian/binary-custom.d/{lpia,lpiacompat}/patchset in ubuntu/ubuntu-hardy.git
[17:55] <pgraner> rtg: ack on that... we are running down on time
[17:55] <lool> I am not in a position to sort them out myself
[17:55] <pgraner> [TOPIC] Open Discussion
[17:55] <MootBot> New Topic:  Open Discussion
[17:56] <lool> So who's sending the hardy patches to the ML?
[17:56] <pgraner> Anyone need to raise anything quickly as we only have 4 min left
[17:56] <apw> lool i think we want you to remind us of where these patches are on the mailing list
[17:56] <apw> nothing here
[17:56] <amitk> lool: add them to the pending issues thread
[17:57] <lool> Hmm ok; albeit sconklin cking yourself and pgraner were in copy
[17:57] <lool> amitk: it's in there...
[17:57] <lool> Since the beginning
[17:57] <amitk> lool: ok.. i thought you had more examples
[17:57] <ogra> point 3)
[17:57] <lool> Well I have more specific examples such as the SSD in the jax10
[17:57] <ogra> in the list
[17:57] <lool> Which I filed as a bug back in the intrepid cycle
[17:57] <lool> As a result we have half the storage on the jax10 when running intrepid
[17:58] <apw> perhaps we need to get some tags on the bugs so we can find them all
[17:58] <apw> kernel-lpia or summat
[17:59] <lool> I filed only one bug about these patches, but I discovered that the bug was a result of the patches being dropped and that's why I wanted them screened/reviewed
[17:59] <lool> And possibly merged
[17:59] <pgraner> lool: lets take this offline and get it sorted... we are about out of time.
[17:59] <pgraner> There will not be a meeting next week due to the sprint in Berlin!
[18:00] <pgraner> We will pick up the following week 9 Feb
[18:00] <ogra> we'll all bug you all the time in preson :P
[18:00] <ogra> *person
[18:00] <pgraner> Thanks everyone
[18:00] <pgraner> #endmeeting
[18:00] <MootBot> Meeting finished at 12:00.
[18:00] <lool> ogra: I'd prefer resolving at least some issues before the sprint
[18:00] <amitk> bye
[18:00] <ogra> lool, for lpia you mean ?
[18:00] <lool> ogra: For whatever isn't low priority


[06:12] <Howlru> TAIWAN, take care over the Typhoon Soulik and try having fun with it!!!!!!!!!!!!!!!
[06:12] <Howlru> SHOOOO LEEEEEEEEEEEE
[06:12] <Howlru> SHOOOO LEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
[06:14] <Howlru> SHOOOOOOOOOOOOOOOOOOOOOO LEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE


[00:29] <knome> ochosi, a very early draft with pleia2: http://pad.ubuntu.com/xubuntu-derivative-guidelines
[06:04] <ochosi> knome: read through, looks good to me!
[06:04] <ochosi> that one is maybe a bit too much "volunteers who do volunteer support" :)
[06:05] <ochosi> other than that, nice work! (ofc you too, pleia2)
[09:55] <knome> ochosi, heh, sure
[11:34] <ochosi> bluesabre: btw, is there anything in the dev projects we have put on the blueprint where you want my input specifically? (as in mockups, code or artwork)
[11:56] <elfy> hi everyone - been minus phone line and interwebs since Monday morning - unfortunately for you they fixed it
[11:56] <astraljava> ...aaaand the fun stops now.
[11:57] <elfy> I'll be off again then ...
[11:57] <astraljava> ;)
[11:57] <astraljava> Good to have you back.
[11:58] <elfy> did you notice I was gone though :p
[11:58] <astraljava> Not really, I've been off quite a lot myself this week.
[11:59]  * ochosi noticed and was already wondering whether to start worrying
[12:02] <elfy> if it had been much longer I would have sent you a I am alive mail :p
[12:04] <elfy> ochosi: re LO - now I know that we have it I'll takemore note of updates
[12:05] <ochosi> yeah, i think there'll be a more formal announcement for LO 5.0 and all
[12:05] <elfy> not sure if I said I grabbed the LO icons or not -  but  I did
[12:05] <ochosi> but i thought it's good to inform everyone as early as possible
[12:05] <ochosi> oh good
[12:06] <ochosi> there is 1) a daily build of them now and 2) you can easily clone/update the git repo and run "make clean && make && sudo make install" to get the latest stuff
[12:06] <elfy> oh right - if you can point me to it please :)
[12:07] <bluesabre> ochosi: running out... but if you feel like doing any refreshed UI mockups for any of our regular apps, I'll try to get that in place this cycle
[12:07] <bluesabre> maybe mugshot/menulibre if we want to embed them
[12:07] <bluesabre> gotta run, bbl
[12:07] <ochosi> elfy: which one do you prefer?
[12:07] <ochosi> bluesabre: ok, let's discuss details when we're both around again
[12:08] <elfy> ochosi: I see it in shimmer daily
[12:08] <ochosi> yup
[12:08] <elfy> I have that ppa anyway
[12:08] <ochosi> perfect, in that case it's only one apt-get install away
[12:08] <elfy> yup
[12:08] <ochosi> not sure when that was built, i pushed some more updates today
[12:09] <ochosi> but generally this repo won't be so terribly active every day throughout the cycle, so i think it's fine
[12:09] <elfy> ok - well when I'mback from work - I'll update and get it installed
[12:09] <ochosi> okeydoke, hf!
[12:17] <elfy> bbl
[12:57] <ochosi> bluesabre: i just noticed that the symlink in /usr/lib/libreoffice/share/config points to images_elementary.zip -> /build/libreoffice-style-elementary-vktw59/libreoffice-style-elementary-201506030415~ubuntu14.04.1/debian/libreoffice-style-elementary/usr/share/libreoffice/share/config/images_elementary.zip
[12:57] <ochosi> bluesabre: instead it should be ../../../../share/libreoffice/share/config/images_elementary.zip
[15:02] <elfy> ochosi: is ^^ why installing LO style from ppa is a fail to work?
[15:02] <elfy> (it installs apparently)
[15:10] <ochosi> elfy: you mean for you it didn't work? if so, then yes
[15:11] <elfy> okey doke - thought I was going madder
[15:16] <ochosi> you can always try the github repo, it does essentially the same thing
[15:16] <ochosi> and with "sudo make uninstall" everything is back to as it was before
[15:21] <elfy> ochosi: yep understood that - just prefer to ppa if I can - then it all gets taken care of for me :)
[15:21] <ochosi> yeah
[15:21] <ochosi> i guess it'll be an easy fix for bluesabre
[19:08] <elfy> oh good lord - suddenly affected by missing letters here after a reboot ...
[21:32] <knome> efy, wht?
[23:42] <ochosi> knome: i think elfy refers to personal letters he authored in moments of passion and/or grief, that suddenly went missing after rebooting his computer. as a human being with feelings, naturally this affects him. rats!
[23:43] <knome> ochosi, heh.
[23:45] <pleia2> lol


[08:13] <mup> Bug #1599402 opened: read-only users: unauthorized access to read-only functionalities <juju-core:New> <https://launchpad.net/bugs/1599402>
[12:58] <mup> Bug #1599503 opened: Cannot upgrade charm if storage is modified, even if the service doesn't use said storage <juju-core:New> <https://launchpad.net/bugs/1599503>
[13:04] <mup> Bug #1599507 opened: juju status show blank for public name for one machine. <juju-core:New> <https://launchpad.net/bugs/1599507>
[13:40] <mgz> dooferlad: bug 1450729
[13:40] <mup> Bug #1450729: juju should be able to use nodes acquired by the same user in MAAS <cloud-installer> <deploy> <landscape> <maas-provider> <juju-core:Triaged> <MAAS:Opinion> <https://launchpad.net/bugs/1450729>
[14:32] <mup> Bug #1599507 changed: juju status show blank for public name for one machine. <juju-core:New> <OPNFV:New> <https://launchpad.net/bugs/1599507>
[14:55] <aisrael> cherylj: Could you take a new look at https://bugs.launchpad.net/juju-core/+bug/1287665? We ran into this issue during customer meetings last week in Madrid.
[14:55] <mup> Bug #1287665: Export bundle without juju GUI <canonical-is> <deployer> <sts-support> <juju-core:Triaged> <juju-deployer:New> <https://launchpad.net/bugs/1287665>
[14:56] <cherylj> aisrael: sure
[14:58] <cherylj> aisrael: we are already fully booked for 2.1 and the remaining 2.0 work.  We can put this on a wish list, but I wouldn't be optimistic about getting it any time soon :(
[14:59] <aisrael> cherylj: ack, thanks for looking
[15:02] <cherylj> aisrael: just fyi - it's already on the "feature request" list:  https://github.com/juju/juju/wiki/Feature-Requests
[15:02] <aisrael> cherylj: excellent, thanks!
[15:03] <cherylj> aisrael: the idea is that we would look there for features when we make our plans, but we were already overcommitted for 2.1
[15:04] <aisrael> cherylj: Understood. I'll check juju-bundlizer to see if that can be updated to work with the new API in the meantime
[15:06] <aisrael> deployerizer, rather
[15:50] <mup> Bug #1599315 changed: LXD no longer gets correct network in JUJU beta11 and MAAS2rc1 <network> <juju-core:Invalid> <https://launchpad.net/bugs/1599315>
[16:17] <marcoceppi> aisrael: it might be worth renaming deployerizer to something like `juju get-bundle` to make it clearer what it's doing?
[16:18] <marcoceppi> cherylj: I also noticed that the hook-tool descriptions are out of date as of beta11, they still reference "service"
[16:18] <rick_h_> but 'deployerizer' is so cool! It seems like a james bond weapon.
[16:19] <aisrael> marcoceppi: ack, I agree. I kept typing it as bundlizer because name =/= functionality
[16:19] <cherylj> marcoceppi: oh, thanks for finding that.  Want to open a bug, or should I?
[16:19] <marcoceppi> cherylj: https://bugs.launchpad.net/juju-core/+bug/1599570
[16:19] <mup> Bug #1599570: hook-tool help messages still reference service <juju-core:New> <https://launchpad.net/bugs/1599570>
[16:19] <cherylj> there ya go
[16:19] <cherylj> thanks :)
[16:20] <mup> Bug #1599570 opened: hook-tool help messages still reference service <juju-core:New> <https://launchpad.net/bugs/1599570>
[18:56] <mup> Bug #1599612 opened: remove-application has unexpected output with subordinate units <juju-core:New> <https://launchpad.net/bugs/1599612>
[22:15] <mup> Bug #1573020 changed: upgrade-charm --path does not recognize dot <juju-release-support> <upgrade-charm> <juju-core:Triaged> <https://launchpad.net/bugs/1573020>
[22:15] <mup> Bug #1576346 changed: upgrade-charm with a local charm fails with trailing slash <juju-release-support> <papercut> <upgrade-charm> <juju-core:Triaged> <https://launchpad.net/bugs/1576346>


[04:17] -queuebot:#ubuntu-release- Unapproved: rejected lg-gpio [source] (kinetic-proposed) [<IP_ADDRESS>-0ubuntu1]
[04:20] -queuebot:#ubuntu-release- Unapproved: accepted budgie-control-center [source] (jammy-proposed) [1.0.1-2ubuntu3]
[05:04] -queuebot:#ubuntu-release- Unapproved: accepted budgie-desktop [source] (jammy-proposed) [10.6.1-1ubuntu2]
[05:24] -queuebot:#ubuntu-release- Unapproved: accepted gnome-calendar [source] (kinetic-proposed) [43.1-0ubuntu1]
[05:27] -queuebot:#ubuntu-release- Unapproved: accepted runc [source] (focal-proposed) [1.1.0-0ubuntu1~20.04.2]
[05:36] -queuebot:#ubuntu-release- Unapproved: accepted runc [source] (jammy-proposed) [1.1.0-0ubuntu1.1]
[05:45] -queuebot:#ubuntu-release- Unapproved: accepted runc [source] (kinetic-proposed) [1.1.2-0ubuntu1.1]
[06:28] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (kinetic-proposed) [2.57.5+22.10]
[08:00] <schopin> sru-team: could it be possible to promote the tzdata SRUs out of their respective -proposed? That's LP: #1992692 and LP: #1969671
[08:00] -ubottu:#ubuntu-release- Launchpad bug 1992692 in tzdata (Ubuntu Jammy) "tzdata 2022e release" [Undecided, Fix Committed] https://launchpad.net/bugs/1992692
[08:00] -ubottu:#ubuntu-release- Launchpad bug 1969671 in tzdata (Ubuntu Jammy) "Misspelled Ukrainian cities in tzdata" [Undecided, Fix Committed] https://launchpad.net/bugs/1969671
[08:13] -queuebot:#ubuntu-release- Unapproved: apparmor (focal-proposed/main) [2.13.3-7ubuntu5.1 => 2.13.3-7ubuntu5.2] (core, i386-whitelist)
[08:26] -queuebot:#ubuntu-release- Unapproved: apparmor (jammy-proposed/main) [3.0.4-2ubuntu2.1 => 3.0.4-2ubuntu2.2] (core, i386-whitelist)
[09:16] <bdmurray> schopin: I've released tzdata but it would be good to chase an AA to fully phase the updates
[10:14] <schopin> ubuntu-archive: could you please fully phase tzdata in bionic, focal and jammy, and copy it to the -security pockets? TIA :)
[10:15] <bdmurray> schopin: I didn't see security team member sign off on the copy but I didn't look closely
[10:17] <schopin> bdmurray: you're right, I forgot to check! (didn't handle the update, just trying to move things along)
[10:19] <schopin> sbeattie: I see you handled the ESM updates. Could you sign off on the rest of the updates?
[11:12] <coreycb> hello sru team, we have new versions of python-oslo.messaging in the jammy/kinetic queues that revert a patch that is breaking active/active rabbitmq failover. I'm wondering if they can get reviewed, unless they are blocked until L is open.
[11:42] <coreycb> here's the bug for the SRU above https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1993149
[11:42] -ubottu:#ubuntu-release- Launchpad bug 1993149 in python-oslo.messaging (Ubuntu Kinetic) "VMs stay stuck in scheduling when rabbitmq leader unit is down" [Critical, Triaged]
[12:06] <bdmurray> coreycb: looking
[12:08] <coreycb> thanks bdmurray
[12:12] <bdmurray> coreycb: its not a blocker but I'd have expected ubuntu1.1 not ubuntu2
[12:13] <coreycb> bdmurray: oh I thought I did do that. or do you mean for jammy?
[12:13] <bdmurray> coreycb: I was looking at jammy yes
[12:16] -queuebot:#ubuntu-release- Unapproved: accepted python-oslo.messaging [source] (kinetic-proposed) [14.0.0-0ubuntu1.1]
[12:16] <bdmurray> coreycb: if you could fix the jammy version that would be nice
[12:17] <coreycb> bdmurray: ok I'll re-upload that to jammy with 1.1. I tend to only use 1.x for dev-1 releases that still have the same upstream version as the dev release. but maybe I should use it for older releases as well when it's just a patch change.
[12:18] <georgiag> rbasak: hello! amurray sponsored apparmor SRUs for both focal and jammy and they're sitting in the unapproved queue. could you please review and promote them to -proposed when you're available? thank you!
[12:21] <coreycb> bdmurray: 1.1 uploaded. thanks again.
[12:21] -queuebot:#ubuntu-release- Unapproved: python-oslo.messaging (jammy-proposed/main) [12.13.0-0ubuntu1 => 12.13.0-0ubuntu1.1] (openstack)
[12:23] -queuebot:#ubuntu-release- Unapproved: rejected python-oslo.messaging [source] (jammy-proposed) [12.13.0-0ubuntu2]
[12:25] -queuebot:#ubuntu-release- Unapproved: accepted python-oslo.messaging [source] (jammy-proposed) [12.13.0-0ubuntu1.1]
[14:43] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-advantage-tools [source] (focal-proposed) [27.11.3~20.04.1]
[14:43] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-advantage-tools [source] (jammy-proposed) [27.11.3~22.04.1]
[14:44] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-advantage-tools [source] (bionic-proposed) [27.11.3~18.04.1]
[14:44] <rbasak> bdmurray: ^ is Kinetic open for SRUs yet? I'm accepting ubuntu-advantage-tools everywhere else, and it'll need a copy forward to L.
[14:45] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-advantage-tools [source] (xenial-proposed) [27.11.3~16.04.1]
[14:45] <rbasak> (and I've reviewed K; it's fine to accept when ready)
[14:52] <bdmurray> I did accept a Kinetic SRU but that could have been possible because I'm in ubuntu-release
[15:06] -queuebot:#ubuntu-release- Unapproved: linux-lowlatency (jammy-proposed/main) [5.15.0-52.58 => 5.15.0-53.59] (kernel) (sync)
[15:06] -queuebot:#ubuntu-release- Unapproved: linux-restricted-modules-lowlatency (jammy-proposed/restricted) [5.15.0-52.58+1 => 5.15.0-53.59] (no packageset) (sync)
[15:06] -queuebot:#ubuntu-release- Unapproved: linux-meta-lowlatency (jammy-proposed/main) [<IP_ADDRESS>.47 => <IP_ADDRESS>.48] (kernel) (sync)
[15:07] -queuebot:#ubuntu-release- Unapproved: linux-restricted-signatures-lowlatency (jammy-proposed/restricted) [5.15.0-52.58+1 => 5.15.0-53.59] (no packageset) (sync)
[15:07] -queuebot:#ubuntu-release- Unapproved: linux-signed-lowlatency (jammy-proposed/main) [5.15.0-52.58 => 5.15.0-53.59] (no packageset) (sync)
[15:20] -queuebot:#ubuntu-release- Unapproved: accepted linux-lowlatency [sync] (jammy-proposed) [5.15.0-53.59]
[15:20] -queuebot:#ubuntu-release- Unapproved: accepted linux-restricted-modules-lowlatency [sync] (jammy-proposed) [5.15.0-53.59]
[15:20] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed-lowlatency [sync] (jammy-proposed) [5.15.0-53.59]
[15:20] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-lowlatency [sync] (jammy-proposed) [<IP_ADDRESS>.48]
[15:20] -queuebot:#ubuntu-release- Unapproved: accepted linux-restricted-signatures-lowlatency [sync] (jammy-proposed) [5.15.0-53.59]


[10:46] <mup> Bug #1910552 changed: machines fail to boot if MAAS doesn't respond to cloud-init <cloud-init:Fix Released> <MAAS:Invalid by adam-collard> <https://launchpad.net/bugs/1910552>
[10:49] <mup> Bug #1910552 opened: machines fail to boot if MAAS doesn't respond to cloud-init <cloud-init:Fix Released> <MAAS:Invalid by adam-collard> <https://launchpad.net/bugs/1910552>
[10:55] <mup> Bug #1910552 changed: machines fail to boot if MAAS doesn't respond to cloud-init <cloud-init:Fix Released> <MAAS:Invalid by adam-collard> <https://launchpad.net/bugs/1910552>