Skip to content
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

break(nix): disable nix channels #466

Merged
merged 1 commit into from
Aug 30, 2024
Merged

break(nix): disable nix channels #466

merged 1 commit into from
Aug 30, 2024

Conversation

zimbatm
Copy link
Member

@zimbatm zimbatm commented Jul 16, 2024

Channels are not reproducible and should be removed.

This change:

  • removes the nix-channel binary
  • sets an empty NIX_PATH
  • stop adding the /root/.nix-channels file

This will lead scripts depending on channels to break, exposing their dependency on channels.

Channels are not reproducible and should be removed.

This change:
* removes the `nix-channel` binary
* sets an empty NIX_PATH
* stop adding the /root/.nix-channels file

This will lead scripts depending on channels to break, exposing their
dependency on channels.
@SuperSandro2000
Copy link
Member

  • sets an empty NIX_PATH

that unfortunately currently breaks things NixOS/nixpkgs#323613

@Mic92
Copy link
Member

Mic92 commented Aug 25, 2024

With the pull request closed, is this now merge-able? NixOS/nixpkgs#323613

@phaer
Copy link
Member

phaer commented Aug 30, 2024

I believe it is! That PR was also backported, so we should be good with stable support.

One think we could consider in another PR is to set NIX_PATH and flake registry.json entries for config.srvos.flake and config.srvos.flake.inputs.nixpkgs where config.srvos.flake is set.

@zimbatm zimbatm merged commit b8e1078 into main Aug 30, 2024
98 checks passed
@zimbatm zimbatm deleted the disable-nix-channels branch August 30, 2024 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants