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

etlas update cannot read index #656

Closed
mbrc12 opened this issue Feb 15, 2018 · 5 comments
Closed

etlas update cannot read index #656

mbrc12 opened this issue Feb 15, 2018 · 5 comments

Comments

@mbrc12
Copy link
Contributor

mbrc12 commented Feb 15, 2018

On Fedora 27, running etlas update yields

Downloading the latest package lists from:
- hackage.haskell.org
- etlas.org
etlas: Could not read index. Did you call 'checkForUpdates'?

stack update works fine.

The output for etlas update -v3 is

no user package environment file found at /home/mbrc/eta
Downloading the latest package lists from:
- hackage.haskell.org
- etlas.org
Searching for curl in path.
Found curl at /home/mbrc/anaconda3/bin/curl
Searching for powershell in path.
Cannot find powershell on the path
Searching for wget in path.
Found wget at /usr/bin/wget
Selected http transport implementation: curl
Updating index cache file
/home/mbrc/.etlas/packages/hackage.haskell.org/01-index.cache ...
Searching for git in path.
Found git at /usr/bin/git
/usr/bin/git --version
etlas: Could not read index. Did you call 'checkForUpdates'?
@rahulmutt
Copy link
Member

Have you installed and used etlas before? If so, try cleaning out ~/.etlas and try again.

@rahulmutt
Copy link
Member

This doesn't appear to be a proxy issue since it would've showed some failure on curl.

@rahulmutt
Copy link
Member

rahulmutt commented Feb 15, 2018

While this user was affected on Windows (#487) I think it may be of use. I noticed that the curl being used was anaconda3/bin/curl - is it a special curl implementation?

Try out etlas update --http-transport=wget or etlas update --http-transport=plain-http and see if that fixes it.

@jneira
Copy link
Collaborator

jneira commented Feb 15, 2018

Another check could be try the index url in a browser to discard that the proxy rules are banning the request

@rahulmutt
Copy link
Member

This was fixed by using a different transport - wget in this case and adding http-transport: wget in ~/.etlas/config.

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

3 participants