| 9 May 2026 |
leona | i fear that every new package would be broken with the current state of the fetcher | 08:21:45 |
K900 | I don't think so | 08:22:11 |
K900 | That PR doesn't change every single package that uses yarn-berry_4 | 08:22:29 |
K900 | At least | 08:22:30 |
K900 | I'm not sure why some are affected and some aren't | 08:22:49 |
Yureka (she/her) | I don't have the context | 08:56:26 |
Yureka (she/her) | fetchYarnBerryDeps does not use yarn | 08:56:36 |
Yureka (she/her) | so it is odd that the FOD hashes change | 08:56:43 |
K900 | Yarn 4.14 seems to require lockfile changes for some packages | 08:56:50 |
Yureka (she/her) | Ah | 08:56:55 |
Yureka (she/her) | If the lockfile changes, the FOD hash changes | 08:56:59 |
K900 | Yeah | 08:57:03 |
Yureka (she/her) | because the lockfile is copied to the FOD | 08:57:06 |
K900 | But it's some and not all | 08:57:10 |
K900 | It's weird | 08:57:12 |
Yureka (she/her) | but this does not require any change on the fetchYarnBerryDeps side | 08:57:18 |
Yureka (she/her) | so I'd say it's fine | 08:57:25 |
leona | no, the fod hash didn't change | 08:57:33 |
K900 | Yeah but they patched a bunch of lockfiles and now do we have to do that for everything | 08:57:37 |
leona | the build just failed | 08:57:39 |
Yureka (she/her) | do you have a reproducer I can look at? | 08:57:49 |
K900 | OK wait two different issues | 08:57:54 |
K900 | 4.14 changes FOD hashes | 08:58:00 |
K900 | 4.13 just locks up | 08:58:03 |
K900 | When you build yarn itself | 08:58:07 |
K900 | On next | 08:58:08 |
leona | https://github.com/NixOS/nixpkgs/pull/512685#issuecomment-4319558204 | 08:58:10 |
leona | in https://github.com/NixOS/nixpkgs/pull/513745 they now patched the .yarnrc.yml | 08:59:02 |
leona | so you need to revert this part for a reproducer | 08:59:13 |
Yureka (she/her) | ok but it's not failing in the FOD phase, right? | 08:59:58 |