[12:01] <barry> hi everyone.  if i'm not mistaken, it's time once again for our bi-weekly udd stakeholders meeting
[12:01] <barry> #startmeeting
[12:01] <MootBot> Meeting started at 07:01. The chair is barry.
[12:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[12:01] <jelmer> hi barry!
[12:01] <barry> jelmer: hi!
[12:01] <poolie> hi barry, jelmer
[12:01] <barry> hi poolie
[12:01] <barry> do you know if anyone else is joining us today?
[12:02] <barry> well, anyway, let's get started
[12:02] <barry> [TOPIC] agenda
[12:02] <MootBot> New Topic:  agenda
[12:02] <barry> [LINK] https://wiki.ubuntu.com/DistributedDevelopment/20110713
[12:02] <MootBot> LINK received:  https://wiki.ubuntu.com/DistributedDevelopment/20110713
[12:03] <barry> [TOPIC] action items
[12:03] <MootBot> New Topic:  action items
[12:03] <barry>    * jelmer to study the feasibility of merge helper ([[https://bugs.launchpad.net/bzr-builddeb/+bug/608675|bug 608675]]) as an intermediate step for quilt support
[12:03] <barry>  
[12:04] <jelmer> I've been away for the last week so haven't spent any time on this since
[12:04] <jelmer> at the last meeting (at the rally) we discussed it, and my conclusions there were that it seems feasible and I've started working on implementing it.
[12:05] <barry> jelmer: awesome.  we'll just keep it on for next time
[12:05] <poolie> that's great
[12:05] <barry>    * jelmer to look into [[https://bugs.launchpad.net/udd/+bug/609187|bug 609187]] (warn when package import is out of date)
[12:05] <poolie> there was some discussion recently of this being useful even for non-quilt branches
[12:05] <poolie> hm
[12:05] <poolie> or, more generally, of being able to merge both the patched and unpatched forms
[12:06] <jelmer> jam mentioned on IRC earlier that he's working on bug 609187
[12:06] <poolie> barry, i think jam and others worked on that
[12:06] <poolie> oh, and maxb in london
[12:06] <barry> very nice.  so, in progress?
[12:06] <jelmer> yep
[12:06] <jelmer> should perhaps be owned by jam though?
[12:07] <james_w> hi
[12:07] <maxb> jam has taken my proof of concept "How to talk to LP without launchpadlib" and is pursuing it
[12:07] <barry> sure, i can update that.
[12:07] <poolie> hi maxb
[12:07] <barry> hi maxb
[12:07] <barry> maxb: do you just make straight up http calls?
[12:08] <poolie> the point of avoiding lplib is that it's much faster to just make the single call we care about
[12:08] <poolie> yes
[12:08] <barry> makes sense
[12:08] <maxb> Minimizing roundtrips and costly WADL downloads really matters if we're going to do this interactively
[12:08] <barry> +1
[12:08] <Pendulum> 
[12:09] <barry>    * Riddell to file bug saying that packaging branch pages on code.lp.net should be better labeled
[12:09] <barry> anybody know if the bug has been filed?
[12:09] <poolie> istr that he did
[12:09] <jelmer> ... and fixed the bug :)
[12:09] <poolie> and, perhaps he worked on it at the rally
[12:09] <poolie> hooray
[12:10] <barry> yay!
[12:10] <barry> do you happen to have the bug #?
[12:11] <poolie> bug 797688
[12:11] <barry> thanks (you're quicker at searching than me at this hour :)
[12:11] <poolie> i have kanban fu
[12:11] <poolie> http://people.canonical.com/~mbp/kanban/jr-kanban.html
[12:11] <MootBot> LINK received:  http://people.canonical.com/~mbp/kanban/jr-kanban.html
[12:11] <poolie> scan down the right hand column until you find it
[12:11] <barry> ah, nice!
[12:12] <poolie> i like it
[12:12] <barry> i didn't realize each person had their own kanban
[12:13] <barry> [TOPIC] package importer progress
[12:13] <MootBot> New Topic:  package importer progress
[12:13] <poolie> yes, there's one aggregated per team and one per person
[12:13] <poolie> let's see
[12:13] <poolie> i think max said some new things started failing
[12:13] <maxb> There does seem to have been a small uptick in the count
[12:13] <poolie> hm, so it stepped down a bit, but now has drifted up
[12:13] <maxb> Besides the append-revisions-only stuff, which I'm taking account of
[12:13] <poolie> back from 400 to 425?
[12:14] <poolie> some of these are AppendRevisionsOnlyViolation which is a recent regression
[12:14] <poolie> so i'm proposing to make this rather more of a priority for the canonical bzr team
[12:14] <maxb> The append-revisions-only stuff accounts for ~25, but I've fixed about ~20 imports in the last 48 hours, which is why were are back at around 400
[12:14] <poolie> putting it at the top of our quarterly planning commitments, and trying to get it below 200 by the start of october
[12:15] <poolie> which would be much faster than our current trend
[12:15] <poolie> thanks max
[12:15] <barry> poolie: that would be amazing
[12:15] <jelmer> I've made some progress on support for multiple upstream tarballs, which isn't finished yet but should help a bit too.
[12:15] <poolie> oh, that's great
[12:15] <maxb> One thing is that there seems to be a gradual uptick in the number of packages using multiple upstream tarballs. That's also the top single failure cause at the moment
[12:16] <maxb> Another thing to consider is that quite a number of the failures are failures during the generation of merge preview diffs - *not* the import itself
[12:16] <maxb> A subcategory of those are, I believe, being addressed by a bugfix of vila's
[12:17] <poolie> why does it generate merge preview diffs?
[12:17] <maxb> I'm guessing because james_w thought it would be useful?
[12:17] <maxb> I doubt many people know they exist.
[12:17] <maxb> http://package-import.ubuntu.com/merges/
[12:17] <MootBot> LINK received:  http://package-import.ubuntu.com/merges/
[12:18] <james_w> I started generating them as a test
[12:18] <poolie> hi james
[12:18] <james_w> but never followed it through to be the replacement for merges.ubuntu.com
[12:18] <james_w> hi
[12:18] <poolie> huh
[12:18] <barry> james_w: hi.  i didn't know that existed either
[12:18] <poolie> so, what shall we do
[12:19] <poolie> perhaps we should move it out of line so that it doesn't cause failure of the actual package import?
[12:19] <maxb> I estimate ~44 failures are in the merge generation. They are probably legitimate bzrlib bugs
[12:20] <maxb> I think we should be mindful of that possibility, but see how many of the failures are cleared up by vila's NoFinalPath bugfix before investing time
[12:20] <james_w> that seems to be a fair number of them
[12:21] <jelmer> Merges are one of the goals of the UDD branches, so it seems useful to keep it in.
[12:21] <james_w> given no-one is using the output currently it wouldn't really cost anything to delete the code
[12:21] <barry> or maybe comment it out for now?
[12:22] <poolie> ok, well, now i know it's there :)
[12:22] <barry> :)
[12:22] <poolie> i agree with max, let's see how it goes with current in progress work landed, and then we can think about pruning it
[12:22] <poolie> or, alternatively, at least linking to ti
[12:22] <barry> +1
[12:23] <barry> so, not really on the agenda, but i see lp and bzr got updated last night?  how'd that go?
[12:23] <poolie> it was a bit bumpy
[12:23] <barry> dang
[12:23] <barry> but everything worked out?
[12:23] <poolie> since we went several revisions forward, and there were some bad interactions between changes in bzr and in bzr-svn when importing large branches
[12:24] <poolie> we are having a postmortem thread at the moment
[12:24] <poolie> to try to understand what happened
[12:24] <poolie> but i think it will be ok
[12:24] <barry> cool.  i'm on the mlist so i'll follow along
[12:24] <poolie> we will make it safer to deploy and roll back, and then deploy more often
[12:24] <poolie> similar to the approach being taken with other bits of lp
[12:25] <poolie> and speaking of which, can i just say how much i'm looking forward to their new shorter upgrade windows
[12:25] <poolie> (https://lists.launchpad.net/launchpad-dev/msg07623.html but it's a bit offtopic)
[12:25] <poolie> jelmer, can you tell us about what this is likely to change with imports?
[12:26] <jelmer> poolie: Can you rephrase that, do you mean the vcs imports?
[12:27] <poolie> yes
[12:27] <barry> also, what are the top-level user visible changes we'll see in bzr/udd/codehosting now?
[12:27] <poolie> we can hope to see more of them succeed after the lp upgrade?
[12:28] <jelmer> poolie: What was the recent lp upgrade from last night barry was referring to exactly?
[12:28] <poolie> there should be a big new feature in lp which is showing diffs inline in the branch pages
[12:28] <poolie> lp had an upgrade outage today (australian time)
[12:28] <poolie> hm
[12:28] <poolie> perhaps we should get our story straight offline :)
[12:28] <barry> that will be *awesome*
[12:28] <poolie> and then post something on the lp blog about user visible changes, if any
[12:29] <barry> poolie: +1, can i give you that action?
[12:29] <poolie> actually could i put that on jelmer, since he landed the change iirc
[12:30] <poolie> the inline content feature is http://people.canonical.com/~andrew/Inline-diff-screenshot.png
[12:30] <poolie> not landed yet
[12:30] <barry> [ACTION] jelmer to post summary of user visible changes with lp rollout
[12:30] <MootBot> ACTION received:  jelmer to post summary of user visible changes with lp rollout
[12:30] <jelmer> I haven't caught up on all that email yet, but I'd be happy to take an action item about the post-morten analysis
[12:30] <jam> poolie: that specific screenshot is for merge proposal pages
[12:30] <poolie> true
[12:30] <jam> danilo's change was for Branch pages, which I certainly don't see, but I don't know whether or not his expander code has landed.
[12:30] <poolie> i think the code changes proposed now may only touch mp pages but we should be able to follow through and show stuff on the branch too
[12:31] <poolie> jelmer so i guess there's two things to follow on, one is the postmortem (what went wrong) and the other is the feature announcement, if any (what will go right)
[12:31] <poolie> i had the idea that the updated bzr-git etc are going to help a lot more branch imports complete
[12:31] <poolie> am i confused?
[12:32] <jelmer> I haven't landed anything related to the expander code
[12:32] <jelmer> I do have a fix for having bzr-svn deal with tags better (not use so much memory), but IIRC I haven't proposed that for landing on lp yet
[12:33] <poolie> didn't you land several updates into lp when we were at the rally?
[12:35] <poolie> perhaps we should move on; this isn't really udd specific
[12:35] <maxb> I have something I'd like people to have a think about: What are we going to do about developer-maintained package branches, which don't use upstream-* tags because they merge directly from upstream's bzr, and thus the UDD importer always fails on currently? I'm thinking of, e.g. apport
[12:35] <jelmer> (sorry, looking through the revision log atm..)
[12:35] <barry> poolie: okay
[12:35] <barry> [TOPIC]  * Get rid of `bzr mark-uploaded` ?
[12:35] <MootBot> New Topic:   * Get rid of `bzr mark-uploaded` ?
[12:35] <jelmer> taking that offline (in the post-mortem thread perhaps?) might indeed be better
[12:36] <Riddell> hi, sorry I'm late
[12:36] <barry> so, if i'm not mistaken, mark-uploaded is more or less unnecessary now, right?
[12:37] <jelmer> somewhat; debcommit -r will tag too and "bzr tag" without argument can also behave the same way as mark-uploaded
[12:37] <Riddell> hmm, I was hoping to get away from using debcommit
[12:37] <barry> jelmer: what does mark-uploaded do that bzr tag or debcommit doesn't?
[12:38] <barry> i guess there are two things leading these questions: whether to change the udd documentation to just use bzr tag, and whether to actually deprecate or get rid of the command?
[12:38] <jelmer> barry: I don't think there's anything it does that bzr tag doesn't, other than perhaps being a bit more clearly named
[12:39] <barry> jelmer: cool.  any objections to me changing the udd docs to use tag instead?
[12:39] <poolie> james_w ^?
[12:39] <barry> Riddell: i'd like to get away from recommending debcommit too
[12:39] <james_w> not really
[12:40] <poolie> i wonder if bzr builddeb could instead hook into the tag command (through adding a hook, not in some gross way) to give people policy checks?
[12:40] <james_w> probably worth a note that if bzr says that they have to give a tag name they need a newer bzr/bzr-builddeb, or their bzr-builddeb is incorrectly installed
[12:40] <poolie> if those checks are seen as useful
[12:41] <barry> james_w: good idea
[12:41] <barry> [ACTION] barry to update udd docs to use `bzr tag` instead of `bzr mark-uploaded`
[12:41] <MootBot> ACTION received:  barry to update udd docs to use `bzr tag` instead of `bzr mark-uploaded`
[12:41] <poolie> barry i suggested Riddell might put his packaging background to use in working on the packaging guide with yourself and daniel
[12:42] <Riddell> yes, I'm working my way through it fixing things and working out what's missing or not clear
[12:42] <poolie> great
[12:42] <barry> Riddell: fantastic.  you can add me as a reviewer for any mp
[12:42] <poolie> shall we talk about max's question?
[12:42] <barry> Riddell: do you want to take the above action instead of me?
[12:42] <ScottK> Riddell: Does that include non-UDD packaging?
[12:42] <Riddell> barry: yes can do
[12:43] <poolie> hi scott
[12:43] <barry> [ACTION] Riddell to update udd docs to use `bzr tag` instead of `bzr mark-uploaded`
[12:43] <MootBot> ACTION received:  Riddell to update udd docs to use `bzr tag` instead of `bzr mark-uploaded`
[12:43] <barry> poolie: yes, let's take up maxb's question
 I have something I'd like people to have a think about: What are we going to do about developer-maintained package branches, which don't use upstream-* tags because they merge directly from upstream's bzr, and thus the UDD importer always fails on currently? I'm thinking of, e.g. apport
[12:43] <Riddell> ScottK: I'd like to discuss that with dholbach, it needs quite a lot of changes to include non-UDD bits and I don't know if he has thought about how to do that (but essentially i'm working on it from a bzr developer perspective so no)
[12:44] <ScottK> That's one of the guide's biggest problems at the moment.
[12:44] <Riddell> ScottK: but the guide should either be renamed or fixed for that
[12:44] <ScottK> Agreed.
[12:44] <Riddell> yep
[12:44] <barry> ScottK: yep
[12:44] <jelmer> maxb: It would seem reasonable to just directly tag the upstream versions with upstream-X if they have the same contents
[12:46] <poolie> by detecting there's a revision identical to the orig.tgz?
[12:47] <jelmer> either by detecting or having some place where the upstream tag algorithm is specified
[12:47] <maxb> So perhaps the way forward is to discuss with the packagers of those packages how much they are willing to tweak their workflow for UDD compatibility
[12:47] <poolie> can we do something towards recognizing the actual tag in the upstream branch?
[12:47] <poolie> there very likely is one, istm
[12:47] <poolie> right
[12:47] <jelmer> bzr-builddeb already has a config variable export-upstream-revision which can be set to the tag pattern for finding upstream versions
[12:48] <poolie> maxb, what kind of tweaks?
[12:49] <jelmer> e.g. "export-upstream-revision = tag:bzr-svn-$UPSTREAM_VERSION" as bzr-svn's tagging algorithm uses the tag name "bzr-svn-1.0a" for version "1.0a"
[12:50] <jelmer> The proper place to store that sort of information would be in Launchpad's release information I think
[12:50] <poolie> that would be useful in other places
[12:50] <poolie> for instance automatically presenting the releases in the ui and ws
[12:50] <maxb> As in, potentially making use of "bzr merge-upstream", or setting tags manually
[12:52] <barry> it's getting late, so let's move on
[12:52] <barry> [TOPIC] bugs of interest
[12:52] <MootBot> New Topic:  bugs of interest
[12:52] <barry> [LINK] http://people.canonical.com/~mbp/kanban/canonical-bazaar-kanban.html
[12:52] <MootBot> LINK received:  http://people.canonical.com/~mbp/kanban/canonical-bazaar-kanban.html
[12:52] <poolie> good idea
[12:52] <barry> anything in particular to point out?
[12:53] <poolie> i plan to stop the package importer pretending to be james tomorrow
[12:53] <barry> nice :)
[12:53] <poolie> lots of bugs there
[12:53] <poolie> moving across
[12:54] <poolie> jelmer it looks like you should do a bzr-svn release
[12:54] <poolie> barry, james, maxb, is there anything especially biting you, or that you think especially needs attention?
[12:54] <jam> barry: [LINK] lp:///~jameinel/bzr/2.2-is-up-to-date
[12:54] <jelmer> poolie: I agree; the tags memory usage issue is the main thing that's blocking that at the moment.
[12:54] <jam> [LINK] lp:///~jameinel/bzr/2.2-is-up-to-date
[12:54] <MootBot> LINK received:  lp:///~jameinel/bzr/2.2-is-up-to-date
[12:55] <poolie> jam, what is that?
[12:55] <jam> I just added a "Branch.open" hook
[12:55] <jam> so that doing "bzr info lp:ubuntu/bzr" tells you if the branch is up-to-date
[12:55] <poolie> oh i see
[12:55] <poolie> great
[12:55] <barry> poolie: atm, nope. things are going well
[12:55] <poolie> we need to try again with a 2.3.4 sru into natty
[12:55] <poolie> ok
[12:55] <poolie> it's getting late here for sure
[12:55] <poolie> next?
[12:56] <jam> http://paste.ubuntu.com/643225/
[12:56] <MootBot> LINK received:  http://paste.ubuntu.com/643225/
[12:56] <barry> [TOPIC] aob
[12:56] <MootBot> New Topic:  aob
[12:56] <barry> just one small note: poolie the meeting 2 weeks from now is at the wrong time i think
[12:56] <jam> barry: I think that goes with the earlier action item (that I missed), for checking if import branches are up-to-date
[12:56] <poolie> yes, it does, that's nice
[12:57] <barry> jam: thanks
[12:57] <poolie> ok
[12:57] <barry> jam: that looks great
[12:57] <poolie> so we're going to keep it at the same time as today?
[12:57] <barry> poolie: if that worked for you guys.  it was much better for me ;)
[12:58] <jam> wfm, poolie is the one most impacted by it
[12:58] <poolie> ok
[12:58] <poolie> thanks everyone for coming, especially maxb
[12:58] <barry> okay, with that...
[12:59] <barry> #endmeeting
[12:59] <MootBot> Meeting finished at 07:59.
[12:59] <barry> thanks everyone
[12:59] <jelmer> thanks barry :)
[15:03] <mvo> hello
[15:03] <ev> hiya
[15:04] <jhunt_> ...././.-../.-../---
[15:04]  * slangasek waves
[15:04] <cjwatson> ..-. .. ... ....
[15:04] <slangasek> heh
[15:05] <barry> huzzah!
[15:05] <slangasek> #startmeeting
[15:05] <MootBot> Meeting started at 10:05. The chair is slangasek.
[15:05] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:05] <slangasek> [TOPIC] lightning round
[15:05] <MootBot> New Topic:  lightning round
[15:05] <slangasek> $ echo $(shuf -e cjwatson barry doko csurbhi stgraber jhunt mvo ev vorlon bdmurray)
[15:05] <slangasek> and... go
[15:05] <slangasek> bdmurray ev jhunt barry csurbhi stgraber cjwatson vorlon doko mvo
[15:05] <slangasek> bdmurray:
[15:05] <mvo> last again!
[15:05] <bdmurray> bug work
[15:05] <bdmurray> bug triage of ubiquity bug reports with SQUASHFS errors, fsys-tarfile-error apport package bug report cleanup, incompletion of ubiquity    install failures due to oom, FTBFS bug report modifications, added bug reporting guidelines for ubuntu-meta, crichton function to deal     with package-install-segfault bug reports, wrote a bug pattern for update-initramfs failures on Live Media and wrote a wiki page to point  people at
[15:06] <bdmurray> community stuff/work
[15:06] <bdmurray> review and approval of 2 new Ubuntu Bug Control members, added in iso-testing bug reports to the package status pages, udw class prep and  presentation regarding working with apport bugs
[15:06] <psurbhi> o/
[15:06] <bdmurray> development work
[15:06] <bdmurray> update-manager apport hook SRU update and new merge proposal for oneiric, branch adding casper version to apport bug reports from live     media, updated ubiquity apport package hook to ask permission before adding debug log and block SQUASHFS error bug reports, patch pilot    day (fixed pm-utils failed to inhibit suspend bug, 665651 which revealed a bug in toshset which caused suspend to fail), bzr branch for    unattended-upgrades and messag
[15:06]  * slangasek waves to psurbhi 
[15:06] <mvo> \o/ for u-m
[15:06] <bdmurray> done
[15:08] <ev> - More fighting over desk space. Now resolved! I'm officially a Millbank-based
[15:08] <ev>   employee from here on out. Yay.
[15:08] <ev> - integrating Wubi builds into cdimage. Should be working just as soon as
[15:08] <ev>   LP: #807974 gets fixed.
[15:08] <ev> - Further work on the IronPython Wubi test. I now have an executable bundle
[15:08] <ev>   that displays a WebKit view (of the people.ubuntu.com slideshow).
[15:08] <ev>   It's 8,751 KB, but I think I can further trim that down some. It's roughly:
[15:08] <ev>   7-zip's SFX header, a small configuration file, and an LZMA archive
[15:08] <ev>   concatenated together.  In the LZMA archive is the IronPython DLLs (3.32
[15:08] <ev>   MB), the Chromium Embedded Framework DLLs (25.7 MB), CefSharp DLLs (293 KB),
[15:08] <ev>   and the application bytecode (.NET) and libraries (12.6 KB). I'm going to
[15:08] <ev>   stick an address bar on this and deliver it to The Team to use for Wubi
[15:08] <ev>   slideshow development.
[15:08] <ev> - Looking into writing a small C++ wrapper around the front of our .NET
[15:08] <ev>   application to download and install the .NET 2.5 runtime when it's not
[15:08] <ev>   present on the system, rather than just letting Windows throw up an obtuse
[15:08] <ev>   error dialog.
[15:08] <ev> - Trying to target an IronPython build for .NET 2/3.5.
[15:08] <ev> - Developer Experience Community of Practice call.
[15:08] <ev> - Stuck recovering my work from home laptop using the black magic of grub2's
[15:08] <ev>   loop mounting code (hooray for having a spare ISO lying around in /home).
[15:08] <ev>   Any thoughts on writing a copy of the installation ISO to the filesystem
[15:08] <ev>   during installation and wiring it into grub such that if everything goes to
[15:08] <ev>   hell, the user has something to boot into. Or should we do the ChromiumOS
[15:08] <ev>   A and B boot branch thing instead?
[15:09] <ev> - Finished the PyGI port of SegmentedBar and nearly done with the timezone
[15:09] <ev>   map. Ran headfirst into GdkPixbuf.get_pixels() being hideously broken in
[15:09] <ev>   PyGI, blocking the finishing of the timezone port. Spent a lot of time
[15:09] <ev>   digging through the PyGI source looking for the best way to solve this in
[15:09] <ev>   this brave new world, proposed an approach to tomeu, and may have a solution
[15:09] <ev>   soon.
[15:09] <ev> - Helped the web team again with the Launchpad API, further modifying the
[15:09] <ev>   script I wrote for them to generate reports of what bugs they fixed to work
[15:09] <ev>   with date ranges.
[15:09] <ev> - Call with Steve on the plan for Wubi, and the hiring of a Windows developer.
[15:09] <ev> - Chat with Francis on our plans for the crash database. He's going to circle
[15:09] <ev>   back with Rob and then presumably continue the discussion on the existing
[15:09] <ev>   mail thread.
[15:09] <ev> - Started writing unit tests for gtkwidgets in ubiquity and a harness that
[15:09] <ev>   plays nice with the GTK main loop and the weird fact that PyGI raises
[15:09] <ev>   exceptions in a different thread of execution, thus they don't bubble up
[15:09] <ev>   around Gtk.main. I know, awesome, right?
[15:09] <ev> - Had to do some running around and paperwork for signing up to Canonical's
[15:09] <ev>   implementation of the cycle to work scheme.
[15:09] <ev> - More work on the wireless page for ubiquity. Implemented passphrase
[15:09] <ev>   handling.
[15:09] <slangasek> bdmurray: I think your line truncated; "unattended-upgrades and messag[...]"
[15:09] <ev> TODO:
[15:09] <ev> - Objectives. Eep.
[15:09] <ev> - Get hardware expensed for ubiquity testing in the datacenter.
[15:09] <ev> (done)
[15:09] <doko> ev: how much are charged for the desk? ;p
[15:10] <bdmurray> "bzr branch for unattended-upgrades and messages during shutdown, apt branch blocking of fsys tarfile error package install failures"
[15:10] <jhunt_> Raised MP to revert dokos gcc+armel change for libnih. Worked with
[15:10] <jhunt_> hallyn to find a resolution for bug 495394. Reviewed marrusl's
[15:10] <jhunt_> material for UDw. Some progress on Upstart disabling jobs feature.
[15:10] <jhunt_> Reviewed documentation changes for psurbhi's Upstart initramfs branch.
[15:10] <jhunt_> Worked through initramfs setup steps for Upstart and discussed with
[15:10] <jhunt_> psurbhi. Started to look at bug 436936 (again). Made some good
[15:10] <jhunt_> progress but then switched to bug 807293 which I am currently looking
[15:10] <jhunt_> at.
[15:10] <jhunt_> ./-./-..
[15:10] <ev> doko: I think you pay cvd in endless thank yous and one appears
[15:10] <barry> rebuilding main dev machine (still need to restore pbuilder/sbuild/vms) - been filing bugs like mad; bug 806661 (python-imaging needs to be multiarch aware); bug 806744 (lazr.smtptest testing); looked at bug 212370 (coretemp kernel module) but need to come back to it; pep382 lively discussion on mlist and code reviews; patch pilot (see ubuntu-devel@); developer experience CoP; lead UDW session on dh_python2; UDD stakeholders meeting;
[15:10] <barry> this week: work on lts ppa, continue on bug 788514; done.
[15:10] <barry>  
[15:13] <slangasek> barry: sorry I missed the UDD stakeholders meeting yet again; it's creeping towards the time of day that I can make it, but I had an 11pm call last night so 5am was going to be a little rough :)
[15:13] <slangasek> psurbhi: your turn
[15:13] <barry> slangasek: no worries ;)
[15:13] <psurbhi> *) working on making a ppa of initramfs, upstart and mountall - testing the install scripts, updated mkinitramfs and update-initramfs.
[15:13] <psurbhi> *) done.
[15:14] <slangasek> and learning about the evils of NSS in initramfses...
[15:14] <slangasek> stgraber is on vacation this week
[15:14] <psurbhi> :) yeah !
[15:14] <slangasek> cjwatson:
[15:15]  * stgraber waves
[15:15] <stgraber> and gets back to doing non Ubuntu stuff :)
[15:15] <cjwatson> hah, yeah, I remember discovering the fun of NSS in reduced systems when doing openssh-server-udeb a while back
[15:15] <cjwatson> Spent most of this week so far working on Launchpad, with mvo's help from the apt/python-apt side:
[15:15] <cjwatson>  * My dpkg-xz-support branch from last year will be ready to go once apt and python-apt SRUs land in lucid-updates.
[15:15] <cjwatson>  * My multiarch-translations branch probably still needs a bit more code review, but it's had a DB review and I believe the necessary apt change is due to go in as an SRU.  Unfortunately, I think the Launchpad downtime schedule is such that this may not actually land in production until a day or two after feature freeze.  Perhaps we should go ahead with the installer change to activate multiarch anyway, since the ...
[15:15] <cjwatson> ... Launchpad work is "only" a bandwidth reduction exercise?
[15:15] <cjwatson>  * Good news: it only took about half a day to set up a Launchpad development VM, and most of that was waiting for downloads.  It's not as hard as I remember it being.
[15:16] <cjwatson> Working on mountall for /run transition, with Steve.  Will review Surbhi's stop-timer branch again once that transition is unstuck.
[15:16] <cjwatson> Kicked off preliminary CD building for 10.04.3.
[15:16] <cjwatson> Working on apt-setup error handling in the case of a non-downloadable local repository key (bug 728710).
[15:16] <cjwatson> Launchpad branch to add Lubuntu tasks has landed, so I'll be working on getting Lubuntu CDs going once we can debootstrap again.
[15:16] <cjwatson> Almost done with home plumbing problems saga of doom, at long last \o/
[15:16] <cjwatson> --
[15:16] <psurbhi> cjwatson, thanks !
[15:16] <psurbhi> i am waiting for the mountall review !
[15:16] <psurbhi> :)
[15:16] <cjwatson> sorry that's taken so long :-/
[15:16] <slangasek> activate multiarch anyway> that seems fair to do now and give a bandwidth hit since it only affects those using the dev release
[15:16] <psurbhi> np
[15:16] <slangasek> as long as we're confident we'll have it really really fixed by beta :)
[15:17] <cjwatson> yeah, the branch is not that painful
[15:17] <cjwatson> although I don't actually have figures for how much it cuts
[15:17] <cjwatson> I should work on that
[15:17] <cjwatson> OK then, I'll pull the switch in the installer if I can say you told me to do it :-)
[15:18] <mvo> what could possible go wrong?
[15:18]  * slangasek gets the asbestos longjohns out of storage
[15:18] <cjwatson> you had them in storage?
[15:18] <slangasek> global warming
[15:18] <cjwatson> you've been away from platform too long
[15:18] <slangasek> heh
[15:18] <slangasek> my turn
[15:18] <slangasek> this week has pretty much been eaten up with bug #807974, development-wise
[15:19] <slangasek> started my long heart-to-heart with the initscripts merge on Friday... been working on it since
[15:19] <slangasek> should actually be in a position to upload initscripts+mountall later today
[15:19] <slangasek> if someone were to have a look at debianutils and see whether we should merge it from unstable, that would knock one prereq off my list
[15:20] <cjwatson> I can do that
[15:20] <slangasek> thanks :)
[15:20] <slangasek> nothing else to report here
[15:20] <slangasek> doko:
[15:21] <doko> - updates and merges: binutils, gcc-4.6, gcc-4.5, gcc-4.4, gcj-4.5
[15:21] <doko> - python 3.2.1 release
[15:21] <doko> - openjdk-7 and openjdk-6 updates, build fixes for powerpc and armel (and sparc)
[15:21] <doko> - some other merges and syncs
[15:21] <doko> - just one MIR
[15:21] <doko> - new installation on a toshiba ac100 (armel)
[15:21] <doko> - integrated some GCC patches upstream
[15:21] <doko> - GCC bug triage
[15:21] <doko> rebuild test not yet launched
[15:21] <doko> done
[15:22] <mvo> software-center: debug/fix hang in piston helper, fix pyflakes issues, SRU for maverick/natty to obstrufucate private PPA details from the log, add some gtk3 specific tests
[15:22] <mvo> apt/python-apt: signature verification work, improve support for compression in python-apt and avoid code duplicatoin, lucid-proposed backport of long-description splitout and xz-compression,
[15:22] <mvo> debdelta: setup prototype for securty deltas on macaroni, waiting for IS for a role-account and a final place, send some patches to debdelta upstream
[15:22] <mvo> software-properties: work on dbus/polkit backend code based on apacheloggers branch, add tests for all the dbus methods (backend now mostly there)
[15:22] <mvo> update-manager: merge gtk3/pygi/gsettings branch, fix tests and upload
[15:22] <mvo> misc: debug/fix upgrade issue with doc-base  (#781076), debug/fix lp-extract-changelogs hang, apt-btrfs-snapshot: fix crash when fstab misses some entries, upload new version, merged gparted, played with livebuild as replacement for ubuntu-vm-builder that the server team wants to deprecate
[15:22] <mvo> EOF
[15:23] <mvo> cjwatson: what do you reckon would it take to write a wrapper that has a similar "ui" as ubuntu-vm-builder, i.e. "ubuntu-vm-builder-using-live-build kvm lucid" and it would build a minimal qcow2 image? or does that not make much sesne at all?
[15:24] <cjwatson> mvo: it's not too hard, make an auto directory and symlink canned config/build/clean scripts into it the way livecd-rootfs does, then call lb config and lb build
[15:24] <cjwatson> mvo: and either patch live-build to add facilities you need (and forward them to Debian, please) or else add hooks in your build wrapper
[15:25] <mvo> cjwatson: that sounds encouraging, I assume I can make it output a raw image that I can then covert to qcow2? or does it do qcow2 natively?
[15:26] <cjwatson> mvo: no native support.  there are various image output options, you should be able to bodge one of them into a useful form yes
[15:26] <cjwatson> 'man lb config'
[15:26] <mvo> great, thanks
[15:27] <slangasek> thanks
[15:27] <slangasek> [TOPIC] Oneiric bugz
[15:27] <MootBot> New Topic:  Oneiric bugz
[15:27] <slangasek> new topic!
[15:28] <cjwatson> you can probably just use '--binary-images none' or something and do it by hand
[15:28] <bdmurray> I just wanted to mention a couple of bugs that have come to light in the past week
[15:28] <slangasek> bdmurray and I were talking this past week about bug tracking for the release, and the conclusion was that it would be useful to have a slot during the weekly meeting to talk about the status of any bugs that might be lingering
[15:28]  * slangasek yields the floor to bdmurray :)
[15:29] <bdmurray> bug 807636 was found while isotesting
[15:29] <cjwatson> I wondered why you assigned that to mvo
[15:29] <cjwatson> though I don't mind if mvo wants it :)
[15:29] <bdmurray> cjwatson: I think it was rather early for me
[15:29] <cjwatson> ah, yeah, you undid that latere
[15:30] <bdmurray> bug 806574 is a regression and targetted to Oneiric
[15:30] <mvo> *puhhh* for a moment I was scared ;)
[15:30] <barry> bdmurray: i'll take that one
[15:31] <bdmurray> barry: great, thanks
[15:31] <bdmurray> and then bug 806543 also found during iso testing
[15:31] <bdmurray> er 806453
[15:31] <bdmurray> bug 806453
[15:32] <slangasek> bdmurray: that's a duplicate of the bug pitti just uploaded for
[15:32] <slangasek> tied to the /run transition
[15:32] <slangasek> bug #807306
[15:33] <bdmurray> slangasek: okay great
[15:34] <bdmurray> what about bug 791134? should it be fixed with pitti's upload too?
[15:34] <slangasek> that bug number looks wrong for it to be a duplicate
[15:34] <slangasek> too old, this issue was just introduced last Thursday
[15:35] <slangasek> oh, wait
[15:35] <slangasek> Debian/sid - so that was the same bug, but in Debian :)
[15:35] <cjwatson>   * Compatibility symbolic links are relative, not absolute.  e.g.
[15:35] <cjwatson>     /var/lock is ../run/lock rather than /run/lock.  This means that if
[15:35] <cjwatson>     you're using a chroot from the host system, you'll always be using
[15:35] <cjwatson>     locations in the chroot, rather than the host, when following the
[15:35] <cjwatson>     links.
[15:35] <bdmurray> right and I just (yesterday) ran into it with oneiric
[15:35] <cjwatson> sysvinit 2.88dsf-13.5
[15:36] <cjwatson> hm, except:
[15:36] <cjwatson>         # Create absolute symlink if not already present.  This is to
[15:36] <cjwatson>         # upgrade from older versions which created relative links,
[15:36] <cjwatson>         # which are not permitted in policy between top-level
[15:36] <cjwatson>         # directories.
[15:36] <cjwatson> so I'm confused
[15:36] <cjwatson> ah yes
[15:36] <cjwatson>   * Revert to using absolute paths in compatibility symlinks in order
[15:36] <cjwatson>     to comply with Policy §10.5 symlink rules. (Closes: #626263)
[15:36] <cjwatson> I guess sbuild needs to cope then?
[15:37] <slangasek> ah, fun
[15:37] <slangasek> I had assumed rleigh knew what he was doing and was going to stick with the not-quite-policy symlinks on purpose
[15:37] <cjwatson> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626826
[15:37] <MootBot> LINK received:  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626826
[15:38] <cjwatson> so we should either merge sbuild, or cherry-pick that change
[15:39] <slangasek> any volunteers to take that merge?
[15:39] <cjwatson> maybe somebody who uses sbuild could do that?
[15:39]  * cjwatson doesn't
[15:39] <barry> i do
[15:39] <slangasek> winner
[15:39] <barry> slangasek: fsvo
[15:40] <barry> is there an lp bug for that?
[15:40] <bdmurray> okay those 3 bugs were all I had for this week - the sbuild one was just something I happened to remember
[15:40] <bdmurray> barry: bug 791134
[15:40] <slangasek> barry: assigned to you, summary comment added
[15:41] <barry> cool
[15:41] <slangasek> barry: ideally we would SRU this as well, for the benefit of anyone who might actually want to use sbuild for building in chroots for a different release than the one they're running :)
[15:41] <cjwatson> ev: could you take the ubiquity console expander bug bdmurray pointed out?
[15:41] <barry> i'll be rebuilding my sbuild environment today, so it'll be a good time to look at it ;/
[15:41] <ev> yup
[15:41] <cjwatson> ta
[15:41] <slangasek> barry: ah, then you'll have ample opportunity to confirm the bug :-)
[15:42] <ev> though I wont touch it until FF. It's not a critical bug, as far as I can tell
[15:42] <cjwatson> no, medium (I think correctly)
[15:42] <ev> indee
[15:42] <ev> d
[15:42]  * slangasek eyes the daily dist-upgrade, getting wedged on sun-java downloads that don't want to complete
[15:43] <slangasek> bdmurray: that all the bugs?
[15:43] <slangasek> um.  worse than "don't want to complete", I just saw the download counter roll backwards
[15:43] <slangasek> mvo: I think I have an update-manager bug to report ;)
[15:43] <bdmurray> slangasek: well not *all* the bugs but the ones that appeared on my radar this week
[15:44] <slangasek> bdmurray: :)
[15:44] <slangasek> [TOPIC] AOB
[15:44] <MootBot> New Topic:  AOB
[15:44] <ev> slangasek: so, out of random curiosity, what are your thoughts on using the Windows NT PAM module in, say, Wubi?
[15:44] <mvo> slangasek: *ick* it rolls *backwards* ?
[15:44]  * ev ducks
[15:44] <slangasek> mvo: yes, it went from 'Downloaded 25.1 MB of 28.7 MB' to 'Dowloaded 24.8 MB of 28.7 MB'
[15:44] <slangasek> mvo: it is now at 'Downloaded 33.1 MB of 28.7 MB' :)
[15:45] <slangasek> 33.4 ... 33.5 ... 33.6 ... 33.5....
[15:45] <slangasek> 33.1...
[15:45] <mvo> hahaa, woah
[15:45] <slangasek> now it's finally decided it's finished :-)
[15:45] <mvo> that is on a amd64, right?
[15:45] <slangasek> ev: so, ah, I would defer to the security team on this
[15:45] <slangasek> mvo: yep
[15:45] <ev> slangasek: well played
[15:46] <ev> it's seemingly the only thing standing between me and single click wubi installations.
[15:46] <ev> so I'm just toying around with the idea
[15:46] <slangasek> ev: there should be an analysis of whether the default hashes used by Windows there are as strong as what we get by default with pam_smbpasswd, which we *do* pull in by default whenever filesharing is turned on
[15:46] <ev> (see: not for oneiric)
[15:47] <ev> to be clear, is there just the one that comes from Microsoft's Services for UNIX, or is there an open source implementation kicking about?
[15:47] <slangasek> ev: however, *I* am not opposed to the idea in principle; I did, after all, implement pam_smbpasswd with its 'migrate' option
[15:47] <ev> yay, that I like to hear
[15:47] <slangasek> oh, I don't know if there's an open source one
[15:47] <slangasek> I thought you had one in mind
[15:48] <slangasek> pam_smbpasswd could do it, if samba were wired up to support reading directly from the Windows database
[15:48] <slangasek> but I don't know the database format
[15:48] <slangasek> I think the person to talk to about this is probably Simo Sorce at Red Hat
[15:48] <slangasek> (Samba Team member)
[15:49] <ev> okay
[15:49] <ev> mind you, I'm not opposed to using Microsoft's
[15:49] <ev> if they wrote it, chances are it works
[15:50] <slangasek> but I'm guessing its license isn't GPL-compatible :-)
[15:50] <ev> pish tosh
[15:50] <ev> neither is Broadcom's
[15:51] <slangasek> but PAM modules we configure by default get intentionally loaded into memory by every authentication-using application on the system, many of which are GPL
[15:51] <ev> ah, damn
[15:51]  * ev shakes his fist at Stallman
[15:52] <slangasek> :)
[15:53] <slangasek> #endmeeting
[15:53] <MootBot> Meeting finished at 10:53.
[15:53] <slangasek> thanks, everyone!
[15:53] <ev> fanks!
[15:54] <barry> thanks!
[15:54] <jhunt_> thx
[17:01] <jibel> hggdh, patrickmw pedro_ bdmurray Ursinha charlie-tca meeting time ?
[17:01] <pedro_> hello
[17:01] <jibel> hello pedro_
[17:01]  * patrickmw waves
[17:01] <patdk-wk> hmm?
[17:01] <bdmurray> oh hai
[17:02]  * pgraner waves
[17:02] <jibel> hggdh, you're chairing today
[17:02] <jibel> you volunteered, remember ?
[17:02] <patdk-wk> oh, wrong channel :)
[17:04] <jibel> I'll do, hggdh to chair next meeting
[17:04] <jibel> #startmeeting
[17:04] <MootBot> Meeting started at 12:04. The chair is jibel.
[17:04] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[17:04] <jibel> [topic] Previous Actions
[17:04] <MootBot> New Topic:  Previous Actions
[17:04] <jibel> no actions from previous meeting.
[17:05] <jibel> [topic] Community Efforts/Testing
[17:05] <MootBot> New Topic:  Community Efforts/Testing
[17:05] <pgraner> jibel, question, I saw a bug day announcement go out with no test in the body of the email, might need a resend?
[17:06] <pgraner> pedro_, sent it out I think
[17:06] <jibel> pedro_ resent it.
[17:06] <jibel> there is a bug in evolution
[17:06] <pedro_> pgraner, it was re sent already, is an evolution bug
[17:06] <bdmurray> I don't thnk the resend went to ubuntu-devel-announce
[17:06] <pedro_> its sending empty body messages...
[17:06] <pgraner> pedro_, cool then it hasn't made it to me yet
[17:06] <jibel> pedro_, did you resent to ubuntu-devel-announce ?
[17:07] <pedro_> jibel, yes
[17:07] <jibel> pedro_, thanks.
[17:07] <pedro_> it was re sent to the same mailing lists
[17:07] <pedro_> looks like evolution really want me to switch to thunderbird :-P
[17:08] <bdmurray> I'll check the moderation queue then
[17:08] <jibel> Last week was Oneiric Alpha2
[17:08] <jibel> You'll find the results at [LINK] https://wiki.ubuntu.com/QATeam/ReleaseReports/OneiricAlpha2TestReport
[17:09] <jibel> not much to add, please read the results and if you have questions just ask.
[17:09] <pgraner> One quick note, I  have had several developers contact me with good words about the testing this cycle
[17:09] <pgraner> specifically:
[17:09] <pgraner> * No critical issues requiring a late respin
[17:09] <pgraner> * No installer issues
[17:09] <pgraner> due to the automated testing
[17:10] <pgraner> all were caught and fixed prior
[17:10] <pgraner> Great work!
[17:10] <pgraner> ..
[17:10] <patrickmw> +1
[17:10] <pedro_> awesome \o/
[17:11] <jibel> yay, that's good to see the result of our testing effort \o/
[17:12] <jibel> Next week, we will test 10.04.3 and there will be no automation.
[17:12] <jibel> there are still some SRUs to verify http://people.canonical.com/~ubuntu-archive/pending-sru.html
[17:12] <patrickmw> 0/
[17:12] <jibel> patrickmw, ?
[17:13] <jibel> patrickmw, We are all ears
[17:13] <patrickmw> I'm glad you mentioned the lack of testing.
[17:13] <patrickmw> Do we have older lucid tests?
[17:15] <jibel> the automated test doesn't run on Lucid and we estimated that it was a lot of work to backport them to lucid for 2 point releases only
[17:15] <patrickmw> the reason I ask is that we will be adding kernel sru tests for LTS.  just wondering if I could add things while I was at it
[17:15] <patrickmw> ok, fair enough
[17:16] <jibel> kernel SRU is a different thing, it has to be done on a very regular basis, next week we'll be testing ISOs that happens every 6 months for an LTS
[17:16] <skaet> o/
[17:17] <jibel> skaet, ?
[17:17] <skaet> would just like to encourage any one with the right hardware and spare cycles to help with the verification.
[17:18] <skaet> There are some old bugs that seem to be lingering in the pending-sru.html list that would be good to get fixed and out with 10.04.3
[17:18] <skaet> thanks.
[17:18] <jibel> indeed. If you're willing to help the first images of 10.04.3 landed today on cdimage.u.c
[17:19] <jibel> only powerpc is available at the moment.
[17:19] <jibel> So keep monitoring http://cdimage.ubuntu.com/lucid/ for other images.
[17:19] <jibel> And to second what skaet said, you don't need to wait next week to start smoketesting the images.
[17:20] <jibel> Still on community testing, but another area: nVidia/ATI proprietary drivers testing.
[17:20] <jibel> We sent a call for testing proprietary graphics driver today.https://wiki.ubuntu.com/X/Testing/ProprietaryDrivers/Oneiric/VideoDrivers
[17:20] <jibel> If you have an nVidia (GeForce 6 or higher) or ATI (R600 or higher) graphics card you can help with testing the drivers in Oneiric and report rthe results to the tracker http://xorg.qa.ubuntu.com
[17:22] <jibel> Any question or comment ?
[17:23] <jibel> [topic] Automated/Systems Testing
[17:23] <MootBot> New Topic:  Automated/Systems Testing
[17:23] <jibel> patrickmw, the floor is yours
[17:23] <patrickmw> = QA Lab =
[17:23] <patrickmw> * Albali is configured as an additional Jenkins slave
[17:23] <patrickmw> * Naartjie is next.  Need access to Remote KVM (appears to be locked.)  I've been in contact with IS about the issue.
[17:23] <patrickmw>  
[17:23] <patrickmw> = Kernel SRU =
[17:23] <patrickmw> * Proposed branch for merge to allow -proposed update testing
[17:23] <patrickmw> * add QRT tests when ppa is complete
[17:23] <patrickmw> * add lucid (updates and proposed)
[17:23] <patrickmw>  
[17:23] <patrickmw> = Ubiquity Testing =
[17:23] <patrickmw> * Pending status on Evan. I've contacted him this week.
[17:23] <patrickmw>  
[17:23] <patrickmw> = Upgrade Testing =
[17:23] <patrickmw> * Albali is ready for Michael to migrate the update test framework.  He is aware and will inform me when he's ready.
[17:23] <patrickmw>  
[17:23] <patrickmw> = DX Testing =
[17:23] <patrickmw> * Alex provided a list of packages with build-time tests.
[17:23] <patrickmw> * We will be having a further discussion on tests with specific graphics hardware requirements
[17:23] <patrickmw>  
[17:24] <patrickmw> = IPv6 Testing =
[17:24] <patrickmw> * Working with Foundations team.  Test plan is complete.
[17:24] <patrickmw> * Stefane is completing work on the framework.
[17:24] <patrickmw>  
[17:24] <patrickmw> = Other projects =
[17:24] <patrickmw> * Wubu - jibel is the owner
[17:24] <patrickmw> * Boot metrics - pending
[17:24] <patrickmw> * Ubuntu packages - pending
[17:24] <patrickmw>  
[17:24] <patrickmw> questions?
[17:24] <patrickmw> ..
[17:25] <hggdh> I have a merge to propose for the server mail test; will do it today
[17:25] <patrickmw> thanks
[17:25]  * hggdh begs pardon, had a bit of an emergency at home
[17:26] <jibel> no question, moving on
[17:26] <jibel> [topic] Engineering Team Bug Status  pedro_ bdmurray Ursinha
[17:26] <MootBot> New Topic:  Engineering Team Bug Status  pedro_ bdmurray Ursinha
[17:26] <pedro_> As you might know already we're having a bug day for the GNOME Control Center  tomorrow https://wiki.ubuntu.com/UbuntuBugDay/20110714
[17:27] <pedro_> the purpose of that bug day is to triage + fix bugs on the new control center
[17:27] <pedro_> rodrigo who is the maintainer in both Ubuntu and at the upstream project is going to be around to help
[17:27] <pedro_> so if you have questions just ask those at #ubuntu-bugs or #ubuntu-desktop
[17:28] <pedro_> remember, the whole day tomorrow your timezone
[17:28] <pedro_> ..
[17:28] <bdmurray> added bug reporting guidelines for ubuntu-meta
[17:28] <bdmurray> fsys-tarfile-error apport package bug report cleanup
[17:29] <bdmurray> apt branch blocking of fsys tarfile error package install failures
[17:29] <bdmurray> updated ubiquity apport package hook to ask permission before adding debug log and block SQUASHFS error bug reports
[17:29] <bdmurray> review and approval of 2 new Ubuntu Bug Control members
[17:29] <bdmurray> added in iso-testing bug reports to the package status pages
[17:29] <bdmurray> udw class prep and  presentation regarding working with apport bugs
[17:30] <bdmurray> I also fixed a bug in pm-utils that was preventing things from inhibiting suspend - bug 665651
[17:31] <bdmurray> However, this means that some things like a script in toshset would inhibit suspend all the time
[17:31] <bdmurray> So I fixed that too
[17:31] <bdmurray> Point being if you see any weird suspend regression bugs let me know
[17:31] <bdmurray> ...
[17:32] <Ursinha> I've been basically boostraping in the ubuntu server team
[17:32] <Ursinha> am working to give them the basics, such as an SRU report for the packages we care about
[17:33] <Ursinha> reading what we already have, and modifying for us
[17:33] <Ursinha> ..
[17:34] <Ursinha> btw, if any of you are using scripts to generate reports that aren't in the BugSquad page, please, let me know
[17:34] <Ursinha> ..
[17:35] <jibel> Do you reused this report http://people.canonical.com/~chucks/SRUTracker/ to tracker server SRUs?
[17:35] <Ursinha> jibel: it's not working, just fixed what was stopping that from producing the reports
[17:36] <jibel> ok thanks
[17:36] <jibel> any other question ?
[17:36] <Ursinha> thanks for pointing that anyway, jibel
[17:37] <jibel> [topic] Other Topics
[17:37] <MootBot> New Topic:  Other Topics
[17:37] <jibel> any other topic you'd like to talk about ?
[17:38] <jibel> last topic then
[17:38] <jibel> [topic] Chair Selection
[17:38] <MootBot> New Topic:  Chair Selection
[17:38] <jibel> hggdh you volunteer again ?
[17:38] <hggdh> jibel: yes, I do :-)
[17:39] <jibel> Thanks hggdh , I'll be prepared next time then!
[17:39] <jibel> 3
[17:39]  * charlie-tca made it, finally
[17:39] <jibel> charlie-tca, want to add a word before ending the meeting ?
[17:40] <charlie-tca> Can't think of anything, other than we all know desktop images for oneiric are broken for a week now, right?
[17:40] <charlie-tca> .
[17:40] <charlie-tca> ..
[17:41] <jibel> Yes all desktop images are broken for a week. I don't remember the package that causes this though.
[17:41] <jibel> Thanks all for attending
[17:41] <jibel> #endmeeting
[17:41] <MootBot> Meeting finished at 12:41.
[17:41] <charlie-tca> jibel: that /run/udev thingy
[17:41] <charlie-tca> I think
[17:41] <jibel> charlie-tca, oh yeah the /run transition
[17:42] <jibel> it's part of it.
[17:42] <charlie-tca> I just keep seeing people surprised to know they have been broken for so long, when they should have known already
[17:45] <Ursinha> charlie-tca: what do you mean by broken? not installing? borked X?
[17:45] <charlie-tca> There has not been a new image since july 5
[17:45] <charlie-tca> as in, none
[17:46] <charlie-tca> They can't even create one
[17:47] <Ursinha> oh
[17:48] <jibel> Ursinha, and users who upgraded their system ended up with no keyboard and mouse. pitti fixed it on monday
[17:48] <Ursinha> jibel: I proved that bug myself :)
[17:48] <Ursinha> last update fixed that though
[17:48] <charlie-tca> But we still have no desktop images
[17:49] <Ursinha> hm, that's weird
[17:49] <rsalveti> https://code.launchpad.net/~rsalveti/ubuntu/oneiric/base-files/run-transition/+merge/67444
[17:49] <rsalveti> this is related with the bootstrap issue
[17:49] <rsalveti> but still not yet applied :-(
[17:49] <Ursinha> that's really bad
[17:50] <Ursinha> jibel: is this the bug preventing images to be generated?
[17:50] <Ursinha> if so, I wonder why the fix wasn't applied yet
[17:51] <rsalveti> probably waiting slangasek to get the proper fix at the sysvinit package
[17:51] <rsalveti> but still, we should fix it asap so we can at least generate images again
[17:51] <slangasek> I expect to land this all today
[17:51] <slangasek> just have a few finishing touches to add
[17:52] <slangasek> not being able to bootstrap is messy; not understanding what we've done and having bugs drag out until post-release would be worse :)
[17:52] <Ursinha> ah
[17:52] <jibel> +1
[17:53] <Ursinha> I thought the problem was well known, so as the workaround proposed by the merge
[17:53] <rsalveti> that was the quick workaround, until the proper transition changes were in place
[17:53] <slangasek> it's well *known*, but it's difficult to understand all the implications
[17:54] <slangasek> so since the migration has been Real Soon Now<tm> for 2 days, no one was willing to upload the workaround :)
[17:54] <Ursinha> right
[17:54] <slangasek> (i.e., cjwatson declined when I nudged him, which is sufficient justification for me to not try to talk anyone else into it ;)
[17:54] <charlie-tca> +1
[19:17]  * Kreative` is away: Away