From owner-freebsd-current@FreeBSD.ORG Tue Aug 6 18:20:42 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 870E7C30; Tue, 6 Aug 2013 18:20:42 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from thyme.infocus-llc.com (server.infocus-llc.com [206.156.254.44]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5B02F2E1A; Tue, 6 Aug 2013 18:20:41 +0000 (UTC) Received: from draco.over-yonder.net (c-75-65-60-66.hsd1.ms.comcast.net [75.65.60.66]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by thyme.infocus-llc.com (Postfix) with ESMTPSA id E811937B5BB; Tue, 6 Aug 2013 13:11:07 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 3c8kRv1zjQzSqN; Tue, 6 Aug 2013 13:11:07 -0500 (CDT) Date: Tue, 6 Aug 2013 13:11:07 -0500 From: "Matthew D. Fuller" To: Glen Barber Subject: Re: svn error during 'make buildkernel'? Message-ID: <20130806181107.GR34979@over-yonder.net> References: <20130803210348.GA715@troutmask.apl.washington.edu> <20130803210858.GJ78299@glenbarber.us> <20130803213023.GA812@troutmask.apl.washington.edu> <20130803214313.GL78299@glenbarber.us> <20130804232358.GA6068@troutmask.apl.washington.edu> <20130805004433.GA6355@troutmask.apl.washington.edu> <20130805005530.GL2352@glenbarber.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130805005530.GL2352@glenbarber.us> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.21-fullermd.4 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.8 at thyme.infocus-llc.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org, Peter Wemm , Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 18:20:42 -0000 On Sun, Aug 04, 2013 at 08:55:30PM -0400 I heard the voice of Glen Barber, and lo! it spake thus: > > The error generated is non-fatal, and once I receive response on a > proposed patch, will be suppressed if the svn version used to check > out the tree is not compatible with that used to check the version > of the tree with the kernel build. But not try the ports svn as well? I mean, as breakage goes, it's not even in the top 100; I'd _much_ rather have a kernel that I have to guess the revision of but boots, than one properly recorded that doesn't. But it's still unpleasant, and is one of those things you probably won't notice missing until suddenly you need it. And this isn't just a presentism. Sure, right _now_ devel/subversion and base svnlite get along, but what happens when ports moves to 1.9 which changes the WT format? Even if -CURRENT src gets upgraded simultaneously[0], the same surely can't be said of every back branch. I realize this is all still a WIP, and please don't read any anger into my words. But this _has_ been something I've found a little worrisome since the original import/newvers change. Heck, newvers can show me version info if I'm getting my source tree from git or p4, but can't handle ports svn? By the time this works its way into a stable branch, I really think it should either handle svnversion from ports as well, or come with a big bright flashing warning that using svn from anything but base svnlite for /usr/src is a degraded experience. [0] Which still wouldn't really fix things, since /usr/bin/svnliteversion is arbitrarily old, not up to date with the source tree. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.