bug-cvs
[Top][All Lists]
Advanced

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

assertion failure with 1.11.1p1


From: jay
Subject: assertion failure with 1.11.1p1
Date: Wed, 8 Aug 2001 08:18:49 +0100 (BST)

>Submitter-Id:   net
>Originator:     James Youngman
>Organization:
net
>Confidential:  no
>Synopsis:      assertion failure in cvs export
>Severity:      serious
>Priority:      medium
>Category:      cvs
>Class:         sw-bug
>Release:       cvs-1.11.1p1
>Environment:
        Solaris 2.6 (compiled with GCC 2.95)
System: Solaris 2.5
Architecture: SPARC

>Description:

I installed 1.11.1p1 (as an upgrade from Halibut) yesterday on Solaris
2.6 (compiled with GCC).

Only config change is to use LockDir to move the locks into /var/tmp/mumble.

Mostly works, however a colleague did this (left hand column indicates
which version of CVS each step was done with) :-


1.10         cvs co -rmybranch module
             [...]
1.10         cvs commit 
1.11.1p1     cvs tag whatever
             cd $HOME
             mkdir tmp
             cd tmp
1.11.1p1     cvs export -rwhatever module



>How-To-Repeat:
        Do not yet know if this is reproducible.  
        If you just repeat the last step, you always get the assertion failure.
        The export command workd fine under cvs 1.10.
>Fix:
        Workaround is to use the cvs-1.10 binary.
        This is not a good workaround because of the use of LockDir, I think. 



reply via email to

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