15:00:26 <bcotton> #startmeeting Prioritized bugs and issues 15:00:26 <zodbot> Meeting started Wed Mar 27 15:00:26 2019 UTC. 15:00:26 <zodbot> This meeting is logged and archived in a public location. 15:00:26 <zodbot> The chair is bcotton. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:26 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:26 <zodbot> The meeting name has been set to 'prioritized_bugs_and_issues' 15:00:28 <bcotton> #meetingname Fedora Prioritized bugs and issues 15:00:28 <zodbot> The meeting name has been set to 'fedora_prioritized_bugs_and_issues' 15:00:49 <bcotton> #topic Purpose of this meeting 15:00:51 <bcotton> #info The purpose of this process is to help with processing backlog of bugs and issues found during the development, verification and use of Fedora distribution. 15:01:05 <bcotton> #info The main goal is to raise visibility of bugs and issues to help contributors focus on the most important issues. 15:01:07 <bcotton> #link https://fedoraproject.org/wiki/Fedora_Program_Management/Prioritized_bugs_and_issues_-_the_process 15:01:15 <bcotton> #topic Roll Call 15:01:24 * bcotton will wait a few minutes to see who rolls in 15:02:06 <mattdm> bcotton: here I am! 15:02:16 <bcotton> hooray! 15:02:35 <bcotton> i did CC owners of all the relevant bugs, so i'll wait one more moment ot see if any of them arrive 15:04:15 <bcotton> #topic Nominated bugs 15:04:16 <bcotton> #link https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&classification=Fedora&keywords=Triaged&keywords_type=nowords&list_id=9195844&product=Fedora&query_format=advanced&status_whiteboard=PrioritizedBug&status_whiteboard_type=allwords 15:04:18 <bcotton> #info 2 nominated bug 15:04:30 <bcotton> #topic Custom UEFI layout with /boot/efi on second disk fails: is_valid_stage1_device not called on disks after the first 15:04:32 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=1168118 15:05:57 <mattdm> Huh, that has more interest and attention than I would have guessed from the summary 15:06:20 <bcotton> yeah, it's a little undersold 15:07:22 <mattdm> alright +1 15:07:46 <bcotton> agreed 15:07:59 <bcotton> #agreed BZ 1168118 is accepted as a PrioritizedBug 15:08:09 <bcotton> now how do we prioritize it? :-) 15:08:45 <mattdm> not really sure of anaconda team's preferred process. 15:09:05 <mattdm> I guess post to anaconda-devel-list@redhat.com as first step? 15:09:36 <bcotton> i'll ask sir mix-a-lot 15:09:56 <bcotton> #action bcotton to contact anaconda team about this bug 15:10:00 <mattdm> bcotton++ 15:10:17 <bcotton> #topic [abrt] hexchat: fatal_error(): hexchat killed by SIGABRT 15:10:18 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=1632039 15:11:41 <bcotton> this one sucks, but it's an upstream bug and not a core feature, imo 15:11:49 <mattdm> Is this a general bug in python or smoething, or just this one irc client? 15:12:05 <mattdm> do we promote or feature that particular client anywhere? 15:12:54 <mattdm> I'm pretty sure the answer is 'no'. With that *and* in combination with the fact that it's on track to get fixed upstream, I'm -1 15:13:34 <bcotton> it seems to be in that particular client from what i read in the upstream bug 15:13:43 <bcotton> #link https://github.com/hexchat/hexchat/issues/2237 15:13:43 <mattdm> if the maintainer doesn't respond after a bit, the non-responsive maintainer process is probably the best one 15:14:13 <bcotton> yeah. and i'm not sure what the maintainer can do until upstream is fixed (assuming the maintainer isn't an upstream dev) 15:15:16 <bcotton> #agreed BZ1632039 is rejected as a prioritized bug 15:15:28 <bcotton> #topic Accepted bugs 15:15:29 <bcotton> #link https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&classification=Fedora&keywords=Triaged&keywords_type=allwords&list_id=9195442&product=Fedora&query_format=advanced&status_whiteboard=PrioritizedBug&status_whiteboard_type=allwords 15:15:31 <bcotton> #info 2 accepted bugs 15:15:41 <bcotton> #topic Require all other updates to be installed before allowing to start system upgrade 15:15:43 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=1336435 15:15:44 <bcotton> #info BZ 13364535 was accepted on 2017-08-02 15:15:52 <bcotton> so i'm inclined to drop this one 15:16:04 <bcotton> i think it's important, but i don't think we can force some kind of resolution 15:16:20 <mattdm> yeah. :( 15:16:24 <mattdm> "We tried" 15:16:34 <bcotton> pretty much 15:16:41 <mattdm> I think also that the solution is going to be "silverblue sidesteps this" 15:17:06 <bcotton> #agreed BZ13364535 is dropped as a PrioritizedBug because we do not see a path forward to drive a resolution 15:17:09 <bcotton> yup 15:17:36 <bcotton> #topic Plymouth doesn't echo LUKS keypresses or show boot progress with amdgpu+LUKS 15:17:38 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=1490490 15:17:47 <bcotton> #info Bug filed upstream 15:17:48 <bcotton> #link https://bugs.freedesktop.org/show_bug.cgi?id=109282 15:17:50 <bcotton> #info A test build is available which addresses at least part of the problem 15:18:04 <mattdm> and no feedback 15:18:14 <bcotton> yup 15:18:31 <bcotton> #action bcotton to NEEDINFO reporter 15:18:35 <mattdm> +1 15:19:36 <bcotton> #topic Next meeting 15:19:37 <bcotton> #info We will meet again on 10 April at 1500 UTC in #fedora-meeting 15:19:43 <bcotton> anything else? 15:20:58 <mattdm> I'm good :) 15:21:02 <bcotton> hooray! 15:21:03 <bcotton> #endmeeting