March 2012 - cabal-devel

[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

[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

[Hackage] #922: “lexical error (UTF-8 decoding error)” in WIndows 7
by Hackage 16 Apr '12

16 Apr '12

#922: “lexical error (UTF-8 decoding error)” in WIndows 7 ---------------------------------+------------------------------------------ Reporter: hamukazu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: minor | Keywords: UTF-8 Difficulty: unknown | Ghcversion: Platform: Windows | ---------------------------------+------------------------------------------ ==== Symptom ==== When I type > cabal install cabal it fails with the following error: > Distribution\Compat\Exception.hs:0:4: lexical error (UTF-8 decoding error) ==== Environment ==== It happens with 64 bit version of Windows 7. It came to occur after I failed to install HXT. (I am not sure it is related.) ==== Workaround ==== By setting > set LANG=C in command line, cabal comes to work. I regard this is just a workaround and this issue should be reported as a bug. ==== Related links ==== http://stackoverflow.com/questions/9371438/cabal-install-complains-built- in04-lexical-error-utf-8-decoding-error/9533205#9533205 http://trac.haskell.org/network/ticket/43 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/922> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[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