No ghc-pkg unregister call on upgrade?
When I upgrade to a newer version of a package, the old package is not getting unregistered by ghc-pkg. I believe this is because ghc-pkg update does not actually unregister the old package, and the ghc-pkg unregister call in the prerm script is not called during an upgrade, only during a remove. But I could be mistaken on these details. My question is, does anyone else see the "ghosts" of packages that have been upgraded in the output of ghc-pkg list? Does ghc-pkg check say you have broken packages? This will only happen if you have upgraded a package to a newer version on your system. I believe network has been upgraded, along with parallel, cpphs, magic, and time.
-david
Reply to: