2025-05-29 19:00:45 <@yselkowitz:fedora.im> !startmeeting ELN SIG 29 May '25
2025-05-29 19:00:47 <@meetbot:fedora.im> Meeting started at 2025-05-29 19:00:45 UTC
2025-05-29 19:00:47 <@meetbot:fedora.im> The Meeting name is 'ELN SIG 29 May '25'
2025-05-29 19:00:50 <@yselkowitz:fedora.im> !meetingname eln
2025-05-29 19:00:51 <@meetbot:fedora.im> The Meeting Name is now eln
2025-05-29 19:01:04 <@salimma:fedora.im> !hi
2025-05-29 19:01:05 <@zodbot:fedora.im> Michel Lind (salimma) - he / him / his
2025-05-29 19:01:22 <@tdawson:fedora.im> !hi
2025-05-29 19:01:23 <@zodbot:fedora.im> Troy Dawson (tdawson)
2025-05-29 19:01:37 <@gmoro:matrix.org> !hi
2025-05-29 19:01:39 <@zodbot:fedora.im> Guilherme Moro (guilhermemoro)
2025-05-29 19:01:57 <@sgallagh:fedora.im> !hi
2025-05-29 19:01:57 <@zodbot:fedora.im> Stephen Gallagher (sgallagh) - he / him / his
2025-05-29 19:03:33 <@yselkowitz:fedora.im> !topic New business
2025-05-29 19:04:01 <@yselkowitz:fedora.im> !link https://github.com/fedora-eln/eln/issues/247
2025-05-29 19:04:13 <@yselkowitz:fedora.im> Troy Dawson ?
2025-05-29 19:04:51 <@tdawson:fedora.im> I'd say I'm about 2/3 of my way through all the logo's.
2025-05-29 19:05:54 <@tdawson:fedora.im> Some of them I'm very impressed with.   But it's just a bit of a chore.  There are so many different formats, shapes, and different ways to present the logo.
2025-05-29 19:06:19 <@tdawson:fedora.im> OK, I wouldn't call it a chore ... I really love doing it.
2025-05-29 19:06:51 <@tdawson:fedora.im> Anyway ... work is progressing, when I'm done, I'll put it up on github just like the backgrounds.
2025-05-29 19:07:28 <@yselkowitz:fedora.im> !link https://github.com/fedora-eln/eln/issues/249
2025-05-29 19:08:20 <@nhanlon:beeper.com> !hi
2025-05-29 19:08:21 <@zodbot:fedora.im> Neil Hanlon (neil) - he / him / his
2025-05-29 19:08:22 <@yselkowitz:fedora.im> a couple weeks back, the rc6 kernel and subsequent snapshots broke booting on media
2025-05-29 19:08:45 <@salimma:fedora.im> both Rawhide and ELN, or just ELN?
2025-05-29 19:08:49 <@yselkowitz:fedora.im> the bug has since been fixed
2025-05-29 19:09:11 <@yselkowitz:fedora.im> both, but the rawhide builds were caught by gating on the update
2025-05-29 19:09:33 <@yselkowitz:fedora.im> where the ELN builds made in parallel got through (since we don't gate) and then made compose tests fail
2025-05-29 19:09:56 <@yselkowitz:fedora.im> I am working with the kernel maintainer to switch kernel builds over to ELNBuildSync
2025-05-29 19:10:26 <@salimma:fedora.im> I wonder if we should just defer starting the build until the Rawhide build passed gating
2025-05-29 19:10:31 <@salimma:fedora.im> or will that slow things down too much
2025-05-29 19:10:39 <@yselkowitz:fedora.im> that's what using ELNBuildSync would do
2025-05-29 19:10:43 <@salimma:fedora.im> oh - is that what... yeah
2025-05-29 19:10:51 <@salimma:fedora.im> why is the kernel currently built in a special way then?
2025-05-29 19:10:55 <@yselkowitz:fedora.im> because the ELN build would not start until the rawhide build was stable
2025-05-29 19:11:20 <@salimma:fedora.im> right. but why is the kernel not using elnbuildsync already
2025-05-29 19:11:25 <@yselkowitz:fedora.im> 1) secure boot
2025-05-29 19:11:45 <@yselkowitz:fedora.im> 2) the maintainer wanted to keep a closer eye on the builds
2025-05-29 19:11:55 <@yselkowitz:fedora.im> but that dated back to the beginning of ELN
2025-05-29 19:12:47 <@sgallagh:fedora.im> Right, I think at this point the original reasons are no longer really valid
2025-05-29 19:12:58 <@sgallagh:fedora.im> What did Justin have to say when you spoke with him?
2025-05-29 19:13:12 <@yselkowitz:fedora.im> he agreed once the bug got fixed
2025-05-29 19:13:17 <@yselkowitz:fedora.im> which it since has
2025-05-29 19:13:33 <@yselkowitz:fedora.im> I just need to fix a bug in ELNBuildSync wrt reloading the config
2025-05-29 19:14:22 <@sgallagh:fedora.im> I was going to ask about that bug later
2025-05-29 19:15:16 <@yselkowitz:fedora.im> since we're on the topic already...
2025-05-29 19:16:08 <@yselkowitz:fedora.im> https://gitlab.com/redhat/centos-stream/ci-cd/distrosync/distrobuildsync/-/commit/6db3b915e06dd0bf85c20db3bf4184a93753d0da
2025-05-29 19:16:52 <@yselkowitz:fedora.im> When I updated EBS to F42 (from F37), it wouldn't work at first
2025-05-29 19:17:13 <@salimma:fedora.im> woof, from F37!
2025-05-29 19:17:14 <@yselkowitz:fedora.im> the reason being that /tmp was no longer writable as it was in previous builds
2025-05-29 19:17:48 <@yselkowitz:fedora.im> https://gitlab.com/redhat/centos-stream/ci-cd/distrosync/distrobuildsync/-/commit/2d97e3fcb0d54acb7e414303e0a764e03e19265d
2025-05-29 19:19:10 <@sgallagh:fedora.im> Hmm, we probably could have dropped htmlmin support entirely
2025-05-29 19:19:10 <@yselkowitz:fedora.im> anyway, afaics the bug was in gitlab-runner so I decided just to avoid it by using a different directory (/var/tmp) for writing
2025-05-29 19:19:24 <@yselkowitz:fedora.im> and that *seemed* to work fine, updates were flowing etc.
2025-05-29 19:19:43 <@yselkowitz:fedora.im> but the config update mechanism doesn't work now
2025-05-29 19:19:47 <@sgallagh:fedora.im> It's there to make the status.html endpoint a big faster to load, but it's not all that much of a gain
2025-05-29 19:20:06 <@sgallagh:fedora.im> It's there to make the status.html endpoint a bit faster to load, but it's not all that much of a gain
2025-05-29 19:21:10 <@sgallagh:fedora.im> Someone who knows web design a lot better than I do could almost certainly rework things to use a paged lookup of the status.json to speed it up far more efficiently without needing to minimize the JSON, but it's just not a real priority.
2025-05-29 19:21:23 <@sgallagh:fedora.im> Since very few people would ever look at the status.html anyhow
2025-05-29 19:23:20 <@yselkowitz:fedora.im> which only became apparent once I tried updating the config, which was last week iirc, and I was on PTO for part of this week, so haven't got back to that yet
2025-05-29 19:25:02 <@yselkowitz:fedora.im> Stephen Gallagher do you have any insight into the possibility that gitlab-runner would change the permissions of the working directory of an image it builds, and why that didn't happen with past builds?
2025-05-29 19:26:11 <@sgallagh:fedora.im> It shouldn't actually have the privilege to change the permissions.
2025-05-29 19:26:28 <@sgallagh:fedora.im> (I assume we're talking about the gitlab-runner operator in OpenShift?)
2025-05-29 19:27:04 <@yselkowitz:fedora.im> yes, some searches showed that it had happened before, and options were put in place to enable/disable that
2025-05-29 19:27:30 <@yselkowitz:fedora.im> but iiuc we switched from docker to podman runners sometime recently?
2025-05-29 19:28:37 <@sgallagh:fedora.im> yselkowitz: In OpenShift? I think they were always podman runners
2025-05-29 19:29:51 <@sgallagh:fedora.im> But if the problem is that /tmp isn't guaranteed to be writable, then we should probably just move the tempfile location to /var/tmp
2025-05-29 19:30:16 <@yselkowitz:fedora.im> hence https://gitlab.com/redhat/centos-stream/ci-cd/distrosync/distrobuildsync/-/commit/6db3b915e06dd0bf85c20db3bf4184a93753d0da
2025-05-29 19:30:19 <@sgallagh:fedora.im> https://gitlab.com/redhat/centos-stream/ci-cd/distrosync/distrobuildsync/-/blob/main/elnbuildsync/config.py#L322 needs to add the `dir=` kwarg
2025-05-29 19:31:37 <@sgallagh:fedora.im> `/var/tmp` is not mounted from the host, correct?
2025-05-29 19:32:03 <@yselkowitz:fedora.im> I don't think so
2025-05-29 19:32:55 <@yselkowitz:fedora.im> export TEMP=/var/tmp in run.sh?
2025-05-29 19:35:06 <@sgallagh:fedora.im> yselkowitz: Does Python honor that for `tempfiles`?
2025-05-29 19:35:16 <@sgallagh:fedora.im> yselkowitz: Does Python honor that for `tempfile`?
2025-05-29 19:35:23 <@yselkowitz:fedora.im> https://docs.python.org/3/library/tempfile.html#tempfile.mkstemp ?
2025-05-29 19:35:42 <@yselkowitz:fedora.im> > If dir is not None, the file will be created in that directory; otherwise, a default directory is used. The default directory is chosen from a platform-dependent list, but the user of the application can control the directory location by setting the TMPDIR, TEMP or TMP environment variables
2025-05-29 19:36:58 <@sgallagh:fedora.im> Ah, I was unaware of that. So yeah, I guess that would work.
2025-05-29 19:37:14 <@yselkowitz:fedora.im> ok I'll try that then
2025-05-29 19:37:35 <@yselkowitz:fedora.im> anything else on this?
2025-05-29 19:38:15 <@yselkowitz:fedora.im> !link https://github.com/fedora-eln/eln/issues/250
2025-05-29 19:38:43 <@salimma:fedora.im> ahh. interesting
2025-05-29 19:39:06 <@yselkowitz:fedora.im> since RHEL 10 was "reverted" to wget-1 after branching, now that wget1 is back in Fedora, I'm thinking ELN should probably switch back
2025-05-29 19:39:31 <@salimma:fedora.im> seems reasonable
2025-05-29 19:40:13 <@yselkowitz:fedora.im> !link https://github.com/fedora-eln/eln/issues/251
2025-05-29 19:40:56 <@yselkowitz:fedora.im> adamw was nice enough to not only let us know about this but also pinpoint the issue and file an upstream bug
2025-05-29 19:41:40 <@yselkowitz:fedora.im> does further point out the need for notifications for openqa failures though
2025-05-29 19:41:47 <@salimma:fedora.im> oh woops, ha, it was my PR to mutter that triggered this
2025-05-29 19:42:46 <@salimma:fedora.im> I'm glad we're flushign out issues caused by turning off X11 though. since EL10 is a bit weird
2025-05-29 19:42:54 <@salimma:fedora.im> that we build some packages with X11 support but they are not usable
2025-05-29 19:43:13 <@yselkowitz:fedora.im> agreed
2025-05-29 19:44:00 <@salimma:fedora.im> ELN, living in the future further ahead even of Rawhide
2025-05-29 19:44:20 <@yselkowitz:fedora.im> !link https://github.com/fedora-eln/eln/issues/252
2025-05-29 19:44:49 <@yselkowitz:fedora.im> notice was sent to devel@ that the python update is coming as soon as next week
2025-05-29 19:45:02 <@yselkowitz:fedora.im> that will be disruptive
2025-05-29 19:45:30 <@yselkowitz:fedora.im> between that and the F43 mass rebuild in July, I have the feeling it will be a long couple of months
2025-05-29 19:46:27 <@gmoro:matrix.org> I almost finished the buildsync work for bodhi at least 
2025-05-29 19:46:29 <@salimma:fedora.im> hopefully easier than the tooling update in Q1
2025-05-29 19:46:37 <@salimma:fedora.im> after all the Python team has been filing bugs for months
2025-05-29 19:46:49 <@gmoro:matrix.org> But not sure if we can put that online on time tho
2025-05-29 19:47:07 <@sgallagh:fedora.im> gmoro: If you need a reviewer, feel free to ping me.
2025-05-29 19:47:20 <@yselkowitz:fedora.im> if we don't have it in time for the python mass rebuild, we'll just do what we did in January and bypass openqa
2025-05-29 19:47:32 <@yselkowitz:fedora.im> hopefully we can get this done for the f43 mass rebuild at least
2025-05-29 19:47:37 <@gmoro:matrix.org> Stephen Gallagher: will do
2025-05-29 19:48:13 <@yselkowitz:fedora.im> yes they have, but filing bugs isn't always enough unfortunately
2025-05-29 19:48:35 <@yselkowitz:fedora.im> but yes at least they've been doing their due diligence
2025-05-29 19:48:55 <@salimma:fedora.im> nods
2025-05-29 19:49:25 <@salimma:fedora.im> but at least us provenpackagers can fix bugs now without being accused of ignoring the packagers, since... the bugs have been open for a long time
2025-05-29 19:49:39 <@yselkowitz:fedora.im> was there a policy change?
2025-05-29 19:50:01 <@yselkowitz:fedora.im> oh you're just saying the bugs mean they already have been put on notice
2025-05-29 19:50:20 <@salimma:fedora.im> yeah
2025-05-29 19:50:35 <@salimma:fedora.im> no policy change, and in general I prefer bugging the maintainer first, but... if it's been months
2025-05-29 19:50:42 <@yselkowitz:fedora.im> anything else on this?
2025-05-29 19:51:13 <@yselkowitz:fedora.im> !topic Old business
2025-05-29 19:51:13 <@yselkowitz:fedora.im> !link https://github.com/fedora-eln/eln/issues/202
2025-05-29 19:51:29 <@yselkowitz:fedora.im> Michel Lind UTC-5:  fsverity-utils (from the hyperscale Extras workload) is the last known dependent on openssl-devel-engine, but it is built for neither EPEL 10 nor in CBS. Is it still needed?
2025-05-29 19:52:29 <@salimma:fedora.im> ah right, we meant to check on this... let me report back after the meeting?
2025-05-29 19:52:42 <@salimma:fedora.im> I think tentatively not, but one sec
2025-05-29 19:52:51 <@salimma:fedora.im> I mean, don't wait, carry on first
2025-05-29 19:53:10 <@salimma:fedora.im> ah ok. yes, remove it please
2025-05-29 19:53:16 <@salimma:fedora.im> I just found the chat where we discussed this :P
2025-05-29 19:53:29 <@yselkowitz:fedora.im> could you file the CR PR?
2025-05-29 19:53:35 <@salimma:fedora.im> will do
2025-05-29 19:53:40 <@yselkowitz:fedora.im> thanks!
2025-05-29 19:53:46 <@yselkowitz:fedora.im> !topic Next meeting
2025-05-29 19:53:57 <@yselkowitz:fedora.im> the next two weeks are flock and devconf.cz iiuc
2025-05-29 19:54:11 <@salimma:fedora.im> fwiw Davide and I are not going so we'll be here
2025-05-29 19:54:20 <@salimma:fedora.im> we'll be at DevConf.cz in two weeks though
2025-05-29 19:54:48 <@tdawson:fedora.im> I won't be available for either of the next two Thursdays, so I won't be able to be here.
2025-05-29 19:55:38 <@yselkowitz:fedora.im> then on for next week and probably off for the following?
2025-05-29 19:55:58 <@salimma:fedora.im> that should work
2025-05-29 19:56:15 <@salimma:fedora.im> june 5th.. I'm flying out june 7th
2025-05-29 19:56:47 <@yselkowitz:fedora.im> !info next meeting is next Thursday 05 June at 15:00 EDT
2025-05-29 19:56:52 <@yselkowitz:fedora.im> !topic Open Floor
2025-05-29 19:56:58 <@yselkowitz:fedora.im> anything else for today?
2025-05-29 19:59:00 <@tdawson:fedora.im> Nothing from me.
2025-05-29 19:59:35 <@yselkowitz:fedora.im> ok then, seeing none, thank you all for joining the good discussions today, see you in channel or back here next week
2025-05-29 19:59:38 <@yselkowitz:fedora.im> !endmeeting