package libllvm4.0:amd64 1:4.0-1ubuntu1~16.04.2 [modified: usr/share/doc/libllvm4.0/changelog.Debian.gz usr/share/doc/libllvm4.0/copyright] failed to install/upgrade: package libllvm4.0:amd64 1:4.0-1ubuntu1~16.04.2 cannot be configured because libllvm4.0:i386 is at a different version (1:4.0.1-10)

[Patrick Costello]

Found during upgrade from 14.04 to 18.04.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libllvm4.0:amd64 1:4.0-1ubuntu1~16.04.2 [modified: usr/share/doc/libllvm4.0/changelog.Debian.gz usr/share/doc/libllvm4.0/copyright]
ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
Uname: Linux 4.4.0-141-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Tue Jan 8 17:39:34 2019
ErrorMessage: package libllvm4.0:amd64 1:4.0-1ubuntu1~16.04.2 cannot be configured because libllvm4.0:i386 is at a different version (1:4.0.1-10)
InstallationDate: Installed on 2014-07-17 (1636 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt 1.6.6
SourcePackage: llvm-toolchain-4.0
Title: package libllvm4.0:amd64 1:4.0-1ubuntu1~16.04.2 [modified: usr/share/doc/libllvm4.0/changelog.Debian.gz usr/share/doc/libllvm4.0/copyright] failed to install/upgrade: package libllvm4.0:amd64 1:4.0-1ubuntu1~16.04.2 cannot be configured because libllvm4.0:i386 is at a different version (1:4.0.1-10)
UpgradeStatus: Upgraded to bionic on 2019-01-08 (0 days ago)

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance!

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]