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

nixUnstable = nixStable #175603

Merged
merged 1 commit into from
Jun 12, 2022
Merged

nixUnstable = nixStable #175603

merged 1 commit into from
Jun 12, 2022

Conversation

edolstra
Copy link
Member

Description of changes

Now that we have regular (6-weekly) releases, there no longer is a compelling reason to have an unstable version of Nix in Nixpkgs. People who really need the bleeding edge can use the 'nix' flake.

Things done
  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 22.11 Release Notes (or backporting 22.05 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
    • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
  • Fits CONTRIBUTING.md.

Now that we have regular (6-weekly) releases, there no longer is a
compelling reason to have an unstable version of Nix in
Nixpkgs. People who really need the bleeding edge can use the 'nix'
flake.
@vcunat
Copy link
Member

vcunat commented May 31, 2022

👍🏽 and /cc PR #175541

@bobby285271 bobby285271 added the 12.approvals: 1 This PR was reviewed and approved by one reputable person label Jun 1, 2022
sha256 = "sha256-RH77Y4IhbTofNYlLQSGKLL0fJAG9iHSwRNvMEZ4M0VQ=";
};
});
unstable = self.stable;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'd prefer not to remove it but if it is wanted then this should be turned in to a throw alias that explains why it has been removed

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The title says "remove" but to me it's more like increasing version of nixUnstable to 2.8.

@vcunat vcunat changed the title Remove nixUnstable nixUnstable = nixStable Jun 12, 2022
@vcunat vcunat merged commit c5b964b into NixOS:master Jun 12, 2022
@github-actions
Copy link
Contributor

Backport failed for release-22.05, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally.

git fetch origin release-22.05
git worktree add -d .worktree/backport-175603-to-release-22.05 origin/release-22.05
cd .worktree/backport-175603-to-release-22.05
git checkout -b backport-175603-to-release-22.05
ancref=$(git merge-base f51cb36f2c98a991b8e4fbe257dc146577075f84 f888642ec69962a5da2e80c69b731d89e61f637d)
git cherry-pick -x $ancref..f888642ec69962a5da2e80c69b731d89e61f637d

vcunat added a commit to vcunat/nixpkgs that referenced this pull request Jun 12, 2022
On master we did this in f888642 in PR NixOS#175603,
but on stable nixpkgs we surely don't want to advance nixStable.
@edolstra edolstra deleted the remove-nix-unstable branch June 15, 2022 09:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants