Distfile availability status for net/py-zope.proxy
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://g.pypi.python.org/packages/source/z/zope.proxy/zope.proxy-4.1.3.zip |
2013-06-19, 17:40:01 |
|
200 |
| http://pypi.python.org/pypi/zope.proxy |
2013-06-19, 13:51:15 |
|
200 |
| http://b.pypi.python.org/packages/source/z/zope.proxy/zope.proxy-4.1.3.zip |
2013-06-19, 10:43:15 |
|
200 |
| http://pypi.crate.io/packages/source/z/zope.proxy/zope.proxy-4.1.3.zip |
2013-06-18, 15:36:03 |
|
200 |
| http://f.pypi.python.org/packages/source/z/zope.proxy/zope.proxy-4.1.3.zip |
2013-06-18, 17:23:02 |
|
200 |
| http://pypi.python.org/packages/source/z/zope.proxy/zope.proxy-4.1.3.zip |
2013-06-18, 21:03:54 |
|
200 |
| http://pypi.python.jp/zope.proxy/zope.proxy-4.1.3.zip |
2013-06-18, 20:52:47 |
|
200 |
| http://c.pypi.python.org/packages/source/z/zope.proxy/zope.proxy-4.1.3.zip |
2013-06-18, 22:34:53 |
|
200 |
| http://e.pypi.python.org/packages/source/z/zope.proxy/zope.proxy-4.1.3.zip |
2013-06-18, 20:30:46 |
|
200 |
| http://a.pypi.python.org/packages/source/z/zope.proxy/zope.proxy-4.1.3.zip |
2013-06-19, 12:09:14 |
|
200 |
| http://d.pypi.python.org/packages/source/z/zope.proxy/zope.proxy-4.1.3.zip |
2013-06-19, 05:52:27 |
N/A |
404 |
| http://pypi.inqbus.de/zope.proxy/zope.proxy-4.1.3.zip |
2013-06-19, 18:45:33 |
N/A |
404 |
| http://pypi.it.uwosh.edu/zope.proxy/zope.proxy-4.1.3.zip |
2013-06-19, 10:48:17 |
N/A |
404 |
