-
-
Notifications
You must be signed in to change notification settings - Fork 17.5k
virtualbox: 7.1.6a -> 7.1.8 #400278
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
virtualbox: 7.1.6a -> 7.1.8 #400278
Conversation
|
@muellerbernd could you (or someone else) please run |
|
| virtualboxSubVersion = ""; | ||
| virtualboxSha256 = "3f7132c55ac6c5f50585bfaa115d29e30b47ccf535cb0a12ff50214ddae2f63d"; | ||
|
|
||
| kvmPatchVersion = "20250207"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
KVM patch for 7.1.6 still applies with 7.1.8, we might want to adjust the build to avoid breaking virtualbox-kvm
diff --git a/pkgs/applications/virtualization/virtualbox/default.nix b/pkgs/applications/virtualization/virtualbox/default.nix
index 524b873be198..6a4bddaaab2b 100644
--- a/pkgs/applications/virtualization/virtualbox/default.nix
+++ b/pkgs/applications/virtualization/virtualbox/default.nix
@@ -249,8 +249,8 @@ stdenv.mkDerivation (finalAttrs: {
++ optional enableKvm (
let
patchVboxVersion =
- # There is no updated patch for 7.0.22 yet, but the older one still applies.
- if finalAttrs.virtualboxVersion == "7.0.22" then "7.0.20" else finalAttrs.virtualboxVersion;
+ # There is no updated patch for 7.1.8 yet, but the older one still applies.
+ if finalAttrs.virtualboxVersion == "7.1.8" then "7.1.6" else finalAttrs.virtualboxVersion;
in
fetchpatch {
name = "virtualbox-${finalAttrs.virtualboxVersion}-kvm-dev-${finalAttrs.kvmPatchVersion}.patch";
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer your proposed change as a separate PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer to have it in the same PR, as otherwise this breaks the virtualbox-kvm build needlessly. In general, we may consider moving virtualbox-kvm to a separate package, so the versions can be bumped independently when the KVM patch does not apply.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pushed the change to re-use the 7.1.6 patch for virtualboxKvm so we do not break it.
Yarny0
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review per https://github.com/NixOS/nixpkgs/tree/f771eb401a46846c1aebd20552521b233dd7e18b/pkgs#package-updates
Reviewed points
- package name fits guidelines
- package version fits guidelines
- package builds on x86-64
- executables tested on ARCHITECTURE
- all depending packages build
- patches have a comment describing either the upstream URL or a reason why the patch wasn't upstreamed
- patches that are remotely available are fetched rather than vendored
Comments
After cherry-picking the commit onto the current nixos-unstable, I prepared a network boot image with NixOS (with the new vbox guest additions, and X11/Plasma5) and booted the image inside the new virtualbox host version on a NixOS. Works all nice for me!
|
This PR should be merged together with #352640 |
|
Successfully created backport PR for |
Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a 👍 reaction to pull requests you find important.