May 2012 - cabal-devel

darcs patch: Add a new checkout Command (and 1 more)
by Joachim Breitner 20 Jul '13

20 Jul '13

Hi, the small feature implemented by the attached patches could make it more convenient for people to quickly and easily contribute to hackage packages. Do you want me to open a ticket for this or can you appl yit right away? Thanks, Joachim 2 patches for repository http://darcs.haskell.org/cabal-install: Sun Nov 7 12:35:32 CET 2010 Joachim Breitner <mail(a)joachim-breitner.de> * Add a new checkout Command Given a package name, this uses the SourceRepo field of the newest versionf of that pacakge to figure out the repository location and calls the right VCS invocation. Sun Nov 7 12:43:35 CET 2010 Joachim Breitner <mail(a)joachim-breitner.de> * Add a --dry-run flag to cabal checkout

2 3

hackage-server: index format
by Antoine Latter 20 Dec '12

20 Dec '12

Hi folks, The index tar-ball on Hackage has an odd naming convention. Package descriptions are given paths of the form: ./$pkg/$version/$pkg.cabal including the leading "./". I'm guessing that this is done as a method of distinguishing non-package meta-data. Is this a convention we need to preserve? Thanks, Antoine

6 12

[Hackage] #935: implementation of Distribution.Version.invertVersionRange
by Hackage 26 Oct '12

26 Oct '12

#935: implementation of Distribution.Version.invertVersionRange ----------------------------------+----------------------------------------- Reporter: dsf | Owner: Type: enhancement | Status: new Priority: low | Milestone: Component: Cabal library | Version: 1.10.2.0 Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: 7.4.1 Platform: | ----------------------------------+----------------------------------------- Attached is an implementation of a function to return the complement of a VersionRange. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/935> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #777: cabal install {hledger, others} ExitFailure 11
by Hackage 14 Aug '12

14 Aug '12

#777: cabal install {hledger, others} ExitFailure 11 ---------------------------------+------------------------------------------ Reporter: philips | Owner: Type: defect | Status: new Priority: normal | Milestone: cabal-install-0.8 Component: cabal-install tool | Version: 1.8.0.2 Severity: normal | Keywords: ExitFailure Difficulty: unknown | Ghcversion: Platform: Linux | ---------------------------------+------------------------------------------ I am getting ExitFailure 11 when trying to install hledger on Debian and openSUSE. I reported this to the hledger author, Simon, and he said he is experiencing this on his machines too and for other packages, not just hledger. Log file attached. Summary below: {{{ ledger:~/ $ cabal install -v3 hledger Lots of debug output (see attached)... hledger-0.13 failed during the configure step. The exception was: ExitFailure 11 ledger:~/ $ cabal --version cabal-install version 0.8.2 using version 1.8.0.2 of the Cabal library ledger:~/ $ ghc --version The Glorious Glasgow Haskell Compilation System, version 6.12.1 }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/777> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 11

cabal-install-ghc74 fixes
by xemdetia . 28 May '12

28 May '12

Greetings, I was doing a clean, from scratch install of ghc-7.4.1 and was trying to get cabal-install to work, and since I am new I tried to do all the bootstrap.sh stuff myself. After failing and starting over I saw this package (cabal-install-ghc74) and gave it a shot. Unfortunately with a fresh install there are three things wrong. 1. It was not checking for the right .cabal file. 2. network-2.3.0.5 has the restriction of base <4.5, ghc-7.4.1 ships with base 4.5 so bootstrap.sh fails. Using the latest version (2.3.0.13 at time of writing) solved that issue. 3. HTTP-4000.1.2 has the same restriction as the previous (base <4.5). I just used HTTP-4000.2.3 instead. This builds cabal correctly on my x86_64 Debian stable box. I don't know how I am supposed to do this, but I just attached a diff if that helps. Thanks === BEGIN DIFF === 50c50 < NETWORK_VER="2.3.0.5"; NETWORK_VER_REGEXP="2\." # == 2.* --- > NETWORK_VER="2.3.0.13"; NETWORK_VER_REGEXP="2\." # == 2.* 54c54 < HTTP_VER="4000.1.2"; HTTP_VER_REGEXP="4000\.[01]\." # == 4000.0.* || 4000.1.* --- > HTTP_VER="4000.2.3"; HTTP_VER_REGEXP="4000\.2\." # == 4000.2.* 69c69 < grep "cabal-install-ghc72" ./cabal-install-ghc72.cabal > /dev/null 2>&1 \ --- > grep "cabal-install-ghc74" ./cabal-install-ghc74.cabal > /dev/null 2>&1 \ === END DIFF === PS: There are a lot of emacs temp files (~) in this tarball as well. I don't know what the policy is on removing them or if anyone cares.

3 2

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