Bazaar Explorer "environmental error" on commit to colo workspace

[Evan Burkitt]

Using Bazaar Explorer 1.2.1 on 64-bit Windows 7 I created a colo workspace in a directory containing an existing (non-bzr) project and added all its files. On choosing to commit the changes I get an error dialog with the following error details:
bzr: ERROR: [Error 5] C:/Users/evanb.ES01/Documents/Visual Studio 2005/Projects/task_scheduler/.bzr/branches/trunk/.bzr/branch/lock/releasing.a2jtk4huv7p5evilmzs7.tmp/*

[Martin Pool (mbp)]

please post the traceback from .bzr.log

[Alexander Belchenko (bialix)]

Evan Burkitt пишет:
> Public bug reported:
>
> Using Bazaar Explorer 1.2.1 on 64-bit Windows 7 I created a colo workspace in a directory containing an existing (non-bzr) project and added all its files. On choosing to commit the changes I get an error dialog with the following error details:
> bzr: ERROR: [Error 5] C:/Users/evanb.ES01/Documents/Visual Studio 2005/Projects/task_scheduler/.bzr/branches/trunk/.bzr/branch/lock/releasing.a2jtk4huv7p5evilmzs7.tmp/*

Error 5 is "Access is denied."

[Martin Pool (mbp)]

Could you please check the permissions on this directory, or the
enclosing directories. Maybe one is owned by a different user?

[Evan Burkitt (ubuntu-burkitt)]

When I checked today I could not find a .bzr.log file, and the "../.bzr/branches/trunk/.bzr/branch/lock" directory was empty, so I decided to try again. I deleted the project's .bzr directory (but left the shared repository in which this project lives) and did the workspace creation and file add again. This time, of course, no errors. It failed ~3 times during a similar regimen the day I reported it so I thought I was on to something. Apparently not.

For the record, the permissions on the lock directory, the lowest remaining in the path reported in the error, are the same as any other in the project's tree (except for the .bzr directory itself, which has the "hidden" attribute set).

In case this happens again, where should I look for the .bzr.log file?

[Martin Pool (mbp)]

bzr --version will tell you where the log is

[Martin Packman (gz)]

Very similar error to bug 901104 so likely comes from file watcher as well.