Comment 2 for bug 878132

Hi Casufi,

Where is your shared central repository located? (This is where the reserved edit locks are going to be stored.)

When you run red-enable it attempts to recurse from the working tree to a common place where the reserved edit locks can be stored. It is currently only designed to support shared respositories on a local networked file system - though in principle I think it should be able to support URL based transports there is supposed to be functionality that prevents their use.

As a work around, If you can change directory to the central point where you wish to store your locks then you can use the red-enable --force-central option to stop the command recursing and have it set up reserved edit.

Cheers,
Simon