Date: Sun, 11 Mar 2012 13:00:37 +0000 From: Chris Rees <crees@freebsd.org> To: Sergio de Almeida Lenzi <lenzi.sergio@gmail.com> Cc: ajtiM <lumiwa@gmail.com>, Colin Percival <cperciva@freebsd.org>, FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: portsnap problem Message-ID: <CADLo83_Q2AVqZiLMqwpkYfGsN47kYqRLC%2BPHht%2BoHg=WX=qqCw@mail.gmail.com> In-Reply-To: <1331470527.25467.4.camel@z6000.lenzicasa> References: <4F5C950F.2020203@mailbox.sk> <201203110738.02969.lumiwa@gmail.com> <1331470527.25467.4.camel@z6000.lenzicasa>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11 March 2012 12:55, Sergio de Almeida Lenzi <lenzi.sergio@gmail.com> wr= ote: > Em Dom, 2012-03-11 =C3=A0s 07:38 -0500, ajtiM escreveu: > >> On Sunday 11 March 2012 07:05:35 Herby Voj=C4=8D=C3=ADk wrote: >> > Hello, >> > >> > for a day already, portsnap fetch seems not to fetch newest changes. >> > freshports shows lots of changes, port portsnap fetch says there >> > everything is up to date. >> > I checked that the ports are really newer in freshports than in my mac= hine. >> > I also removed everything in /usr/ports and /var/db/portsnap and issue= d >> > portsnap fetch extract, but it did not help. >> > >> > Maybe some job that creates patches for portsnap died? >> > > > Or just that ports system is "frozen" because of the 8.3 release??? > > Occam's razor: > > when you have two or more competing theories > that make exactly the same predictions, > the simpler one is the better. CC: portsnap maintainer Although that might be a reasonable explanation, it's much more likely that portsnap data is not being generated right now. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo83_Q2AVqZiLMqwpkYfGsN47kYqRLC%2BPHht%2BoHg=WX=qqCw>