| 11 Nov 2023 |
 hexa | would love a review of the crimes committed in this pr | 21:54:22 |
| 12 Nov 2023 |
| hexa | nope, doesn't bootstrap | 01:41:12 |
| hexa |
error: process didn't exit successfully: /nix/store/ky7lbns8jyd9z835h06v6j01hvapvdr0-rustc-bootstrap-1.71.1/bin/rustc -vV (signal: 11, SIGSEGV: invalid memory reference)
| 01:41:25 |
| hexa | retrying rust_1_70 instead, the minimal requirement should hopefully be sufficient until the 23.05 EOL | 20:06:01 |
| hexa | firefox-beta/devedition maintainer seems unresponsive when contacted by mail https://github.com/NixOS/nixpkgs/pull/264553#issuecomment-1806896786 | 20:06:32 |
| hexa | 
Download image.png | 20:08:50 |
| hexa | three months (feb-may), then I poked them that their maintenance was lacking and that resulted in three more bumps in august | 20:09:39 |
| hexa | nothing since then | 20:09:44 |
| hexa | what is good is that I can find problems in the upcoming releases early that way | 20:10:15 |
| hexa | 120 in 9 days and we won't be blocked on backporting rust or the dbus include path issue | 20:10:58 |
| hexa | vcunat: https://www.thunderbird.net/en-US/thunderbird/115.4.2/releasenotes/ | 20:15:34 |
| hexa |
Version 115.4.2, first offered to channel users on November 6, 2023
| 20:15:50 |
| hexa | L() | 20:15:51 |
| hexa | * 🐦️ | 20:15:58 |
 vcunat | Oh, OK. Doesn't look urgent. | 20:16:17 |
| hexa | In reply to @hexa:lossy.network
retrying rust_1_70 instead, the minimal requirement should hopefully be sufficient until the 23.05 EOL looks like that bootstraps just fine. | 20:25:53 |
| 13 Nov 2023 |
|  Christoph joined the room. | 12:15:53 |
| Christoph changed their display name from c8h4 ⚡️ to Christoph. | 12:18:48 |
| Christoph set a profile picture. | 12:18:49 |
| Christoph changed their display name from Christoph to c8h4. | 12:19:01 |
 felschr | Noticed that GPU acceleration wasn't working for Tor/Mullvad Browser:
https://github.com/NixOS/nixpkgs/pull/267085 | 18:59:56 |
| Christoph | Hi, regarding issue #266620 (enabling WebRTC in Floorp) - according to this comment in buildMozillaMach, webrtcSupport should only be set through privacySupport, but what exactly is the reason for that? Setting privacySupport = true would enable a bunch of other (undesirable) stuff .. | 19:05:37 |
| Christoph | Or is the intention here that privacySupport = true should be set, and then all the unwanted things explicitly disabled? | 19:05:57 |
 K900 | No, that's not what it's set to | 19:06:15 |
| K900 | It's set to NOT privacySupport | 19:06:21 |
| K900 | So it'll be enabled if privacySupport is disabled | 19:06:32 |
| Christoph | Yeah, that's the thing, as that would also enable e.g. geolocationSupport .. so there no way to enable webrtc while keeping geolocation disabled? IOW, would privacySupport = false; geolocationSupport = false; be a supported configuration? | 19:13:22 |
| Christoph | If one wants webrtc enabled, while keeping the rest of the stuff that privacySupport = false entails disabled | 19:13:22 |
| Christoph | Or am I missing something here completely? | 19:14:02 |
| K900 | privacySupport only disables features | 19:15:07 |
