package kodi-repository-kodi (not installed) failed to install/upgrade: trying to overwrite '/usr/share/kodi/addons/repository.xbmc.org/addon.xml', which is also in package kodi-data 2:17.3+dfsg1-3

[flamur]

kodi.service is a disabled or a static unit, not starting it.
Processing triggers for libc-bin (2.26-0ubuntu2) .

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: kodi-repository-kodi (not installed)
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Sun Nov 12 11:47:42 2017
DuplicateSignature:
 package:kodi-repository-kodi:(not installed)
 Unpacking kodi-repository-kodi (2:17.3+dfsg1-3) ...
 dpkg: error processing archive /tmp/apt-dpkg-install-5qDGFt/11-kodi-repository-kodi_2%3a17.3+dfsg1-3_all.deb (--unpack):
  trying to overwrite '/usr/share/kodi/addons/repository.xbmc.org/addon.xml', which is also in package kodi-data 2:17.3+dfsg1-3
ErrorMessage: trying to overwrite '/usr/share/kodi/addons/repository.xbmc.org/addon.xml', which is also in package kodi-data 2:17.3+dfsg1-3
InstallationDate: Installed on 2017-10-22 (20 days ago)
InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt 1.5
SourcePackage: kodi
Title: package kodi-repository-kodi (not installed) failed to install/upgrade: trying to overwrite '/usr/share/kodi/addons/repository.xbmc.org/addon.xml', which is also in package kodi-data 2:17.3+dfsg1-3
UpgradeStatus: No upgrade log present (probably fresh install)

[Hans Joachim Desserud (hjd)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1721914, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.