On Wed, Feb 23, 2011 at 10:33 AM, W. Trevor King <[email protected]> wrote:
> 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 ** > >... > Full traceback? I'm wondering which libbe.storage.vcs.bzr.Bzr call > triggered the issue. > Full trace here ** 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\libbe\ui\command_line.py", line 263, in dispatch ret = ui.run(command, options, args) File "C:\PROGRA~1\Python26\lib\site-packages\libbe\command\base.py", line 535, in run return command.run(options, args) File "C:\PROGRA~1\Python26\lib\site-packages\libbe\command\base.py", line 262, in run self.status = self._run(**params) File "C:\PROGRA~1\Python26\lib\site-packages\libbe\command\init.py", line 95, in _run storage.init() File "C:\PROGRA~1\Python26\lib\site-packages\libbe\storage\base.py", line 194, in init return self._init() File "C:\PROGRA~1\Python26\lib\site-packages\libbe\storage\vcs\base.py", line 602, in _init self._vcs_add(self._u_rel_path(self.be_dir)) File "C:\PROGRA~1\Python26\lib\site-packages\libbe\storage\vcs\bzr.py", line 159, in _vcs_add cmd.run(file_list=[path], file_ids_from=self.repo) File "C:\PROGRA~1\Python26\lib\site-packages\bzrlib\commands.py", line 705, in run return self._operation.run_simple(*args, **kwargs) File "C:\PROGRA~1\Python26\lib\site-packages\bzrlib\cleanup.py", line 135, in run_simple self.cleanups, self.func, *args, **kwargs) File "C:\PROGRA~1\Python26\lib\site-packages\bzrlib\cleanup.py", line 165, in _do_with_cleanups result = func(*args, **kwargs) File "C:\PROGRA~1\Python26\lib\site-packages\bzrlib\builtins.py", line 690, in run no_recurse, action=action, save=not dry_run) File "C:\PROGRA~1\Python26\lib\site-packages\bzrlib\mutabletree.py", line 48, in tree_write_locked self.lock_tree_write() File "C:\PROGRA~1\Python26\lib\site-packages\bzrlib\workingtree_4.py", line 622, in lock_tree_write return self._lock_self_write() File "C:\PROGRA~1\Python26\lib\site-packages\bzrlib\workingtree_4.py", line 602, in _lock_self_write state.lock_write() File "C:\PROGRA~1\Python26\lib\site-packages\bzrlib\dirstate.py", line 3065, in lock_write self._lock_token = lock.WriteLock(self._filename) 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.') C:\Temp\testdir> ** SNIP ** > 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. > > So I created this current repo this morning ... I am at revision 1 right now. Here is a quick sessio to do a 'bzr commit' ** SNIP ** C:\Temp\testdir>bzr status unknown: .be/ <touch files testFileA.cpp and testFileB.cpp> C:\Temp\testdir>bzr status modified: testFileA.cpp testFileB.cpp unknown: .be/ C:\Temp\testdir>bzr commit -m "Minor changes to force commit" Committing to: C:/Temp/testdir/ modified testFileA.cpp modified testFileB.cpp Committed revision 2. C:\Temp\testdir> ** SNIP ** So, no I think this is specific to how libbe is calling bzrlib functions on my machine right now > > 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> > I thought I like you King; I will do what I can from my side to help debug this problem.
_______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
