something wrong with portsnap and INDEX ?

2010-08-09 Thread Barbara
I'm updating my ports tree using portsnap and then checking for new version with 'portversion -l '. I've noticed that virtualbox-ose-* ports are not reported as old, but they should have been committed about 9 hours ago. In fact: $ pkg_version -l virtualbox-ose

Re: something wrong with portsnap and INDEX ?

2010-08-09 Thread b. f.
Could it be that net/p5-IO-INET6 and net/p5-IO-Socket-INET6 are making the indexing crazy? 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