[cvsnt] Re: Build 1966 does not preserve sticky tag on update...

[Glen Starrett]

Bo Berglund wrote:
> Whilst checking the binary file issue I did the following:
> 
> - Added a file as binary and committed
> - Cvs removed the file and committed
> - Cvs added the file again and committed
> - Updated the file to sticky tag rev 1.1
> 
> I updated the file with sticky tag 1.1 to retrieve the first revision
> in order to check it against the original file. Same length and no
> differences.
> Then I made a simple cvs update in the sandbox in order to get other
> files in working order.
> SURPRISE!
> The bug that was there in some intermediate builds prior to 2.5.01
> release is there again!
> The update (*without* specifying reset of sticky tags) *does* in fact
> reset the sticky tag and retrieves the HEAD revision, which is
> definitely *not* what we want...

I just checked against 1927 and it's a problem there too, but not 
exactly how you are describing it.  Please confirm if this is the same 
for you:

cvs up -CAdP
cvs up -r 1.2 test2.c
cvs status test2.c

File: test2.c           Status: Needs Patch

    Working revision:    1.2
    Repository revision: 1.19    /var/cvs/general/test/test2.c,v
    Expansion option:    kv
    Commit Identifier:   776642851ec7a876
    Sticky Tag:          (none)
    Sticky Date:         (none)
    Sticky Options:      -kkv
    Merge From:          (none)


==> Note that "Sticky Tag" is NOT set, and Status is "Needs Patch".

cvs up
==> Now, cvsnt updates test2.c to HEAD again.


-- 
Glen Starrett