Re: svn error during 'make buildkernel'?

On Sat, Aug 03, 2013 at 02:30:23PM -0700, Steve Kargl wrote:
> 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.
> 

The port was at 1.8.x before I added the additional lookup of
svnlite to the script.  There really is no need for UPDATING entry,
since 1.7.9 is deprecated, and the behavior you have seen is not a fatal
error with the buildkernel process.

BTW, you should upgrade devel/subversion anyway, since there are
security vulnerabilities.

Glen