[cvsnt] Re: Lost keyword expansion settingaftermultiplemergeswith added files

[Bo Berglund]

I had more than one repositories and I grabbed the tag from the val-tags
file in our main repository but I tested on a different repository that
did not have this tag in val-tags...

Once I fixed this the keyword is lost also for me..

Bo


-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Bo Berglund
Sent: den 6 april 2006 10:50
To: Oliver Koltermann; cvsnt at cvsnt.org
Subject: RE: [cvsnt] Re: Lost keyword expansion
settingaftermultiplemergeswith added files

The file name is CVSROOT/val-tags and it contains among others this
line:
BRANCH_AES y

That is where I went to retrieve the tag value to use.
We added this not so long ago.

And I have now confirmed the versions of CVSNT both client and server
are build 2151 


Best regards,

Bo Berglund


-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Oliver Koltermann
Sent: den 6 april 2006 09:15
To: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Re: Lost keyword expansion setting
aftermultiplemergeswith added files

Hello Bo,

thank you, for your patience and support!

Am Mittwoch, den 05.04.2006, 18:25 +0200 schrieb Bo Berglund:
> C:\3RProj\Bosse\Test\CVStests>cvs update -r BRANCH_AES -jHEAD cvstest
> cvs [server aborted]: no such tag BRANCH_AES

> As you can see the file is still binary for me...
> And the error persists concerning the tag.
> 
> The tag BRANCH_AES *does* exist in the *repository* in a completely
> different location of course.

Hmmm, this is strange. Okay, you don't have the problem with the binary
sticky option because the merge causing the option to be lost never runs
due to the unknown tag issue.

I remember that the tags are checked against a file CVSROOT/valtags in
this situation. And I think I have seen situations with old versions of
CVSNT, where the valtags file wasn't updated. If you used this
tag/branch name inside this repository before, it should be in the
valtags file. If not, and you have used it with a recent version of
CVSNT, this may be another issue?

Best regards,
O. Koltermann
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt