Date: Sun, 11 Mar 2012 06:07:38 -0700 From: Colin Percival <cperciva@freebsd.org> To: Chris Rees <crees@freebsd.org> Cc: ajtiM <lumiwa@gmail.com>, Sergio de Almeida Lenzi <lenzi.sergio@gmail.com>, FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: portsnap problem Message-ID: <4F5CA39A.7000401@freebsd.org> In-Reply-To: <CADLo83_Q2AVqZiLMqwpkYfGsN47kYqRLC%2BPHht%2BoHg=WX=qqCw@mail.gmail.com> References: <4F5C950F.2020203@mailbox.sk> <201203110738.02969.lumiwa@gmail.com> <1331470527.25467.4.camel@z6000.lenzicasa> <CADLo83_Q2AVqZiLMqwpkYfGsN47kYqRLC%2BPHht%2BoHg=WX=qqCw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F5CA39A.7000401>