info-cvs
[Top][All Lists]
Advanced

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

RE: Assert error checking out tagged files with -p option


From: Peter Connolly
Subject: RE: Assert error checking out tagged files with -p option
Date: Wed, 16 Jun 2004 23:18:14 -0700

I think that the problem is that the 'val-tags' admin file is being checked
for an entry and new tags do not have an entry created in that file until a
checkout or update (without the -p option) has been performed.  Here is one
bug in the CVS queue related this problem:

"checkout (or update) with -p fails because val-tags doesn't have new tag
yet"  
https://ccvs.cvshome.org/issues/show_bug.cgi?id=186

And here is a related one (I think):

"`cvs co -rTAG -f' fails if TAG isn't in val-tags"
https://ccvs.cvshome.org/issues/show_bug.cgi?id=31

In the meantime, the workaround is to checkout with that tag before using
the -p option.


> -----Original Message-----
> From: address@hidden [mailto:info-cvs-
> address@hidden On Behalf Of Abhinandan Jain
> Sent: Wednesday, June 16, 2004 6:37 PM
> To: address@hidden
> Subject: Assert error checking out tagged files with -p option
> 
> I am using cvs 1.11.17 and am getting assert errors when using the "-pr"
> tagged checkout option for a freshly tagged file. That is, if I
> 
>  1) tag a file A with tag B
>  2) right away checkout the file using "-pr B", I get an assert error of
> the form
> 
>     Assertion failed: repository != NULL, file ../../src/recurse.c, line
> 641
>     cvs [checkout aborted]: received abort signal
> 
>  3) If however I checkout the file without the -p option, i.e. using
>     simply  "-r B", things work, and strangely enough, after this the
>     "-pr B" option also starts working.
> 
> Unforutnately, if I now use a new tag "C", I get exactly the same
> problem going from step 1-3 with this new tag. So it appears that this
> version of CVS requires at least one checkout to the file system using a
> new tag before the tag can be used with the "-p" option.
> 
> This beharior is causing quite a few problems in our environment.
> 
> I have included a short test case below which reproduces the problem:
> 
>     # create a new repository
>     cvs -d /home/jain/tempRepo init
> 
>     # import a single file "tmpfile" into the repository
>     mkdir tmpdir
>     touch tmpdir/tmpfile
>     cd tmpdir
>     cvs -d /home/jain/tempRepo import -m "" tmpmod ddd ggg
> 
>     # checkout "tmpfile" and tag it with the "tmptag" tag
>     cvs -d /home/jain/tempRepo co tmpmod
>     cvs -d /home/jain/tempRepo tag tmptag tmpmod/tmpfile
> 
>     # try to checkout tmpfile with the -p -r tmptag options
>     cvs -d /home/jain/tempRepo co -P -p -r tmptag tmpmod/tmpfile
> 
> This results in the error message:
> 
>   Assertion failed: repository != NULL, file ../../src/recurse.c, line 641
>   cvs [checkout aborted]: received abort signal
> 
>     # try to checkout tmpfile with the "-r tmptag" option (no -p option)
>     cvs -d /home/jain/tempRepo co -P -r tmptag tmpmod/tmpfile
> 
> WORKS! Checks out tmpfile to the file system.
> 
>     # try the -p -r tmptag option again
>     cvs -d /home/jain/tempRepo co -P -p -r tmptag tmpmod/tmpfile
> 
> WORKS!! No more problems using -pr option with the tmptag tag.
> 
> Thanks in advance for any help.
> 
> Abhi
> 
> 
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/info-cvs






reply via email to

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