| 9 May 2026 |
 K900 | Yeah | 09:00:02 |
 Yureka (she/her) | I don't see anything to be done on the fetcher side. the fetcher works correctly and you can detect all failures using nixpkgs-review/... | 09:00:34 |
| Yureka (she/her) | the fetcher's (and config hook's) job is to make sure the FOD does not randomly break, which it didn't | 09:00:52 |
 leona | IMO it's how https://github.com/NixOS/nixpkgs/blob/master/pkgs/by-name/ya/yarn-berry/fetcher/berry-4-offline.patch is intergrated into yarn? | 09:01:25 |
| leona | and this now longer works in this way by default? | 09:01:34 |
| leona | but I may be wrong | 09:01:54 |
| Yureka (she/her) | yes, this is the config hook | 09:03:54 |
| leona | Tried to use yarn-berry_4.yarnConfigHook (nixpkgs) which expects lockfile version 8, but found lockfile version 8 is just confusing... | 09:04:50 |
| leona | as an error message | 09:04:54 |
 Marie | about 60 MiB | 10:05:51 |
 hexa | looking | 11:40:07 |
| hexa | looks like you dealt with it hours ag | 11:45:39 |
| hexa | Redacted or Malformed Event | 11:45:40 |
| K900 | In reply to @hexa:lossy.network
looks like you dealt with it hours ag Well, "dealt with it" | 11:56:18 |
| K900 | By skipping the two tests that still fail | 11:56:24 |
| K900 | Without fully figuring out why | 11:56:30 |
| hexa | yeah, that's fine | 11:57:34 |
 dish [Fox/It/She] | In reply to @k900:0upti.me
@dish [Fox/It/She] how much should I expect to explode if yarn-berry_4 4.13.0 -> 4.14.1? everything since they changed the defaults, we already reverted that upgrade once | 15:13:19 |
| 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 defaults
settings, we already reverted that upgrade once | 15:13:49 |
| 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 |
