Skip to content

~flake.lock:~ Update Nixpkgs (partial backport #13010) #13064

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

Merged
merged 2 commits into from
Apr 23, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 23, 2025

Motivation

This fixes evaluation for Windows. There are unfortunately deps that still don't build, but this can be fixed next.

Context


Add 👍 to pull requests you find important.

The Nix maintainer team uses a GitHub project board to schedule and track reviews.


This is an automatic backport of pull request #13010 done by [Mergify](https://mergify.com).

@mergify mergify bot requested a review from edolstra as a code owner April 23, 2025 10:46
@mergify mergify bot added automatic backport This PR is a backport produced by automation (does not trigger backporting) conflicts merge-queue labels Apr 23, 2025
Copy link
Contributor Author

mergify bot commented Apr 23, 2025

Cherry-pick of f6df573 has failed:

On branch mergify/bp/2.28-maintenance/pr-13010
Your branch is up to date with 'origin/2.28-maintenance'.

You are currently cherry-picking commit f6df573a9.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   flake.lock

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

roberth and others added 2 commits April 23, 2025 16:42
... by moving our stuff out of the way from upstream's
`nixComponents` and `nixDependencies` attrsets.

(I prefer not to use overlays, but let's make it work this way
first)

(cherry picked from commit b257ea9)
Co-authored-by: Robert Hensing <[email protected]>
(cherry picked from commit ef36806)
@roberth roberth changed the title flake.lock: Update Nixpkgs (backport #13010) ~flake.lock:~ Update Nixpkgs (backport #13010) Apr 23, 2025
@roberth roberth changed the title ~flake.lock:~ Update Nixpkgs (backport #13010) ~flake.lock:~ Update Nixpkgs (partial backport #13010) Apr 23, 2025
@roberth roberth force-pushed the mergify/bp/2.28-maintenance/pr-13010 branch from 6e37dfc to f666ec3 Compare April 23, 2025 14:42
@mergify mergify bot merged commit 7092171 into 2.28-maintenance Apr 23, 2025
18 checks passed
@mergify mergify bot deleted the mergify/bp/2.28-maintenance/pr-13010 branch April 23, 2025 15:09
@Ericson2314
Copy link
Member

Ah the title is a bit misleading. Glad this didn't actually bump Nixpkgs as that would break the windows build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automatic backport This PR is a backport produced by automation (does not trigger backporting) conflicts merge-queue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants