16:00:46 #startmeeting Fedora 13 Alpha blocker bug meeting #2 16:00:46 Meeting started Fri Feb 12 16:00:46 2010 UTC. The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:47 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:54 #topic blockerbug 16:01:00 grr 16:01:39 #topic welcome 16:01:43 who's around? 16:01:52 * akia is here 16:01:53 I'm here ... finishing up another meeting 16:03:00 well, let's dive in I guess 16:03:24 working off https://bugzilla.redhat.com/showdependencytree.cgi?id=538273&hide_resolved=1 16:03:37 #topic https://bugzilla.redhat.com/show_bug.cgi?id=555526 16:04:24 this seems like something that should be fixed quickly (as it may be breaking the build of several packages), but I don't see why it should block the alpha 16:04:51 well... 16:04:57 if there was an alpha-blocking bug in another package that couldn't be rebuilt because of this bug, maybe it would indirectly block it, but otherwise... 16:07:32 does anybody know why it's an alpha-blocking bug? 16:07:47 doesn't seem to have been any rationale provided 16:08:16 set by the reporter, on feb 10th 16:09:24 he's a packager, it seems, but I can't find an IRC nick for him 16:09:54 jlaska: any opinion on this one? 16:10:32 my other meeting just ended. I'm back now 16:10:38 reading .. 16:11:46 I don't have context on this one 16:11:56 shall we request more info, then move it? 16:12:03 * maxamillion is kinda here (late ... of course) :/ 16:12:06 (if appropriate) 16:12:07 heya maxa 16:12:13 * jlaska tips hat 16:12:21 hi hi 16:12:26 yeah I think we can drop it from the blocker list with a note to re-add it with rationale if desired 16:12:29 adamw: I don't see why that's an alpha blocker 16:12:52 okay 16:12:59 who wants to be Bug Secretary For The Day? 16:13:15 (do all the bug updates that we agree on) 16:13:36 * maxamillion *would* volunteer, but is trying to multitask with $dayjob tasks and would probably miss things 16:13:50 i'll do it then :) 16:13:53 adamw: I'll be happy to take a few, not fast enough to take all 16:13:57 I'll grab this one 16:14:16 #agreed 555526 will be dropped from the blocker list as there's no clear reason why it should block alpha release, it does not meet any criteria 16:14:42 #topic https://bugzilla.redhat.com/show_bug.cgi?id=557386 16:14:49 this is the abrt-borkage bug we discussed last week 16:14:58 it's in progress atm 16:15:31 i've just pinged jmoskovc for an update 16:16:42 that one could be seen as an alpha blocker but might not be ... where are the alpha requirements again? 16:16:51 maxamillion: we already went over it last week and decided it was 16:18:13 ah ok, sorry ... I must have missed that one :( 16:18:38 jmoskovc says he expects to have it done in time for alpha 16:19:00 no action needed here I think... 16:19:32 so it stays where it lays 16:20:11 #agreed 557386 is being worked and should be done in time according to jmoskovc, no action needed 16:20:26 #topic https://bugzilla.redhat.com/show_bug.cgi?id=558318 16:20:38 tech33 kindly provided a couple of nouveau bugs for us :) 16:20:49 yay! 16:20:54 i think he intended to be around to discuss them but he's not, so I'll do my best... 16:21:35 okay, few problems with this: we don't know how many systems it affects (historically we haven't added single-adapter 'x fail' bugs as blockers) and it's on f12, not rawhide 16:22:12 i agree... 16:22:28 three, it doesn't actually appear to be fatal, just a failure to clear the screen which shouldn't really be a problem except gdm apparently has a bug too. so it's workaround-able by not using gdm, I guess 16:22:32 I'mhere 16:22:34 sorry for being late 16:22:36 hi oxf13 16:23:32 ...so it's not critical 16:23:56 yeah 16:24:17 so i'm leaning towards dropping this for now with an explanation, we could ask if the reporter feels like testing with an f13 nightly 16:24:48 +1 on dropping 16:24:53 good idea 16:25:14 okay, let's do that 16:25:39 #agreed 558318 does not seem to meet blocker criteria for now, it's against 12, seems to have an unlisted workaround, we don't know that it affects more than one user 16:25:55 #agreed 558318 will be dropped from list with explanation and request for further testing 16:27:56 #topic https://bugzilla.redhat.com/show_bug.cgi?id=560444 16:28:01 here's the other one tech33 provided 16:29:41 again, doesn't meet the criteria for me - 12, single system, not even a function we've traditionally considered blocker-y in the past 16:29:47 just for me ... suspend to disk is also known as hibernate, right? 16:29:54 yes 16:29:57 i should mention to tech33 that we usually set suspend bugs as medium not high, actually 16:30:00 not quite 16:30:03 Oxf13: thx! 16:30:03 oh right yes 16:30:08 +1 for dropping as alpha blocker 16:30:09 there's lots of words :) 16:30:21 'suspend' = 'sleep' = 'write everything to RAM and shut down' 16:30:26 'suspend to disk' = 16:30:30 (not even sure if we're supposed to be doing the "+1 system" right now ... just kinda going with it) 16:30:35 'hibernate' = write everything to disk and shut down' 16:30:38 +1 is fine 16:30:44 rgr 16:30:51 not a blocker bug :) 16:31:06 #idea Do we need suspend/hibernate coverage on the release criteria? 16:31:14 #agreed 560444 does not meet blocker criteria, single-system and in a function (suspend) we don't usually consider blocking alpha 16:31:21 jlaska: it may be worth explicitly mentioning, yeah 16:31:22 suspend yes, not sure about hibernate, but probably 16:31:35 coverage yes, blocking for alpha no. Blocking for beta is a more interesting question 16:31:56 don't mean to derail things, just wanted to toss that in as food for thought 16:32:34 Oxf13: traditionally we haven't even blocked final for single-system suspend bugs 16:32:52 i think a bug which broke suspend for everyone would be worth blocking final and possibly beta for, but that's about it... 16:33:14 adamw: good to know 16:33:17 yeah, it certainly touches on https://fedoraproject.org/wiki/Blocker_Bug_FAQ#What_about_hardware_and_local_configuration_dependent_issues.3F 16:33:24 adamw: single system correct, it'd have to be more systemic 16:33:48 yeah, it's a hardware-dependent grey area thing 16:34:02 but we could put a little more explicit reasoning in there to help explain 16:35:07 #topic https://bugzilla.redhat.com/show_bug.cgi?id=560477 16:35:47 I recall we discussed this one last week and the action was just to make sure the fix got into a build 16:35:51 seems like no-one's tested yet 16:36:05 should be pretty simple to test 16:36:13 anyone want to volunteer to test it and close this off? 16:36:57 * jlaska raises hand 16:37:04 yay 16:37:14 I'll test the updates.img, but will hold off on closing until it's in the next build 16:37:18 #action jlaska to test the fix for 560477 and close off bug (assuming it's fixed) 16:37:31 #agreed 560477 just needs to be tested and confirmed fixed 16:38:05 #topic https://bugzilla.redhat.com/show_bug.cgi?id=562209 16:38:38 this was discussed and accepted as a blocker last week, looks like installer folk are working on it 16:39:17 i've pinged clumens but he's listed as away right now 16:39:48 I don't know if we're closer on this ... kamil is looking for ways to reproduce this outside of anaconda (or inside but with more debugging) 16:39:51 jlaska: were you able to reproduce? 16:40:07 this certainly needs a re-test once I get new images in place 16:40:13 right on 16:40:22 it's easy to reproduce using previous images 16:40:27 just boot the boot.iso and try to install 16:40:34 oh, clumens said you couldn't reproduce 16:40:45 yeah, so it might be worth clarifying that 16:40:48 ah ... he posted a procedure to try to reproduce outside the installer 16:40:58 I tried that procedure, and it didn't reproduce the issue as we thought 16:41:09 sorry, mixed it up there 16:42:16 ah, ok. 16:42:23 so I still think this affects the alpha rel. crit. 16:42:28 yeah 16:42:34 i'm not sure what action we can take 16:42:37 besides cracking the big whip 16:42:44 we'll certainly get updated test results on this in the coming week 16:44:08 ok 16:44:18 #agreed jlaska will continue to track and provide testing for 562209 16:44:39 #topic https://bugzilla.redhat.com/show_bug.cgi?id=563212 16:44:53 i threw this one in there, it's an intel bug which broke the driver for rather a lot of users 16:44:57 should already be fixed in -4, though 16:45:03 oh nice 16:45:35 just set to modified and asked people to test with -4 16:46:08 don't think there's any other action here 16:46:35 move on? 16:47:08 yeah 16:47:18 #agreed 563212 is likely fixed in -4, set to modified and await testing results 16:47:32 #topic https://bugzilla.redhat.com/show_bug.cgi?id=563348 16:47:56 this is the bug that broke rawhide boot because the syslogger wouldn't come up, heh 16:48:06 the patch seems to work... 16:48:32 yeah, and -6 has gone through koji 16:48:33 http://koji.fedoraproject.org/koji/buildinfo?buildID=155653 16:48:43 so we can set this MODIFIED and ask people to test and confirm, I guess 16:49:18 yes 16:49:44 anything else? 16:49:58 this is the issue many folks were hitting on the list yesterday right? 16:50:05 yes 16:50:14 and what was thought to be the original cause of our installer woes 16:51:54 adamw: can't think of anything else ... Oxf13's undup'd issue is being tracked elsewhere on the list 16:52:04 no, i just meant on this issue :) 16:52:15 none here 16:52:22 #agreed 563348 is a blocker, fix is going through rawhide, set to MODIFIED and ask for retesting 16:52:30 http://git.fedorahosted.org/git/?p=anaconda.git;a=commit;h=e8cdfc480ccec62cfb2b70598dd792bbab43a1b2 16:52:34 looks like it's in 16:52:45 this does bring up a question, but will raise outside this meeting 16:53:35 #topic https://bugzilla.redhat.com/show_bug.cgi?id=564103 16:53:58 new one from jlaska, smells like a blocker to me, yeah 16:54:33 yeah, I think this hits one of the criteria pretty good 16:54:36 I listed it at the end 16:54:43 "# The installed system must be able to download and install updates with 16:54:46 yum and PackageKit " 16:55:03 yeah 16:55:24 I was going to look into this one with the new images and see what's failing here, but well the new images failed 16:55:48 so I'm in full agreement that this is a blocker. It's indicative that something is going wrong with the @core and @base group installs 16:55:54 definitely a blocker bug... 16:55:55 and there is likely worse fallout 16:56:16 Oxf13: clumens indicated he found out what the problem was in a message earlier 16:56:21 oh! 16:56:22 so, action here? 16:56:23 but I haven't circled back with him yet 16:57:14 adamw: re: action, I don't think so ... just some devel time to assess the issue and work up a patch? 16:57:16 k, so this one just waits for input 16:57:49 now we have at least a couple reasons to want a new anaconda today 16:57:50 ok 16:58:08 #agreed 564103 constitutes a blocker, action currently on development team for investigation 16:58:32 #topic https://bugzilla.redhat.com/show_bug.cgi?id=564213 16:58:47 so this is the installer version of the syslog bug? 16:59:24 yep 16:59:45 so not much discussion needed really 17:00:01 I debugged, sent a patch, and committed the patch today 17:00:26 ok 17:00:42 Oxf13: full service baby! 17:00:45 #agreed 564213 is a blocker, oxf13 has prepared and committed a patch, next action is to confirm fix in a new anaconda build 17:01:02 ...and bang on one hour, we're through the list 17:01:02 nice 17:01:15 adamw: well done 17:01:43 So I'm going to wait for a new anaconda and then do a TC.1 17:01:56 Oxf13: okay 17:02:14 sounds good 17:02:26 anyone have any other bugs to discuss that weren't on the list? 17:02:33 nope 17:03:01 I have a few new ones that came out of the RATS#3 drop 17:03:07 but I don't believe those are Alpha blockers 17:03:11 more edge cases 17:03:25 so nothing from me 17:03:29 ok 17:03:54 let's call it a day then! 17:03:58 thanks for helping, everyone 17:04:45 thanks for leading Adam :) 17:06:03 #endmeeting