| 14 May 2026 |
 André Lima | So is the fix here to just remove the chromium patch from https://github.com/dtolnay/rustversion/blob/a1dfebcd35f6082886548156f02f3832f52c0853/src/bound.rs#L51-L55 and change the selectors that bytemuck uses from rustversion::before(2026-01-27) to rustversion::any(before(2026-01-27), before(1.95)) and rustversion::since(2026-01-27) to rustversion::any(since(2026-01-27), since(1.95))? | 15:08:33 |
| André Lima | * So is the fix here to just remove the chromium patch from the chromium derivation and change the selectors that bytemuck uses from rustversion::before(2026-01-27) to rustversion::any(before(2026-01-27), before(1.95)) and rustversion::since(2026-01-27) to rustversion::any(since(2026-01-27), since(1.95))? | 15:09:49 |
| André Lima | * So is the fix here to just remove the chromium patch from https://github.com/NixOS/nixpkgs/blob/e81ce22cc4479459c0adcda35fb64a62027aa80b/pkgs/applications/networking/browsers/chromium/common.nix#L614-L624 and change the selectors that bytemuck uses from rustversion::before(2026-01-27) to rustversion::any(before(2026-01-27), before(1.95)) and rustversion::since(2026-01-27) to rustversion::any(since(2026-01-27), since(1.95))? | 15:10:12 |
| André Lima | Maybe just before(1.95) and since(1.95) would even work here | 15:11:57 |
| 15 May 2026 |
| André Lima | https://github.com/NixOS/nixpkgs/pull/520266 still building this locally but it should fix the electron and chromium build failures on staging-next | 00:25:44 |
|  tjni joined the room. | 04:23:37 |
| 17 May 2026 |
 winston | when is staging-next expected to get merged?
any chance the gnome extensions https://github.com/NixOS/nixpkgs/pull/519427 can still make it for 26.05? | 23:07:21 |
 emily | current staging-next won't miss 26.05 | 23:11:19 |
| emily | merged | 23:11:34 |
| winston | ah yeah i was just worried about missing this cycle, thanks 🙂 | 23:15:03 |
| 18 May 2026 |
 leona | 26.05 branchoff currently waits for the staging-next merge :) | 06:34:03 |
|  ethancedwards8 joined the room. | 06:44:04 |
 Vladimír Čunát | I believe we need to change the schedule in future releases. It's like... this staging-next was still allowed to get breaking changes - even to release-critical packages. | 06:47:11 |
| Vladimír Čunát | For some reason the schedule assumes that we can do a staging-next iteration every week. | 06:47:27 |
| Vladimír Čunát | But the reality is every month. (as there's the old stable release, too) | 06:47:51 |
| leona | The release requires much more coordination with staging currently than stated in the TL | 07:00:44 |
| leona | Or actually anywhere in the release wiki | 07:00:59 |
| leona | But I guess that’s also more a culture thing | 07:01:08 |
| Vladimír Čunát | Some important tests fail on staging-next reproducibly, e.g. nixosTests.misc or others in https://hydra.nixos.org/eval/1825464 | 08:15:17 |
| Vladimír Čunát | (i.e. unstable-small would get blocked if merged now) | 08:15:35 |
 K900 | Installer tests are looking like the usual bootstrap nonsense again | 08:16:22 |
| K900 | IPv6 test seem to be failing because something changed about interface names? | 08:17:48 |
| K900 | client_defaults: waiting for success: [ `ip -o -6 addr show dev eth1 scope link -tentative -temporary | wc -l` -eq 1 ]
client_global_setting # [ 11.392934] dhcpcd[1110]: ens3: adding default route via 10.0.2.2
client_defaults # Device "eth1" does not exist.
| 08:17:49 |
| K900 | * IPv6 test seems to be failing because something changed about interface names? | 08:17:54 |
| K900 | I wonder if misc is broken by the nspawn change | 08:20:11 |
| K900 | If it's trying to read /proc/cmdline | 08:20:16 |
 hexa | ens vs eth | 12:03:42 |
| K900 | Maybe it was racing the rename or something | 12:04:01 |
| K900 | And now it wins | 12:04:02 |
| hexa |
virtio_net virtio6 ens9: renamed from eth1
| 12:04:14 |
