problem upgrading kdelibs3-crypto (2.2.2-2)
I've just tried to do an update of my sid install and the upgrade
process chokes on kdelibs3-crypto, the error message is
(appologies for the long and mangled wrapping)
Preparing to replace kdelibs3-crypto 4:2.2.2-1
(using.../kdelibs3-crypto_4%3a2.2.2-2_i386.deb) ...
Adding `diversion of /usr/lib/kde2/kio_https.la to
/usr/lib/kde2/kio_https-nossl.la by kdelibs3-crypto'
Adding `diversion of /usr/lib/kde2/kio_https.so to
/usr/lib/kde2/kio_https-nossl.so by kdelibs3-crypto'
Leaving `diversion of /usr/lib/libkssl.so.2.0.2 to
/usr/lib/libkssl-nossl.so.2.0.2 by kdelibs3-crypto'
Leaving `diversion of /usr/lib/libkssl.la to
/usr/lib/libkssl-nossl.la by kdelibs3-crypto'
Unpacking replacement kdelibs3-crypto ...
dpkg: error processing
/var/cache/apt/archives/kdelibs3-crypto_4%3a2.2.2-2_i386.deb
(--unpack):
trying to overwrite `/usr/share/apps/kssl/caroot/ca-bundle.crt',
which is also in package kdelibs3
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Removing `diversion of /usr/lib/kde2/kio_https.la to
/usr/lib/kde2/kio_https-nossl.la by kdelibs3-crypto'
Removing `diversion of /usr/lib/kde2/kio_https.so to
/usr/lib/kde2/kio_https-nossl.so by kdelibs3-crypto'
Removing `diversion of /usr/lib/libkssl.so.2.0.2 to
/usr/lib/libkssl-nossl.so.2.0.2 by kdelibs3-crypto'
dpkg-divert: rename involves overwriting `/usr/lib/libkssl.so.2.0.2'
with different file `/usr/lib/libkssl-nossl.so.2.0.2', not allowed
After this dpkg exits (leaving 95 packages not upgraded), to try and
fix this I tried to remove kdelibs3-crypto and when that didn't work
tried to purge kdelibs3-crypto and neither worked:
dpkg: error processing kdelibs3-crypto (--purge):
Package is in a very bad inconsistent state - you should
reinstall it before attempting a removal.
I have tried reinstalling the package using apt and dpkg but it gives
the same messages as the upgrade gives.
Does anyone have any ideas here? I'm going to have another fiddle
with it but I'm tired and probably missing the obvious =)
-Paul Chamberlain
Reply to: