Ticket #650 (closed defect: fixed)

Opened 3 years ago

Last modified 18 months ago

cabal-install clueless of previously installed lib with custom package-db

Reported by: nomeata Owned by:
Priority: normal Milestone:
Component: cabal-install tool Version:
Severity: normal Keywords:
Cc: 575608@… Difficulty: unknown
GHC Version: Platform: Linux

Description

This bug was reported by a Debian user:

This seems to happen for any library that carried dependencies, not just parallel/deepseq.

lane@biped:~/src/test $ cabal --version
cabal-install version 0.8.0
using version 1.8.0.2 of the Cabal library 
lane@biped:~/src/test $ cabal update
Downloading the latest package list from hackage.haskell.org
lane@biped:~/src/test $ echo "[]" > my-package-db
lane@biped:~/src/test $ cabal install parallel --package-db="/home/lane/src/test/my-package-db" --prefix="/home/lane/src/test/prefix/"
Resolving dependencies...
Downloading deepseq-1.1.0.0...
Configuring deepseq-1.1.0.0...
Preprocessing library deepseq-1.1.0.0...
Building deepseq-1.1.0.0...
[1 of 1] Compiling Control.DeepSeq  ( Control/DeepSeq.hs, dist/build/Control/DeepSeq.o )
Registering deepseq-1.1.0.0...
Installing library in
/home/lane/src/test/prefix//lib/deepseq-1.1.0.0/ghc-6.12.1
Registering deepseq-1.1.0.0...
Downloading parallel-2.2.0.1...
Configuring parallel-2.2.0.1...
Preprocessing library parallel-2.2.0.1...
Building parallel-2.2.0.1...
[1 of 2] Compiling Control.Parallel ( Control/Parallel.hs, dist/build/Control/Parallel.o )
[2 of 2] Compiling Control.Parallel.Strategies ( Control/Parallel/Strategies.hs, dist/build/Control/Parallel/Strategies.o )
Registering parallel-2.2.0.1...
cabal: parallel-2.2.0.1: dependency
"deepseq-1.1.0.0-14fbf43e1c607f21a1eab1783c9c45d4" doesn't exist (use --force to override)
cabal: Error: some packages failed to install:
parallel-2.2.0.1 failed during the building phase. The exception was: ExitFailure 1

Was he doing something wrong, or is this a bug in cabal-install?

Change History

Changed 3 years ago by duncan

  • status changed from new to closed
  • resolution set to fixed

Yes it's a bug that happens with cabal-install-0.8.0 when using ghc-6.12 with the --package-db flag. It is already fixed in the cabal-install-0.8.x branch and will be included in the upcoming 0.8.2 release.

Changed 18 months ago by elga

Note: See TracTickets for help on using tickets.