On Sat, Oct 18, 2008 at 4:16 PM, Winston Wolff <email address hidden> wrote:
> Any news on this bug? I have switched back to Subversion because of
> this problem--at work I use network home folders so bzr cannot be used.
>
No news, and I have had to switch back to subversion, as you have. The
bzr developers were happy to help resovlve the issue if they knew how
to create locks on AFP volumes. I did a bit of searching, but nothing
came up. If you know any of the relevant APIs (or pointers to same),
I'd be happy to get that info to the bzr guys.
barry
> --
> dirstate locks don't work on Apple AFP network mounts
> https://bugs.launchpad.net/bugs/114528
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Bazaar Version Control System: Confirmed
>
> Bug description:
> Using bzr 0.16.0 under python 2.4 on Mac OS X (installed from MacPorts). Working dir/repos is on a network (AFP) share served from a Mac OS X machine, and from the looks of it AFP doesn't support some of the necessary locking.
>
> bzr init and/or bzr upgrade (depending whether I'm in an existing repos or not) give me the following error:
>
> bzr: ERROR: Could not acquire lock [Errno 45] Operation not supported
> /opt/local/lib/python2.4/site-packages/bzrlib/lock.py:79: UserWarning: lock on <open file u'/Volumes/WebServer/work_dir/.bzr/checkout/dirstate', mode 'wb+' at 0x1225de8> not released
> warn("lock on %r not released" % self.f)
> Exception exceptions.IOError: (45, 'Operation not supported') in <bound method _fcntl_WriteLock.__del__ of <bzrlib.lock._fcntl_WriteLock object at 0x1248690>> ignored
> /opt/local/lib/python2.4/site-packages/bzrlib/lockable_files.py:110: UserWarning: file group LockableFiles(<bzrlib.transport.local.LocalTransport url=file:///Volumes/WebServer/work_dir/.bzr/checkout/>) was not explicitly unlocked
> warn("file group %r was not explicitly unlocked" % self)
>
On Sat, Oct 18, 2008 at 4:16 PM, Winston Wolff <email address hidden> wrote:
> Any news on this bug? I have switched back to Subversion because of
> this problem--at work I use network home folders so bzr cannot be used.
>
No news, and I have had to switch back to subversion, as you have. The
bzr developers were happy to help resovlve the issue if they knew how
to create locks on AFP volumes. I did a bit of searching, but nothing
came up. If you know any of the relevant APIs (or pointers to same),
I'd be happy to get that info to the bzr guys.
barry
> -- /bugs.launchpad .net/bugs/ 114528 lib/python2. 4/site- packages/ bzrlib/ lock.py: 79: UserWarning: lock on <open file u'/Volumes/ WebServer/ work_dir/ .bzr/checkout/ dirstate' , mode 'wb+' at 0x1225de8> not released WriteLock. __del__ of <bzrlib. lock._fcntl_ WriteLock object at 0x1248690>> ignored lib/python2. 4/site- packages/ bzrlib/ lockable_ files.py: 110: UserWarning: file group LockableFiles( <bzrlib. transport. local.LocalTran sport url=file: ///Volumes/ WebServer/ work_dir/ .bzr/checkout/ >) was not explicitly unlocked
> dirstate locks don't work on Apple AFP network mounts
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Bazaar Version Control System: Confirmed
>
> Bug description:
> Using bzr 0.16.0 under python 2.4 on Mac OS X (installed from MacPorts). Working dir/repos is on a network (AFP) share served from a Mac OS X machine, and from the looks of it AFP doesn't support some of the necessary locking.
>
> bzr init and/or bzr upgrade (depending whether I'm in an existing repos or not) give me the following error:
>
> bzr: ERROR: Could not acquire lock [Errno 45] Operation not supported
> /opt/local/
> warn("lock on %r not released" % self.f)
> Exception exceptions.IOError: (45, 'Operation not supported') in <bound method _fcntl_
> /opt/local/
> warn("file group %r was not explicitly unlocked" % self)
>