| 6 May 2023 |
 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 |
| Lily Foster | (Ugh some stuff still needs 16 for now is the thing though... hopefully upstreams actually update their stuff by then) | 13:46:18 |
| hexa | I personally subscribe to python announcements, and we generally watch the support timeline pretty closely | 13:47:34 |
| hexa | they are of course less volatile, | 13:47:56 |
| hexa | * they are of course less volatile | 13:47:57 |
| hexa | the issue is, that we cannot really remove EOL stuff from a running stable release | 13:48:37 |
| hexa | so we mostly decided to drop things ahead of the release | 13:48:59 |
| Lily Foster | Looks like they has RSS for their announcements. I'll add it to my rss2email config I guess | 13:49:28 |
| Lily Foster | * Looks like they have RSS for their announcements. I'll add it to my rss2email config I guess | 13:49:39 |
| hexa | bitwarden fails to build with nodejs 18 😄 | 13:50:03 |
| hexa | bitwarden> /nix/store/pgf87rgkzdbqhhsddpligy8xiwar63w8-stdenv-linux/setup: line 122: Unknown command: "bin"
| 13:50:14 |
| hexa | *
bitwarden> /nix/store/pgf87rgkzdbqhhsddpligy8xiwar63w8-stdenv-linux/setup: line 122: Unknown command: "bin"
| 13:50:17 |
| Lily Foster | In reply to @hexa:lossy.network
bitwarden fails to build with nodejs 18 😄 Oh, I know. I know a few things that will | 13:50:26 |
| Lily Foster | Especially C/++ modules | 13:50:40 |
| Lily Foster | In reply to @hexa:lossy.network
bitwarden> /nix/store/pgf87rgkzdbqhhsddpligy8xiwar63w8-stdenv-linux/setup: line 122: Unknown command: "bin"
Okay that's... a weird error... | 13:50:59 |
| hexa |
To see a list of supported npm commands, run:
npm help/electron-builder: No such file or directory
| 13:51:29 |
| hexa | continues like that | 13:51:31 |
| Lily Foster | I guess I'll actually get out my laptop | 13:52:09 |
 @ambroisie:belanyi.fr | I saw tandoor-recipes in your list, just updated my version bump PR to use nodejs 😉 | 16:56:22 |
| 8 May 2023 |
|  aktaboot joined the room. | 20:44:24 |
| aktaboot | In reply to @lily:lily.flowers
We, uh, should probably make tooling to handle those soon can I open an issue about this ? 👀 | 20:53:07 |
| Lily Foster | In reply to @aktaboot:tchncs.de
can I open an issue about this ? 👀 Yeah, I can do that in a bit | 21:01:51 |
| 9 May 2023 |
|  denbrahe joined the room. | 10:30:01 |
| denbrahe | Hi, I'm trying to create a derivation for a React package using buildNpmPackage. However, both buildNpmPackage and prefetch-npm-deps always fail with Error: https://registry.npmjs.org/@babel/eslint-parser/-/eslint-parser-7.19.1.tgz: Connection Failed: tls connection init failed: Connection reset by peer (os error 104). Which package failed varies between retries. What could cause that? | 10:34:20 |
