Distfile availability status for sysutils/hachoir-subfile
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://d.pypi.python.org/packages/source/h/hachoir-subfile/hachoir-subfile-0.5.3.tar.gz |
2012-05-25, 10:02:57 |
|
200 |
| http://c.pypi.python.org/packages/source/h/hachoir-subfile/hachoir-subfile-0.5.3.tar.gz |
2012-05-25, 08:20:48 |
|
200 |
| http://b.pypi.python.org/packages/source/h/hachoir-subfile/hachoir-subfile-0.5.3.tar.gz |
2012-05-25, 09:12:15 |
|
200 |
| http://f.pypi.python.org/packages/source/h/hachoir-subfile/hachoir-subfile-0.5.3.tar.gz |
2012-05-25, 08:31:28 |
|
200 |
| http://pypi.python.org/packages/source/h/hachoir-subfile/hachoir-subfile-0.5.3.tar.gz |
2012-05-25, 07:14:25 |
|
200 |
| http://e.pypi.python.org/packages/source/h/hachoir-subfile/hachoir-subfile-0.5.3.tar.gz |
2012-05-25, 09:03:38 |
|
200 |
| http://bitbucket.org/haypo/hachoir/wiki/hachoir-subfile |
2012-05-25, 09:33:15 |
|
200 |
| http://pypi.it.uwosh.edu/hachoirsubfile-/hachoir-subfile-0.5.3.tar.gz |
2012-05-25, 09:18:16 |
N/A |
404 |
| http://pypi.inqbus.de/hachoirsubfile-/hachoir-subfile-0.5.3.tar.gz |
2012-05-25, 09:27:57 |
N/A |
404 |
| http://pypi.python.jp/hachoirsubfile-/hachoir-subfile-0.5.3.tar.gz |
2012-05-25, 08:08:24 |
N/A |
404 |
