17:00:00 #startmeeting FESCO (2023-10-19) 17:00:00 Meeting started Thu Oct 19 17:00:00 2023 UTC. 17:00:00 This meeting is logged and archived in a public location. 17:00:00 The chair is mhayden. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:00 The meeting name has been set to 'fesco_(2023-10-19)' 17:00:00 Meeting started Thu Oct 19 17:00:00 2023 UTC. 17:00:00 This meeting is logged and archived in a public location. 17:00:00 The chair is mhayden. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 17:00:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:01 The meeting name has been set to 'fesco_(2023-10-19)' 17:00:05 #meetingname fesco 17:00:05 The meeting name has been set to 'fesco' 17:00:06 The meeting name has been set to 'fesco' 17:00:10 #chair nirik, decathorpe, zbyszek, sgallagh, mhroncok, dcantrell, mhayden, Conan_Kudo, Pharaoh_Atem, Son_Goku, King_InuYasha, Sir_Gallantmon, Eighth_Doctor, tstellar 17:00:11 Current chairs: Conan_Kudo Eighth_Doctor King_InuYasha Pharaoh_Atem Sir_Gallantmon Son_Goku dcantrell decathorpe mhayden mhroncok nirik sgallagh tstellar zbyszek 17:00:11 Current chairs: Conan_Kudo Eighth_Doctor King_InuYasha Pharaoh_Atem Sir_Gallantmon Son_Goku dcantrell decathorpe mhayden mhroncok nirik sgallagh tstellar zbyszek 17:00:15 #topic init process 17:00:25 .hello ngompa 17:00:25 Son_Goku: [hellomynameis ngompa] 17:00:26 Son_Goku: ngompa 'Neal Gompa' 17:00:29 .hello2 17:00:29 mhayden: [hellomynameis mhayden] 17:00:31 mhayden: mhayden 'Major Hayden' 17:00:35 that's different 17:00:40 πŸ€” 17:00:57 .hi 17:00:57 decathorpe: [hellomynameis decathorpe] 17:00:57 decathorpe: decathorpe 'Fabio Valentini' 17:01:12 feels like one of the zodbots want to issue me one of those sticky name tags that people wear at parties :) 17:01:31 .hello tstellar 17:01:31 tstellar: [hellomynameis tstellar] 17:01:34 tstellar: tstellar 'Tom Stellard' 17:01:42 .hello churchyard 17:01:42 mhroncok_web: [hellomynameis churchyard] 17:01:43 mhroncok_web: churchyard 'Miro Hrončok' 17:02:03 yay we have 5! i'll give it another minute or two 17:03:12 okay, let's move along :) 17:03:32 #topic #3059 F39 incomplete changes: 100% complete deadline 17:03:40 .fesco 3059 17:03:41 mhayden: [showticket https://pagure.io/fesco/issue/%s 3059] 17:03:41 mhayden: Issue #3059: F39 incomplete changes: 100% complete deadline - fesco - Pagure.io - https://pagure.io/fesco/issue/3059 17:03:46 what do we have left here 17:03:57 wow the bot isn't doing well here 17:04:04 what's with all the weird text 17:04:07 * mhayden patpats zodbot_ 17:04:21 Python 3.12 is CLOSED 17:04:27 was the matrix zodbot deployed to irc xD 17:04:46 mhroncok_web: it seems open for business on my machine 17:04:47 oh there are two zodbots 17:04:52 that's what's going on 17:04:52 :) 17:05:49 last update there from adam says the Cloud EC2 UEFI preferred and IMDSv2Only are already implemented but just weren't noted as such 17:06:18 is there somewhere an up-to-date list of things that are still in flight? 17:06:27 decathorpe: i was wondering the same 17:06:56 ah, there is a BZ query linked at the top 17:06:58 #link https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cbug_severity&f1=blocked&list_id=13304012&o1=substring&order=id%2C%20&query_format=advanced&v1=F39Changes 17:07:18 just four 17:07:36 SPDX looks ongoing with 43% converted 17:07:40 also the SPDX stuff is ongoing process that can just continue past F39 release date 17:08:00 Fedora in Azure will be done manually for a bit (thanks davedunc) until we get automation in place in F40 17:08:18 next if Flatpaks without modules 17:08:23 s/if/is/ 17:08:26 #link https://bugzilla.redhat.com/show_bug.cgi?id=2216764 17:08:43 flatpaks without modules seems to be progressing well, from what I can read in the matrix channels 17:09:02 sweet. owen makes a good point that they need people to be done with everything before they can make flatpaks :) 17:09:17 last is clean systemd-boot installs 17:09:19 #link https://bugzilla.redhat.com/show_bug.cgi?id=2233234 17:09:56 last updated September 22 17:10:33 looks like https://bugzilla.redhat.com/show_bug.cgi?id=2234638 is still open 17:11:00 but it's already marked as freeze excpetion 17:11:18 #link https://bugzilla.redhat.com/show_bug.cgi?id=2234638 17:12:27 though another bug for this was already closed: https://bugzilla.redhat.com/show_bug.cgi?id=2237327 17:12:28 last update there is Oct 8 but i can't tell if it's fixed or not 17:13:32 i'm not sure if there's anything for us to take action on with any of these (unless someone sees something i missed) 17:13:41 I suppose we shouldn't block the release on this, so either it's fixed with the freeze exception, or it isn't 17:13:44 or should we? 17:14:19 I'm inclined to agree with adamw here - "So in theory we can call the current state 'complete' based on the scope in the Change (...) so...I guess we can call this MODIFIED, for now?" 17:14:44 looks like there's still some bugs to be worked out, but the change itself seems done 17:15:54 I'd say so 17:17:06 ack 17:17:27 we also just got "Fedora Linux 39 Final is NO-GO (#2)" 22 minutes ago, so that gives everyone one more week to get things ironed out :D 17:17:36 😒 17:18:26 okay, anything else on this topic? 17:18:54 nope 17:19:32 so ... is there any Change that we still need to keep an eye on, or can we close the ticket for F39? 17:19:41 I don't think there's anything left to track 17:19:59 πŸ‘ 17:20:01 close it 17:20:09 #topic #3074 Change: SQLAlchemy 2 17:20:13 .fesco 3074 17:20:13 mhayden: [showticket https://pagure.io/fesco/issue/%s 3074] 17:20:14 mhayden: Issue #3074: Change: SQLAlchemy 2 - fesco - Pagure.io - https://pagure.io/fesco/issue/3074 17:20:38 Original author here was asked to revise the change request to remove the side-by-side part -- still have a -1 in the ticket left over from pre-revision 17:20:39 that seems approved 17:20:47 ah, we do 17:21:19 I think the intent was that reset after the amendments 17:21:21 i assume that was from the previous revision there but i didn't want to clear zbyzek's -1 without talking to him first 17:21:33 I see 17:21:35 +1 17:21:35 hum ... the stuff about the parallel-installable compat package is still in there? 17:21:41 oh this was an area where i couldn't find the rules on it and i wasn't sure what to do 17:21:52 decathorpe: no 17:22:04 the feedback section even explains that 17:22:19 "Originally, it was proposed that the compatibility package for version 1.4 would be installable in parallel, but in discussion it turned out the implementation would be technically complicated (an application would have to select which major version of SQLAlchemy to use on startup for which Python doesn’t have good tools, various approaches 17:22:19 would break RPM dependency tooling) and possibly a maintenance nightmare. " 17:22:37 haha, mhroncok_web and were both copying the same paragraph πŸ‘ 17:22:37 "A (conflicting) compatibility package python-sqlalchemy1.4..." 17:22:38 ah. the Summary part doesn't make that clear, but ok, that sounds good to me 17:23:07 +1 then 17:23:21 "this can be installed alternatively" is not typical thing to say, but I think it's correct 17:23:39 https://fedoraproject.org/w/index.php?title=Changes%2FSQLAlchemy_2&type=revision&diff=690656&oldid=689626 17:23:56 this changed "side-by-side" to "alternatively" 17:26:15 okay, well how about i ask zbysek to re-review in the ticket and clear his -1 if he's good with the new revision? 17:26:38 or we can approve it here 17:27:30 clearly, his intention wasn't to block this proposal entirely. "Procedural -1 to prevent auto-approval." 17:28:13 okay, let's do that here 17:28:22 Proposal: Voting on approval for change 3074 (SQLAlchemy 2) after its revision 17:28:57 +1 <- I voted this on the ticket too. 17:29:04 +1 (also in ticket) 17:29:58 +1 still 17:30:42 +1 17:30:48 decathorpe? πŸ˜‰ 17:31:13 +1 (sorry, had to step away from PC for a minute) 17:31:18 that's okay 17:31:36 #agreed Approved change 3074 for SQLAlchemy 2 (+5, 0, -0) 17:31:50 * mhayden always has difficulty remembering irc meeting commands πŸ€¦β€β™‚οΈ 17:32:10 #topic Next week's chair πŸͺ‘πŸͺ‘πŸͺ‘πŸͺ‘πŸͺ‘ 17:32:33 hoping someone would "sit" in for me next week as my Thursday is crazy busy 17:32:38 that would be chair-itable of you 17:32:39 I can probbaly πŸͺ‘ 17:32:52 *probably 17:33:02 * mhayden revels in mhroncok_web's usage of emojis πŸ₯° 17:33:11 I could do it too. 17:33:34 i'll have to ask y'all to arm wrestle now. that's how we solve it in Texas. 17:34:09 mhayden: Who gets to chair, the winner or the loser? 17:34:18 πŸ€” 17:34:27 * mhayden didn't think of that 17:34:54 mhroncok_web: would you do it and have tstellar as a backup in case you're busy? 17:34:59 ack 17:35:03 thanks! 17:35:16 #action mhroncok_web to chair next week's meeting and have tstellar as a backup if something comes up 17:35:22 mhroncok_web++ 17:35:26 tstellar++ 17:35:26 mhayden: Karma for tstellar changed to 1 (for the release cycle f39): https://badges.fedoraproject.org/tags/cookie/any 17:35:33 #topic Open Floor 17:35:57 anything anyone wants to talk about? 🍿 17:36:16 Do we need to re-vote on the -fno-omit-frame-pointer change for F40? 17:36:37 I forgot all about it 17:36:44 πŸ‘€ 17:37:29 #link https://fedoraproject.org/wiki/Changes/fno-omit-frame-pointer 17:37:35 not sure about re-vote, IIRC we just said "re-evaluate" 17:37:40 #link https://pagure.io/fesco/issue/2923 17:37:59 ah, yes. "FESCo will evaluate whether to retain it by Fedora Linux 40" 17:38:45 i'll open a ticket in pagure as a reminder and link back to the old tickets -- that's a good reminder tstellar 17:39:54 good idea, we are not going to evaluate that here 17:40:16 #link https://pagure.io/fesco/issue/3084 17:40:24 ⬆️ ticket made for us to review 17:41:10 okay, anything else for the open floor? 17:41:26 πŸ‘‹ zbyszek 17:41:41 hi zbyszek. we approved the sqlalchemy change here assuming your -1 was strictly procedural. the requested changes have been made 17:41:44 Hi, sorry, I went to my grandma's birthday and lost track of time. 17:41:49 somebody approached FPC with a problem of an "unresponsive" but "active" maintainer 17:41:55 https://pagure.io/packaging-committee/issue/1312 17:41:56 mhroncok_web: yes, sounds good. 17:42:05 not sure what can / should be done here 17:42:16 decathorpe: honestly, I'd retire that package 17:42:35 too bad the updates weren't stopped in time 17:43:19 I agree. but it's still disheartening that the maintainer hasn't responded to either bugmail, bodhi-mail, nor direct messages in *weeks* 17:43:47 disheartening? disquieting? words are failing me today 17:44:09 decathorpe: normal? 17:44:15 * zbyszek runs away 17:44:36 * decathorpe cries 17:44:54 typically in such cases, I start a nonresponsive maintainer process and they feel offended :shrug: 17:45:11 been there, done that. it's what we have 17:45:24 In this particular case, the package should be retired. I don't think we need to do anything else. 17:45:29 Regardless of if the maintainer is active or not, it's pretty clear that adding this package was a bug. 17:45:48 Exactly. It was a bug, let's fix the bug and move on. 17:46:06 ok, so I can add a comment with a fesco-go-ahead for the package retirement? 17:46:15 Yes please. 17:46:31 decathorpe: πŸ‘ 17:46:47 anything else on the open floor or are we all set? my belly is rumbling. πŸ˜‹ 17:47:17 will do, thank you 17:47:18 * mhroncok_web is eating as we type, feel guilty 17:47:25 *feels 17:47:28 * mhroncok_web hides 17:47:35 i hope you feel full! 😜 17:47:51 I had dinner before the FPC meeting ;) 17:47:54 anyway. endmeeting? 17:48:52 indeed 17:48:54 thanks y'all! 17:48:57 #endmeeting