We were passing the flag --coverage-for for every library in the package
when building the testsuites.

However, if a particular testsuite doesn't depend on one of the packages
passed with --coverage-for we would crash.

Since we look for the unit ids of all packages given in --coverage-for in the
package database (to find hpc artifacts), if the testsuite builds before
the library this lookup would fail.

The fix is easy: don't pass --coverage-for=<lib> to <testsuite> if
<testsuite> doesn't depend on <lib>. If <lib> is an indirect dependency
of <testsuite> it'll no longer be covered by HPC, but this is a weird
behaviour that I doubt anyone relies on.

Fixes #10046

Filter out -dinitial-unique and -dunique-increment from hash flags

These options shouldn't affect the output of the package and hence
shouldn't affect the store hash of a package.

use fixed cabal version per #10175

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* allow hashable-1.5

* allow tasty-quickcheck 0.11, and in case of cabal-install:test move to ^>=0.11

---------

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Add simple QuickCheck test for solver exceptions

The solver QuickCheck tests can already detect exceptions, but this test is
simpler and easier to debug.

Add MultilineStrings extension

* Update cabal-install-solver synopsis (fix #10183)

* fixup! remove trailing dot

---------

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

reorder Haddock markup for dynprof constructor

Older ghcs don't like it being after the constructor.

* clarify "configure" messages from Cabal

* add changelog

* Apply suggestions from code review

Co-authored-by: Javier Sagredo <jasataco@gmail.com>

---------

Co-authored-by: Javier Sagredo <jasataco@gmail.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

New `extra-files` field for neutral `sdist` files

The new `extra-files` field provides a way to specify extra files that
should be included in sdist, without adding any other semantics
(cf. `extra-source-files` are tracked by `cabal build`).

Resolves #8817.

regenerate bootstrap files without arch-native (backport #10148)

(cherry picked from commit aede6c4e)

Also remove 8.10.7 to match 3.12 branch.

Makefile:  Use `cabal doctest`

* rm-old-base: remove ifdefs for pre-4.13 bases

4.13 and older have fallen out of the support window. Hence this commit
removes code only conditionally included for base 4.13 and older. Some
occasional transitive removals were implied and done in this same commit.

* Remove 8.6.5 from CI and Makefile

* Remove test for GHC <8.6.5

* Update GHC versions mentioned in the user guide

* rm-old-base: use Distribution.Compat.Prelude

The change was likely an artifact of a rebase.

* rm-old-base: restore builds not of cabal itself

The #ifdefs being generated need to be kept here so that projects other
than cabal can be built using older ghc versions and current cabal
versions.

* rm-old-base: restore older catchIO

This needs to be included so running with older bases and ghcs can be
done even while building cabal itself demands recent ghcs.

* Bump base lower bounds to >=4.13

* Update a few package version in the documentation

* rm-old-base: remove Distribution.Compat.Typeable

It's not needed with our currently supported ghcs.

* rm-old-base: restore T6906

---------

Co-authored-by: Andrea Bedini <andrea.bedini@tweag.io>
Co-authored-by: brandon s allbery kf8nh <allbery.b@gmail.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Die if dynamic executable is requested on Windows

Fix write-ghc-environment-files documentation

Fix ForeignLibs test for Windows

make cabal-install integration tests hermetic

They were using the user's config, which is a problem if they don't
have one or if it contains settings that interfere with tests
(such as `documentation: True`).

I'm not entirely certain of this, but it seems to work here. It's
a bit of a hack, though.

Fix Windows tests