| 29 Sep 2025 |
|  xxlpitu joined the room. | 18:37:08 |
| xxlpitu | hi, I have a change that fixes a bug in pkgs/build-support/rust/fetch-cargo-vendor-util.py but I'm not sure if I should open a PR to merg in to staging or staging-next. This changes causes every rust package to rebuild. | 18:41:49 |
| xxlpitu | * hi, I have a change that fixes a bug in pkgs/build-support/rust/fetch-cargo-vendor-util.py but I'm not sure if I should open a PR to merge into staging or staging-next. This changes causes every rust package to rebuild. | 18:42:14 |
 K900 | staging | 18:45:33 |
| K900 | Too late for next now | 18:45:36 |
| K900 | Will have to be next cycle | 18:45:42 |
| xxlpitu | thank you 🙂 | 18:49:17 |
 VladimÃr ÄŒunát | Yeah, unless that's something critical/urgent, but it doesn't sound so. | 18:49:46 |
| xxlpitu | PR in question https://github.com/NixOS/nixpkgs/pull/447298. none urgent, since this is a rare edge case | 20:48:16 |
| 30 Sep 2025 |
 Grimmauld (migrated to @grimmauld:m.grimmauld.de) | huh, do we now split and compile rust crates one by one? While switching to -next, my system built like 600 rust crates as their own derivations, which tbh is kinda cool but it didn't do that before | 07:35:00 |
 Marie | importCargoLock maybe? | 07:35:42 |
 Alyssa Ross | (Which only fetches in separate derivations) | 07:40:18 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | interesting... | 07:41:48 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | i didn't go poke whether it was compiles or just source fetches, but i didn't even know we could import cargo locks into one-by-one rust packages. | 07:42:48 |
| Alyssa Ross | We discourage it because it increases eval time | 07:47:31 |
| VladimÃr ÄŒunát | staging-next only has 12k jobs queued, but we have 8k newly-failing ones and we already did have restart-all-failed recently. (it will probably be more than 8k once everything finishes) | 11:17:17 |
| VladimÃr ÄŒunát | Not giving me much confidence to merge so far. | 11:17:32 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | i am still seeing like 6 fails on my laptop | 13:34:28 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | will poke those this evening | 13:34:35 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | 
Download image.png | 13:34:56 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | we should probably fix nixd | 13:35:14 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | soqt is fixed and i'll poke py-slvs later, but indeed this is looking wonky. Especially considering it is just a few days to feature freeze... | 13:36:09 |
| Grimmauld (migrated to @grimmauld:m.grimmauld.de) | * soqt is fixed and i'll poke py-slvs later, but indeed this is looking wonky. Especially considering it is just a few days to break freeze... | 13:36:19 |
 nim65s | vcunat: re https://github.com/casadi/casadi/issues/4225 : do you want to handle this directly in https://github.com/NixOS/nixpkgs/pull/444862, or should I open another PR for that ? (in the later case: on which branch ?) | 16:07:30 |
| VladimÃr ÄŒunát | Yes, PR targeting staging-next. | 16:15:25 |
| VladimÃr ÄŒunát | Or pushing directly there if you're sure. | 16:15:41 |
| nim65s | a PR is fine :) | 16:16:39 |
| 1 Oct 2025 |
|  lovesegfault changed their profile picture. | 22:36:10 |
| 2 Oct 2025 |
| VladimÃr ÄŒunát | staging-next: we have all binaries, but still at >9k build regressions even if I subtract newly-succeeding, and we still have those blockers. | 05:46:36 |
| VladimÃr ÄŒunát | The convenient moment to start the next iteration is Sunday, as Saturday is the last day of merging breaking changes to critical packages (e.g. glibc upgrade is pending). So I don't feel like rushing a staging-next merge right now. | 05:48:09 |
