| 6 Sep 2025 |
 raitobezarius | Yeah, I think we should drop 2.92 as well | 12:57:21 |
 emily | well I replied and we established that what versions exist on unstable is irrelevant for upgrade compatibility | 12:57:37 |
| emily | (because you care about bug-compatibility of dependency closures, so you really just have to pin the old Nixpkgs if you want to validate that) | 12:57:55 |
| raitobezarius | I did see that reply but I didn't see a clear TLDR consensus | 12:57:56 |
| emily | ok I'll reply again summarizing what I understand the consensus to be now :P | 12:58:05 |
| raitobezarius | If you tell me that consensus has been reached on that position, all good | 12:58:07 |
 aloisw | 2.91 is the default in 25.05 so it needs to stay anyway. | 12:58:10 |
| aloisw | ("stay" as in "supported upstream" in case it's not clear) | 12:58:41 |
| emily | it doesn't need to stay in unstable | 12:58:41 |
| emily | which is the only place getting the toml11 bump | 12:58:48 |
| emily | IOW, you have to security-support (2.91 on 25.05), but not (2.91 on 25.11) | 12:58:57 |
| emily | so changes in libraries in 25.11 are irrelevant, which is what my toml11 series is about | 12:59:09 |
| emily | in this case this is a significantly lower burden | 12:59:19 |
| aloisw | OTOH the main effort was backporting the bumps to 25.05 which is probably not a bad idea anyway as they are supported for that nixpkgs release. | 12:59:54 |
| raitobezarius | Hm, I think we are still running in an annoying systemd bug | 13:00:36 |
| raitobezarius | taking down all CI operations | 13:00:43 |
| emily | raitobezarius: posted https://github.com/NixOS/nixpkgs/pull/426260#issuecomment-3262112732 with my belief on what the consensus bottom line is:
In other words, I’d expect our minimum expectations to be “the default version on any given supported Nixpkgs releases is supported for security and critical bug fixes when used in the context of that Nixpkgs releases”.
| 13:09:03 |
| aloisw | Is the systemd bug taking them down or did you take them down because they won't work anyway with the systemd bug? | 13:15:28 |
| raitobezarius | https://github.com/systemd/systemd/issues/37843 | 13:15:47 |
| raitobezarius | the bug is everytime systemctl reload systemd-resolved happens | 13:15:57 |
| raitobezarius | all DNS resolution go down | 13:16:00 |
| raitobezarius | because we have only a stub listener extra entry for IPv6 | 13:16:12 |
| raitobezarius | and not any stub listener entry for IPv4 | 13:16:17 |
| raitobezarius | (due to the pasta bug) | 13:16:19 |
| raitobezarius | so everytime they gets redeployed for any reason, e.g. updates or anything, DNS resolution goes down | 13:16:42 |
| aloisw | Oh god systemd-resolved. I have removed that on all my systems due to being pretty garbage. (In my experience it would consistently SERVFAIL after a few hours though, instead of just stopping listening entirely.) | 13:17:06 |
| raitobezarius | hah, i wish there would be a good well integrated replacement to it | 13:17:35 |
| raitobezarius | (i don't feel like dnsmasq or kresd is that) | 13:17:48 |
 K900 | kresd is almost good tbh | 13:18:41 |
| K900 | Just impossible to debug | 13:18:45 |
