| 12 Nov 2025 |
 Emma [it/its] | i dont use VSC either | 12:29:17 |
| Emma [it/its] | rider is mostly okay | 12:29:36 |
|  Inayet changed their display name from inayet to Inayet. | 12:38:45 |
| 13 Nov 2025 |
 Samuel | someone's opened a pr for the new releases: https://github.com/NixOS/nixpkgs/pull/461120 | 10:15:04 |
 Corngood | I've been working on one too. I should have mentioned it. I'll post it today and compare them. | 11:32:33 |
| Corngood | I generally start on it when I get the release announcement. Unfortunately the update bot doesn't really work because of how the source and binary packages are coupled, but update.nix does usually work. | 11:34:32 |
| Corngood | Mine is here: https://github.com/NixOS/nixpkgs/pull/461246
It would be great to get the update bot working. It actually does manage to update the binary packages most of the time, but we currently build the top level packages (e.g. dotnet-sdk_8) as a composite of the binary SDK and source-built runtime. This means that you need to update them at the same time, or it'll fail a version assert.
So like:
99acf9463aef dotnetCorePackages.dotnet_8.vmr: 8.0.21 -> 8.0.22
9cc88eb04523 dotnetCorePackages.sdk_8_0-bin: 8.0.415 -> 8.0.416
It'
| 13:59:42 |
| Corngood | * Mine is here: https://github.com/NixOS/nixpkgs/pull/461246
It would be great to get the update bot working. It actually does manage to update the binary packages most of the time, but we currently build the top level packages (e.g. dotnet-sdk_8) as a composite of the binary SDK and source-built runtime. This means that you need to update them at the same time, or it'll fail a version assert.
So like:
99acf9463aef dotnetCorePackages.dotnet_8.vmr: 8.0.21 -> 8.0.22
9cc88eb04523 dotnetCorePackages.sdk_8_0-bin: 8.0.415 -> 8.0.416
| 13:59:56 |
| Samuel | running nixpkgs-review now | 14:01:48 |
| Corngood | I had a brief look for examples of update scripts that deal with this sort of coupling, but I didn't find anything obvious. One method would be to make the composite SDK have an update script that calls both of the child ones. | 14:02:02 |
| Samuel | Dang, that's a chonky rebuild, pulling ≈20GB from the cache, that's ≈60GB uncompressed | 14:06:17 |
| Corngood | Building all this stuff is too expensive for nixpkgs-review-gha, so I'm not sure if the update bot would even be able to do it...
I'm also running a review btw, on x86_64-linux. | 14:06:42 |
| Corngood | And then I usually do a darwin one from the community builder after that. | 14:07:02 |
| Samuel | I'm running on an 8C/16T ryzen server and it still takes a long time every update 🙃 | 14:08:19 |
| Samuel | Mostly due to a full webkit build somewhere down the dependency graph | 14:09:34 |
| Corngood | VMR 10 already failed for me... Looks like some sort of change to the output structure :|
Why is there a webkit build? Something that's currently broken on master? | 14:10:55 |
| Samuel | No webkit was last time, this time it's just opencv for now | 14:16:42 |
| Samuel | 
Download image.png | 14:16:47 |
| Samuel | Still annoying but not that bad | 14:17:07 |
|  qsevers23 joined the room. | 14:20:50 |
| qsevers23 | Thanks for getting the new dotnet releases wrapped up, running nixpkgs-review on aarch64-darwin now | 14:24:04 |
| qsevers23 changed their display name from gorillaman43 to qsevers23. | 14:24:24 |
| Corngood | VMR failed because it now outputs dotnet-sdk-10.0.100-rtm.25523.111-linux-x64, but the sdkVersion field in release.json is just '10.0.100'. I guess in the past this always matched, ugh | 15:46:15 |
