| 17 Jul 2022 |
Winter (she/her) | oh huh what
what Nixpkgs revision and Nix version are you using? | 04:56:10 |
@rendakuenthusiast:imperishable.name | also setting it to false | 04:56:14 |
@rendakuenthusiast:imperishable.name | I'm never sure quite how to figure that out | 04:56:31 |
@rendakuenthusiast:imperishable.name | in the hive file I have nixpkgs = <nixpkgs>. so that says, use the nixpkgs version on my local system, right? | 04:56:49 |
@rendakuenthusiast:imperishable.name | but I'm not sure how ot figure out what I have running locally | 04:57:00 |
Winter (she/her) | In reply to @rendakuenthusiast:imperishable.name in the hive file I have nixpkgs = <nixpkgs>. so that says, use the nixpkgs version on my local system, right? correct | 04:57:07 |
Winter (she/her) | In reply to @rendakuenthusiast:imperishable.name also setting it to false wait so enableACME = true -> no segfault, but false -> segfault?? | 04:57:42 |
@rendakuenthusiast:imperishable.name | I used to have a complicated thing there that I think was pinning the version of nixpkgs deployed to the remote host to a specific git commit, but I had to get rid of that | 04:57:43 |
@rendakuenthusiast:imperishable.name | In reply to @winterqt:nixos.dev wait so enableACME = true -> no segfault, but false -> segfault?? yes | 04:57:56 |
Winter (she/her) | what the hell | 04:58:00 |
Winter (she/her) | can younix-shell -p nix-info --run "nix-info -m" and post the output? | 04:59:17 |
Winter (she/her) | * can you nix-shell -p nix-info --run "nix-info -m" and post the output? | 04:59:40 |
Winter (she/her) | * can you nix-shell -p nix-info --run "nix-info -m" and post the output? | 04:59:52 |
@rendakuenthusiast:imperishable.name | - system: `"x86_64-linux"`
- host os: `Linux 5.18.11-arch1-1, Arch Linux, noversion, rolling`
- multi-user?: `yes`
- sandbox: `no`
- version: `nix-env (Nix) 2.10.1`
- channels(root): `""`
- channels(myusername): `"nixpkgs"`
- nixpkgs: `/nix/var/nix/profiles/per-user/myusername/channels/nixpkgs`
| 05:00:41 |
Winter (she/her) | :( no version info
okay, can you try just directly using the output of the function? like, do "..." = { enableACME = false; locations = ...; } to see if it's the function invocation that's causing it for whatever reason? | 05:02:34 |
Winter (she/her) | oh also can you run nix-instantiate --eval -E '(import <nixpkgs> {}).lib.nixpkgsVersion' | 05:03:20 |
@rendakuenthusiast:imperishable.name | I already did that, it's not just the function invocation, it's having the full block there too | 05:04:57 |
@rendakuenthusiast:imperishable.name | that command gets me:
trace: `lib.nixpkgsVersion` is deprecated, use `lib.version` instead!
"22.11pre388097.9a17f325397"
| 05:05:30 |
Winter (she/her) | can you switch your nixpkgs channel temporarily to nixos-unstable-small, update it, and try to apply again? (i'm not sure what that process looks like on non-NixOS) | 05:13:27 |
Winter (she/her) | it has a newer Nix version | 05:13:57 |
@rendakuenthusiast:imperishable.name | how do I do that? | 05:25:05 |
Winter (she/her) | nix-channel --add https://nixos.org/channels/nixos-unstable-small nixpkgs && nix-channel --update | 05:30:16 |
Winter (she/her) | you know better than me how to update Nix and such from that afterwards, though 😅 | 05:30:56 |
Winter (she/her) | (hopefully) | 05:31:04 |
@rendakuenthusiast:imperishable.name | ok I'll try that | 05:32:43 |
@rendakuenthusiast:imperishable.name | what is nixos-unstable-small? I"ve never seen that before | 05:32:51 |
@rendakuenthusiast:imperishable.name | anyway that did something | 05:32:57 |
Winter (she/her) | cool. can you update Nix (again, i assume you've done this before, if you haven't let me know and i can scour the docs), make sure nix --version reports 2.10.3, and try to apply it again? | 05:35:34 |
@rendakuenthusiast:imperishable.name | okay, I'm trying this again, and it seems to be taking longer and not crashing | 05:36:42 |
@rendakuenthusiast:imperishable.name | I assume it's updating every single package somehow | 05:36:50 |