The copy of the file in .svn/base-text was incorrect. While I have just
started working from a fresh checkout, it would be nice to workout what
caused the problem so it can be avoided in the future. Can messing with the
timestamp of the file in you working area still cause a problem with the
update command not getting the correct modifications from the server?
Although I could have made a mistake somewhere I don't think I've messed
with anything in the .svn directory and I would have thought that any
changes made to the actual working copy file shouldn't effect that operation
anyway.
On 03/09/07, Ryan Schmidt <subversion-2007b@ryandesign.com> wrote:
>
>
> On Sep 2, 2007, at 19:55, Clint Lawrence wrote:
>
> > I have a file in my working copy that doesn't appear to get updated
> > correctly. I have also run an svn cleanup on the working copy
> > previously. I've also checked out a fresh copy of the trunk and
> > tried the same operations and it works fine, so it looks like
> > something in this particular working copy is corrupt.
> >
> > Does this look like a bug, or have I just done something stupid
> > along the way and need to start with a fresh checkout?
>
> If a fresh working copy works correctly, use that new working copy
> and discard the old one. Strange things can happen sometimes.
>
> Did you happen to modify a file but not update its timestamp, or use
> a utility that behaves that way? That's a good way to muck up the
> working copy.
>
>
>
Received on Mon Sep 3 05:57:21 2007