Skip to content

staging-nixos -> staging-next#501226

Merged
vcunat merged 82 commits into
staging-nextfrom
staging-nixos
Mar 19, 2026
Merged

staging-nixos -> staging-next#501226
vcunat merged 82 commits into
staging-nextfrom
staging-nixos

Conversation

@vcunat

@vcunat vcunat commented Mar 19, 2026

Copy link
Copy Markdown
Member

Because the merge of staging-next -> master is imminent via PR #497493

kmein and others added 30 commits January 27, 2026 16:58
Co-authored-by: Jeremy Fleischman <jeremyfleischman@gmail.com>
Co-authored-by: Jeremy Fleischman <jeremyfleischman@gmail.com>
This prepares the driver for non-QEMU backends by abstracting
the machine logic.

Co-authored-by: Jeremy Fleischman <jeremyfleischman@gmail.com>
Co-authored-by: Jeremy Fleischman <jeremyfleischman@gmail.com>
Co-authored-by: Jeremy Fleischman <jeremyfleischman@gmail.com>
Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
If the names for systemd-nspawn containers are too long,
the generated bridge interface names will surpass the
kernel limit IFNAMSIZ (15 characters + '\0').
The test merely ensures that machines can reach each other
via ICMP ping. This does not require the firewall to be opened
or disabled.
@vcunat vcunat enabled auto-merge March 19, 2026 06:11
@vcunat vcunat added this pull request to the merge queue Mar 19, 2026
@nixpkgs-ci nixpkgs-ci Bot added 8.has: package (update) This PR updates a package to a newer version 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-darwin: 501+ This PR causes many rebuilds on Darwin and should normally target the staging branches. 10.rebuild-linux: 501-1000 This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-darwin: 501-1000 This PR causes many rebuilds on Darwin and should normally target the staging branches. labels Mar 19, 2026
Merged via the queue into staging-next with commit 2e5b118 Mar 19, 2026
31 checks passed
@zowoq

zowoq commented Mar 19, 2026

Copy link
Copy Markdown
Contributor

As this has been merged to staging-next but staging-next hasn't been merged to master yet, where should today's kernel updates go? master or staging-next? #501448

@zowoq zowoq mentioned this pull request Mar 19, 2026
13 tasks
@vcunat

vcunat commented Mar 20, 2026

Copy link
Copy Markdown
Member Author

It hasn't merged yet, but https://hydra.nixos.org/jobset/nixos/unstable is building it already with nixos.tests.* about halfway through now, so I believe we can still add kernel updates. Merging to master now happens basically right after clearing any channel blockers.

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

Labels

8.has: package (update) This PR updates a package to a newer version 10.rebuild-darwin: 501-1000 This PR causes many rebuilds on Darwin and should normally target the staging branches. 10.rebuild-darwin: 501+ This PR causes many rebuilds on Darwin and should normally target the staging branches. 10.rebuild-linux: 501-1000 This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches.

Projects

None yet

Development

Successfully merging this pull request may close these issues.