[ILUG] Subversion not seeing working copy changes

[Sean Ryan]

Naill,
Excellent catch - had more or less figured out that something like that was
the problem not before I hosed a working copy.


I did manage to work around using a similar mechanism

vim  $(find . -name '*.h' -o -name '*.cpp' -o -name '*Makefile*' -o -name
'*.pc'  -o -name '*.java' -o -name '*.py' | grep -v svn) then within vim
using
 
argdo %s/PATTERN1/PATTERN2/g | wq

Which worked a treat

Thanks,
Sean
On 22/10/2009 20:32, "Niall O Broin" <niall at magicgoeshere.com> wrote:

> On 22 Oct 2009, at 15:35, Éibhear wrote:
> 
>> Hi Sean,
>> 
>> Your problem is in your find command:
>> 
>> find . -type f...
>> 
>> will find *all* files, including all the files in the .svn
>> directories.
>> The sed command will be executed on both the working copy files, and
>> the
>> meta-data versions that subversion keeps for local comparison
>> purposes.
>> Therefore, svn doesn't see that the files have changed, as the
>> "backups"
>> it maintains are changed in exactly the same way.
>> 
>> You'll need to exclude all files in all .svn directories from your
>> find
>> command. Off the top of my head, I don't know how you'd do that.
>> 
>> One possibility is:
>> 
>> find . -type f -print | grep -v '\.svn' | \
>>    xargs sed -i 's/FILE1.h/FILE2.h/g'
> 
> 
> Instead of   find .    simply use find *
> 
> 
> Niall
> 
> --
> Irish Linux Users' Group mailing list
> About this list : http://mail.linux.ie/mailman/listinfo/ilug
> Who we are : http://www.linux.ie/
> Where we are : http://www.linux.ie/map/