http://permalink.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://permalink.gmane.org/gmane.comp.lang.haskell.cabal.devel/8996 <pre> Possibly. I thought I had some code in there to fix that up, but I guess it didn't do its thing. </pre> Bryan O'Sullivan 2012-05-25T16:59:37 http://permalink.gmane.org/gmane.comp.lang.haskell.cabal.devel/8995 <pre> My speculation would be that some Trac tickets don't exist because they have been deleted, and then these don't get converted, and this introduces an offset. Cheers, Andres </pre> Andres Löh 2012-05-25T16:59:31 http://permalink.gmane.org/gmane.comp.lang.haskell.cabal.devel/8994 <pre> Is the problem due to there already being some issue reports in the repo and thus all the Trac tickets got offset by some number? </pre> Johan Tibell 2012-05-25T16:56:13 http://permalink.gmane.org/gmane.comp.lang.haskell.cabal.devel/8993 <pre> Ugh. I'll see if I can find time to write a script to fix up the cross references. </pre> Bryan O'Sullivan 2012-05-25T16:49:43 http://permalink.gmane.org/gmane.comp.lang.haskell.cabal.devel/8992 <pre>Hi Ben and Bryan. I can confirm that. I've checked a number of cross-references in cabal-install bugs, and afaics, they're all(?) wrong. Cheers, Andres </pre> Andres Löh 2012-05-25T06:48:45 http://permalink.gmane.org/gmane.comp.lang.haskell.cabal.devel/8991 <pre> I could do that, but it might be as fast to do it by hand as to write a script for the job. </pre> Bryan O'Sullivan 2012-05-24T17:12:19 http://permalink.gmane.org/gmane.comp.lang.haskell.cabal.devel/8990 <pre> Haven't had time to look at it yet (on the road atm) but I just wanted to say a big thank you Bryan for all the hard work! Will do when I get back (unless Andres beats me to it) Duncan _______________________________________________ cabal-devel mailing list cabal-devel&lt; at &gt;haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel </pre> Duncan Coutts 2012-05-24T17:06:53 http://permalink.gmane.org/gmane.comp.lang.haskell.cabal.devel/8989 <pre> At least one of the ticket cross-references has gone wrong: https://github.com/haskell/cabal/issues/653 I refer to #719 in this ticket, which links to github issue #719, but that's Trac ticket #729. I wanted the ticket imported from Trac #719, i.e. this one https://github.com/haskell/cabal/issues/710 </pre> Ben Millwood 2012-05-24T14:49:10 http://permalink.gmane.org/gmane.comp.lang.haskell.cabal.devel/8988 <pre>Hi Bryan. First of all, thanks. It looks great. On Thu, May 24, 2012 at 8:14 AM, Bryan O'Sullivan &lt;bos&lt; at &gt;serpentine.com&gt; wrote: Sorry for noting this only once I go through the Wiki page. The difficulty level has not been converted? It's not terribly important, but we've used it in the past to point interested newcomers to supposedly "easy" tasks. If it's a lot of work to change now, then don't. But perhaps it could be done by just modifying the already converted tickets in one batch process and adding new tags? I have tried to delete ticket modification permissions for authenticated users in the trac. I'm hesitating to change the file permissions, as we'll probably still want to use the Wiki for now. I changed the pointers on the Trac main page and on haskell.org/cabal -- there are probably other references elsewhere. If you know of anything important that should be changed, please let me know. Cheers, Andres </pre> Andres Löh 2012-05-24T06:43:16 http://permalink.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://permalink.gmane.org/gmane.comp.lang.haskell.cabal.devel/8986 <pre>#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 (&lt; 1 day) | Ghcversion: 6.8.2 Platform: | ---------------------------------+------------------------------------------ Changes (by rrnewton): * cc: rrnewton&lt; at &gt;… (added) </pre> Hackage 2012-05-23T15:50:13 http://permalink.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 sui</pre> Hackage 2012-05-21T06:08:07 http://permalink.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:</pre> Hackage 2012-05-20T15:43:01 http://permalink.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://permalink.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 --e</pre> Hackage 2012-05-15T22:24:13 http://permalink.gmane.org/gmane.comp.lang.haskell.cabal.devel/8981 <pre>#951: Incorrect error messages for non-existing dependencies ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: cabal-install-0.16 Component: cabal-install tool | Version: 1.14.0 Severity: normal | Keywords: message, solver Difficulty: unknown | Ghcversion: 7.4.1 Platform: Linux | ---------------------------------+------------------------------------------ Comment(by guest): What about outputting all fails from the solver? Something that would behave similar to {{{ $ cabal install -v3 | grep fail }}} If this is too verbose as the default behavior, it might be good as one verbosity level. </pre> Hackage 2012-05-15T14:40:41 http://permalink.gmane.org/gmane.comp.lang.haskell.cabal.devel/8980 <pre>#951: Incorrect error messages for non-existing dependencies ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: cabal-install-0.16 Component: cabal-install tool | Version: 1.14.0 Severity: normal | Keywords: message, solver Difficulty: unknown | Ghcversion: 7.4.1 Platform: Linux | ---------------------------------+------------------------------------------ Comment(by kosmikus): It's really a question about which error message to choose. If you scan up in your log, you will see another "fail (backjumping ..." line before the one you've just shown. Currently, the solver tries backtracking to a limit, and if it fails, it will print the *first* error it encountered. This is based on the heuristic that us</pre> Hackage 2012-05-15T13:58:32 http://permalink.gmane.org/gmane.comp.lang.haskell.cabal.devel/8979 <pre>#951: Incorrect error messages for non-existing dependencies ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: cabal-install-0.16 Component: cabal-install tool | Version: 1.14.0 Severity: normal | Keywords: message, solver Difficulty: unknown | Ghcversion: 7.4.1 Platform: Linux | ---------------------------------+------------------------------------------ Comment(by guest): Thanks for answering! Sounds complicated. I guess, good error reporting for unsuccessful constraint solving is a big subject in its own right. BTW: Increased verbosity (-v3) results in a message containing this: {{{ [_39] fail (unknown package: bogus) [__0] fail (backjumping, conflict set: bogus, foo) }}} Which is what I wo</pre> Hackage 2012-05-15T13:36:00 http://permalink.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://permalink.gmane.org/gmane.comp.lang.haskell.cabal.devel/8977 <pre>#951: Incorrect error messages for non-existing dependencies ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: cabal-install-0.16 Component: cabal-install tool | Version: 1.14.0 Severity: normal | Keywords: message, solver Difficulty: unknown | Ghcversion: 7.4.1 Platform: Linux | ---------------------------------+------------------------------------------ Changes (by kosmikus): * keywords: message solver =&gt; message, solver * type: defect =&gt; enhancement * milestone: =&gt; cabal-install-0.16 Comment: Thanks for the report. I'm not sure what you would actually expect here. The solver has some freedom in which order to try to resolve the goals. And the problem it reports is the first problem it </pre> Hackage 2012-05-15T12:05:15 http://permalink.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 depend</pre> Hackage 2012-05-15T11:43:42 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.lang.haskell.cabal.devel