Skip to content

merge queue: checking master (d1fc7dc) and #12055 together#12066

Closed
mergify[bot] wants to merge 2 commits into
masterfrom
mergify/merge-queue/b9f4d7c175
Closed

merge queue: checking master (d1fc7dc) and #12055 together#12066
mergify[bot] wants to merge 2 commits into
masterfrom
mergify/merge-queue/b9f4d7c175

Conversation

@mergify

@mergify mergify Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch master (d1fc7dc) and #12055 are queued together for merge.

This pull request has been created by Mergify to check the mergeability of #12055.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

  • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Doctest Cabal
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Meta checks
    • check-neutral = Meta checks
    • check-skipped = Meta checks
  • any of [🛡 GitHub branch protection]:
    • check-success = docs/readthedocs.org:cabal
    • check-neutral = docs/readthedocs.org:cabal
    • check-skipped = docs/readthedocs.org:cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Validate post job
    • check-neutral = Validate post job
    • check-skipped = Validate post job
  • any of [🛡 GitHub branch protection]:
    • check-success = fourmolu
    • check-neutral = fourmolu
    • check-skipped = fourmolu
  • any of [🛡 GitHub branch protection]:
    • check-success = hlint
    • check-neutral = hlint
    • check-skipped = hlint
  • any of [🛡 GitHub branch protection]:
    • check-success = Bootstrap post job
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
  • any of [🛡 GitHub branch protection]:
    • check-success = whitespace
    • check-neutral = whitespace
    • check-skipped = whitespace
  • any of [🛡 GitHub branch protection]:
    • check-success = Check sdist post job
    • check-neutral = Check sdist post job
    • check-skipped = Check sdist post job
  • any of [🛡 GitHub branch protection]:
    • check-success = Changelogs
    • check-neutral = Changelogs
    • check-skipped = Changelogs

Required conditions to stay in the queue:

---
checking_base_sha: d1fc7dcffb68616b45ae004dc805f4328958d5f7
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 12055
    scopes: []
scopes: []
...

TeofilC and others added 2 commits June 28, 2026 23:46
GHC-9.14 ships with base-4.22, since that release of GHC, base is
"reinstallable". This means that we can install a version of base that
is not the one that was shipped with GHC.
In #10982, we extended cabal-install to allow reinstalling base when
GHC>=9.14

Yet, we should *not* allow solving for very old versions of base. Older
versions of base can be picked by the solver, but they are unbuildable
and give confusing error messages.

To solve this, we simply also add a constraint that base must be >=4.22
if we take it to be reinstallable. So, now the error mentions that
versions of base <4.22 are non-reinstallable.

This is an unfortunate hack to resolve this error, but it's the best we
can do.
Alternatively we could try to revise old versions of base so that the
solver does not pick them, but then we would still get a somewhat
confusing error message (old versions of base require such and such a
version of the rts), and it would require that users have a version of
the Hackage tarball that is latter than the revisions.

Resolves #11356
@mergify mergify Bot closed this Jun 30, 2026
@mergify mergify Bot deleted the mergify/merge-queue/b9f4d7c175 branch June 30, 2026 21:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant