Re: Update from head gets an old revision

[Jim Hyslop]

GraemeF wrote:
> 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.
Hmmm.... that's strange. Can you try using CVSNT directly, or with the 
stock CVS client?

> > 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)

OK, that eliminates the obvious problem of a sticky tag.

> 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.

So, if you explicitly request 1.25 you can get it, is that right?

> Any ideas? We're really stumped. 
BTW, this list doesn't specialize in cvsnt or wincvs, so you may get 
better answers from CVSNT (www.cvsnt.org) or from www.wincvs.org.

> My manager never wanted us to leave
> SourceSafe and doesn't like CVS, so I'd really appreciate a response!
> :)

If this doesn't convince your manager that VSS is the worst thing to 
happen to version management, then nothing will:

http://www.highprogrammer.com/alan/windev/sourcesafe.html

One key statement: "A single misbehaving computer can destroy the 
database." Niiice.

--
Jim