Ticket #826 (closed defect: invalid)

Opened 2 years ago

Last modified 2 years ago

"dependency conflict"

Reported by: nue_057 Owned by:
Priority: normal Milestone:
Component: cabal-install tool Version: 1.8.0.6
Severity: normal Keywords:
Cc: Difficulty: unknown
GHC Version: 6.12.3 Platform: Windows

Description

when depnedency conflict happens, I usually use ghc-pkg unregister to solove the problem, but there is another problem. when I use ghc-pkg check, it always return a lot of problems, for example:

there is a conflict with bytestring-0.9.1.10 and bytestring-0.9.1.7, I unregister the version of 0.9.1.10.

ghc-pkg check, the message is: there are problems in package Win32-2.2.0.2 dependency "bytestring-0.9.1.10..." the following packages are broken, either beacause they have a problem listed above, or beacause the depend on a broken package. Win32-2.2.0.2, haskell98-1.0.1.1 QuickCheck?-2.4.0.1... does anyone can help me to fix these broken package?

thanks in advance !!

Change History

Changed 2 years ago by duncan

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

When you unregister a package, anything that depends on that package becomes broken. It is possible to "fix" that either by unregistering the broken package, or rebuilding it.

Changed 2 years ago by simonmic

I use this bash function:

# unregister broken GHC packages. Run this a few times to resolve dependency rot in installed packages. function ghc-pkg-clean() {

for p in ghc-pkg check 2>&1 | grep problems | awk '{print $6}' | sed -e 's/:$//' do

echo unregistering $p; ghc-pkg unregister $p

done

}

Note: See TracTickets for help on using tickets.