As Paul Hammant wrote:
> Works for me (svn, version 1.13.0 (r1867053) on Mac) ....
> $ svn co https://svn.freebsd.org/base/head/usr.bin/passwd freebsdTest
> A freebsdTest/Makefile
> A freebsdTest/passwd.c
> A freebsdTest/Makefile.depend
> A freebsdTest/passwd.1
> Checked out revision 357040.
What automounter is below?
If the automounter already yields ENOENT for the ../.svn directory
probe, everything is not going to be a problem. I think the point here
is the automounter (eventually, after "thinking" about it for about 1
s) offers a successful stat() result for ../.svn (probably because
that directory *might be* a possible mount point for the automounter)
but then yields EIO when trying to access anything within that
ficticous directory (because nothing is actually mounted there).
My entire point is: when getting any error for ..*/.svn/wc.db, just
stop traversing there, and proceed with the checkout (in its own
You could construct a similar testcase without involving an automounter
by creating a directory /.svn as root which is not accessible by any
j_at_uriah 53% su
root_at_uriah:/home/joerg # mkdir /.svn
root_at_uriah:/home/joerg # chmod 0700 /.svn
root_at_uriah:/home/joerg # exit
j@uriah 54% svn co https://svn.freebsd.org/base/head/usr.bin/passwd freebsdTest
svn: E000013: Can't check path '/.svn/wc.db': Permission denied
In other words, the sys admin, by creating that directory, prevents
*any* user of the system from checking out any (new) SVN repository in
the system. I don't believe this is intented. ;-)
cheers, Joerg .-.-. --... ...-- -.. . DL8DTL
Never trust an operating system you don't have sources for. ;-)
Received on 2020-01-23 12:44:19 CET