Hi Petter, > Yeah, the problem is related to how libdevmapper1.02 was replaced > with a package with a different version number. The short term > solution is to purge the currently no longer installed > libdevmapper1.02 package.
After brief confusion (searching for libdevmapper got me the libdevmapper1.02.1 package and I didn't initially realise that wasn't the one I was looking for; removing it would have been problematic - I'll hazard a guess it's the replacement package) I find that this package is indeed un-needed. Mildly surprised it wasn't dumped by aptitude's dependency tracking on account of that - aptitude knew it was only present because it was pulled in as a dependency. One dpkg-reconfigure sysv-rc later, <quote> success: Enabled dependency-based boot system </quote> :-) > Not sure how to fix the problem properly using the package system. Would a Provides: in the replacement, purporting to provide the old, and maybe a Conflicts: to give it a bit of a kick, help ? Otherwise, find which packages mention it as an alternative in their Requires: or similar headers, get them to all stop mentioning it. I take it it's obsolete anyway ... Thanks for your help, Eddy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org