Re: Exp state on top of dead

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

CARTER-HITCHIN, David, GBM <address@hidden> writes:

> We've got a file which is 'dead' at revision
> 1.11 but 'Exp' at 1.12 and 1.13. The file is now
> in the Attic in the repository.

This sounds like a bug. The Attic directory is
intended as an optimization for the main trunk. A
file with live versions on the main trunk should
not be in the Attic directory and should have been
resurrected when 1.12 was added.

If you are using client/server CVS, then what revision?
If you are using local CVS and an NFS location for your
repository, you probably wish to avoid this if possible.

In any case, you will want to run the
contrib/validate_repo.pl script to see if there
are any other problems with your repository.

> If I checkout HEAD, I don't get this file, so
> it's 'dead' for all intents and purposes.
> However, one of our chaps somehow checked this
> file out (working with HEAD), so I suppose the
> solution for him is to simply remove it from his
> 'CVS/Entries' and remove his copy of it.

I suppose a time-based "cvs checkout -D'now'"
followed by a 'cvs update -A' might have found the
live 1.12 revision. Or, if the same tree that
created the 1.12 revision was also used to create
1.13, that could do it.

To be honest, I have only ever seen such odd
behaviors with very old cvs clients and NFS being
used to access the repository store.

> Begs the question though, how did 1.12 and 1.13
> get there? Is it a problem? If so what's the
> solution?

It is a problem. It needs to be fixed. For this
particular file, manually move it from the Attic
to the normal directory.

Consider upgrading your cvs server if it is not
the latest STABLE release.

Consider avoiding NFS if that is how you are
accessing the repository storage.

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (FreeBSD)

iD8DBQFE7baMCg7APGsDnFERAgZoAKCfFBNSGUtQAmnbdmzp0AHbNjrx9wCeNLub
aQ91LEuYceoUDjBr6vJ+iAk=
=AutE
-----END PGP SIGNATURE-----