Re: Problem with an archive

2012-11-13 Thread Daniel Shahaf
Daniel Shahaf wrote on Wed, Nov 14, 2012 at 09:14:13 +0200: > IIRC format 5 is identical to 4 except for storage of revprops. It > would be straightforward to export it without the revprops, and should > be straightforward to write a script to convert the revprops storage to > format 4 (supported

Re: Problem with an archive

2012-11-13 Thread Daniel Shahaf
Ryan Schmidt wrote on Wed, Nov 14, 2012 at 00:27:21 -0600: > > On Nov 13, 2012, at 21:54, Robert R. Kessler wrote: > > > Unfortunately, I have not been able to find an archived download of the 1.7 > > alpha3 version in order to try to see if the svnadmin extraction will work. > > > > Does anyo

Re: Problem with an archive

2012-11-13 Thread Ryan Schmidt
On Nov 13, 2012, at 21:54, Robert R. Kessler wrote: > Unfortunately, I have not been able to find an archived download of the 1.7 > alpha3 version in order to try to see if the svnadmin extraction will work. > > Does anyone have a copy of that version so I can give this a shot. Source downloa

Problem with an archive

2012-11-13 Thread Robert R. Kessler
I am not a subscriber so please cc: me on any responses. I appreciate it…. Now to the issue: I have an svn archive that a student of mine was using in March. I am trying to access the files in the archive, however, when I try to access it, I get the following error: Found format '5', only

SVN 1.7.5 curiosity...

2012-11-13 Thread BRM
I'm running SVN 1.7.5 Command-line client on Kubuntu 12.10 with latest updates. What puzzles me is that when I run "svn status" it no longer reports the status of any svn:externals. Is this expected behavior? Or is there a bug? Working Copy is proper version for 1.7 series so far as I know. Ben

RE: Commit failed Error after upgrading 1.7.7

2012-11-13 Thread Bob Archer
> On Tue, Nov 13, 2012 at 10:22 AM, Bob Archer > wrote: > >> If you are using LDAP and the server is on Windows there is a bug in > >> Apache > >> 2.2.23 that can cause an HTTP 500 on the first authenticated request for a > user. > >> See: > >> > >> https://issues.apache.org/bugzilla/show_bug.cgi?

Re: Commit failed Error after upgrading 1.7.7

2012-11-13 Thread Mark Phippard
On Tue, Nov 13, 2012 at 10:22 AM, Bob Archer wrote: >> If you are using LDAP and the server is on Windows there is a bug in Apache >> 2.2.23 that can cause an HTTP 500 on the first authenticated request for a >> user. >> See: >> >> https://issues.apache.org/bugzilla/show_bug.cgi?id=54140 > > Mark

RE: Commit failed Error after upgrading 1.7.7

2012-11-13 Thread Bob Archer
> If you are using LDAP and the server is on Windows there is a bug in Apache > 2.2.23 that can cause an HTTP 500 on the first authenticated request for a > user. > See: > > https://issues.apache.org/bugzilla/show_bug.cgi?id=54140 Mark... that looks exactly what we are running into. Indeed we ar