From owner-freebsd-current@FreeBSD.ORG Tue Aug 6 18:31:04 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 456F5ED6; Tue, 6 Aug 2013 18:31:04 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F06FA2E9A; Tue, 6 Aug 2013 18:31:03 +0000 (UTC) Received: from glenbarber.us (unknown [IPv6:2001:470:8:120e:1:1:c57c:729]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id D20CFA733; Tue, 6 Aug 2013 18:30:55 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us D20CFA733 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Tue, 6 Aug 2013 14:30:54 -0400 From: Glen Barber To: "Matthew D. Fuller" Subject: Re: svn error during 'make buildkernel'? Message-ID: <20130806183054.GB2190@glenbarber.us> 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> <20130806181107.GR34979@over-yonder.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="QTprm0S8XgL7H0Dt" Content-Disposition: inline In-Reply-To: <20130806181107.GR34979@over-yonder.net> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) 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:31:04 -0000 --QTprm0S8XgL7H0Dt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 06, 2013 at 01:11:07PM -0500, Matthew D. Fuller wrote: > On Sun, Aug 04, 2013 at 08:55:30PM -0400 I heard the voice of > Glen Barber, and lo! it spake thus: > >=20 > > 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. >=20 > 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. >=20 > 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. >=20 > 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. >=20 >=20 > [0] Which still wouldn't really fix things, since > /usr/bin/svnliteversion is arbitrarily old, not up to date with > the source tree. >=20 I have this on my todo list, but right now I have bigger things to deal with. As soon as I can, I will fix the logic. Right now, it is not "as easy as checking which svn works", because the more I look at the logic for newvers.sh, the more I dislike how it all works. Glen --QTprm0S8XgL7H0Dt Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJSAUDeAAoJEFJPDDeguUaj2xIH/11KAffErE4gjYwBxuPe43h+ CNCtuQjxMm6iqowJNap6MnShYHKiTmllqHdIgo+qk9MIKJjw6EDq3ox+7kAaht69 eMEaYGkVQkKBK7i0+gyR/xApLHWx2WSlpUt4xhWKL67ScISOToYv2MWMO7IahRV7 GtzHfiP+DxEfYZ7xYp4h68T/M2TNnOQdDclP6n82ii3tJbPKX6jYJzxP52fWPFpK Zu/9kRbKdAzfuOkk2z068Vrp8KCSvE25+/d/BjziTPNIs9MTZW1HVSBtjuUn1moq JgBfeEVJrO1Dhs7+FgBtDh0AZmcUtzL0HV2wfyCBWdwm1NABXJ8jMHIOn6uS6tc= =suAp -----END PGP SIGNATURE----- --QTprm0S8XgL7H0Dt--