From owner-freebsd-questions@FreeBSD.ORG Tue Jun 25 23:26:44 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D465DDA7; Tue, 25 Jun 2013 23:26:44 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id 875671C1D; Tue, 25 Jun 2013 23:26:44 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.7/8.14.7) with ESMTP id r5PNQPv9024723 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 25 Jun 2013 18:26:25 -0500 (CDT) (envelope-from tundra@tundraware.com) Message-ID: <51CA2720.9070009@tundraware.com> Date: Tue, 25 Jun 2013 18:26:24 -0500 From: Tim Daneliuk User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: Cannot Update Source Tree After Move To Subversion 1.8 References: <51C89DC4.20908@tundraware.com> <51C8AA24.1050202@FreeBSD.org> <51C8C113.3060504@tundraware.com> In-Reply-To: <51C8C113.3060504@tundraware.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (ozzie.tundraware.com [192.168.0.1]); Tue, 25 Jun 2013 18:26:25 -0500 (CDT) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: r5PNQPv9024723 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Cc: lev@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 23:26:44 -0000 On 06/24/2013 04:58 PM, Tim Daneliuk wrote: > On 06/24/2013 03:20 PM, Matthew Seaman wrote: >> On 24/06/2013 20:28, Tim Daneliuk wrote: >>> After the update to svn 1.8, I did a new svn co of the FBSD 9-STABLE >>> source branch. When I try to do an update to it, I see this now: >>> >>> svn: E155005: Working copy not locked at /usr/scr >>> svn co svn://svn.freebsd.org/base/stable/9 /usr/src >>> >>> /usr/src is a symlink to another directory in a separate filesystem, >>> but this historically worked, so I'm guess that is not the problem. >>> >>> Ideas? >>> >> >> svn upgrade > > > > Hmmmmm .... > > [root] ozzie ~>svn upgrade /usr/src > [root] ozzie ~>svn update /usr/src > svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) > svn: E155004: Working copy '/usr1/src-9-STABLE' locked. > svn: E155004: '/usr1/src-9-STABLE' is already locked. > [root] ozzie ~>svn cleanup /usr/src > [root] ozzie ~>svn update /usr/src > Updating '/usr/src': > svn: E155005: No write-lock in '/usr/src/sys' > svn: E155005: Additional errors: > svn: E155005: Working copy not locked at '/usr/src'. > > > It seems that svn 1.8 does not like symlinks. I have this: /usr/src -> /usr1/src-9-STABLE I can do this fine: svn update /usr1/src-9-STABLE But this causes svn to dump core: svn update /usr/src At which point I have to do a cleanup to get the locks cleared out. -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/