support nixos 22.05 + remove bud and misleading onboarding docs (via #477) #476
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
montchr
changed the title
|
currently failing checks in devos: ...
warning: flake output attribute 'devShell' is deprecated; use 'devShells.<system>.default' instead
error: Package ‘btrfs-progs-5.17’ in /nix/store/rk75azx537h33ddmna2hvmb2l4fhw5r0-source/pkgs/tools/filesystems/btrfs-progs/default.nix:60 is not supported on ‘x86_64-darwin’, refusing to evaluate.
a) To temporarily allow packages that are unsupported for this system, you can use an environment variable
for a single invocation of the nix tools.
$ export NIXPKGS_ALLOW_UNSUPPORTED_SYSTEM=1
Note: For `nix shell`, `nix build`, `nix develop` or any other Nix 2.4+
(Flake) command, `--impure` must be passed in order to read this
environment variable.
b) For `nixos-rebuild` you can set
{ nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.
c) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
{ allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.
(use '--show-trace' to show detailed location information)
rm 'examples/devos/flake.lock'
exit 1: command [/nix/store/lsl7mwsi2ag0170gkfhgppfz1bxha696-nix-2.9.1/bin/nix flake check "$@"] failed |
|
welp, it looks like the fix is removing |
This has been planned for some time. It seems necessary to do so now because after updating inputs to track NixOS 22.05 channels and releases, checks fail unexpectedly, with the traces leading back to `bud`. Disabling its modules allows checks to run successfully. Rather than figuring out what's going wrong with `bud`, it seems more appropriate to remove it as planned.
Many many people have complained about the misleading documentation. Rather than continuing the path of "we need to fix this", we can reduce the harmful effects of the inaccurate docs by removing them all together. Since much of the confusion in the "getting started" docs came from `bud`-specific instructions, and `bud` is being removed, removing the inaccurate docs also seems like it can be a kick towards replacing them. Also: - The NixOS manual is the canonical guide to installation. We don't need to repeat its instructions. - The numerous references to networking configuration don't have a place within Digga -- I'm assuming these are `bud`-specific things which are no longer relevant with `bud` gone.
|
now depends on #477 |
remove bud and misleading onboarding docs
montchr
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
22.05 is the current version of NixOS, so we should update digga to match.
fixes #475