Hi. Em Mon, 06 Jul 2009 12:52:35 +0000 Joachim Breitner <nome...@debian.org> escreveu: (...) > Am Montag, den 06.07.2009, 09:38 -0300 schrieb Marco Túlio Gontijo e > Silva: > > I built network from hackage and installed with --user > > --prefix=$HOME/.cabal. Then, I tried to remove libghc6-parsec3-dev, > > which is a dependency of my home built network. So I got this > > message: > > > > ghc-pkg: unregistering parsec-3.0.0 would break the following > > packages: network-2.2.1.3 (use --force to override) > > > > but the package was removed nicely. So I tried to build network > > again, and I got: > > > > Preprocessing library network-2.2.1.3... > > Building network-2.2.1.3... > > > > Network/URI.hs:108:7: > > Could not find module `Text.ParserCombinators.Parsec': > > There are files missing in the `parsec-3.0.0' package, > > try running 'ghc-pkg check'. > > Use -v to see a list of the files searched for. > > > > I think this is a bug in our prerm script. But I'm not sure what's > > the best way to fix it. If we use --force, the user installed > > package will become inconsistent. The other option is to exit with > > error in the prerm script in such cases, but I'm not sure is a good > > option either. > > > > What do you think? > > Why does the ghc-pkg call from postinst look at ~/.cabal at all? Does > the same happen when removing the package as a different user (e.g. su > instead of sudo)?
No. > We probably should pass "--global" to ghc-pkg, so that it does not > look at the user’s package registry at all. I'll try to reproduce it with --global in the prerm script. If it works, I'll prepare a haskell-devscripts package with this fix. Greetings. -- marcot http://marcot.iaaeee.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
