On Jul 19, 2004, at 8:28 PM, Shawn Erickson wrote:
> On Jul 19, 2004, at 3:14 PM, paul. wrote:
>> After taking everyone's screaming recommendation to use the https://
>> method (because svn+ssh doesn't work)
> svn+ssh doesn't work? How so?
Nope. Permissions and BDB logfiles. A well discussed topic.
I'm running an svn install on a server where I can't just 'move the
binary and replace it with a umask script' and as such, svn+ssh is
broken for me. I asked the list about it a month ago, because I spent a
good chunk of the day su-ing and chmod-ing and chown-ing files. The
answer was "huh, that sure sucks." Not exactly *working* in my opinion,
but that's what the new filesystem support in svn is about. Too bad
that's not ready for prime-time either.
Anyhow, now I'm having an unexplained BDB problem, this time taking the
solution to "just have a single point of access" with apache2. BDB
screws up again, this time in such a manner as to fail svnadmin
recover. Awesome. So, how do I un-nuke data that shows the symptoms
given in the original post? When can I expect that not to happen
anymore?
- paul
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 20 02:47:47 2004