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

Suggested package names repeated #3562

Closed
tfausak opened this issue Nov 9, 2017 · 1 comment
Closed

Suggested package names repeated #3562

tfausak opened this issue Nov 9, 2017 · 1 comment

Comments

@tfausak
Copy link
Contributor

@tfausak tfausak commented Nov 9, 2017

I accidentally put a package identifier that doesn't exist into my stack.yaml and got some interesting output:

The following package identifiers were not found in your indices: servant-foreign-0
Perhaps you meant servant-foreign, servant-foreign, servant-foreign, servant-foreign, servant-foreign, servant-foreign, servant-foreign, servant-foreign, servant-foreign, or servant-foreign?

😆

$ stack --version
Version 1.5.1 x86_64 hpack-0.17.1
# stack.yaml
resolver: lts-9.0
extra-deps: [ servant-foreign-0 ]
# package.yaml
name: example
version: 0.0.0
library: { dependencies: servant-foreign }
mgsloan added a commit that referenced this issue Nov 9, 2017
@mgsloan
Copy link
Contributor

@mgsloan mgsloan commented Nov 9, 2017

Thanks for the report! Looks like this is fixed in 1.6:

The following package identifiers were not found in your indices: servant-foreign-0
Possible candidates: servant-foreign-0.9.1, servant-foreign-0.5, servant-foreign-0.10.1, servant-foreign-0.6, servant-foreign-0.9, servant-foreign-0.6.1, servant-foreign-0.8, servant-foreign-0.10, servant-foreign-0.9.0.1, servant-foreign-0.7, servant-foreign-0.10.2, servant-foreign-0.7.1, servant-foreign-0.8.1, servant-foreign-0.9.1.1.

I've added a note to the ChangeLog

@mgsloan mgsloan closed this Nov 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants