| 16 Sep 2023 |
 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 |
| nbp | the person who posted this message internally was looking for communication channels to linux distribution, such as Ubuntu, I figured I should forward it here. | 09:26:40 |
| vcunat | OK. Then noone will notice a difference, I hope. | 09:27:06 |
| vcunat | (except some extreme edge cases possibly) | 09:27:38 |
|  Sam Lehman joined the room. | 18:16:11 |
| Sam Lehman | Not sure if this is the right place to ask, but I'm using the packages from pkgs.nur.repos.rycee.firefox-addons via the NUR overlay, and rebuilding has been giving me an error like this for some time now:
Package ‘firemonkey-2.72’ in /nix/store/rx9xdvi39lg6rnxs577rwv3v4snif3xa-source/pkgs/firefox-addons/generated-firefox-addons.nix:1978 has an invalid meta attrset:
- key 'meta.mozPermissions' is unrecognized; expected one of:
['available', 'badPlatforms' ... 'version' ], refusing to evaluate.
| 20:09:01 |
| Sam Lehman | I checked flake.lock and my NUR input seems to be on the latest revision, so what could be preventing my NUR packages from not matching the latest from rycee's repo that define meta.mozPermissions for the firefox addons?
| 20:12:25 |
| vcunat | To me that sounds more like question for rycee. | 20:42:53 |
| 19 Sep 2023 |
 K900 ⚡️ | So uh | 14:02:54 |
| K900 ⚡️ | https://github.com/colemickens/flake-firefox-nightly/commit/85bed151ce3966327af4bfccf5ef0d1bad479733 | 14:02:56 |
| K900 ⚡️ | Any idea why Firefox would start just segfaulting on startup after this commit | 14:03:05 |
| K900 ⚡️ | It just hard segfaults immediately | 14:04:52 |
| K900 ⚡️ | Even before the crash handler is set up | 14:05:05 |
| nbp | strace says anything? | 14:05:07 |
| K900 ⚡️ | mprotect(0x7f389129c000, 4096, PROT_READ) = 0
mprotect(0x7f389129c000, 4096, PROT_READ|PROT_WRITE) = 0
mprotect(0x7f389129c000, 4096, PROT_READ) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x1ed40} --- | 14:05:14 |
| K900 ⚡️ | Looks sus but nothing immediate | 14:05:20 |
| nbp | I know there is a process which checks for GPU support which has been broken since 2/3 releases … | 14:05:38 |
