From owner-freebsd-ports@FreeBSD.ORG Tue May 12 06:47:43 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 24C4441D for ; Tue, 12 May 2015 06:47:43 +0000 (UTC) Received: from so.liwest.at (so.liwest.at [212.33.55.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D3BF31EBE for ; Tue, 12 May 2015 06:47:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=liwest.at; s=20140502; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version:Content-Type; bh=x7KB54dpOdJfaTGV1RrS0fpZbZ4PCkLVsEqfCEU2lXA=; b=hdDrStBmESa4ZuDlqHwaElGqZysuwlAUZWEZh32oBaw1j5KDRFPTh0/1LJzZdqrVJ1zPGkwqyx8BKvnXAwFA+MZBHmgpg96A+LuCdVGoxvBX19TA3YNPD9d/gDZmZwB1ykevqf7e/QIOsCvph0DtYfKx35MGEqC9tQ6+R55EdG5Pu2iNszWNAI7TYJgyw+Gv+Q7L7xLa3hpYVKTd3NDV6podty/+e1RaW7V+2zTvIzGhhH5ALvmhIEkgPTXDBAFTetTIAPCQM4HW9TlWez2eyiHXyAZx2MvbRRDjh6VFW37WYt6xtWE2xIJ64DqvGxqtd//1xiuFfggL49MgGAbvQQ==; Received: from [90.146.7.130] (helo=[192.168.35.4]) by so.liwest.at with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1Ys3ye-00026r-3f; Tue, 12 May 2015 08:47:41 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) Subject: Re: persistent svn error message From: horst leitenmueller In-Reply-To: <201505120602.t4C62qli023867@sdf.org> Date: Tue, 12 May 2015 08:47:31 +0200 Cc: David Wolfskill , freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <8EED8AF7-875A-457E-AF61-9ACC22D71EB9@liwest.at> References: <201505111209.t4BC92Qb029366@sdf.org> <0EF0B2FD-7C3A-4077-9D97-1CA59F782724@liwest.at> <201505120602.t4C62qli023867@sdf.org> To: Scott Bennett X-Mailer: Apple Mail (2.2098) X-Spam-Score: -1.0 (-) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 May 2015 06:47:43 -0000 hi Scott, you have solved it now ?=20 do you still geht the error if you do an update=20 cd /usr/ports/databases/ svn up ? you can also make a=20 cd /usr/ports/databases/innotop svn diff=20 (http://svnbook.red-bean.com/de/1.7/svn-book.html#svn.ref.svn.c.diff ) which shows you the differences from your svn tree to the remote one please is problem still exists, do a=20 cd /usr/ports/ svn info =20 with this info i can check what happened with this node=20 br horst did you have deleted=20 > On 12 May 2015, at 08:02, Scott Bennett wrote: >=20 > horst leitenmueller wrote: >=20 >> you can try to follow this posting >>=20 >> = http://stackoverflow.com/questions/13376483/how-to-solve-svn-error-e155010= >>=20 >> first: >>=20 >> svn cleanup (in /usr/ports/) >>=20 >> if not helping you have to check WHY this node was not updated/ = removed or whatever.. >>=20 >> hope info helps a little >>=20 > I took a look at that page. Its example shows two error messages, = the > latter of which looks like the one I got. But I didn't get any other = error. > Nevertheless, I did try the rest of the procedure, but it didn't make = any > difference (other than to download all the updates that had = accumulated over > the last several days that I had not been running "svn update" on = /usr/ports. > However, the web site looked pretty cool, so I'm bookmarking it = for the > future. :-) > On Mon May 11 12:49:06 2015 David Wolfskill = wrote: >=20 >> I don't know what causes it, but if your /usr/ports is just an SVN >> working copy, I suspect tha tthe easiest course of action would be to >=20 > It nearly is. >=20 >> move it aside (by renaming it), then checking out a fresh new copy. >>=20 >> (You could then move over anything that hadn't been created by SVN, >> e.g., the former /usr/ports/distfiles and /usr/ports/packages, and = blow >=20 > I recovered distfiles and local patches, but...oops...forgot = packages. > However, I did back up the old /usr/ports, which is where I recovered = the > distfiles from, so I can get packages back, too. Thanks for the = reminder! >=20 >> away the old /usr/ports -- or keep it around to try to figure out = what >> was causing the issue.) >>=20 > Well, given that a new checkout got rid of the problem message, I = can > surmise that the problem was indeed on my system and not the server. = I'm > unlikely to find the source of the problem, but the web page to which = Horst > directed me did have a comment added by a later poster that suggested = that > an interrupted svn run might have been the origin of the problem. I = don't > like doing those checkouts because they take so long, which was why I = was > hoping to find a shorter method of correction. Oh, well...on to the = next > problem on my list (but in a separate posting). > Thanks much to both of you for your replies. >=20 >=20 > Scott Bennett, Comm. ASMELG, CFIAG > ********************************************************************** > * Internet: bennett at sdf.org *xor* bennett at freeshell.org * > *--------------------------------------------------------------------* > * "A well regulated and disciplined militia, is at all times a good * > * objection to the introduction of that bane of all free governments * > * -- a standing army." * > * -- Gov. John Hancock, New York Journal, 28 January 1790 * > **********************************************************************