Skip to content

[Backport release-25.11] nixVersions.nix_2_33: init#491376

Open
ulucs wants to merge 1 commit intoNixOS:release-25.11from
ulucs:ulucs/push-souyossrpspy
Open

[Backport release-25.11] nixVersions.nix_2_33: init#491376
ulucs wants to merge 1 commit intoNixOS:release-25.11from
ulucs:ulucs/push-souyossrpspy

Conversation

@ulucs
Copy link
Contributor

@ulucs ulucs commented Feb 17, 2026

Things done

Cherry-picked #480542 for backporting

  • Built on platform:
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • Tested, as applicable:
  • Ran nixpkgs-review on this PR. See nixpkgs-review usage.
  • Tested basic functionality of all binary files, usually in ./result/bin/.
  • Nixpkgs Release Notes
    • Package update: when the change is major or breaking.
  • NixOS Release Notes
    • Module addition: when adding a new NixOS module.
    • Module update: when the change is significant.
  • Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

This report is automatically generated by the PR / Check / cherry-pick CI workflow.

Some of the commits in this PR require the author's and reviewer's attention.

Please follow the backporting guidelines and cherry-pick with the -x flag.
This requires changes to the unstable master and staging branches first, before backporting them.

Occasionally, commits are not cherry-picked at all, for example when updating minor versions of packages which have already advanced to the next major on unstable.
These commits can optionally be marked with a Not-cherry-picked-because: <reason> footer.

If you need to merge this PR despite the warnings, please dismiss this review shortly before merging.

Warning

Couldn't locate the cherry-picked commit's hash in the commit message of 44566e2.

Hint: The full diffs are also available in the runner logs with slightly better highlighting.

@ulucs ulucs force-pushed the ulucs/push-souyossrpspy branch 2 times, most recently from 0e6950d to 1fe8273 Compare February 17, 2026 12:18
@ulucs
Copy link
Contributor Author

ulucs commented Feb 17, 2026

I see there have been quite a lot of patch upgrades; do they also go in this PR, or is the backport bot able to handle them?

@nixpkgs-ci nixpkgs-ci bot requested review from a team and RaitoBezarius February 17, 2026 12:23
@nixpkgs-ci nixpkgs-ci bot added 8.has: package (new) This PR adds a new package 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 4.workflow: backport This targets a stable branch labels Feb 17, 2026
@xokdvium
Copy link
Contributor

Would make sense to init at 2.33.3

@ulucs ulucs force-pushed the ulucs/push-souyossrpspy branch from 1fe8273 to 44566e2 Compare February 17, 2026 12:40
@ulucs
Copy link
Contributor Author

ulucs commented Feb 17, 2026

the builds were successful on both linuxes and aarch64-darwin (after pulling in the patches disabling flaky tests)

@ulucs
Copy link
Contributor Author

ulucs commented Mar 3, 2026

@xokdvium are there any other changes you need from me?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4.workflow: backport This targets a stable branch 8.has: package (new) This PR adds a new package 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants