matthew at FreeBSD.org
Sun Mar 11 13:07:31 UTC 2012
On 11/03/2012 12:55, Sergio de Almeida Lenzi wrote:
> Em Dom, 2012-03-11 às 07:38 -0500, ajtiM escreveu:
>> On Sunday 11 March 2012 07:05:35 Herby Vojčík wrote:
>>> 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.
That's not it. Ports only gets frozen completely for a matter of an
hour or so as part of the release process. Instead, it spends much of
the period leading up to a release in "Slush" -- which is the case at
Slush doesn't mean that ports stop being updated. On the contrary,
there have been some twenty-odd ports updated just this morning as I can
see from the cvs-ports@ mailing list.
Slush does mean that changes with large scale ramifications are not
permitted, so last week's perl-related updates for instance, would not
be allowed right now.
The portsnap thing is a real problem. No idea what or why or how long
to fix, but I'd hazard a guess that the answer to the last is "by later
Dr Matthew J Seaman MA, D.Phil.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 267 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20120311/7e057671/signature.pgp
More information about the freebsd-ports