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

libvirt: 10.10.0 -> 11.0.0 #375888

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

r-ryantm
Copy link
Contributor

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

meta.description for libvirt is: Toolkit to interact with the virtualization capabilities of recent versions of Linux and other OSes

meta.homepage for libvirt is: https://libvirt.org/

meta.changelog for libvirt is: https://gitlab.com/libvirt/libvirt/-/raw/v11.0.0/NEWS.rst

Updates performed
  • Ran passthru.UpdateScript
To inspect upstream changes
Impact

Checks done


  • built on NixOS
  • The tests defined in passthru.tests, if any, passed
  • found 11.0.0 with grep in /nix/store/q33bp7mkkpmzmds8q9kdiyi9hbxvp3hg-libvirt-11.0.0
  • found 11.0.0 in filename of file in /nix/store/q33bp7mkkpmzmds8q9kdiyi9hbxvp3hg-libvirt-11.0.0

Rebuild report (if merged into master) (click to expand)
36 total rebuild path(s)

36 package rebuild(s)

First fifty rebuilds by attrpath

appvm
collectd
diffoscope
docker-machine-kvm2
fdroidserver
garble
gnome-boxes
htcondor
libguestfs
librenms
libvirt
libvirt-glib
libvmi
mgmt
minikube
multipass
perl538Packages.SysVirt
perl540Packages.SysVirt
prometheus-libvirt-exporter
python312Packages.guestfs
python312Packages.libvirt
python313Packages.guestfs
python313Packages.libvirt
rubyPackages.ruby-libvirt
rubyPackages_3_1.ruby-libvirt
rubyPackages_3_2.ruby-libvirt
rubyPackages_3_3.ruby-libvirt
rubyPackages_3_4.ruby-libvirt
vagrant
virt-manager
virt-manager-qt
virt-top
virt-v2v
virt-viewer
virtnbdbackup
Instructions to test this update (click to expand)

Either download from the cache:

nix-store -r /nix/store/q33bp7mkkpmzmds8q9kdiyi9hbxvp3hg-libvirt-11.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.

Or, build yourself:

nix-build -A libvirt https://github.com/r-ryantm/nixpkgs/archive/55402a8db5e222b356c9b9a592f270ddf8d34ba3.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/55402a8db5e222b356c9b9a592f270ddf8d34ba3#libvirt

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/q33bp7mkkpmzmds8q9kdiyi9hbxvp3hg-libvirt-11.0.0
ls -la /nix/store/q33bp7mkkpmzmds8q9kdiyi9hbxvp3hg-libvirt-11.0.0/bin


Pre-merge build results

We have automatically built all packages that will get rebuilt due to
this change.

This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review


x86_64-linux

❌ 3 packages failed to build:
  • htcondor
  • python313Packages.guestfs
  • python313Packages.guestfs.dist
✅ 50 packages built:
  • appvm
  • collectd
  • diffoscope
  • diffoscope.dist
  • diffoscope.man
  • docker-machine-kvm2
  • fdroidserver
  • fdroidserver.dist
  • garble
  • gnome-boxes
  • guestfs-tools
  • libguestfs
  • libguestfs-with-appliance
  • libguestfs-with-appliance.guestfsd
  • libguestfs.guestfsd
  • librenms
  • libvirt
  • libvirt-glib
  • libvirt-glib.dev
  • libvirt-glib.devdoc
  • libvmi
  • libvmi.dev
  • libvmi.lib
  • mgmt
  • minikube
  • multipass
  • ocamlPackages.ocaml_libvirt
  • perl538Packages.SysVirt
  • perl538Packages.SysVirt.devdoc
  • perl540Packages.SysVirt
  • perl540Packages.SysVirt.devdoc
  • prometheus-libvirt-exporter
  • python312Packages.guestfs
  • python312Packages.guestfs.dist
  • python312Packages.libvirt
  • python312Packages.libvirt.dist
  • python313Packages.libvirt
  • python313Packages.libvirt.dist
  • rubyPackages.ruby-libvirt
  • rubyPackages_3_1.ruby-libvirt
  • rubyPackages_3_2.ruby-libvirt
  • rubyPackages_3_4.ruby-libvirt
  • vagrant
  • virt-manager
  • virt-manager-qt
  • virt-top
  • virt-v2v
  • virt-viewer
  • virtnbdbackup
  • virtnbdbackup.dist

Maintainer pings

cc @fpletz @globin @lovesegfault for testing.

Tip

As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.


Add a 👍 reaction to pull requests you find important.

@dtomvan
Copy link

dtomvan commented Feb 15, 2025

Can confirm that nix build github:r-ryantm/nixpkgs/55402a8db5e222b356c9b9a592f270ddf8d34ba3#nixosTests.libvirtd -o libvirt-v11-test exits with a zero exit code, but there's nothing in the output directory (I am new to these test so IDK if that is a success or not). Store path is /nix/store/7xzlyahg5dqg9msp8kc18yn2py2brly5-vm-test-run-libvirtd.

When swapping out my nixpkgs in flake.nix with github:r-ryantm/nixpkgs/55402a8db5e222b356c9b9a592f270ddf8d34ba3 and rebuilding my system configuration, creating and running a VM via virt-manager still works as intended.
Screenshot_20250215_155622

@dtomvan
Copy link

dtomvan commented Feb 15, 2025

Also, github:nixos/nixpkgs/nixos-24.11#python313Packages.guestfs never built in the first place. So I guess let's open an issue for that? Possibly related #167865 to that problem... The rest LGTM

@SuperSandro2000 SuperSandro2000 force-pushed the auto-update/libvirt branch 2 times, most recently from 8d88cc8 to e465bca Compare March 1, 2025 03:26
@wegank wegank added the 12.approvals: 1 This PR was reviewed and approved by one reputable person label Mar 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants