This package does not build with Cabal 3.10

[kindaro]

what I do

% git remote -v
origin	https://github.com/lpsmith/split-channel.git (fetch)
origin	https://github.com/lpsmith/split-channel.git (push)
% git rev-parse @
1fe04a46a4f12e10fe378c690258f6f2cb6ab1a3
% cabal --version
cabal-install version 3.10.2.1
compiled using version 3.10.2.1 of the Cabal library
% cabal build
Resolving dependencies...
Error: cabal: Could not resolve dependencies:
[__0] trying: split-channel-0.2.0.1 (user goal)
[__1] next goal: split-channel:setup.Cabal (dependency of split-channel)
[__1] rejecting: split-channel:setup.Cabal-3.8.1.0/installed-3.8.1.0
(conflict: split-channel => split-channel:setup.Cabal>=1.7 && <1.25)
[__1] skipping: split-channel:setup.Cabal-3.12.0.0,
split-channel:setup.Cabal-3.10.3.0, split-channel:setup.Cabal-3.10.2.1,
split-channel:setup.Cabal-3.10.2.0, split-channel:setup.Cabal-3.10.1.0,
split-channel:setup.Cabal-3.8.1.0, split-channel:setup.Cabal-3.6.3.0,
split-channel:setup.Cabal-3.6.2.0, split-channel:setup.Cabal-3.6.1.0,
split-channel:setup.Cabal-3.6.0.0, split-channel:setup.Cabal-3.4.1.0,
split-channel:setup.Cabal-3.4.0.0, split-channel:setup.Cabal-3.2.1.0,
split-channel:setup.Cabal-3.2.0.0, split-channel:setup.Cabal-3.0.2.0,
split-channel:setup.Cabal-3.0.1.0, split-channel:setup.Cabal-3.0.0.0,
split-channel:setup.Cabal-2.4.1.0, split-channel:setup.Cabal-2.4.0.1,
split-channel:setup.Cabal-2.4.0.0, split-channel:setup.Cabal-2.2.0.1,
split-channel:setup.Cabal-2.2.0.0, split-channel:setup.Cabal-2.0.1.1,
split-channel:setup.Cabal-2.0.1.0, split-channel:setup.Cabal-2.0.0.2 (has the
same characteristics that caused the previous version to fail: excluded by
constraint '>=1.7 && <1.25' from 'split-channel')
[__1] rejecting: split-channel:setup.Cabal-1.24.2.0,
split-channel:setup.Cabal-1.24.0.0, split-channel:setup.Cabal-1.22.8.0,
split-channel:setup.Cabal-1.22.7.0, split-channel:setup.Cabal-1.22.6.0,
split-channel:setup.Cabal-1.22.5.0, split-channel:setup.Cabal-1.22.4.0,
split-channel:setup.Cabal-1.22.3.0, split-channel:setup.Cabal-1.22.2.0,
split-channel:setup.Cabal-1.22.1.1, split-channel:setup.Cabal-1.22.1.0,
split-channel:setup.Cabal-1.22.0.0, split-channel:setup.Cabal-1.20.0.4,
split-channel:setup.Cabal-1.20.0.3, split-channel:setup.Cabal-1.20.0.2,
split-channel:setup.Cabal-1.20.0.1, split-channel:setup.Cabal-1.20.0.0,
split-channel:setup.Cabal-1.18.1.7, split-channel:setup.Cabal-1.18.1.6,
split-channel:setup.Cabal-1.18.1.5, split-channel:setup.Cabal-1.18.1.4,
split-channel:setup.Cabal-1.18.1.3, split-channel:setup.Cabal-1.18.1.2,
split-channel:setup.Cabal-1.18.1.1, split-channel:setup.Cabal-1.18.1,
split-channel:setup.Cabal-1.18.0, split-channel:setup.Cabal-1.16.0.3,
split-channel:setup.Cabal-1.16.0.2, split-channel:setup.Cabal-1.16.0.1,
split-channel:setup.Cabal-1.16.0, split-channel:setup.Cabal-1.14.0,
split-channel:setup.Cabal-1.12.0, split-channel:setup.Cabal-1.10.2.0,
split-channel:setup.Cabal-1.10.1.0, split-channel:setup.Cabal-1.10.0.0,
split-channel:setup.Cabal-1.8.0.6, split-channel:setup.Cabal-1.8.0.4,
split-channel:setup.Cabal-1.8.0.2, split-channel:setup.Cabal-1.6.0.3,
split-channel:setup.Cabal-1.6.0.2, split-channel:setup.Cabal-1.6.0.1,
split-channel:setup.Cabal-1.4.0.2, split-channel:setup.Cabal-1.4.0.1,
split-channel:setup.Cabal-1.4.0.0, split-channel:setup.Cabal-1.2.4.0,
split-channel:setup.Cabal-1.2.3.0, split-channel:setup.Cabal-1.2.2.0,
split-channel:setup.Cabal-1.2.1, split-channel:setup.Cabal-1.1.6,
split-channel:setup.Cabal-1.24.1.0 (constraint from minimum version of Cabal
used by Setup.hs requires >=3.8)
[__1] fail (backjumping, conflict set: split-channel,
split-channel:setup.Cabal)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: split-channel:setup.Cabal,
split-channel

what should happen

Running cabal build should build the package.

[kindaro]

I can build this package after removing Setup.hs and updating cabal-version in split-channel.cabal to 3.0. I am not sure what the custom Setup.hs is doing so maybe the maintainers can offer a more careful solution.