Error when attempting to add directory containing a "junction" on Windows

[Pete Johanson]

This is on Windows, using the standalone 2.3.0 installer. When trying to do a "bzr add", when bzr gets to a directory containing a 'junction' (identified in "cmd" as <JUNCTION> when doing a "dir") it exists immediately with an error:

bzr: ERROR: [Error 3] The system cannot find the path specified: u'C:/Users/pete.johanson/dev/repo/mainline/wraps/openwrap\\*.*'

In this scenario, "repo" is an initialized bzr repository, and "mainline" is an initialized bzr branch. The "openwrap" item is a <JUNCTION> item that points to "mainline/wraps/_cache/openwrap-1.0.0/" which does exist.

I'm not sure what the intended/ideal behavior should be. At a minimum, a nice warning/error message as was added for Bug #81689 would be helpful.

Let me know what other details are required. You should be able to recreate the scenario fairly easily by using "mklink.exe" (found on my Windows 7 system, not sure what version introduced the utility (Vista maybe?))

[Martin Packman (gz)]

Junctions at least don't require admin privileges, but still have the basic problem of being alien to the windows shell and user expectations.

The error you got is actually reasonable, it indicates the problem is with your setup not bzr, and gives you the path at issue. If you attach the full traceback (get it from the bzr log file, `bzr version` tells you where to find that), anyone wanting to add more specific reparse point detection would know where to start.