Re: Up-to-date check failed for 'module'

[David Berry]

Larry,

Please tell me what is wrong with the following
scenerio:


Note: cvso is a script I use to check out source
      from cvs. Program alnmo has revisions 201.4,
      201.5 and 201.6

cato:/users/721/berry/src/scripts% cvso -r201.4 alnmo
Do you want to place a lock on these files? (Y/N) or (y/n)
y
U esproc/alnmo/alnmo.c
RCS file: /cm/cvs/esproc/alnmo/alnmo.c,v
201.4 locked
done
U esproc/alnmo/alnmo.h
RCS file: /cm/cvs/esproc/alnmo/alnmo.h,v
201.4 locked
done
U esproc/alnmo/alnmo.nsd
RCS file: /cm/cvs/esproc/alnmo/alnmo.nsd,v
201.4 locked
done
U esproc/alnmo/makefile
RCS file: /cm/cvs/esproc/alnmo/makefile,v
201.4 locked
done
U esproc/alnmo/ChangeLog
RCS file: /cm/cvs/esproc/alnmo/ChangeLog,v
201.4 locked
done
cato:/users/721/berry/src/scripts% cd esproc/alnmo
cato:/users/721/berry/src/scripts/esproc/alnmo% cvs update -A
cvs update: Updating .
U ChangeLog
U alnmo.c
U alnmo.h
U alnmo.nsd
U makefile
cato:/users/721/berry/src/scripts/esproc/alnmo% cd ..

Note: cvsi is a script I use to check source into CVS.

cato:/users/721/berry/src/scripts/esproc% cvsi alnmo
RCSD = /cm/cvs/esproc/alnmo
SRCL =alnmo.c alnmo.h alnmo.nsd makefile ChangeLog
----- scanning CVS and working directories -----
#1 $FILE = alnmo.c
#1 $FILE = alnmo.h
#1 $FILE = alnmo.nsd
#1 $FILE = makefile
#1 $FILE = ChangeLog
                =============================================
                  derived <rev> to be used is "201.5"
                =============================================
=====================================================================
 Please enter revision comments. Try to be brief, but include enough
 information to adequately explain the reason for a new revision.
 End comments with a period ('.') as the first character in a line.
=====================================================================
> testing cvs update
> .
cvs commit: Up-to-date check failed for `alnmo.c'
cvs [commit aborted]: correct above errors first!
cvs commit: Up-to-date check failed for `alnmo.h'
cvs [commit aborted]: correct above errors first!
cvs commit: Up-to-date check failed for `alnmo.nsd'
cvs [commit aborted]: correct above errors first!
cvs commit: Up-to-date check failed for `makefile'
cvs [commit aborted]: correct above errors first!
cvs commit: Up-to-date check failed for `ChangeLog'
cvs [commit aborted]: correct above errors first!
  ---------------------------------------------------------
    Checkin of "alnmo" source set was successful.
  ---------------------------------------------------------
cato:/users/721/berry/src/scripts/esproc% 

It appears I cannot check out old code and check it 
in over the latest code, even if I update it.

Rgds,
David Berry

Larry Jones wrote:
> 
> David Berry writes:
> >
> > I have versions 201.4, 201.5 and 201.6 .
> > There is NO difference in the code in
> > any of these versions, except for the
> > revision string $Id:$
> 
> Note that a difference is a difference; the fact that it's in the
> revision string doesn't really matter.
> 
> > When I check out 201.4 and try to check
> > it back in on top of 201.6, I get the
> > following:
> > cvs commit: Up-to-date check failed for `alnmo.c'
> > cvs [commit aborted]: correct above errors first!
> 
> What this is telling you is that there is a more recent revision of that
> file in the repository.  If you were to check in your current copy of
> the file, you would lose the changes from the more recent revision(s) in
> the repository, so CVS won't allow it.  You need to use ``cvs update''
> (perhaps with the -A option) to update your working copy to the most
> recent revision in the repository before CVS will allow you to check it
> in.
> 
> -Larry Jones
> 
> Why is it you always rip your pants on the day everyone has to
> demonstrate a math problem at the chalkboard? -- Calvin