-
Notifications
You must be signed in to change notification settings - Fork 696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"To use ... the package needs to specify at least 'cabal-version: >= 1.18'" ◀ should drop >= #7088
Labels
Comments
juhp
changed the title
"To use ... the package needs to specify at least 'cabal-version: >= 1.18'" <<== should be just 1.18
"To use ... the package needs to specify at least 'cabal-version: >= 1.18'" ◀ should drop >=
Sep 24, 2020
It-Is-Jeremy
pushed a commit
to It-Is-Jeremy/cabal
that referenced
this issue
Oct 8, 2020
3 tasks
It-Is-Jeremy
pushed a commit
to It-Is-Jeremy/cabal
that referenced
this issue
Oct 8, 2020
Update version warnings as per review in haskell#7104. resolves: haskell#7088
ulysses4ever
pushed a commit
to ulysses4ever/cabal
that referenced
this issue
Jun 10, 2022
ulysses4ever
pushed a commit
to ulysses4ever/cabal
that referenced
this issue
Jun 10, 2022
Update version warnings as per review in haskell#7104. resolves: haskell#7088
3 tasks
ulysses4ever
added a commit
to ulysses4ever/cabal
that referenced
this issue
Jun 10, 2022
Co-authored-by: Jeremy Scott <[email protected]> Co-authored-by: Artem Pelenitsyn <[email protected]>
ulysses4ever
added a commit
to ulysses4ever/cabal
that referenced
this issue
Jun 10, 2022
Co-authored-by: Jeremy Scott <[email protected]> Co-authored-by: Artem Pelenitsyn <[email protected]>
ulysses4ever
added a commit
to ulysses4ever/cabal
that referenced
this issue
Jun 11, 2022
Co-authored-by: Jeremy Scott <[email protected]> Co-authored-by: Artem Pelenitsyn <[email protected]> Co-authored-by: Francesco Gazzetta <[email protected]>
GuillaumeGen
pushed a commit
to tweag/cabal
that referenced
this issue
Jun 17, 2022
Co-authored-by: Jeremy Scott <[email protected]> Co-authored-by: Artem Pelenitsyn <[email protected]> Co-authored-by: Francesco Gazzetta <[email protected]>
mergify bot
pushed a commit
that referenced
this issue
Jul 8, 2022
Co-authored-by: Jeremy Scott <[email protected]> Co-authored-by: Artem Pelenitsyn <[email protected]> Co-authored-by: Francesco Gazzetta <[email protected]> (cherry picked from commit e944b70)
andreabedini
pushed a commit
that referenced
this issue
Jul 8, 2022
Co-authored-by: Jeremy Scott <[email protected]> Co-authored-by: Artem Pelenitsyn <[email protected]> Co-authored-by: Francesco Gazzetta <[email protected]> (cherry picked from commit e944b70)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
If I have:
cabal check
complainsAfter changing to
cabal-version: >= 1.18
it then complains:Okay, apparently Hackage would not reject
cabal-version: >= 1.18
,but this is annoying, it should just suggest
cabal-version: 1.18
to the user in the first place.System information
Additional info
Seems it is determined in Cabal/src/Distribution/PackageDescription/Check.hs
The text was updated successfully, but these errors were encountered: