Skip to content
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

cabal update says to use cabal new-update, but latter is broken. #5398

Closed
phadej opened this issue Jun 26, 2018 · 4 comments
Closed

cabal update says to use cabal new-update, but latter is broken. #5398

phadej opened this issue Jun 26, 2018 · 4 comments

Comments

@phadej
Copy link
Collaborator

@phadej phadej commented Jun 26, 2018

I cannot find my old ticket, but not it's super annoying:

% cabal update
Warning: The update command is a part of the legacy v1 style of cabal usage.

Please switch to using either the new project style or the legacy v1-update
alias as new-style projects will become the default in the next version of
cabal-install. Please file a bug if you cannot replicate a working v1- use
case with the new-style commands.

Downloading the latest package list from hackage.haskell.org
% cabal new-update
No cabal.project file or cabal file matching the default glob './*.cabal' was found.
Please create a package description file <pkgname>.cabal or a cabal.project file referencing the packages you want to build.

I consider this is a release blocker.

@typedrat
Copy link
Collaborator

@typedrat typedrat commented Jun 26, 2018

Are you within a new-build project? There are two possible bugs here, either new-update only works in a project which is decidedly non-ideal but a missing functionality issue or it's very broken internally, and I hope it's the former.

@phadej
Copy link
Collaborator Author

@phadej phadej commented Jun 26, 2018

Found previous issue: #5096

@typedrat
Copy link
Collaborator

@typedrat typedrat commented Jun 26, 2018

@typedrat typedrat added this to the 2.4 milestone Jun 26, 2018
@typedrat
Copy link
Collaborator

@typedrat typedrat commented Jun 26, 2018

Duplicate of #5096.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.