!VRULIdgoKmKPzJZzjj:nixos.org

Nix Package Manager development

873 Members
For people hacking on Nix: https://github.com/NixOS/nix Nix maintainers can be reached here.183 Servers

Load older messages


SenderMessageTime
31 Mar 2025
@emilazy:matrix.orgemily there's a reason we avoid doing major bumps shortly before release even when we haven't totally rewritten a package 20:57:30
@Ericson2314:matrix.orgJohn EricsonI think that delay applies more to the source code / behavior content than the packaging itself20:58:12
@Ericson2314:matrix.orgJohn Ericsonthe thing that is rushed here feels much more "meta"20:58:21
@emilazy:matrix.orgemilyand right now I am taking time out of my evening outside because the costs of insufficient communication have been externalized and this needs resolving days before the freeze20:58:34
@Ericson2314:matrix.orgJohn Ericsonthis is why it is crucial to mentally separate 2.2{4,7} from build system / packaging / etc.20:58:51
@elvishjerricco:matrix.orgElvishJerricco raitobezarius: I would like to know an example I could use to verify whether or not Nix actually has the problem you describe. 20:58:54
@Ericson2314:matrix.orgJohn Ericson emily: I would just go back to doing your normal evening things then 20:59:16
@emilazy:matrix.orgemily
In reply to @Ericson2314:matrix.org
this is why it is crucial to mentally separate 2.2{4,7} from build system / packaging / etc.
as I said, if the old packaging was restored then there would be a much more viable discussion of whether to bump
20:59:38
@emilazy:matrix.orgemilyI'm happy to separate those20:59:45
@Ericson2314:matrix.orgJohn Ericsonlet me try to do this bump, and if I screw it up in the next few days you can "haha told you it was harder than you thought!" me all you like :)20:59:52
@emilazy:matrix.orgemilyi don't think "don't worry about it, I'm going to do it anyway" is reassuring for the concerns I am trying to raise21:00:19
@Ericson2314:matrix.orgJohn Ericson(I am still thinking pre 9th freeze period start)21:00:24
@Ericson2314:matrix.orgJohn Ericsonthat is why I introduced "next few days"21:00:39
@Ericson2314:matrix.orgJohn Ericson the honus is on me to get a bunch of stuff working quickly, so we still have vastly more time for unkown-unknowns 21:01:06
@Ericson2314:matrix.orgJohn Ericson * the onus is on me to get a bunch of stuff working quickly, so we still have vastly more time for unkown-unknowns 21:01:13
@emilazy:matrix.orgemily I think you're responding but not listening. I'm trying to tell you why this relationship has become fraught and what we can do to fix it. if you filed off the Nix name and asked any of the people who handle bumps of major packages in Nixpkgs whether now is a good time for a change like this at this point in the release process they'd tell you it's nuts. 21:01:31
@emilazy:matrix.orgemily "don't worry, I'll fix it" isn't a helpful response to that. those people put lots of effort into fixing things too 21:01:51
@emilazy:matrix.orgemilyand the response to some of the things that need fixing like breaking all overrides with no "safe" option for the transition period between Nixpkgs releases and no deprecation warnings has just been wontfix21:02:31
@elvishjerricco:matrix.orgElvishJerricco John Ericson: While I personally don't object to a Nix bump, I do think you need to realize that you are undermining the release managers by doing something to the release that they don't want. 21:02:46
@Ericson2314:matrix.orgJohn Ericsonhow many people are against the version bump separately from the packaging concerns?21:03:27
@Ericson2314:matrix.orgJohn EricsonUpstream doesn't have prerogative on downstream packaging style, I know21:03:59
@emilazy:matrix.orgemilyI don't think it is a good idea based on past precedent. i would be perfectly happy to bump to the new version with the old packaging immediately after branch off21:04:14
@Ericson2314:matrix.orgJohn Ericsonmy claim of authority there is not "I am a Nix developer" but "there was an RFC about layering"21:04:23
@emilazy:matrix.orgemilyif it goes swimmingly, then next time around that's something we can point to21:04:39
@emilazy:matrix.orgemilywe listened, talked, worked together, made a show of cooperation by changing the plan in response to concerns, and it went totally fine21:05:01
@emilazy:matrix.orgemilyi would be very happy with that outcome21:05:09
@emilazy:matrix.orgemilywe could also ship a patching interface that works with both old and new packaging in 25.0521:06:06
@emilazy:matrix.orgemilyto help a transition to that21:06:15
@emilazy:matrix.orgemilyjust like we do with lib changes21:06:21
@Ericson2314:matrix.orgJohn EricsonOn the level of really slowing down and listening, I feel like all the upset about the new packaging has been on things that are not actually the split itself21:06:47

Show newer messages


Back to Room ListRoom Version: 6