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

[phadej]

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]

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]

Found previous issue: #5096

[typedrat]

That’s an easy fix. Should have it in today. Alexis Williams

…

On Tue, Jun 26, 2018 at 12:12 PM Oleg Grenrus < Oleg Grenrus ( Oleg Grenrus ***@***.***> ) > wrote: Found previous issue: #5096 ( #5096 ) — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub ( #5398 (comment) ) , or mute the thread ( https://github.com/notifications/unsubscribe-auth/ABAj_d-WK-YzBhLy_Uv1jyCFFhJjw3tBks5uAoeFgaJpZM4U4bEE ).

[typedrat]

Duplicate of #5096.