From owner-freebsd-current@FreeBSD.ORG Sat Aug 3 22:29:35 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 55816F7E; Sat, 3 Aug 2013 22:29:35 +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 2A74D2044; Sat, 3 Aug 2013 22:29:34 +0000 (UTC) Received: from glenbarber.us (70.15.88.86.res-cmts.sewb.ptd.net [70.15.88.86]) (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 F3EBD85B8; Sat, 3 Aug 2013 22:29:32 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us F3EBD85B8 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Sat, 3 Aug 2013 18:29:30 -0400 From: Glen Barber To: Anton Shterenlikht Subject: Re: svn error during 'make buildkernel'? Message-ID: <20130803222930.GO78299@glenbarber.us> References: <20130803221702.GA979@troutmask.apl.washington.edu> <201308032221.r73MLqVm040351@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="WoqaC9TUMqqIOlla" Content-Disposition: inline In-Reply-To: <201308032221.r73MLqVm040351@mech-cluster241.men.bris.ac.uk> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org, sgk@troutmask.apl.washington.edu 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: Sat, 03 Aug 2013 22:29:35 -0000 --WoqaC9TUMqqIOlla Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 03, 2013 at 11:21:52PM +0100, Anton Shterenlikht wrote: > >svn repository. The change to use svnlite in newvers.sh should > >have an entry in UPDATING to alert users that have a too old=20 > >svn port that they need to upgrade. I go as far to suggest that >=20 > I agree. > To me this is a sort of change that > should be mentioned in src/UPDATING. >=20 If a tree was checked out 2 months ago, and devel/subversion was upgraded from 1.7.x to 1.8.x, when the src/ tree is next updated (or attempted), the user would be prompted to run 'svn upgrade'. Again, this was added *after* the devel/subversion port was updated to 1.8.x (now almost 2 months ago). Adding an entry to UPDATING when both the base svn and the ports svn are both at 1.8.x is not reasonable. Additionally, if WITHOUT_SVNLITE is set, then svnlite would not be built, and the ports version would be used. Glen --WoqaC9TUMqqIOlla Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJR/YRKAAoJEFJPDDeguUajOPEH/26E5zHF+5omEWa2fk0Cq7ca 5EOopOkpvHcbznH2vtP3r2ZDH3NtkkOHhMnb2Pw2buSCzO6sJBhNz+PLFCyl5wqb HiDynPus4baXkkkEb6+NyIDSFbt9De98I/Z+3xbmFsqcRzK9o2r2+8GpxKH5jsAG ePRXQR9yi5NS3tRDAf6UfyQUSLP1xih3Ngn23EgGoJkM3GyZfBD6wtZHQFd6ZvaK d4SwNe8eH/TaqH+kHRFuGx2zQJVSxoyOdLQRv/qS8ae0TJSSbgEMztGIjfZSHxmo h/hf3x/ZXmQCHjvmBwItSTxDtiC+TBxmFjmTSHF72m/2k5IWyGAdHDnkIP7ApZ4= =HwY1 -----END PGP SIGNATURE----- --WoqaC9TUMqqIOlla--