retitle 348807 Make postinst script more robust in case package has been removed thanks
Jose. Thanks for the details. For now, I'd advise that you not use unregister. There's no reason to unregister Cabal since there's a cabal package. I'll look into making the script more robust so it doesn't fail if the package is already unregistered. Do you need help getting your system out of a bad state? peace, isaac José Salavert Torres <[EMAIL PROTECTED]> writes: >> The configure script should definitely not remove cabal 1.0, but >> ghc-pkg should probably hide previous versions. With ghc 6.4.1, I >> believe this is the case. > > yes. > > but if you uninstall with ghc-pkg > > # ghc-pkg unregister Cabal > > then you can't run: > > # apt-get remove libghc6-cabal-dev > > Because the cript returns error, due to that cabal 1.1.3 is not there > and you can't reinstall the package again with: > > # apt-get install libghc6-cabal-dev > > because you can uninstall it with apt. > > so ghc-pkg uninstall makes dpkg script to not uninstall properly the > package.
