Distfile availability status for net/py-medusa
Status codes:
- numeric values represent RFC 2616 status codes
- NXDOMAIN means that the hostname could not be resolved
- network timeouts result in code 500
It is possible that a failed check could work now. Status codes between 500-599 are transient errors and the status you see represents the period of time when the distfile was checked.
Ports that set DEPRECATED, FETCH_CMD, FETCH_ENV, FETCH_BEFORE_ARGS, FETCH_AFTER_ARGS, or have a do-fetch: target are simply skipped.
All the tables have clickable headers that sort the table by the clicked column.
back
show bad only,
cvsweb,
other ports from this maintainer
| URL |
Checked |
Last OK |
Status |
| http://e.pypi.python.org/packages/source/m/medusa/medusa-0.5.4.tar.gz |
2013-05-22, 06:01:19 |
|
200 |
| http://pypi.crate.io/packages/source/m/medusa/medusa-0.5.4.tar.gz |
2013-05-22, 11:42:52 |
|
200 |
| http://pypi.python.org/packages/source/m/medusa/medusa-0.5.4.tar.gz |
2013-05-21, 11:36:19 |
|
200 |
| http://g.pypi.python.org/packages/source/m/medusa/medusa-0.5.4.tar.gz |
2013-05-22, 02:17:13 |
|
200 |
| http://pypi.it.uwosh.edu/medusa/medusa-0.5.4.tar.gz |
2013-05-21, 22:11:58 |
|
200 |
| http://f.pypi.python.org/packages/source/m/medusa/medusa-0.5.4.tar.gz |
2013-05-22, 12:50:34 |
|
200 |
| http://b.pypi.python.org/packages/source/m/medusa/medusa-0.5.4.tar.gz |
2013-05-22, 01:40:52 |
|
200 |
| http://pypi.inqbus.de/medusa/medusa-0.5.4.tar.gz |
2013-05-22, 04:39:53 |
|
200 |
| http://a.pypi.python.org/packages/source/m/medusa/medusa-0.5.4.tar.gz |
2013-05-21, 12:54:37 |
|
200 |
| http://c.pypi.python.org/packages/source/m/medusa/medusa-0.5.4.tar.gz |
2013-05-22, 04:21:02 |
|
200 |
| http://pypi.python.org/pypi/medusa/ |
2013-05-22, 14:12:49 |
|
200 |
| http://pypi.python.jp/medusa/medusa-0.5.4.tar.gz |
2013-05-21, 12:44:14 |
N/A |
404 |
| http://d.pypi.python.org/packages/source/m/medusa/medusa-0.5.4.tar.gz |
2013-05-22, 10:42:45 |
2013-01-03, 01:58:41 |
503 |
