Hi Mike, Thanks for the report.
> We think this may be an unintended consequence of a patch that was > applied to address CVE-2015-1197. Was this change in behavior for > relative symlinks intended, or is this a bug? It is definitely a bug. I'm working on a solution and will let you know when it is available. Until then, the best course of action would be to revert 45b0ee2b407913c533f7ded8d6f8cbeec16ff6ca. Regards, Sergey
