http://blog.gmane.org/gmane.comp.lang.haskell.cabal.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8987 <pre>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? </pre> Bryan O'Sullivan 2012-05-24T06:14:01 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8985 <pre>#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&gt; 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&gt; }}} 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. </pre> Hackage 2012-05-21T06:08:07 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8984 <pre>#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. </pre> Hackage 2012-05-20T15:43:01 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8983 <pre>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. </pre> Bryan O'Sullivan 2012-05-17T03:44:21 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8982 <pre>#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. </pre> Hackage 2012-05-15T22:24:13 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8978 <pre>#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 &gt;= 0.2.2.0 (indirectly via mtl). Should either adapt the code to work with older versions or fix the dependency. </pre> Hackage 2012-05-15T12:08:23 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8976 <pre>#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 =&gt; mtl&gt;=2.0 &amp;&amp; &lt;2.1) rejecting: mtl-2.0.1.0, 2.0.0.0 (conflict: transformers==0.3.0.0, mtl =&gt; 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 =&gt; mtl&gt;=2.0 &amp;&amp; &lt;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 }}} </pre> Hackage 2012-05-15T11:43:42 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8975 <pre>#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 }}} </pre> Hackage 2012-05-11T20:01:44 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8974 <pre>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). </pre> Bryan O'Sullivan 2012-05-11T07:55:31 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8973 <pre>#949: cabal should fail if compilation depends on a file not existing in the cabal file ---------------------------------+------------------------------------------ Reporter: LeventErkok | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.10.2.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Cabal doesn't complain if the build depends on a Haskell module that exists in the filesystem properly, but is not mentioned in the cabal file itself as part of "exposed-modules" or "other-modules". The build succeeds because ghc can find the relevant file just fine. I've got bitten by this several times, especially after pushing a package to hackage, only to get it fail to build on the server because I've failed to put the name of a file in the appropriate section of the cabal file, thus it didn't make it to the .tar.gz bundle that got uploaded to the server. I realize this might be hard to ensure, as it would require a deeper look into the dependencies between modules, but I trust the GHC API should have all the information necessary for cabal to complain appropriately. </pre> Hackage 2012-05-11T04:14:14 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8968 <pre>With 2.8 released, I felt Darcs deserves better presentation. After surveying other VCS sites I worked on an update to our home page layout and content over the last few days, with review and input from #darcs, and it went live last night. It's far from perfect but I hope it's a good step forward. Thanks for the input, and have at it: http://darcs.net -Simon </pre> Simon Michael 2012-04-30T19:27:57 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8963 <pre>#948: some way to specify common build-depends for library, executables and test- suites ---------------------------------+------------------------------------------ Reporter: Oblosys | Owner: Type: enhancement | Status: new Priority: low | Milestone: Component: cabal-install tool | Version: 1.10.2.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Not sure whether this is a feature request or a bug report. I sometimes have a number of dependencies that are the same for library, executable, and test-suite. The global property 'build-depends' looks like an ideal place to put these, but any dependencies I list there seem to be ignored by cabal. </pre> Hackage 2012-04-27T18:26:29 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8962 <pre>#947: let "cabal -fSomeFlag" produce error for undeclared flags ---------------------------------+------------------------------------------ Reporter: Oblosys | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.10.2.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Typos in flags can lead to confusing problems, especially with large projects that take a long time to build. A simple check could be quite useful: ~&gt; hconfigure -fNonExistentFlag -fSomeFlag cabal: undeclared flag 'NonExistentFlag'. Declared flags are: ExistentFlag, SomeFlag </pre> Hackage 2012-04-27T17:51:03 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8961 <pre>#947: Raspberry Ketone Plus Miracle ----------------------------+----------------------------------------------- Reporter: antibac01 | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.10.2.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- All ingredients used in [http://healthremediesblog.com/raspberry-ketone- plus/ Raspberry Ketone Plus] are all natural and 100% certified by FDA. Raspberry Ketone Plus has been reported with no side effect and been a outstanding to lose weight effectively. Being the latest and newest product in town, it has indeed create a storm of craze for those who wish to lose weight fast. Fox News has reported that most of the health stores have been sold out for this supplement and waiting for a new batch of it to arrived while other has been placing their orders. Nothing really bids this supplement and if you wish to [http://healthremediesblog.com/raspberry-ketone-plus/ buy raspberry ketone plus], good luck in finding one at stores, you would have a better chance to buy it online from the distributors or its suppliers. Many of the online stores also give you a 30 days money back guaranteed so you can try out the product without any risk. </pre> Hackage 2012-04-27T08:59:47 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8960 <pre>#946: Packages are downloaded insecurely ----------------------------+----------------------------------------------- Reporter: cooldude | Owner: Type: defect | Status: new Priority: high | Milestone: Component: Cabal library | Version: 1.10.2.0 Severity: major | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- It appears that when running cabal install package, the package is downloaded without any transport security. Anyone who can perform a man in the middle attack could tamper with the package that is being downloaded, resulting in a complete compromise of the cabal user. This makes it impossible to use cabal. The servers should utilize TLS, it is possible to get a free certificate from startcom if price is a concern. Additionally when packages are verified as non-malicious, they should be signed with a "cabal" signing key, and then the package signatures should be verified by cabal. </pre> Hackage 2012-04-26T10:16:58 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8945 <pre>#945: Fails to find install plan for containers package tests ---------------------------------+------------------------------------------ Reporter: tibbe | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.14.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: 7.4.1 Platform: Linux | ---------------------------------+------------------------------------------ The containers package has a test-suite section which seems to create a cycle when building the package. Could it be that Cabal treats the package as one unit instead of treating the library and test-suite sections separately, which should remove the cycle. {{{ $ cabal install --enable-tests -v3 searching for ghc in path. found ghc at /usr/local/bin/ghc ("/usr/local/bin/ghc",["--numeric-version"]) /usr/local/bin/ghc is version 7.4.1 looking for tool "ghc-pkg" near compiler in /usr/local/bin found ghc-pkg in /usr/local/bin/ghc-pkg ("/usr/local/bin/ghc-pkg",["--version"]) /usr/local/bin/ghc-pkg is version 7.4.1 ("/usr/local/bin/ghc",["--supported-languages"]) ("/usr/local/bin/ghc",["--info"]) Reading installed packages... ("/usr/local/bin/ghc-pkg",["dump","--global","-v0"]) ("/usr/local/bin/ghc-pkg",["dump","--user","-v0"]) ("/usr/local/bin/ghc",["--print-libdir"]) Reading available packages... Choosing modular solver. Resolving dependencies... [__0] trying: containers-0.5.0.0 (user goal) [__1] next goal: base (dependency of containers-0.5.0.0) [__1] rejecting: base-3.0.3.2, 3.0.3.1 (global constraint requires installed instance) [__1] trying: base-4.5.0.0/installed-f76... [__2] trying: rts-1.0/installedbuil... (dependency of base-4.5.0.0/installed-f76...) [__3] trying: integer-gmp-0.4.0.0/installed-ec8... (dependency of base-4.5.0.0/installed-f76...) [__4] rejecting: containers-0.5.0.0:!test (global constraint requires opposite flag selection) [__4] trying: containers-0.5.0.0:*test [__5] trying: test-framework-quickcheck2-0.2.12.1 (dependency of containers-0.5.0.0:*test) [__6] trying: test-framework-quickcheck2-0.2.12.1:+base4 [__7] trying: test-framework-quickcheck2-0.2.12.1:-base3 [__8] trying: random-1.0.1.1/installed-3be... (dependency of test- framework-quickcheck2-0.2.12.1:+base4) [__9] trying: time-1.4/installed-3e1... (dependency of random-1.0.1.1 /installed-3be...) [_10] trying: old-locale-1.0.0.4/installed-29b... (dependency of time-1.4 /installed-3e1...) [_11] trying: extensible-exceptions-0.1.1.4/installed-d27... (dependency of test-framework-quickcheck2-0.2.12.1) [_12] trying: test-framework-hunit-0.2.7 (dependency of containers-0.5.0.0:*test) [_13] trying: test-framework-hunit-0.2.7:+base4 [_14] trying: test-framework-hunit-0.2.7:-base3 [_15] trying: test-framework-0.6 (dependency of containers-0.5.0.0:*test) [_16] trying: test-framework-0.6:-tests [_17] trying: test-framework-0.6:+splitbase [_18] trying: hostname-1.0 (dependency of test-framework-0.6) [_19] trying: xml-1.3.12 (dependency of test-framework-0.6) [_20] trying: text-0.11.2.0/installed-a62... (dependency of xml-1.3.12) [_21] trying: bytestring-0.9.2.1/installed-4ad... (dependency of xml-1.3.12) [_22] trying: regex-posix-0.95.1 (dependency of test-framework-0.6) [_23] trying: regex-posix-0.95.1:+splitbase [_24] trying: regex-posix-0.95.1:+newbase [_25] trying: regex-base-0.93.2 (dependency of regex- posix-0.95.1:+newbase) [_26] trying: regex-base-0.93.2:+splitbase [_27] trying: regex-base-0.93.2:+newbase [_28] trying: mtl-2.1/installed-0a8... (dependency of regex- base-0.93.2:+newbase) [_29] trying: transformers-0.3.0.0/installed-f23... (dependency of mtl-2.1 /installed-0a8...) [_30] trying: ansi-wl-pprint-0.6.4 (dependency of test-framework-0.6) [_31] trying: ansi-wl-pprint-0.6.4:+newbase [_32] trying: ansi-wl-pprint-0.6.4:-example [_33] trying: ansi-terminal-0.5.5 (dependency of test-framework-0.6) [_34] trying: ansi-terminal-0.5.5:+splitbase [_35] trying: ansi-terminal-0.5.5:-example [_36] trying: unix-2.5.1.0/installed-346... (dependency of ansi- terminal-0.5.5) [_37] trying: QuickCheck-2.4.2 (dependency of containers-0.5.0.0:*test) [_38] trying: QuickCheck-2.4.2:+templatehaskell [_39] trying: QuickCheck-2.4.2:+base4 [_40] trying: QuickCheck-2.4.2:+base3 [_41] next goal: template-haskell (dependency of QuickCheck-2.4.2:+templatehaskell) [_41] rejecting: template-haskell-2.7.0.0/installed-164... (conflict: containers==0.5.0.0, template-haskell =&gt; containers==0.4.2.1/installed- 7c5...) [_41] trying: template-haskell-2.7.0.0 [_42] trying: pretty-1.1.1.0/installed-7e1... (dependency of template- haskell-2.7.0.0) [_43] trying: HUnit-1.2.4.2 (dependency of containers-0.5.0.0:*test) [_44] trying: HUnit-1.2.4.2:+base4 [_45] trying: ghc-prim-0.2.0.0/installed-bd2... (dependency of containers-0.5.0.0) [_46] trying: deepseq-1.3.0.0/installed-6c1... (dependency of containers-0.5.0.0) [_47] next goal: array (dependency of containers-0.5.0.0) [_47] trying: array-0.4.0.0/installed-0b3... [_48] done cabal: internal error: could not construct a valid install plan. The proposed (invalid) plan contained the following problems: The following packages are involved in a dependency cycle test-framework- hunit-0.2.7, test-framework-0.6, regex-posix-0.95.1, regex-base-0.93.2, containers-0.5.0.0, test-framework-quickcheck2-0.2.12.1, QuickCheck-2.4.2, template-haskell-2.7.0.0 }}} </pre> Hackage 2012-04-24T18:50:09 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8938 <pre>Hi everyone. The cabal repository now lives at Github: https://github.com/haskell/cabal The bug tracker remains with Trac for now. I'll run some experiments with converters from Trac to Github to see whether it's feasible to convert that as well. The darcs repositories should no longer be used. Cheers, Andres </pre> Andres Löh 2012-04-22T13:26:31 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8937 <pre>#944: Duplicate C symbol names -----------------------------+---------------------------------------------- Reporter: PaulVanDerWalt | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.14.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: 7.2.2 Platform: Mac OS | -----------------------------+---------------------------------------------- I've run into a problem where I want to include the vty and haskeline packages, which both contain the same C code, of which the symbol names are not translated or made unique. When I use both packages, and try to compile something which has Template Haskell (which triggers loading of all dependencies), I get the following error. GHCi runtime linker: fatal error: I found a duplicate definition for symbol _mk_wcswidth whilst processing object file /Users/paul/.cabal/lib/haskeline-0.6.4.6/ghc-7.2.2/HShaskeline-0.6.4.6.o A workaround is to patch the libraries to make the function names unique, but this is less than ideal. </pre> Hackage 2012-04-22T13:07:54 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8935 <pre>Wed Mar 28 20:08:42 PDT 2012 Duncan Coutts &lt;duncan&lt; at &gt;community.haskell.org&gt; * Fix doc comment for ghcOptSourcePathClear Spotted by tibbe M ./Cabal/Distribution/Simple/Program/GHC.hs -1 +2 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=20120329030842-5c91e-ac9056beede12f84766d832f0b00e466eab2a942.gz Tue Jul 26 15:29:23 PDT 2011 Thomas Tuegel &lt;ttuegel&lt; at &gt;gmail.com&gt; * New detailed test suite interface. This patch implements a new interface for detailed test suites based on Duncan's proposal. This implementation differs from his in a few ways: * The constructors of 'Tests' have been renamed. I think 'TestGroup' and 'ExtraTestOptions' are redundant: it is clear from context what sort of Group and what sort of ExtraOptions are being considered and qualified imports can resolve any name conflicts. Group and ExtraOptions have the advantage of improving the brevity of pattern matches on Tests, which are used very often in D.S.Test. * The 'concurrentSafe :: Bool' field of TestInstance has become the 'concurrently' field of Group, allowing package and test framework authors greater control over concurrency. * The 'Finished' constructor of 'Progress' now contains the options used to run the test in addition to the test result. Without returning the options, it would be difficult to extract the RNG seed used to run a test. * A detailed test suite module now exports the symbol 'test :: IO Tests'. This enables the use of IO to enumerate the tests in a group, suggested by Duncan as a way to accomodate the GHC test suite. M ./Cabal/Distribution/Simple/Test.hs -72 +152 M ./Cabal/Distribution/TestSuite.hs -259 +68 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=20110726222923-30370-7d42433d44a2b2c3fb88e8a955c76ac5e83a903e.gz Fri Jul 29 08:02:38 PDT 2011 Thomas Tuegel &lt;ttuegel&lt; at &gt;gmail.com&gt; * Renamed Distribution.TestSuite.Tests to Test. M ./Cabal/Distribution/Simple/Test.hs -4 +4 M ./Cabal/Distribution/TestSuite.hs -4 +4 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=20110729150238-30370-a2fc53aa388d175e80faec05723c6e36b2c2b298.gz Fri Jul 29 08:10:01 PDT 2011 Thomas Tuegel &lt;ttuegel&lt; at &gt;gmail.com&gt; * Removed obsolete LANGUAGE pragma from Distribution.TestSuite. M ./Cabal/Distribution/TestSuite.hs -1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=20110729151001-30370-feefa70db2cb7fce720a0ce73402f0af51884a5a.gz Fri Jul 29 08:42:49 PDT 2011 Thomas Tuegel &lt;ttuegel&lt; at &gt;gmail.com&gt; * Cleaned for warnings in D.TestSuite and D.S.Test. M ./Cabal/Distribution/Simple/Test.hs -4 +4 M ./Cabal/Distribution/TestSuite.hs -1 +1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=20110729154249-30370-5e7c74f65fce8eb08b408862c1a3894b14dd887c.gz Fri Jul 29 08:48:12 PDT 2011 Thomas Tuegel &lt;ttuegel&lt; at &gt;gmail.com&gt; * Removed 'optionStringDescription' from OptionType. M ./Cabal/Distribution/TestSuite.hs -1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=20110729154812-30370-915f671e6b9cd23d2286090b69dbcc91432bc061.gz Thu Sep 1 11:26:06 PDT 2011 Thomas Tuegel &lt;ttuegel&lt; at &gt;gmail.com&gt; * Changed detailed test exported type to [Test]. M ./Cabal/Distribution/Simple/Test.hs -21 +23 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=20110901182606-30370-52b1f4413c9e96c4f951d7b483ad8058a6a46a89.gz Tue Sep 6 14:16:11 PDT 2011 Thomas Tuegel &lt;ttuegel&lt; at &gt;gmail.com&gt; * Clean D.S.Test for unused symbols. The unused declarations were all related to replaying test suites with logged options, but the command-line option for this feature has been disabled for some time. Changing the detailed test suite type to expect "tests :: IO [Test]" instead of "tests :: IO Test" made the old method of replaying options clumsy. Since it was already disabled, I chose to remove it, rather than rewrite it again. M ./Cabal/Distribution/Simple/Test.hs -45 +1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=20110906211611-30370-b69b92b2a6d5070add303626eeeac3a9927f2e0f.gz Tue Sep 6 14:55:57 PDT 2011 Thomas Tuegel &lt;ttuegel&lt; at &gt;gmail.com&gt; * Removed Options from Finished. M ./Cabal/Distribution/Simple/Test.hs -3 +8 M ./Cabal/Distribution/TestSuite.hs -4 +1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=20110906215557-30370-45c2e98be628e5fb739cf536873576fa40430cae.gz Tue Sep 6 14:56:00 PDT 2011 Thomas Tuegel &lt;ttuegel&lt; at &gt;gmail.com&gt; * Improved documentation for 'concurrently' field of Test. M ./Cabal/Distribution/TestSuite.hs -3 +8 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=20110906215600-30370-a9192723e395e2606959107efd59f113eedad09e.gz Tue Sep 6 16:36:32 PDT 2011 Thomas Tuegel &lt;ttuegel&lt; at &gt;gmail.com&gt; * Added 'testGroup' to D.S.TestSuite. M ./Cabal/Distribution/TestSuite.hs +6 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=20110906233632-30370-f079e5a5c17d88eab9833cf4871bf6b7aa2e4600.gz Tue Sep 6 16:49:31 PDT 2011 Thomas Tuegel &lt;ttuegel&lt; at &gt;gmail.com&gt; * Updated user manual for new detailed interface. M ./Cabal/doc/developing-packages.markdown -27 +21 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=20110906234931-30370-b59143f738f36f5314f4710604444a128f04618d.gz </pre> Duncan Coutts 2012-04-22T10:56:00 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8929 <pre>Hi. I have converted the existing Cabal/cabal-install darcs repo plus branches into a git repo. Per Igloo's request, I have tried to use the same method that has already been used by ghc to mirror the Cabal darcs repo to git, so that hashes of commits stay stable. However, it turns out that the resulting repo has two invalid commits: $ git fsck error in commit 26ef89b1272a0d860d8c0c0b06e9a78270b179c6: invalid author/committer line - missing space before email error in commit cc2f67f98fbc246f010516c71722d5c3432e0a2b: invalid author/committer line - missing space before email dangling tag d50b3b58bbaac67412af0e1e197946599a627f0d dangling tag 070e971fa01b7801c51455f924522d2edd4408e5 dangling tag b21bf31fc1a95688c27d5e2bd04224802ee9d82c dangling tag 272c383a0dcaeeb8d774136bfd8b555ddcaa32c4 dangling tag 633c2bf039bbfa3fb66b204d358519d374cade22 dangling tag bb40c2dce611768b03600f6baea8b5b19f4a5da3 dangling tag 074186b4abe147ad74287ce9d674b5e29a1989f1 dangling tag b0ae0f70fe571cb89b126eb4b3132627a846d2ca dangling tag 15b05c2da997604e4bbcfb89a6587a13c9db3705 dangling tag b5b5bb276b6102a07ed8e6f6c5aa9d4ca607c039 dangling tag a3baffce1f42c2368f653eaecba95a2278df5928 dangling tag 8ce6b0314c3eeacd6352d48e295b6362082fb68c The presence of these commits prevents me from pushing to github. One of these two is in the trunk and also present in the already mirrored repository on Github. Ian tells me that they have convinced the Github people to manually upload the repo in the past. The question now is how to deal with this situation: * Should I ask the Github admins again to do some manual intervention? Are we happy that these two patches won't cause problems in the future? * Or: Should we fix the two patches by rewriting the author information, but as a consequence changing nearly all the commit hashes of the Cabal repo, causing a less smooth transition for everyone who has an already checked out ghc source tree? Cheers, Andres </pre> Andres Löh 2012-04-21T14:40:14 http://comments.gmane.org/gmane.comp.lang.haskell.cabal.devel/8924 <pre>#943: Synopsis field causes haddock build failure ----------------------------+----------------------------------------------- Reporter: davidt | 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: Linux | ----------------------------+----------------------------------------------- For some reason the presence of the 'synopsis' field causes haddock documentation to fail to build. Steps: $ cabal unpack dclabel $ cabal configure $ cabal haddock {{{ Running Haddock for dclabel-0.0.6... Warning: The documentation for the following packages are not installed. No links will be generated to these packages: rts-1.0, cereal-0.3.5.1 Preprocessing library dclabel-0.0.6... &lt;command line&gt;: Could not find module `The' Use -v to see a list of the files searched for. }}} I assume something is mis-configured on my system but have no idea what and how to fix it Versions: {{{ $ cabal --version cabal-install version 0.14.0 using version 1.14.0 of the Cabal library $ ghc --version The Glorious Glasgow Haskell Compilation System, version 7.4.1 $ haddock --version Haddock version 2.10.0, (c) Simon Marlow 2006 Ported to use the GHC API by David Waern 2006-2008 }}} This is on Ubuntu Linux 11.10. </pre> Hackage 2012-04-21T00:48:37 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.lang.haskell.cabal.devel