15:01:09 #startmeeting Prioritized bugs and issues 15:01:09 Meeting started Wed Oct 21 15:01:09 2020 UTC. 15:01:09 This meeting is logged and archived in a public location. 15:01:09 The chair is bcotton_. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:09 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:09 The meeting name has been set to 'prioritized_bugs_and_issues' 15:01:10 #meetingname Fedora Prioritized bugs and issues 15:01:10 The meeting name has been set to 'fedora_prioritized_bugs_and_issues' 15:01:21 #topic Purpose of this meeting 15:01:22 #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:24 #info The main goal is to raise visibility of bugs and issues to help contributors focus on the most important issues. 15:01:25 #link https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/#_process_description 15:01:28 #topic Roll Call 15:01:51 * cyberpear listens in 15:02:07 welcome, cyberpear! 15:05:44 * bcotton_ nudges mattdm 15:05:58 bcotton_ I'm busy talking to you in another channel! 15:06:28 if we're not talking in at least three separate conversations, are we even talking? 15:06:38 #topic Nominated bugs 15:06:40 #info 2 nominated bugs 15:06:41 #link https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__&f1=flagtypes.name&f2=OP&list_id=10871664&o1=substring&query_format=advanced&v1=fedora_prioritized_bug%3F 15:06:46 #topic glibc: Back out glibc-rhbz1869030-faccessat2-eperm.patch workaround for systemd UAPI breakage 15:06:48 #link https://bugzilla.redhat.com/show_bug.cgi?id=1869030 15:07:53 mhroncok: you nominated this one 15:08:00 does this even need our attention? looks like it's moving forward 15:08:11 or do we just want to highlight it as important? 15:08:14 it does seem important 15:08:20 bcotton_: have I? 15:08:39 mhroncok: so says bugzilla 15:08:42 * mhroncok is on the fesco meeting at the same time, sorry 15:09:09 * bcotton_ understands :-) 15:09:11 bcotton_: Error 500 - Internal Server Error 15:09:18 bcotton_: so says bugzilla 15:09:22 no bugs, everyone go home! 15:10:33 I'm already home! 15:11:20 so if i understand it correctly, we're carrying a patch in glibc that needs to be backed out, but we can't yet because it breaks copr and mock if we do? 15:12:13 bugzilla loaded 15:12:20 * mhroncok reads 15:13:03 so, let's accept this as prioritized, and then if the copr people don't see that thread in a couple of days nudge them? 15:13:03 oh! 15:13:15 also this was proposed as a prioritized bug before it was fixed 15:13:20 basically the bug got repurposed 15:13:39 oh that's cheating :) 15:13:47 -1 from me 15:14:07 thsi was fixed in fedora 15:14:12 it was reopened for rhel purposes 15:14:17 no longer rioritized for fedora 15:14:24 *prioritized 15:14:47 my flag was just a leftover 15:15:05 yeah -1 on that now 15:15:28 technically, I'd like to simply withdraw my proposal :) 15:15:41 sure :) 15:15:41 but bugzilla won't let me apparently. 15:15:46 #info mhroncok withdraws the prioritized proposal since the behavior was fixed 15:15:49 easy enough! 15:16:04 (i can clear the flag on it) 15:16:07 #topic [Rawhide/Fedora33] gcc crashes at brew during Firefox build 15:16:08 #link https://bugzilla.redhat.com/show_bug.cgi?id=1886399 15:16:34 note that this is apparently not the same gcc/Firefox bug(s?) as we've discussed in the past 15:16:50 this is fixed 15:16:55 updates pending 15:17:51 ok, so we can accept it for an easy win on our stats? :) 15:18:16 i'm okay with that. it's always the possible the fix didn't actually fix :-) 15:19:16 sure 15:19:25 +1 then :) 15:19:25 +1 to prioritize this 15:19:34 proposed #agreed 1886399 - Accepted as a prioritized bug in case the pending fix is insufficient. Building Firefox is important. 15:20:56 that's a yes, okay 15:20:57 ack 15:21:00 #agreed 1886399 - Accepted as a prioritized bug in case the pending fix is insufficient. Building Firefox is important. 15:21:18 #topic Accepted bugs 15:21:20 #info 0 accepted bugs 15:21:21 #link https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__&f1=flagtypes.name&f2=OP&list_id=10871665&o1=substring&query_format=advanced&v1=fedora_prioritized_bug%2B 15:21:24 technically no longer correct, but whatever :-) 15:21:29 heh 15:21:37 #topic Prioritized bugs fixed from last meeting 15:21:39 Just a quick review to remind ourself that this process works sometimes 15:21:40 #info [Fedora Media Writer] Does not work on macOS Catalina - https://bugzilla.redhat.com/show_bug.cgi?id=1840663 15:21:42 #info [Rawhide] gcc crashes at brew during Firefox build - https://bugzilla.redhat.com/show_bug.cgi?id=1862029 15:21:48 yay fixed bugs! 15:21:59 #topic Next meeting 15:22:00 #info We will meet again on 4 November at 1500 UTC in #fedora-meeting 15:22:11 bcotton_ I have a metatopic 15:22:26 #topic open floor 15:22:29 mhroncok: metatopic away! 15:22:40 so, we have this FTBFS policy in Fedora 15:22:50 #link https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ 15:23:28 I know there are some packages that will be affected by point 8 in couple months 15:23:40 "Cca a week before the Fedora N mass branching, packages that weren’t successfully rebuilt at least in Fedora N-2 will be retired" 15:24:10 #link https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb 15:24:39 is it applicable to mark a FTBFS bug prioritized when I know that the retirement would negatively impact Fedora? 15:25:15 i'd say yes. 15:25:33 as an example, https://bugzilla.redhat.com/show_bug.cgi?id=1863143 15:25:58 there might not be anything that can be done about it, but at least it could help find new maintainers to fix it 15:26:32 for example, when I attempted to prioritize shim FTBFS, it was rejected IIRC 15:27:03 shim got a policy exception instead... to avoid retirement 15:27:26 that sounds right and i think the reasoning was "it's not actually a problem, it's just a policy edge case" 15:28:02 this one is more on the "it's a problem" end of the spectrum, even though xen is no longer a blocking test case, iirc 15:28:22 but in general, nominating a bug is free, so i'd err on the side of nominating 15:28:30 ok, let me propose it 15:29:09 do you want us to come back around and consider it right now, or take care of it in 2 weeks like normal? 15:29:11 and we can go right away voting or wait for the next meeting, whatever works for you. it's important, but not urgent (yet) 15:29:17 :D 15:29:28 okay, i'll go with the "let's wait until next time" 15:29:33 ack 15:29:42 that gives a chance for the maintainer to respond to the proposal, etc 15:30:24 anything else for this time around? 15:30:32 not from me 15:30:38 thanks bcotton_! 15:30:42 and mhroncok 15:30:45 bcotton++ 15:31:07 Great! Thanks everyone, and I'll see you all in two weeks 15:31:10 #endmeeting