On Thu, Aug 03, 2017 at 11:10:07AM +0000, Baker, Randy (US) (Contractor)
> Thank you for the speedy reply, and Yes, on purpose. I didn't think
> the list could benefit from the language in my last email. So, if I
> may more thoroughly explain : I'm a new hire here at this firm, tasked
> with upgrading the Subversion server from RHEL 5x to 7x. That was done
> successfully, but a user suggested I also upgrade the repos as well to
> benefit from the new server's features. The current server (from which
> I ran 'svnadmin upgrade') is 1.6.11. At the time, it was the only
> management server connected to NetApp (repos). Now, when users
> attempt any svn work, they get the error I reported in the ticket.
There must be a missing link in this story somewhere.
A 1.6.11 'svnadmin upgrade' would *not* create a format 5 repository.
It would create format 4.
Are you 100% sure that you (or someone else) didn't run 'svnadmin upgrade'
with a 1.7 alpha release accidentally? That's the only possible
explanation for the error you are seeing. At least I cannot think of
any other reason (apart from manual meddling with repository data, but
that's obviously not a supported use case either).
How many repositories are affected by this? All of them? Just one?
Received on 2017-08-03 13:36:14 CEST