#327 closed defect (wontfix)
chicken-install is PARTIALLY DOWN
| Reported by: | Jim Ursetto | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | infrastructure | Version: | 4.5.x |
| Keywords: | Cc: | ||
| Estimated difficulty: |
Description
galinha no longer exists and alaric's machine isn't responding.
chicken-install does not work.
Change History (5)
comment:1 Changed 14 years ago by
| Priority: | critical → major |
|---|---|
| Summary: | chicken-install is TOTALLY DOWN → chicken-install is PARTIALLY DOWN |
comment:2 Changed 14 years ago by
We have code.call-cc.org/cgi-bin/henrietta.cgi now
It can be used like that:
chicken-install -l code.call-cc.org/cgi-bin/henrietta.cgi egg-name-here
comment:3 Changed 14 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
You can give an exact location, as Mario has shown, or you can change the defaults in <PREFIX>/share/chicken/setup.defaults:
(server (location "http://code.call-cc.org/cgi-bin/henrietta.cgi") (transport http))
The order of server declarations in this file gives the order in which they are tried.
I will post a message on chicken-users about this.
comment:4 Changed 14 years ago by
More worrisome is that alaric's machine returned #f when looking for the extension. It did not time out.
I know how to change the default location, but new users don't, such as the user in IRC who was trying Chicken for the first time and brought this to my attention.
This should probably be prominently posted on the wiki for anyone using Chicken < 4.6.
OK, I guess alaric's machine is somehow serving eggs again.
Leaving this open at reduced priority until someone enlightens me on the battle plan for addressing the single point of failure situation.