There were theese lines in the end of ghc-pkg output log:
The following packages are broken, either because they have a problem
listed above, or because they depend on a broken package.
pipes-core-0.1.0
pipes-core-0.1.0
And yes, I tried to load Control.Pipes in ghci. It worked not.
Now I solved
Thanks, haven't tried it yet, but ...
> 7. nixpkgs$ ghc-pkg check
... the output of "ghc-pkg check" for the wrapped GHC is possibly a
bit suspicious. Have you tried
$ ghci -package pipes-core
$ ghci -package categories
Do these work or not?
Cheers,
Andres
___
Steps:
1. ~$ git clone https://github.com/NixOS/nixpkgs.git
2. ~$ cd nixpkgs/pkgs/development/libraries/haskell/; mkdir categories;
mkdir pipes-core; cd ../../../../
3. nixpkgs$ cabal2nix cabal://categories-1.0.3 >
pkgs/development/libraries/haskell/categories/default.nix
nixpkgs$ cabal2nix cab
> After rechecking found, that installing `pipes-core` package didn't install
> `categories` package, .nix file for which I added also. When I installed
> `categories`, it worked. Is it a bug? `Categories` package is mentioned in
> dependencies in pipes-core/default.nix
>From your description, I d
Oh! Realy! Kind of magic.
After rechecking found, that installing `pipes-core` package didn't install
`categories` package, .nix file for which I added also. When I installed
`categories`, it worked. Is it a bug? `Categories` package is mentioned in
dependencies in pipes-core/default.nix
2012/8/1
> But dependency hell was not gone.
>
> pipes-core-0.1.0: dependency "base-4.5.0.0-f76ceb9607ba9bd4fcfb9c7b92d8cfe1"
> doesn't exist (ignoring)
> pipes-core-0.1.0: dependency
> "categories-1.0.3-e9ab00168a7d0fdacafd64b31a5e1100" doesn't exist (ignoring)
> pipes-core-0.1.0: dependency
> "lifted-base
>
>How to rebuild everything from source? Got to the definition of that ghc
> version, then add a dummy env var such as
>
> FORCE_REBUILD=1;
>
> and retry. That FORCE_REBUILD should cause nix rebuilding everything
> from source. Report if this solved the issue. If it does we should
> documen
Those hashes have been introduced somewhen after ghc 6.12 to make the
dependency hell easier which existed with cabal. Eg if you have
A > B > C > D and you cabal had to recompile A and B because you tried
installing yet another package C and D are "stale" because A,B it
depends on are gone. To det