> Thanks for those tips Konstantin.
> There are about 16 developers. Is there anything I can look at on
> server side to determine whether such bad directory copy/moves have
> 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
> that. Is this a helpful answer? If you need more info, please let
> 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
> > not to mention the later versions. In some other thread recently
> > "CentOS 5.5" was mentioned one of the answers was to upgrade to
> > ASAP.
> Upgrading is non-trivial for us, for internal policy reasons
> 150+ active repos). We realize that "upgrade now" would be a very
> encouragement in this forum, and understand that rationale. With
> respect to that idea, I'm hoping we can identify why only one
> manifests this issue, and maybe why, after an export / import to a
> repository, the problem appears in the new repo.
Does the same team us more than one repository? Or is each repo used by different people and teams?
Is the update funky when there is no file on the disk, or only when merging into an existing file?
What encoding are the files using? I have found that svn doesn't really work well with Unicode files.
Is it always the same file(s) or different ones each time?
Received on 2011-05-12 16:20:44 CEST