- cabal-devel - Haskell.org

Trac import is complete
by Bryan O'Sullivan 28 May '12

28 May '12

You can now find open issues here: https://github.com/haskell/cabal/issues?state=open Duncan or Andres, could one of you please chmod -w the files owned by Trac, and add a note pointing people to github for filing bugs?

5 11

Re: [Hackage] #282: profiling versions of libraries not managed well
by Hackage 23 May '12

23 May '12

#282: profiling versions of libraries not managed well ---------------------------------+------------------------------------------ Reporter: SamB | Owner: Type: defect | Status: new Priority: normal | Milestone: cabal-install-0.16 Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Keywords: profiling Difficulty: hard (< 1 day) | Ghcversion: 6.8.2 Platform: | ---------------------------------+------------------------------------------ Changes (by rrnewton): * cc: rrnewton@… (added) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/282#comment:11> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #955: Incorrect hpcdir during cabal test for testsuites w/ library coverage enabled
by Hackage 21 May '12

21 May '12

#955: Incorrect hpcdir during cabal test for testsuites w/ library coverage enabled ----------------------------+----------------------------------------------- Reporter: albertfong | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.14.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: 7.4.1 Platform: Windows | ----------------------------+----------------------------------------------- When running "cabal test" on a project configured with "cabal configure --enable-tests --enable-library-coverage", the hpcdir for test suites points to dist/hpc/mix/PackageName, not dist/hpc/mix/TestSuiteName. This results in an aborted run: {{{ PS C:\Users\Albert Fong\Repositories\working\projects\Simple> runhaskell.exe .\Setup.hs test -v Running 3 test suites... Test suite Tests3: RUNNING... Test suite Tests3: PASS Test suite logged to: dist\test\Simple-0.1.0.0-Tests3.log C:\Users\Albert Fong\Repositories\working\devenv\tools\ghc-7.4.1\bin\hpc.exe markup dist\hpc\tix\Tests3\Tests3.tix --hpc dir=dist\hpc\mix\Simple-0.1.0.0 --destdir=dist\hpc\html\Tests3 --exclude=Main hpc.exe: can not find Library in ["./dist\\hpc\\mix\\Simple-0.1.0.0"] PS C:\Users\Albert Fong\Repositories\working\projects\Simple> }}} Note the hpcdir during build ("-fhpc -hpcdir dist\hpc\mix\Tests3") is not what's used during test ("--hpcdir=dist\hpc\mix\Simple-0.1.0.0") {{{ Preprocessing test suite 'Tests3' for Simple-0.1.0.0... Building test suite Tests3... creating dist\build\Tests3 creating dist\build\Tests3\Tests3-tmp C:\Users\Albert Fong\Repositories\working\devenv\tools\ghc-7.4.1\bin\ghc.exe --make -o dist\build\Tests3\Tests3.exe -hid e-all-packages -fbuilding-cabal-package -no-user-package-conf -package- conf dist\package.conf.inplace -i -idist\build\Te sts3\Tests3-tmp -i. -idist\build\autogen -Idist\build\autogen -Idist\build\Tests3\Tests3-tmp -optP-include -optPdist\bui ld\autogen\cabal_macros.h -odir dist\build\Tests3\Tests3-tmp -hidir dist\build\Tests3\Tests3-tmp -stubdir dist\build\Tes ts3\Tests3-tmp -package-id base-4.5.0.0-597748f6f53a7442bcae283373264bb6 -O -fhpc -hpcdir dist\hpc\mix\Tests3 -XHaskell9 8 .\Tests.hs }}} Here's the layout of the dist/hpc folder: {{{ dist\hpc\mix dist\hpc\mix\Simple-0.1.0.0 dist\hpc\mix\Simple-0.1.0.0\Simple-0.1.0.0 dist\hpc\mix\Simple-0.1.0.0\Simple-0.1.0.0\Library.mix dist\hpc\mix\Tests1 dist\hpc\mix\Tests1\Library.mix dist\hpc\mix\Tests1\Main.mix dist\hpc\mix\Tests2 dist\hpc\mix\Tests2\Library.mix dist\hpc\mix\Tests2\Main.mix dist\hpc\mix\Tests3 dist\hpc\mix\Tests3\Library.mix dist\hpc\mix\Tests3\Main.mix dist\hpc\tix dist\hpc\tix\Tests3 dist\hpc\tix\Tests3\Tests3.tix }}} The double nested "Simple-0.1.0.0" under mix may be another issue as well. A cabal project used to repro this issue is attached. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/955> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #954: setup haddock fails for packages without modules
by Hackage 20 May '12

20 May '12

#954: setup haddock fails for packages without modules ----------------------------+----------------------------------------------- Reporter: nomeata | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.14.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- http://hackage.haskell.org/package/diagrams-0.5 is a meta-package, i.e. only depends on other packages. Running setup haddock fails: {{{ $ ./Setup haddock --hyperlink-source Running Haddock for diagrams-0.5... Running hscolour for diagrams-0.5... Preprocessing library diagrams-0.5... Warning: The documentation for the following packages are not installed. No links will be generated to these packages: rts-1.0 Preprocessing library diagrams-0.5... haddock: No input file(s). }}} Not a big deal, but still a corner-case that could be fixed. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/954> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Heads up: importing the Cabal issue tracker to github next week
by Bryan O'Sullivan 16 May '12

16 May '12

I am planning on doing this early next week, probably in two phases. As part of the import process, github will generate a *lot* of notification emails. I'm afraid there is nothing I can do to stem the tide, as github does not provide a mechanism to suppress these. If you have a github account, please brace yourself.

1 0

[Hackage] #953: Alex-generated Lexer isn't found when building test-suite
by Hackage 15 May '12

15 May '12

#953: Alex-generated Lexer isn't found when building test-suite ----------------------------+----------------------------------------------- Reporter: owst | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.14.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- I'd like to use my Alex-generated lexer in my test-suite. I've tried adding other-modules/build-tools to my test-suite section, but upon building the Lexer module isn't found. I've got no problems using the lexer within my normal executable. Should I be able to use my Lexer in the test-suite? I'll attach a fairly minimal example, the Main module and the TestSuite module both use the Lexer, Main will compile, TestSuite won't: $ cabal configure --enable-tests $ cabal build [... blurb] Preprocessing test suite 'tests' for test-suite-with-alex-0.0... tests/TestSuite.hs:7:8: Could not find module `MyLexer' Perhaps you meant Lexer (needs flag -package ghc-7.4.1) Use -v to see a list of the files searched for. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/953> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #951: Incorrect error messages for non-existing dependencies
by Hackage 15 May '12

15 May '12

#951: Incorrect error messages for non-existing dependencies ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.14.0 Severity: normal | Keywords: message solver Difficulty: unknown | Ghcversion: 7.4.1 Platform: Linux | ---------------------------------+------------------------------------------ When the build-depends-field contains non-existing packages, cabal-install sometimes does not report that these packages could not be found but complains about other constraints being unsolvable. The attached cabal-file contains a dependency for a non-existing package called "bogus". This is what I get: {{{ $ cabal install --only-dependencies --dry-run Resolving dependencies... cabal: Could not resolve dependencies: next goal: foo (user goal) rejecting: foo-1.0 (global constraint requires ==0.1.0.0) trying: foo-0.1.0.0 trying: heist-0.8.0 (dependency of foo-0.1.0.0) trying: transformers-0.3.0.0 (dependency of heist-0.8.0) next goal: mtl (dependency of heist-0.8.0) rejecting: mtl-2.1.1, 2.1 (conflict: heist => mtl>=2.0 && <2.1) rejecting: mtl-2.0.1.0, 2.0.0.0 (conflict: transformers==0.3.0.0, mtl => transformers==0.2.*) rejecting: mtl-1.1.1.1, 1.1.1.0, 1.1.0.2, 1.1.0.1, 1.1.0.0, 1.0 (conflict: heist => mtl>=2.0 && <2.1) }}} When removing "bogus" from the build-depends, cabal-install is able to come up with a working install plan. Used versions: {{{ $ cabal --version cabal-install version 0.14.0 using version 1.14.0 of the Cabal library }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/951> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #952: cabal-install-0.14.0 dependencies are incorrect
by Hackage 15 May '12

15 May '12

#952: cabal-install-0.14.0 dependencies are incorrect ---------------------------------+------------------------------------------ Reporter: kosmikus | Owner: kosmikus Type: defect | Status: new Priority: normal | Milestone: cabal-install-0.14.2 Component: cabal-install tool | Version: 1.14.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Apparently, we depend on transformers >= 0.2.2.0 (indirectly via mtl). Should either adapt the code to work with older versions or fix the dependency. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/952> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #950: no dyn_o generated for C files
by Hackage 11 May '12

11 May '12

#950: no dyn_o generated for C files ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Keywords: dynamic objects Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- When verifying a bug in GHC-7.5.20120510 I think I discovered a bug in Cabal-1.15.0 that is shipped with the nightly build of GHC. In the llvm-base package the C/C++ modules in the cbits directory are only compiled for the static version and the dynamic objects are not generated. This results in the compiler error: {{{ gcc: dist/build/cbits/extra.dyn_o: file not found gcc: dist/build/cbits/free.dyn_o: file not found gcc: dist/build/cbits/malloc.dyn_o: file not found gcc: dist/build/cbits/support.dyn_o: file not found }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/950> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Heads up - moving the bug tracker to github
by Bryan O'Sullivan 11 May '12

11 May '12

Hi folks - Some time next week, I am planning to import all open Cabal bugs into the github issue tracker. At that point, we should put the Trac issue tracker into read-only mode. Here's a preview of what the imported issues will look like: https://github.com/bos/test1/issues Most issue metadata is preserved, except for being able to attribute issues and their comments directly to users (github's API doesn't allow this).

1 0