[cvsnt] Not complete Tags
alberto.difede at gmail.com
Tue Aug 21 17:53:13 BST 2007
Hello and sorry to answer so late,
> If a file cannot be tagged I do not think CVSNT returns an error. Eg:
> if a tag already exists with the same name then that is not considered
> an error - the file is "simply" skipped. Quite possibly all errors
> (other than things like communication failures) are treated that same
We're talking about "add" operations, thus forcing is not necessary and
all files should be tagged.
> The best thing to do would be to enable auditing,
it is enabled and records correctly: tags are recorded for the files
correctly tagged and not recorded for those who are not (although they
and also redirect the
> stdout and stderr of the tag process to files with unique names.
developer following the procedure is reporting me that stderr redirect
caused a lot of troubles with the 2151 build, anyway, he will try with
> problem occurs again now you have updated the client to 2382, look at
> the SessionLog, TagLog and HistoryLog and also the stderr/stdout of the
> tag operation and see if that sheds any light on what is happening.
files not tagged, although commanded to be tagged, are not recorded in
the auditing database.
> I am not aware of any limit on the number of tags or on any bugs that
> would cause a tag not to be applied and this is the first time I can
> remember having seen such a report.
> Is there anything "special" about the files that have not received that
> tag (eg: is it on a magic branch, or is it -kx) and is it always the
> same file(s) that are not tagged?
nothing special, and the behavior is quite random. freaky, ain't it?
Anyway, it seems the issue is only with the tags creation, because
moving with the "force" attribute dows tag everything correctly.
We're gonna investigate further in the coming days and will report back.
In the meantime it would be great if you could help me further with
hints about how to spot better the cause.
Thanks in advance and Regards,
More information about the cvsnt