On Fri, Oct 21, 2016 at 11:42:03AM +0200, Andreas Beckmann wrote: > This is a serious bug as it makes installation fail, and violates > sections 7.6.1 and 10.1 of the policy. An optimal solution would > consist in only one of the packages installing that file, and renaming > or removing the file in the other package. Depending on the > circumstances you might also consider Replace relations or file > diversions. If the conflicting situation cannot be resolved then, as a > last resort, the two packages have to declare a mutual > Conflict. Please take into account that Replaces, Conflicts and > diversions should only be used when packages provide different > implementations for the same functionality.
I has checked the code, and these two packages provide very different implementation of bitbucket API. So I think the solution is mutual Conflict. Another solution is removing python-bitbucket-api since I only need python3-bitbucket-api for git-repo (#840371), and it is Python3 only. Not sure if that is a good solution, but it can solve the problem too. -- ChangZhuo Chen (陳昌倬) <czc...@debian.org> Debian Developer (https://nm.debian.org/public/person/czchen) Key fingerprint = EC9F 905D 866D BE46 A896 C827 BE0C 9242 03F4 552D BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B
signature.asc
Description: PGP signature
