something wrong with portsnap and INDEX ?
bf1783 at googlemail.com
Tue Aug 10 02:40:39 UTC 2010
>Could it be that net/p5-IO-INET6 and net/p5-IO-Socket-INET6 are making the
>Maybe this is not the cause, but isn't an entry in MOVED required?
There were a number of problem commits in the past day or two,
breaking the INDEX and some individual ports. Some of these are now
supposed to be fixed, e.g. [*]. Wait a bit longer, then update and
check your ports tree, and if something is still broken afterward, let
More information about the freebsd-ports