Happened during a nixos-rebuild, I’m pretty sure I didn’t mess up anything, and I just changed a value in
Module `/etc/nixos/configuration.nix' has an unsupported attribute `boot'. This is caused by introducing a top-level `config' or `options' attribute. Add configuration attributes immediately on the top le
vel instead, or move all of them (namely: boot environment fonts hardware home-manager i18n networking nix nixpkgs programs security services sound system time users virtualisation xdg zramSwap) into the explici
t `config' attribute.
I’ve searched for all occurrences of boot
opened in two editor
and even looked for unicode hidden chars (maybe a zwnj be in the boot causing issue),
this is all of my lines starting with boot
This can be confusing, but the latter syntax is used to define custom options, whereas the former is just used to set them. config in the latter should contain any options the module sets, and usually contains a whole bunch of conditionals so that it changes based on what is set with the options.
The way it works is that if you omit options and config, all keys will simply be treated as if they were in config.
However, if you define a configand try to set options at the same time, nix won’t be able to distinguish between these two modes, and you get the error message you have.
The reason it talks about boot is simply because it’s the first problem it encountered.
Thus, while looking for boot is nice and all, I really need to see your full config file to se where you went wrong. You probably added an options or config somewhere
Right, I wish the output would have mentioned to look for option and config clearly
the following line, caused me this issue config.firefox.enablePlasmaBrowserIntegration = true;