Thanks a lot for the suggestion. This is a binary file. I double checked
the properties (output below signature)
I also noticed another thread titled " E155011 + E160013: how to clear this
mess? " which seems to be a similar issue. But svn up --set-depth empty,
which worked for the other user, didn't fix it for me.
> svn pl projfile
Properties on 'projfile':
> svn pg svn:mime-type projfile
On Tue, Mar 5, 2019 at 12:42 PM Eric Johnson <eric_at_tibco.com> wrote:
> Possibly a line-ending conversion?
> Check to see if the svn:eol-style property is set.
> On Tue, Mar 5, 2019 at 10:34 AM Satya Mishra <satya.devel_at_gmail.com>
>> I recently encountered a strange problem while trying to revert a failed
>> experiment. svn revert apparently succeeded, but kept giving me the
>> unreverted files. Example shell output showing the problem is below. The
>> sha1sum of the file doesn't match the sha1sum from repo in this working
>> copy. But it does in a freshly checked out working copy. I am using
>> Subversion 1.10.3 on CentOS 7. I'll greatly appreciate any insight into why
>> this might happen.
>> > rm -f projfile
>> > svn up projfile
>> Updating 'projfile':
>> Restored 'projfile'
>> At revision 6878.
>> > sha1sum projfile
>> c58a4e654e2e8ac565e9705a7f83901a3ea7e321 projfile
>> > svn info projfile
>> Path: projfile
>> Name: projfile
>> Working Copy Root Path: ~/proj
>> URL: svn://repohost/proj/trunk/projfile
>> Relative URL: ^/proj/trunk/projfile
>> Repository Root: svn://repohost
>> Repository UUID: .....
>> Revision: 6878
>> Node Kind: file
>> Schedule: normal
>> Last Changed Author: satya
>> Last Changed Rev: 5734
>> Last Changed Date: 2018-03-27 12:03:21 -0700 (Tue, 27 Mar 2018)
>> Text Last Updated: 2019-03-05 10:03:46 -0800 (Tue, 05 Mar 2019)
>> Checksum: 6c0ff2498b56833e603908a66a284351ad0ec7dc
Received on 2019-03-05 21:25:54 CET