search

nix-community / home-manager

Manage a user environment using Nix [maintainer=@rycee]
https://nix-community.github.io/home-manager/
MIT License
7.07k stars 1.82k forks source link

bug: docs should mention channel nixpkgs #5120

Open giggio opened 8 months ago

giggio commented 8 months ago

Are you following the right branch?

Is there an existing issue for this?

Issue description

I followed the docs to install home-manager (standalone home-manager, multi-user nix), but updates did not work. I was running:

nix-channel --update
home-manager switch

But packages did not update.

I found out that I only had the home-manager channel available, as stated in the docs:

Add the appropriate Home Manager channel. If you are following Nixpkgs master or an unstable channel you can run

nix-channel --add https://github.com/nix-community/home-manager/archive/master.tar.gz home-manager
nix-channel --update

After I added the nixpkgs channel it worked:

nix-channel --add https://nixos.org/channels/nixos-unstable nixpkgs
nix-channel --update
home-manager switch

This is not mentioned in the docs, and I believe it should be there.

Maintainer CC

No response

System information

these 2 paths will be fetched (0.02 MiB download, 0.05 MiB unpacked):
  /nix/store/imd120fan53pgy6qi6kra0q15v5kn6dn-nix-info
  /nix/store/v099hqvw5z87423p4hz1vfhzaqa07dii-stdenv-linux
copying path '/nix/store/imd120fan53pgy6qi6kra0q15v5kn6dn-nix-info' from 'https://cache.nixos.org'...
copying path '/nix/store/v099hqvw5z87423p4hz1vfhzaqa07dii-stdenv-linux' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.146.1-microsoft-standard-WSL2, Ubuntu, 22.04.4 LTS (Jammy Jellyfish), nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.20.4`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/home/user/.nix-defexpr/channels/nixpkgs`
stale[bot] commented 5 months ago

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 you are the original author of the issue

* 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 not the original author of the 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.

Memorandum on closing issues

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.

giggio commented 5 months ago

Not stale.