[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Issues with raising the 'floor' in CVS

From: Teala Spitzbarth
Subject: Issues with raising the 'floor' in CVS
Date: Wed, 14 Feb 2001 12:41:33 -0800

I am attempting to implement a 'floor' model in our cvs repository
i.e. we would like to have our build levels, in addition to tags, we
demarcated by revisions, i.e. anything above revsion 2.0 is a change
going into our build level 2 etc.

I am running cvs 1.10.7

I have two issues I am hoping for assistence with:

1) when running the 'cvs ci -r 2.0' command I think I hit a bug (or
corruption in our tree?) where the checkin command wouldn't recurse
the whole tree, (the behavior was exactly the same with explictly adding
'cvs ci -R -f -r 2.0')

After traversing down 4 levels in the first subdir, and correctly ci'ing
about 20 files, the checkin says it aborts with this message:

        cvs commit: in directory 3rdparty/apache/etc/rc.d/init.d:
        cvs [commit aborted]: there is no version here; do 'cvs checkout' first

But there is a proper version of the existing file in this directory,  & as
far as I can
tell the file is not corrupted, nor is it corrupted in the repository.

I wrote a  script to recurse into each directory of my working copy and run
the cvs ci -r 2.0,  and this worked, all files were correctly updated to the

Are  there known problems with doing a checkin to update a whole tree/module
to a new revision?   Or does that 'ci aborted' message above indicate some
kind of corruption that I can clean up?

2) So now I know that I have successfully raised the floor on all existing
but new files will still go in as 1.1
Is the best way to enforce the raised revision on new files to
write a script to be run by commitinfo ?

Thanks much,
Teala Spitzbarth

reply via email to

[Prev in Thread] Current Thread [Next in Thread]