April 2012 - cabal-devel

Re: [Hackage] #517: make cabal install command support haddock options
by Hackage 16 Apr '12

16 Apr '12

#517: make cabal install command support haddock options ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: cabal-install-0.14 Component: cabal-install tool | Version: Severity: normal | Resolution: fixed Keywords: | Difficulty: normal Ghcversion: | Platform: ---------------------------------+------------------------------------------ Changes (by kosmikus): * status: new => closed * resolution: => fixed Comment: Seems to work. Closing. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/517#comment:16> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #412: build-reports: option is invalid in a config file
by Hackage 16 Apr '12

16 Apr '12

#412: build-reports: option is invalid in a config file ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: cabal-install-0.16 Component: cabal-install tool | Version: HEAD Severity: normal | Keywords: Difficulty: easy (<4 hours) | Ghcversion: 6.8.3 Platform: | ---------------------------------+------------------------------------------ Changes (by kosmikus): * milestone: cabal-install-0.14 => cabal-install-0.16 Comment: Duncan says: "Right. There is a 'remote-build-reporting' field and that's broken for other reasons :-(" So I'm leaving this open, but moving it to a later release. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/412#comment:4> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #368: The "optimization" option in ~/.cabal/config does not work
by Hackage 16 Apr '12

16 Apr '12

#368: The "optimization" option in ~/.cabal/config does not work ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: closed Priority: normal | Milestone: cabal-install-0.14 Component: cabal-install tool | Version: 1.4.0.1 Severity: minor | Resolution: fixed Keywords: | Difficulty: normal Ghcversion: 6.8.2 | Platform: Linux ---------------------------------+------------------------------------------ Changes (by kosmikus): * status: new => closed * resolution: => fixed Comment: This should be fixed in cabal-install-0.14, although it is a hack: {{{ Mon Apr 16 14:29:03 CEST 2012 Andres Loeh <andres(a)well-typed.com> * handling the "optimization" option properly in config file }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/368#comment:6> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #939: Update cabal-install bootstrap.sh
by Hackage 16 Apr '12

16 Apr '12

#939: Update cabal-install bootstrap.sh ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: Severity: normal | Keywords: Difficulty: normal | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Update package versions in cabal-install bootstrap.sh. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/939> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #906: cabal install cabal-install-0.10.2 fails due to dependencies
by Hackage 16 Apr '12

16 Apr '12

#906: cabal install cabal-install-0.10.2 fails due to dependencies ---------------------------------+------------------------------------------ Reporter: AndreasVoellmy | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ cabal install cabal-install-0.10.2 fails for me. The problem is that it depends on unix < 2.5 and versions of unix before 2.5 depend on base < 4.4. But base 4.4 is selected very early on in the cabal install. Later versions of unix (i.e. 2.5.0.0) work with base < 4.5, so it seems like this issue could be fixed by releasing a new version of cabal-install that works with unix 2.5. Here is the output from cabal install cabal-install-0.10.2 -v3 --dry-run: {{{ searching for ghc in path. found ghc at /usr/local/bin/ghc ("/usr/local/bin/ghc",["--numeric-version"]) /usr/local/bin/ghc is version 7.2.1 looking for package tool: ghc-pkg near compiler in /usr/local/bin found package tool in /usr/local/bin/ghc-pkg ("/usr/local/bin/ghc-pkg",["--version"]) /usr/local/bin/ghc-pkg is version 7.2.1 ("/usr/local/bin/ghc",["--supported-languages"]) Reading installed packages... ("/usr/local/bin/ghc-pkg",["dump","--global","-v2"]) ("/usr/local/bin/ghc-pkg",["dump","--user","-v2"]) ("/usr/local/bin/ghc",["--print-libdir"]) Reading available packages... Resolving dependencies... selecting cabal-install-0.10.2 (hackage) and discarding Cabal-1.1.6, 1.2.1, 1.2.2.0, 1.2.3.0, 1.2.4.0, 1.4.0.0, 1.4.0.1, 1.4.0.2, 1.6.0.1, 1.6.0.2, 1.6.0.3, 1.8.0.2, 1.8.0.4, 1.8.0.6, 1.10.0.0, 1.12.0, HTTP-3000.0.0, 3001.0.0, 3001.0.1, 3001.0.2, 3001.0.3, 3001.0.4, 3001.1.3, 3001.1.4, 3001.1.5, 4000.0.0, 4000.0.1, pretty-1.1.0.0, process-1.1.0.0, time-1.0, 1.3, unix-2.5.0.0, zlib-0.2 and 0.3 selecting base-4.4.0.0 (installed) selecting ffi-1.0 (installed) selecting ghc-prim-0.2.0.0 (installed) selecting integer-gmp-0.3.0.0 (installed) selecting rts-1.0 (installed) selecting random-1.0.1.0 (installed or hackage) and discarding random-1.0.0.0, 1.0.0.1, 1.0.0.2 and 1.0.0.3 selecting time-1.2.0.5 (installed or hackage) and discarding time-1.1.2.0, 1.1.2.1, 1.1.2.2, 1.1.2.3, 1.1.2.4, 1.1.3, 1.1.4, 1.2, 1.2.0.1, 1.2.0.2, 1.2.0.3 and 1.2.0.4 selecting zlib-0.5.3.1 (hackage) and discarding zlib-0.4, 0.4.0.1, 0.4.0.2, 0.4.0.3, 0.4.0.4, 0.5.0.0 and 0.5.2.0 selecting HTTP-4000.1.2 (hackage) and discarding HTTP-4000.0.2, 4000.0.3, 4000.0.4, 4000.0.5, 4000.0.6, 4000.0.7, 4000.0.8, 4000.0.9, 4000.0.10, 4000.1.0 and 4000.1.1 selecting network-2.3.0.5 (hackage) and discarding 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, 2.3, 2.3.0.1, 2.3.0.2, 2.3.0.3 and 2.3.0.4 selecting parsec-3.1.1 (hackage) and discarding parsec-2.0, 2.1.0.0, 2.1.0.1, 3.0.0, 3.0.1 and 3.1.0 selecting bytestring-0.9.2.0 (installed or hackage) and discarding bytestring-0.9, 0.9.0.1, 0.9.0.2, 0.9.0.3, 0.9.0.4, 0.9.1.0, 0.9.1.1, 0.9.1.2, 0.9.1.3, 0.9.1.4, 0.9.1.5, 0.9.1.6, 0.9.1.7, 0.9.1.8, 0.9.1.9 and 0.9.1.10 selecting mtl-2.0.1.0 (installed or hackage) and discarding mtl-1.0, 1.1.0.0, 1.1.0.1, 1.1.0.2, 1.1.1.0, 1.1.1.1, 2.0.0.0, 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 and 0.1.4.0 selecting transformers-0.2.2.0 (installed or hackage) and discarding transformers-0.2.0.0 and 0.2.1.0 selecting Cabal-1.10.2.0 (hackage) and discarding Cabal-1.10.1.0 selecting process-1.0.1.5 (hackage) and discarding filepath-1.0, process-1.0.0.0, 1.0.1.1, 1.0.1.2, 1.0.1.3 and 1.0.1.4 selecting pretty-1.0.1.2 (hackage) and discarding pretty-1.0.0.0, 1.0.1.0 and 1.0.1.1 selecting directory-1.1.0.1 (installed or hackage) and discarding directory-1.0.0.0, 1.0.0.3, 1.0.1.0, 1.0.1.1, 1.0.1.2 and 1.1.0.0 selecting cabal: cannot configure unix-2.4.2.0. It requires base >=4.2 && <4.4 For the dependency on base >=4.2 && <4.4 there are these packages: base-4.2.0.0, base-4.2.0.1, base-4.2.0.2, base-4.3.0.0 and base-4.3.1.0. However none of them are available. base-4.2.0.0 was excluded because base-4.4.0.0 was selected instead base-4.2.0.0 was excluded because of the top level dependency base -any base-4.2.0.1 was excluded because base-4.4.0.0 was selected instead base-4.2.0.1 was excluded because of the top level dependency base -any base-4.2.0.2 was excluded because base-4.4.0.0 was selected instead base-4.2.0.2 was excluded because of the top level dependency base -any base-4.3.0.0 was excluded because base-4.4.0.0 was selected instead base-4.3.0.0 was excluded because of the top level dependency base -any base-4.3.1.0 was excluded because base-4.4.0.0 was selected instead base-4.3.1.0 was excluded because of the top level dependency base -any }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/906> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #864: worldfile written with incorrect case
by Hackage 16 Apr '12

16 Apr '12

#864: worldfile written with incorrect case ---------------------------------+------------------------------------------ Reporter: benmachine | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ If I issue a command like `cabal install bindings-dsl`, cabal will happily install `bindings-DSL` and write `bindings-dsl` to the world file. Then when I `cabal install --dry-run world`, I get {{{ Warning: The following 'world' packages will be ignored because they refer to packages that cannot be found: bindings-dsl }}} This seems to be because of the discrepancies in capitalisation -- the world file is case-sensitive, the install command isn't. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/864> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #905: Test-suite extra-libraries conditional
by Hackage 16 Apr '12

16 Apr '12

#905: Test-suite extra-libraries conditional ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.6 Severity: normal | Keywords: test-suite Difficulty: unknown | Ghcversion: Platform: Mac OS | ---------------------------------+------------------------------------------ 1) If a library specified in an "extra-libraries" line in a test-suite is not present, cabal will not build the package even when tests are disabled. 2) Conditionals are not allowed in a test-suite section. The first issue should ideally be fixed, but at least resolving the second would allow me to fix my current issue (I need a framework on mac, and an extra-libraries elsewhere). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/905> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

Re: [Hackage] #380: Ability to blacklist packages that are on hackage
by Hackage 16 Apr '12

16 Apr '12

#380: Ability to blacklist packages that are on hackage ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: cabal-install-0.16 Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: hard (< 1 day) | Ghcversion: 6.8.3 Platform: | ---------------------------------+------------------------------------------ Changes (by kosmikus): * milestone: cabal-install-0.14 => cabal-install-0.16 Comment: The following works now: * Constraints and preferences can be added to the global config file. * Each `constraint:` or `preference:` line can specify only a single constraint, but several such lines can occur. * Config file constraints will be handled like command-line constraints by the solver. This can be used to specify a personal blacklist. However, the following remains to be done: * Make it easier to work with several config files. Currently, we can reset the config file, but not use a stack of config files. `cabal-dev` allows the latter. * Distinguish config file constraints from command-line constraints in error messages. * Allow a single config file line to contain a list of constraints. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/380#comment:4> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #930: cabal test is dropping --test-option flags
by Hackage 16 Apr '12

16 Apr '12

#930: cabal test is dropping --test-option flags ----------------------------+----------------------------------------------- Reporter: tibbe | Owner: ttuegel Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.10.2.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Adding two `--test-option` flags doesn't work correctly. For example, this {{{ cabal test --test-option=--plain }}} causes cabal to (correctly) pass the `--plain` flag to the underlying test-framework binary. However, this {{{ cabal test --test-option=--plain --test-option=--jxml=dist/unit-tests.xml }}} drops it on the ground. Some debug output {{{ cabal test --test-option=--plain --test-option=--jxml=dist/unit-tests.xml -v3 Using external setup method with build-type Custom Creating ./dist/setup (and its parents) Using Cabal library version 1.14.0 Using ./Setup.hs as setup script. ./dist/setup/setup test --verbose=3 --test-options=--jxml=dist/unit- tests.xml --test-option=--jxml=dist/unit-tests.xml }}} There looks like there's an extra newline in the `./dist/setup/setup` invocation, perhaps that's the issue? The problem can be reproduced on Cabal's own test suite. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/930> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #929: cabal test -v3 should output command line used to run test binary
by Hackage 16 Apr '12

16 Apr '12

#929: cabal test -v3 should output command line used to run test binary ---------------------------------+------------------------------------------ Reporter: tibbe | Owner: ttuegel Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.10.2.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ I was trying to debug a `cabal test` issue today and in doing that I needed to understand how cabal invoked the test binary (e.g. a `stdio- exitcode` test suite.) However, passing `-v3` to `cabal test` doesn't cause it to be printed. Proposed fix: Have `cabal test -v3` output all commands being run. Model it after `-v3` for e.g. `build` or `install`. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/929> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3