Thanks for those tips Konstantin.
There are about 16 developers. Is there anything I can look at on the
server side to determine whether such bad directory copy/moves have been
done, and perhaps by whom?
> On the server: what protocol you are using to access the repository and
> commit the files?
HTTPS...I'm not sure what mechanisms happen "within" or "lower than"
that. Is this a helpful answer? If you need more info, please let me
know how I can find it out. I personally am a facilitator for
researching this issue, I'm not an admin.
> I hope there is no proxy in between you and client,
> that performs some sort of url rewriting?
>
No proxy, no rewriting.
>
>> We administer subversion (v 1.4.2, r22196 on CentOS 5.5)
>>
> Anyway, 1.4.2 is very old, and misses a number of fixes in 1.4.x line,
> not to mention the later versions. In some other thread recently when
> "CentOS 5.5" was mentioned one of the answers was to upgrade to 5.6
> ASAP.
>
Upgrading is non-trivial for us, for internal policy reasons (recall
150+ active repos). We realize that "upgrade now" would be a very strong
encouragement in this forum, and understand that rationale. With due
respect to that idea, I'm hoping we can identify why only one repository
manifests this issue, and maybe why, after an export / import to a new
repository, the problem appears in the new repo.
Again, thank you very much.
-Dave
Received on 2011-05-12 15:51:17 CEST