commit 2dc1009c749af45bd300309765d6281ae1d7cb09
Merge: 721d6e0 34a202e
Author: Moritz Muehlenhoff <jmm@debian.org>
Date: Tue Jun 23 18:16:03 2026 +0000
Merge branch 'qemu-v10.2' into 'master'
Fix compatiblity with QEMU >= 10.2
See merge request ganeti-team/ganeti!7
commit 721d6e0581b4975c794315ae3289ec4b186efa90
Merge: 923f14a 0ce95f7
Author: Moritz Muehlenhoff <jmm@debian.org>
Date: Tue Jun 23 17:57:47 2026 +0000
Merge branch 'systemd' into 'master'
Improve systemd support
See merge request ganeti-team/ganeti!8
commit 0ce95f7dbb142554ed0e56979da10ae252739ab1
Author: Aurelien Jarno <aurelien@aurel32.net>
Date: Sun Mar 29 15:44:02 2026 +0200
Do not assume sysvinit in the postinst script
The postinst script currently check for the availability of
/etc/init.d/ganeti before stopping the service with invoke-rc.d. This
will break when the sysvinit script get remove.
Just remove the check as the return status of invoke-rc.d is ignored and
as it does not output any error message if the service does not exists.
commit 5c10241354135317a75aab3357a73e68c83d5193
Author: Aurelien Jarno <aurelien@aurel32.net>
Date: Sun Mar 29 15:43:45 2026 +0200
Fix autopkgtest failure with systemd
Since systemd services got shipped in version 3.1.0~rc2-5, autopkgtest
fails. The vcluster-qa test expects a minimal init system to start
multiple ganeti daemons (one per virtual node), but systemd prevents
that.
To work around the issue, mask the ganeti.target service so that
daemon-util does not attempt to use systemd to start ganeti services
during tests.
commit 34a202e43a08eb8b0c7c0661637c27a298a9e73f
Author: Aurelien Jarno <aurelien@aurel32.net>
Date: Sat Mar 28 16:22:49 2026 +0100
Fix compatiblity with QEMU >= 10.2
Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.
Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.
Among the 7 debian patches available in version 3.1.0~rc2-5 of the package, we noticed the following issues: