-
-
Notifications
You must be signed in to change notification settings - Fork 902
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
Error with listing gems #16
Labels
Comments
I think I accidentally blew away the gem index when I deployed...I need to fix the capistrano scripts so that doesn't happen. Anyway, it should work now. |
I can't seem to reproduce what blew away the index...if this crops up again for you let me know. Thanks! |
ok works now for me, too! |
dwradcliffe
pushed a commit
that referenced
this issue
Nov 19, 2014
dwradcliffe
pushed a commit
that referenced
this issue
Nov 19, 2014
Fixes #16 - Better breaking for my gems list on dashboard
dwradcliffe
pushed a commit
that referenced
this issue
Nov 19, 2014
dwradcliffe
pushed a commit
that referenced
this issue
Nov 19, 2014
Fixes #16 - Fix my gems list on dashboard
acacheung
added a commit
that referenced
this issue
Jan 29, 2015
acacheung
added a commit
that referenced
this issue
Jan 29, 2015
Fixes #16 - Better breaking for my gems list on dashboard
acacheung
added a commit
that referenced
this issue
Jan 29, 2015
acacheung
added a commit
that referenced
this issue
Jan 29, 2015
Fixes #16 - Fix my gems list on dashboard
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
gem list -r
results in:
*** REMOTE GEMS ***
ERROR: http://gemcutter.org does not appear to be a repository ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError) bad response Not Found 404 (http://gemcutter.org/yaml)
The text was updated successfully, but these errors were encountered: