svn error during 'make buildkernel'?

Steve Kargl sgk at troutmask.apl.washington.edu
Mon Aug 5 01:15:19 UTC 2013


On Sun, Aug 04, 2013 at 08:55:30PM -0400, Glen Barber wrote:
> On Sun, Aug 04, 2013 at 05:44:33PM -0700, Steve Kargl wrote:
> > >   If you want to upgrade, and use http/https access to repositories,
> > >   please check, that SERF option is enabled, as NEON support
> > >       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > 
> > I did not want to upgrade.  It was suggested/forced on me
> > by revisio 252505 of newvers.sh that looks for svnliteversion instead
> > of the installed svnversion.  1.7.9 was working fine.
> > 
> 
> You were not forced to do anything.
> 
> If svn 1.7.9 works, great.  Use it.
>
> 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.

I don't care if it was nonfatal or not.  An prominent ERROR message
during 'make buldkernel' should set off an alarm in anyone's head. 

> 
> But seriously, this is -CURRENT.  Things change.
> 

Yeah,  I've been running -current since it was called 386bsd+patchkit
some 20 years ago.  In the old days, committers cared about the quality
of their commits.  When informed of an issue, they looked into the 
problem instead of blaming the users.

-- 
Steve


More information about the freebsd-current mailing list