From owner-freebsd-ports@FreeBSD.ORG Tue May 12 07:07:38 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5791C91D for ; Tue, 12 May 2015 07:07:38 +0000 (UTC) Received: from sdf.lonestar.org (mx.sdf.org [192.94.73.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx.sdf.org", Issuer "SDF.ORG" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 390991112 for ; Tue, 12 May 2015 07:07:37 +0000 (UTC) Received: from sdf.org (IDENT:bennett@otaku.freeshell.org [192.94.73.9]) by sdf.lonestar.org (8.14.8/8.14.5) with ESMTP id t4C7716G001383 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO); Tue, 12 May 2015 07:07:01 GMT Received: (from bennett@localhost) by sdf.org (8.14.8/8.12.8/Submit) id t4C770Ng005608; Tue, 12 May 2015 02:07:00 -0500 (CDT) From: Scott Bennett Message-Id: <201505120707.t4C770Ng005608@sdf.org> Date: Tue, 12 May 2015 02:07:00 -0500 To: horst.leitenmueller@liwest.at Subject: Re: persistent svn error message Cc: freebsd-ports@freebsd.org, david@catwhisker.org References: <201505111209.t4BC92Qb029366@sdf.org> <0EF0B2FD-7C3A-4077-9D97-1CA59F782724@liwest.at> <201505120602.t4C62qli023867@sdf.org> <8EED8AF7-875A-457E-AF61-9ACC22D71EB9@liwest.at> In-Reply-To: <8EED8AF7-875A-457E-AF61-9ACC22D71EB9@liwest.at> User-Agent: Heirloom mailx 12.5 6/20/10 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 07:07:38 -0000 horst leitenmueller wrote: > you have solved it now ? As I wrote before, I took David Wolfskill's suggestion when the method on the web page you suggested made no difference. I backed up /usr/ports (and I still have the backup), unmounted it, newfs'ed the partition, remounted it, and then ran the svn checkout. I dislike doing that very often because of the time it takes and the nuisance of having to save and restore a few things, but it does usually cause many sins to be forgotten. :-> > > do you still geht the error if you do an update > > cd /usr/ports/databases/ > svn up > > ? Yes, I did still get the error. The procedure did not appear to have had any effect whatsoever, which is why I proceeded with the other method (see above and in previous followup). > > you can also make a > > cd /usr/ports/databases/innotop > svn diff > > (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 > > cd /usr/ports/ > svn info > > with this info i can check what happened with this node > I'd rather not do that now that the problem has been dealt with. To do what you ask, I would have to blow away the newly checked out /usr/ports and restore the old one from the backup. Sorry about that. :-) 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 * **********************************************************************