| 19 May 2024 |
 raboof | how does the release process work with respect to breaking changes? https://github.com/NixOS/nixpkgs/issues/303285 says "no breaking changes on any branch from 2024-05-01". https://github.com/NixOS/nixpkgs/pull/309347 was merged 2024-05-16, but it turns out that broke python3Packages.pythonocc-core (https://github.com/NixOS/nixpkgs/issues/312955). Fixing this on the pythonocc-core side seems nontrivial. should we revert https://github.com/NixOS/nixpkgs/pull/309347 for now? | 18:42:48 |
 vcunat | Yes, I think so. | 18:43:40 |
| vcunat | (I haven't looked at the links, just your description.) | 18:43:51 |
| vcunat | * Yes, I believe so. | 18:44:03 |
| raboof | ah wait there might be a way out - I'll try and see if I can fix pythonocc-core after all, otherwise I'll create the revert PR | 18:44:49 |
| raboof | (looks like I could avoid a revert, https://github.com/NixOS/nixpkgs/pull/312962, though nixpkgs-review seems to choke on it for some reason?) | 19:06:56 |
| raboof | * (looks like I could avoid a revert, https://github.com/NixOS/nixpkgs/pull/312962 😄) | 19:45:25 |
| 20 May 2024 |
 hexa | Who has merge access here? https://github.com/NixOS/calamares-nixos-extensions/pull/33 | 22:17:13 |
