| 26 Nov 2025 |
 K900 | Hydra also does not have capacity to run multiple stagings at once in its current state | 17:11:11 |
 Marcus | How does this correlate with the perl and python jobsets? They often take half a week or so, and are run separately from the staging process. I guess they then steal capacity from ongoing staging process? | 17:13:49 |
| Marcus | (and other similar ones) | 17:14:15 |
| K900 | I don't think there's a perl jobset | 17:14:42 |
| K900 | python-updates does steal some capacity | 17:14:47 |
| K900 | But it's configured to have a lower priority | 17:15:01 |
| Marcus | I'm pretty sure there is 😄 | 17:15:01 |
| Marcus | https://hydra.nixos.org/jobset/nixpkgs/perl-updates | 17:15:26 |
| K900 | That is currently disabled and configured to use 600 shares | 17:16:31 |
 leona | python-updates do currently primarily run on a personal hydra | 17:16:31 |
| K900 | Which is very few shares | 17:16:33 |
| K900 | Though Hydra scheduling is exceptionally fucked | 17:16:42 |
| K900 | And the number of shares is kind of arbitrary and irrelevant | 17:16:54 |
 whispers (it/fae) | i have been curious, how do y'all actually monitor the status of a staging cycle? is it through the eval results at e.g. https://hydra.nixos.org/eval/1820494 or…? | 17:18:45 |
| K900 | Basically that yes | 17:18:59 |
| Marcus | I imagine not a lot of folks want to touch the hydra code base to improve it, given it's catalyst 🙂 | 17:19:57 |
 VladimÃr ÄŒunát | The PRs have some further useful links:
https://github.com/NixOS/nixpkgs/pull/464512 | 17:36:05 |
|  Grimmauld (any/all) joined the room. | 18:09:23 |
|  Yifei Sun joined the room. | 22:32:13 |
|  @stepbrobd:matrix.org left the room. | 22:32:18 |
 ShamrockLee (Yueh-Shun Li) | Dear staging experts,
I'm authoring a rustPlatform.buildRustPackage fix that passes RUSTFLAGS only if specified or needed to prevent shadowing other *_RUSTFLAGS environment variables. (This partially restore the behavior before PR NixOS/nixpkgs#435278.)
Should I choose staging-next as its target branch for this fix? Since the issue also affects the Nixpkgs 25.11 release, should I backport with the backport staging-25.11 label?
https://github.com/NixOS/nixpkgs/pull/464707
| 22:50:24 |
| leona | staging-next and staging currently don't make a difference time-wise, so for more clarity I suggest staging. | 23:05:01 |
| leona | As this is currently broken in 25.11, a backport to staging-25.11 should also be justified, yes | 23:05:57 |
| 27 Nov 2025 |
|  conatsera joined the room. | 01:16:52 |
| 28 Nov 2025 |
| Grimmauld (any/all) changed their display name from grimmauld (any/all) to musl-official | Grimm | any/all. | 11:35:37 |
| Grimmauld (any/all) changed their display name from musl-official | Grimm | any/all to Grimmauld (any/all). | 11:36:00 |
| K900 | @Yureka (she/her) do you have a consistent repro for the Asahi crash? | 18:37:09 |
 Yureka (she/her) | use firefox | 18:37:29 |
| Yureka (she/her) | browse the web | 18:37:32 |
| Yureka (she/her) | it happens consistently after 5-10 min | 18:37:41 |
