inaccessible shared repositories

[Kent Gibson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I just noticed that this situation also causes the following selftests
to fail:

branch_txt
blackbox.test_info.TestInfo.test_info_non_existing
blackbox.test_outside_wt.TestOutsideWT.test_cwd_log
blackbox.test_outside_wt.TestOutsideWT.test_diff_ouside_tree

This in itself worries me.  Shouldn't the selftests be running in a
sandbox?
Or might they go twiddling with my shared repositories?

And more importantly, shouldn't "ouside" be "outside"?

Cheers,
Kent.

Kent Gibson wrote:
> Hi all,
>
> I ran across a small wrinkle wrt shared repositories. 'bzr branch'
> goes looking for a containing shared repository before deciding
> whether to create a new one.  To find a containing shared
> repository, bzr walks up the path until it finds one. If the one it
> finds it not accessible (e.g. it is owned by someone else) then bzr
> reports:
>
> bzr: ERROR: Permission denied: u'/.bzr/branch-format': [Errno 13]
> Permission denied: u'/.bzr/branch-format'
>
> (In my case I have a bzr repository in / that is owned by root and
> not accessible to other users - chmod 700.)
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFeYYcgoxTFTi1P8QRAn1uAJ4v9PuTWbtY74w9EnT5e9ze4ZIZuQCgtii5
vocmskXyVgNRti6vHFQQkcI=
=WJpw
-----END PGP SIGNATURE-----