January 2012 - cabal-devel

[Hackage] #799: ./dist/setup/setup without execute bit causes cabal to exit silently with code 127
by Hackage 05 Mar '12

05 Mar '12

#799: ./dist/setup/setup without execute bit causes cabal to exit silently with code 127 ---------------------------------+------------------------------------------ Reporter: rrnewton | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ I ran into this one thanks to Dropbox. All my cabal commands started to fail in the same way all of a sudden (no output, error code 127). A cabal clean -v3 revealed the problem and a chmod +x fixed it. $ cabal clean -v3; echo $? Using external setup method with build-type Custom Creating ./dist/setup (and its parents) Using Cabal library version 1.8.0.6 Using ./Setup.hs as setup script. ./dist/setup/setup clean --verbose=3 127 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/799> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #669: Allow cabal-install's package build location to be set
by Hackage 05 Mar '12

05 Mar '12

#669: Allow cabal-install's package build location to be set ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Apparently some systems mount /tmp such that one cannot create and run executables. This is clearly problematic for cabal-install because it needs somewhere to build packages. http://article.gmane.org/gmane.comp.lang.haskell.cafe/73517 It may be useful for cabal-install to have a config setting to specify where to do package builds (for downloaded packages). If not specified this would default to the temp dir as now. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/669> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #670: cabal-install should warn about common problem after installing progs
by Hackage 05 Mar '12

05 Mar '12

#670: cabal-install should warn about common problem after installing progs ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.3 Severity: normal | Keywords: Difficulty: easy (<4 hours) | Ghcversion: Platform: | ---------------------------------+------------------------------------------ There are a few common problems have when installing programs. * target bindir (or symlink-bindir) is not on the `$PATH` so they cannot run the program after installation. * target bindir is on the `$PATH` but the installed program is masked by the presence of the same named prog in a dir that is earlier on the `$PATH`. For example `/usr/local/bin/cabal` and `~/.cabal/bin/cabal`, the latter might have just been installed but the earlier one will still be picked up. * the shell keeping a cache of name -> path and so not picking up a new program. Eg in the above example, even if `~/.cabal/bin/` comes first on the `$PATH`, if bash has the mapping `cabal` -> `/usr/local/bin/cabal` then it will not notice when `~/.cabal/bin/cabal` is installed. The fix here is to run `hash -r`. The only time we might want to tell users to run `hash -r` is if the program did not previously exist and if it gets installed in a location that is earlier on the `$PATH` than an existing installed instance (which may thus be in the cache). Sadly we cannot query sh to find out what its cache holds. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/670> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #672: 'cabal init' command should allow for multiple entries in the Category field
by Hackage 05 Mar '12

05 Mar '12

#672: 'cabal init' command should allow for multiple entries in the Category field ---------------------------------+------------------------------------------ Reporter: byorgey | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: Severity: minor | Keywords: init, categories Difficulty: easy (<4 hours) | Ghcversion: Platform: | ---------------------------------+------------------------------------------ The .cabal format allows multiple categories (e.g. Data, Network, Math, etc.) to be listed in the Category field, but the 'cabal init' interactive mode only lets the user choose a single category. It would be nice to allow the user to choose multiple categories. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/672> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 6

[Hackage] #673: cabal init: fail gracefully if bogus files are found during recursive search for source code
by Hackage 05 Mar '12

05 Mar '12

#673: cabal init: fail gracefully if bogus files are found during recursive search for source code ---------------------------------+------------------------------------------ Reporter: byorgey | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: Severity: normal | Keywords: init, search, file, crash Difficulty: easy (<4 hours) | Ghcversion: 6.12.1 Platform: Mac OS | ---------------------------------+------------------------------------------ cabal init does a recursive search looking for things that look like Haskell modules to be added to the exports list. The following error messages were reported by Ivan Miljenovic: {{{ cabal: /scratch/ghc-6.12.1/distrib/installer-scripts/MacOS: does not exist cabal: /tmp/pulse-a7kaqGHss6Yh/native: inappropriate type }}} Not sure exactly what causes these errors, but in any case cabal init should not crash. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/673> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #681: cabal-install init should not overwrite files without good reason
by Hackage 05 Mar '12

05 Mar '12

#681: cabal-install init should not overwrite files without good reason ---------------------------------+------------------------------------------ Reporter: ezyang | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.2 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ If you run "cabal init" in a directory with an already existing .cabal file, it will happily overwrite the old version without asking you. It should detect that a file exists and ask you before writing it out (or even prompting you for info). Alternatively, it could fill up it's defaults using the existing .cabal file. Furthermore, if you pass -n for non-interactive mode, cabal can't ask whether or not the user wanted to overwrite, so probably adding a --force flag is in order. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/681> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #682: 'cabal init' should try to set 'main-is' for executables
by Hackage 05 Mar '12

05 Mar '12

#682: 'cabal init' should try to set 'main-is' for executables ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Currently, `cabal init` will find modules and add them to the `exposed- modules` of a library. It should try to do something similar for executables. The `main-is` field is required for executables and any `other-modules` also need to be listed. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/682> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #685: cabal install does not work in /tmp/
by Hackage 05 Mar '12

05 Mar '12

#685: cabal install does not work in /tmp/ ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.3 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Wanting to to build darcs 2.4.3, I downloaded the tarball ( http://wiki.darcs.net/Releases/2.4 ) and uncompressed it in /tmp/ to run cabal install. I got the following error : cabal: Error: some packages failed to install: darcs-2.4.3 failed during the configure step. The exception was: ExitFailure 127 See http://hpaste.org/fastcgi/hpaste.fcgi/view?id=25412#a25412 for a full verbose log, but i think there is nothing informative to it. However, if I do "rm -fr dist" and try cabal install again, darcs build fine. Also, if I try in $HOME, cabal install works directly. Here are the versions of the software I'm using: cabal-install version 0.8.2 using version 1.8.0.4 of the Cabal library ghc 6.12.1 Linux distribution: Ubuntu 10.04 (Lucid Lynx). I hope this will help you! -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/685> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #686: cabal install - Codec.Compression.Zlib: incorrect header check
by Hackage 05 Mar '12

05 Mar '12

#686: cabal install - Codec.Compression.Zlib: incorrect header check ---------------------------------+------------------------------------------ Reporter: Monsikos | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.2 Severity: normal | Keywords: Zlib Difficulty: unknown | Ghcversion: 6.12.1 Platform: Windows | ---------------------------------+------------------------------------------ The command "cabal install packagename" fails with : "Codec.Compression.Zlib: incorret header check". The message appears while trying to extract the tar.gz file. I have manually updated Cabal (1.8.0.2), cabal-install(0.8.2) and zlib(0.5.2.0) but the error remains. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/686> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 12

[Hackage] #688: hard-coded path to configuration file
by Hackage 05 Mar '12

05 Mar '12

#688: hard-coded path to configuration file ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.2 Severity: minor | Keywords: Difficulty: easy (<4 hours) | Ghcversion: 6.10.4 Platform: Linux | ---------------------------------+------------------------------------------ I want to be able to tell {{{cabal}}} to read the configuration from a different place than {{{$HOME/.cabal/config}}}. The ultimate goal is to get rid of the non-standard {{{.cabal}}} directory altogether, so far careful {{{--package-db}}}/{{{--prefix}}} etc. juggling served me well; {{{config}}} is the last remaining file there. {{{ > cabal --version cabal-install version 0.8.2 using version 1.8.0.2 of the Cabal library }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/688> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 8