gchristensen changed the topic of #nixos-borg to: https://www.patreon.com/ofborg https://monitoring.nix.ci/dashboard/db/ofborg?refresh=10s&orgId=1&from=now-1h&to=now "I get to skip reviewing the PHP code and just wait until it is rewritten in something sane, like POSIX shell. || https://logs.nix.samueldr.com/nixos-borg
supersandro2000 has quit [Disconnected by services]
supersandro2000 has joined #nixos-borg
cole-h has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 240 seconds]
cole-h has joined #nixos-borg
cole-h has quit [Ping timeout: 240 seconds]
<flokli> piegames: lib/minver.nix is at 2.2. That can't be bumped too easily, as older nix still need to be able to evaluate the new nixpkgs
<flokli> I'm not sure about the garanties we have on these versions
orivej has joined #nixos-borg
<infinisil> flokli: I think we should solve this by having each nixpkgs version point to the earliest previous nixpkgs version that can fully evaluate the current one
<infinisil> E.g. `pkgs.minNixpkgsSrc = fetchTarball { url = "https://github.com/NixOS/nixpkgs/archive/<rev>.tar.gz"; sha256 = "..."; }`
<infinisil> Then people can always build a Nix from that version to evaluate the current nixpkgs
<infinisil> But also, if the users current Nix can't even evaluate minNixpkgsSrc, it uses the minNixpkgsSrc one level deeper
<infinisil> And so on. So you have a chain of nixpkgs versions, where you can go back arbitrarily far
<flokli> Not sure if this shouldn't then be some sort of language feature
<flokli> Which we don't even have yet
<infinisil> How would that be a language feature?
<infinisil> With such an approach we can also enforce minVer, because CI could use the Nix version from minNixpkgsSrc
<infinisil> Also, we could properly bootstrap the Nix for nixos-rebuild like that
<gchristensen> what about it requires 2.3.10?
<gchristensen> I'm pretty sure we try to not use new Nix features for at least 1 year
<infinisil> Oh, you're talking to piegames (who isn't here anymore)
<hexa-> something about handling unicode
<hexa-> the extension descriptions apparently contained \u0000 sequences which made nix 2.2. trip
<flokli> and these are generated in some updater script?
<flokli> we might just be able to "sanitize" them
<hexa-> they are the ones pulled from extensions.g.o
evanjs has joined #nixos-borg
orivej has quit [Ping timeout: 272 seconds]
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-borg
supersandro2000 has quit [Quit: The Lounge - https://thelounge.chat]
supersandro2000 has joined #nixos-borg
<{^_^}> [ofborg] @veprbl opened pull request #548 → config.public.json: add paths for the "6.topic: agda" tag → https://github.com/NixOS/ofborg/pull/548
<andi-> I also already recommended just sanitizing the input... If there is wild unicode sequences in there we can probably just strip them.
<andi-> Might not look perfect but better than requiring a update of Nix. In ~2y or whenever we can still remove that.
supersandro2000 has quit [Quit: The Lounge - https://thelounge.chat]
supersandro2000 has joined #nixos-borg
cole-h has joined #nixos-borg
orivej has quit [Ping timeout: 240 seconds]
<{^_^}> [ofborg] @cole-h merged pull request #548 → config.public.json: add paths for the "6.topic: agda" tag → https://github.com/NixOS/ofborg/pull/548