September 2009 - cabal-devel

patch applied (cabal): Don't simplify empty/inconsistent version ranges
by Duncan Coutts 20 Sep '09

20 Sep '09

Sun Sep 20 08:16:47 PDT 2009 Duncan Coutts <duncan(a)haskell.org> * Don't simplify empty/inconsistent version ranges Ignore-this: aeddcb5625dd29963036c07be5a9c2da They all get squashed to ">1 && <1" which while canonical is not helpful. M ./Distribution/Version.hs -3 +15 M ./tests/Test/Distribution/Version.hs -1 +3 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20090920151647-adfee-0ee1bdf5…

1 0

Windows Install Issues for erf (and statistics)
by Dominic Steinitz 20 Sep '09

20 Sep '09

The package statistics uses the package erf. Doing cabal install statistics works fine but when I try to use anything I get: > Loading package syb ... linking ... done. > Loading package base-3.0.3.0 ... linking ... done. > Loading package erf-1.0.0.0 ... linking ... <interactive>: > C:\Program Files\Haskell\erf-1.0.0.0\ghc-6.10.1\HSerf-1.0.0.0.o: unknown symbol > `_erfc' > : unable to load package `erf-1.0.0.0' I assume that erf is looking for some C functions which are available on linux but not windows. I'm not sure what the solution is. Should cabal complain? Should there be some documentation on the erf homepage telling windows users what to do? Or at least that it doesn't work on windows? Dominic.

1 0

Re: [Hackage] #588: requiring '.' for blank lines is annoying
by Hackage 19 Sep '09

19 Sep '09

#588: requiring '.' for blank lines is annoying ----------------------------+----------------------------------------------- Reporter: Jake Wheat | Owner: Type: defect | Status: closed Priority: low | Milestone: Component: Cabal library | Version: 1.6.0.2 Severity: minor | Resolution: duplicate Keywords: | Difficulty: unknown Ghcversion: | Platform: ----------------------------+----------------------------------------------- Comment (by guest): Yes I missed that text, my mistake. I did check a few packages on hackage db before reporting and somehow managed to only find ones where the package author had made the same mistake as me, looking again I can see most uploaders got this right. Since a few others have also made this mistake, could I suggest adding a sentence to description property, something like: For library packages, this field is used as prologue text by setup haddock (see the section called “setup haddock”), and thus may contain the same markup as haddock documentation comments (you need to use an indented '.' to get a blank line in the markup passed to haddock, as noted above). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/588#comment:3> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #588: requiring '.' for blank lines is annoying
by Hackage 19 Sep '09

19 Sep '09

#588: requiring '.' for blank lines is annoying ----------------------------+----------------------------------------------- Reporter: Jake Wheat | Owner: Type: defect | Status: closed Priority: low | Milestone: Component: Cabal library | Version: 1.6.0.2 Severity: minor | Resolution: duplicate Keywords: | Difficulty: unknown Ghcversion: | Platform: ----------------------------+----------------------------------------------- Changes (by duncan): * status: new => closed * resolution: => duplicate * summary: whitespace in description mangled before running haddock => requiring '.' for blank lines is annoying Comment: In that same section of the user guide it state: * To get a blank line in a field value, use an indented “.” This is an annoying historical artifact in the Cabal specification from the time when blank lines were used to separate sections. There's no need to keep this "feature". See ticket #478. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/588#comment:2> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #588: whitespace in description mangled before running haddock
by Hackage 19 Sep '09

19 Sep '09

#588: whitespace in description mangled before running haddock ----------------------------+----------------------------------------------- Reporter: Jake Wheat | Owner: Type: defect | Status: new Priority: low | Milestone: Component: Cabal library | Version: 1.6.0.2 Severity: minor | Resolution: Keywords: | Difficulty: unknown Ghcversion: | Platform: ----------------------------+----------------------------------------------- Changes (by guest): * reporter: guest => Jake Wheat Old description: > The cabal documentation on this page: > > http://www.haskell.org/cabal/release/cabal-latest/doc/users- > guide/authors.html#pkg-descr > > contains this under the documentation for the description property: > 'For library packages, this field is used as prologue text by setup > haddock (see the section called “setup haddock”), and thus may contain > the same markup as haddock documentation comments.' > > But when I try to use e.g. paragraphs in this field, it appears as though > the whitespace gets stripped out and so the paragraphs don't appear and > all the text gets shoved together. > > Example from my cabal file: > > Description: Sql parser, pretty printer and type checker, targets > PostGreSQL SQL and PL/pgSQL, uses Parsec and UUAGC. > > Overview: > > see the module 'Database.HsSqlPpp.TypeChecking.Ast' > for the ast types; > > 'Parser' for converting text to asts; > > 'PrettyPrinter' for converting asts to text; > > <snip> > > this results in: > > Sql parser, pretty printer and type checker, targets PostGreSQL SQL and > PL/pgSQL, uses Parsec and UUAGC. Overview: see the module > Database.HsSqlPpp.TypeChecking.Ast for the ast types; Parser for > converting text to asts; PrettyPrinter for converting asts to text;<snip> > > coming out in the haddock docs and on hackagedb - all the newlines are > missing. When I copy this text to a separate file an invoke haddock -p, > the documentation comes out with the paragraphs correctly, so I'm > guessing this is something cabal is doing to the description property > before passing it to haddock. > > full cabal file here: > http://hackage.haskell.org/packages/archive/hssqlppp/0.0.6/hssqlppp.cabal > scrunched text viewable here: > http://hackage.haskell.org/package/hssqlppp > > reported by Jake Wheat New description: The cabal documentation on this page: http://www.haskell.org/cabal/release/cabal-latest/doc/users- guide/authors.html#pkg-descr contains this under the documentation for the description property: 'For library packages, this field is used as prologue text by setup haddock (see the section called “setup haddock”), and thus may contain the same markup as haddock documentation comments.' But when I try to use e.g. paragraphs in this field, it appears as though the whitespace gets stripped out and so the paragraphs don't appear and all the text gets shoved together. Example from my cabal file: Description: Sql parser, pretty printer and type checker, targets PostGreSQL SQL and PL/pgSQL, uses Parsec and UUAGC. Overview: see the module 'Database.HsSqlPpp.TypeChecking.Ast' for the ast types; 'Parser' for converting text to asts; 'PrettyPrinter' for converting asts to text; <snip> this results in: Sql parser, pretty printer and type checker, targets PostGreSQL SQL and PL/pgSQL, uses Parsec and UUAGC. Overview: see the module Database.HsSqlPpp.TypeChecking.Ast for the ast types; Parser for converting text to asts; PrettyPrinter for converting asts to text;<snip> coming out in the haddock docs and on hackagedb - all the newlines are missing. When I copy this text to a separate file an invoke haddock -p, the documentation comes out with the paragraphs correctly, so I'm guessing this is something cabal is doing to the description property before passing it to haddock. full cabal file here: http://hackage.haskell.org/packages/archive/hssqlppp/0.0.6/hssqlppp.cabal scrunched text viewable here: http://hackage.haskell.org/package/hssqlppp -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/588#comment:1> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #588: whitespace in description mangled before running haddock
by Hackage 19 Sep '09

19 Sep '09

#588: whitespace in description mangled before running haddock ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: low | Milestone: Component: Cabal library | Version: 1.6.0.2 Severity: minor | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- The cabal documentation on this page: http://www.haskell.org/cabal/release/cabal-latest/doc/users- guide/authors.html#pkg-descr contains this under the documentation for the description property: 'For library packages, this field is used as prologue text by setup haddock (see the section called “setup haddock”), and thus may contain the same markup as haddock documentation comments.' But when I try to use e.g. paragraphs in this field, it appears as though the whitespace gets stripped out and so the paragraphs don't appear and all the text gets shoved together. Example from my cabal file: Description: Sql parser, pretty printer and type checker, targets PostGreSQL SQL and PL/pgSQL, uses Parsec and UUAGC. Overview: see the module 'Database.HsSqlPpp.TypeChecking.Ast' for the ast types; 'Parser' for converting text to asts; 'PrettyPrinter' for converting asts to text; <snip> this results in: Sql parser, pretty printer and type checker, targets PostGreSQL SQL and PL/pgSQL, uses Parsec and UUAGC. Overview: see the module Database.HsSqlPpp.TypeChecking.Ast for the ast types; Parser for converting text to asts; PrettyPrinter for converting asts to text;<snip> coming out in the haddock docs and on hackagedb - all the newlines are missing. When I copy this text to a separate file an invoke haddock -p, the documentation comes out with the paragraphs correctly, so I'm guessing this is something cabal is doing to the description property before passing it to haddock. full cabal file here: http://hackage.haskell.org/packages/archive/hssqlppp/0.0.6/hssqlppp.cabal scrunched text viewable here: http://hackage.haskell.org/package/hssqlppp reported by Jake Wheat -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/588> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[patch] #562: cabal-install update fails going through a HTTP proxy
by valery.vv＠gmail.com 19 Sep '09

19 Sep '09

Dear Cabal maintainers, A couple of days ago I was unable to cabal-install a library from Hackage -- 00-index.tar.gz was not downloaded completely. And if obtaining one with wget, other .tar.gz files (packages) still could not be fetched in full. This problem has been reported already (see http://hackage.haskell.org/trac/hackage/ticket/562) 06/11/09 09:49:25 changed by duncan: > Why has this started cropping up all of a sudden? Never seen this > before then 3 reports in as many days. Do we suspect HTTP-4000.0.6 -> > 7 perhaps? 06/11/09 13:02:47 changed by michaeldever: > So it's definitely a problem with the HTTP package in my opinion. I'm > not sure if it is a problem with the packages proxy handling, as it > does download some of the package, but not all of it. > > Seeing as both the Zlib library, and tar yield an end of stream error, > its something that I'm reckoning is happening during transport. 06/13/09 09:05:26 changed by michaeldever: > http://trac.haskell.org/http/ticket/8#comment:1 The bug is not in HTTP API, but in the way cabal-install uses it. The type of HTTP response body is polymorphic within `HTTP' library (rspBody :: Response a -> a) but it is specialized to Lazy.ByteString by cabal-install's `getHTTP' function (Distribution/Client/HttpUtils.hs). Once the type of response body is changed to _strict_ ByteString, files get downloaded through proxy completely. The attached module [proxy-POC.hs] makes this quite apparent (you need to be behind a proxy; HTTP >= 4000.0.8): vvv@takeshi:~/src$ time runhaskell proxy-POC.hs Content-Length: 1200593 bytes downloaded: 2408 proxy-POC.hs: user error (sizes differ) real 0m1.210s user 0m0.556s sys 0m0.052s vvv@takeshi:~/src$ time runhaskell -DSTRICT proxy-POC.hs Content-Length: 1200593 bytes downloaded: 1200593 real 0m17.956s user 0m0.620s sys 0m0.028s vvv@takeshi:~/src$ runhaskell proxy-POC.hs # repeatable Content-Length: 1200593 bytes downloaded: 2408 proxy-POC.hs: user error (sizes differ) There are only 4 lines that need to be changed (2 in HttpUtils.hs and 2 in Fetch.hs); see the accompanying patch. ...And could anyone explain me, why don't lazy ByteString cause cropped downloads in proxy-free environment? Thank you. -- vvv

3 2

[Hackage] #572: cabal update download too short when through privoxy
by Hackage 18 Sep '09

18 Sep '09

#572: cabal update download too short when through privoxy ---------------------------------+------------------------------------------ Reporter: wolverian | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: Linux | ---------------------------------+------------------------------------------ I have a Privoxy proxy running on localhost, set in the $http_proxy env var. Running cabal update gets a partial 00-index.tar.gz file: {{{ wolverian@pupupu:~ (master)$ cabal update -v3 Downloading the latest package list from hackage.haskell.org Sending: GET /packages/archive/00-index.tar.gz HTTP/1.1 User-Agent: cabal-install/0.6.2 Host: hackage.haskell.org proxy uri host: 127.0.0.1, port: :8118 Creating new connection to 127.0.0.1:8118 Received: HTTP/1.1 200 OK Date: Mon, 03 Aug 2009 14:10:46 GMT Server: Apache/2.2.3 (Debian) Last-Modified: Mon, 03 Aug 2009 13:56:03 GMT ETag: "595494-111c43-216dc2c0" Accept-Ranges: bytes Content-Length: 1121347 Connection: close Content-Type: application/x-tar Content-Encoding: x-gzip Downloaded to /home/wolverian/.cabal/packages/hackage.haskell.org/00-index.tar.gz cabal: user error (Codec.Compression.Zlib: premature end of compressed stream) }}} The resulting file is 1078 bytes. Running wget on the file gives: {{{ wolverian@pupupu:~ (master)$ LANG=C wget --server-response hackage.haskell.org/packages/archive/00-index.tar.gz --2009-08-03 17:12:26-- http://hackage.haskell.org/packages/archive/00-index.tar.gz Connecting to 127.0.0.1:8118... connected. Proxy request sent, awaiting response... HTTP/1.1 200 OK Date: Mon, 03 Aug 2009 14:12:26 GMT Server: Apache/2.2.3 (Debian) Last-Modified: Mon, 03 Aug 2009 13:56:03 GMT ETag: "595494-111c43-216dc2c0" Accept-Ranges: bytes Content-Length: 1121347 Connection: close Content-Type: application/x-tar Content-Encoding: x-gzip Length: 1121347 (1.1M) [application/x-tar] Saving to: `00-index.tar.gz.3' 100%[===================================>] 1,121,347 84.8K/s in 12s 2009-08-03 17:12:38 (90.4 KB/s) - `00-index.tar.gz.3' saved [1121347/1121347] }}} The file is downloaded correctly. Versions: cabal-install is 0.6.2, Cabal is 1.6.0.2, and I have HTTP version 4000.0.7 installed, though I am not sure if that is the one cabal- install is compiled against. GHC is 6.10.3. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/572> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

patch applied (cabal): Fix pretty printing of version ranges to use parens in the right places
by Duncan Coutts 17 Sep '09

17 Sep '09

Wed Sep 16 21:26:12 PDT 2009 Duncan Coutts <duncan(a)haskell.org> * Fix pretty printing of version ranges to use parens in the right places Ignore-this: 198737aa806fa92774494f6e33344a84 M ./Distribution/Version.hs -17 +14 M ./tests/Test/Distribution/Version.hs +41 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20090917042612-adfee-882b89eb…

1 0

patch applied (cabal): Fix the depth calculation for the version range expression check
by Duncan Coutts 17 Sep '09

17 Sep '09

Wed Sep 16 20:27:48 PDT 2009 Duncan Coutts <duncan(a)haskell.org> * Fix the depth calculation for the version range expression check Ignore-this: da1f0fefd17c1269f39e93e4623dc274 Previously it was complaining about expressions like >= 2 && < 3 because internally >= is represented in terms of >, == and ||. The fix is to use new fold that gives a view with the extra syntactic sugar so that <= and <= can be counted as one. M ./Distribution/PackageDescription/Check.hs -2 +4 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20090917032748-adfee-4f44bc30…

1 0