dpkg isn't actually confused, it knows exactly what it's doing. When
you build a package locally without using pkgbinarymangler, you wind up
with full package changelogs, various documentation being file copies
instead of symlinks, etc. When launchpad builds, it obviously applies
all these changes to the package as part of the build.
So the contents of the packages are different between the two archs, and
dpkg has no basis for deciding which contents are the "right" ones in a
multiarch context. It does the only thing it can do, it refuses to
install the new package whose contents differ from the existing ones.
** Changed in: dpkg (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/827950
Title:
Multiarch: dpkg gets confused when installing new packages with the
same version
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/827950/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
