Hi Kevin,
Thanks for reporting this bug and helping making Ubuntu better.
As Guilherme mentioned, mixing the upstream provided packages and the
distribution provided packages is not a supported use case. You should
use either one or the other provider, but not both.
The Debian policy mentioned should be restricted to distribution
provided packages, which, as mentioned by Guilherme, are under the
dustribution's control.
Moreover, one could also argue that since these packages are being
distributed specifically for Ubuntu as implied by the URL, the provider
should work around such conflicts on their end (i.e., they are aware of
the distribution, but the distribution cannot control what they ship or
how they will change what is being shipped in the future).
** Changed in: docker-compose-v2 (Ubuntu)
Status: New => Opinion
** Changed in: docker-compose-v2 (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2151249
Title:
docker-compose-v2 conflicts with docker-compose-plugin: both ship
/usr/libexec/docker/cli-plugins/docker-compose without Conflicts:
marker
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker-compose-v2/+bug/2151249/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
