| 23 Apr 2024 |
|  Seth Meyer joined the room. | 21:52:26 |
| 24 Apr 2024 |
 Diego Herrera | I have continued working on running willit on github-actions, this time I tried separating it so that it does the work per repo on different jobs.
at first I tried running all repos on different jobs, but noticed quickly that the -next branches failed cos they need information from the base branches.
now I'm running them separatelly so that the -next branches run on the same job as their corresponding base branch
https://github.com/dherrerace/willit-workflow/actions/runs/8810567747
I already have an idea on how to mix the results, but i'll continue working on that tomorrow :) | 03:45:50 |
 Michel Lind 🎩 | I'm running errands so might not be back in time for the meeting. So in case election cycle is open. @[Troy Dawson] already nominated himself, Neal nominated Jonathan and I nominated @[Carl George] . Someone needs to nominate nirik 😉 still working on the django lts doc PR. Got a PR in to make angora run on aarch / with a local npm installation and oh yeah Django 4.2 has landed I wonder in general how to follow up with JIRA issues that has no response? Esp the one about iptables ABI regression. No response and 9.4 is out soon (on mobile, hard to find the link)
| 17:04:02 |
 Neil Hanlon | EPEL Steering Committee meeting in 45 minutes on https://chat.fedoraproject.org/#/room/#meeting-1:fedoraproject.org | 17:16:07 |
| Michel Lind 🎩 | so - Stephen J Smoogen nirik if there's an ABI break that leaked out into RHEL 9.4, is that basically now the new ABI? or can we get missing symbols re-added (but keep any new symbols introduced in iptables in RHEL 9.4)? | 19:03:33 |
| Michel Lind 🎩 | the devs of our internal tool that currently expects the missing symbols need to know if this is coming back at some point, or if they just need to work around it | 19:04:13 |
| Michel Lind 🎩 | (oh I guess I can also figure out how to restore those symbols then build a new iptables in Hyperscale... but I'd rather not maintain something like this myself. Maybe I can submit a fix as a MR) | 19:04:59 |
 nirik | I... don't know. ;) I think it depends on what level of abi compat that thing has... | 19:22:54 |
 Stephen J Smoogen | what is the application which had the ABI break? | 19:26:47 |
| Stephen J Smoogen | it depends on that. | 19:27:00 |
| Neil Hanlon | iptables - https://issues.redhat.com/browse/RHEL-32463 | 19:29:10 |
| Stephen J Smoogen | different applications have different ABI guarentees. if it is a break with something that has 'strong' guarentees then its one thing. If it is a break with weak or none.. the new package is the new abi until the next time | 19:29:12 |
| nirik | iptables-libs has a 2 abi value... so it shouldn't break abi... | 19:31:44 |
| Stephen J Smoogen | Michel Lind 🎩: my non-educated guess is that iptables comes under https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/9.0_release_notes/deprecated_functionality | 19:32:05 |
| nirik | oh, sorry: "APIs and ABIs are stable within the lifetime of a single major release" | 19:32:18 |
| Stephen J Smoogen | beyond that.. it is probably a matter to bring up with the Technical Account Manager to get an idea of what this fell under | 19:34:40 |
| Michel Lind 🎩 | In reply to @nirik:matrix.scrye.com
I... don't know. ;) I think it depends on what level of abi compat that thing has... it's ASG 2 which Carl told me is quite strong | 19:38:49 |
| Michel Lind 🎩 | In reply to @nirik:matrix.scrye.com
oh, sorry: "APIs and ABIs are stable within the lifetime of a single major release" yeah... this counts as a break right? Though I guess I don't know how this interacts with the deprecation policy | 19:39:36 |
| Michel Lind 🎩 | but... deprecating iptables means it really should not have received changes right? | 19:40:34 |
| Michel Lind 🎩 | I can ask our EE team to start the conversation with the TAM, since ... while this mostly affect our data centers, they're also affected as they use the same Chef cookbooks and now can't upgrade :P | 19:41:17 |
| 25 Apr 2024 |
| Diego Herrera | https://dherrerace.github.io/willit-workflow/epel8/status-wont-install.html tada | 03:39:07 |
| Diego Herrera | * https://dherrerace.github.io/willit-workflow/ tada | 03:39:25 |
|  @sergiomassa:sibnsk.net removed their profile picture. | 15:39:26 |
| @sergiomassa:sibnsk.net left the room. | 15:51:56 |
| 26 Apr 2024 |
|  Fabio Valentini (AFK until April 28) changed their display name from Fabio Valentini to Fabio Valentini (AFK until April 28). | 13:00:10 |
| Michel Lind 🎩 | Is anyone else having issue building in mock against epel8? Might be only if you don't use container bootstrap It failed for me both with an alma and centos-stream base, trying to bootstrap DNF and not finding Python (travel day, can't send repro) | 14:05:10 |
| Neil Hanlon | I didn't have an issue last night with a stream base | 14:05:47 |
| Neil Hanlon | what base os? f40? | 14:05:57 |
| Michel Lind 🎩 | F40, yes. Though mock is normally kept in sync | 16:37:59 |
| Michel Lind 🎩 | Note that as I said you have to turn off containers. My F40 "host" is a container so obviously I don't run mock in another nested container | 16:38:48 |
