portsnap problem

[Colin Percival]

On 03/11/12 06:00, Chris Rees wrote:
> CC: portsnap maintainer

Thanks!  I don't regularly read freebsd-ports (funny for the portsnap maintainer
to not be subscribed, I know, but I get way too much email already...).

> Although that might be a reasonable explanation, it's much more likely
> that portsnap data is not being generated right now.

Almost correct -- I just restarted the portsnap builds a few minutes ago.  They
were broken for about 18 hours; I'm not entirely certain of the cause but I
suspect a freebsd.org DNS glitch was at least partly responsible.

-- 
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid