| 12 May 2026 |
 kuflierl | I was in the art group with some suggestions last time. I wonder how it looks this time | 01:52:35 |
 raf | I know and trust llakala with this kind of stuff, so I'm inclined to trust their PR when it comes to optimizing and doing so safely. | 05:20:43 |
| 13 May 2026 |
|  phonkd joined the room. | 08:44:50 |
 yaya | Name is Yarara and a logo does not exist yet (I submitted a call-for-art in NixOS/branding#35) | 10:21:59 |
|  joe6784 joined the room. | 11:20:31 |
| 14 May 2026 |
 vcunat | When nixpkgs-26.05-darwin gets created, we'll get a bit hit by the mess which we have in the channel-blocking package sets, as here it contains some packages which do not block nixpkgs-unstable (no idea why, really).
In particular, gimp2 and cabal2nix will probably turn out problematic. Ref: https://hydra.nixos.org/job/nixpkgs/staging-next/darwin-tested#tabs-constituents
I suppose we mainly need to adjust the darwin channel-blocking package set, somehow.
| 12:27:01 |
 emily | I suppose it's a bit late to try implementing the jobset merge I proposed to fix that? (I figured 26.11 made more sense given the x86_64-darwin drop) | 13:34:42 |
| vcunat | That sounds like overkill for this particular thing. | 13:38:06 |
| vcunat | It's just about which set of packages is meant to be blocking. | 13:39:15 |
|  LucasOe joined the room. | 18:14:28 |
| LucasOe left the room. | 18:25:24 |
| 15 May 2026 |
|  jmchapman joined the room. | 16:51:44 |
| kuflierl | Sooo, i made a mistake while merging https://github.com/NixOS/nixpkgs/pull/515479 and the version in the attr-name is wrong. I suggest merging https://github.com/NixOS/nixpkgs/pull/520658 in order to remove the offending version from the attr-name. | 23:46:43 |
| kuflierl | * Sooo, i made a mistake while merging https://github.com/NixOS/nixpkgs/pull/515479 and the version in the attr-name is wrong. I suggest merging https://github.com/NixOS/nixpkgs/pull/520658 in order to remove the offending version from the attr-name. The change should not cause any rebuilds. | 23:46:55 |
| 16 May 2026 |
|  same joined the room. | 10:49:54 |
| same | hey! quick question: i see that the dates in the schedule on pr 503391 were edited; should pr 516381 be updated accordingly? i'd edit it myself but i don't have permissions | 11:24:56 |
 hexa | yes, correct. will happen in a minute. | 11:28:40 |
| hexa | rm poked | 11:28:49 |
| yaya | thanks for the hint! | 13:26:41 |
| 17 May 2026 |
 Grimmauld (any/all) | https://github.com/NixOS/nixpkgs/pull/521022#pullrequestreview-4304200622
Technically this is a change in behavior, pointing a path to a runtime-mutable config from /etc to /var/lib.
It was broken before and never really worked properly, which is why the fix here is imo non-breaking. However, it is still a change in behavior. Does this need a breaking changes exception? Do i just wait for branch-off? The change of the PR is overall just necessary and much-needed cleanup, and i'd really hate to block on a technicality, but i also don't want some release manager to come chew me out for merging stuff after freeze i shouldn't merge. | 12:06:38 |
| yaya | Reviewed the PR and agree with having it merged with a release note. | 16:07:09 |
| Grimmauld (any/all) | thanks! | 16:08:42 |
| emily | are we okay to land non-backwards-incompatible deprecation warnings? (context: https://github.com/NixOS/nixpkgs/pull/521144) | 19:39:04 |
 Sandro 🐧 | might be a little late, but the change itself is very good | 19:43:27 |
| Sandro 🐧 | * might be a little late, but the change itself is very good as nested lists IIRC break cross or something closely related | 19:43:44 |
| Sandro 🐧 | * might be a little late, but the change itself is very good as nested lists IIRC break cross | 19:43:53 |
| emily | plausible, they don't handle e.g. getDev | 19:44:00 |
| emily | re late, I figure the main deadline for warnings is ~branch-off as they can't break anything by themselves and branch-off is when people might be doing early testing to see if there's any issues they'll need to handle | 19:44:32 |
| emily | but will defer to RMs for sure :) | 19:44:35 |
| yaya | agreed. I leave it up to you to merge :) | 22:37:28 |
