Distfile availability status for x11/i3lock
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://i3wm.org/i3lock/i3lock-2.4.1.tar.bz2 |
2013-05-22, 11:30:07 |
|
200 |
| http://i3.zekjur.net/i3lock/ |
2013-05-21, 11:22:56 |
|
200 |
| ftp://ftp.ru.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/dhn/i3lock-2.4.1.tar.bz2 |
2013-05-22, 02:07:02 |
N/A |
404 |
| ftp://ftp.uk.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/dhn/i3lock-2.4.1.tar.bz2 |
2013-05-22, 10:07:16 |
N/A |
404 |
| ftp://ftp.se.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/dhn/i3lock-2.4.1.tar.bz2 |
2013-05-21, 20:26:10 |
N/A |
404 |
| ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/dhn/i3lock-2.4.1.tar.bz2 |
2013-05-22, 03:23:39 |
N/A |
404 |
| ftp://ftp.jp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/dhn/i3lock-2.4.1.tar.bz2 |
2013-05-21, 23:29:07 |
N/A |
404 |
| http://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/dhn/i3lock-2.4.1.tar.bz2 |
2013-05-22, 07:17:48 |
N/A |
404 |
| ftp://ftp.cn.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/dhn/i3lock-2.4.1.tar.bz2 |
2013-05-21, 12:52:36 |
N/A |
404 |
| ftp://ftp.tw.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/dhn/i3lock-2.4.1.tar.bz2 |
2013-05-22, 13:56:30 |
N/A |
404 |
| http://mirror.4bit.ws/i3lock-2.4.1.tar.bz2 |
2013-05-21, 16:45:11 |
N/A |
NXDOMAIN |
