Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Feb 2009 09:34:08 -0900
From:      Mel <fbsd.questions@rachie.is-a-geek.net>
To:        freebsd-questions@freebsd.org
Cc:        Paul Schmehl <pschmehl_lists@tx.rr.com>
Subject:   Re: RELENG_7 != STABLE?
Message-ID:  <200902250934.09429.fbsd.questions@rachie.is-a-geek.net>
In-Reply-To: <alpine.BSF.2.00.0902251114410.49033@wonkity.com>
References:  <591F97E51551F72295A54D9D@utd65257.utdallas.edu> <B3036F295322199AAA14F9BF@utd65257.utdallas.edu> <alpine.BSF.2.00.0902251114410.49033@wonkity.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 25 February 2009 09:16:51 Warren Block wrote:
> On Wed, 25 Feb 2009, Paul Schmehl wrote:
> > --On Tuesday, February 24, 2009 23:02:36 -0600 Mel
> >
> > <fbsd.questions@rachie.is-a-geek.net> wrote:
> >> Presence of tag enables checkout mode, so it's not that you have a cvs
> >> repo copy. Kernel date tag suggests a reboot, so the only thing that
> >> comes to mind
> >> is newvers.sh not having done it's job or UNAME_r set in env.
> >> sysctl kern.osrelease also shows 7.1-PRERELEASE?
> >
> > # sysctl kern.osrelease
> > kern.osrelease: 7.1-PRERELEASE
>
> Something that might apply: your cvsup file showed cvsup12 as the
> server.  cvsup12 stopped responding for me several months ago.  If your
> csup and build is automated so you don't see the timeouts, that would
> explain why you aren't getting updated.

Yep, looks like this is the problem. You can verify by 
inspecting /usr/src/sys/conf/newvers.sh. It should be:
# $FreeBSD: src/sys/conf/newvers.sh,v 1.72.2.10 2009/01/05 04:45:17 kensmith 
Exp $

TYPE="FreeBSD"
REVISION="7.1"
BRANCH="STABLE"

-- 
Mel

Problem with today's modular software: they start with the modules
    and never get to the software part.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200902250934.09429.fbsd.questions>