From owner-freebsd-arm@freebsd.org Wed Mar 29 00:52:43 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B40BD1E44E for ; Wed, 29 Mar 2017 00:52:43 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4B62E3F3A for ; Wed, 29 Mar 2017 00:52:42 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id v2T0ql5d041940 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 28 Mar 2017 17:52:47 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v2T0qke3041939; Tue, 28 Mar 2017 17:52:46 -0700 (PDT) (envelope-from fbsd) Date: Tue, 28 Mar 2017 17:52:46 -0700 From: bob prohaska To: ticso@cicely.de Cc: freebsd-arm@freebsd.org Subject: Re: Uname -a no longer reports revision number on RPI2 Message-ID: <20170329005245.GB41615@www.zefox.net> References: <20170329003055.GA41615@www.zefox.net> <20170329003520.GD88450@cicely7.cicely.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170329003520.GD88450@cicely7.cicely.de> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Mar 2017 00:52:43 -0000 On Wed, Mar 29, 2017 at 02:35:20AM +0200, Bernd Walter wrote: > > The revision number uses svnversion on a subversion worktree. > If you've got your source in any other way this can't work. > > -- Ok, that makes sense, I started using svnup when svnlite stopped working: root@www:/usr # svnlite checkout https://svn.FreeBSD.org/base/head /usr/src svn: E175003: Attempt to fetch capability 'depth' resulted in 'yes' root@www:/usr # The error is identical, whether checkout out a new tree or just updating an existing one. I think the problem is a damaged config file, but I haven't found it. Thanks for reading, and any guidance! bob prohaska