[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Strange update behavior
From: |
Mark D. Baushke |
Subject: |
Re: Strange update behavior |
Date: |
Wed, 24 Aug 2005 13:02:39 -0700 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Christian Schmolzi <address@hidden> writes:
> I have noticed a strange behavior that occured exactly two times in the
> last few weeks. I tried to update my sandbox (Sun Solaris, CVS client 1.12)
> from a branch to HEAD with "cvs -PAd". Strangely, one file, that was added
I assume you mean 'cvs update -PAd' as the command?
> since that branch was not retrieved from the repository (CVS Server 1.12 on
> Linux, pserver). Since the cvs server simply ignored that file, we did not
> notice at first that the file was missing.
>
> Several update tries with differnt options did not succeed. The only way to
> get the file from the repository was by telling cvs explicitely which file
> to update ("cvs update -P file.txt"). Another colleague of me reported this
> behavoir happened with his windows client (WinCvs).
>
> Does anybody know under which circumstances something like this can happen.
> Since that I have not been able to reproduce this behavior but we are a
> little concerned about the reliability of a cvs update before we deliver
> our software to the customer.
What does a 'cvs status file.txt' tell you (before and after you do the
update)? Does another 'cvs update -PAd' cause file.txt to disappear?
You don't happen to have both a file.txt directory and a file.txt,v file
in your repository do you? (Although I would have expected you to have
run across a 'file.txt already exists but is not a directory' kind of error
message in that case).
-- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFDDNJeCg7APGsDnFERAqzTAJ9y0pYMHM1omr+bmib38WL+EtmqZQCgyTG/
C/Iru3pm/Q+76efeEyXUONI=
=aTAQ
-----END PGP SIGNATURE-----