I understand this is a backport from questing, and the diff confirms
that only d/changelog changed, but since this update is introducing
dependency changes, I think it needs some specific and careful testing.
Specifically, how can we test this change? What are the risks?
--- a/debian/control
+++ b/debian/control
@@ -12,9 +12,10 @@ Rules-Requires-Root: no
Package: docker-compose-v2
Architecture: any
-Depends: docker.io,
- ${misc:Depends},
+Depends: ${misc:Depends},
${shlibs:Depends}
+Recommends: docker.io
+Provides: docker-compose
** Changed in: docker-compose-v2 (Ubuntu Plucky)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2079929
Title:
docker-compose-v2 should depend on "docker.io | podman"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker-compose-v2/+bug/2079929/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
