February 2012 - cabal-devel

[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

[Hackage] #731: Custom Build-type with --package-db and --global encounters runtime error
by Hackage 28 Mar '12

28 Mar '12

#731: Custom Build-type with --package-db and --global encounters runtime error ---------------------------------+------------------------------------------ Reporter: cygnus | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.4 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: 6.12.2 Platform: Linux | ---------------------------------+------------------------------------------ To reproduce: * Run `cabal init`, change `Build-type` to `Custom` (`Setup.hs` already provided by `cabal init`) * Run `ghc-pkg init db` * Run `cabal configure --package-db=./db --global` * Output: {{{ Resolving dependencies... cabal: internal error: unexpected package db stack }}} In `cabal-install-0.8.2`, this appears to be caused by the code on lines 112-114 of `Distribution.Client.Configure`: {{{ usePackageDB = if UserPackageDB `elem` packageDBs then packageDBs else packageDBs ++ [UserPackageDB] }}} in combination with the code on lines 297-306 of `Distribution.Client.SetupWrapper`: {{{ ghcPackageDbOptions :: PackageDBStack -> [String] ghcPackageDbOptions dbstack = case dbstack of (GlobalPackageDB:UserPackageDB:dbs) -> concatMap specific dbs (GlobalPackageDB:dbs) -> "-no-user-package-conf" : concatMap specific dbs _ -> ierror where specific (SpecificPackageDB db) = [ "-package-conf", db ] specific _ = ierror ierror = error "internal error: unexpected package db stack" }}} Essentially, the order of the package databases in the stack is not as expected since the list already contains a `SpecificPackageDB` when the `UserPackageDB` is appended. (Note: this applies to GHC 6.12.3 and Cabal 1.8.0.6 on my system, but I could not select those versions in the ticket properties.) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/731> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #920: hackage-mirror fails with HTTP 400 on PlslTools
by Hackage 23 Mar '12

23 Mar '12

#920: hackage-mirror fails with HTTP 400 on PlslTools -------------------------------+-------------------------------------------- Reporter: bgamari | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Hackage 2 server | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | -------------------------------+-------------------------------------------- hackage-mirror against hackage.haskell.org fails with, {{{ $ hackage-mirror http://hackage.haskell.org/ http://bgamari:xxx@localhost:8080/ 17816 packages to mirror. mirroring PlslTools-0.0.1 hackage-mirror: Failed to upload package PlslTools-0.0.1, HTTP error code 400, Bad Request http://bgamari:...@localhost:8080/package/PlslTools-0.0.1/PlslTools-0.0.1.t… short tar trailer }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/920> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #917: Generated Paths module broken with NoImplicitPrelude
by Hackage 17 Mar '12

17 Mar '12

#917: Generated Paths module broken with NoImplicitPrelude ----------------------------+----------------------------------------------- Reporter: dag | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- A .cabal with NoImplicitPrelude breaks the generated Paths_pkgname module which relies on Prelude being implicitly imported, and is built using the extensions configured in .cabal: Name: pkgname Library Extensions: NoImplicitPrelude Other-Modules: Paths_pkgname Something like the above will result in build errors for missing symbols in Paths_pkgname. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/917> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #807: inplace is shadowed by package
by Hackage 15 Mar '12

15 Mar '12

#807: inplace is shadowed by package ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: test Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- I have a library, persistent, that builds. When I try to build the test suite, I get: {{{ Preprocessing library persistent-0.4.0.1... Preprocessing test suites for persistent-0.4.0.1... Building persistent-0.4.0.1... Registering persistent-0.4.0.1... <command line>: cannot satisfy -package-id persistent-0.4.0.1-inplace: persistent-0.4.0.1-inplace is shadowed by package persistent-0.4.0.1-f5ffa1e952f5d8b58608c8d1f9f69825 (use -v for more information) }}} The test-suite build-depends has: {{{ persistent >= 0.4.0.1, persistent-mongoDB, persistent-postgresql, persistent-sqlite, }}} persistent-mongoDB (and postgresql and sqlite) depends on persistent to build. I have tried this twice now from a fairly clean install- immediately after upgrading to a new version of ghc. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/807> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 7

[Hackage] #896: cabal install cabal-install fails if gcc not in /Developer/usr/bin/gcc
by Hackage 11 Mar '12

11 Mar '12

#896: cabal install cabal-install fails if gcc not in /Developer/usr/bin/gcc ---------------------------------+------------------------------------------ Reporter: jeremyw.sherman | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.2 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: Mac OS | ---------------------------------+------------------------------------------ Under Mac OS X, `cabal` assumes `gcc` is at `/Developer/usr/bin/gcc`. This fails when Xcode is installed to another directory. Xcode has supported installing to an arbitrary folder since at least Xcode 3.x. This is particularly common among iOS developers, as they frequently require multiple parallel Xcode installs. Since Xcode installs gcc to both `$DEVELOPER/usr/bin/gcc` and `/usr/bin/gcc`, this could be fixed by using `/usr/bin/gcc` directly or the result of a search in `$PATH` for `gcc`. The user workaround for now is to symlink `/Xcode_4_2` (or whatever the user's latest Xcode install directory is) to `/Developer`. (Apple is moving from `gcc` to `clang`, anyway. Apple's `gcc` has been frozen at an ancient version for some time now.) Sample session exhibiting this bug: {{{ $ cabal install cabal-install Resolving dependencies... Configuring cabal-install-0.10.2... ghc: could not execute: /Developer/usr/bin/gcc cabal: Error: some packages failed to install: cabal-install-0.10.2 failed during the configure step. The exception was: ExitFailure 1 $ cabal --version cabal-install version 0.8.0 using version 1.8.0.2 of the Cabal library $ which gcc /usr/bin/gcc $ which clang /usr/bin/clang $ ls -l `which gcc` lrwxr-xr-x 1 root wheel 12 13 Okt 15:37 /usr/bin/gcc@ -> llvm-gcc-4.2 $ ls -l `which clang` -rwxrwxr-x 1 root admin 41251344 27 Aug 03:53 /usr/bin/clang* $ ghc --version The Glorious Glasgow Haskell Compilation System, version 7.0.3 }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/896> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 5

[Hackage] #842: cabal appears to complain about relative paths
by Hackage 10 Mar '12

10 Mar '12

#842: cabal appears to complain about relative paths ---------------------------------+------------------------------------------ Reporter: jeffz | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.10.1.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ With `cabal configure --extra-lib-dirs=foo` $ cabal build Preprocessing library HENet-0.0.1... Building HENet-0.0.1... Registering HENet-0.0.1... cabal.exe: HENet-0.0.1: library-dirs: .libs is a relative path (use --force to override) Originally reported on irc: <dcoutts> jeffz: the right solution here would be for cabal to make the paths absolute before passing them on to ghc-pkg -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/842> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #908: Error installing base
by Hackage 08 Mar '12

08 Mar '12

#908: Error installing base ----------------------------+----------------------------------------------- Reporter: mcandre | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.2 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Specs: {{{ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 10.04.3 LTS Release: 10.04 Codename: lucid $ ghc --version The Glorious Glasgow Haskell Compilation System, version 6.12.1 $ cabal --version cabal-install version 0.8.0 using version 1.8.0.2 of the Cabal library }}} Trace: {{{ $ sudo cabal install base Resolving dependencies... cabal: Distribution/Client/Dependency/TopDown.hs:169:37-73: Non-exhaustive patterns in lambda }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/908> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #910: per-package configuration
by Hackage 06 Mar '12

06 Mar '12

#910: per-package configuration ---------------------------------+------------------------------------------ Reporter: kowey | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ This may be related to #223 but I don't particularly want it in my global config. I'm sick of running "cabal build" and not noticing until much later that my test had a compile error because I'd neglected to reconfigure with "--enable-test". A similar issue happens with packages with custom flags, say sometimes I lose the "-f-library" flag I sometimes use for faster compilation. I wish I had a mechanism to remember the command line flags passed in for a particular package. Editing my global config doesn't seem quite like what I'm looking for; it has to be something that works, eg. with different branches of the same package. What might be better for me is something like the Darcs prefs system, where I could edit a file in the current working directory like ".cabal" that says something like {{{ configure --enable-test -f-library install -fgui }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/910> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #675: template-haskell cannot be upgraded (broken data-accessor-template)
by Hackage 05 Mar '12

05 Mar '12

#675: template-haskell cannot be upgraded (broken data-accessor-template) ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: 6.12.1 Platform: | ---------------------------------+------------------------------------------ data-accessor-template-0.2.1.3 has flags in the cabal file on template- haskell versions, which makes it broken for cabal-install on ghc-6.12: cabal-install tries to install template-haskell-2.3, which fails (and it can't be expected to succeed because TH is integrated into ghc due to quotes) You can work around the build failure with: {{{ cabal install data-accessor-template --constraint='template-haskell >= 2.4' }}} cabal-install ought to know that template-haskell isn't something it should install (as it does with base). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/675> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4