On Sun, 14 Jul 2013 18:15:52 +0200 cpghost <cpgh...@cordula.ws> wrote:
> On 07/13/13 03:03, Dan Mack wrote: > > I'm not sure exactly when but recently I've lost the subversion id > > from kern.version and hence uname and motd. > > > > Subsequent fresh rebuilds from source don't bring it back even after > > wiping out the tree. > > > > Today it looks like this: > > > > root@olive:~ # uname -a > > FreeBSD olive.example.com 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Fri > > Jul 12 19:38:24 CDT 2013 > > r...@olive.example.com:/usr/obj/usr/src/sys/MACKGEN amd64 > > root@olive:~ # sysctl kern.version > > kern.version: FreeBSD 10.0-CURRENT #0: Fri Jul 12 19:38:24 CDT 2013 > > r...@olive.example.com:/usr/obj/usr/src/sys/MACKGEN > > > > Previously it would have '#0 r253307' in it's place. > > > > This only happened on 1 of 3 build machines. > > There was an update to subversion recently (1.7.x to 1.8.y). > If you updated the /usr/src tree with the new subversion > (i.e. svn upgrade; svn update), and then transferred that tree > to another machine that contains a non-upgraded subversion > client, if you build the tree there, you'll miss the r###### in > uname. > > Upgrade your subversion client on the target machine, and, > optionally, run 'svn upgrade' on the source tree, then rebuild > and reinstall. uname -a should show r###### again. > > > dan > > -cpghost. > 2 gjb@: That is a case, when we have 1.7.x checkout and _possible_ subversion17 installed. We was talking few weeks ago about that. (efnet@tigerby) -- wbr, tiger _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
