Yes, it'd be nice to figure out how and why this happens on dozens of machines each and every time vim gets updated... And pkg_admin rebuild, and rebuild-tree, don't fix the problem. pkg_delete gives vim-share-8.whatever is still required by other packages errors, where whatever is the old version of vim-share which has already been replaced. An -f needs to be added. I'll check it out the next time vim gets updated BEFORE running pkg_rolling-replace on dozens of machines.I think this means your pkgdb is corrupt, not that the package is broken... try running pkg_admin rebuild-tree (and probably also pkg_admin rebuild) would be nice to find out why this happens sometimes, of course...
John