June 2011 - cabal-devel

[Hackage] #818: cabal sdist warns about optimization levels
by Hackage 03 Mar '12

03 Mar '12

#818: cabal sdist warns about optimization levels ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.10.1.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ For some reason 'cabal sdist' dislikes fast code so much that it tells me not to use -O2. What does it know about my needs and my project? See below for an example: {{{ $ cabal sdist Distribution quality warnings: 'ghc-options: -O2' is rarely needed. Check that it is giving a real benefit and not just imposing longer compile times on your users. }}} Is there a way to disable this warning in my .cabal file? If not, can the warning please be removed? It doesn't seems appropriate for sdist to tell me which compiler flags I should use to optimize my code. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/818> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #820: cabal-install clobbers itself on multi-arch platforms
by Hackage 03 Mar '12

03 Mar '12

#820: cabal-install clobbers itself on multi-arch platforms ---------------------------------+------------------------------------------ Reporter: bos | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ On my Mac, I have 32-bit and 64-bit versions of GHC 7.0.2 installed, and cabal installs the object and interface files into the same directory. The {{{$arch}}} variable looks like it should do the right thing, but in fact it's expanded to whatever architecture cabal-install was built for, not the architecture that's supported by GHC itself. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/820> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #804: support remote .cabal files in cabal info
by Hackage 03 Mar '12

03 Mar '12

#804: support remote .cabal files in cabal info ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: enhancement | Status: new Priority: low | Milestone: Component: cabal-install tool | Version: Severity: normal | Keywords: Difficulty: normal | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Currently, `cabal info` supports local .cabal files and remote tarballs, but not remote .cabal files. The [http://hackage.haskell.org/package/lscabal lscabal] program supports remote .cabal file target like: {{{ $ lscabal http://code.haskell.org/xmonad/xmonad.cabal XMonad XMonad.Main }}} Is this useful? Presumably it would also need a more general query language to pull out the fields that the user is interested in. Note that `lscabal` only lists exposed modules and only unconditional ones (e.g. not ones that are platform dependent). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/804> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #834: cabal should detect case errors in build-depends:
by Hackage 03 Mar '12

03 Mar '12

#834: cabal should detect case errors in build-depends: ---------------------------------+------------------------------------------ Reporter: cmh | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ for example, with a foo.cabal file containing: build depends: http >= 4000 Resolving dependencies... cabal: cannot configure foo-0.0.1. It requires http >=4000 There is no available version of http that satisfies >=4000 The solution is of course to specify HTTP, but the user may be led to believe that there is a version problem, which is confusing. Perhaps a message such as - "Did you mean package HTTP" - Would be appropriate. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/834> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #849: [PATCH] Store licenses in text files instead of code.
by Hackage 03 Mar '12

03 Mar '12

#849: [PATCH] Store licenses in text files instead of code. ----------------------------+----------------------------------------------- Reporter: refold | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- This shaves 300 KiB off the final executable size and makes it slightly easier to add new license types (just drop the text file under %SRCDIR%/licenses and modify the 'licenseFile' function in Distribution.Client.Init.hs). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/849> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 9

[Hackage] #855: cabal behind proxy
by Hackage 03 Mar '12

03 Mar '12

#855: cabal behind proxy ---------------------------------+------------------------------------------ Reporter: sms | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.10.1.0 Severity: normal | Keywords: proxy, authentication Difficulty: unknown | Ghcversion: Platform: Windows | ---------------------------------+------------------------------------------ I'm getting an error No action for prompting/generating user+password credentials provided (use: setAuthorityGen); returning Nothing when using 'cabal update' being behind proxy that is requiring authentication. My login and password contain \ and @ symbols, so I have them escaped in HTTP_PROXY environment variable: HTTP_PROXY=http://domain%5Cuser:passw%40rd@proxy.host:3128 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/855> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #667: Improve tools to manage ad-hoc package releases
by Hackage 05 Jan '12

05 Jan '12

#667: Improve tools to manage ad-hoc package releases ------------------------------+--------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: miscellaneous | Version: Severity: normal | Keywords: Difficulty: project(> week) | Ghcversion: Platform: | ------------------------------+--------------------------------------------- Hackage is suited for major software releases by package maintainers. It is not suited to distributing betas, daily snapshots or random forks, or patches of existing releases. For example a user may have some patch or bugfix for a package that they need. It takes time for maintainers to review and integrate these. Sometimes maintainers have little time, or they disagree with a patch approach or quality. It is right that maintainers have control over what is released on hackage. However there is a need for decentralised, ad-hoc and short term releases. We do not want to encourage the pollution of the package namespace with lots of short-term forks. One solution is to let users post package forks on their own webspace. We would want to extend cabal so that people can run: {{{ cabal install http://code.haskell.org/~user/foo/foo-fork-to-fix- blah-1.0.1.tar.gz }}} This makes it very decentralised. We may want to add some feature to hackage package pages to link to third-party forks. In addition to hosting and installing single packages it would be useful to be able to publish package collections. Of course this is exactly what a hackage archive is. We should provide easy tools to make and manage hackage archives that can be hosted on dumb http file servers. Going one step further, the hackage index format should be extended to make it more RESTful by including links to tarballs rather than just assuming that tarballs are found relative to the index file using some fixed layout. This would allow people to publish indexes that span multiple servers. This gets close to the concept of a package "search path" promoted by the searchpath project (http://searchpath.org/) Additonally, an index should allow us to point to source control repos rather than just to release tarballs. This kind of index would be useful for nighly builds. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/667> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #859: network doesn't build with 1.11.0
by Hackage 05 Jan '12

05 Jan '12

#859: network doesn't build with 1.11.0 ----------------------------+----------------------------------------------- Reporter: tibbe | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- The network package from http://github.com/haskell/network (the "stable" branch) doesn't build with the current HEAD but does build with 1.10.2. {{{ $ ./Setup -V Cabal library version 1.11.0 $ ./Setup configure --user -v Configuring network-2.3.0.4... Dependency base >=3 && <4.4: using base-4.3.1.0 Dependency bytestring <1.0: using bytestring-0.9.1.10 Dependency parsec >=2.0 && <3.2: using parsec-3.1.1 Dependency unix ==2.*: using unix-2.4.2.0 Using Cabal-1.11.0 compiled by ghc-7.0 Using compiler: ghc-7.0.3 Using install prefix: /home/tibell/.cabal Binaries installed in: /home/tibell/.cabal/bin Libraries installed in: /home/tibell/.cabal/lib/network-2.3.0.4/ghc-7.0.3 Private binaries installed in: /home/tibell/.cabal/libexec Data files installed in: /home/tibell/.cabal/share/network-2.3.0.4 Documentation installed in: /home/tibell/.cabal/share/doc/network-2.3.0.4 Using alex version 2.3.1 found on system at: /home/tibell/bin/alex Using ar found on system at: /usr/bin/ar No c2hs found Using cpphs version 1.11 found on system at: /home/tibell/.cabal/bin/cpphs No ffihugs found Using gcc version 4.4.3 found on system at: /usr/bin/gcc Using ghc version 7.0.3 found on system at: /home/tibell/bin/ghc Using ghc-pkg version 7.0.3 found on system at: /home/tibell/bin/ghc-pkg No greencard found Using haddock version 2.9.2 found on system at: /home/tibell/bin/haddock Using happy version 1.18.2 found on system at: /home/tibell/bin/happy No hmake found Using hsc2hs version 0.67 found on system at: /home/tibell/bin/hsc2hs Using hscolour version 1.16 found on system at: /home/tibell/.cabal/bin/HsColour No hugs found No jhc found Using ld found on system at: /usr/bin/ld No lhc found No lhc-pkg found No nhc98 found Using pkg-config version 0.22 found on system at: /usr/bin/pkg-config Using ranlib found on system at: /usr/bin/ranlib Using strip found on system at: /usr/bin/strip Using tar found on system at: /bin/tar No uhc found sh configure --with-compiler=ghc --with-gcc=/usr/bin/gcc configure: WARNING: unrecognized options: --with-compiler, --with-gcc checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for an ANSI C-conforming const... yes checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking for stdlib.h... (cached) yes checking for sys/types.h... (cached) yes checking for unistd.h... (cached) yes checking winsock2.h usability... no checking winsock2.h presence... no checking for winsock2.h... no checking ws2tcpip.h usability... no checking ws2tcpip.h presence... no checking for ws2tcpip.h... no checking wspiapi.h usability... no checking wspiapi.h presence... no checking for wspiapi.h... no checking arpa/inet.h usability... yes checking arpa/inet.h presence... yes checking for arpa/inet.h... yes checking netdb.h usability... yes checking netdb.h presence... yes checking for netdb.h... yes checking netinet/in.h usability... yes checking netinet/in.h presence... yes checking for netinet/in.h... yes checking netinet/tcp.h usability... yes checking netinet/tcp.h presence... yes checking for netinet/tcp.h... yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking sys/uio.h usability... yes checking sys/uio.h presence... yes checking for sys/uio.h... yes checking sys/un.h usability... yes checking sys/un.h presence... yes checking for sys/un.h... yes checking for readlink... yes checking for symlink... yes checking for struct msghdr.msg_control... yes checking for struct msghdr.msg_accrights... no checking for struct sockaddr.sa_len... no checking for in_addr_t in netinet/in.h... yes checking for SO_PEERCRED and struct ucred in sys/socket.h... yes checking for _head_libws2_32_a in -lws2_32... no checking for getaddrinfo... yes checking for gai_strerror... yes checking whether AI_ADDRCONFIG is declared... yes checking whether AI_ALL is declared... yes checking whether AI_NUMERICSERV is declared... yes checking whether AI_V4MAPPED is declared... yes checking for sendfile in sys/sendfile.h... yes checking for sendfile in sys/socket.h... no checking for gethostent... yes configure: creating ./config.status config.status: creating network.buildinfo config.status: creating include/HsNetworkConfig.h config.status: include/HsNetworkConfig.h is unchanged configure: WARNING: unrecognized options: --with-compiler, --with-gcc Reading parameters from ./network.buildinfo $ ./Setup build -v Reading parameters from ./network.buildinfo creating dist/build creating dist/build/autogen Building network-2.3.0.4... Preprocessing library network-2.3.0.4... creating dist/build/Network /home/tibell/bin/hsc2hs --cc=/usr/bin/gcc --ld=/usr/bin/gcc --cflag=-fno- stack-protector --lflag=-fno-stack-protector --cflag=-D__GLASGOW_HASKELL__=700 --cflag=-Dlinux_BUILD_OS --cflag=-Dlinux_HOST_OS --cflag=-Dx86_64_BUILD_ARCH --cflag=-Dx86_64_HOST_ARCH --cflag=-Iinclude --cflag=-I/home/tibell/lib/ghc-7.0.3/unix-2.4.2.0/include --cflag=-Idist/build/autogen --cflag=-include --cflag=dist/build/autogen/cabal_macros.h --cflag=-Idist/build/autogen --cflag=-include --cflag=dist/build/autogen/cabal_macros.h --cflag=-Idist/build/autogen --cflag=-include --cflag=dist/build/autogen/cabal_macros.h --cflag=-Idist/build/autogen --cflag=-include --cflag=dist/build/autogen/cabal_macros.h --cflag=-I/home/tibell/lib/ghc-7.0.3/bytestring-0.9.1.10/include --cflag=-Idist/build/autogen --cflag=-include --cflag=dist/build/autogen/cabal_macros.h --cflag=-I/home/tibell/lib/ghc-7.0.3/base-4.3.1.0/include --cflag=-Idist/build/autogen --cflag=-include --cflag=dist/build/autogen/cabal_macros.h --cflag=-Idist/build/autogen --cflag=-include --cflag=dist/build/autogen/cabal_macros.h --cflag=-Idist/build/autogen --cflag=-include --cflag=dist/build/autogen/cabal_macros.h --cflag=-I/home/tibell/lib/ghc-7.0.3/include --cflag=-Idist/build/autogen --cflag=-include --cflag=dist/build/autogen/cabal_macros.h --cflag=-I/home/tibell/lib/ghc-7.0.3/include --cflag=-Idist/build/autogen --cflag=-include --cflag=dist/build/autogen/cabal_macros.h --lflag=-L/home/tibell/lib/ghc-7.0.3/unix-2.4.2.0 --lflag=-Wl,-R,/home/tibell/lib/ghc-7.0.3/unix-2.4.2.0 --lflag=-lrt --lflag=-lutil --lflag=-ldl --lflag=-L/home/tibell/.cabal/lib/parsec-3.1.1/ghc-7.0.3 --lflag=-Wl,-R,/home/tibell/.cabal/lib/parsec-3.1.1/ghc-7.0.3 --lflag=-L/home/tibell/.cabal/lib/mtl-2.0.1.0/ghc-7.0.3 --lflag=-Wl,-R,/home/tibell/.cabal/lib/mtl-2.0.1.0/ghc-7.0.3 --lflag=-L/home/tibell/.cabal/lib/transformers-0.2.2.0/ghc-7.0.3 --lflag=-Wl,-R,/home/tibell/.cabal/lib/transformers-0.2.2.0/ghc-7.0.3 --lflag=-L/home/tibell/lib/ghc-7.0.3/bytestring-0.9.1.10 --lflag=-Wl,-R,/home/tibell/lib/ghc-7.0.3/bytestring-0.9.1.10 --lflag=-L/home/tibell/lib/ghc-7.0.3/base-4.3.1.0 --lflag=-Wl,-R,/home/tibell/lib/ghc-7.0.3/base-4.3.1.0 --lflag=-L/home/tibell/lib/ghc-7.0.3/integer-gmp-0.2.0.3 --lflag=-Wl,-R,/home/tibell/lib/ghc-7.0.3/integer-gmp-0.2.0.3 --lflag=-lgmp --lflag=-L/home/tibell/lib/ghc-7.0.3/ghc-prim-0.2.0.0 --lflag=-Wl,-R,/home/tibell/lib/ghc-7.0.3/ghc-prim-0.2.0.0 --lflag=-L/home/tibell/lib/ghc-7.0.3 --lflag=-Wl,-R,/home/tibell/lib/ghc-7.0.3 --lflag=-lm --lflag=-lrt --lflag=-ldl --lflag=-L/home/tibell/lib/ghc-7.0.3 --lflag=-Wl,-R,/home/tibell/lib/ghc-7.0.3 -o dist/build/Network/Socket.hs Network/Socket.hsc Socket.hsc: In function ‘main’: Socket.hsc:1033: error: invalid application of ‘sizeof’ to incomplete type ‘struct ucred’ Socket.hsc:1033: error: invalid application of ‘sizeof’ to incomplete type ‘struct ucred’ Socket.hsc:1033: error: invalid application of ‘sizeof’ to incomplete type ‘struct ucred’ Socket.hsc:1039: error: invalid use of undefined type ‘struct ucred’ Socket.hsc:1040: error: invalid use of undefined type ‘struct ucred’ Socket.hsc:1041: error: invalid use of undefined type ‘struct ucred’ compiling dist/build/Network/Socket_hsc_make.c failed (exit code 1) command was: /usr/bin/gcc -c dist/build/Network/Socket_hsc_make.c -o dist/build/Network/Socket_hsc_make.o -fno-stack-protector -fno-stack- protector -D__GLASGOW_HASKELL__=700 -Dlinux_BUILD_OS -Dlinux_HOST_OS -Dx86_64_BUILD_ARCH -Dx86_64_HOST_ARCH -Iinclude -I/home/tibell/lib/ghc-7.0.3/unix-2.4.2.0/include -Idist/build/autogen -include dist/build/autogen/cabal_macros.h -Idist/build/autogen -include dist/build/autogen/cabal_macros.h -Idist/build/autogen -include dist/build/autogen/cabal_macros.h -Idist/build/autogen -include dist/build/autogen/cabal_macros.h -I/home/tibell/lib/ghc-7.0.3/bytestring-0.9.1.10/include -Idist/build/autogen -include dist/build/autogen/cabal_macros.h -I/home/tibell/lib/ghc-7.0.3/base-4.3.1.0/include -Idist/build/autogen -include dist/build/autogen/cabal_macros.h -Idist/build/autogen -include dist/build/autogen/cabal_macros.h -Idist/build/autogen -include dist/build/autogen/cabal_macros.h -I/home/tibell/lib/ghc-7.0.3/include -Idist/build/autogen -include dist/build/autogen/cabal_macros.h -I/home/tibell/lib/ghc-7.0.3/include -Idist/build/autogen -include dist/build/autogen/cabal_macros.h -I/home/tibell/lib/ghc-7.0.3/include/ }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/859> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 5

[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