RE: SVN 1.8.1 Errors - Show Log and Commit New Files - SOLVED (FOR ME)

> From: Geoff Field
> Sent: Friday, 16 August 2013 11:56 AM
> Thanks to everybody for their patience with my issue. The
> root cause is not really solved, but at least I (and my
> colleagues) can get back to normal work patterns.
>
> I've finally managed to get the upgrade to Apache 2.2 and SVN
> server 1.6.9 running. As it turns out, my former colleagues
> had deliberately configured all the ports one up from the
> default (thus, SSL was running on port 444 instead of the
> default 443). Once I'd fixed this, Apache 2.2 started
> serving SVN via the default interfaces.
>
> With that, I can now run everything happily.

It seems I spoke too soon. It turns out that the updated SVN server 1.6.9 works for those few of our repositories that are in FSFS format. Unfortunately, our legacy repositories are almost all in BDB format and I'm loathe to touch them if I can avoid it.

Building SVN from source is not really a useful option, but we can do it (with a struggle) if we absolutely have to. Frankly, I'd rather convert all the repositories (and there are 100 all up, although some are in FSFS format already) than build the server code. Has anybody built a version that handles BDB in a DAV module?

> I have not deleted the Apache 2.0/SVN server 1.2.3
> configuration, so I should be able to switch back to that if
> needed. I suppose it's possible some repositories might
> become inaccessible to the earlier server due to the server
> upgrade, but I'm not particularly fussed about that.

We can swap back to the other version fairly easily if we have to, just by stopping Apache2.2 and starting Apache2 (or vice-versa).

Regards,

Geoff

-- 
Geoff Field
Testing Coordinator, Work Health & Safety Rep, Chief Fire Warden, First Aider
Australian Arrow Pty Ltd www.australianarrow.com.au
46 Lathams Rd, Carrum Downs, Vic, 3201, Australia
phone (+61-3) 97850597, fax (+61-3) 9785 0583
GYNET x-067-597 
- The contents of this email, and any attachments, are strictly private
and confidential.
- It may contain legally privileged or sensitive information and is intended
solely for the individual or entity to which it is addressed.
- Only the intended recipient may review, reproduce, retransmit, disclose,
disseminate or otherwise use or take action in reliance upon the information
contained in this email and any attachments, with the permission of
Australian Arrow Pty. Ltd.
- If you have received this communication in error, please reply to the sender
immediately and promptly delete the email and attachments, together with
any copies, from all computers.
- It is your responsibility to scan this communication and any attached files
for computer viruses and other defects and we recommend that it be
subjected to your virus checking procedures prior to use.
- Australian Arrow Pty. Ltd. does not accept liability for any loss or damage
of any nature, howsoever caused, which may result
directly or indirectly from this communication or any attached files.