[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Checkout fails on restrictions in higher .svn dir

From: Josh Cepek <josh.cepek_at_usa.net>
Date: Thu, 07 Aug 2014 23:35:28 -0500

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 your entire filesystem is a Subversion checkout.
> The extend to which this is a bad idea is..... really amazing.

Yes, I generally agree. Politics doesn't make this a great option in
this case. It sounds like there's not much current (or prior) material
on doing this because few people use such a strange workflow. Eventually
some change may be possible, but in the meantime the method is used
across an infra that isn't easy to change quickly.

I do get the "source control isn't a deployment strategy", but for
better or worse it plays a predominant role to that end for this site.
Much of that I can't control, so I'm merely looking for other options.

The odd part of this particular failure case is that Subversion is happy
to do everything properly except new checkouts when it lacks access to
the unrelated wc.db file. This feels like a bug, but I'm sure one with
minimal interest in having fixed.
Received on 2014-08-08 06:36:16 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.