If this is an issue that should be sent to the bugtracker or a different
mailing list, please let me know and I'm happy to do so.
We're using svn:externals properties to reference files within another part
of the same repo, and the documented behavior of 'svn export' when using a
PATH as the fi
On 08/07/2014 10:46 PM, Nico Kadel-Garcia wrote:
>> The permissions on the /.svn/ dir are such that only root
> can access them (file mode 0700.)
>
> Don't Do That(tm). Write Subversion checkos for the parts of hte
> filesystem individuall, not as a master based at /.
>
> It's pretending that y
It seems that if Subversion finds a .svn directory in any parent path up
to the filesystem root, it requires access to the wc.db file or fails to
perform a checkout operation.
The use-case that caused this is a system where parts of the filesystem
are checked into an SVN repo for operational manag
I was building the subversion 1.7.0-alpha2 pre-release in a CentOS 5.6
environment and encountered an interesting problem with the new
dependency for python's sqlite support.
CentOS seems to name the site python library 'sqlite' while the
subversion system expects to import 'sqlite3'. This cau
