By the way, another aspect of this bug has surfaced when I tried to remove the package:
$ sudo dpkg --purge --force-all libghc6-missingpy-dev (Reading database ... 215333 files and directories currently installed.) Removing libghc6-missingpy-dev ... ghc-pkg: cannot find package MissingPy dpkg: error processing libghc6-missingpy-dev (--purge): subprocess pre-removal script returned error exit status 1 Errors were encountered while processing: libghc6-missingpy-dev Because installation failed and left the package half-configured, the .prerm runs and fails this way. This happens for removing, purging, or (judging by the code) upgrading, so every path forward is blocked. Looks like I will need to do a bit of surgery. Will it be safe to comment out the ghc-pkg line in .prerm, and try again? I expect that, on my try at installation, ghc-pkg did not end up doing anything that needs to be undone, but I would like your confirmation first. Or do you have a pointer to a document for ghc-pkg? (Another bug: no man page for ghc-pkg. I'll file one for it.) Regards, Roger Hale -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
