Packages all screwed up

Hello, I recently tried to upgrade some package (eg. yesod) and it seems that, in the process, I screwed up my Haskell packages setup. When I am trying to do a simple:
ghc --make Crete1941
It fails with message: Loader\Communication.hs:14:7: Could not find module `System.Process': Use -v to see a list of the files searched for. which is quite annoying ! Is there a way to reconstruct a sane baseline ? Thanks in advance Arnaud PS: In case it might be helpful, here is the output of ghc-pkg check -v There are problems in package pandoc-1.6: dependency "utf8-string-0.3.6-02c7018b15768d3d72b99557d0f847ff" doesn't exist There are problems in package zip-archive-0.1.1.6: dependency "binary-0.5.0.2-0da250ded3b79a6e76d15de8e7ffc885" doesn't exist dependency "utf8-string-0.3.6-02c7018b15768d3d72b99557d0f847ff" doesn't exist There are problems in package url-2.1.2: dependency "utf8-string-0.3.6-02c7018b15768d3d72b99557d0f847ff" doesn't exist There are problems in package filestore-0.3.4.3: dependency "utf8-string-0.3.6-02c7018b15768d3d72b99557d0f847ff" doesn't exist There are problems in package happstack-server-0.5.0.2: dependency "utf8-string-0.3.6-02c7018b15768d3d72b99557d0f847ff" doesn't exist There are problems in package happstack-data-0.5.0.2: dependency "binary-0.5.0.2-0da250ded3b79a6e76d15de8e7ffc885" doesn't exist There are problems in package feed-0.3.7: dependency "utf8-string-0.3.6-02c7018b15768d3d72b99557d0f847ff" doesn't exist There are problems in package SHA-1.4.1.3: dependency "binary-0.5.0.2-0da250ded3b79a6e76d15de8e7ffc885" doesn't exist There are problems in package hashed-storage-0.5.3: dependency "binary-0.5.0.2-0da250ded3b79a6e76d15de8e7ffc885" doesn't exist There are problems in package yesod-0.6.0.2: dependency "cereal-0.3.0.0-835aef1b61feb29c879c2cdae5c16608" doesn't exist dependency "clientsession-0.4.0.3-83420d6960f048ed87e049bcfa4d3d35" doesn't exist dependency "neither-0.1.0-50e3e802c117062181b91d4cbd45270b" doesn't exist dependency "wai-0.2.2-11adeb24d79e447264a1c6aa73a257e8" doesn't exist There are problems in package xss-sanitize-0.2.2: dependency "utf8-string-0.3.6-02c7018b15768d3d72b99557d0f847ff" doesn't exist There are problems in package web-routes-0.23.0: dependency "utf8-string-0.3.6-02c7018b15768d3d72b99557d0f847ff" doesn't exist There are problems in package wai-extra-0.2.4: dependency "utf8-string-0.3.6-02c7018b15768d3d72b99557d0f847ff" doesn't exist dependency "wai-0.2.2-11adeb24d79e447264a1c6aa73a257e8" doesn't exist dependency "zlib-bindings-0.0.0-c2a6f489bd57d072e884afc1d6466b99" doesn't exist There are problems in package snap-server-0.2.11: dependency "cereal-0.3.0.0-835aef1b61feb29c879c2cdae5c16608" doesn't exist dependency "monads-fd-0.1.0.2-8e71857db7c17ae96ca5bff72f20d9fa" doesn't exist There are problems in package snap-core-0.2.11: dependency "cereal-0.3.0.0-835aef1b61feb29c879c2cdae5c16608" doesn't exist dependency "monads-fd-0.1.0.2-8e71857db7c17ae96ca5bff72f20d9fa" doesn't exist There are problems in package pureMD5-2.1.0.2: dependency "binary-0.5.0.2-0da250ded3b79a6e76d15de8e7ffc885" doesn't exist dependency "cereal-0.3.0.0-835aef1b61feb29c879c2cdae5c16608" doesn't exist There are problems in package persistent-0.3.0.1: dependency "neither-0.1.0-50e3e802c117062181b91d4cbd45270b" doesn't exist There are problems in package hsx-0.7.0: dependency "utf8-string-0.3.6-02c7018b15768d3d72b99557d0f847ff" doesn't exist There are problems in package HStringTemplate-0.6.5: dependency "utf8-string-0.3.6-02c7018b15768d3d72b99557d0f847ff" doesn't exist There are problems in package HSlim-0.1: dependency "utf8-string-0.3.6-02c7018b15768d3d72b99557d0f847ff" doesn't exist There are problems in package hint-0.3.3.0: dependency "utf8-string-0.3.6-02c7018b15768d3d72b99557d0f847ff" doesn't exist There are problems in package haskeline-0.6.3.1: dependency "utf8-string-0.3.6-02c7018b15768d3d72b99557d0f847ff" doesn't exist There are problems in package happstack-state-0.5.0.2: dependency "binary-0.5.0.2-0da250ded3b79a6e76d15de8e7ffc885" doesn't exist dependency "happstack-data-0.5.0.2-80c87686add000961445ac7ad8f41385" doesn't exist dependency "happstack-util-0.5.0.2-781b128492ee5ce69eb3c01f6e6a02bb" doesn't exist There are problems in package happstack-ixset-0.5.0.2: dependency "happstack-data-0.5.0.2-80c87686add000961445ac7ad8f41385" doesn't exist dependency "happstack-util-0.5.0.2-781b128492ee5ce69eb3c01f6e6a02bb" doesn't exist There are problems in package happstack-0.5.0.2: dependency "happstack-data-0.5.0.2-80c87686add000961445ac7ad8f41385" doesn't exist dependency "happstack-server-0.5.0.2-9d48ec66664b8dd67d495020314c5d2b" doesn't exist dependency "happstack-util-0.5.0.2-781b128492ee5ce69eb3c01f6e6a02bb" doesn't exist dependency "utf8-string-0.3.6-02c7018b15768d3d72b99557d0f847ff" doesn't exist There are problems in package crypto-api-0.1.2.4: dependency "cereal-0.3.0.0-835aef1b61feb29c879c2cdae5c16608" doesn't exist There are problems in package bytestring-show-0.3.3: dependency "binary-0.5.0.2-0da250ded3b79a6e76d15de8e7ffc885" doesn't exist There are problems in package attoparsec-iteratee-0.1.1: dependency "monads-fd-0.1.0.2-8e71857db7c17ae96ca5bff72f20d9fa" doesn't exist There are problems in package regex-compat-0.93.1: dependency "regex-posix-0.94.2-0a3c1e41d8c2d26547372e229b3f776c" doesn't exist There are problems in package haskell-platform-2010.2.0.0: dependency "regex-posix-0.94.2-0a3c1e41d8c2d26547372e229b3f776c" doesn't exist The following packages are broken, either because they have a problem listed above, or because they depend on a broken package. pandoc-1.6 zip-archive-0.1.1.6 url-2.1.2 filestore-0.3.4.3 happstack-server-0.5.0.2 happstack-data-0.5.0.2 feed-0.3.7 SHA-1.4.1.3 hashed-storage-0.5.3 yesod-0.6.0.2 xss-sanitize-0.2.2 web-routes-0.23.0 wai-extra-0.2.4 snap-server-0.2.11 snap-core-0.2.11 pureMD5-2.1.0.2 persistent-0.3.0.1 hsx-0.7.0 HStringTemplate-0.6.5 HSlim-0.1 hint-0.3.3.0 haskeline-0.6.3.1 happstack-state-0.5.0.2 happstack-ixset-0.5.0.2 happstack-0.5.0.2 crypto-api-0.1.2.4 bytestring-show-0.3.3 attoparsec-iteratee-0.1.1 regex-compat-0.93.1 haskell-platform-2010.2.0.0 ConfigFile-1.0.6 MissingH-1.1.0.3 hsp-0.5.2 HJScript-0.5.0

On Monday 31 January 2011 23:59:57, Arnaud Bailly wrote:
Hello, I recently tried to upgrade some package (eg. yesod) and it seems that, in the process, I screwed up my Haskell packages setup.
Big time.
When I am trying to do a simple:
ghc --make Crete1941
It fails with message:
Loader\Communication.hs:14:7: Could not find module `System.Process': Use -v to see a list of the files searched for.
Scary. Does 'ghc-pkg list process' list - no package process at all - one package process in the global db - more than one process (one in the global db) - process in user db but not global ? The first would mean your GHC is really borked and you'd need to reinstall. The second and third would mean there's hope, four looks like a reinstall again. Unfortunately, the error message lets me fear the first.
which is quite annoying !
Is there a way to reconstruct a sane baseline ?
1. Check whether ghc itself is affected, rename (or move, or delete if you think it's not worth saving) the directory your user db is in (ghc-pkg list process should tell you where if you don't know), so ghc doesn't see it. ghc-pkg check. If nothing is reported as broken, try compiling a programme or two using only the core libs, if it works, you probably don't need to reinstall ghc, if not, you have to start from zero. 2. If ghc itself is okay, you can decide whether you want to start fresh, then delete the old directory and cabal install what you need/want. If you think trying to rescue what you have and is not broken is worth the effort, ghc-pkg unregister the broken packages and cabal install them again.

On Mon, Jan 31, 2011 at 4:59 PM, Arnaud Bailly
Hello, I recently tried to upgrade some package (eg. yesod) and it seems that, in the process, I screwed up my Haskell packages setup. When I am trying to do a simple:
ghc --make Crete1941
What command(s) did you issue to "upgrade some packages?" Were you trying to do a user or global install? When ghc loads packages, I've had cases where packages in the user db would shadow packages in the global db, causing *other* packages in the global db to report as "broken". Thanks, Antoine

Hi, Thanks for your answers. I did
cabal upgrade yesod
As for the user/global issue, I think I tried a user install, this is
default isn't it?
Looks like I will have to reinstall everything :-(
Arnaud
On Tue, Feb 1, 2011 at 1:34 AM, Antoine Latter
On Mon, Jan 31, 2011 at 4:59 PM, Arnaud Bailly
wrote: Hello, I recently tried to upgrade some package (eg. yesod) and it seems that, in the process, I screwed up my Haskell packages setup. When I am trying to do a simple:
ghc --make Crete1941
What command(s) did you issue to "upgrade some packages?" Were you trying to do a user or global install?
When ghc loads packages, I've had cases where packages in the user db would shadow packages in the global db, causing *other* packages in the global db to report as "broken".
Thanks, Antoine

This is the easiest way conceptually. You can also try to --reinstall every
package that 'ghc-pkg check' report is broken. If you pick up the right
version and compilation options will match there is a high chance you can
fix this state. I've done this before and it worked.
Best regards,
Krzysztof Skrzętnicki
On Tue, Feb 1, 2011 at 08:16, Arnaud Bailly
Hi, Thanks for your answers.
I did
cabal upgrade yesod
As for the user/global issue, I think I tried a user install, this is default isn't it?
Looks like I will have to reinstall everything :-(
Arnaud
On Tue, Feb 1, 2011 at 1:34 AM, Antoine Latter
wrote: On Mon, Jan 31, 2011 at 4:59 PM, Arnaud Bailly
wrote: Hello, I recently tried to upgrade some package (eg. yesod) and it seems that, in the process, I screwed up my Haskell packages setup. When I am trying to do a simple:
ghc --make Crete1941
What command(s) did you issue to "upgrade some packages?" Were you trying to do a user or global install?
When ghc loads packages, I've had cases where packages in the user db would shadow packages in the global db, causing *other* packages in the global db to report as "broken".
Thanks, Antoine
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

I started that way but quickly ran into issues about compilers
toolchain for certain packages: I am on windows and some core packages
require mingw toolchain.
2011/2/1 Krzysztof Skrzętnicki
This is the easiest way conceptually. You can also try to --reinstall every package that 'ghc-pkg check' report is broken. If you pick up the right version and compilation options will match there is a high chance you can fix this state. I've done this before and it worked. Best regards, Krzysztof Skrzętnicki
On Tue, Feb 1, 2011 at 08:16, Arnaud Bailly
wrote: Hi, Thanks for your answers.
I did
cabal upgrade yesod
As for the user/global issue, I think I tried a user install, this is default isn't it?
Looks like I will have to reinstall everything :-(
Arnaud
On Tue, Feb 1, 2011 at 1:34 AM, Antoine Latter
wrote: On Mon, Jan 31, 2011 at 4:59 PM, Arnaud Bailly
wrote: Hello, I recently tried to upgrade some package (eg. yesod) and it seems that, in the process, I screwed up my Haskell packages setup. When I am trying to do a simple:
ghc --make Crete1941
What command(s) did you issue to "upgrade some packages?" Were you trying to do a user or global install?
When ghc loads packages, I've had cases where packages in the user db would shadow packages in the global db, causing *other* packages in the global db to report as "broken".
Thanks, Antoine
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

AFAIK GHC on Windows comes with it's own mingw, but I'm not sure if the
toolchain is complete. But I wouldn't try to reinstall core packages anyway.
They are best picked from installation package.
Best regards,
Krzysztof Skrzętnicki
2011/2/1 Arnaud Bailly
I started that way but quickly ran into issues about compilers toolchain for certain packages: I am on windows and some core packages require mingw toolchain.
2011/2/1 Krzysztof Skrzętnicki
: This is the easiest way conceptually. You can also try to --reinstall every package that 'ghc-pkg check' report is broken. If you pick up the right version and compilation options will match there is a high chance you can fix this state. I've done this before and it worked. Best regards, Krzysztof Skrzętnicki
On Tue, Feb 1, 2011 at 08:16, Arnaud Bailly
wrote: Hi, Thanks for your answers.
I did
cabal upgrade yesod
As for the user/global issue, I think I tried a user install, this is default isn't it?
Looks like I will have to reinstall everything :-(
Arnaud
On Tue, Feb 1, 2011 at 1:34 AM, Antoine Latter
wrote:
On Mon, Jan 31, 2011 at 4:59 PM, Arnaud Bailly < arnaud.oqube@gmail.com> wrote:
Hello, I recently tried to upgrade some package (eg. yesod) and it seems that, in the process, I screwed up my Haskell packages setup. When I am trying to do a simple:
ghc --make Crete1941
What command(s) did you issue to "upgrade some packages?" Were you trying to do a user or global install?
When ghc loads packages, I've had cases where packages in the user db would shadow packages in the global db, causing *other* packages in the global db to report as "broken".
Thanks, Antoine
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

On Tue, Feb 1, 2011 at 1:16 AM, Arnaud Bailly
Hi, Thanks for your answers.
I did
cabal upgrade yesod
As for the user/global issue, I think I tried a user install, this is default isn't it?
Looks like I will have to reinstall everything :-(
Well, since you went wrong with a user install you should be fine clearing out your user package DB. So you'll only need to reinstall most things :-) There might be a path forward, but I get frustrated easily with this sort of thing - I would have cleared by user package DB by no, I think.
Arnaud
On Tue, Feb 1, 2011 at 1:34 AM, Antoine Latter
wrote: On Mon, Jan 31, 2011 at 4:59 PM, Arnaud Bailly
wrote: Hello, I recently tried to upgrade some package (eg. yesod) and it seems that, in the process, I screwed up my Haskell packages setup. When I am trying to do a simple:
ghc --make Crete1941
What command(s) did you issue to "upgrade some packages?" Were you trying to do a user or global install?
When ghc loads packages, I've had cases where packages in the user db would shadow packages in the global db, causing *other* packages in the global db to report as "broken".
Thanks, Antoine

That's what my experience tell me :-)
I guess it is mainly my private packages that are screwed up. I will
first try moving this out of the way before reinstalling Haskell
Platform.
On Tue, Feb 1, 2011 at 1:41 PM, Antoine Latter
On Tue, Feb 1, 2011 at 1:16 AM, Arnaud Bailly
wrote: Hi, Thanks for your answers.
I did
cabal upgrade yesod
As for the user/global issue, I think I tried a user install, this is default isn't it?
Looks like I will have to reinstall everything :-(
Well, since you went wrong with a user install you should be fine clearing out your user package DB.
So you'll only need to reinstall most things :-)
There might be a path forward, but I get frustrated easily with this sort of thing - I would have cleared by user package DB by no, I think.
Arnaud
On Tue, Feb 1, 2011 at 1:34 AM, Antoine Latter
wrote: On Mon, Jan 31, 2011 at 4:59 PM, Arnaud Bailly
wrote: Hello, I recently tried to upgrade some package (eg. yesod) and it seems that, in the process, I screwed up my Haskell packages setup. When I am trying to do a simple:
ghc --make Crete1941
What command(s) did you issue to "upgrade some packages?" Were you trying to do a user or global install?
When ghc loads packages, I've had cases where packages in the user db would shadow packages in the global db, causing *other* packages in the global db to report as "broken".
Thanks, Antoine

On Mon, Jan 31, 2011 at 11:16 PM, Arnaud Bailly
Hi, Thanks for your answers.
I did
cabal upgrade yesod
I think 'upgrade' is deprecated, and known to break things on occasion (or at least have unexpected behavior--I'm not clear on the details). You can use 'cabal install' to upgrade packages. --Rogan
participants (5)
-
Antoine Latter
-
Arnaud Bailly
-
Daniel Fischer
-
Krzysztof Skrzętnicki
-
Rogan Creswick