| 5 May 2023 |
 Lily Foster | That would just mean npm is hecked beyond any hope of reproducibility | 12:06:28 |
| Lily Foster | Can package owners reupload a given version? Maybe it's just that and not a wider problem | 12:07:15 |
 stroem - sourcegraph | It only says "published a month ago", which is correct | 12:08:38 |
| stroem - sourcegraph | In reply to @lily:lily.flowers
Can package owners reupload a given version? Maybe it's just that and not a wider problem not since 2014 | 12:09:48 |
| stroem - sourcegraph | In reply to @lily:lily.flowers
Can package owners reupload a given version? Maybe it's just that and not a wider problem * not since 2014, to registry.npmjs.org at least | 12:09:56 |
| Lily Foster | Maybe transient network error during initial or current download that didn't meaningfully affect functionality? | 12:10:15 |
| Lily Foster | In reply to @strum355:matrix.org
not since 2014, to registry.npmjs.org at least (That's good. It's worrying you could do that before, but 🤷♀️) | 12:10:38 |
| stroem - sourcegraph | it was someone else that reported the mismatch last night (from tweag), and I got the same issue as well today having not run nix develop since yesterday | 12:11:00 |
| Lily Foster | Do you know if the integrity hash listed for that version at https://registry.npmjs.org/pnpm changed? | 12:11:35 |
| Lily Foster | * Do you know if the integrity hash listed for that version at https://registry.npmjs.org/pnpm/8.1.0 changed? | 12:12:35 |
| stroem - sourcegraph | huh its the same hash as the new one determined by nix, interesting | 12:13:30 |
| stroem - sourcegraph | i dont know if its changed or not though | 12:13:36 |
| stroem - sourcegraph | I dont have the old one in my nix store anymore either (hence getting the mismatch now) | 12:14:21 |
| stroem - sourcegraph | ok nevermind, ignore this entire discussion | 12:14:50 |
| stroem - sourcegraph | someone bumped it from 7.28.0 without changing the hash 🤦♂️ | 12:15:03 |
| Lily Foster | Well. I guess that mystery's solved then and for once it wasn't npm's fault | 12:16:13 |
| 6 May 2023 |
 hexa | 
Download image.png | 13:39:15 |
| hexa |
https://endoflife.date/nodejs | 13:39:15 |
| hexa | looks like we're also going to have a nodejs 16 issue during 23.05? | 13:39:28 |
| Lily Foster | In reply to @hexa:lossy.network
looks like we're also going to have a nodejs 16 issue during 23.05? Yep :/ | 13:39:50 |
| Lily Foster | OpenSSL announced 1.1.1 EOL for september so nodejs pushed theirs up | 13:40:03 |
| hexa | nixos/modules/services/web-apps/peertube.nix
nixos/modules/services/web-apps/wiki-js.nix
doc/languages-frameworks/javascript.section.md
pkgs/applications/networking/n8n/default.nix
pkgs/applications/networking/n8n/node-composition.nix
pkgs/applications/misc/tandoor-recipes/frontend.nix
pkgs/servers/code-server/default.nix
pkgs/servers/web-apps/whitebophir/default.nix
pkgs/servers/web-apps/discourse/default.nix
pkgs/servers/openvscode-server/default.nix
pkgs/servers/psitransfer/default.nix
pkgs/top-level/all-packages.nix
pkgs/servers/audiobookshelf/default.nix
pkgs/top-level/aliases.nix
pkgs/development/tools/electron-fiddle/default.nix
pkgs/development/tools/language-servers/docker-compose-language-service/default.nix
pkgs/development/tools/misc/kibana/7.x.nix
pkgs/development/tools/continuous-integration/github-runner/default.nix
pkgs/development/web/netlify-cli/composition.nix
pkgs/tools/admin/meshcentral/default.nix
pkgs/tools/security/vaultwarden/webvault.nix
pkgs/tools/security/bitwarden/default.nix
| 13:40:23 |
| hexa | doesn't look too bad | 13:40:26 |
| hexa | * doesn't look too bad on first grep | 13:40:29 |
| hexa | ngl … the nodejs eol stuff should be carried by the nodejs maintainers | 13:42:41 |
| hexa | the same happens for most other languages as well (php, haskell, python, go, rust) | 13:43:11 |
| hexa | I do understand that node is scattered throughout the package set, but there is a need to ping everyone on time | 13:43:51 |
| hexa | * I do understand that node is scattered throughout the package set, but there is a need to at least ping everyone on time | 13:44:02 |
| Lily Foster | I'd noticed the nodejs 16 eol a few days ago was pushed up. I didn't consider that it would land within 23.05 though | 13:44:03 |
| Lily Foster | I can probably open a tracking issue today or tomorrow for it and ping relevant maintainers and RMs. Just so everyone is aware it'll eventually be a problem for 23.05 | 13:45:04 |
