On 08/05/2007 7:34 AM, Jonathan Ashley wrote:
> Hello,
>
> I have a problem with a particular file, where Subversion seems to think
> the file is unchanged even after it has been changed. This means I can't
> commit it back. I'd welcome opinions on whether this is a problem with
> the tool, or whether it's my setup that's wrong.
>
> The file is a binary file that is two bytes long, 0x01 followed by 0x3F.
> It needs to be changed to 0x01 followed by 0x0F. It has properties
> 'svn:mime-type = application/octet-stream', and 'svn:needs-lock = *'.
Does the "last modification date" of the file change when you edit it?
If not, svn won't look at the contents. (There have been lots of
requests to change this behaviour, see the archives.)
Duncan Murdoch
>
> If I get the lock and do the edit, then 'svn diff' doesn't notice a
> change. Using Tortoise, the overlay icon stays as a green tick too.
> However, the Tortoise "check for modifications" command *does* identify
> the changed file, but lists 'text status' as 'normal' (where I would
> have expected 'modified').
>
> I also tried repeating this with a fresh working copy, just in case the
> WC was subtly corrupt.
>
> Command line client 1.4.2 r22196; using Apache server (same version)
> with SSPI authentication to access repository.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 10 03:21:50 2007