You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are quite a few fake-package issues. The user experience around this is not good when a cabal command expecting [TARGETS] is called without a target.
$ cabal repl
Resolving dependencies...
Error: [Cabal-7076]
Internal error when trying to open a repl for the package fake-package-0.
The package is not in the set of available targets for the project plan, which
would suggest an inconsistency between readTargetSelectors and resolveTargets.
$ cabal repl containers
Resolving dependencies...
Build profile: -w ghc-9.8.2 -O1
In order, the following will be built (use -v for more details):
- containers-0.6.8 (interactive) (lib) (configuration changed)
...
Ok, 37 modules loaded.
ghci>
There is a cabal.project that we could use to list possible [TARGETS], such as those shown by #9744.
Just noticed this today on an internal project. Anything I can collect and share to help? I thought this used to work with cabal-install 3.10, but the internal project now requires 3.12 so I haven't tested an older commit, yet.
EDIT: No, this did NOT work on 3.10. It just had a different error message that I found easier to understand.
This can be reproduced on top of srid/haskell-multi-nix@9286987 by adding multi-repl: True to the cabal.project file followed by nix develop -c cabal repl:
Error: [Cabal-7076]
Internal error when trying to open a repl for the package fake-package-0. The package is not in the set of available targets for the project plan, which would suggest an inconsistency between readTargetSelectors and resolveTargets.
There are quite a few
fake-package
issues. The user experience around this is not good when a cabal command expecting[TARGETS]
is called without a target.With haskell/containers@c651094;
There is a
cabal.project
that we could use to list possible[TARGETS]
, such as those shown by #9744.The text was updated successfully, but these errors were encountered: