Kodi在Ubuntu 16.04上的安装失败

Question

当我试图安装Kodi时，我得到：

root@xKaganovich:/home/kaganovich# apt-get install kodi
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  fonts-roboto fonts-roboto-hinted kodi-data libcec-platform1v5 libcec3
  libfstrcmp0 libhdhomerun2 libjs-iscroll libsdl2-2.0-0 libsndio6.1
Use 'sudo apt autoremove' to remove them.
Suggested packages:
  kodi-pvr-mythtv kodi-pvr-vuplus kodi-pvr-vdr-vnsi kodi-pvr-njoy
  kodi-pvr-nextpvr kodi-pvr-mediaportal-tvserver kodi-pvr-tvheadend-hts
  kodi-pvr-dvbviewer kodi-pvr-argustv kodi-pvr-iptvsimple
  kodi-audioencoder-vorbis kodi-audioencoder-flac kodi-audioencoder-lame
The following NEW packages will be installed:
  kodi
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/20.0 MB of archives.
After this operation, 37.1 MB of additional disk space will be used.
(Reading database ... 264739 files and directories currently installed.)
Preparing to unpack .../kodi_2%3a17.6+git20171114.2125-final-0xenial_all.deb ...
Unpacking kodi (2:17.6+git20171114.2125-final-0xenial) ...
dpkg: error processing archive /var/cache/apt/archives/kodi_2%3a17.6+git20171114.2125-final-0xenial_all.deb (--unpack):
 trying to overwrite '/usr/share/kodi/media/icon32x32.png', which is also in package kodi-data 15.2+dfsg1-3ubuntu1.1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for menu (2.1.47ubuntu1.16.04.1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/kodi_2%3a17.6+git20171114.2125-final-0xenial_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

我怎样才能解决这个问题？

Answer 1

你有文件冲突。两个包试图提供相同的文件，这在基于Debian的系统中是不允许的。

包kodi 2:17.6+git20171114.2125-final-0xenial和kodi-data 15.2+dfsg1-3ubuntu1.1冲突。它们不能同时安装。当包来自不同的来源时，通常会发生这种情况。

解决这个问题有两种方法。

1)选择要保留的包，从拒绝的源卸载所有软件包，并删除拒绝的源。将包与拒绝的源保持在一起可能会导致版本冲突或更多的文件冲突。

2)使用apt的--force标志同意覆盖文件。这解决了今天的问题，但这个问题可能会在每次升级包时再次出现。

防止此问题的简单方法是限制非Ubuntu源，在尝试失败后删除实验源，并偶尔使用apt autoremove清除系统中的孤立包。