I'm not the original reporter but I just ran into the same problem:
I'm not sure I entirely follow what's going on when this happens. We're in the postinst which means files from older amd64-libs packages have been removed. If removing the diversion would cause a conflict, then you must have both ldd and ldd.i386; ldd.i386 is presumably the standard version from libc6, after diversion; what's providing /usr/bin/ldd?
On our sarge upgrades it's owned by libc6: [EMAIL PROTECTED]:~ $ dpkg -S /usr/bin/ldd diversion by amd64-libs from: /usr/bin/ldd diversion by amd64-libs to: /usr/bin/ldd.i386 libc6: /usr/bin/ldd [EMAIL PROTECTED]:~ $ dpkg -l libc6 Desired=Unknown/Install/Remove/Purge/Hold| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half- installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description+++-===========================-===========================- ====================================================================== ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries
smime.p7s
Description: S/MIME cryptographic signature
