[Hackage] #490: cabal unpack gives bad error message for unsatisfiable constraints
#490: cabal unpack gives bad error message for unsatisfiable constraints ----------------------------------+----------------------------------------- Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: cabal-install-0.6 Component: cabal-install tool | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: Platform: | ----------------------------------+----------------------------------------- The simple use case works fine: {{{ $ cabal unpack HaXml Downloading HaXml-1.13.3... Unpacking HaXml-1.13.3... }}} But we also allow constraints and that does not necessarily work: {{{ $ cabal unpack HaXml-1.19.6 cabal: List.maximumBy: empty list }}} The problem is that the index does not contain `HaXml-1.19.6`. After a `cabal update` it is fine. In general this would happen for any user- supplied version constraint that turns out to be unsatisfiable. The function `resolvePackages` in `Distribution.Client.Unpack` does not consider the possibility that a dependency may be unsatisfiable. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/490> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects
#490: cabal unpack gives bad error message for unsatisfiable constraints ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: cabal-install-0.6 Component: cabal-install tool | Version: 1.6.0.1 Severity: normal | Resolution: Keywords: | Difficulty: very easy (<1 hour) Ghcversion: | Platform: ---------------------------------+------------------------------------------ Comment (by Saizan): With the attached patch we have: {{{ $ cabal unpack haxml-1.20 cabal: There is no available version of HaXml that satisfies ==1.20 }}} {{{ $ cabal unpack containers haxml-1.20 array 'containers-0.2.0.0' is cached. Unpacking containers-0.2.0.0... cabal: There is no available version of HaXml that satisfies ==1.20 }}} {{{ $ cabal unpack containers nonexistant cabal: There is no package named nonexistant }}} So, non-existant package names make unpack die early, while non-resolvable deps for existing packages make it die on the first one encountered while fetching, like other fetching-related problems (e.g. downloading or extracting). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/490#comment:1> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects
#490: cabal unpack gives bad error message for unsatisfiable constraints ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: defect | Status: closed Priority: normal | Milestone: cabal-install-0.6 Component: cabal-install tool | Version: 1.6.0.1 Severity: normal | Resolution: fixed Keywords: | Difficulty: very easy (<1 hour) Ghcversion: | Platform: ---------------------------------+------------------------------------------ Changes (by duncan): * status: new => closed * resolution: => fixed Comment: Applied, thanks. {{{ Sun Feb 8 16:52:40 GMT 2009 Andrea Vezzosi <sanzhiyan@gmail.com> * Fix #490, unpack now gives a proper error message. }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/490#comment:2> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects
participants (1)
-
Hackage