| 17 Nov 2023 |
 hexa | nixpkgs supporting resholve is a hack | 16:18:04 |
 raitobezarius | Agreed | 16:18:20 |
| raitobezarius | Sent | 16:18:58 |
 Randy Eckenrode | In reply to @hexa:lossy.network
and a fix by me that was too costly to go into the running staging cycle, because darwin-stdenv loves python Yes. 😠LLVM and a few other things depend on it. | 17:02:20 |
| raitobezarius | https://github.com/NixOS/nixpkgs/pull/266270 this was merged | 17:02:40 |
| raitobezarius | All further issues should be dealt by working on the top of that PR instead of reverting it | 17:02:50 |
| raitobezarius | Or reverting it partially to adopt similar workarounds to the "do not use ensureDBOwnership" | 17:03:01 |
| hexa | wondering whether we can get the staging-23.11 branch going | 17:24:52 |
| hexa | it's a bit annoying to keep track of staging fixes, that should be backported after they've been merged into staging | 17:25:32 |
| raitobezarius | https://github.com/NixOS/nixpkgs/pull/264361 merged | 17:43:40 |
| raitobezarius | figsoda: can you arrange staging-23.11 ? We can perform https://nixos.github.io/release-wiki/Branch-Off.html steps in advance without doing the thing for the master branch and without the beta commit? | 17:45:20 |
| raitobezarius | figsoda: Also you should prepare a time for doing the branch-off video call meeting thingie | 17:45:38 |
 Artturin | In reply to @hexa:lossy.network
it's a bit annoying to keep track of staging fixes, that should be backported after they've been merged into staging IIRC We have this problem every release so time to add it to the release wiki? | 17:58:39 |
 Lily Foster | yeah i don't see details for specifically making the staging-23.11 branch on the wiki, but i'm admittedly just skimming it on mobile and may have just missed it. i would intuit that it should be created at least when the final staging-next for release starts (i.e. so there's no gap where there's nowhere to put staging changes intended for the release) and labels/backport stuff for it too? | 18:02:39 |
| raitobezarius | llvm 5, ruby 3.0 dropped FYI | 19:27:18 |
| raitobezarius | I'm fixing the last evaluation errors with the nodejs drop and I will drop Node.js 14 & 16. | 19:27:29 |
| raitobezarius | In reply to @artturin:matrix.org
IIRC We have this problem every release so time to add it to the release wiki? waiting for your PR :P | 19:27:42 |
| raitobezarius | any PR to the release wiki is welcome | 19:27:50 |
| raitobezarius | Node.js was dropped | 22:26:20 |
 @julienmalka:matrix.org | completely ? | 22:28:31 |
| @julienmalka:matrix.org | That seems excessive | 22:28:37 |
| Lily Foster | nah it's fine | 22:28:43 |
| Lily Foster | who needs it anyway | 22:28:48 |
| @julienmalka:matrix.org | It was kinda painful anyway | 22:28:57 |
| Lily Foster | (i assume @raitobezarius just means old versions that have been marked insecure regardless) | 22:29:17 |
| raitobezarius | the whole thing boom | 22:29:32 |
| raitobezarius | no one will ask again lily about buildNodePackages | 22:29:41 |
| @julienmalka:matrix.org | can we delete openssl too | 22:29:44 |
| @julienmalka:matrix.org | completely | 22:29:48 |
| raitobezarius | I dropped Node.js 14 & 16 as per my messages here | 22:29:51 |
