Open V4G4X opened 9 months ago
I referred to this, but their solution of doing a simple nix-channel --update
didn't work for me.
You are almost certainly having an old Nixpkgs somewhere. Try running nix-channel --update
both as root
and as your regular user.
I am sure I had tried this before, but yes. This changed things.
I have now started getting a version mismatch in the logs.
How do I fix this?
❯ darwin-rebuild check
building the system configuration...
trace: warning: varungawande profile: You are using
Home Manager version 23.11 and
Nixpkgs version 24.05.
Using mismatched versions is likely to cause errors and unexpected
behavior. It is therefore highly recommended to use a release of Home
Manager that corresponds with your chosen release of Nixpkgs.
If you insist then you can disable this warning by adding
home.enableNixpkgsReleaseCheck = false;
to your configuration.
ok
nvm.
So running nix-channel --add https://github.com/nix-community/home-manager/archive/master.tar.gz home-manager
did it for me.
I was able to change the version of home-manager by listing nix-channels, and adding master
(latest).
I had a couple of questions.
Nixpkgs
version? (Here it's 24.05)Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.
* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.
Are you following the right branch?
Is there an existing issue for this?
Issue description
I am trying
darwin-rebuild check
.There's been no change to my config but I get this:
How do I fix this?
Maintainer CC
No response
System information