[Top][All Lists]

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

Re: Update from head gets an old revision

From: Todd Denniston
Subject: Re: Update from head gets an old revision
Date: Thu, 08 Sep 2005 09:18:24 -0500

GraemeF wrote:
> Hi,
> We've been getting on quite nicely with CVS (CVSNT & TortoiseCVS on
> Windows) for the last few months, but yesterday we ran into the
> following problem. Our commits seem to be working fine, but any updates
> from the HEAD are fetching an old revision. For example:
> >cvs log Aston.Outputs.csproj
> [snip!]
> keyword substitution: t
> total revisions: 25;    selected revisions: 25
> [snip!]
> >cvs status Aston.Outputs.csproj
> ===================================================================
> File: Aston.Output.csproj       Status: Up-to-date
>    Working revision:    1.24
>    Repository revision: 1.24
> /labcvs/Helix/Aston.Output/Aston.Output.csproj,v
>    Expansion option:    t
>    Commit Identifier:   da44316c48910b1
>    Sticky Tag:          (none)
>    Sticky Date:         (none)
>    Sticky Options:      -kt
>    Merge From:          (none)
> This is on a clean checkout of the module. As you can see, the latest
> revision is 1.25, but the status says 1.24, and any updates or
> checkouts (without specifying revision 1.25) get revision 1.24.
> Any ideas? We're really stumped. My manager never wanted us to leave
> SourceSafe and doesn't like CVS, so I'd really appreciate a response!
> :)
> Cheers,
> G.

you may be using CVSNT for all your work and may need to ask on one of their
mailing lists

however from a pure CVS perspective it looks like you have some sticky
option that is not one I recognize.

perhaps the following is relevant:

maybe someone tried running `cvs admin -kt Aston.Outputs.csproj` and it got

Is this happening for all users, one user, fresh checkout (i.e. start in an
empty directory, like /tmp/, not a checkout on top of an existing
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter

reply via email to

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