Comment 2 for bug 2008830

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Well, when looking at it in detail it isn't that trivial.

On one hand I'll rebase to 9.0.0-2 as [2] is the other thing I want and the stabilization is good as well.

But we already have the suggested change [1] since it was part of the merge of 9.0.0-2.
To get rid of the policykit-1 dependency we will need more.
You'll see that [3] has no direct dependency to policykit-1.
Instead it has:
  Package: libvirt-daemon-system
  ...
  polkitd (>= 121+compat0.1-2) [linux-any],

This is what causes the locked migration right now, as only the on in proposed is providing that:

 polkitd | 0.105-33 | lunar | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
 polkitd | 122-3 | lunar-proposed | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x

The latter is the version that is stuck due to the duktape MIR processsing in bug 1997417 for now.

Just as we assumed when landing this in Debian (the later assumption was that the new polkit will make it in time eventually, but per your request we give up on that for now) we have to revert [4].

[1]: https://salsa.debian.org/libvirt-team/libvirt/-/commit/b9b2923
[2]: https://salsa.debian.org/libvirt-team/libvirt/-/merge_requests/177
[3]: https://launchpadlibrarian.net/650583774/buildlog_ubuntu-lunar-amd64.libvirt_9.0.0-1ubuntu1_BUILDING.txt.gz
[4]: https://salsa.debian.org/libvirt-team/libvirt/-/commit/c62b8b2