On Monday 23 May 2016 17:17:19 Jörg-Volker Peetz wrote: > Gene Heskett wrote on 05/23/16 05:53: > <snip> > > > gene@coyote:/var/cache/apt/archives$ sudo > > dpkg -i --force-remove-reinstreq libexpat1_2.1.0-1+deb7u3_i386.deb > > libexpat1-dev_2.1.0-1+deb7u3_i386.deb > > <snip> > > > dpkg: error processing libexpat1:i386 (--install): > > package libexpat1:i386 2.1.0-1+deb7u3 cannot be configured because > > libexpat1:amd64 is at a different version (2.1.0-1+deb7u2) > > <snip> > > This is the relevant error message, I think. Either, update the amd64 > version too or purge it like so: > > dpkg --purge 'libexpat1:amd64' > > Anything depending on it (should only be amd64 packages) must also be > purged. > > Regards, > > jvp.
After an hour long search of the whole email corpus here (about 22 Gb) I did find the previous procedure, but had to add the --force-all option to get this: ============================== root@coyote:/etc/dpkg# dpkg --purge --force-all libexpat1:amd64 dpkg: libexpat1:amd64: dependency problems, but removing anyway as you requested: libfontconfig1:amd64 depends on libexpat1 (>= 2.0.1). (Reading database ... 421566 files and directories currently installed.) Removing libexpat1:amd64 ... Purging configuration files for libexpat1:amd64 ... root@coyote:/etc/dpkg# dpkg --configure -a Setting up libexpat1:i386 (2.1.0-1+deb7u3) ... Setting up libexpat1-dev (2.1.0-1+deb7u3) ... ======================== And now a normal run of synaptic is happy as a clam. The only thing I had to restart was tde's kmail. Its possible a refresh of the libs by running as root, an "ldconfig" might have fixed it too, but I didn't think of it at the time. So once again, the solution for a severe case of stupidity on my part, is part of the lists archives. :) Thank you. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
