-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
home-manager as nixos module is broken with documentation.nixos.includeAllModules=true #896
Comments
I have good news! And I have bad news... I think. The good news is that I think this was fixed in NixOS/nixpkgs#73966 A workaround until the fix is added to your channel may be to use the ustable So, if you're using home-manager as a NixOS module you could do something like this{ config, ... }:
let
# Make pkgs.unstable available for future usage
addUnstableScope = self: super: {
unstable = import <nixos-unstable> {
config = config.nixpkgs.config;
};
};
# Use pkgs.unstable.nixosOptionsDoc instead of pkgs.nixosOptionsDoc
upgradePackages = self: super: {
nixosOptionsDoc = self.unstable.nixosOptionsDoc;
};
in {
nixpkgs.overlays = [ addUnstableScope upgradePackages ];
} And now the bad news; When you get past that point there's another problem (which is also mentioned in NixOS/nixpkgs#73966):
I'm trying to investigate it, but any help is appreciated since the documentation is a new area to me. It looks like the "unknown ID" option is defined here: https://github.com/rycee/home-manager/blob/release-19.09/modules/services/window-managers/i3.nix#L387 so I'm not yet sure what the issue really is. Maybe it is looking in the wrong place (the ID is defined wrong)? I dunno. But I'm thinking |
This is still an issue... |
Ah, your link references the release pinned at 19.09. Current unstable does have an assigns option, but it's hidden in a nullable submodule type: https://github.com/rycee/home-manager/blob/5969551a5cc52f9470b5ff5ca01327bf4bda82c1/modules/services/window-managers/i3-sway/i3.nix#L254 - I think that may be the underlying issue, because once I made that type non-nullable, I saw a similar issue due to a nullable string in |
I give up trying to fix this. I got as far as this patch to fix al the bad validations, and then the manual derivations fail to build at all due to illegal path references. |
FWIW I'm currently using this as a workaround: Ma27@01db651 A few thoughts in case people are interested in getting this fixed here:
|
Thank you for your contribution! I marked this issue as stale due to inactivity. If this remains inactive for another 7 days, I will close this issue. Please read the relevant sections below before commenting. If you are the original author of the issue
If you are not the original author of the issue
Memorandum on closing issuesIf you have nothing of substance to add, please refrain from commenting and allow the bot close the issue. Also, 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. |
I get
With the following in configuration.nix:
Commenting the
documentation
line allow thenixos-rebuild
The text was updated successfully, but these errors were encountered: