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

update command only ever states the previous index state, but not the current one #6804

Closed
samuela opened this issue May 14, 2020 · 0 comments
Milestone

Comments

@samuela
Copy link

samuela commented May 14, 2020

Describe the bug
The (v2-)update command is great in that it gives the exact command necessary in order to revert to the previous package index state, but it doesn't actually say what state the package list just got update to. Adding this would be super useful info, esp. when trying to get exactly reproducible builds!

To Reproduce
Currently

$ cabal v2-update
Downloading the latest package list from hackage.haskell.org
To revert to previous state run:
    cabal v2-update 'hackage.haskell.org,2020-05-14T21:24:35Z'

Expected behavior

It would be great if we could get something like

$ cabal v2-update
Downloading the latest package list from hackage.haskell.org...

Updated package list to 'hackage.haskell.org,2020-05-14T21:24:35Z'!

To revert to previous state run:
    cabal v2-update 'hackage.haskell.org,2020-05-14T21:24:35Z'

System information

  • Debian 9
ghc@bf86fd77bccf:~/out$ ./cabal --version
cabal-install version 3.2.0.0
compiled using version 3.2.0.0 of the Cabal library
ghc@bf86fd77bccf:~/out$ ghc --version
The Glorious Glasgow Haskell Compilation System, version 8.8.3
@phadej phadej closed this as completed in 0e2e7cd May 15, 2020
phadej added a commit that referenced this issue May 15, 2020
Resolve #6804: v2-update reports new index-state
@phadej phadej added this to the 3.4.0.0-rc1 milestone Jul 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants