-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
bug: installation fails with XML validation errors #3342
Comments
I just tried switching home-manager to track 22.05, but alas no change.
|
I'm also able to reproduce this with a completely "blank" { config, pkgs, ... }:
{
home.username = "sam.ainsworth";
home.homeDirectory = "/home/sam.ainsworth";
home.stateVersion = "22.05";
programs.home-manager.enable = true;
} |
Workaround: add |
Btw, just noticed that even when manpages are disabled HM still gives the same intro message after the install is finished:
which is misleading |
Seems to be an "upstream" nixpkgs issue: NixOS/nixpkgs#196651. |
Related: https://gitlab.com/rycee/nmd As I understand, it's upstream, but not nixpkgs, instead the doc framework? |
Hopefully fixed now. |
Hmm faced with something similar while upgrading to 22.11. Here is the log. Disabling manuals in home-manager allowed to proceed. Should I create new issue? |
@ein-shved how did you do it? Read the code, found the keys. Adding this fixes to
|
Results in a buildfailure, revert after home-manager updates to fix it themselves. See nix-community/home-manager#3342
Results in a buildfailure, revert after home-manager updates to fix it themselves. See nix-community/home-manager#3342
Results in a buildfailure, revert after home-manager updates to fix it themselves. See nix-community/home-manager#3342
Are you following the right branch?
Is there an existing issue for this?
Issue description
When attempting to install home-manager I get an error:
Full log: https://gist.github.com/samuela/e4b0c8362e32f8fcfffcd8acc088d511
Maintainer CC
@rycee @ncfavier @aakropotkin
System information
The text was updated successfully, but these errors were encountered: