Hide Forgot
Currently, if a symlink exists locally, it can't be replaced by a downloaded directory from the upstream server by the versioned and snapshot tree plugins. On its own rsync won't overwrite the existing local file, and the sync plugins' own attempts to create the local destination directory (before invoking rsync) also fail.
GSv3 needs to faithfully represent the upstream structure. If a directory changes to a symlink or vice versa we need to mirror that in what GSv3 syncs so as not to deviate from what is the canonical source. Tim
OK, the sync algorithms for versioned and snapshot trees have been updated to drop any local files (including symlinks) that correspond to upstream directory names before invoking rsync for those directories.