Date: Sat, 3 Aug 2013 14:30:23 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Glen Barber <gjb@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: svn error during 'make buildkernel'? Message-ID: <20130803213023.GA812@troutmask.apl.washington.edu> In-Reply-To: <20130803210858.GJ78299@glenbarber.us> References: <20130803210348.GA715@troutmask.apl.washington.edu> <20130803210858.GJ78299@glenbarber.us>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Aug 03, 2013 at 05:08:58PM -0400, Glen Barber wrote: > On Sat, Aug 03, 2013 at 02:03:49PM -0700, Steve Kargl wrote: > > I updated my /usr/src with subversion from ports: > > > > % pkg info | grep subver > > subversion-1.7.9_1 Version control system > > > > 'make buildworld' completed as expected. 'make buildkernel' > > seems to complete, but I'm seeing > > > > :> hack.c > > cc -shared -nostdlib hack.c -o hack.So > > rm -f hack.c > > MAKE=make sh /usr/src/sys/conf/newvers.sh MOBILE > > svn: E155036: The working copy at '/usr/src' > > is too old (format 29) to work with client version '1.8.0 (r1490375)' (expects format 31). You need to upgrade the working copy first. > > > > > Why is svn being run during 'make buildkernel'? More importantly, > > why is the freshly built svn in /usr/obj being invoked when it > > has not previously been installed and so /usr/src may indeed be > > in a older, yet valid, format? > > > > src/sys/conf/newvers.sh sets the svn revision, which is printed by > uname(1). > > devel/subversion is at version 1.8.x, so you should upgrade your > installed port. Or you can use /usr/bin/svnlite directly, and run: > > # /usr/bin/svnlite upgrade /usr/src > Thanks. Looks like an entry in /usr/src/UPDATING is missing if /usr/bin/svn* is forcing an obsolscence of a functioning installed port. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130803213023.GA812>