| 25 May 2024 |
 Jan Tojnar | In reply to @hexa:lossy.network
https://vulners.com/redhatcve/RH:CVE-2024-5148 https://github.com/NixOS/nixpkgs/pull/314666 beat me to it | 20:26:58 |
 hexa | Thomas 💜 | 20:28:00 |
 SebTM | Hey, someone willing to-do review for this? https://github.com/NixOS/nixpkgs/pull/311480
Posted second time now in discourse today | 20:40:19 |
| SebTM | * Hey, someone open to-do review for this? https://github.com/NixOS/nixpkgs/pull/311480
Posted second time now in discourse today | 20:43:16 |
| SebTM | * Hey, someone open to review for this? https://github.com/NixOS/nixpkgs/pull/311480
Posted second time now in discourse today | 20:43:20 |
| SebTM | * Hey, someone open to review this? https://github.com/NixOS/nixpkgs/pull/311480
Posted second time now in discourse today | 20:43:24 |
| Jan Tojnar | I believe the extensions are unmaintained now | 21:28:19 |
| 26 May 2024 |
| SebTM | So I can just merge it on my own because it only can get better? 😄 | 00:51:33 |
| SebTM | * So I can just merge it on my own (without review) because it only can get better? 😄 | 00:51:44 |
| SebTM | * So I can just merge it on my own (without review) because it only can get better? 😄
I don't really care, I can just update my nixpkgs-fork but then I might just stop upstreaming it if there is not a high chance to get it merged in the end. | 00:52:50 |
| SebTM | * So I can just merge it on my own (without review) because it only can get better? 😄
I mean, I don't really care (about the merge), I can just keep my nixpkgs-fork up2date but then I might just stop upstreaming it if there is no chance to get a review/merged. | 00:53:48 |
| Jan Tojnar | In reply to @sebtm:lodere.es
So I can just merge it on my own (without review) because it only can get better? 😄
I mean, I don't really care (about the merge), I can just keep my nixpkgs-fork up2date but then I might just stop upstreaming it if there is no chance to get a review/merged. yeah, if there is no-one else interested in the code, self-merge should be fine | 10:48:29 |
