[Pkg-libvirt-commits] [Git][libvirt-team/libvirt][debian/latest] 3 commits: daemon-system: Only build on ARCHES_QEMU

[Andrea Bolognani (@abologna)]

Andrea Bolognani pushed to branch debian/latest at Libvirt Packaging Team / libvirt


Commits:
c192aea6 by Andrea Bolognani at 2025-04-21T22:49:25+02:00
daemon-system: Only build on ARCHES_QEMU

The package directly depends on daemon-driver-qemu, so it
would be uninstallable on any other architecture anyway.
Making it not exist at all instead makes for a better user
experience.

- - - - -
60fe506f by Andrea Bolognani at 2025-04-21T23:00:27+02:00
news: Update with more information about daemon-system

Expand the entry for 10.6.0-2 to explain how the daemon-system
package is no longer available on architectures where QEMU
itself isn't, and how that doesn't affect the ability to run
libvirtd as a system daemon since all necessary files are now
shipped as part of the daemon package.

Gbp-Pq: Ignore

- - - - -
1e4d998b by Andrea Bolognani at 2025-04-21T23:03:35+02:00
lintian: Update overrides for daemon-system

It's an empty package, so of course it contains no
architecture-dependent files; and yet we can't make it
arch:all, since we only want it to be available on ARCHES_QEMU.

Gbp-Dch: Ignore

- - - - -


4 changed files:

- debian/NEWS
- debian/control
- debian/control.in
- debian/libvirt-daemon-system.lintian-overrides


Changes:

=====================================
debian/NEWS
=====================================
@@ -63,10 +63,15 @@ libvirt (10.6.0-2) experimental; urgency=medium
 
   The system-wide configuration for the libvirtd daemon is no longer
   shipped separately from the daemon itself, as was the case until
-  now. The libvirt-daemon-system package still exists, but it's now
+  today; the libvirt-daemon package now contains everything
+  necessary to run libvirtd as a system daemon.
+
+  The libvirt-daemon-system package still exists, but it's now
   simply a convenient way to install the "typical" libvirt
   deployment consisting of all the components needed to run a
-  QEMU-based hypervisor.
+  QEMU-based hypervisor, and it is completely safe to uninstall it
+  if you would rather have a more tailored deployment or if QEMU
+  is not available on your architecture.
 
  -- Andrea Bolognani <eof at kiyuko.org>  Sat, 24 Aug 2024 11:01:43 +0200
 


=====================================
debian/control
=====================================
@@ -814,7 +814,7 @@ Homepage: https://libvirt.org/kbase/locking-sanlock.html
 
 Package: libvirt-daemon-system
 Section: admin
-Architecture: linux-any
+Architecture: amd64 arm64 armel armhf i386 loong64 mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x sparc64 x32
 Depends:
  libvirt-clients (= ${binary:Version}),
  libvirt-common (= ${binary:Version}),


=====================================
debian/control.in
=====================================
@@ -706,7 +706,7 @@ Homepage: https://libvirt.org/kbase/locking-sanlock.html
 
 Package: libvirt-daemon-system
 Section: admin
-Architecture: linux-any
+Architecture: ${ARCHES_QEMU}
 Depends:
  libvirt-clients (= ${binary:Version}),
  libvirt-common (= ${binary:Version}),


=====================================
debian/libvirt-daemon-system.lintian-overrides
=====================================
@@ -1 +1,2 @@
 libvirt-daemon-system: empty-binary-package
+libvirt-daemon-system: package-contains-no-arch-dependent-files



View it on GitLab: https://salsa.debian.org/libvirt-team/libvirt/-/compare/07012beeeb8603cc4039de5105b530545f56fe2c...1e4d998b30ae58d9208033e23dc95270b885c5c5

-- 
View it on GitLab: https://salsa.debian.org/libvirt-team/libvirt/-/compare/07012beeeb8603cc4039de5105b530545f56fe2c...1e4d998b30ae58d9208033e23dc95270b885c5c5
You're receiving this email because of your account on salsa.debian.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-libvirt-commits/attachments/20250422/4e8834e2/attachment-0001.htm>