Allow Cabal-3.8 about postgresql-libpq HOT 4 CLOSED

yeah, I've checked it too and it turned out that I left a freeze file from a previous GHC version and it affected the build plan by disregarding allow-newer, but I interpreted it as if allow-newer wasn't affecting setup-depends the same way as build-depends. False reporting on my side.

from postgresql-libpq.

Done in #29

from postgresql-libpq.

Why is there an upper bound if Setup.hs doesn't have this upper bound applied to the setup logic? This check is destined to fail each time there's a new major GHC release without visible benefits, and it's not possible to override the bound with allow-newer on the receiving side of the package.

from postgresql-libpq.

it's not possible to override the bound with allow-newer on the receiving side of the package.

What do you mean? This works on Cabal 3.8.1.0 and GHC 9.4.2:

cabal get postgresql-libpq
cd postgresql-libpq*
cabal repl --allow-newer=postgresql-libpq:base,postgresql-libpq:Cabal

from postgresql-libpq.