14:03:07 <bcotton> #startmeeting Prioritized bugs and issues
14:03:07 <zodbot> Meeting started Wed Jun  1 14:03:07 2022 UTC.
14:03:07 <zodbot> This meeting is logged and archived in a public location.
14:03:07 <zodbot> The chair is bcotton. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
14:03:07 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:03:07 <zodbot> The meeting name has been set to 'prioritized_bugs_and_issues'
14:03:08 <bcotton> #meetingname Fedora Prioritized bugs and issues
14:03:08 <zodbot> The meeting name has been set to 'fedora_prioritized_bugs_and_issues'
14:03:23 <bcotton> #topic Purpose of this meeting
14:03:24 <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.
14:03:32 <bcotton> #info The main goal is to raise visibility of bugs and issues to help  contributors focus on the most important issues.
14:03:33 <bcotton> #link https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/#_process_description
14:03:42 <bcotton> #topic Roll Call
14:04:06 <bittin> .hello bittin
14:04:07 <zodbot> bittin: bittin 'Luna Jernberg' <droidbittin@gmail.com>
14:05:15 <mattdm> hello!
14:06:06 <bcotton> welcome, one and all
14:06:19 <bcotton> i'll let the two of you decide which of you is one and which is all ;-)
14:06:29 <bittin> lol
14:06:42 <bcotton> #topic Common Bugs review
14:06:42 <bcotton> #info Let's start with a check of the Common Bugs pages for supported releases and see if any should be nominated as Prioritized Bugs
14:06:43 <bcotton> #link https://ask.fedoraproject.org/c/common-issues/141/none/l/latest?order=votes
14:07:02 <bcotton> bittin: don't laugh, it only encourages me :-D
14:08:59 <bcotton> none of these look particularly like we can do anything about them
14:09:03 <bittin> hm okay, NVIDIA drivers, scanners and printers
14:10:24 <mattdm> yeah, agreed.
14:11:08 <bcotton> #topic Nominated bugs
14:11:09 <bcotton> #info 1 nominated bug
14:11:09 <bcotton> #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
14:11:15 <bcotton> #topic Torsocks fails to work with ɪᴘv6 domain names.
14:11:15 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=2089005
14:13:05 <bcotton> so the requester thinks we should carry a patch to support this until upstream does, but apparently no such patch exists
14:13:44 <bittin> don't know enough about tor, but would it not be best to try to fix it upstream? so it can trickle down to all distros
14:14:03 <bcotton> it would
14:14:39 <bcotton> this isn't in common use and it's not a bug so much as a lack of feature upstream, imo
14:14:41 <bittin> maybe report the bug here: https://gitlab.torproject.org/tpo/core/torsocks/-/issues if someone has not done that already?
14:14:47 <bcotton> so i don't see a lot of justification for accepting it
14:14:57 <mattdm> yeah this is esoterica
14:15:32 * bittin agrees
14:16:12 <bcotton> proposed #agreed 2089005 is rejected as a prioritized bug. This is a feature for upstream to add support for
14:16:37 <mattdm> And... "upstream isn't active" isn't a good reason for Fedora to carry patches
14:16:41 <mattdm> Like, NEVER.
14:16:49 <mattdm> If the software isn't important, we should drop it.
14:16:58 <bcotton> it's probably a better reason to not carry a patch
14:17:10 <bittin> i guess its important for the people that want to be really anonymous, but better to have it fixed upstream then
14:17:13 <mattdm> If it is critical to us, we should work on invigorating the upstream.
14:18:55 <bcotton> i didn't hear any objections, so
14:18:59 <bcotton> #agreed 2089005 is rejected as a prioritized bug. This is a feature for upstream to add support for
14:19:05 <mattdm> ALso I see that the packager already said all this.
14:19:18 <mattdm> Let's phrase this in support of what they said
14:19:29 <mattdm> https://bugzilla.redhat.com/show_bug.cgi?id=2089005#c1
14:20:02 <bcotton> #undo
14:20:02 <zodbot> Removing item from minutes: <MeetBot.items.Link object at 0x7fe2d6664a58>
14:20:10 <mattdm> am writing hold on
14:22:08 <mattdm> #proposed We reviewed this at the Prioritized Bugs meeting and agree with Marcel that this doesn't qualify as a Fedora prioritized bug. Please work with upstream on this. As a general rule, Fedora does not want our packages to become long-lived forks. This is particularly important for security-sensitive software, where patches can introduce problems we might not fully understand.
14:22:33 <mattdm> (see the debian zero-entropy ssh key fiasco of yore)
14:22:57 <bcotton> ETOOMANYWORDS
14:23:29 <mattdm> lol ok
14:23:54 <mattdm> Proposed: first sentence, and I'll add the rest personally as my own color commentary :0
14:24:00 <mattdm> s/0/)/
14:24:24 <bcotton> proposed #agreed 2089005 is rejected as a prioritized bug.  (and then I'll add mattdm's text lightly edited afterward in support of that)
14:25:12 <mattdm> +1
14:25:13 <mattdm> works for me
14:25:17 <bcotton> #agreed 2089005 is rejected as a prioritized bug.  (and then I'll add mattdm's text lightly edited afterward in support of that)
14:25:33 <bcotton> #info mattdm's text: Please work with upstream on this. As a general rule, Fedora does not want our packages to become long-lived forks. This is particularly important for security-sensitive software, where patches can introduce problems we might not fully understand.
14:26:06 <bcotton> #topic Accepted bugs
14:26:06 <bcotton> #info 1 accepted bugs
14:26:07 <bcotton> #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
14:26:12 <bcotton> #topic Lenovo ThinkPad T490, unable to boot following clean install, stuck at splash screen
14:26:12 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=1955416
14:26:32 <bcotton> we were told early June for a signed shim and it's just now June, so I think it's a little early to poke this again
14:26:39 <bcotton> i'll follow up next week if there are no updates
14:26:56 <bittin> sounds good
14:27:12 <mattdm> yeah that poor team gets a lot of pokes
14:27:43 <bcotton> #topic Next meeting
14:27:43 <bcotton> #info We will meet again on 15 June at 1400 UTC in #fedora-meeting-1
14:27:49 <bcotton> anything else before we wrap this up?
14:28:05 <mattdm> I don't have anything. Thanks ben!
14:28:12 <bittin> nope i don't have anything thanks
14:29:00 <bcotton> woohoo!
14:29:02 <bcotton> #endmeeting