February 2011 - cabal-devel

[Hackage] #782: When building a plan, use installed package dependencies in preference to those from Hackage
by Hackage 07 Apr '12

07 Apr '12

#782: When building a plan, use installed package dependencies in preference to those from Hackage ---------------------------------+------------------------------------------ Reporter: batterseapower | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ I was installing a package, let us call it foo. This package depended on a package foo', which in turn depended on bar, which in turn depended on baz < 0.3, but baz 0.3 was the default that came with the newer version of GHC I had just installed. Thus, I cabal-unpacked bar and bumped the baz dependency to < 0.4, **without changing the baz version number** since this was just a private change. This built and installed just fine with the new baz. I then went back to cabal install foo. I expected that cabal-install would just install foo' and then foo in that order. Instead, it tried to install baz 0.2, then bar, then foo', then foo. This seems stupid because I already had a perfectly acceptable bar installed. Why didn't Cabal just reuse that? It seems as if it is resolving dependencies by looking at the dependency information for bar **from the Hackage database** rather than the dependencies **from the installed bar**. The workaround is to go back to the unpacked bar and bump the version number, then reinstall it. Now when you install foo the installed baz is used as expected. It would be cool if this worked as expected without bumping the version number, because having to bump the version number even if not making a Hackage release is tiresome. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/782> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #731: Custom Build-type with --package-db and --global encounters runtime error
by Hackage 28 Mar '12

28 Mar '12

#731: Custom Build-type with --package-db and --global encounters runtime error ---------------------------------+------------------------------------------ Reporter: cygnus | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.4 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: 6.12.2 Platform: Linux | ---------------------------------+------------------------------------------ To reproduce: * Run `cabal init`, change `Build-type` to `Custom` (`Setup.hs` already provided by `cabal init`) * Run `ghc-pkg init db` * Run `cabal configure --package-db=./db --global` * Output: {{{ Resolving dependencies... cabal: internal error: unexpected package db stack }}} In `cabal-install-0.8.2`, this appears to be caused by the code on lines 112-114 of `Distribution.Client.Configure`: {{{ usePackageDB = if UserPackageDB `elem` packageDBs then packageDBs else packageDBs ++ [UserPackageDB] }}} in combination with the code on lines 297-306 of `Distribution.Client.SetupWrapper`: {{{ ghcPackageDbOptions :: PackageDBStack -> [String] ghcPackageDbOptions dbstack = case dbstack of (GlobalPackageDB:UserPackageDB:dbs) -> concatMap specific dbs (GlobalPackageDB:dbs) -> "-no-user-package-conf" : concatMap specific dbs _ -> ierror where specific (SpecificPackageDB db) = [ "-package-conf", db ] specific _ = ierror ierror = error "internal error: unexpected package db stack" }}} Essentially, the order of the package databases in the stack is not as expected since the list already contains a `SpecificPackageDB` when the `UserPackageDB` is appended. (Note: this applies to GHC 6.12.3 and Cabal 1.8.0.6 on my system, but I could not select those versions in the ticket properties.) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/731> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #675: template-haskell cannot be upgraded (broken data-accessor-template)
by Hackage 05 Mar '12

05 Mar '12

#675: template-haskell cannot be upgraded (broken data-accessor-template) ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: 6.12.1 Platform: | ---------------------------------+------------------------------------------ data-accessor-template-0.2.1.3 has flags in the cabal file on template- haskell versions, which makes it broken for cabal-install on ghc-6.12: cabal-install tries to install template-haskell-2.3, which fails (and it can't be expected to succeed because TH is integrated into ghc due to quotes) You can work around the build failure with: {{{ cabal install data-accessor-template --constraint='template-haskell >= 2.4' }}} cabal-install ought to know that template-haskell isn't something it should install (as it does with base). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/675> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #665: Confusion situation when linking ./dist/setup/setup is interrupted
by Hackage 05 Mar '12

05 Mar '12

#665: Confusion situation when linking ./dist/setup/setup is interrupted ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.3 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ If one accidentally interrupts cabal when it's linking `./dist/setup/setup` then you can end up with the file existing it not being executable. This leads to a confusing situation for the user. Running `cabal install` or `cabal configure` will fail silently. Running with -v indicates that something returns exit code 127. This corresponds to a permission error when trying to execute `./dist/setup/setup` Two improvements could be made: * Report the failure to execute `./dist/setup/setup` * If ghc is interrupted when creating `./dist/setup/setup`, cabal should delete the file, if it exists. That way, cabal will recompile on the next invocation. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/665> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[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