January 2012 - cabal-devel

[Hackage] #856: cabal list UTF-8 problem
by Hackage 16 Apr '12

16 Apr '12

#856: cabal list UTF-8 problem ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.10.1.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: Windows | ---------------------------------+------------------------------------------ C:\>cabal list dedukti * dedukti Synopsis: A type-checker for the cabal.EXE: <stdout>: invalid argument http://hackage.haskell.org/packages/archive/dedukti/1.1.4/dedukti.cabal "A type-checker for the λΠ-modulo calculus." -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/856> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 7

[Hackage] #695: cabal install world always reinstalls programs
by Hackage 16 Apr '12

16 Apr '12

#695: cabal install world always reinstalls programs ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: Severity: normal | Keywords: Difficulty: easy (<4 hours) | Ghcversion: Platform: | ---------------------------------+------------------------------------------ cabal-install does not currently track the installed state of programs. It does now list them in the world file however. This leads to it always wanting to reinstall programs. Probably we do want to keep the programs in the world file, since we hopefully will track programs better in future. The temporary hack would be to filter out packages that have no lib when retrieving packages from the world file. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/695> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 6

[Hackage] #694: mention --constraint flag in error essage when dep planning fails
by Hackage 16 Apr '12

16 Apr '12

#694: mention --constraint flag in error essage when dep planning fails ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: Severity: normal | Keywords: Difficulty: easy (<4 hours) | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Dependency planning problems can often be solved by running with --dry-run -v, seeing what the planner is selecting and forcing it to make different choices using the --constraint flag. When dependency planning fails with particular kinds of constraint problem, it may be useful to users to mention this. We should check if this advice applies to all cases where the dep planner fails, or if its only appropriate for certain classes of failure. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/694> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #909: cabal-install-ghc72 tarball has Mac-specific files.
by Hackage 12 Apr '12

12 Apr '12

#909: cabal-install-ghc72 tarball has Mac-specific files. ---------------------------------+------------------------------------------ Reporter: pdxleif | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ In the tarball of http://hackage.haskell.org/package/cabal-install- ghc72-0.10.4, there are Mac-specific metadata files: ._bootstrap.sh ._cabal-install-ghc72.cabal ._Main.hs These cause problems on my Linux system, ./Setup configure complains of multiple cabal files, and refuses to run until I delete the ._* files. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/909> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #789: build-depends on packages that provide no library
by Hackage 10 Apr '12

10 Apr '12

#789: build-depends on packages that provide no library ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ It is possible to list build-depends on packages that have just an executable and no library. Currently the behaviour of cabal-install does not consider this and it will allow such packages to be pulled in as dependencies. It leads to problems however because the non-lib package never gets registered with ghc-pkg and so it leads to re-install loops. The solution is for cabal-install to not consider exe-only packages to be valid for satisfying a build-depends requirement. It should produce a suitable error message. Note that it must take into account the posibility that a newer or older version of a package may switch from exe only to exe+lib or just lib, or indeed vica versa. We should mark exe-only versions of the package as excluded with a reason. Then if the dep is not satisfiable then we can explain why all the excluded ones were excluded (ie due to not exposing a lib). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/789> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #753: cabal executable chooses different versions of libraries than cabal library
by Hackage 09 Apr '12

09 Apr '12

#753: cabal executable chooses different versions of libraries than cabal library ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Hi, cabal-install version 0.8.2 using version 1.8.0.2 of the Cabal library This bug was originally reported by a Debian user. the `cabal' executable, when run on the attached sample library, chooses base 3.0.3.2: $ cabal -v configure [...] Configuring foobar-0.0... Dependency base ==3.0.3.2: using base-3.0.3.2 [...] whereas, the library (via Setup.hs) correctly gets base 4.2.0.0, probably due to ghc's hiding of the earlier version $ runhaskell Setup.hs -v configure Configuring foobar-0.0... Dependency base -any: using base-4.2.0.0 [...] cabal-install should probably perform the same hiding that ghc does. Cheers, Iain -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/753> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 6

[Hackage] #762: cabal-install failed to resolve dependencies
by Hackage 07 Apr '12

07 Apr '12

#762: cabal-install failed to resolve dependencies ---------------------------------+------------------------------------------ Reporter: james_m_chapman | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.2 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ I tried to update my installation of the development version of Agda. I did a darcs pull from the repo (darcs get --lazy http://code.haskell.org/Agda) and then tried to build it: $ darcs pull $ cabal update $ cabal clean $ cabal install I get the following error: "Resolving dependencies... cabal: cannot configure haskeline-0.6.2.2. It requires mtl ==1.1.* For the dependency on mtl ==1.1.* there are these packages: mtl-1.1.0.0, mtl-1.1.0.1, mtl-1.1.0.2 and mtl-1.1.1.0. However none of them are available. mtl-1.1.0.0 was excluded because Agda-2.2.9 requires mtl ==2.0.* mtl-1.1.0.1 was excluded because Agda-2.2.9 requires mtl ==2.0.* mtl-1.1.0.2 was excluded because Agda-2.2.9 requires mtl ==2.0.* mtl-1.1.1.0 was excluded because Agda-2.2.9 requires mtl ==2.0.*" Agda's .cabal file is here http://code.haskell.org/Agda/Agda.cabal and contains the build-depends line haskeline >= 0.3 && < 0.7 The solution is to upgrade haskeline to the latest version by running: $ cabal install haskeline Should cabal-install have been able to work this out itself? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/762> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 6

[Hackage] #782: When building a plan, use installed package dependencies in preference to those from Hackage
by Hackage 07 Apr '12

07 Apr '12

#782: When building a plan, use installed package dependencies in preference to those from Hackage ---------------------------------+------------------------------------------ Reporter: batterseapower | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ I was installing a package, let us call it foo. This package depended on a package foo', which in turn depended on bar, which in turn depended on baz < 0.3, but baz 0.3 was the default that came with the newer version of GHC I had just installed. Thus, I cabal-unpacked bar and bumped the baz dependency to < 0.4, **without changing the baz version number** since this was just a private change. This built and installed just fine with the new baz. I then went back to cabal install foo. I expected that cabal-install would just install foo' and then foo in that order. Instead, it tried to install baz 0.2, then bar, then foo', then foo. This seems stupid because I already had a perfectly acceptable bar installed. Why didn't Cabal just reuse that? It seems as if it is resolving dependencies by looking at the dependency information for bar **from the Hackage database** rather than the dependencies **from the installed bar**. The workaround is to go back to the unpacked bar and bump the version number, then reinstall it. Now when you install foo the installed baz is used as expected. It would be cool if this worked as expected without bumping the version number, because having to bump the version number even if not making a Hackage release is tiresome. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/782> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #884: Changed dependencies in locally installed packages ignord
by Hackage 07 Apr '12

07 Apr '12

#884: Changed dependencies in locally installed packages ignord ---------------------------------+------------------------------------------ Reporter: nomeata | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Hello, in Debian, I have patched yesod-json-0.2.1 to depend on aeson instead of aeson-native, because we want only one aeson and blaze-textual package in Debian. Still, if I use cabal install to install a package that depends on yesod- json, it wants to re-build yesod-json against the -native variants. It seems that cabal install does not take the actual dependencies of installed packages into account and uses the Hackage provided information for them as well. What it should do instead is: If a dependency of some packages that is to be installed can be fulfilled by a locally installed package, and none of its dependencies (as known by ghc-pkg) have to be rebuild, then this package should be used. Only if the package in question has to be rebuild, the dependencies according to hackage should be taken into account. The work around in Debian is to bump the version number, adding a vendor level (0.2.1.0.1), but it would be nice if this could be avoided. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/884> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 8

[Hackage] #904: Solver fails for unknown reason
by Hackage 07 Apr '12

07 Apr '12

#904: Solver fails for unknown reason ----------------------------+----------------------------------------------- Reporter: tibbe | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- I was trying to build `snap-core` and got this constraint solving error, which I can't make sense of: {{{ Reading available packages... Resolving dependencies... selecting snap-server-0.7.1.1 (hackage) and discarding MonadCatchIO-transformers-0.0.1.0, 0.0.2.0, 0.1.0.0, 0.1.0.1, 0.2.0.0, PSQueue-1.0, array-0.1.0.0, attoparsec-0.4, 0.5, 0.5.1, 0.6, 0.7.1, 0.7.2, 0.8.0.0, 0.8.0.1, 0.8.0.2, 0.8.1.0, 0.8.1.1, 0.8.2.0, 0.8.3.0, 0.8.4.0, 0.8.5.0, 0.8.5.1, 0.8.5.2, 0.8.5.3, 0.8.6.0, 0.8.6.1, 0.9.0.0, 0.9.1.1, 0.9.1.2, attoparsec-enumerator-0.1, 0.1.0.1, 0.1.0.2, 0.1.0.3, 0.2, 0.2.0.1, 0.2.0.2, 0.2.0.3, 0.2.0.4, 0.2.0.5, binary-0.2, 0.3, 0.4, 0.4.1, 0.4.2, 0.4.3, 0.4.3.1, 0.4.4, blaze-builder-0.1, 0.2.0.0, 0.2.0.1, 0.2.0.2, 0.2.0.3, 0.2.1.0, 0.2.1.1, 0.2.1.2, 0.2.1.3, blaze-builder-enumerator-0.1, bytestring-0.9, 0.9.0.1, 0.9.0.2, 0.9.0.3, 0.9.0.4, case-insensitive-0.1, 0.2, 0.2.0.1, 0.2.0.2, containers-0.1.0.0, 0.1.0.1, 0.2.0.0, 0.2.0.1, directory-tree-0.1, 0.1.1, 0.1.2, 0.2.0, 0.2.1, 0.9.0, 0.9.1, enumerator-0.1, 0.1.1, 0.2, 0.2.1, 0.3, 0.3.0.1, 0.4, 0.4.0.1, 0.4.0.2, 0.4.1, 0.4.2, 0.4.3, 0.4.3.1, 0.4.4, 0.4.5, 0.4.6, 0.4.7, 0.4.8, 0.4.9, 0.4.9.1, 0.4.10, 0.4.11, 0.4.12, 0.4.13, filepath-1.0, 1.3.0.0, mtl-1.0, 1.1.0.0, 1.1.0.1, 1.1.0.2, 1.1.1.0, 1.1.1.1, network-2.0, 2.1.0.0, 2.2.0.0, 2.2.0.1, 2.2.1, 2.2.1.1, 2.2.1.2, 2.2.1.3, 2.2.1.4, 2.2.1.5, 2.2.1.6, 2.2.1.7, 2.2.1.8, 2.2.1.9, 2.2.1.10, 2.2.3, 2.2.3.1, snap-core-0.1.1, 0.1.2, 0.2.1, 0.2.2, 0.2.3, 0.2.4, 0.2.5, 0.2.6, 0.2.7, 0.2.7.1, 0.2.8, 0.2.8.1, 0.2.9, 0.2.10, 0.2.11, 0.2.12, 0.2.13, 0.2.14, 0.2.15, 0.2.15.1, 0.2.16, 0.3.0, 0.3.1, 0.3.1.1, 0.4.0, 0.4.0.1, 0.4.0.2, 0.4.1, 0.4.2, 0.4.3, 0.5.0, 0.5.1, 0.5.1.1, 0.5.1.2, 0.5.1.3, 0.5.1.4, 0.5.2, 0.5.3, 0.5.3.1, 0.5.4, 0.5.5, 0.6.0, 0.6.0.1, template-haskell-2.7.0.0, text-0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.7.0.1, 0.7.1.0, 0.7.2.1, 0.8.0.0, 0.8.1.0, 0.9.0.0, 0.9.0.1, 0.9.1.0, 0.10.0.0, 0.10.0.1, 0.10.0.2, transformers-0.0.0.0, 0.0.1.0, 0.1.0.0, 0.1.0.1, 0.1.1.0, 0.1.3.0, 0.1.4.0, unix-compat-0.1, 0.1.1, 0.1.2.0, 0.1.2.1, vector-0.1, 0.2, 0.3, 0.3.1, 0.4, 0.4.1, 0.4.2, 0.5, 0.6, 0.6.0.1, 0.6.0.2, vector-algorithms-0.3, 0.3.1, 0.3.2, 0.3.3 and 0.3.4 selecting PSQueue-1.1 (hackage) selecting attoparsec-enumerator-0.3 (hackage) selecting base-4.5.0.0 (installed) selecting directory-tree-0.10.0 (hackage) selecting ghc-prim-0.2.0.0 (installed) selecting integer-gmp-0.4.0.0 (installed) selecting rts-1.0 (installed) selecting snap-core-0.7 (hackage) and discarding HUnit-1.1, bytestring-mmap-0.1.1, 0.1.2, 0.2.0, 0.2.1, deepseq-1.0.0.0, dlist-0.2, 0.3, 0.3.1, 0.3.2, 0.4, 0.4.1, mwc-random-0.4.1, 0.4.1.1, 0.5.0.0, 0.5.1.1, 0.5.1.2, 0.5.1.3, 0.5.1.4, 0.6.0.0, 0.7.0.0, 0.7.0.1, 0.8.0.0, 0.8.0.1, 0.8.0.2, 0.8.0.3, 0.8.0.5, 0.9.0.0, unix-2.0, 2.2.0.0, 2.3.0.0, 2.3.1.0, 2.3.2.0, unordered-containers-0.1.0.0, 0.1.1.0, 0.1.2.0, 0.1.3.0, 0.1.4.0, 0.1.4.1, 0.1.4.2, zlib-enum-0.0, 0.1 and 0.2 selecting bytestring-mmap-0.2.2 (hackage) selecting dlist-0.5 (hackage) selecting zlib-enum-0.2.1 (hackage) selecting vector-algorithms-0.5.3 (hackage) and discarding primitive-0.1, 0.2, 0.2.1, vector-algorithms-0.4, 0.5.0, 0.5.1 and 0.5.2 selecting unordered-containers-0.1.4.4 (hackage) and discarding hashable-1.0.0, 1.0.1.0 and unordered-containers-0.1.4.3 selecting zlib-bindings-0.0.1 (hackage) and discarding bytestring-0.9.1.0, 0.9.1.1, 0.9.1.2, 0.9.1.3, zlib-0.2, 0.3, 0.4, 0.4.0.1, 0.4.0.2, 0.4.0.3, 0.4.0.4, 0.5.0.0 and zlib-bindings-0.0.0 selecting unix-compat-0.3 (hackage) and discarding unix-compat-0.2, 0.2.1, 0.2.1.1, 0.2.1.2, 0.2.1.3, 0.2.2 and 0.2.2.1 selecting zlib-0.5.3.1 (hackage) and discarding zlib-0.5.2.0 selecting mwc-random-0.10.0.1 (hackage) and discarding mwc-random-0.10.0.0 selecting vector-0.9.1 (installed) and discarding primitive-0.3, 0.3.1, 0.4, 0.4.0.1, vector-0.7, 0.7.0.1, 0.7.1, 0.8 and 0.9 selecting primitive-0.4.0.1 (installed) selecting murmur-hash-0.1.0.5 (installed) and discarding bytestring-0.9.1.4, 0.9.1.5, 0.9.1.6, 0.9.1.7, 0.9.1.8, 0.9.1.9, 0.9.1.10, 0.9.2.0, murmur-hash-0.1, 0.1.0.2 and 0.1.0.4 selecting bytestring-0.9.2.1 (installed) selecting case-insensitive-0.4.0.1 (hackage) and discarding case-insensitive-0.3, 0.3.0.1 and 0.4 selecting hashable-1.1.2.2 (hackage) and discarding hashable-1.0.1.1, 1.1.0.0, 1.1.1.0, 1.1.2.0, 1.1.2.1, text-0.11.0.0, 0.11.0.1, 0.11.0.2, 0.11.0.3 and 0.11.0.4 selecting bytestring-nums-0.3.5 (hackage) and discarding bytestring-nums-0.1.0, 0.2.0, 0.2.1, 0.3.0, 0.3.1, 0.3.2, 0.3.3 and 0.3.4 selecting blaze-builder-enumerator-0.2.0.3 (hackage) and discarding blaze-builder-enumerator-0.2.0.0, 0.2.0.1 and 0.2.0.2 selecting blaze-builder-0.3.0.2 (hackage) and discarding blaze-builder-0.2.1.4, 0.3.0.0 and 0.3.0.1 selecting base16-bytestring-0.1.1.3 (hackage) and discarding base16-bytestring-0.1.0.0, 0.1.1.0, 0.1.1.1 and 0.1.1.2 selecting enumerator-0.4.16 (hackage) and discarding enumerator-0.4.13.1, 0.4.14 and 0.4.15 selecting attoparsec-0.10.1.0 (hackage) and discarding attoparsec-0.10.0.0, 0.10.0.1, 0.10.0.2, 0.10.0.3, text-0.11.0.5, 0.11.0.6, 0.11.0.7, 0.11.0.8, 0.11.1.0, 0.11.1.1, 0.11.1.2 and 0.11.1.3 selecting MonadCatchIO-transformers-0.2.2.3 (hackage) and discarding MonadCatchIO-transformers-0.2.1.0, 0.2.2.0, 0.2.2.1 and 0.2.2.2 selecting transformers-0.2.2.0 (hackage) and discarding transformers-0.2.0.0 and 0.2.1.0 selecting network-2.3.0.8 (installed or hackage) and discarding network-2.3, 2.3.0.1, 2.3.0.2, 2.3.0.3, 2.3.0.4, 2.3.0.5, 2.3.0.6 and 2.3.0.7 selecting parsec-3.1.2 (installed or hackage) and discarding parsec-2.0, 2.1.0.0, 2.1.0.1, 3.0.0, 3.0.1, 3.1.0 and 3.1.1 selecting text-0.11.1.10 (installed) and discarding array-0.2.0.0, 0.3.0.0, 0.3.0.1, 0.3.0.2, 0.3.0.3, deepseq-1.1.0.0, 1.1.0.1, 1.1.0.2, 1.2.0.0, 1.2.0.1, text-0.11.1.5, 0.11.1.6, 0.11.1.7, 0.11.1.8 and 0.11.1.9 selecting array-0.4.0.0 (installed) selecting deepseq-1.2.0.2 (installed) selecting regex-posix-0.95.1 (hackage) and discarding regex-base-0.71, 0.72.0.1, 0.72.0.2, 0.83, 0.90, 0.91, 0.92, regex-posix-0.71, 0.72, 0.72.0.1, 0.72.0.2, 0.72.0.3, 0.91, 0.92, 0.93, 0.93.1, 0.93.2, 0.94.0, 0.94.1, 0.94.2, 0.94.4 and 0.95.0 selecting regex-base-0.93.2 (hackage) and discarding regex-base-0.93 and 0.93.1 selecting extensible-exceptions-0.1.1.4 (installed) and discarding extensible-exceptions-0.1.0.1, 0.1.1.0, 0.1.1.1, 0.1.1.2 and 0.1.1.3 selecting template-haskell-2.6.0.0 (hackage) and discarding template-haskell-2.2.0.0, 2.3.0.0, 2.3.0.1, 2.4.0.0, 2.4.0.1 and 2.5.0.0 selecting cabal: dependencies conflict: binary-0.5.0.3 requires deepseq ==1.2.0.1 however deepseq-1.2.0.1 was excluded because deepseq-1.2.0.2 was selected instead deepseq-1.2.0.1 was excluded because text-0.11.1.10 requires deepseq ==1.2.0.2 }}} I don't know why deepseq-1.2.0.1 and deepseq-1.2.0.2 ended up conflicting. I couldn't find any lib that depended on an exact patch-level version of deepseq. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/904> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4