[15:38] <ma10> @now
[16:10] <persia> Erm.  That's just not right.
[16:10] <persia> Anybody from the news team around?  Could you populate the calendar a bit?  I *know* there's lots of meetings during the next 30 hours or so.
[17:57] <heno_> Hey everyone
[17:57]  * pedro_ waves
[17:57] <intellectronica> 'alo
[17:57] <LaserJock> hi heno_
[17:57] <heno_> I may have to run in a few minutes
[17:57] <heno_> hey LaserJock
[17:58] <bdmurray> greetings
[17:58] <heno_> pedro_: could you chair the meeting? - in case I need to dash off
[17:58] <pedro_> heno_: yes no problem
[17:58] <LaserJock> pedro_: I think we need to send the meeting emails earlier
[17:59] <LaserJock> it'd be nice if we had the agenda set by Monday and the email sent out Tuesday I think
[17:59] <LaserJock> to allow people who don't normally come but may be interested in specific agenda items
[17:59] <heno_> should we schedule meetings when there are no suggested agenda items?
[17:59] <pedro_> LaserJock: indeed, but we didn't have an agenda till today morning, that's why i didn't send it yesterday
[18:00] <LaserJock> heno_: well, I would propose that unless we have a full agenda a "spec status" roll call would be good to do each meeting
[18:00] <heno_> we may have some standing items of course like, indeed
[18:00] <LaserJock> it's often good if we don't have big agenda items :-)
[18:00] <sbeattie> hey
[18:00] <bdmurray> Or a round table
[18:00] <heno_> also looking toward testing of the next milestone and SRU status
[18:01] <LaserJock> but it's also good to get everybody together, talk about the week
[18:01] <ara> hello
[18:01] <heno_> yay, let's do a round table!
[18:01] <pedro_> yeah
[18:01] <pedro_> ok everybody is here, let's start
[18:01] <pedro_> #startmeeting
[18:01] <LaserJock> I think it's especially nice to find out about blockers :-)
[18:01]  * pedro_ kicks the bot
[18:02] <heno_> I'll go first since I may have to run
[18:02] <davmor2> hello
[18:02] <pedro_> Welcome to the Ubuntu QA Meeting the Agenda for today is at https://wiki.ubuntu.com/QATeam/Meetings
[18:02] <heno_> I was at a Canonical distro team leads sprint all last week
[18:03] <heno_> we discussed the usual admin stuff but also some Ubuntu QA stuff
[18:03] <stgraber> hey
[18:03] <heno_> There is broad agreement that we will ramp up the focus on quality in the releases to come
[18:03] <heno_> I can write more when I get the notes
[18:04] <LaserJock> that's always a good thing? :-)
[18:04] <LaserJock> s/?/!/
[18:04] <heno_> of course!
[18:04] <heno_> oh, not '?'
[18:04] <heno_> heh
[18:04]  * LaserJock plays "punctuation jumble" today
[18:04] <heno_> on monday I was at an LP team sprint as well
[18:05] <heno_> the numbers that we discussed for the LP bugs priorities were presented
[18:05] <heno_> it looks like they have a good process for taking that forward
[18:05] <davmor2> cool :)
[18:06] <heno_> they will decide on actual priorities this week
[18:06] <LaserJock> excellent
[18:06] <pedro_> yay
[18:06] <heno_> ok, that's it from me!
[18:06] <pedro_> thanks
[18:06] <pedro_> ok the next point i see is
[18:06] <pedro_> Ubuntu Developer Week preparations
[18:07] <pedro_> the Ubuntu Developer Week starts next week
[18:07] <heno_> That's just pointing out https://wiki.ubuntu.com/UbuntuDeveloperWeek
[18:07] <pedro_> and there's a few talks from the members of the team
[18:08] <pedro_> anyone wants to give a brief overview about their talk?
[18:08] <LaserJock> I was pleasantly surprised to see Ara scheduled
[18:08] <heno_> and it looks like there are no more open slots
[18:08] <pedro_> bdmurray, ara ?
[18:08] <LaserJock> go ara go! ;-)
[18:08] <ara> pedro_: ok, I'll go
[18:09] <pedro_> rock
[18:09] <ara> I will be presenting the automated testing library that we've been working on
[18:09] <ara> what is exactly, how to use it, etc.
[18:10] <ara> i will be completing the docuementation at https://wiki.ubuntu.com/Testing/Automation/LDTP/HowToUseTestingLibrary
[18:10] <ara> before the session, so people will be able to have some reading after it
[18:11] <ara> what I would like to achieve from the session is making people more involved in testing and more specifically in automated testing
[18:11] <ara> only some very basic python knowledge is required
[18:11] <LaserJock> ara: very nice
[18:12] <pedro_> nice! looking forward to it
[18:12] <pedro_> bdmurray: may you tell us a bit about the launchpad hacks session?
[18:12] <LaserJock> ara: so are you going to be able to go through how people can contribute test scripts?
[18:13] <ara> LaserJock: yes, how to contribute with new scripts that use the library; but not how to extend the library
[18:13] <ara> LaserJock: if I get people willing to contribute also to extend the library, it will be great
[18:14] <bdmurray> pedro_: I plan on talking about recent features added to bughelper / python-launchpad-bugs.  Additionally, I want to talk about all the scripts in the launchpad-gm-scripts project and how they might help you use launchpad.
[18:15] <LaserJock> next time we should get a QA Team overview session
[18:15] <pedro_> cool!
[18:15] <heno_> should we continue the round table?
[18:16] <bdmurray> If so there's one thing I wanted to mention...
[18:18] <bdmurray> I've written a script that checks needs-packaging bugs to see if they are already packged in debian or ubuntu and checks to see if there is a request to have them packaged in debian
[18:18] <bdmurray> I plan on running this on qa.ubuntu.com soon and announcing it
[18:19] <bdmurray> However, one way we can help is ensuring the needs-packaging bugs follow a specific format for the title
[18:19] <bdmurray> for example: [needs-packaging] softwarename ....
[18:19] <heno_> how does it find the package in the archive?
[18:19] <bdmurray> So if you happen to see any that don't follow that convention please modify the title.
[18:19] <intellectronica> bdmurray: why do you want to use the title?
[18:20] <bdmurray> heno_: rmadison
[18:20] <ara> bdmurray: one thing that is unclear from the documentation is that instead of "naming [needs-packaging]" the document reads "tagging [needs-packaging]"
[18:20] <intellectronica> bdmurray: rather than a tag, that is
[18:20] <bdmurray> intellectronica: so it is distinguishable in a list of bugs - both are done
[18:20] <bdmurray> ara: okay, I'll update the documentation
[18:21] <bdmurray> Ideally they'll be tagged needs-packaging and have that prepended to the title
[18:21] <LaserJock> hmm, but how reliable would the title be?
[18:22] <bdmurray> LaserJock: I've modified ~134 needs-packaging bugs which is >10%
[18:22] <bdmurray> So I think it has been pretty successful
[18:22] <LaserJock> bdmurray: you've modified the title of 134?
[18:23] <LaserJock> what I meant was that by definition we don't have a package name for needs-packaging bugs
[18:23] <bdmurray> LaserJock: no, I've linked to upstream bug watches, marked as duplicate or Fix Released 134 bugs
[18:23] <LaserJock> so how do you go from a bug title to finding if it's in the archive?
[18:23]  * heno_ is afk
[18:24] <bdmurray> I assume the 2nd word in the title is the name of the software needing packaging
[18:25] <bdmurray> And that's where help would be useful - ensuring the bug titles follow that convention
[18:25] <LaserJock> bdmurray: right but quite often that's not a great mapping to package name
[18:25] <LaserJock> but consistency is usually a good thing :-)
[18:26] <LaserJock> I'm just worried that if we take a scripted list we'll could have a significant amount of false positives
[18:26] <LaserJock> so then we'd be triaging anyway
[18:27] <davmor2> bdmurray: so bug title Intrepid: xapian doesn't work  and intrepid: bunnys have big ears is cool for you?
[18:28] <davmor2> where bunnys needs packaging sorry
[18:29] <bdmurray> davmor2: heh
[18:29] <hggdh> LaserJock, this is one reason why we would still need the tag -- titles may not work always
[18:30] <LaserJock> hggdh: that's the whole reason why I made the tag in the first place ;-)
[18:30] <hggdh> and this is another reason why we need more tags ;-)
[18:30] <bdmurray> and if a particular ubuntu bug has too many results just skip it or modify the title and it'll get processed in the next run of the script
[18:30] <davmor2> bdmurray: sorry talking at cross purposes missed the first bit just played catch up
[18:31] <LaserJock> bdmurray: ok, so what does your script output?
[18:31] <LaserJock> the bugs where the software exists in Debian/Ubuntu?
[18:31] <bdmurray> The output of rmadison or links and titles of debian bugs
[18:32] <LaserJock> hmm, that just seems so error prone
[18:34] <pedro_> Any other issues?
[18:35] <LaserJock> well, the Testing Day thing is still up in the air
[18:35] <LaserJock> it'd be nice to get something nailed down for that
[18:37] <pedro_> Yes, LaserJock can you send a reminder about it to the ubuntu-qa list ?
[18:37] <LaserJock> k
[18:37] <davmor2> also before I need to dash off the bugs I've come across whilst smoke testing I've collated here https://wiki.ubuntu.com/Testing/DailySmoke/bugs I won't be around next week so if someone can quickly blitz through them and see if there fixed early next week that would be great
[18:37] <pedro_> thanks you
[18:40] <pedro_> alright, thanks davmor2
[18:40] <pedro_> ok it seems we don't have anything else
[18:40] <intellectronica> just a quick one
[18:40] <pedro_> intellectronica: go ahead
[18:41] <intellectronica> has there been any progress on preparation for that bug status migration?
[18:41] <pedro_> intellectronica: i haven't had the time yet to prepare the wiki page, but ill need to do it soon
[18:42] <intellectronica> cool. let me know if you need any help
[18:42] <pedro_> yup , thanks
[18:42] <pedro_> ok , let's wrap then
[18:42] <pedro_> thanks everybody
[18:43] <intellectronica> thanks, pedro_
[18:43] <ara> thanks
[18:43] <bdmurray> thanks
[18:44] <sbeattie> thanks everyone
[19:42] <jjesse> @schedule detroit
[22:56]  * asac first
[22:56] <asac> hi
[22:56] <evand> hi
[22:56] <liw> hi
[22:56] <james_w> hi all
[22:57] <ArneGoetje> morning
[22:57] <calc> hi
[22:57] <cjwatson> evening
[22:58]  * ogra waves
[22:59]  * slangasek waves
[23:01] <cjwatson> bryce: ping?
[23:03] <cjwatson> guess not; let's move on without him for now
[23:03] <bryce> hi
[23:03] <cjwatson> aha
[23:03] <cjwatson> ok, so feature freeze is at some time I'm not entirely certain of, but at any rate within the next day
[23:04] <cjwatson> so now's a good time to look over our team's progress and see what needs to be deferred and what might want exceptions from the release team
[23:04]  * ogra hopes late
[23:04] <james_w> 5 minutes ago I thought
[23:04] <slangasek> 0000 UTC
[23:04] <slangasek> which by my clock leaves us all with 2h :)
[23:04] <cjwatson> I heard COB Wednesday, though personally I'd been shooting for COB Thursday; but I shouldn't imagine a few hours will make a whole lot of difference either way
[23:05] <ogra> slangasek, eeek
[23:05] <james_w> ah, I fail at timezones yet again
[23:05] <cjwatson> so, I asked for a one-line summary of each of your feature goals (something of the form "name of goal: where it's at" would be fine)
[23:06] <cjwatson> how about we go in reverse order, since ogra was expressing concern
[23:06] <cjwatson> ogra:
[23:06] <slangasek> (cjwatson: there was apparently a precedent in the wiki that freezes start at 0000UTC on the given day; we diverged from this for hardy, reinstated now for intrepid, sorry to catch people flat-footed)
[23:06] <ogra> well, still busy getting the latest ltsp upstream changes in
[23:06] <persia> According to my clock, FF is in 114 minutes
[23:07] <cjwatson> slangasek: there were older precedents yet that were different again, of course ;-)
[23:07] <slangasek> heh
[23:07] <cjwatson> we've gone through various interpretations
[23:07] <ogra> my only left goal for intrepid was compcache: implemented and running fine
[23:07] <ogra> (just getting it into ltsp)
[23:07] <cjwatson> that was certainly the only major item
[23:08] <cjwatson> I'm very pleased with how memory use has come out so far on the desktop CD, and I gather there's more room for tweakage
[23:08] <ogra> yeh, definately
[23:08]  * ogra is hoping for 24M ltsp client support
[23:08] <cjwatson> ogra: edubuntu-menus-completion and local-content-filter deferred, I take it?
[23:08] <ogra> yeah
[23:08] <cjwatson> I thought that was likely
[23:09] <ogra> and though i'm likely moving teams now, i'D still like to go after the content filter stuff
[23:09] <ogra> (trying to get to that since the sydney UDS where i had to take edubuntu to actually get the spec :P )
[23:10] <slangasek> heh :)
[23:10] <cjwatson> ogra: on that note, remind me to give you a ring tomorrow
[23:10] <ogra> oki
[23:10] <cjwatson> doko is on holiday
[23:11] <cjwatson> of his feature goals, OpenJDK seems pretty happy at this point barring a few glitches the server team would like to be cleared up
[23:11] <cjwatson> Python 3 was only ever preparation for the future
[23:11] <cjwatson> TheMuso:
[23:11] <TheMuso> dmraid: Complete bar no event monitoring due to broken code and incomplete upstream tarballs.
[23:11] <TheMuso> desktop a11y review: Deferred, dmraid took more time than expected.
[23:11] <doko> Hola
[23:12] <cjwatson> doko: oh, hiya
[23:12] <TheMuso> audio: due to the kernel fuss nothing has been uploaded yet, although things are almost ready on my end, just need to test check and upload alsa pieces.
[23:12] <TheMuso> pulseaudio I'd rather PPA test, and if people really want it, we FF for it.
[23:12] <cjwatson> TheMuso: though dmraid not yet promoted to main - I'll get to that before the deadline
[23:12] <TheMuso> cjwatson: Ok no problem.
[23:13] <cjwatson> right, for those who haven't noticed, the kernel team is pretty set on trying out 2.6.27, but acknowledges the regression risk so we're going to be pretty careful about it
[23:13] <TheMuso> I doubt I can get all of alsa done before FF, but I'll see...
[23:13] <cjwatson> https://wiki.ubuntu.com/KernelTeam/2.6.27-kernel-plan is the plan and timeline
[23:13] <asac> TheMuso: can we at least get a fix for the also through pulseaudio by default thing?
[23:13] <cjwatson> we're going to have to switch up to .27 in intrepid in order to get certification testing done, but that's not necessarily final
[23:13] <asac> TheMuso: otherwise we will end up with flash blocking sound device
[23:14] <asac> TheMuso: i know that the current fix isnt kde compatible.
[23:14] <TheMuso> asac: Yes, I need to reread up on everything to work out what exactly has to be done but yes, that is regardless of pulse version
[23:14] <asac> but maybe that should be solved on a package base somehow (if we cannot find a real solution)
[23:14] <asac> TheMuso: ok. as long as you keep in line tha tthis is really a big show stopper and we need a solution i am happy ;)
[23:15] <asac> s/in line/in mind/
[23:15] <cjwatson> TheMuso: do you have some skeleton disk images that people could use in a vm to do basic dmraid testing?
[23:15] <TheMuso> cjwatson: Yes, but thats not really useful.
[23:15] <cjwatson> something of the form "create zero-filled images, and run this dd command"
[23:15] <TheMuso> Other than testing whether everything fits together.
[23:15] <cjwatson> I would find it very useful to be able to try out the installer and suggest possible improvements
[23:15] <TheMuso> but yes, I do have images.
[23:16] <cjwatson> 23:10 <cjwatson> doko is on holiday
[23:16] <cjwatson> 23:11 <cjwatson> of his feature goals, OpenJDK seems pretty happy at this point barring a few glitches the server team would like to be cleared up
[23:16] <cjwatson> 23:11 <cjwatson> Python 3 was only ever preparation for the future
[23:16] <cjwatson> TheMuso: thanks
[23:16] <cjwatson> doko: anything you want to add? just a very quick run-down
[23:16] <TheMuso> cjwatson: I'm going to blog/post to devel about dmraid anyway, so I will put the images up somewhere for people to download.
[23:16] <cjwatson> TheMuso: great, thanks
[23:17] <doko> cjwatson: I will upload python3 next week, including with a few modules how python3 modules sould be packaged.
[23:17] <doko> I didn't see any critical reports about OpenJDK
[23:18] <cjwatson> the server team wanted to get bugs 261847 and 249178 cleared up
[23:18] <doko> python3 should go to main however, because we want to build modules from one source package
[23:18] <slangasek> that's going to bloat the size of all the python module packages again?
[23:18] <doko> 261847 seems to be controversial
[23:19] <slangasek> I don't see how that can be justified as a post-FF change
[23:19] <doko> slangasek: no, not the binary ones, we'll have python3-XXX binaries
[23:19] <slangasek> hmm, breaking the python policy instead, ok... :)
[23:19] <cjwatson> you can't have the same source used by both python 2 and 3, to a good first approximation
[23:20] <doko> 249178 should be uploaded
[23:20] <cjwatson> so this is really something the python policy failed to predict :)
[23:20] <slangasek> well, ouch
[23:20] <doko> not breaking, but changing.
[23:21] <cjwatson> doko: 249178 is a two-parter, I understand: one using -headless, and one being a recommends change that I understand is disputed
[23:21] <cjwatson> they seem quite upset about all the X libraries being pulled in
[23:22] <cjwatson> I didn't want to overrule you in your absence; in any case this all seems to be under the bug-fix heading
[23:22] <doko> well, yes, maybe we could drop this recommend, now that we have java-gcj-compat and java-gcj-compat-hl. I'll do this next week
[23:22] <doko> I mean: dropping the recomend of libgcj9-0-awt in libgcj9-0
[23:23] <cjwatson> doko: thanks for the update; we'd best move on, as time is pressing
[23:23] <cjwatson> liw:
[23:23] <liw> CleanupCruft: package almost ready, gui sucks but works, need to find how to do root from gui
[23:23] <liw> DebianPolicyInDocbook: ignored
[23:23] <liw> FastLsbRelease: ignored
[23:23] <liw> GetRidOfPythonCentralAndSupport: not ready, lots of work needed
[23:23] <liw> GobbyServerPersistentState: my patch works, upstream now maintains package and has corresponding patch (which I should review)
[23:23] <liw> LintianHarness. ignored
[23:23] <liw> NoFsckAtBoot: deemed semi-impossible, but ubuntu-devel(-discuss) has had similar discussions
[23:23] <liw> PythonProfilingTool: playing with Heapy (it does work!), but no concrete results
[23:23] <liw> SuperPiuparts: deferred
[23:24] <cjwatson> perhaps somebody could help liw out with the last bits needed for cleanup-cruft
[23:24] <asac> what is needed?
[23:24] <james_w> policykit?
[23:25] <liw> should I run gksu (what update-manager seems to do currently) or go straight for policykit?
[23:25] <asac> ah ... root from gui ;)
[23:25] <slangasek> AIUI we're well on the path for transitioning to policykit, so better if new stuff uses that?
[23:25] <james_w> liw: policykit, though it may require architecture changes
[23:26] <james_w> and may require frustration
[23:26] <liw> ok, policykit it is (unless it looks too difficult, in which case I'll go for gksu, call it a bug, and fix it to use policykit later...)
[23:26] <TheMuso> Policykit please, for accessibility reasons.
[23:26] <TheMuso> gksu is not an option. :p
[23:27] <james_w> I know pitti recently converted to policykit, so he may be able to help, and I have a basic knowledge, so I'll help if I can
[23:27] <cjwatson> pitti is on holiday at the moment
[23:27] <liw> james_w, thanks, that'll be helpful
[23:27] <cjwatson> as is, I gather, most of the desktop team :P
[23:28] <cjwatson> liw: thanks, better to get system-cleaner into the archive while a bit suboptimal than to leave it until it's too late; we still have time for bug-fixing and polishing provided the basic functionality works
[23:28] <liw> cjwatson, ack
[23:28] <cjwatson> james_w: it's been a while since we talked about UDD. What's the good word?
[23:29] <james_w> I've got bzr-builddeb 2.0 in bzr since about an hour, that has the features I think we need for Intrepid.
[23:29] <james_w> I'd love a sponsor (perhaps for Debian as well, but that's less important)
[23:30] <james_w> if not I can get an FFe and have my usual sponsor upload
[23:30] <cjwatson> I don't see it on https://code.edge.launchpad.net/bzr-builddeb ?
[23:30] <james_w> the rest is not bound by feature freeze, and hasn't moved in the last couple of weeks
[23:30] <asac> bzr http mirror syncs are broken i think
[23:31] <cjwatson> hmm, worked for me earlier today
[23:31] <asac> strange. then thats just affecting the mozillateam branches ;)
[23:31] <james_w> cjwatson: I also tried to upgrade the alioth branch that it mirrors from at the same time, so there may be a delay
[23:31] <asac> (but havent checked today)
[23:31] <james_w> http://bzr.debian.org/pkg-bazaar/bzr-builddeb/trunk if anyone is interested
[23:32] <slangasek> interested, but otherwise occupied at the moment
[23:32] <cjwatson> james_w: I'll be up for a little while after the meeting, and can sponsor
[23:32] <james_w> cjwatson: great, thanks
[23:32] <cjwatson> bzr: ERROR: No repository present: "http://bzr.debian.org/pkg-bazaar/bzr-builddeb/trunk/"
[23:32] <cjwatson> EHOSEDBRANCH
[23:32] <james_w> cjwatson: just fixed that, there's a bug in bzr I'll report
[23:33] <slangasek> not EHOSEDHOSTING?
[23:33] <slangasek> (I can't seem to get http transport to work for bzr.debian.org for my stuff, maybe I'm doing it wrong)
[23:33] <cjwatson> slangasek: I shall withhold my comments on the delays involved in getting new branches created on bzr.d.o
[23:33] <james_w> slangasek: try nosmart+http://
[23:33] <james_w> slangasek: *another* bzr bug, fixed in 1.6
[23:34] <james_w> which leads me to
[23:34] <slangasek> james_w: hum, ok :/
[23:34] <james_w> bzr* updates: all lined up as sponsored sync requests, thanks to LaserJock and jelmer. Probably bugs to fix in 1.6, but we definitely want its features. We shou
[23:34] <james_w> ld evaluate 1.7 in 3 weeks.
[23:34] <james_w> slangasek: assuming it's the bug I think it is.
[23:34] <slangasek> james_w: I don't suppose we'll get 1.6 into lenny...?
[23:34] <slangasek> (I imagine not)
[23:34] <cjwatson> just about every problem I've run into in the last couple of weeks has been "fixed in 1.6"
[23:34] <james_w> slangasek: it's in experimental, but no-ones pushing for it
[23:34] <cjwatson> (including the ones that had nothing to do with bzr)
[23:35] <slangasek> cjwatson: fwiw, I haven't had problems with getting bzr setups done for bzr.d.o
[23:35] <james_w> slangasek: I should investigate backporting the fix.
[23:35] <james_w> 1.6 was a real pain of a release, I think it may have reached 4 months.
[23:35] <james_w> pretty bad for a monthly release project
[23:37] <james_w> the rest of my list:
[23:37] <james_w> font-selector: nowhere, sorry.
[23:37] <james_w> lvm .39: done, thanks to TheMuso.
[23:37] <james_w> mono-tools: still needs MIR for webkit-sharp, though could be sponsored as-is I
[23:37] <james_w> believe.
[23:39] <cjwatson> james_w: ok, thanks
[23:39] <cjwatson> evand:
[23:39] <evand>  * usb-installer-images: Mostly finished.  I just need to figure out
[23:39] <evand> why an io_watch isn't promptly firing, polish the code and UI, and
[23:39] <evand> pick a name (suggestions welcome).  This will be done in time for the
[23:39] <evand> feature freeze cutoff Thursday.
[23:39] <evand> (written before the above conversation)
[23:39] <evand>  * dvd-performance-hacks: Mostly done.  Just need to merge in my
[23:40] <evand> ubiquity changes and triggerize packages.
[23:40] <evand>  * ubiquity-visual-refresh:  The partition bar work has been committed
[23:40] <evand> to ubiquity trunk.  I did not manage to coordinate the slideshow work
[23:40] <evand> in time and will have to defer that (though I'll continue working with
[23:40] <evand> the art and documentation team to obtain the required media for it
[23:40] <evand> during the remainder of the 8.10 cycle).  I am going to apply for a
[23:40] <evand> feature freeze for the timezone map changes for over the weekend as
[23:40] <evand> I'm having some difficulty with rsvg and locating the mouse within a
[23:40] <evand> particular time zone.  If the work fails to produce effective results,
[23:40] <cjwatson> slangasek: the usb installer stuff is largely (afaik) a new package, so I think the regression risk is pretty low; can we manage the one-day slip there?
[23:40] <evand> I will work to fix the remaining usability bugs in the previous
[23:40] <evand> timezone map.
[23:41] <slangasek> cjwatson: yes
[23:41] <evand> thanks
[23:41] <cjwatson> evand: if you could push the ubiquity branch for dvd-performance-hacks somewhere, I can have a look at it for you
[23:41] <TheMuso> Speaking of slips, I can get alsa uploaded today, but it won't all be before FF. Is this ok?
[23:42] <liw> /msg evand name suggestion for the usb thing: gloffod (glorious freedom from optical disks)
[23:42] <evand> cjwatson: will do
[23:42] <doko> james_w: pitti and I will clean up MIRs next week
[23:42] <slangasek> TheMuso: what part is going to be past FF?
[23:42] <james_w> doko: great, I'll try and get it written before then
[23:42] <evand> thanks liw, any other suggestions?
[23:42] <TheMuso> slangasek: Getting lib/utils/plugins in.
[23:43] <cjwatson> evand: I'm looking forward to having a look at the partition bar work; you should blog about it :)
[23:43] <evand> (can be mailed so we don't eat up time here)
[23:43] <slangasek> TheMuso: hmm, you said it won't /all/ be before FF... will /any/ of it be before FF? :)
[23:43] <evand> cjwatson: blog?  I don't think I've done that since Summer of Code ;)
[23:43] <cjwatson> yes, I know ;-)
[23:43] <asac> slangasek: i think he ment that this upload will take a few more hours
[23:43] <asac> (but thats just what i read from it)
[23:43] <TheMuso> slangasek: lib likely will be yes.
[23:43] <asac> oh ok ;)
[23:44] <slangasek> TheMuso: ok.  yes, that'll be alright.
[23:47] <cjwatson> on my own bits:
[23:47] <cjwatson> recommends-by-default: germinate updated and all seems to be working, although some people have requested the ability to exempt certain recommendations from CD building. We may be able to do something about tha
[23:48] <cjwatson> t.
[23:48] <cjwatson> splitting server and mobile into separate branches and metapackages: not done, will probably wait for archive-reorganisation.
[23:48] <cjwatson> archive-reorganisation: call tomorrow morning with Mark to iron out some details. I think we have high-level agreement though and it's on the LP 3.0 plan.
[23:48] <cjwatson> policy-and-standards: initial version of Ubuntu policy uploaded; need to reinstate pristine debian-policy and repackage but that's no big deal.
[23:48] <ogra> recommends-by-default, any idea what to do with the lilo dep of linux-image-* ?
[23:48] <cjwatson> also been helping out the server team with some installer bits, but I think my end is done and any FFEs they need are their business :)
[23:49] <slangasek> ogra: I think that's wrong under the definition of Recommends and should be dropped?
[23:49] <TheMuso> 5~/c
[23:49] <ogra> slangasek, well, lilo seems to be still wanted ...
[23:49] <cjwatson> you can also use --no-install-recommends as a stopgap measure
[23:49] <cjwatson> it's not appropriate as the first alternative
[23:49] <ogra> yeah, thats what i switched ltsp to now
[23:49] <slangasek> oh, it's linux-image-* that was Recommending lilo?
[23:49] <cjwatson> yes
[23:49] <ogra> since my chroots just explode with recommends ...
[23:49] <slangasek> yeah, shouldn't be the first one, anyway
[23:50] <ogra> right and lilo in a chroot isnt really fun :)
[23:50] <cjwatson> for minimal chroots I think --no-install-recommends is entirely appropriate
[23:50] <cjwatson> they aren't the usual case
[23:50] <ogra> i was fearing i miss anyhing ..
[23:50] <ogra> but it seems to stil work fine
[23:51] <ogra> wont be the caes if we start to rely on recommends
[23:51] <ogra> *case
[23:51] <cjwatson> if we follow the definitions properly, it should be fine
[23:51] <slangasek> right; for a minimal chroot, --no-install-recommends is precisely how one finds out if a recommends should've been a depends instead :)
[23:52] <ogra> heh
[23:52] <cjwatson> calc:
[23:52] <calc> ok
[23:52] <calc> OOo 3.0 rc1 is delayed again until sept 1
[23:53] <calc> i am working on OOo 3.0 packaging split and hope to have some debs in PPA by the end of the week (maybe not all packages though)
[23:53] <calc> potentially having OOo 3.0 split packages parallel installable
[23:53] <slangasek> parallel alongside what?
[23:53] <calc> slangasek: the regular debs, if the 3.0 release slips much more we may have 3.0 split debs for test and 2.4.1 debs for the main install
[23:53] <doko> calc: is this the mmeks split?
[23:54] <cjwatson> my suggestion was, by way of having some concrete progress on OOo this cycle, to produce openoffice.org3-* modularised packages
[23:54] <calc> doko: yes
[23:54] <slangasek> ah :/
[23:54] <slangasek> right, that's better than getting stuck with prerelease 3.0 packages at release time
[23:54] <calc> slangasek: yea
[23:54] <cjwatson> and to use those as a guideline for the observable quality of 3.0
[23:55] <calc> slangasek: they still have sept 16 listed as release date, but that looks awfully optimistic
[23:55] <cjwatson> realistically we aren't going to get much feedback until there's something in the archive, but it seems like they're slipping too much for us to commit to 3.0
[23:55] <cjwatson> that's my take on it, anyway ...
[23:56] <calc> yes
[23:56]  * slangasek nods
[23:56] <calc> if they slip between rc1 and final as much as usual it will be around a week before ubuntu rc when its released
[23:56] <slangasek> yeah, not an ok time to be uploading it :-)
[23:56] <cjwatson> calc: did anything ever come of talking to Till about applications-printing?
[23:56] <calc> and final upstream releases generally are still a bit buggy
[23:57] <cjwatson> I remember you said you'd missed him at the sprint
[23:57] <calc> cjwatson: not much no
[23:57] <cjwatson> did you discuss it with Till?
[23:57] <calc> i talked to him again a few weeks ago, but i don't remember the outcome now
[23:57] <cjwatson> notes, IRC logs, ...?
[23:57] <calc> it looks like there aren't patches for the OOo bit so i would need to track down how to convert OOo to output as PDF
[23:58] <calc> i found the email
[23:58] <cjwatson> (I know I'm putting you on the spot, I just want to check it wasn't lost)
[23:58] <calc> OOo's PDF output is not that great to begin with so i am not sure what would be needed there
[23:59] <calc> there are some pdf changes for 3.0 but i haven't looked into what exactly has changed
[23:59] <calc> eg pdf import via poppler