16:05:11 <jlaska> #startmeeting F13Beta review
16:05:12 <zodbot> Meeting started Fri Mar 26 16:05:11 2010 UTC.  The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:05:14 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:05:23 <jlaska> #meetingname f-13-beta-blocker-review
16:05:24 <zodbot> The meeting name has been set to 'f-13-beta-blocker-review'
16:05:27 <jlaska> #topic Gathering
16:05:36 <jlaska> #chair adamw
16:05:38 <zodbot> Current chairs: adamw jlaska
16:06:07 <jlaska> dlehman: welcome
16:06:37 * jlaska pulls up blocker list while waiting for others to join
16:06:44 <Oxf13> Sorry I'm late
16:06:46 <Oxf13> but I'm here.
16:07:05 <jlaska> Oxf13: no worries, things just got started
16:07:40 <jlaska> #topic Why are we here ...
16:07:51 <jlaska> just a reminder (for me really)
16:07:58 <jlaska> #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
16:08:13 <jlaska> we're here to review the F13Beta list and determine whether the contents are Beta blockers
16:08:25 <jlaska> The list of F13Beta blocker bugs - https://bugzilla.redhat.com/showdependencytree.cgi?id=538274&hide_resolved=1
16:09:02 <jlaska> do we want to include ON_QA and MODIFIED bugs during review?
16:09:15 <jlaska> NEW + MODIFIED + ON_QA = 15 bugs
16:09:23 <jlaska> NEW = 3 bugs
16:09:26 <adamw> i think we should run through them quickly to make sure that we have a plan for confirming the fixes
16:09:34 <Oxf13> we should since we have the capability of testing some of those MODIFIED
16:09:41 <jlaska> alrighty ... lemme sort by component ...
16:10:23 <jlaska> http://tinyurl.com/yk9dgez
16:10:31 <jlaska> okay, starting off ...
16:10:38 <jlaska> #topic https://bugzilla.redhat.com/show_bug.cgi?id=569377
16:10:39 <buggbot> Bug 569377: medium, low, ---, pjones, MODIFIED, CDROM install unable to eject disc - storage: error ejecting cdrom sr0: (5, 'Input/output error')
16:11:00 <adamw> cranes maska time!
16:11:11 <jlaska> he's a good guy, I really like him
16:11:12 <jlaska> a lot
16:11:33 <jlaska> well, I tested the updates.img for this yesterday
16:11:42 <jlaska> now it just needs testing against the updated images
16:12:22 <adamw> seems simple enough
16:12:33 <jlaska> it does ... this might come up again later when we look at the last anaconda bug on the list
16:12:42 <jlaska> anything else to discuss here?
16:12:55 <Oxf13> just needs somebody to test split media
16:13:01 <adamw> not really, as long as it's on your list to test we're all good
16:13:08 <jlaska> #info Tested updates.img - Fixed in anaconda-13.37-1 (F-13-Beta-RC1) awaiting testing
16:13:33 <jlaska> alrighty, next up
16:13:38 <jlaska> #topic https://bugzilla.redhat.com/show_bug.cgi?id=574587
16:13:40 <buggbot> Bug 574587: high, high, ---, hdegoede, MODIFIED, Failure to install on Intel Matrix RAID box when raid level 5 is active
16:13:59 <jlaska> #info Fix included in anaconda-13.37-1 (F-13-Beta-RC1)
16:14:16 <adamw> looks like we need dledford to re-test with rc1
16:14:21 <jlaska> yeah
16:14:35 <jlaska> adamw: you already posting in the bz?
16:14:46 <Oxf13> yeah I have no way to re-test this
16:15:07 <jlaska> same here, I don't have access to this type of hardware right now
16:15:16 <adamw> jlaska: will do
16:15:50 <jlaska> #help needs confirmation that the fix solves the reported problem ... possibly dledford
16:16:19 <adamw> posted
16:16:19 <jlaska> #action adamw requesting updated test results in bz
16:16:22 <jlaska> adamw: thx
16:16:25 <jlaska> alright, next up ...
16:16:36 <jlaska> #topic https://bugzilla.redhat.com/show_bug.cgi?id=574743
16:16:37 <buggbot> Bug 574743: medium, medium, ---, dlehman, MODIFIED, NameError: global name 'request' is not defined
16:17:32 <jlaska> #info Fixed in anaconda-13.37-1 (F-13-Beta-RC1) - awaiting re-test
16:18:16 <adamw> a lot of these are going to be on you to re-test, james - do you want any help with some of them?
16:18:31 <jlaska> not much else to say here ... dlehman's fixes here looked solid in the updates.img tested yesterday
16:18:50 <jlaska> #action jlaska to retest fix and update bz
16:19:01 <jlaska> adamw: definitely!
16:19:39 <jlaska> the reproducer should be in the bug report ... but I think the best people can do is edit pre-existing partitions during install
16:19:42 <jlaska> dlehman does that sound good?
16:20:19 <dlehman> preexisting logical volumes, right?
16:20:45 <jlaska> #help Looking to help test?  Install F-13-Beta-RC1 and play around with pre-existing logical volumes during install
16:20:49 <adamw> jlaska: i can take some of the ones that can be tested in a VM if you like - shall we sort it out in pm after the meeting?
16:21:23 <jlaska> adamw: okay, yeah we can divide up afterwards
16:21:30 <jlaska> see how each of our plates looks
16:21:49 <jlaska> next up ...
16:21:56 <jlaska> #topic https://bugzilla.redhat.com/show_bug.cgi?id=575855
16:21:57 <buggbot> Bug 575855: medium, low, ---, clumens, MODIFIED, Referencing disks by-path in clearpart doesn't work
16:22:55 <jlaska> #info Fixed in anaconda-13.37-1 (F-13-Beta-RC1) - awaiting testing
16:23:24 <Oxf13> sounds like this needs kickstart testing
16:23:33 <adamw> looks like orion poplawski is the initial reporter?
16:23:48 <jlaska> yeah, I'd like if we could get his help confirming the fix
16:24:22 <adamw> i can post in the bug
16:24:30 <jlaska> adamw: go for it
16:24:41 <jlaska> this shouldn't be hard to test, it's just the time to setup
16:25:08 <jlaska> #action adamw asking Orion Poplawski for help testing the fix
16:25:33 <jlaska> dlehman: do you know if that patch accounts for orion's comment?
16:25:37 <jlaska> https://bugzilla.redhat.com/show_bug.cgi?id=575855#c2
16:25:41 <jlaska> > Well, I can use the /dev/disk/by-path/... form but not disk/by-path/...
16:25:42 <buggbot> Bug 575855: medium, low, ---, clumens, MODIFIED, Referencing disks by-path in clearpart doesn't work
16:26:32 <dlehman> jlaska: yeah, he made it so you can take or leave the leading '/dev/'
16:26:47 <jlaska> yeah, docs confirm that too ... cool
16:26:55 * jlaska confirmed at http://fedoraproject.org/wiki/Anaconda/Kickstart
16:27:01 <jlaska> okay, next up ...
16:27:16 <jlaska> #topic https://bugzilla.redhat.com/show_bug.cgi?id=576085
16:27:17 <buggbot> Bug 576085: medium, medium, ---, anaconda-maint-list, MODIFIED, TypeError: format requires a mapping
16:27:43 <jlaska> #info Fixed in anaconda-13.37-1 (F-13-Beta-RC1) - awaiting re-test
16:28:05 <jlaska> Hurry found this while testing Beta-TC1, I'll ask her if the issue is still present
16:28:49 <adamw> i'm not sure the rest of us could test this, i'm not entirely sure what her step 2. means
16:29:17 <jlaska> I believe she was testing - https://fedoraproject.org/wiki/QA/TestCases/PartitioningExt2OnNativeDevice
16:29:28 <jlaska> then shrinking the partition on the next install
16:29:36 <jlaska> https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_(shrink)_install
16:30:09 <jlaska> #action jlaska updated bz asking for help from Hurry to re-test
16:30:28 <jlaska> okay, moving on ... stop me if I'm going to fast (or slow :) )
16:30:43 <jlaska> #topic https://bugzilla.redhat.com/show_bug.cgi?id=576529
16:30:44 <buggbot> Bug 576529: medium, medium, ---, dlehman, MODIFIED, KeyError: 'originalFormat'
16:31:01 <jlaska> #info Fixed in anaconda-13.37-1 (F-13-Beta-RC1) - awaiting re-test
16:31:10 <jlaska> same deal here, this is easy for me to retest
16:31:23 <jlaska> I confirmed the fix in an updates.img, but will re-test in RC1
16:31:31 <adamw> oka
16:31:32 <adamw> y
16:31:40 <jlaska> #action jlaska will retest 576529 on F-13-Beta-RC1
16:31:51 <jlaska> next up ...
16:31:52 <jlaska> #topic https://bugzilla.redhat.com/show_bug.cgi?id=576628
16:31:53 <buggbot> Bug 576628: medium, medium, ---, anaconda-maint-list, MODIFIED, AttributeError: 'DMRaidMember' object has no attribute 'partedDisk'
16:32:31 <jlaska> #info Fixed in anaconda-13.37-1 (F-13-Beta-RC1) - awaiting re-test
16:32:59 <jlaska> I've not tested this in an updates.img, but the reproducer involves attempting to manually create partitions on BIOS RAID hardware
16:33:14 <jlaska> I've got the setup for this already, so I plan to test
16:33:26 <Oxf13> I think I can test this too
16:33:29 <jlaska> anyone else with BIOS RAID is encouraged to contribute results as well
16:33:34 <jlaska> Oxf13: cool, thanks
16:33:35 <Oxf13> since I have a dmraid machine with an install already on it
16:33:57 <Oxf13> #action Oxf13 to confirm fix for 576628
16:33:59 <jlaska> #action jlaska and Oxf13 will post test results for 576628 against F-13-Beta-RC1
16:34:06 <jlaska> #undo
16:34:07 <Oxf13> jynx
16:34:07 <zodbot> Removing item from minutes: <MeetBot.items.Action object at 0x179e5090>
16:34:12 <jlaska> love that undo :)
16:34:23 <jlaska> #action jlaska will also post test results for 576628 against F-13-Beta-RC1
16:34:36 <jlaska> there we go, that works ... gives me a good TODO list :)
16:34:46 <jlaska> okay, last MODIFIED anaconda bug ...
16:34:48 <jlaska> #topic https://bugzilla.redhat.com/show_bug.cgi?id=576691
16:34:49 <buggbot> Bug 576691: medium, medium, ---, clumens, MODIFIED, ValueError: Error parsing "proxy = 'intel-s3ea2-02.rhts.eng.bos.redhat.com:8080'": URL must be http, ftp or https not "intel-s3ea2-02.rhts.eng.bos.redhat.com"
16:35:06 <jlaska> #info Fixed in anaconda-13.37-1 (F-13-Beta-RC1)
16:35:22 <jlaska> I'm not sure how to test this really, it involves installing from a proxy
16:35:35 <Oxf13> I bet clumens could restest for us
16:35:38 <Oxf13> retest even
16:35:47 <jlaska> atodorov can probably help here too
16:37:00 <jlaska> #action jlaska to ask atodorov+clumens for help verifying fix
16:37:19 <jlaska> adamw: can you take it from here, I'm sorry I've got to step out for a moment
16:37:27 <adamw> sure
16:37:56 <adamw> jlaska: what list have you been working from?
16:38:09 <jlaska> tinyurl at the top ... /me grabs
16:38:26 <jlaska> http://tinyurl.com/yk9dgez
16:39:00 <adamw> ok, let's go with
16:39:01 <adamw> #topic https://bugzilla.redhat.com/show_bug.cgi?id=577196
16:39:03 <buggbot> Bug 577196: medium, low, ---, anaconda-maint-list, NEW, Freeze when installing bootloader
16:39:17 <adamw> this is the only un-modified anaconda bug
16:39:28 <adamw> seems new in rc1
16:39:29 <dlehman> the freeze is actually when ejecting the cdrom
16:39:42 <adamw> and revealed by the disc swap fix for split media?
16:39:49 <dlehman> seems so
16:41:02 <Oxf13> cute
16:41:04 <adamw> so it seems this is a pretty obvious show-stopper, no need to debate its blockerness
16:41:12 <adamw> do you reckon you'll be able to fix it soon?
16:41:16 <dlehman> sounds right
16:41:16 <Oxf13> the install is done at this point, just doesn't reboot on its own?
16:41:24 <dlehman> no idea about fix eta
16:41:42 <dlehman> Oxf13: yeah, box locks up
16:42:33 <adamw> do we know if this happens on real hardware, or only in virt?
16:43:17 <adamw> jlaska's obviously seen it, but his comments don't mention how he was testing
16:43:20 <dlehman> good question
16:43:32 <Oxf13> well, hopefully we can get a fix in for it, asap
16:43:35 <dlehman> the original unable to eject bug was real hw
16:43:51 <adamw> right, we're on a tight timescale for beta here
16:44:05 <dlehman> Oxf13: it doesn't look like we're doing anything wrong in anaconda
16:44:17 <adamw> ideally we'd want a fix over the weekend, certainly early monday, to have any chance of spinning a new build with the fix and running the matrix before go/no-go
16:44:39 <adamw> dlehman: any chance pjones would know more than you, or are you up to speed with his latest thoughts?
16:45:07 <dlehman> he's going to get back into after he eats
16:45:09 <Oxf13> wait, this sounds familiar
16:45:15 <Oxf13> freezing when ejecting in virt
16:45:45 <adamw> i can't easily test on real hw :/ i *really* need a test disk, sigh. should just go buy one.
16:46:42 <adamw> anyway, summary: we need to verify whether this affects virt only or also real hw, and we need to get a fix asap :)
16:46:44 <adamw> is there more to say?
16:47:12 <dlehman> not afaik
16:47:27 <adamw> the X log in jlaska's logs identifies the graphics card as a Cirrus
16:47:31 <adamw> which smells like virt to me
16:48:02 <adamw> so we definitely need real hw testing. i'll try and find a way to do it, but oxf13/jlaska if you also could that'd be good
16:48:13 <Oxf13> I can do
16:48:24 <adamw> #agreed 577196 is clearly a showstopper, needs a fix ASAP. need to verify if it happens on real hardware or only in virt
16:48:30 <dlehman> yeah -- disks are vda, vdb
16:48:32 <adamw> #action oxf13 and adamw to test on real hw
16:48:39 <adamw> #action dlehman and pjones to co-ordinate on fix
16:49:27 <adamw> ok, i believe we're done with anaconda now
16:49:28 <adamw> thanks dlehman
16:49:41 <dlehman> np
16:50:25 <adamw> ok, so let's take the next few bugs as a group:
16:50:42 <adamw> #topic https://bugzilla.redhat.com/show_bug.cgi?id=567346 https://bugzilla.redhat.com/show_bug.cgi?id=577123 https://bugzilla.redhat.com/show_bug.cgi?id=577100
16:50:45 <buggbot> Bug 567346: high, low, ---, richard, ON_QA, gpk-update-viewer does not install updates if there is any dependency issue, and does not correctly report this
16:50:49 <buggbot> Bug 577123: medium, low, ---, davidz, NEW, dbus unresolved dep on Beta.RC1 x86_64
16:50:49 <buggbot> Bug 577100: medium, low, ---, richard, NEW, PackageKit-related unresolved deps on Beta.RC1
16:51:06 <adamw> so oxf13 pulled a new PackageKit build into RC1, at my request - that's 567346
16:51:30 <adamw> unfortunately this version has a lib major bump compared to the previous package, and this has introduced some dependency issues
16:52:09 <Oxf13> I didn't notice it in the pungi logs either because pungi just pulled in the old PackageKit to match deps
16:52:16 <adamw> the new pk definitely addressed the underlying 567346 bug, for me: i had a problematic update set, i updated to the newer packagekit, and the update worked
16:52:21 <adamw> Oxf13: ah, yeah - i was guessing that's what happened
16:52:41 <Oxf13> which means I need to actually run repoclosure on my repos with --newest before I assume they're good
16:52:42 <adamw> Oxf13: the old one being available from dist-f13, i guess?
16:52:46 <Oxf13> yep
16:52:52 <adamw> right, just needs a process tighten i guess
16:53:09 <adamw> so so far we know we need a newer dbus, kpackagekit and gnome-packagekit
16:53:15 <Oxf13> I've pulled the gnome-packagekit and kpackagekit builds into my bleed repo
16:53:25 <Oxf13> just need to make sure these are bundled with the PackageKit bodhi request
16:53:40 <Oxf13> #action Oxf13 to make sure kpackagekit and gnome-packagekit are bundled with PackageKit update in bodhi
16:54:00 <adamw> actually, is the dbus issue different? i may be reading the output wrong
16:54:41 <Oxf13> dbus too?
16:54:47 <adamw> that's https://bugzilla.redhat.com/show_bug.cgi?id=577123
16:54:47 <Oxf13> I wasn't aware of a dbus issue
16:54:48 <buggbot> Bug 577123: medium, low, ---, davidz, NEW, dbus unresolved dep on Beta.RC1 x86_64
16:54:53 <adamw> i thought it was related to this but i may be misreading
16:55:01 <adamw> i will ask mclasen to update the Bodhi request
16:55:44 <Oxf13> I already updated the PackageKit update request
16:55:48 <adamw> oh ok :)
16:56:52 <Oxf13> hrm, so I think the dbus thing might just be because I didn't make my bleed repo multilib
16:56:53 <adamw> #action oxf13 to pull newer kpackagekit and gnome-packagekit into Beta, and added to the Bodhi update request: https://admin.fedoraproject.org/updates/PackageKit-0.6.3-0.1.20100322git.fc13
16:56:59 <Oxf13> not sure though, will have to investigate
16:57:01 <adamw> okay, let me separate it out then
16:57:07 <Oxf13> adamw: you missed my earlier action call
16:57:09 <Oxf13> #undo
16:57:25 <adamw> d'oh, thanks
16:57:26 <adamw> #undo
16:57:28 <zodbot> Removing item from minutes: <MeetBot.items.Action object at 0x2b03af258a90>
16:57:39 <adamw> #topic https://bugzilla.redhat.com/show_bug.cgi?id=577123
16:57:40 <buggbot> Bug 577123: medium, low, ---, davidz, NEW, dbus unresolved dep on Beta.RC1 x86_64
16:57:52 <Oxf13> this one I have to look into more
16:57:55 <adamw> so as discussed above, this isn't related to the packagekit issue.
16:58:09 <adamw> it's obviously a blocker, as repoclosure fails
16:58:14 <adamw> #agreed 577123 is a blocker
16:58:17 <Oxf13> almost certainly it's because I didn't make my bleed repo multilib
16:58:26 <adamw> #action oxf13 to investigate the cause and fix for next build
16:58:30 <Oxf13> however installs from DVD won't do multilib by default so this shouldn't actually break anything
16:58:54 <Oxf13> I don't really think it is a blocker because those i686 packages aren't actually used when installing from DVD/split media
16:59:04 <Oxf13> in fact I was thinking we should remove them from the media
16:59:07 <adamw> hmm, okay.
16:59:15 <Oxf13> they haven't been used since yum defaulted to "best arch" strategy
16:59:49 <adamw> i'm a little nervous - it feels like one of those things where we might go 'oops, but of COURSE they get used when XXXXX' next week - but i'll go with it if you're confident :)
17:00:43 <adamw> #agreed correction: 577123 not a blocker: oxf13 "I don't really think it is a blocker because those i686 packages aren't actually used when installing from DVD/split media"
17:01:25 <Oxf13> brb, I have a visitor, shouldn't take more than 5 minutes
17:01:47 <adamw> ok
17:01:51 <adamw> i've updated the bug
17:02:48 <adamw> #topic https://bugzilla.redhat.com/show_bug.cgi?id=533746
17:02:49 <buggbot> Bug 533746: urgent, low, ---, linville, ON_QA, Fedora 12 livecd freezes at udev on Acer Aspire One D250
17:03:07 <adamw> despite the bug name this affects f13 too. it's the 'hang with some broadcom wireless chips' bug
17:03:42 <adamw> i consider it a beta blocker - it's a judgment call issue as it's a some-hardware-affected one; the amount of affected systems is big enough for it to be a blocker at beta stage, imo.
17:04:04 <adamw> it should be fixed in kernel-2.6.33.1-19.fc13 . oxf13, is that the one which got pulled into rc1?
17:06:13 <Oxf13> back.
17:06:24 <Oxf13> yes
17:06:29 <Oxf13> I think
17:06:30 <Oxf13> let me check
17:06:54 <Oxf13> yep, 1-19
17:06:59 <Oxf13> it's already in branched stable
17:07:33 <adamw> okay
17:07:38 <adamw> i'll try and get someone from the bug to test
17:07:46 <adamw> i don't believe we (qa) have any affected systems unfortunately
17:07:58 <Oxf13> yeah, that's the problem.
17:09:03 <adamw> okay. not much else to say here then i guess
17:09:24 <adamw> oh, except the fix i believe still doesn't actually make the wireless work with the open driver, it just prevents the hang
17:09:31 <Oxf13> right
17:09:35 <Oxf13> that's the best we can hope for at this point
17:09:44 <adamw> #action adamw to request testing from bug reporters for 533746, fix should be in RC1
17:11:07 <adamw> if we can't get a confirmation i think we should just assume it's fixed and go ahead and ship, but it'd be nice to have confirmation
17:11:27 <adamw> okay, last one
17:11:29 <adamw> #topic https://bugzilla.redhat.com/show_bug.cgi?id=572215
17:11:30 <buggbot> Bug 572215: medium, low, ---, jforbes, ON_QA, unhandled vm exit: 0x11 - while creating a guest using virt-install
17:12:04 <Oxf13> this is still in updates-testing for F12 isn't it?
17:12:10 <adamw> seems like this has been worked on for f12 but not f13
17:12:13 <adamw> seems that way
17:12:21 <adamw> i'm just reading the comments, don't know anything else about this one
17:12:31 <adamw> let's see if we can get jforbes in
17:14:03 <adamw> hiya justin
17:14:14 <adamw> we're on https://bugzilla.redhat.com/show_bug.cgi?id=572215
17:14:16 <buggbot> Bug 572215: medium, low, ---, jforbes, ON_QA, unhandled vm exit: 0x11 - while creating a guest using virt-install
17:14:49 <adamw> oh, i see now - this is an f13 blocker, but it's actually in f12
17:14:58 <jforbes> adamw: right, so there is an update in testing which fixes this, but it shouldnt be an F13 blocker at all
17:15:01 <adamw> we don't need to push anything to f13 to fix it...
17:15:19 <adamw> no, it's correct for it to be an f13 blocker - one of the criteria for f13 is that it should boot on an f12 host
17:15:22 <jforbes> Yeah, the bug was in the F12 host, F13 already has the fix
17:15:36 <adamw> there are a few situations where a bug in N-1 can actually block N, though it sounds odd :)
17:16:19 <adamw> as far as i'm concerned we can drop this from the blocker list just since it's available in updates-testing, we can always document the use of the updates-testing package; but obviously it's best when it gets to f12 updates. so all it needs is testing to confirm it's okay, I guess.
17:16:26 <jforbes> adamw: Well, in this case I wouldn't think it makes sense...
17:16:59 <jforbes> adamw: Right, update just needs a bit more karma
17:17:22 <adamw> oh yeah, it's the one that got a couple of -1s
17:17:22 <jforbes> adamw: anyway, nothign you can do in F13 to change this, which is why I find it odd as a blocker.
17:18:00 <jforbes> Right, the first -1 is silly.  It doesnt fix a bug completely, certainly no regression though.
17:18:18 <adamw> well, that's mostly our fault that we don't have clearly defined what you're supposed to vote for
17:18:27 <adamw> the second -1 looks a bit more worrying; have you looked into that?
17:20:03 <jforbes> adamw: yeah, it seems a bit odd...
17:20:46 <adamw> well let's see, anyway. i guess the summary is we'd like the fix to go into f12 asap, but not if there's regressions; for now, we should document the use of the updates-testing package for those wanting to boot f13 on f12 systems, i'll put a note in common bugs for both releases...
17:21:28 <jforbes> adamw: FWIW, most people running F12 wont need the update either.
17:21:37 <adamw> ah ok
17:21:56 <adamw> what's the specific circumstance here, then?
17:22:10 <jforbes> adamw: jlaska is one of a very small number who run 32bit kvm hosts... It hasn't been seen or reported on 64bit
17:22:23 <Oxf13> oh right
17:22:36 <Oxf13> this is 32bit kvm host stuff, which at one point wasn't even supported
17:23:38 <adamw> ohh, right.
17:23:46 <adamw> so it's only if you're running a 32-bit f12 host. gotcha.
17:23:59 <adamw> ok, i think that's everything...thanks jforbes :)
17:24:16 <jforbes> NP
17:24:40 <adamw> Oxf13: so would you agree we can drop this a blocker as it's a) a corner case and b) workaroundable now?
17:24:47 <Oxf13> yeah
17:24:49 <adamw> okey dokey
17:25:07 <adamw> #agreed 572215 is not a blocker: it affects only 32-bit kvm hosts (corner case) and is workaroundable with a candidate update
17:25:17 <adamw> #action adamw to document use of updates-testing package in f12 common bugs page for those affected
17:25:39 <adamw> well, that's the end of the list, i believe
17:26:12 <adamw> any other bugs to bring up? i don't have any
17:26:46 <Oxf13> what do the test results look like for RC1 thus far?
17:27:42 <Oxf13> https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
17:27:43 <Oxf13> and
17:27:50 <Oxf13> https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
17:28:21 <adamw> haven't been able to do the desktop testing yet
17:28:32 <adamw> i would be surprised if the results differ from tc1, but hey, that's why we do the testing :)
17:29:11 <adamw> we have a failure in https://fedoraproject.org/wiki/QA/TestCases/KickstartKsHttpServerKsCfg logged by liam, with no associated bug report
17:29:32 <adamw> other than that, no failures we haven't already discussed
17:30:45 <Oxf13> nod
17:32:04 <adamw> might be worth dropping a quick email to liam to ask about that failure
17:32:05 <adamw> i can do that
17:32:20 <adamw> #action adamw to check in with lili about the failure he logged in https://fedoraproject.org/wiki/QA/TestCases/KickstartKsHttpServerKsCfg
17:32:58 <adamw> okay then...i think we're done here?
17:33:07 <Oxf13> yeah, we'd need ot know what ks he used and whether it had graphical listed or not in the ks
17:33:10 <Oxf13> I think so too
17:35:39 <adamw> alrighty
17:35:42 <adamw> thanks
17:35:46 <adamw> #endmeeting