June 2011 - cabal-devel

[Hackage] #831: Strange message
by Hackage 05 Jan '12

05 Jan '12

#831: Strange message ---------------------------------+------------------------------------------ Reporter: Ptharien's Flame | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.10.1.0 Severity: normal | Keywords: base, cabal, install, ghc, version, no Difficulty: unknown | Ghcversion: Platform: Mac OS | ---------------------------------+------------------------------------------ I just entered this at my terminal prompt: {{{ sudo cabal install -g ObjectIO }}} And its only output was: {{{ Resolving dependencies... cabal: There is no installed version of base }}} This problem occurs with any package, not just ObjectIO. {{{ sudo cabal --version }}} returns {{{ cabal-install version 0.10.2 using version 1.10.1.0 of the Cabal library }}} I am working on a 2011 i7 quad-core MacBook Pro running Mac OS X 10.6.7 (Snow Leopard) and using the Haskell Platform 2011.2.0 (March 2011) with a separately pre-built x86_64 binary GHC 7.0.3. Please help. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/831> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 6

[Hackage] #832: Cabal aggregates dependencies for executables
by Hackage 05 Jan '12

05 Jan '12

#832: Cabal aggregates dependencies for executables ----------------------------+----------------------------------------------- Reporter: juhp | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.10.1.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- I discovered over the weekend while trying to subpackage bluetile, that Cabal seems to aggregate dependencies of executables. For example http://hackage.haskell.org/packages/archive/bluetile/0.5.3/bluetile.cabal generates several executables. Some depend on gtk, others not, and yet Cabal passes "--package-id gtk-..." to "ghc --make" for all of them and as a result the bluetile program (which doesn't depend on gtk) gets linked against gtk (and glade), leading to executable/dependency bloat. Only the executables that are listed with explicit build-depends on gtk should be linked against the gtk package, etc. I will try to dig into the source later and maybe even cook up a patch if I can: a code pointer would be appreciated. I assume Cabal is currently just accumulating all the build-depends which is sub-optimal. (Arguably ghc shouldn't link unused libraries to executables either, though I think that is pretty standard compiler behaviour. But I can file a bug against ghc too if appropriate.) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/832> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #830: Use wide Windows APIs in Cabal
by Hackage 05 Jan '12

05 Jan '12

#830: Use wide Windows APIs in Cabal -----------------------------+---------------------------------------------- Reporter: batterseapower | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | -----------------------------+---------------------------------------------- As part of my work on GHC's Unicode support (http://hackage.haskell.org/trac/ghc/wiki/Status/Encoding-Tickets) I identified some potential Unicode problems in Cabal install. The attached patch resolves them: 1. Use wide (UTF-16) APIs to retrieve file paths 2. Use withFilePath (from base) when marshalling a file path, as this will do the Right Thing when my changes are committed, though it is functionally equivalent to withCAString right now. Patch attached. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/830> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[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] #836: Provide the state of Cabal flags in an auto-generated module
by Hackage 05 Jan '12

05 Jan '12

#836: Provide the state of Cabal flags in an auto-generated module ----------------------------+----------------------------------------------- Reporter: lemming | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.10.0.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- I would like to query the state of cabal flags at configure time without CPP hackery. I would prefer to import an autogenerated module, that contains Bool variables with the names of the Cabal flags, just like the Paths module contains the paths of installed data files. For instance if my Cabal file contains {{{ Flag buildExamples description: Build example executables default: False Flag buildTests description: Build test suite default: True Flag debug description: Compile with debug messages default: False }}} and I install the package by {{{ $ cabal install -fdebug }}} then the autogenerated module shall contain {{{ module Flags_mypkg where -- | Build example executables buildExamples :: Bool buildExamples = False -- | Build test suite buildTests :: Bool buildTests = True -- | Compile with debug messages debug :: Bool debug = True }}} Maybe this feature would also solve #778. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/836> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[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] #845: [patch] Distribution/Compat/TempFile.hs: add dash separator before pid for createTempDirectory and openBinaryTempFile
by Hackage 05 Jan '12

05 Jan '12

#845: [patch] Distribution/Compat/TempFile.hs: add dash separator before pid for createTempDirectory and openBinaryTempFile ----------------------------+----------------------------------------------- Reporter: juhp | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- This patch just adds a '-' separator before pid when creating a temp directory or binary-file. So we get /tmp/mypkg-version/mypkg-version-pid/ instead of /tmp/mypkg-version/mypkg-versionpid/, which makes it much easier to pick out the version number. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/845> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[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