[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Why does svn up give me a different file than in the repo

From: Eric Johnson <eric_at_tibco.com>
Date: Tue, 5 Mar 2019 10:41:55 -0800

Possibly a line-ending conversion?

http://svnbook.red-bean.com/nightly/en/svn.advanced.props.file-portability.html#svn.advanced.props.special.eol-style

Check to see if the svn:eol-style property is set.

Eric

On Tue, Mar 5, 2019 at 10:34 AM Satya Mishra <satya.devel_at_gmail.com> wrote:

> Hi,
>
> 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 19:42:22 CET

This is an archived mail posted to the Subversion Users mailing list.