-
Notifications
You must be signed in to change notification settings - Fork 704
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
process >= 1.6.14
requires ghc-9.2.4
to be built again, which causes error
#8489
Comments
alex
, happy
are missing, then fatal error happens in GHC moduleprocess >= 1.6.14
requires ghc-9.2.4
to be built again, which causes error
What version of cabal do you use? With your cabal file I get: > cabal test pulp-commons
Resolving dependencies...
Error: cabal: The test command is for running test suites, but the target
'pulp-commons' refers to the library pulp-commons from the package
pulp-commons-0. Also, please try to post reproducers that's easy to use. E.g. a git repository that we could clone or an archive would make our life much easier than the incomplete cabal file that you posted so far. |
I was able to reproduce it (I think) with this
And doing
Maybe, the |
Ouch, sorry for not having a proper reproducer. I would try to give an easier-to-use reproducer next time I open an issue! |
So there is a list of non-upgradable packages hardwired here and i think it just lacks ghc itself!
(also i think the comment above this line in the source about needing to update a second place is now outdated and this is the only source of truth?) |
@Abastro are you interested in submitting a patch by any chance? |
I think that at least all of "ghc" "ghc-boot" and "ghci" should be added fwiw. |
Let me try opening a PR for adding these. |
That list seems redundant with the list in Distribution.Client.Dependency. It looks like cabal avoids choosing a source version for packages in either list. We should probably remove the list in Distribution.Solver.Modular.Solver, because the list in Distribution.Client.Dependency is implemented using constraints, which are more general, and it is better to pass constraints into the solver than hard code non-upgradable package names in the solver. |
I think I just hit this issue in
|
Blame for this extra constraint goes to 95cf762. (Ping @robx.)
This extra constraint seems to have been removed from |
My problems would not be addressed by the linked PR, so maybe I open a new issue: |
BTW, #8342 already fixed the underlying problem (the bound on |
…8501) * ghc, ghc-boot, ghci should be non-upgradable * (PR number) * Checks for depending on GHC * Also tests ghc-boot, ghci * Simplify condition * Added "rejecting:" bits * Synced cabal-install-solver's list & Simplify testcase * Updated changelog * Fully remove base dependency in test dbNonUpgrade Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
…8489) (haskell#8501) * ghc, ghc-boot, ghci should be non-upgradable * (PR number) * Checks for depending on GHC * Also tests ghc-boot, ghci * Simplify condition * Added "rejecting:" bits * Synced cabal-install-solver's list & Simplify testcase * Updated changelog * Fully remove base dependency in test dbNonUpgrade Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Describe the bug
At some point, I added
process >= 1.6.14
as that version fixed a bug.After a while, I tried to build a test and it failed:
I use
hspec
as dependency, which hasghc
package as a transitive dependency.Then, it tries to build
ghc-9.2.4
package instead of using what should be already available.First it complained that
alex
thenhappy
is missing. After installing those, it error-ed out while trying to build GHC modules.To Reproduce
Steps to reproduce the behavior:
pulp-commons.cabal
:Ran command
Then, e..g this happens when
alex
is not installedExpected behavior
If
ghc
package is never supposed to be built, proper error messages should have complained about the version bounds - it took quite some time to .If
ghc
package could be built, it should build successfully without errors.System information
Additional context
In the dependencies of the test, when I have
process
part commented out like:then existing
ghc
package is used, and build proceeds normally.The text was updated successfully, but these errors were encountered: