Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

cabal v2-install (local) executable is affected by default environment #6410

Closed
phadej opened this issue Dec 9, 2019 · 0 comments · Fixed by #6428
Closed

cabal v2-install (local) executable is affected by default environment #6410

phadej opened this issue Dec 9, 2019 · 0 comments · Fixed by #6428

Comments

@phadej
Copy link
Collaborator

phadej commented Dec 9, 2019

Describe the bug

default environment affects at least (local) executable installation.

To Reproduce

  1. Create an environment with e.g. aeson-1.4.5.0.
  2. Try to install an executable which requires ^>= aeson-1.4.6.0, e.g. cabal v2-install cabal-deps
    (its dependency, cabal-install-parsers, wants the latest aeson).
cabal: Could not resolve dependencies:
[__0] next goal: aeson (user goal)
[__0] rejecting: aeson-1.4.6.0 (constraint from user target requires
==1.4.5.0)
[__0] trying: aeson-1.4.5.0
[__1] trying: cabal-bundler-0.1 (user goal)
[__2] next goal: cabal-install-parsers (dependency of cabal-bundler)
[__2] rejecting: cabal-install-parsers-0.2, cabal-install-parsers-0.1
(conflict: aeson==1.4.5.0, cabal-install-parsers => aeson^>=1.4.6.0)

Expected behavior

Installation should just work.

System information

  • cabal-install-3.0.0.0
@phadej phadej added this to the 3.0.1.0 milestone Dec 14, 2019
phadej added a commit to phadej/cabal that referenced this issue Dec 14, 2019
Resolve haskell#5919
Resolve haskell#6410

Add `withProjectOrGlobalConfigIgn` to unify the behaviour with `-z` in `cabal
repl`
phadej added a commit to phadej/cabal that referenced this issue Dec 14, 2019
Resolve haskell#5919
Resolve haskell#6410

Add `withProjectOrGlobalConfigIgn` to unify the behaviour with `-z` in `cabal
repl`
phadej added a commit to phadej/cabal that referenced this issue Dec 14, 2019
Resolve haskell#5919
Resolve haskell#6410

Add `withProjectOrGlobalConfigIgn` to unify the behaviour with `-z` in `cabal
repl`
netbsd-srcmastr pushed a commit to NetBSD/pkgsrc that referenced this issue Apr 25, 2021
3.4.0.0 Oleg Grenrus <oleg.grenrus@iki.fi> February 2021
	* See https://github.com/haskell/cabal/blob/master/release-notes/cabal-install-3.4.0.0.md

3.2.0.0 Herbert Valerio Riedel <hvr@gnu.org> April 2020
	* `v2-build` (and other `v2-`prefixed commands) now accept the
	  `--benchmark-option(s)` flags, which pass options to benchmark executables
	  (analogous to how `--test-option(s)` works). (#6209)
	* Add solver optimization to skip a version of a package if it does not resolve
	  any conflicts encountered in the last version, controlled by flag
	  '--fine-grained-conflicts'. (#5918)
	* `cabal v2-exec` doesn't fail in clean package (#6479)
	* Show full ABI hash for installed packages in solver log (#5892)
	* Create incoming directory even for empty packages (#4130)
	* Start GHCi with `main-is` module in scope (#6311)
	* Implement `--benchmark-options` for `v2-bench` (#6224)
	* Fix store-dir in ghc env files generated by `cabal install --lib
	  --package-env` (#6298)
	* `cabal v2-run` works with `.lhs` files (#6134)
	* `subdir` in source-repository-package accepts multiple entries (#5472)

3.0.1.0 Herbert Valerio Riedel <hvr@gnu.org> April 2020
	* Create store incoming directory
	  ([#4130](haskell/cabal#4130))
	* `fetchRepoTarball` output is not marked
	  ([#6385](haskell/cabal#6385))
	* Update `setupMinCabalVersionConstraint` for GHC-8.8
	  ([#6217](haskell/cabal#6217))
	* Implement `cabal install --ignore-project`
	  ([#5919](haskell/cabal#5919))
	* `cabal install executable` solver isn't affected by default
	  environment contents
	  ([#6410](haskell/cabal#6410))
	* Use `lukko` for file locking
	  ([#6345](haskell/cabal#6345))
	* Use `hackage-security-0.6`
	  ([#6388](haskell/cabal#6388))
	* Other dependency upgrades
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant