error when permission denied on lstat of ~/.gvfs

To make it easier to address this bug, could you please post the traceback from ~/.bzr.log?

I think we're probably trying to stat it as part of listing the directory, and we should probably cope more gracefully. But this _is_ a pretty odd situation: normally on Unix if you can see a file or directory you can at least stat it, even if you can't look inside it.

Here is the traceback:

0.210 opening working tree '/home/gioele'
0.314 Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 835, in exception_to_return_code
    return the_callable(*args, **kwargs)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 1030, in run_bzr
    ret = run(*run_argv)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 647, in run_argv_aliases
    return self.run(**all_cmd_args)
  File "/usr/lib/python2.5/site-packages/bzrlib/builtins.py", line 1117, in run
    if (tree.has_changes(tree.basis_tree())
  File "/usr/lib/python2.5/site-packages/bzrlib/decorators.py", line 138, in read_locked
    result = unbound(self, *args, **kwargs)
  File "/usr/lib/python2.5/site-packages/bzrlib/mutabletree.py", line 243, in has_changes
    change = changes.next()
  File "_dirstate_helpers_pyx.pyx", line 1350, in bzrlib._dirstate_helpers_pyx.ProcessEntryC.__next__
  File "_dirstate_helpers_pyx.pyx", line 1514, in bzrlib._dirstate_helpers_pyx.ProcessEntryC._iter_next
  File "_dirstate_helpers_pyx.pyx", line 1491, in bzrlib._dirstate_helpers_pyx._iter_next
  File "/usr/lib/python2.5/site-packages/bzrlib/osutils.py", line 1485, in _walkdirs_utf8
    dirblock = sorted(read_dir(relroot, top))
  File "_readdir_pyx.pyx", line 237, in bzrlib._readdir_pyx.UTF8DirReader.read_dir
  File "_readdir_pyx.pyx", line 343, in bzrlib._readdir_pyx._read_dir
OSError: [Errno 13] lstat: Permission denied: '/home/gioele//.gvfs'

0.315 return code 3

This bug is still present in Bazaar 2.0.2.

Is it possible to avoid stating files (at least .bzrignore'd files) when "bzr push"-ing?

2009/12/1 Gioele Barabucci <email address hidden>:
> This bug is still present in Bazaar 2.0.2.
>
> Is it possible to avoid stating files (at least .bzrignore'd files) when
> "bzr push"-ing?

It's possible to change bzr so that it doesn't do that, and we can
help you make such a patch if you're interested. It's not possible to
configure bzr to do it with no code changes.

--
Martin <http://launchpad.net/~mbp/>