| 13 Sep 2023 |
 hexa | firefox 115 esr reached profiling | 14:47:57 |
 vcunat | TB 115 built for me again. | 14:55:58 |
| hexa | good to go then? | 14:57:53 |
| hexa | waiting for eval is probably unnecesary | 14:58:15 |
| hexa | https://github.com/NixOS/nixpkgs/pull/254976 | 15:57:00 |
| hexa | https://github.com/NixOS/nixpkgs/pull/255036 | 23:42:49 |
| hexa | busy day | 23:42:55 |
| 16 Sep 2023 |
 Artturin | nbp: take a look https://github.com/mozilla/nixpkgs-mozilla/pull/309 | 03:52:09 |
| Artturin | * nbp: please take a look https://github.com/mozilla/nixpkgs-mozilla/pull/309 | 03:52:20 |
| hexa | vcunat: I assume you want to stay with sha512 as well? https://github.com/NixOS/nixpkgs/pull/255512/commits/bbd4ae85e3570324c7c1475bcf85267ddd0b4f88#diff-c31c9c46667258c9a9cce5227f5913537894a3e1a85fe877e9e3c56ea6e1e171 | 18:23:46 |
| vcunat | It's generated by the updater. | 18:24:51 |
| vcunat | I suspect it's simpler to reuse the format that upstream publishes. | 18:25:17 |
| hexa | if that is the same updater as for firefox, well | 18:25:20 |
| hexa | also it's not tofu that way | 18:25:27 |
| vcunat | The updater could convert it e.g. by calling nix hash but why not just use it as it is? | 18:26:07 |
| hexa | ask the PR author 😄 | 18:26:47 |
| vcunat | As a compromise for the hash attribute I had proposed https://github.com/NixOS/nixpkgs/pull/199660 but got no reaction. | 18:27:23 |
| hexa | 
Download image.png | 18:27:51 |
| hexa | that's draft state for you 😄 | 18:28:18 |
| vcunat | I linked it from a heavily discussed RFC IIRC. | 18:29:08 |
| hexa | from which I probably unsubscribed because of all the noise? 😄 | 18:33:43 |
| hexa | In reply to @vcunat:matrix.org
The updater could convert it e.g. by calling nix hash but why not just use it as it is? he just submitted a PR for that | 18:37:02 |
| vcunat | I'd personally prefer to keep the strings exactly the same as from upstream, which is why I had suggested that PR. | 18:38:34 |
| vcunat | But it's not like such a policy can be done just by one person or two. | 18:38:58 |
| hexa | there is no policy, so we're open to accept or reject such changes as maintainers of the package | 19:02:43 |
| hexa | we're even arguging for why it should be kept that way | 19:03:04 |
| vcunat | For the fetchurl change I'd want wider consensus, at least. | 19:15:18 |
| 18 Sep 2023 |
 nbp | “[…] heads-up about an upcoming change in 119 […] (unshipping plugin-container)” | 09:22:52 |
| vcunat | Was that for plugins? I thought those aren't a thing for years. | 09:24:47 |
| nbp | which is probably the reason for unshipping. | 09:25:28 |
