16:01:01 #startmeeting ELN (2023-08-11) 16:01:01 Meeting started Fri Aug 11 16:01:01 2023 UTC. 16:01:01 This meeting is logged and archived in a public location. 16:01:01 The chair is sgallagh. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:01:01 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:01:01 The meeting name has been set to 'eln_(2023-08-11)' 16:01:01 #meetingname eln 16:01:01 The meeting name has been set to 'eln' 16:01:01 #topic Init Process 16:01:09 .hi 16:01:09 .hi 16:01:10 neil: Something blew up, please try again 16:01:13 sgallagh: Something blew up, please try again 16:01:16 neil: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:01:19 sgallagh: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:01:21 f 16:01:24 we broke it 16:01:46 It happens 16:01:55 .hello sgallagh 16:01:57 sgallagh: Something blew up, please try again 16:02:00 sgallagh: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:02:08 <-- Stephen Gallagher 16:02:16 <-- Neil Hanlon 16:04:04 * neil sent a message to fedora infra team on Matrix about zodbot, in case that is helpful 16:04:14 .hello 16:04:14 yselkowitz: (hello ) -- Alias for "hellomynameis $1". 16:04:16 .hi 16:04:17 yselkowitz: Something blew up, please try again 16:04:20 yselkowitz: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:04:23 .hello yselkowitz 16:04:24 yselkowitz: Something blew up, please try again 16:04:27 yselkowitz: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:04:31 yea, it's a bit broke right now yselkowitz 16:05:17 OK, it's five-past, so let's get started 16:05:50 #topic General status post-F39 branching 16:06:10 It's been a rough couple weeks for ELN. 16:06:52 The Content Resolver got broken by the end of Modularity and the Branching had some signing issues so we haven't had a valid compose this week 16:07:13 We finally fixed the signing issues and then the ODCS broke down. That just got fixed in the last hour. 16:07:29 ouch 16:07:32 * neil sends virtual hugs 16:07:36 Now we just need to catch up on some compose changes (specifically the rework of the firmware packages) 16:07:51 plus firefox builds have hung, so dependencies have spiked by 300+ rust crates due to the rawhide build 16:08:11 double ouch :\ 16:08:13 @yselkowitz I can untag it if you want 16:08:20 is there anything someone like me can do to help with any of this? 16:08:28 I don't know: who are you? :) 16:08:33 <-- Neil Hanlon ;) 16:09:01 I meant, what are your specialities? :) 16:09:42 breakin' shit, unbreakin' shit, spending hours trying to figure out why packages fail to build for no apparent reason 16:10:07 i'm most familiar with python stuff on the packaging side, but I get my hands dirty in all of it due to working on Rocky 16:10:34 neil: if you want to look into the *unchecked* items at https://github.com/fedora-eln/eln/issues/153 there are a few python-related failures there 16:11:34 okay cool, thank you 16:13:40 yselkowitz: Firefox doesn't have a circular build, does it? I should be able to just untag it and let the CR settle, I think 16:13:40 Of course, this will stop being necessary once we get ELNBuildSync into production. 16:13:40 sgallagh, no, and I just untagged it 16:13:40 (Hey look, a segue!) 16:13:40 #topic ELNBuildSync rewrite progress 16:14:04 I'm happy to report that I'm super-close to the MVP (minimum viable product) for ELNBuildSync 16:15:38 There are three remaining big tasks: 16:15:38 1) Figure out how to get to the built SRPM NVR from a Koji task ID (not a build_id...) 16:16:10 2) Get it plugged into the Fedora Infra postgresql to retain state if the process crashes or otherwise gets terminated. 16:16:23 3) Deploy it to our OpenShift instance 16:17:26 I may get to the deployment stage before the DB stuff is all finished, if only for expediency. 16:17:52 I've been trying to be much more defensive in my programming, so it's far less likely to crash than the old DistroBuildSync tool. 16:18:22 But we will see how that progresses over the next week. 16:18:30 EOM 16:18:58 Actually, if anyone out there is reading this and happens to have an easy answer for 1), I'd love to hear it! 16:20:25 >.> 16:20:30 <.< 16:21:15 OK, that was too much to hope for. 16:21:27 #topic Open Floor 16:21:41 @neil So... what brings you here today? 16:23:04 some good news: once composes start flowing again and Content Resolver settle down, ELN should drop below the 2500 package mark 16:23:49 from a peak of almost 4800 in March 16:25:35 * sgallagh pops the champagne cork 16:26:07 sgallagh: just want to get involved with ELN 16:26:41 Cool, happy to have you. 16:27:24 As @yselkowitz said above, the best first place to start would be to help with the build failures. After that, digging into the Content Resolver and helping figure out ways to reduce dependencies would be fabulous. 16:27:34 Thanks! appreciate it. i'm looking into python-setuptools right now 16:27:59 note that I have tickets for dependency reduction too 16:28:03 Sure, why start with an easy one when you can pull all of your hair out at once? :-D 16:28:07 :D 16:28:17 even better, the build in koji had its artifacts expire lol 16:28:27 This is fine. 16:28:45 I'll go check the log.. oh. 16:28:47 @yselkowitz Would you be willing to take on an apprentice? 16:29:30 sure, I'm usually on matrix and not IRC (now that those are split) 16:30:12 just joined the matrix channel 16:30:48 that's the place to be, would be glad to point out things that need build fix or dependency reduction work 16:30:58 Same, this split is a real pain in the neck 16:31:16 also, it looks like we might be able to say .hi again (?) 16:31:16 .hi 16:31:18 neil: neil 'Neil Hanlon' 16:31:38 .hi 16:31:39 yselkowitz: yselkowitz 'Yaakov Selkowitz' 16:32:51 .hi 16:32:52 sgallagh: sgallagh 'Stephen Gallagher' 16:34:13 Alright, and with that I don't have anything else. Any other topics for today? 16:34:42 not I, thanks again for the direction and offers to help onboard 16:35:31 Thanks for volunteering! 16:36:20 OK, then I think that's it for today. 16:36:24 Thanks for joining us, folks! 16:36:29 #endmeeting