fix: use patched nix 2.18
turns out this doesn't have the problem linked in the previous commit
This commit is contained in:
parent
f10bfc5db6
commit
f56cb4afa8
2 changed files with 2 additions and 2 deletions
|
@ -12,7 +12,7 @@ in {
|
||||||
nixpkgs.config.allowUnfree = true;
|
nixpkgs.config.allowUnfree = true;
|
||||||
nix = {
|
nix = {
|
||||||
gc.automatic = true;
|
gc.automatic = true;
|
||||||
package = pkgs.nixVersions.nix_2_17;
|
package = pkgs.nixVersions.nix_2_18;
|
||||||
settings =
|
settings =
|
||||||
{
|
{
|
||||||
auto-optimise-store = true;
|
auto-optimise-store = true;
|
||||||
|
|
|
@ -12,7 +12,7 @@
|
||||||
config = {
|
config = {
|
||||||
nixpkgs = {
|
nixpkgs = {
|
||||||
overlays = overlays;
|
overlays = overlays;
|
||||||
config.permittedInsecurePackages = ["nix-2.17.1"];
|
config.permittedInsecurePackages = [];
|
||||||
};
|
};
|
||||||
home-manager = {
|
home-manager = {
|
||||||
backupFileExtension = "backup";
|
backupFileExtension = "backup";
|
||||||
|
|
Loading…
Reference in a new issue