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

Re: svn 1.8 causing locks to be broken on update

From: Felipe Alvarez <felipe.alvarez_at_gmail.com>
Date: Mon, 12 Aug 2013 13:38:47 +1000

On Mon, Aug 5, 2013 at 9:50 AM, Felipe Alvarez <felipe.alvarez_at_gmail.com>wrote:

> Maybe I'm missing something but what exactly is broken in your
>
>> output? It ends with svn up, but shouldn't be there at least one
>> additional svn st to show something about the lock?
>>
>> > Felipe_at_FELIPES ~/SVN
>> > $ svn up
>> > Updating '.':
>> > B Trunk\SystemAdmin\rsync_transfer.cron.FreshASPNEW
>> > B Trunk\SystemAdmin\rsync_transfer.cron.FreshBNE
>> > B Trunk\Lettus\lbin\backup.cron
>>
>> svn up doesn't show info about your locked file because it didn't
>> change or conflict with revisions from the repo.
>>
>> ​My apologies. I have tried it again, this time with final 'svn st'​
>
> ---begin output---
>
> Felipe_at_FELIPES ~/SVN/Trunk/Lettus/lbin
> $ svn st
>
> #---------------------------------------------
> # lock broken from previous update (last week)
> #---------------------------------------------
>
> Felipe_at_FELIPES ~/SVN/Trunk/Lettus/lbin
> $ svn lock backup.cron
> svn: warning: W160035: Path '/Trunk/Lettus/lbin/backup.cron' is already
> locked by user 'felipe' in filesystem '/u3/SVN_Repository/db'
>
> Felipe_at_FELIPES ~/SVN/Trunk/Lettus/lbin
> $ svn lock --force backup.cron
> 'backup.cron' locked by user 'felipe'.
>
> Felipe_at_FELIPES ~/SVN/Trunk/Lettus/lbin
> $ svn st
> K backup.cron
>
> Felipe_at_FELIPES ~/SVN/Trunk/Lettus/lbin
> $ cd ..
>
> Felipe_at_FELIPES ~/SVN/Trunk/Lettus
> $ svn up; svn st
> Updating '.':
> At revision 59397.
> K lbin\backup.cron
>
> Felipe_at_FELIPES ~/SVN/Trunk/Lettus
> $ cd ..
>
> Felipe_at_FELIPES ~/SVN/Trunk
> $ svn up; svn st
> Updating '.':
> At revision 59397.
>
> K Lettus\lbin\backup.cron
> ? SystemAdmin\rsync.sh
> M SystemAdmin\rsync_transfer.cron.FreshASPNEW
>
> M SystemAdmin\rsync_transfer.cron.FreshBNE
>
> Felipe_at_FELIPES ~/SVN/Trunk
> $ cd ..
>
> Felipe_at_FELIPES ~/SVN
> $ svn st
> MM Branches\Lettus\UAT\prod\autotest\code_check.sh
> K Trunk\Lettus\lbin\backup.cron
> ? Trunk\SystemAdmin\rsync.sh
> M Trunk\SystemAdmin\rsync_transfer.cron.FreshASPNEW
> M Trunk\SystemAdmin\rsync_transfer.cron.FreshBNE
> ? wclbin
>
>
> Felipe_at_FELIPES ~/SVN
> $ svn up
> Updating '.':
> B Trunk\Lettus\lbin\backup.cron
> At revision 59397.
>
> Felipe_at_FELIPES ~/SVN
> $ svn st
> MM Branches\Lettus\UAT\prod\autotest\code_check.sh
> ? Trunk\SystemAdmin\rsync.sh
> M Trunk\SystemAdmin\rsync_transfer.cron.FreshASPNEW
> M Trunk\SystemAdmin\rsync_transfer.cron.FreshBNE
> ? wclbin
>
> Felipe_at_FELIPES ~/SVN
> $
>
> ---end output---
>
> --
> Felipe
>
>
Has anybody been able to reproduce or confirm this problem?

Thanks

--
Felipe​
Received on 2013-08-12 05:40:09 CEST

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