On Wed, Feb 23, 2011 at 10:11:46AM -0700, Michael Chaffin wrote:
> On Tue, Feb 22, 2011 at 7:10 PM, W. Trevor King <[email protected]> wrote:
> > ... Could you run `git pull`, re-install, and try again?
> 
> Done, and I still get the same error when trying on a stripped down bzr
> repository.
> 
> ** SNIP **
> C:\Temp\testdir>be init
> Traceback (most recent call last):
>   File "C:\Program Files\Python26\Scripts\be.py", line 26, in <module>
>     sys.exit(libbe.ui.command_line.main())
>   File "C:\PROGRA~1\Python26\lib\site-packages\libbe\ui\command_line.py",
> line 331, in main
>     ret = dispatch(ui, command, args)
> ...
>   File "C:\PROGRA~1\Python26\lib\site-packages\bzrlib\lock.py", line 413, in
> __init__
>     os.O_RDWR, "rb+")
>   File "C:\PROGRA~1\Python26\lib\site-packages\bzrlib\lock.py", line 371, in
> _open
>     raise errors.LockContention(filename, e)
> bzrlib.errors.LockContention: Could not acquire lock
> "C:/Temp/testdir/.bzr/checkout/dirstate":
> (32, 'CreateFileW', 'The process cannot access the file because it is being
> used by another process.')

Full traceback?  I'm wondering which libbe.storage.vcs.bzr.Bzr call
triggered the issue.

My current theory is that it's a stale lock from previous buggy
crashes.  Does `bzr commit` or some other lock-aquiring command work
in your test directory?  Or you could just try in a fresh bzr repo.

> Maybe you can just mark this one up to my unique setup ... but I am not sure
> why? I will see what I can see from my end.

Must fix!  <maniacal cackle>

-- 
This email may be signed or encrypted with GPG (http://www.gnupg.org).
The GPG signature (if present) will be attached as 'signature.asc'.
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt

Attachment: pgp0F0vKlQyO0.pgp
Description: PGP signature

_______________________________________________
Be-devel mailing list
[email protected]
http://void.printf.net/cgi-bin/mailman/listinfo/be-devel

Reply via email to