Sat, Jan 20, 2018 at 1:03 PM, Julius Smith wrote:
> I was cruising along great with my subversion repos on my NAS and my
> working copies on Mac OS X Sierra, but after upgrading to High Sierra
> I see this whenever I try to check something in:
>
>> svn ci -m 'update'
&g
I was cruising along great with my subversion repos on my NAS and my
working copies on Mac OS X Sierra, but after upgrading to High Sierra
I see this whenever I try to check something in:
> svn ci -m 'update'
svn: E45: Commit failed (details follow):
svn: E45: Can't get exclusive lock on f
I figured out my problem! After finally getting my client downgraded to
1.6, I found that svn commands were still hanging. As I mentioned in my
original post, Comcast had reassigned my IP address while I was away, which
has only happened once before in a number of years (when I power-cycled my
ca
Thanks for letting me know it should work. I'll report if I get to the bottom
of why it failed.
"Anyone who knows all about nothing knows everything" - Leonard Susskind
On May 11, 2012, at 12:52 AM, Dave Huang wrote:
> On 5/11/2012 1:45 AM, Julius Smith wrote:
>> My
At 10:18 PM 5/10/2012, Dave Huang wrote:
why would you need to upgrade the server first? All 1.x Subversion
clients and servers are compatible with each other. You can use a
1.7 client with a 1.6 server (or a 1.0 server) if you want. This is
mentioned in the FAQ: http://subversion.apache.org/f
ubt I will
take the chance of going through this again.
- Julius Smith
--
"Anybody who knows all about nothing knows everything" -- Leonard Susskind
