Package: subversion
Version: 1.7.14-1+b1
Severity: normal
Tags: upstream
Dear Maintainer,
This is related to #570271, though now I'm on 1.7.
Steps to reproduce:
~>ls -ld /.svn
11:55pm
drwx------ 7 root root 1024 Jan 17 17:13 /.svn
~>ls -l .svn
11:55pm
ls: cannot access .svn: No such file or directory
svn checkout http://blahblah
svn: E000013: Can't check path '/.svn/wc.db': Permission denied
It would be nice if this would work. In the related upstream discussion on bug
#570271, someone said this was due to looking for 1.6 vs. 1.7 repositories, and
that was my problem, but now I'm on 1.7, and I think subversion always goes up
the ancestor path, since it needs to find the root of the repository, since
that is where the .svn directory lives.
In my example, I am starting a new repository, and don't care what is happening
in my parent (or root) directory, because I don't have permission in that
directory.
If the authors want to print out a warning message, I suppose that is okay, but
it'd be nice to not fail entirely. If it could just ignore directories it
doesn't have permission to read, that seems like the answer to me. (and I
suppose if there is a parent directory that contains a .svn subdirectory that
it can't read, it should stop traversing to further parents, but just bail at
that point, and assume we're not inside a repository, particularly for a
checkout. I'm not sure what it means to run a checkout inside a repository
anyway.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.11-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages subversion depends on:
ii libapr1 1.5.0-1
ii libc6 2.17-97
ii libsasl2-2 2.1.25.dfsg1-17
ii libsvn1 1.7.14-1+b1
subversion recommends no packages.
Versions of packages subversion suggests:
ii db5.1-util 5.1.29-6
ii patch 2.7.1-4
ii subversion-tools 1.7.14-1
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
