d/control: do not track qemu-server and pve-container dependency

While it would be correct to have them tracked here we cannot do this
at the moment, as with those two also depend on pve-ha-manager, and
with dpkg packaged under strech there's an issue with such cyclic
dependencies and trigger cycle detection only resolved for buster[0]

Currently, the issue exists on the following condition:

* update of pve-ha-manager plus either pve-container or qemu-server
* but _no_ update of pve-manager in the same upgrade cycle

[0]: https://salsa.debian.org/dpkg-team/dpkg/commit/7f43bf5f93c857bdb419892abfc014a5e9c3c273

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

diff --git a/debian/control b/debian/control
index 4102f43f4d49d522201b8af9c14d0f6390457356..0cca295a7ed7c49a8115757e9eb8b6cd9775816b 100644 (file)
--- a/debian/control
+++ b/debian/control
@@ -21,8 +21,10 @@ Architecture: any
 Depends: libjson-perl,
          libpve-common-perl,
          pve-cluster (>= 3.0-17),
-         pve-container,
-         qemu-server,
+# TODO: for PVE 6 re-add thos two, we just removed them to avoid a dpkg issue
+# with cyclic depdnencies and wrong trigger cycle detections
+#        pve-container,
+#        qemu-server,
          systemd,
          ${misc:Depends},
          ${perl:Depends},