17:00:12 #startmeeting F24-blocker-review 17:00:12 Meeting started Mon Nov 23 17:00:12 2015 UTC. The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:12 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:12 The meeting name has been set to 'f24-blocker-review' 17:00:13 #meetingname F24-blocker-review 17:00:13 #topic Roll Call 17:00:13 The meeting name has been set to 'f24-blocker-review' 17:00:35 * roshi is here 17:00:39 finally, another meeting 17:00:40 ahoyhoy folks, it's time for more meeting fun with me (cries secretly) 17:00:46 kparal: isn't this just the BEST 17:00:54 #chair kparal roshi 17:00:54 Current chairs: adamw kparal roshi 17:00:59 * pschindl is here 17:01:28 * pschindl has to switch from cable to wifi 17:02:38 #topic Introduction 17:02:38 Why are we here? 17:02:38 #info Our purpose in this meeting is to review proposed blocker and nice-to-have bugs and decide whether to accept them, and to monitor the progress of fixing existing accepted blocker and nice-to-have bugs. 17:02:38 #info We'll be following the process outlined at: 17:02:40 #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 17:02:40 #info The bugs up for review today are available at: 17:02:43 #link http://qa.fedoraproject.org/blockerbugs/current 17:02:44 #info The criteria for release blocking bugs can be found at: 17:02:46 #link https://fedoraproject.org/wiki/Fedora_24_Alpha_Release_Criteria 17:02:48 #link https://fedoraproject.org/wiki/Fedora_24_Beta_Release_Criteria 17:02:50 #link https://fedoraproject.org/wiki/Fedora_24_Final_Release_Criteria 17:03:03 #info 2 Proposed Alpha Blockers, 3 Proposed Final Blockers 17:03:11 #info 1 Accepted Alpha Blocker 17:03:15 #info 0 Proposed Freeze Exceptions 17:03:15 #info 0 Accepted Freeze Exceptions 17:03:29 who wants to secretarialize? 17:04:22 I don't want to, but I will do it :) 17:05:02 thanks pschindl 17:05:11 #info pschindl will secretarialize 17:05:26 starting with the Alpha proposals: 17:05:27 #topic (1283348) Black screen on KDE live session (with qemu-kvm) 17:05:27 #link https://bugzilla.redhat.com/show_bug.cgi?id=1283348 17:05:27 #info Proposed Blocker, plasma-workspace, NEW 17:06:00 this sounds like what satellit was talking about in the QA meeting 17:06:08 +1 17:06:24 on the face of it, it sure sounds blocker-y, would be good to reproduce on bare metal too 17:06:51 +1 17:07:14 i'm gonna vote +1 on the assumption it's not KVM-specific, we can revisit if it turns out to be more limited than it seems 17:07:36 +1 to that too 17:07:46 +1 17:08:25 proposed #agreed 1283348 - AcceptedBlocker (Alpha) - this looks like a violation of "All release-blocking images must boot in their supported configurations." 17:08:47 ack 17:08:56 ack 17:09:03 ack 17:09:06 #agreed 1283348 - AcceptedBlocker (Alpha) - this looks like a violation of "All release-blocking images must boot in their supported configurations." 17:09:12 #topic (1264364) During installation there is no dns-server set: systemd-tmpfiles creates /etc/resolv.conf as a broken symlink, NetworkManager does not overwrite it 17:09:12 #link https://bugzilla.redhat.com/show_bug.cgi?id=1264364 17:09:12 #info Proposed Blocker, systemd, NEW 17:09:46 huh, this was one i was batting around a lot with NM/systemd folks a few weeks back, but not sure of current status 17:10:04 * satellit afk 17:11:06 +1 17:11:20 though, I'm not sure where the best place to fix this is 17:11:22 well, this doesn't seem to happen in a 2015-11-19 nightly 17:11:29 +1 17:11:35 network works there, /etc/resolv.conf is a symlink to NM's file 17:11:46 i'm not sure who changed what, so i can look into it, but i'd suggest punting this for now... 17:12:25 I'm fine with punting 17:12:34 ok 17:13:24 proposed #agreed 1264364 - punt (delay decision) - this is/was a bad bug, but does not seem to be affecting current nightly images; adamw will investigate what changed and see if bug needs to remain open 17:13:42 ack 17:15:03 any other acks? 17:15:31 ack 17:15:34 ack 17:15:36 :) 17:15:42 ack 17:15:45 #agreed 1264364 - punt (delay decision) - this is/was a bad bug, but does not seem to be affecting current nightly images; adamw will investigate what changed and see if bug needs to remain open 17:15:53 alright, onto Final blockers 17:16:00 #topic (1283365) Can't launch gnome-abrt (ImportError: cannot import name 'HTMLParseError') 17:16:00 #link https://bugzilla.redhat.com/show_bug.cgi?id=1283365 17:16:01 #info Proposed Blocker, gnome-abrt, POST 17:17:06 +1 17:17:15 +1, sounds like it affects workstation 17:17:20 +1 17:17:40 +1 17:18:21 proposed #agreed 1283365 - AcceptedBlocker (Final) - clearly violates "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test." 17:18:31 ack 17:18:45 ack 17:19:24 kparal: ? 17:19:30 ack 17:19:31 #agreed 1283365 - AcceptedBlocker (Final) - clearly violates "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test." 17:19:32 #topic (1278562) sealert's GUI doesn't work 17:19:32 #link https://bugzilla.redhat.com/show_bug.cgi?id=1278562 17:19:33 #info Proposed Blocker, setroubleshoot, NEW 17:20:06 +1 17:20:29 +1, i can reproduce this here (doesn't look like a py3.5 issue as i'm still on 3.4) 17:21:14 +1 17:21:18 proposed #agreed 1278562 - AcceptedBlocker (Final) - clearly violates "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test." 17:21:37 ack 17:21:40 ack 17:22:30 roshi: ? 17:22:45 ack 17:22:51 #agreed 1278562 - AcceptedBlocker (Final) - clearly violates "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test." 17:22:58 #topic (1276432) [abrt] yelp: init_compose_table_thread_cb(): yelp killed by SIGSEGV 17:22:58 #link https://bugzilla.redhat.com/show_bug.cgi?id=1276432 17:22:58 #info Proposed Blocker, yelp, NEW 17:23:32 +1 17:23:37 wasn't this fixed already? 17:23:40 +1 anyhow 17:23:43 +1 17:24:37 we 'fixed' it in f23 by downgrading yelp 17:24:41 f24 still has the broken yelp 17:24:50 so, seems like a +1 indeed. 17:25:20 proposed #agreed 1276432 - AcceptedBlocker (Final) - clearly violates "Any element in the installer interface(s) which is clearly intended to display 'help' text must do so correctly when activated." 17:25:28 ack 17:25:35 ack 17:25:58 ack 17:26:21 #agreed 1276432 - AcceptedBlocker (Final) - clearly violates "Any element in the installer interface(s) which is clearly intended to display 'help' text must do so correctly when activated." 17:26:32 alrighty folks, that's all the proposals on the list 17:26:47 shall we wind up in record time? 17:26:50 #topic Open floor 17:26:57 any other f24 / blocker related business? 17:27:04 I wonder if we're not having the blocker bug meetings a bit too soon? most of these issues will be resolved in a few weeks anyway, and f24 branch is in february. how early did we start having blocker bug meetings for f23? 17:27:18 * roshi has nothing 17:27:24 i figured we may as well start so long as we had proposals 17:27:33 early meetings are short and it stops us having a backlog if we start later 17:27:56 Better to spend 30 minutes now than 3 hours in month 17:28:19 that was my thinking, yeah 17:28:23 this is true 17:28:31 it worked pretty well the last cycle 17:28:32 I do not oppose it, just wondered if it wouldn't better to start e.g. 1 month ahead of branch 17:29:15 if you think this is beneficial, no problem 17:29:43 personally i'm ok with a quick meeting whenever there's say >1 proposed blocker, but we could do it on a schedule basis too... 17:29:53 we can kick it around on list if anyone wants to change, i guess 17:29:59 for now, i think some of us have a phone call to be on :P 17:30:39 ok, just wanted to hear your opinions 17:30:42 that's all from me 17:30:59 * adamw doesn't really mind either way. 17:31:42 alrighty, i know this will make kparal sad, but we don't have any more meetings this morning 17:32:05 it's okay though, kparal. it's okay, you can make it. 17:32:08 * adamw sets the fuse 17:32:37 I'll manage somehow 17:33:26 thanks for coming, folks! 17:33:29 #endmeeting