portsnap problem

Chris Rees crees at freebsd.org
Sun Mar 11 13:01:09 UTC 2012


On 11 March 2012 12:55, Sergio de Almeida Lenzi <lenzi.sergio at gmail.com> wrote:
> Em Dom, 2012-03-11 às 07:38 -0500, ajtiM escreveu:
>
>> On Sunday 11 March 2012 07:05:35 Herby Vojčík 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 machine.
>> > I also removed everything in /usr/ports and /var/db/portsnap and issued
>> > 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


More information about the freebsd-ports mailing list