February 2011 - cabal-devel

[Hackage] #803: cabal test after cabal configure --enable-tests without cabal build creates obscure output
by Hackage 05 Jan '12

05 Jan '12

#803: cabal test after cabal configure --enable-tests without cabal build creates obscure output ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- It wasn't obvious to me that cabal build would be required before cabal test. Can cabal test automatically run cabal build? Otherwise a message should be shown telling the user to run cabal build. Here is an example output {{{ >>> Test suite runtests: RUNNING... >>> Test suite runtests: FAIL >>> Test suite logged to: dist/test/persistent-0.4.0.1-runtests.log >>> Test suite runtests: RUNNING... >>> Test suite runtests: FAIL >>> Test suite logged to: dist/test/persistent-0.4.0.1-runtests.log Test suite runtests: FAIL Test suite logged to: dist/test/persistent-0.4.0.1-runtests.log 0 of 1 test suites (0 of 1 test cases) passed. }}} The log is exactly the same as the output -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/803> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #766: hackage build logs gone missing?
by Hackage 05 Jan '12

05 Jan '12

#766: hackage build logs gone missing? --------------------------------+------------------------------------------- Reporter: claus | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | --------------------------------+------------------------------------------- It seems that build logs are no longer linked from package pages (used to be linked from the `built on` entries, iirc), such as: http://hackage.haskell.org/package/haddock Also, the `latest/` directory has `doc/`, but not `logs/`, while the archived versioned directory has both: http://hackage.haskell.org/packages/archive/haddock/latest/ http://hackage.haskell.org/packages/archive/haddock/2.8.1/ And, since I've more than once confused myself with that directory structure (`package` singular, but `packages/archive` plural? why the different prefix, where a version number postfix should be enough? why both `http://hackage.haskell.org/package/haddock-2.8.0` and `http://hackage.haskell.org/packages/archive/haddock/2.8.0/`?), could that be simplified (or, at least, a link be provided from the `package`-entry to the shadow-hierarchy `packages/archive`)? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/766> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #791: Large libraries not installable on OS X
by Hackage 05 Jan '12

05 Jan '12

#791: Large libraries not installable on OS X -----------------------------+---------------------------------------------- Reporter: batterseapower | Owner: Type: defect | Status: new Priority: high | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: Mac OS | -----------------------------+---------------------------------------------- For example: {{{ cabal unpack highlighting-kate-0.2.8.1 cd highlighting-kate-0.2.8.1 ghc --make Setup.hs ./Setup configure ./Setup build }}} This fails: {{{ ld: scattered reloc r_address too large for inferred architecture i386 }}} The underlying reason is that Cabal is trying to create an object file for use with GHCi, but that is not possible (see http://hackage.haskell.org/trac/ghc/ticket/3260) Cabal's GHC.hs should not use combineObjectFiles on with GHC >= 7 and OS X. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/791> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

4 15

[Hackage] #802: copy command should not overwrite files
by Hackage 05 Jan '12

05 Jan '12

#802: copy command should not overwrite files ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- see http://hackage.haskell.org/trac/ghc/ticket/4955 Cabal can inadvertently get users into situations where they have registered packages that do not match their package registration information. Consider the package darcs and darcs-fastconvert which depends on the darcs library. If one installs darcs, then later in the darcs build tree do a `cabal copy` then it will overwrite the library .hi files but not update the library registration. This will mean that subsequent builds of darcs-fastconvert will fail with very confusing error messages (see the ghc ticket above). A similar thing could happen with inplace registrations. The suggestion to avoid this problem is for `cabal copy` to refuse to overwrite .hi files (executables are fine). This is also partly related to #645 because some people are using `cabal copy` to avoid having to use `cabal install` which spends too long reconfiguring and checking nothing needs building before actually installing. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/802> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #801: MissingH won't upgrade
by Hackage 05 Jan '12

05 Jan '12

#801: MissingH won't upgrade ----------------------------+----------------------------------------------- Reporter: mcandre | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: 6.12.3 Platform: Mac OS | ----------------------------+----------------------------------------------- Specs: * cabal-install 0.8.2 * Cabal 1.8.0.6 * GHC 6.12.3 * Mac OS X 10.6.6 * MacBook Pro 5,1 {{{ $ cabal upgrade missingh Resolving dependencies... Configuring regex-base-0.93.2... Preprocessing library regex-base-0.93.2... Building regex-base-0.93.2... [1 of 4] Compiling Text.Regex.Base.RegexLike ( Text/Regex/Base/RegexLike.hs, dist/build/Text/Regex/Base/RegexLike.o ) [2 of 4] Compiling Text.Regex.Base.Context ( Text/Regex/Base/Context.hs, dist/build/Text/Regex/Base/Context.o ) [3 of 4] Compiling Text.Regex.Base ( Text/Regex/Base.hs, dist/build/Text/Regex/Base.o ) [4 of 4] Compiling Text.Regex.Base.Impl ( Text/Regex/Base/Impl.hs, dist/build/Text/Regex/Base/Impl.o ) Registering regex-base-0.93.2... Installing library in /Users/andrew/.cabal/lib/regex- base-0.93.2/ghc-6.12.3 Registering regex-base-0.93.2... Configuring regex-posix-0.94.4... Preprocessing library regex-posix-0.94.4... Building regex-posix-0.94.4... [1 of 6] Compiling Text.Regex.Posix.Wrap ( dist/build/Text/Regex/Posix/Wrap.hs, dist/build/Text/Regex/Posix/Wrap.o ) [2 of 6] Compiling Text.Regex.Posix.String ( Text/Regex/Posix/String.hs, dist/build/Text/Regex/Posix/String.o ) [3 of 6] Compiling Text.Regex.Posix.Sequence ( Text/Regex/Posix/Sequence.hs, dist/build/Text/Regex/Posix/Sequence.o ) [4 of 6] Compiling Text.Regex.Posix.ByteString ( Text/Regex/Posix/ByteString.hs, dist/build/Text/Regex/Posix/ByteString.o ) [5 of 6] Compiling Text.Regex.Posix.ByteString.Lazy ( Text/Regex/Posix/ByteString/Lazy.hs, dist/build/Text/Regex/Posix/ByteString/Lazy.o ) [6 of 6] Compiling Text.Regex.Posix ( Text/Regex/Posix.hs, dist/build/Text/Regex/Posix.o ) Registering regex-posix-0.94.4... Installing library in /Users/andrew/.cabal/lib/regex- posix-0.94.4/ghc-6.12.3 Registering regex-posix-0.94.4... Configuring regex-compat-0.93.1... Preprocessing library regex-compat-0.93.1... Building regex-compat-0.93.1... [1 of 1] Compiling Text.Regex ( Text/Regex.hs, dist/build/Text/Regex.o ) Registering regex-compat-0.93.1... Installing library in /Users/andrew/.cabal/lib/regex- compat-0.93.1/ghc-6.12.3 Registering regex-compat-0.93.1... Configuring MissingH-1.1.0.3... Preprocessing library MissingH-1.1.0.3... Preprocessing executables for MissingH-1.1.0.3... Building MissingH-1.1.0.3... [ 1 of 47] Compiling System.Console.GetOpt.Utils ( src/System/Console/GetOpt/Utils.hs, dist/build/System/Console/GetOpt/Utils.o ) [ 2 of 47] Compiling System.Debian ( src/System/Debian.hs, dist/build/System/Debian.o ) [ 3 of 47] Compiling System.IO.WindowsCompat ( src/System/IO/WindowsCompat.hs, dist/build/System/IO/WindowsCompat.o ) [ 4 of 47] Compiling System.Posix.Consts ( src/System/Posix/Consts.hs, dist/build/System/Posix/Consts.o ) [ 5 of 47] Compiling System.IO.StatCompat ( src/System/IO/StatCompat.hs, dist/build/System/IO/StatCompat.o ) [ 6 of 47] Compiling System.IO.PlafCompat ( src/System/IO/PlafCompat.hs, dist/build/System/IO/PlafCompat.o ) [ 7 of 47] Compiling Data.Compression.Inflate ( src/Data/Compression/Inflate.hs, dist/build/Data/Compression/Inflate.o ) [ 8 of 47] Compiling Data.Hash.MD5.Zord64_HARD ( src/Data/Hash/MD5/Zord64_HARD.lhs, dist/build/Data/Hash/MD5/Zord64_HARD.o ) src/Data/Hash/MD5/Zord64_HARD.lhs:4:2: Bad interface file: /Users/andrew/.cabal/lib/haskell98-1.1.0.0/ghc-6.12.3/Word.hi Something is amiss; requested module haskell98:Word differs from name found in the interface file haskell98-1.1.0.0:Word cabal: Error: some packages failed to install: MissingH-1.1.0.3 failed during the building phase. The exception was: ExitFailure 1 }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/801> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #800: Cabal won't update
by Hackage 05 Jan '12

05 Jan '12

#800: Cabal won't update ----------------------------+----------------------------------------------- Reporter: mcandre | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Specs: * cabal-install 0.8.2 * Cabal 1.8.0.6 * GHC 6.12.3 * Mac OS X 10.6.6 * !MacBook Pro 5,1 Trace: {{{ $ cabal update Downloading the latest package list from hackage.haskell.org Warning: The package list for 'hackage.haskell.org' is 20 days old. Run 'cabal update' to get the latest list of available packages. }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/800> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #806: cabal test should not concatenate test logs by default
by Hackage 05 Jan '12

05 Jan '12

#806: cabal test should not concatenate test logs by default ----------------------------+----------------------------------------------- Reporter: tibbe | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.10.1.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- At the moment `cabal test` concatenates the human readable test logs by default. I don't find this very useful and makes the logs look like there's a bug in Cabal. I suggest that we don't append the logs by default (if ever). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/806> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 5

[Hackage] #787: --test-option should support template argument
by Hackage 05 Jan '12

05 Jan '12

#787: --test-option should support template argument ----------------------------------+----------------------------------------- Reporter: tibbe | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: Platform: | ----------------------------------+----------------------------------------- The test-framework package can optionally output JUnit XML, an XML flavor understood by many continuous build systems, if you pass it the `--jxml` flag. Using that flag, one can get `cabal test` to output JUnit XML: {{{ cabal configure --enable-tests cabal build cabal test --test-option=--jxml=dist/test/junit.xml }}} However, the `--test-option` flag doesn't allow the user to pass different flags to different test executables so each test executable will override the output of the previous. If the `--test-option` flag took a name template argument, supporting a `$test-suite` placeholder, you could generate one JUnit XML file per test suite: {{{ cabal configure --enable-tests cabal build cabal test --test-option=--jxml=dist/test/$test-suite.xml }}} The detailed test interface might support this in some nicer way, but this is a cheap way to have Cabal cooperate better with other test runners. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/787> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 5

[Hackage] #779: Create tarball of all Hoogle input files
by Hackage 05 Jan '12

05 Jan '12

#779: Create tarball of all Hoogle input files --------------------------------+------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: HackageDB Component: hackageDB website | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | --------------------------------+------------------------------------------- For many packages on Hackage there is a corresponding Hoogle input file, for example: http://hackage.haskell.org/packages/archive/cmdargs/0.6.5/doc/html/cmdargs.… To generate Hoogle databases for every package on Hackage I have a script that downloads the documentation for every package, then puts it in a tarball and uploads it back to http://haskell.org/hoogle/hackage- haddock.tar.gz There are three disadvantages to the current process. It's quite a lot of connections to Hackage to download every single file, it takes quite a lot of time to download them individually (about 50 minutes using wget serially), and the tarball on Hoogle is often (always?) out of date. Would it be possible for Hackage to supply a tarball of all the Hoogle input files? -- Neil Mitchell (Hoogle author) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/779> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 8

[Hackage] #792: sdist doesn't not include source files from test-suite stanzas
by Hackage 05 Jan '12

05 Jan '12

#792: sdist doesn't not include source files from test-suite stanzas ----------------------------+----------------------------------------------- Reporter: tibbe | Owner: ttuegel Type: defect | Status: new Priority: normal | Milestone: Cabal-1.10 Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- `cabal sdist` doesn't include the source files from test-suite stanzas when generating the tarball. This leads to Hackage's QA checks rejecting the package. Steps to reproduce: 1. Create a Cabal package with a test-suite stanza (and set `hs-source- dirs` to e.g. `tests`). 2. Run `cabal sdist` 3. Unpack the tarball and look at the content. Thomas, could you please take a look? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/792> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 8