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

[Backport release-24.05] lixVersions.lix_2_91: init #336617

Merged
merged 3 commits into from
Sep 10, 2024

Conversation

lf-
Copy link
Member

@lf- lf- commented Aug 22, 2024

Description of changes

Original PR: #334269

This adds Lix 2.91.0 to nixpkgs and sets it as the default Lix release.
This is compliant with the 24.05 stability policy because Lix 2.91 does
not break any users (io_uring is already only partially available due to
old kernels, nobody on github uses build-hook, and nix 2.3 is the oldest
version of nix with security support).

Reviewer note: this is split into commits on purpose. I recommend an ignore-whitespace diff (?w=1 in url on github).

Blog post:
https://lix.systems/blog/2024-08-12-lix-2.91-release/

Release notes:
https://docs.lix.systems/manual/lix/stable/release-notes/rl-2.91.html

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • 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/)
  • 24.11 Release Notes (or backporting 23.11 and 24.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
  • Fits CONTRIBUTING.md.

Add a 👍 reaction to pull requests you find important.

This meant that pkgs.lix.passthru.tests.misc never evaluated.

It should be noted that it seems like completely different test
infrastructure is in use on master (25.11), or maybe it is just that the
same test got renamed to nix-misc. Either way, this is busted.
This differs in two ways from master:
- tests.misc uses the nixos test name used in 24.05
- the boost stuff rendered obsolete when
  NixOS#86131 was fixed is left
  intact, since it is not fixed in 24.05

This does *not* differ in the accidentally disabling LTO. That's fixed
in the 2.91 commit.

Seems to build on x86_64-linux.

This commit is done so that we can more directly cherry-pick future lix
versions from master by removing gratuitous divergences in the package
that make maintenance annoying (it seems like master has experienced a
round of nixfmt-rfc-style).
Original PR: NixOS#334269

This adds Lix 2.91.0 to nixpkgs and sets it as the default Lix release.
This is compliant with the 24.05 stability policy because Lix 2.91 does
not break any users (io_uring is already only partially available due to
old kernels, nobody on github uses build-hook, and nix 2.3 is the oldest
version of nix with security support).

Blog post:
https://lix.systems/blog/2024-08-12-lix-2.91-release/

Release notes:
https://docs.lix.systems/manual/lix/stable/release-notes/rl-2.91.html

Change-Id: I6960314bddceb7ab10e3cd6d9842d578f501fd76

Co-authored-by: Atemu <[email protected]>
Co-authored-by: Yureka <[email protected]>
Co-authored-by: getchoo <[email protected]>
(cherry picked from commit 5b6d2fb)
@lf-
Copy link
Member Author

lf- commented Aug 23, 2024

(yes this is not a pure cherry pick. this is deliberate, i hopefully structured the commits to make reviewing it ok)

@k1gen
Copy link

k1gen commented Aug 26, 2024

can anyone review this?

@yu-re-ka yu-re-ka merged commit 196c3de into NixOS:release-24.05 Sep 10, 2024
27 of 28 checks passed
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.

3 participants