Cabal: Spurious warning: The package has an extraneous version range for a dependency on an internal library
% cabal new-build cabal-plan:exe:cabal-plan
Resolving dependencies...
Build profile: -w ghc-8.2.2 -O1
In order, the following will be built (use -v for more details):
- cabal-plan-0.3.0.0 (lib) (first run)
- cabal-plan-0.3.0.0 (lib:topograph) (first run)
- cabal-plan-0.3.0.0 (exe:cabal-plan) (first run)
Configuring library for cabal-plan-0.3.0.0..
Configuring library 'topograph' for cabal-plan-0.3.0.0..
Preprocessing library for cabal-plan-0.3.0.0..
Building library for cabal-plan-0.3.0.0..
Preprocessing library 'topograph' for cabal-plan-0.3.0.0..
Building library 'topograph' for cabal-plan-0.3.0.0..
[1 of 1] Compiling Cabal.Plan ( src/Cabal/Plan.hs, /home/ogre/Documents/shared-haskell/cabal-plan/dist-newstyle/build/x86_64-linux/ghc-8.2.2/cabal-plan-0.3.0.0/build/Cabal/Plan.o )
[1 of 1] Compiling Topograph ( src-topograph/Topograph.hs, /home/ogre/Documents/shared-haskell/cabal-plan/dist-newstyle/build/x86_64-linux/ghc-8.2.2/cabal-plan-0.3.0.0/l/topograph/build/topograph/Topograph.o )
Configuring executable 'cabal-plan' for cabal-plan-0.3.0.0..
Warning: The package has an extraneous version range for a dependency on an
internal library: cabal-plan -any && ==0.3.0.0 && ==0.3.0.0. This version
range includes the current package but isn't needed as the current package's
library will always be used.
There aren't such additional version restriction:
executable cabal-plan
default-language: Haskell2010
other-extensions: RecordWildCards
main-is: src-exe/cabal-plan.hs
other-modules: Paths_cabal_plan
if flag(exe)
-- dependencies w/ inherited version ranges via 'cabal-plan' library
build-depends: cabal-plan
, topograph
....
To help bisecting:
ii cabal-install-head 2.1+git20180202.0.2773999-5~16.04 amd64 Command-line interface for Cabal and Hackage
previous cabal-install-head (from around 2017-01-15) didn't had this issue, IIRC.
phadej
All 31 comments
Yeah this me. My refactor PRs should fix this, but if there are too much for 2.1 should we do something else? You can bisect the test suit to see when.
Ericson2314
on 9 Feb 2018
https://github.com/haskell/cabal/pull/4383 caused this.
Ericson2314
on 9 Feb 2018
@Ericson2314 is it easy (or possible) to fix without big (including data-type) changes?
phadej
on 9 Feb 2018
Actually, there might be. The type changes more help make sure its done correctly than fix the problem in itself. Basically, i need to make sure that checking always comes after whatever elaborates the package-local build tool depends.
Ericson2314
on 9 Feb 2018
And we'd technically need to like phantom type GenericPackageDescription assert its been checked, too, for a real type-directed solution.
Ericson2314
on 9 Feb 2018
@phadej I think what would be easiest is to do the 2.1 branch, land the refactors, find the fix, and then backport it.
Ericson2314
on 9 Feb 2018
@Ericson2314 than I'd opt to revert #4383 in 2.2 branch, this warning is so annoying (and plain wrong), we cannot have release with this either.
EDIT because there's hardly time to review refactoring, at least I don't have. I'm very very sorry.
phadej
on 10 Feb 2018
Also note that #4383 landed only 8 days ago. IMO too late for release.
phadej
on 10 Feb 2018
@phadej No worries, I'm fine with reverting on 2.2. I meant backporting the fix without refactors, to be clear, but agreed that last PR is not that much less invasive than the others.
Ericson2314
on 10 Feb 2018
As of https://github.com/haskell/cabal/pull/5148 this is just a problem on master.
Ericson2314
on 16 Feb 2018
This is going to be a problem for 2.4.
quasicomputational
on 13 Aug 2018
How about just knocking the warning down to an info, as a temporary hack, with the intention of bumping it back up once we're no longer generating the spurious warnings with a proper fix? #4383 seems good and we'd want to keep it in; also, I've got no idea how well a revert would apply six months later (and especially not so close to release...).
quasicomputational
on 13 Aug 2018
How close is 2.4?
Ericson2314
on 13 Aug 2018
AIUI, any day now. Ben Gamari said that the 8.6 beta released a few days ago is likely to be the final GHC pre-release, and making the official GHC 8.6.1 release blocks on Cabal 2.4 being cut.
quasicomputational
on 13 Aug 2018
Ah OK. Then hacks are in order.
Ericson2314
on 13 Aug 2018
The only thing I'd say is https://github.com/haskell/cabal/pull/4265 might fix it. Furthermore, it used to work for all but 7.4, and now that is removed, so I can try rebasing it again. But it's also a bigger change before the release.
Ericson2314
on 13 Aug 2018
I'm remilestoning this from 3.0.1.0 to 3.4. We are again "right before release".
phadej
on 28 Nov 2019
As an additional datapoint, this still occurs on
cabal-install version 3.2.0.0
compiled using version 3.2.0.0 of the Cabal library
jrp2014
on 10 Apr 2020
I have this exact problem:
[nix-shell:~/code/redacted]$ cabal --version
cabal-install version 3.2.0.0
compiled using version 3.2.0.0 of the Cabal library
[nix-shell:~/code/redacted]$ ghc --version
The Glorious Glasgow Haskell Compilation System, version 8.8.3
[nix-shell:~/code/redacted]$ cat redacted.cabal
cabal-version: >=1.10
name: redacted
version: 0.1.0.0
synopsis:
description:
bug-reports:
license: MIT
license-file: LICENSE
author: evertedsphere
maintainer: [email protected]
copyright:
category:
build-type: Simple
extra-source-files: CHANGELOG.md
library
exposed-modules: Lib
other-modules:
other-extensions:
build-depends: base >=4.13 && <4.14
hs-source-dirs: src
default-language: Haskell2010
executable redacted-demo
main-is: Main.hs
other-modules:
other-extensions:
build-depends:
base >=4.13 && <4.14,
redacted
hs-source-dirs: exe
default-language: Haskell2010
test-suite redacted-test
default-language: Haskell2010
type: exitcode-stdio-1.0
hs-source-dirs: test
main-is: Test.hs
build-depends: base >=4.13 && <4.14
evertedsphere
on 10 Apr 2020
FWIW, I've just upgraded Cabal from 3.0 to 3.2 and GHC from 8.6 to 8.10, and I'm hitting this where I wasn't before. I don't think I've made any other changes.
georgefst
on 14 May 2020
After updating cabal-install from 3.0.0.0 to 3.2.0.0, I'm now getting this warning. I have not changed my Cabal file, nor have I changed compilers (I'm using GHC 8.6.5).
evanrelf
on 14 May 2020
Just commenting to cross reference #4203, which references #4169, a duplicate of this issue I just closed.
fgaz
on 22 May 2020
Still a problem (cabal-3.2.0.0 here).
simonmichael
on 28 Jun 2020
Just wanted to chime in: Same here with the sbv package. https://hackage.haskell.org/package/sbv
LeventErkok
on 29 Jul 2020
just discovered this myself. Will this be fixed in cabal 3.4?
cartazio
on 11 Nov 2020
Will this be fixed in cabal 3.4?
No.
phadej
on 12 Nov 2020
Is there any way to suppress it ?
On Thu, Nov 12, 2020 at 3:54 AM Oleg Grenrus notifications@github.com
wrote:
Will this be fixed in cabal 3.4?
No.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/haskell/cabal/issues/5119#issuecomment-725971109, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAABBQQ7SBRFPQMGY5X2XJDSPOWEJANCNFSM4EPLUDEQ
.
cartazio
on 12 Nov 2020
I'll be happy to review a patch fixing the underlying issue.
phadej
on 13 Nov 2020
Where does the bug live ? What’s acceptance criteria for quick vs systematic fix or what do they entail?
cartazio
on 13 Nov 2020
If I knew, I'd probably fixed it already :)
phadej
on 13 Nov 2020
Hrmm: @typedrat @fgaz @Hvr any ideas on where to start?
cartazio
on 13 Nov 2020
Related issues
nh2
·
3Comments
phadej
·
3Comments
p75213
·
4Comments
chrissound
·
4Comments
nomeata
·
4Comments
Most helpful comment
As an additional datapoint, this still occurs on