October 2011 - cabal-devel

[Hackage] #854: BSD2 and ISC license
by Hackage 05 Jan '12

05 Jan '12

#854: BSD2 and ISC license ----------------------------------+----------------------------------------- Reporter: kazu-yamamoto | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: Platform: | ----------------------------------+----------------------------------------- Cabal provides BSD3 and BSD4 but not BSD2 and ISC. Please provide them. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/854> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #848: Don't prefix test output with ">>>"
by Hackage 05 Jan '12

05 Jan '12

#848: Don't prefix test output with ">>>" ----------------------------+----------------------------------------------- Reporter: tibbe | Owner: ttuegel Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- The `cabal test` output is a bit too noisy. {{{ $ /tmp/cabal-install/dist/build/cabal/cabal test --show-details=always Running 1 test suites... Test suite tests: RUNNING... >>> Test suite tests: RUNNING... >>> [] bernstein: [Failed] >>> Falsifiable with seed 8771427597089205664, after 1 tests. Reason: Falsifiable >>> text: text/strict: [OK, passed 100 tests] text/lazy: [OK, passed 100 tests] rechunk: [OK, passed 100 tests] text/rechunked: [OK, passed 100 tests] >>> >>> Properties Total >>> Passed 4 4 >>> Failed 1 1 >>> Total 5 5 >>> Test suite tests: FAIL >>> Test suite logged to: dist/test/hashable-1.1.2.0-tests.log Test suite tests: FAIL Test suite logged to: dist/test/hashable-1.1.2.0-tests.log 0 of 1 test suites (0 of 1 test cases) passed. }}} My original request was for the Cabal output (such as "Running 1 test suites...") to be prefixed by ">>>" and the test output to be kept verbatim. This is not quite what happens now as you see above. Here's my new suggestion: since Cabal normally doesn't prefix command output, we should not do so in the test output either. Just output stdio verbatim from the test and don't prefix anything with ">>>". -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/848> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #860: Package seems to depend on itself
by Hackage 05 Jan '12

05 Jan '12

#860: Package seems to depend on itself --------------------------------+------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | --------------------------------+------------------------------------------- In the list of dependencies of the package language-c-quote[0], the name of the package itself is mentioned. [0] http://hackage.haskell.org/package/language-c-quote -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/860> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 6

[Hackage] #886: when installing globally, cabal shouldn't use umask, should set mods to 755 or 644
by Hackage 05 Jan '12

05 Jan '12

#886: when installing globally, cabal shouldn't use umask, should set mods to 755 or 644 ----------------------------+----------------------------------------------- Reporter: alistra | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- I have an umask 077 on my root user, but when i type: cabal install --global pkg or I have a global setting in my configuration file, cabal installs the package globally, but with root's umask. cabal is a package manager and if I install a package globally, I expect it to be accessible globally. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/886> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #887: "cabal sdist" fails if a test suite has "other-modules: Paths_pkg"
by Hackage 05 Jan '12

05 Jan '12

#887: "cabal sdist" fails if a test suite has "other-modules: Paths_pkg" ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.10.1.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- For example, for the skein package I can't specify {{{ Test-suite runtests Type: exitcode-stdio-1.0 Other-modules: Paths_skein }}} I want to do so because there is a file used as test data for the tests. The file is specified inside {{{Data-files}}}. But, if I do so, I get: {{{ $ cabal sdist Building source dist for skein-0.1... cabal: Error: Could not find module: Paths_skein with any suffix: ["gc","chs","hsc","x","y","ly","cpphs","hs","lhs"] }}} Note that the resulting executable {{{runtests}}} works, and {{{cabal test}}} works as well. Note also that {{{Other-modules: Paths_skein}}} works on the {{{Library}}}, it fails only on the {{{Test-suite}}}. I've include a (hopefully) minimal test case. {{{ $ cabal configure --enable-tests Resolving dependencies... Configuring test-case-0.1... $ cabal build Preprocessing library test-case-0.1... Preprocessing test suites for test-case-0.1... Building test-case-0.1... Registering test-case-0.1... [1 of 2] Compiling Paths_test_case ( dist/build/autogen/Paths_test_case.hs, dist/build/runtests/runtests- tmp/Paths_test_case.o ) [2 of 2] Compiling Main ( test.hs, dist/build/runtests /runtests-tmp/Main.o ) Linking dist/build/runtests/runtests ... $ cabal test Running 1 test suites... Test suite runtests: RUNNING... Test suite runtests: PASS Test suite logged to: dist/test/test-case-0.1-runtests.log 1 of 1 test suites (1 of 1 test cases) passed. $ cabal sdist Distribution quality errors: No 'synopsis' or 'description' field. Distribution quality warnings: When distributing packages it is encouraged to specify source control information in the .cabal file using one or more 'source-repository' sections. See the Cabal user guide for details. Note: the public hackage server would reject this package. Building source dist for test-case-0.1... cabal: Error: Could not find module: Paths_test_case with any suffix: ["gc","chs","hsc","x","y","ly","cpphs","hs","lhs"] }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/887> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 5

[Hackage] #878: Install rsync on hackage.haskell.org
by Hackage 05 Jan '12

05 Jan '12

#878: Install rsync on hackage.haskell.org --------------------------------+------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: Severity: normal | Keywords: Difficulty: easy (<4 hours) | Ghcversion: Platform: | --------------------------------+------------------------------------------- I keep a local copy of the HackageDB, which I construct by downloading archive.tar and 00-index.tar.gz on occasion. This is kind of wasteful of bandwidth for me and the hackage.haskell.org server. My proposed solution is to install rsync on hackage.haskell.org in daemon mode, and configure it to serve the HaskellDB archive (or archive.tar and 00-index.tar.gz). This would allow users to download only the differences between their local copy and the official repository's copy. http://everythinglinux.org/rsync/ contains a sample rsync daemon configuration. It looks relatively straight forward to set up. Also, I would suggest that the front page's "Getting the Raw Data" section should contain a sample rsync command line invocation users can use to differentially mirror the archive. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/878> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #877: Cabal config breaks on Windows with username "{"
by Hackage 05 Jan '12

05 Jan '12

#877: Cabal config breaks on Windows with username "{" ------------------------------+--------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.10.1.0 Severity: major | Keywords: escaping Difficulty: easy (<4 hours) | Ghcversion: Platform: | ------------------------------+--------------------------------------------- I can't do anything because my username is "{". Either the parsing is being done incorrectly or the config file was generated incorrectly. I named myself this deliberately to see if any software would break; kind of sad that the one thing that broke so far is cabal, thought you would know better... My config file is attached. C:\Program Files (x86)\Console2>cabal --version cabal-install version 0.10.2 using version 1.10.1.0 of the Cabal library C:\Program Files (x86)\Console2>cabal update Warning: Error parsing config file C:\Users\{\AppData\Roaming\cabal\config:46: opening brace '{'has no matching closing brace '}' Warning: Using default configuration. Downloading the latest package list from hackage.haskell.org -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/877> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #892: Generated Paths file causes warnings
by Hackage 05 Jan '12

05 Jan '12

#892: Generated Paths file causes warnings ----------------------------+----------------------------------------------- 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: | ----------------------------+----------------------------------------------- With GHC 7.2.1 I get: {{{ [ 9 of 33] Compiling Paths_hlint (d ist\build\autogen\Paths_hlint.hs, dist\ build\Paths_hlint.o ) Implicit import declaration: Warning: In the use of `catch' (imported from Prelude, but defined in System.IO.Error): Deprecated: "Please use the new exceptions variant, Control.Exception.catch" }}} My versions are: {{{ $ cabal --version cabal-install version 0.10.2 using version 1.10.1.0 of the Cabal library }}} The paths file should be fixed, and should also probably put out a flag to ignore all warnings at the top - generated and unmodifiable code should not be giving out warnings. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/892> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #863: Can't pass extra arguments to c2hs
by Hackage 05 Jan '12

05 Jan '12

#863: Can't pass extra arguments to c2hs ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.10.1.0 Severity: normal | Keywords: c2hs, arguments Difficulty: unknown | Ghcversion: Platform: Mac OS | ---------------------------------+------------------------------------------ With cabal-install 0.10.2, I am no longer able to pass extra arguments to c2hs. When invoked as: {{{ cabal install -O --c2hs-option=--cppopts=-U__BLOCKS__ --c2hs-options="-- dump=trace" -v }}} c2hs is then called as {{{ /Users/localuser/.cabal/bin/c2hs --cpp=/usr/bin/gcc --cppopts=-E --cppopts=-D__GLASGOW_HASKELL__=700 --cppopts=-Ddarwin_BUILD_OS --cppopts=-Ddarwin_HOST_OS --cppopts=-Dx86_64_BUILD_ARCH --cppopts=-Dx86_64_HOST_ARCH --cppopts=-Icbits --cppopts=-DUSE_SSE2 --include=dist/build --cppopts=-I/Users/localuser/.cabal/lib/vector-0.7.0.1/ghc-7.0.4/include --cppopts=-I/Users/localuser/.cabal/lib/primitive-0.3.1/ghc-7.0.4/include --cppopts=-I/opt/local/include/ --cppopts=-I/usr/local/lib/ghc-7.0.4/base-4.3.1.0/include --cppopts=-I/usr/local/lib/ghc-7.0.4/include --cppopts=-I/usr/local/lib/ghc-7.0.4/include --output-dir=dist/build --output=Sound/Barnet/BandedLib.hs src/Sound/Barnet/BandedLib.chs --cppopts=-U__BLOCKS__ --dump=trace }}} The extra arguments are appended to the end of the call, however c2hs (at least c2hs-0.16.3) requires that the .chs binding file come after all options. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/863> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #893: Bad cabal build error message with mangled top of file
by Hackage 05 Jan '12

05 Jan '12

#893: Bad cabal build error message with mangled top of file ------------------------------+--------------------------------------------- Reporter: rrnewton | Owner: Type: defect | Status: new Priority: low | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: easy (<4 hours) | Ghcversion: Platform: | ------------------------------+--------------------------------------------- I accidentally executed an Emacs keystroke that switched tokens around and mangled the top of my file: {-# Language BangPatterns, CPP #-} # OPTIONS_GHC {--fno-warn-name-shadowing -fwarn-unused-imports #-} When GHC is run directly on this file it gives a sensible error message Control/Monad/Par/Stream.hs:1:36: parse error on input `#' But when building through cabal build it looks like there is a module- name-finding heuristic that is failing (and defaulting to Main), resulting in this weird error message: Building monad-par-0.1.0.2... Control/Monad/Par/Stream.hs:1:1: File name does not match module name: Saw: `Main' Expected: `Control.Monad.Par.Stream' Which really caused me to scratch my head when I saw it ;-). ("No where does it say Main!!") I was afraid I had messed up paths and was loading a different version of the file from another directory or something... -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/893> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2