[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: Thorsten Schöning <tschoening_at_am-soft.de>
Date: Sun, 4 Aug 2013 16:58:47 +0200

Guten Tag Felipe Alvarez,
am Sonntag, 4. August 2013 um 06:41 schrieben Sie:

> ​'m using tortoiseSVN, and noticed that when updating the very root
> of the repository, locks which I have taken under it become broken. Here is output from cygwin.

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.

Mit freundlichen Grüßen,

Thorsten Schöning

Thorsten Schöning       E-Mail:Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Received on 2013-08-04 16:59:22 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.