| 26 Oct 2024 |
emily | (IMO "removing a dead package that we anticipate will cause problems over the course of the release cycle" is one of the more sensible late breaking changes) | 18:43:14 |
Tristan Ross | In reply to @emilazy:matrix.org I think it's sensible to not ship EOL stuff for the new release. the change of default is a little painful: I would be tempted to throw on old stateVersions explaining the situation rather than potentially silently breaking things. Agreed | 18:43:59 |
Tristan Ross | In reply to @emilazy:matrix.org (IMO "removing a dead package that we anticipate will cause problems over the course of the release cycle" is one of the more sensible late breaking changes) Yeah, it's good to get those in | 18:45:15 |
Tristan Ross | The freeze is mainly to prevent any packages from breaking that could hurt the release but a security issue is imo more harmful | 18:45:49 |
| 27 Oct 2024 |
| peterwang joined the room. | 04:32:09 |
| Scrumplex joined the room. | 19:27:49 |
Scrumplex | Hi there, short question: Is renaming a package a breaking change assuming an alias is added? | 19:28:30 |
Vladimír Čunát | Hmm. If your configuration disabled aliases (that's those in aliases.nix), it would be breaking, right? | 19:30:08 |
Vladimír Čunát | Though easy to fix. | 19:30:36 |
Scrumplex | But I feel like disabling aliases is like subscribing to breakage | 19:30:51 |
Scrumplex | In my case I am just worried about causing breakage within Nixpkgs. I was pinged in two separate PRs that involve renaming a package and I wasn't sure if I can merge them during the breaking change freeze | 19:31:46 |
Vladimír Čunát | My gut feeling is that it's still fine at this point. Maybe until the release. | 19:31:53 |
Scrumplex | * In my case I am just worried about causing breakage within Nixpkgs. I was pinged in two independent PRs that involve renaming a package and I wasn't sure if I can merge them during the breaking change freeze | 19:31:58 |
Tristan Ross | The only main case I see this breaking is Ofborg | 19:32:43 |