| 9 May 2026 |
 dish [Fox/It/She] | * <mx-reply><blockquote><a href="https://matrix.to/#/!UNVBThoJtlIiVwiDjU:nixos.org/$YrqzZKlq_8YJHG2dExLQBhChbfrNhZtg_gesetslADQ?via=pyrox.dev&via=matrix.org&via=tchncs.de">In reply to</a> <a href="https://matrix.to/#/@k900:0upti.me">@k900:0upti.me</a><br /><a href="https://matrix.to/#/@pyrox:pyrox.dev">@dish [Fox/It/She]</a> how much should I expect to explode if yarn-berry_4 4.13.0 -> 4.14.1?</blockquote></mx-reply>everything since they changed the default settings, we already reverted that upgrade once | 15:13:59 |
 K900 | OK great it's in staging-next now because 4.13 doesn't build anymore | 15:41:13 |
| K900 | And I am taking back everything bad I said about the Python ecosystem today | 15:41:29 |
| dish [Fox/It/She] | In reply to @k900:0upti.me
OK great it's in staging-next now because 4.13 doesn't build anymore did you check to see if all FOD hashes have to be recalculated or not | 17:12:35 |
| K900 | My small-ish sample says not all | 17:12:51 |
| K900 | But some things needed lockfile patches and got recalculated on the PR | 17:13:03 |
| dish [Fox/It/She] | i figured it wouldn't be all, but i heard of a decent number of breakages on the original update pr | 17:13:14 |
| dish [Fox/It/She] | which is why it got reverted | 17:13:21 |
| K900 | Well the author of the other PR claimed to have fixed them all | 17:13:34 |
| dish [Fox/It/She] | then we should be fine | 17:15:14 |
| 10 May 2026 |
| K900 | Well my everything rebuild is done and nothing significant exploded | 04:37:42 |
| K900 | So that's nice | 04:37:45 |
 ghpzin | chromium and electrons do not build:
https://hydra.nixos.org/build/328718913
error[E0425]: cannot find type `LaneCount` in module `core::simd`
--> ../../third_party/rust/chromium_crates_io/vendor/bytemuck-v1/src/zeroable.rs:234:15
|
234 | core::simd::LaneCount<N>: core::simd::SupportedLaneCount,
| ^^^^^^^^^ not found in `core::simd`
error[E0405]: cannot find trait `SupportedLaneCount` in module `core::simd`
--> ../../third_party/rust/chromium_crates_io/vendor/bytemuck-v1/src/zeroable.rs:234:41
|
234 | core::simd::LaneCount<N>: core::simd::SupportedLaneCount,
| ^^^^^^^^^^^^^^^^^^ not found in `core::simd`
Same error as in:
https://issues.chromium.org/issues/480176523
Revert of:
https://github.com/chromium/chromium/commit/90b77efcecb262823fadb67b0ce218846cd9e756
seems to fix it, probably because rustversion::before from upstream bytemuck is always there on stable. | 20:20:43 |
 hexa | Yureka (she/her)? | 20:21:28 |
| hexa | networkException? | 20:21:35 |
| 11 May 2026 |
 niklaskorz | also related: https://chromium.googlesource.com/chromium/src/+/refs/heads/main/tools/rust/unstable_rust_feature_usage.md | 09:13:41 |
| niklaskorz | * also possibly related: https://chromium.googlesource.com/chromium/src/+/refs/heads/main/tools/rust/unstable_rust_feature_usage.md | 09:15:08 |
 vcunat | There's a musl blocker:
https://hydra.nixos.org/job/nixpkgs/staging-next/stdenvBootstrapTools.x86_64-unknown-linux-musl.test
Alyssa Ross I guess? | 09:22:00 |
|  teutat3s joined the room. | 09:33:49 |
 Alyssa Ross | Builds locally for me. | 12:33:53 |
| hexa | restarted | 12:34:43 |
| hexa | or rather I clicked and it keeps loading 🤔 | 12:35:56 |
| vcunat | Most likely because eval is in late stage, so a huge postgresql transaction hogs everything involved. | 12:37:12 |
| hexa | that tracks | 12:37:46 |
| K900 | Did we merge a big rebuild into next | 13:28:07 |
| vcunat | groff: https://github.com/NixOS/nixpkgs/pull/517946#issuecomment-4420481095 | 13:35:17 |
| vcunat | On Hydra it looked like wasting around 7k jobs. (but part of that might've been due to other changes) Not that bad, considering that it's *-linux jobs. | 13:37:11 |
| K900 | Ouch | 13:38:14 |
| K900 | Welp | 13:38:15 |
| vcunat | 16s to display an important man page sounded pretty bad to me. | 13:39:36 |
