DragonFly bugs List (threaded) for 2004-10
Re: Dragonfly_Stable and newvers.sh
Erik P. Skaalerud wrote:
Matthew Dillon wrote:
:I just rebuilt to latest Dragonfly_Stable tag, and I got a funny
:[erik@dragon:~]$ uname -sr
:Is it supposed to be like this?
Hmm. The CVSROOT/config file in the cvs repository (if you are
pulling down the repository) should have as the last line:
(verses just iDragonFly).
And the tag="\$Name: $" line in /usr/src/sys/conf/newvers.sh
should be expanded out with the tag name, empty if HEAD. If the
is "\$Name$" then it hasn't been expanded at all and there is a
If your repository has the correct config line then try removing
newvers.sh and cvs update'ing it again. If your repository does not
have the correct config line then the question is why doesn't it? If
you are pulling down the checked out source with cvsup then maybe
cvsup is getting confused and not expanding the $Name$.
[root@dragon:/usr/mirror/cvsupd/prefixes/DragonFly.cvs/CVSROOT]$ cat config
# $DragonFly: config,v 1.3 2004/10/22 23:21:00 dillon Exp $
# Set this to "no" if pserver shouldn't check system users/passwords
# Put CVS lock files in this directory rather than directly in the
# Set `TopLevelAdmin' to `yes' to create a CVS directory at the top
# level of the new working directory when using the `cvs checkout'
# Set `LogHistory' to `all' or `TOFEWGCMAR' to log all transactions to the
# history file, or a subset as needed (ie `TMAR' logs all write operations)
# Set `RereadLogAfterVerify' to `always' (the default) to allow the
# script to change the log message. Set it to `stat' to force CVS to
verify# that the file has changed before reading it (this can take up to
# second per directory being committed, so it is not recommended for large
# repositories. Set it to `never' (the previous CVS behavior) to prevent
# verifymsg scripts from changing the log message.
# Add the "DragonFly" keyword and restrict keyword expansion
# The cvs guys did not add support for renaming other keywords, silly them!
# So we have to enable Name in order for newvers.sh to be able to pick out
# the tag being built
I cant see any errors.. Can you?
Matt, several people have reported the same behaviour. Is someone going
to take a look?