| 18 Nov 2025 |
 leona | the idea is relatively simple, having a seperate python3Stdenv package that is used for llvm and other things in the darwin stdenv. but for now it's still at various kinds of broken | 13:07:28 |
| leona | sorry, I'm not feeling good. I don't think I can finish that or any larger decisions or things today | 14:50:47 |
 hexa | take care! | 14:52:58 |
|  @lorenzleutgeb:matrix.org left the room. | 16:38:34 |
|  jopejoe1 (4094@39c3) changed their display name from jopejoe1 to jopejoe1 (4094@39c3). | 20:19:21 |
| 19 Nov 2025 |
|  dave :3 joined the room. | 00:21:32 |
| 20 Nov 2025 |
|  John joined the room. | 05:42:54 |
 raboof | we're planning a small ZHF hackday event in NL the 29th - that still makes sense even if it's a bit close to the release, right? depending on the release we'll have some time to dig into a deeper issue, or help out new contributors get their bearings | 14:22:08 |
| jopejoe1 (4094@39c3) | Yes, of course, fixing packages is even helpful when we are not in the ZHF, soo still good to send in fixes on the last day of ZHF, but remember to backport them ^^ | 14:31:24 |
| raboof | * we're planning a small ZHF hackday event in NL the 29th - that still makes sense even if it's a bit close to the release, right? depending on the turnout we'll have some time to dig into a deeper issue, or help out new contributors get their bearings | 14:36:43 |
| raboof | * we're planning a small ZHF hackday event in NL the 29th - that still makes sense even if it's a bit close to the release, right? depending on who shows up we'll have some time to dig into a deeper issue, or help out new contributors get their bearings | 14:36:54 |
| 21 Nov 2025 |
 ners | I once ran a ZHF that was after the release. We then joked that we're participating in the next ZHF very early. 🙃 | 08:11:20 |
| ners | * I once ran a ZHF that was just a few days after the release. We then joked that we're participating in the next ZHF very early. 🙃 | 08:11:35 |
| ners | Fixes are aways good to get in. | 08:11:38 |
|  jappie joined the room. | 17:02:07 |
| 22 Nov 2025 |
|  Quirin Brändli joined the room. | 00:03:45 |
| Quirin Brändli | I got a quick question just out of curiosity:
While the feature freeze time was ongoing, the full master branch was frozen for 3 weeks, right? That means that nixos-unstable was frozen as well, right? | 00:05:27 |
| hexa | nothing is frozen | 00:21:59 |
| hexa | it is open for fixes and non-breaking changes | 00:22:07 |
| hexa | nixos-unstable also gets built during feature freeze | 00:22:28 |
 Grimmauld (any/all) | That, and not all fixes that look non-breaking are actually non-breaking. Updates always have the potential to cause regressions in downstream packages, it is on the maintainers to estimate the probability of that and weigh that against maintenance burden in the coming release cycle.
E.g. it is possible to have the choice between a risky update on an important package, or be stuck doing security backports for half a year. You then ask release managers laying out the problem and how bad you think fallout will be, and it is a judgment call. But these things do go wrong occasionally, which means even during freeze month we get regressions | 07:55:51 |
 vcunat | Yeah, every change breaks someone's workflow
https://xkcd.com/1172/ | 07:59:57 |
| Grimmauld (any/all) | I was more thinking libxml 2.15 (libxml is notorious to break shit, but I really do not want to manually maintain 2.14.x for half a year). Or sdl3/sdl2-compat, where a harmless looking update (they were always very tame in the past) currently causes dwarf fortress to segfault on launch. | 08:01:53 |
| Grimmauld (any/all) | Neither of the two is spacebar heating. Its gambling, where the risky libxml update surprisingly didn't break barely anything, and the safe-looking SDL update causes issues. And none has the knowledge to know that in advance, maintainers can only guess and will guess wrong. | 08:03:42 |
| vcunat | Yes, I know. I wasn't being serious 🙂 | 08:16:57 |
|  @chaotic-routine:matrix.org joined the room. | 23:13:45 |
| @chaotic-routine:matrix.org left the room. | 23:16:31 |
| 23 Nov 2025 |
| dave :3 set a profile picture. | 16:53:40 |
 eveeifyeve | Any chance to update and remove nim1 from this release or am I late? | 20:27:21 |
| leona | You said, that nim1 is still in LTS, I don't see the reason to urge with that knowledge. Otherwise I can only repeat what I already said: We don't want to ship outdated software that does not get patches, this includes when nobody wants to maintain them in Nixpkgs
We're quite close to the release, though. | 21:57:12 |
