Comment 8 for bug 225135

So, I think RayH was a bit off in his analysis, there are 2 bits:

bzr: ERROR: Permission denied: "4c/installwebaaa.pl-20080429104456-b586jfz3dn1m3hin-1.knit": [Errno 13] Permission denied

The action was failing because of a permission issue. Fixing the permission issue would have resolved this for any version of bzr.

C:\Program Files\Bazaar\lib\library.zip\bzrlib\lockable_files.py:110: UserWarning: file group LockableFiles(<bzrlib.transport.local.LocalTransport url=file:///C:/NMS/Globis/ExtraNet/.bzr/repository/>) was not explicitly unlocked

^- This is a separate issue, that we gave a warning that a lock wasn't properly cleaned up.
In 1.8 (I believe) Martin will merge his change to suppress these warnings, as they are generally more confusing than helpful. I also see this in bzr 1.4:

* If a ``LockableFiles`` object is not explicitly unlocked (for example
  because of a missing ``try/finally`` block, it will give a warning but
  not automatically unlock itself. (Previously they did.) This
  sometimes caused knock-on errors if for example the network connection
  had already failed, and should not be relied upon by code.
  (Martin Pool, #109520)

But that is something a little bit different.