[14:15] <mvo_> @time berlin
[15:58]  * mvo_ looks around
[15:58]  * robbiew waves
[15:59] <robbiew> #startmeeting
[15:59] <liw> hi
[15:59] <TheMuso> Hey folks.
[15:59] <robbiew> hmm...Mootbot is broken
[16:00] <Keybuk> I can pretend to be mootbot
[16:00] <robbiew> heh...it's not like this channel isn't logged
[16:00] <robbiew> lol
[16:00] <robbiew> Agenda is here: https://wiki.ubuntu.com/FoundationsTeam/Meetings/2009/0114#Agenda
[16:00] <evand> hi
[16:01] <robbiew> waiting on doko, james_w, slangasek, and cjwatson
[16:01]  * james_w waves
[16:01] <robbiew> :)
[16:01] <doko> hi
[16:01]  * slangasek waves
[16:01] <cjwatson> hi
[16:02] <robbiew> great...folks are here and I don't have to use mootbot :P
[16:02] <TheMuso> heh
[16:02] <robbiew> first topic is Jaunty Alpha 3
[16:02] <robbiew> how's that going?
[16:02]  * TheMuso is kind of glad he is working early today, going to be stinking hot...
[16:03] <robbiew> silence
[16:03] <Keybuk> robbiew: I was very restrained and expressly didn't break things today ;)
[16:03] <Keybuk> I'm going to wait until Friday
[16:04] <robbiew> heh...thanks
[16:04] <cjwatson> one installer glitch (bug 316618) fixed today, which I've asked slangasek to respin for
[16:04] <evand> encrypted home directory support in the desktop installer is broken.  On it, but it may end up being a release note.
[16:04] <liw> I'm holding off a system-cleaner upload until Friday, too; spec for that should be ready, waiting for approval (and package waits for third and last name)
[16:04] <cjwatson> images grossly oversized due to new OOo Java dependencies
[16:04] <slangasek> OOo has us a bit behind schedule, java snuck back into the CD dependencies with the latest upload and that puts us a little oversized
[16:04] <cjwatson> 90M is a little? :-)
[16:05] <robbiew> whoa
[16:05] <robbiew> heh
[16:05] <TheMuso> OUCH!
[16:05] <slangasek> the OOo-l10n build should finish in a few hours at which point we should have some right-sized images again
[16:05] <slangasek> cjwatson: smaller than a DVD!
[16:05] <mvo_> I have a pending upload for update-manager to fix system where nvidia binary drivers got removed during the upgrade
[16:05] <cjwatson> it's the "taller than Ronnie Corbett" competition - you can be very short and still win
[16:05] <slangasek> ah, no - OOo-l10n is already built
[16:06] <slangasek> so I'll start respinning the desktop images now and see where we get
[16:06] <mvo_> and asac and I debugged a upgrade issue with libnspr today
[16:06] <robbiew> so Alpha 3 most likely released sometime Friday evening?
[16:06] <mvo_> I had trouble getting the upgrade tester going, kvm in jaunty is not my friend currently
[16:06] <cjwatson> good news for a3 is that I spent a kind of a skunkworks day doing ext4 support in the installer
[16:06] <slangasek> robbiew: still aiming for Thursday evening
[16:06] <cjwatson> which seems to be popular
[16:07] <robbiew> slangasek: ok, thnx
[16:07] <slangasek> there are already some images posted and ready for validation
[16:07] <Keybuk> cjwatson: I bet Ted still didn't change his wiki page? :p
[16:07] <cjwatson> not last I checked ;-)
[16:07] <robbiew> so moving on, I've been steadily adding to the 9.04 status page
[16:08] <robbiew> https://wiki.canonical.com/UbuntuPlatform/Foundations/9.04
[16:08] <robbiew> should be complete by tomorrow
[16:08] <doko> hmm, are the java deps really needed for OOo?
[16:08] <robbiew> gives me a single point of tracking status...and a place for others to quickly check
[16:09] <slangasek> doko: same as before, I think
[16:09] <slangasek> they crept in now because Tuesday was the first day OOo 3 was on the daily builds
[16:09] <cjwatson> calc uploaded to take them out again
[16:10] <cjwatson> 1:3.0.1~rc1-2ubuntu3
[16:10]  * slangasek nods
[16:10] <cjwatson> mvo_: (kvm in jaunty has been working fine for me, for the record ...)
[16:10] <TheMuso> So does openoffice lose much functionality without those deps?
[16:11] <slangasek> TheMuso: AIUI, the answer is "no moreso than before"
[16:11] <TheMuso> slangasek: Right.
[16:11] <mvo_> cjwatson: it freeze for me when I do a upgrade test (interpid->jaunty) at random places (amd64 host)
[16:11] <cjwatson> ugh. (I'm on i386)
[16:11] <mvo_> cjwatson: usually after ~45min or so :/
[16:11] <james_w> though the mailing list suggests it may be a little more than before
[16:11] <mvo_> cjwatson: aha, I shall try on a i386 machine
[16:12] <evand> amd64 here and no issues with kvm thusfar
[16:12] <cjwatson> OOo certainly isn't full-featured without Java, and people using it substantially are still going to need to be advised to install the openoffice.org metapackage (as before, only maybe just more so)
[16:12] <mvo_> evand: hmm, how strnage. do you use virtio?
[16:12] <cjwatson> but I think it's still at a basic useful level on the CD without Java
[16:14] <slangasek> if nothing else, it's nice to let users only have to download 100MB to get a usable OOo instead of 250MB :)
[16:14] <TheMuso> Agreed.
[16:14] <slangasek> mumble, OOo also hasn't finished building on amd64
[16:14] <calc> TheMuso: you can't search help without java, so some functionality is lost
[16:14] <slangasek> so the current desktop CD build is just a smoketest to see if it sizes right on i386, then
[16:15] <TheMuso> calc: Right.
[16:15] <slangasek> calc: oh, in that case perhaps we should be taking the help packages off the CD instead of breaking the java dep?  or is there a useful non-search mode for help?
[16:15] <evand> mvo_: Possibly.  I certainly do not pass such an option to kvm on the command line but the virtio modules are loaded in the VM
[16:15] <calc> slangasek: i think i may have to take a knife to suitesparse packaging because I have a feeling that demoting lpsolve may break calc
[16:16] <slangasek> (also, are upstream unaware that people have implemented 'searching' before in C? :)
[16:16] <slangasek> calc: hmm, ok
[16:16] <calc> slangasek: it appears there is a lib in suitesparse that isn't currently broken out that could be to allow it to work without pulling all of it in
[16:16] <doko> calc: what are the *additional* bits that require java in 3.0?
[16:16] <calc> slangasek: upstream wrote Java and needs to justify its existence
[16:16] <slangasek> calc: can you file a bug asking for the split, and target it to alpha-4?
[16:17] <calc> doko: i don't have the specific details but help apparently uses lucene for searching which in turn is a java library
[16:17] <slangasek> robbiew: have we derailed sufficiently yet? :)
[16:17] <calc> slangasek: i will once i can look into what it takes, i will probably end up splitting it in the process myself
[16:17] <robbiew> heh...about to jump in ;)
[16:18] <robbiew> but always think a healthy discussion is good, too
[16:18] <robbiew> so there's a link to the targeted bugs for Jaunty in the Agenda...no need to discuss it. however, I would like to briefly chat about http://qa.ubuntu.com/reports/ogasawara/jaunty-buglist.html
[16:19] <robbiew> mvo and cjwatson look lonely on the Foundations list
[16:19] <robbiew> :P
[16:20] <robbiew> perhaps I should assign these to the ubuntu-foundations LP team...then we work them from there
[16:20] <cjwatson> mdz has suggested taking on the 'apport-package' bugs (mostly upgrade bugs) and farming them out, which would flesh it out somewhat
[16:20] <robbiew> similar to what Desktop has done
[16:20] <cjwatson> there are nearly 700 of those in main and restricted
[16:20] <mdz> probably a lot of gardening to be done there
[16:21] <mvo_> I can have a look at those
[16:21] <cjwatson> robbiew: I don't think farming out the existing list will improve matters; personally, I think it would be better to add more to that list that correspond to the expertise of other members of the team
[16:21] <mvo_> (but its probably good to have more people looking at them, there are *many* :)
[16:21] <robbiew> cjwatson: ok
[16:21] <cjwatson> i.e. I think the existing ones are basically appropriately assigned
[16:22] <liw> robbiew, I was looking for instructions about how to deal with bugs for the bug fixing initiative the other day, and tried to get a consensus out of the related discussion on the distro list last year... without much luck :(
[16:22] <Keybuk> those are pretty much all installer + package manager bugs atm
[16:22] <cjwatson> exactly
[16:22] <cjwatson> which is just a reflection of how only me and mvo have been using those tags, I think :)
[16:23] <slangasek> 78552 is an interesting bug to have there, the fact that /sbin/update-grub complains is part of a deliberate transition plan by the Debian maintainers
[16:23] <Keybuk> tags?
[16:23] <robbiew> liw: yes, I'll take that as a ToDo
[16:23] <liw> robbiew, thanks
[16:23] <cjwatson> so, there are a couple of things that tie into the bug-fixing initiative
[16:23] <robbiew> there still seems to be some cloudiness on how we approach this effort
[16:23] <cjwatson> https://wiki.canonical.com/UbuntuPlatform/QA/BugFixing/TeamBugLists describes the different approaches one might take
[16:24] <robbiew> Keybuk: tags defined there ^
[16:24] <cjwatson> number 3 on that list is what corresponds to the jaunty-buglist URL robbiew posted above
[16:24] <cjwatson> i.e. things tagged with qa-jaunty-foundations end up on that list; I've been using that as a way to say "our team ought to be addressing this for jaunty"
[16:25] <Keybuk> would we add these tags if we were intending to address it?
[16:25] <Keybuk> or are they for finding bugs nobody's assigned to, and getting someone assigned to them?
[16:25] <liw> cjwatson, so: add tag to get on that list Leann produces, and assign to a person to get one's name onto the list as well?
[16:25] <cjwatson> there is a separate notion that came up on distro-team, which is the "I'd love to have some time to fix this ancient crufty bug" thing
[16:25] <cjwatson> Martin Pitt proposed the "pet-bug" tag for that
[16:25] <cjwatson> these are confusingly similar notions (IMO), but I think they can be distinguished
[16:26] <robbiew> it would be nice if we had a central point to refer to for the bug fix effort...and maybe https://wiki.canonical.com/UbuntuPlatform/QA/BugFixing/TeamBugLists is it
[16:26] <cjwatson> Keybuk: I would say that if it's something you'd like to fix just because it's been annoying you (wishlist bugs would often fall into this category), then "pet-bug"; if it's something that you think is important and basically it's a disgrace that our team has been slacking at fixing it :-), then "qa-jaunty-foundations"
[16:27] <cjwatson> regardless of whether that means you or somebody else
[16:27] <robbiew> however, things like the "pet-bug" tag aren't documented there...and that's where confusion creeps in
[16:27] <cjwatson> some of my bugs on that list are mistagged because they predated "pet-bug", but I was planning to solve this by fixing the bugs
[16:28]  * slangasek grins
[16:29]  * robbiew will get the "pet-bug" tag stuff added to the TeamBugList page
[16:29] <robbiew> moving on to 8.04.2
[16:29] <robbiew> cjwatson: do you have an ETA for the manifest list?
[16:30] <cjwatson> end of the week
[16:30] <robbiew> ok, thanks
[16:30] <cjwatson> which conveniently coincides with the drop-dead date for updates
[16:30] <robbiew> :)
[16:31] <robbiew> looking at bugs, I see 33...right?
[16:31] <robbiew> milestoned
[16:31] <robbiew> so am I to assume that all 33 will be resolved by release? or that some may get bumped
[16:31] <slangasek> almost everything on there that's not already 'fix committed' are going to be deferred
[16:32] <robbiew> gotcha
[16:32] <robbiew> thnx
[16:32] <robbiew> then moving on
[16:32] <robbiew> reminder for the sponsorship queue :)
[16:33] <robbiew> I realize with Alphas, LTS, Distro Sprint coming...can get pushed to the side
[16:33] <cjwatson> is everyone in the habit of listing their sponsorship activity for the week in their activity report, by now?
[16:33] <james_w> the queue length is quite stable currently, but there are some long standing items that need addressing from what I can see
[16:33] <robbiew> it's either no...or just don't have many people doing it
[16:33] <slangasek> cjwatson: yes
[16:34] <robbiew> heh
[16:34]  * mvo_ tries to do it
[16:34] <james_w> I usually just list "sponsoring", I can't always be bothered to look up the list
[16:34] <cjwatson> I only managed one item this week, which I consider a failure
[16:34] <cjwatson> I do write it down as I go along
[16:34] <robbiew> james_w: that's acceptable
[16:34] <robbiew> I can always look at the list ;)
[16:35]  * mvo_ has done only a small number too (at least compared to the sponsoring masters james_w and dholbach :)
[16:35] <Keybuk> I haven't yet habit-formed checking the sponsoring queue
[16:35] <robbiew> ohh...Keybuk is shamed! lol
[16:35] <TheMuso> I got some in this past week, however I find that by the time I get to it, its usually taken care of, due to the whole time zone thing I think.
[16:35] <TheMuso> Depends on how early I get to it./
[16:36] <robbiew> ok, just want folks to keep it in mind during the week...which is why I always bring it up ;)
[16:36] <slangasek> TheMuso: but... but... your timezone is earlier :)
[16:36] <robbiew> lol
[16:37] <robbiew> next topic is the Objectives Guidance
[16:37] <robbiew> just want to point out that they are only guidelines...so no need to think yours have to be like them
[16:38] <robbiew> I didn't know the PDR tool locks them in stone once submitted and approved
[16:38] <robbiew> so it would be better to have self-development style objectives
[16:38] <robbiew> versus business/project related ones...as those can change
[16:38] <Keybuk> oh, was meaning to mention something
[16:38] <Keybuk> my PDR has gone a bit wibbly
[16:39] <robbiew> wibbly???
[16:39] <robbiew> lol
[16:39] <Keybuk> it seems to think I report to you now
[16:39] <Keybuk> which is fine
[16:39] <Keybuk> but it also seems to think lots of people report to me
[16:39] <robbiew> oh
[16:39] <Keybuk> and, well, that seems to upset it a lot
[16:39] <robbiew> promotion for me!!
[16:39] <robbiew> lol
[16:39] <robbiew> Keybuk: talk to bongrad
[16:39] <Keybuk> yeah
[16:41] <robbiew> anyways, if you have business related goals...and they change along the way, don't worry about it
[16:41] <robbiew> I would expect common sense to prevail, and not meeting that objective would not count against you
[16:41] <robbiew> ;)
[16:42] <robbiew> last thing on my list
[16:42] <robbiew> EC2!
[16:42] <robbiew> :)
[16:42] <robbiew> https://wiki.canonical.com/UbuntuPlatform/Foundations/AmazonEC2
[16:42] <robbiew> I've listed the only idea there, on the main list that will be reviewed tomorrow
[16:42] <robbiew> anyone else have anything?
[16:43] <robbiew> mvo: you had the update testing idea, right?
[16:43] <mvo> robbiew: yes
[16:43] <liw> james_w had an idea too, I think
[16:43] <robbiew> right
[16:43] <james_w> well, it was liw's idea
[16:43] <mvo> robbiew: its a bit cloudy to me still how exactly to do it without using a big amounts of resources on the ec2
[16:43] <robbiew> james_w and mvo: you can directly add to https://wiki.canonical.com/CoP/EngineeringManagement/AmazonEC2
[16:43] <robbiew> mvo: that's ok
[16:43] <james_w> but rebuilds + piuparts + other things
[16:44] <robbiew> mvo: just a brainstorm list at the moment
[16:44] <mvo> I would love to have install/remove testing, that kind of basic testing is already pretty helpful
[16:44] <james_w> mvo: could upgrade tests be run every day without too much handholding?
[16:44] <evand> I'm not sure if it fits the model of EC2, but I've wanted to do automatic installation testing for a while now.
[16:44] <mvo> james_w: absolutely, the thing that run them now is totally non-interactive etc - its just that is uses kvm and not ec2/xen currently
[16:45] <evand> erm, nevermind
[16:45] <james_w> mvo: cool. With an in-amazon mirror it may not be too expensive.
[16:45] <mvo> james_w: yeah, if that can be done, that would be cool
[16:45] <robbiew> fyi - that is being setup
[16:45] <robbiew> in-amazon mirror
[16:45] <mvo> aha, nice
[16:45] <james_w> mvo: I like your kvm test-upgrade my machine thing
[16:46] <mvo> then it should indeed be less pain, if the base image can be cached in-amazon too that means even less resource usage
[16:46] <james_w> mvo: would it be possible ro have some of that without massive amounts of bandwidth being needed between me and ec2?
[16:46] <mvo> james_w: thanks :) evand had this idea to make it even more spectacular by using aufs overlay on the real system
[16:46] <james_w> ooh
[16:46] <mvo> james_w: I have a branch and some code, its a bit scary but it seems to be working
[16:46] <evand> wonderful!
[16:46] <james_w> e.g. upload package list + tarball of /etc/ or something?
[16:47] <mvo> james_w: that is a interessting idea too
[16:47] <mvo> james_w: yeah, that should be doable
[16:47] <robbiew> mvo, james_w, evand: make sure to capture this idea here:  https://wiki.canonical.com/CoP/EngineeringManagement/AmazonEC2
[16:47] <robbiew> under Foundations
[16:47] <james_w> got it open :-)
[16:47] <robbiew> right now, I had a generic "Test Upgrades" line :/
[16:47] <robbiew> sweet
[16:47] <robbiew> james_w: thanks
[16:48] <robbiew> that's all I got.
[16:48] <robbiew> AOB?
[16:48] <james_w> daily packages?
[16:48] <robbiew> sure...the POC, right?
[16:49] <james_w> I'd appreciate suggestions for packages that would be good to have dailies of that aren't going to be too temperamental
[16:49] <james_w> I imagine kernel, firefox, OOo would break too often
[16:49] <cjwatson> I think I mailed a few to Robbie a while back
[16:49] <mvo> james_w: I would love to see compiz here
[16:49] <james_w> I think evolution would be good to have.
[16:49] <james_w> ah, compiz cool.
[16:49] <robbiew> cjwatson: hmm...really?
[16:49]  * robbiew checks
[16:50] <TheMuso> james_w: Don't the kernel team have their own daily build stuff anyway?
[16:50] <cjwatson> just trying to find it
[16:50] <cjwatson> I certainly suggested some constraints that should be applied
[16:50] <robbiew> yes...I remember that
[16:50] <james_w> TheMuso: probably, I don't fancy taking that one on
[16:51] <TheMuso> One could actually be pulseaudio. I was going to do it myself into my PPA, but if we have this daily build spec, then it may be worthwhile doing for that.
[16:51] <TheMuso> Pulseaudio is in git however.
[16:51] <cjwatson> there's a project called 'ubuntu-bleedingedge' that started trying to do this, and it would be a useful banner
[16:51] <cjwatson> it even has some code with an initial proof of concept
[16:51] <james_w> TheMuso: I'll add it to the list, thanks
[16:52] <james_w> thanks cjwatson, I'll check it out
[16:52] <cjwatson> that project seems moribund at the moment, but could be revived
[16:52] <cjwatson> lp:~ubuntu-bleedingedge/bleedingedge/trunk and there's a wiki page
[16:52] <cjwatson> robbiew: Subject: Re: [Fwd: Daily upstream packages (Re: Laptop hotkey support)]
[16:53] <robbiew> cjwatson: ah, thnx
[16:53] <cjwatson> james_w: I'll forward you this mail
[16:53] <james_w> thanks
[16:53] <james_w> as this is Ubuntu-external I'll be starting after feature freeze on it
[16:53] <robbiew> cjwatson: found it ;)
[16:54] <robbiew> james_w: ok, and you mentioned a spec for this right?  Figure we should at least have a documented plan
[16:54] <james_w> yeah, I'll write up a spec, or find an existing one to co-opt
[16:55] <robbiew> ok...just shoot me the link in an email
[16:55] <james_w> sure
[16:55] <robbiew> anything else?  cjwatson: campaign speech for Tech Board? lol
[16:55]  * cjwatson grins
[16:56] <liw> did we skip "Good News"?
[16:56] <robbiew> that is Good News :)
[16:56] <robbiew> liw: on it now
[16:56] <cjwatson> my good news was ext4
[16:56] <robbiew> ah, yes
[16:56] <cjwatson> oh, I'm going through the archive reorg videos now and trying to shore up the spec
[16:56] <liw> my good news for today is that I managed to survive an encounter with a screwdriver
[16:56] <robbiew> liw: lol...what?
[16:57] <cjwatson> I have been a naming fascist and nailed down a single set of nomenclature
[16:57]  * mvo advices liw to stay away from hardware
[16:57] <liw> (had to tweak my desktop machines a bit)
[16:57] <robbiew> cjwatson: name nazi
[16:57] <liw> mvo, I try, I try...
[16:57]  * TheMuso is starting to get the hang of dealing with alsa hda quirks, and maanged to get an Ubuntu originated quirk patch applied upstream, with many more to come hopefully.
[16:58] <cjwatson> (screw "lobes", I went with "layers")
[16:58] <TheMuso> bad news, my typing sucks. :p
[16:58] <robbiew> cjwatson: yeah...lobes was nasty
[16:58] <liw> cjwatson, if you run out of English words, I can send you a Finnish dictionary ;)
[16:58] <cjwatson> and realised that layers are in fact identical to Mark's package sets
[16:58] <cjwatson> so have been trying to make the spec reflect that
[16:59] <robbiew> #endmeeting ....for Keybuck-bot :P
[16:59] <slangasek> I thought it was "cells"
[17:00] <slangasek> ohwell :)
[17:00] <liw> thanks
[17:00]  * mvo likes cells
[17:00] <james_w> thanks all
[17:00] <evand> thanks!
[17:00] <TheMuso> thanks
[17:00] <mvo> thanks
[17:00]  * Keybuk likes pies
[17:00] <robbiew> lol
[17:00] <robbiew> thanks all
[17:00]  * TheMuso goes and syncs ubunt and studio isos.
[17:02]  * heno waves 
[17:02]  * ara waves
[17:02] <sbeattie> hey
[17:02]  * ogasawara waves
[17:02] <bdmurray> hello
[17:02]  * sbeattie disappears for a second to replentish his caffiene supply
[17:02] <davmor2> hello everybody
[17:02] <charlie-tca> hello
[17:03] <bdmurray> charlie-tca: hello
[17:03] <pedro_> hello everybody
[17:04]  * schwuk waves
[17:04] <heno> welcome all!
[17:04] <heno> #startmeeting
[17:04] <davmor2> no bot
[17:05] <heno> agenda: https://wiki.ubuntu.com/QATeam/Meetings
[17:05] <heno> * Jaunty spec review
[17:06] <heno> I've updated https://wiki.ubuntu.com/QATeam/RoadMap with Jaunty spec info
[17:06] <schwuk> davmor2: you could pretend to be the bot
[17:06] <heno> There are a few bits missing (ran short of time)
[17:06] <davmor2> schwuk: :P
[17:07] <schwuk> heno: looks good
[17:07] <heno> please add other items you are working on that are not registered as specs to the bottom of that page
[17:08] <heno> and please review it for general sanity
[17:08] <heno> There are still a few specs that need more drafting and approval - please try to get that wrapped up this week
[17:09] <heno> Let's not go through the whole list at this meeting though
[17:09] <heno> we can cover it briefly on the c.c call
[17:10] <heno> instead lets focus on Hardy and Jaunty release testing
[17:10] <heno> * Hardy point release testing
[17:11] <heno> sbeattie: can you give an update on 8.04.2 SRU testing?
[17:11] <heno> esp areas you are blocked and could use some help
[17:12] <sbeattie> sure, I've been working on the base-installer one (bug 306356) which looks good for hardy (and intrepid), but I'd like cjwatson to verify my results, because they didn'tmatch his testcase.
[17:12] <davmor2> I've done some testing on bugs past me by slangasek to help clear those
[17:12] <cjwatson> (one moment, looking)
[17:13] <heno> davmor2: also installer bugs right?
[17:13] <sbeattie> I was also poking at the ntfs-3g one (bug 204133) as it affects wubi, but couldn't reproduce it, so I left a ping asking for soeone affected by it to try testing it out.
[17:13] <davmor2> heno: yes
[17:13] <cr3> regarding the QA roadmap, the blueprints section mentions "Intrepid". shouldn't it mention "Jaunty"?
[17:14] <pedro_> FYI there's an issue with evolution 2.24.3 package; bug 316726, which should be fixed pretty soon
[17:14] <pedro_> 2.24.3 from proposed.
[17:15] <heno> Note - the cut-off for SRU testing is Monday - at that point we start rolling ISOs and testing those
[17:15] <cjwatson> sbeattie: the test case is incorrect in that it leaves it implicit that all tests of proposed d-i component changes need to be run with apt-setup/proposed=true
[17:15] <davmor2> sbeattie: I think that got fixed to a degree
[17:15] <heno> davmor2: have you had a chance to smoke test any hardy ISOs?
[17:15] <sbeattie> ones I could use help with are the hardware specific ones, bug 59695, bug 204483, bug 288859 and bug 267570
[17:15] <bdmurray> sbeattie: I could try the wubi one I guess...
[17:16] <davmor2> heno: I've had a quick look at them once installed for the case I was given
[17:16] <cjwatson> sbeattie: oh, but do you just mean that the host name you saw was different from the test case - us.archive rather than security?
[17:16] <sbeattie> cjwatson: yes, that part.
[17:16] <cjwatson> sbeattie: I think that's a mistake in the test case, yes, and also a not very serious pre-existing bug in base-installer
[17:16] <davmor2> heno: there was an issue with umenu and wubi but that should be fixed in today's image
[17:17] <heno> cr3: could you have a look at sbeattie's hw-specific bugs and see if we have the hardware in Montreal?
[17:18] <sbeattie> cjwatson: hrm, that's what I thought the patch was fixing, that $MIRROR (us.archive) would get used, rather than $SECMIRROR (aka apt-setup/security_host)
[17:18] <cr3> heno: noted
[17:18] <heno> which brings us to ...
[17:18] <heno> * cert lab hw data dump status (schwuk)
[17:19] <cjwatson> sbeattie: oh, err - yeah, you're right. insufficient coffee
[17:19] <sbeattie> cjwatson: no worries, wanted to make sure it wasn't insufficient coffee on my end.
[17:19] <cjwatson> sbeattie: I've corrected the test case. I *think* it passes now given your comments?
[17:20] <sbeattie> cjwatson: yes, I agree, I think it passes.
[17:21] <schwuk> heno: can you add a bit more detail to that?
[17:21] <sbeattie> hardware dump: ogasawara and I were hoping, as an interim thing, if we could get just a raw dump (possibly a tarball) of the current hardware we have in the certification lab, at a more detailed level than just model number, but listing components.
[17:21] <heno> schwuk: are you able to generate a dump of the hardware info from the machines we have that can be searched locally?
[17:22] <heno> stuff that has already been gathered during various testing
[17:22] <schwuk> heno: sure - I'll cook something up
[17:22] <heno> but needs to be mined from the db
[17:22] <sbeattie> schwuk: basically something we can grep for things like pci ids locally, to use in identifying whether we have hw available for testing specific issues.
[17:23] <heno> a tarball with a dir for each system perhaps, with various files in each
[17:23] <bdmurray> sbeattie: I thought cr3 made the database available once
[17:23] <schwuk> sbeattie, heno: sure
[17:23] <heno> we could then use local tools to search
[17:24] <sbeattie> bdmurray: if so, I've forgotten the details. I've access to the website, but there's no easy way to search for whether we have specific hardware through it.
[17:24] <heno> I think extracting it from the raw database is not trivial without knowledge of it's structure
[17:24] <cr3> bdmurray: the database is more complicated to query than flat text files
[17:24] <heno> because of the way results are stored
[17:25] <davmor2> schwuk: can you not sudo lshw -html each device it will give you something like http://www.davmor2.co.uk/64test.html
[17:25] <cr3> davmor2: the information is extracted from the database which contains structured information, so the output will have to be generated based on that information
[17:26] <heno> schwuk: ok, thanks
[17:26] <schwuk> davmor2: we already have the info, we just have to re-constitute it
[17:26] <heno> * Testcase wiki migration; automated scripts
[17:26] <heno> ogasawara and I looked at this yesterday
[17:27] <heno> the structure of the pages we have and want are quite different
[17:27] <davmor2> go on
[17:27] <heno> so writing sensible scripts might be more work than copying the content across
[17:28] <heno> I suggest we get a dump of the pages from IS from the server and paste it in and refactor from there
[17:28] <heno> schwuk: do we have access to the moin data dir?
[17:29] <heno> (on the testcases wiki)
[17:29]  * schwuk checks
[17:29] <heno> that way we would have the attachments and history
[17:30] <ara> heno: if that solutions is possible, it would be great
[17:30] <heno> schwuk: can you coordinate that with IS, getting the dump and getting it uploaded?
[17:30] <schwuk> heno: no. We'll need either an RT to get acces, or the content copied accross
[17:31] <schwuk> heno: sure
[17:31] <heno> davmor2: can we speak tomorrow about the refactoring we need to do afterward?
[17:31] <heno> schwuk: both would be ideal
[17:31] <davmor2> yes no probs
[17:31] <schwuk> Where do we want the pages put?
[17:32] <heno> under their current names
[17:32] <heno> then we can rename from there
[17:33] <heno> that's the end of the agenda
[17:33] <schwuk> So basically the whole of /Testing right?
[17:33] <heno> schwuk: Testing/Cases only
[17:34] <schwuk> heno: Got it.
[17:34] <heno> any other business for the meeting?
[17:34] <davmor2> yes
[17:35] <davmor2> is there a way to stop the dl-ubuntu-test-iso script exiting when it hits an issue with md5sum?
[17:35] <sbeattie> davmor2: yes, one sec
[17:35] <cr3> davmor2: what's this script?
[17:36] <davmor2> Xubuntu is the cause this time but it is in the live which means the alternate section can't be downloaded using it
[17:36] <sbeattie> davmor2: you could turn off verification of md5sums
[17:36] <heno> cr3: used for ISO testing - would be worth looking at for the satellite servers too
[17:36] <davmor2> cr3: it's a script which pulls all the isos
[17:37] <heno> https://wiki.ubuntu.com/Testing/Isoscript
[17:37] <sbeattie> davmor2: give me a bit and I think I can fix it up so that it doesn't abort on the md5sum error.
[17:38] <cr3> heno: the images/archives that need to be tested are communicated to the satellite servers from the web server, so I'm not sure how useful this might be but I'll nonetheless look into the script
[17:38] <davmor2> cr3: I have it as a cron job so I get the latest daily each morning before I sit down to test :)
[17:39] <cr3> davmor2: do you have the latest hardy daily too?
[17:39] <davmor2> yes
[17:39] <davmor2> script does it all :)
[17:40] <cr3> if I run the bzr command on the wiki, I get: bzr: ERROR: Connection error: curl connection error (Problem with the SSL CA cert (path? access rights?))
[17:41] <heno> WFM
[17:41] <heno> ok, let's wrap it up
[17:41] <heno> #endmeeting
[17:41] <schwuk> thanks heno
[17:41] <heno> thanks everyone!
[17:41] <sbeattie> cr3: https://code.launchpad.net/~ubuntu-bugcontrol/ubuntu-qa-tools/master
[17:41] <ara> thanks!
[17:41] <sbeattie> thanks.
[17:42] <davmor2> cr3: works for me
[17:42] <davmor2> 51 revisions
[17:43] <davmor2> thanks
[17:43] <cr3> this works for me: bzr branch lp:ubuntu-qa-tools
[22:08] <MTecknology> what's the bot in here?