bug-cvs
[Top][All Lists]
Advanced

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

Re: Case conflicts between Attic and main-line code in CVS 1.10.6


From: Mark . Hewitt
Subject: Re: Case conflicts between Attic and main-line code in CVS 1.10.6
Date: Mon, 2 Jun 2003 16:26:20 +0100


Derek,


OK - that was pretty easy, so here is how it goes:

On a UNIX system where case is significant:

        cvs co testmodule
        cd testmodule
        echo TestFile > testfile
        cvs add testfile
        cvs commit -m Blah testfile
        mv testfile TestFile
        cvs add TestFile
        cvs rm testfile
        cvs commit -m MoreBlah testfile TestFile

On a Windows system via pserver:

        cvs co testmodule

Back on UNIX:

        cd ..
        cvs tag -b NewBranch testmodule

Back on Windows:
       
        cvs update -r NewBranch testmodule

                cvs server: Updating testmodule
                cvs update: move away testmodule/testfile; it is in the way
                C testmodule/testfile

If at this stage I change the UNIX cvs command implementing the pserver from 1.11.6 back to 1.11.5, and trry the update again on Windows, I get:

        cvs update -r NewBranch testmodule

                cvs server: Updating testmodule

and no errors.

Is this sufficient for you?

#!/mjh



Derek Robert Price <address@hidden>

02/06/2003 15:16

       
        To:        address@hidden
        cc:        address@hidden
        Subject:        Re: Case conflicts between Attic and main-line code in CVS 1.10.6



address@hidden wrote:

>
> Since upgrading to CVS 1.10.6 (pserver, Solaris 9), we have a problem
> whereby if we have a filename in the Attic
> that differs only by case from one in the main-line code, Windows
> clients refuse to checkout the branch with a:
>
>         cvs update: move away
> Category_Review/Client/tis_included_app/winhelpkey.orc; it is in the way
>         C Category_Review/Client/tis_included_app/winhelpkey.orc
>
> Regressing to 1.10.5 solves this problem, and this is what we have had
> to do.
>
> Please tell me if there is more information required or a better way
> to report issues of this kind - sorry the 'cvsbug'
> script does not work for me for a variety of reasons (no internet
> access from repository, including mail, it also
> complaining 'mktemp: not found.').


Could you provide us with a minimal number of steps to recreate this
problem?  e.g. `touch foo; cvs ci foo; cvs tag -b br; cvs up -rbr; ...'.

Derek

--
               *8^)

Email: address@hidden

Get CVS support at <http://ximbiot.com>!
--
I will not sleep through my education.
I will not sleep through my education.
I will not sleep through my education...

         - Bart Simpson on chalkboard, _The Simpsons_






reply via email to

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