package libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: package libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured because libheimbase1-heimdal:i386 is at a different version (1.7~git20150920+dfsg-4ubuntu1)

[Nicholas Riegel]

On startup

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1
Uname: Linux 4.8.1-040801-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
AptOrdering:
 libheimbase1-heimdal:amd64: Install
 NULL: ConfigurePending
 NULL: RemovePending
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Oct 14 02:53:05 2016
Dependencies:
 gcc-6-base 6.2.0-5ubuntu12
 libc6 2.24-3ubuntu1
 libgcc1 1:6.2.0-5ubuntu12
DuplicateSignature:
 package:libheimbase1-heimdal:amd64:1.7~git20160703+dfsg-1
 Processing triggers for libc-bin (2.24-3ubuntu1) ...
 dpkg: error processing package libheimbase1-heimdal:amd64 (--configure):
  package libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured because libheimbase1-heimdal:i386 is at a different version (1.7~git20150920+dfsg-4ubuntu1)
ErrorMessage: package libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured because libheimbase1-heimdal:i386 is at a different version (1.7~git20150920+dfsg-4ubuntu1)
InstallationDate: Installed on 2016-02-27 (230 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160226)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt 1.3.1
SourcePackage: heimdal
Title: package libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: package libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured because libheimbase1-heimdal:i386 is at a different version (1.7~git20150920+dfsg-4ubuntu1)
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Joshua Powers (powersj)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

It looks as if you are using packages from proposed and have run into a situation where packages are not in sync. Packages in yakkety-proposed that are not in yakkety are *known to be broken* - otherwise they would migrate to the release pocket within a few hours. We appreciate you helping out in testing, but I suggest that you test by using yakkety only - using the proposed pocket provides no real benefit to developers.

I am marking this a duplicate of another heimdal bug where the user was using proposed as well. If you disagree please feel free to comment adding details as to why you believe this is not the case.

Thanks again