[cvsnt] Export fails

[David Oram]

Thanks Arthur for that suggestion.  I have run with debug as you have
suggested:

cvs -ttt export -r test Frst

...<lots of debug> ...
08:02:35: S -> map_repository(C:/CVSNT/Solutions/Frst/Bin/Install)
08:02:35: S -> lookup_module2(Frst/Bin/Install,42)
08:02:35: S -> verify_access
C:/CVSNT/Solutions/Frst/Bin/Install,Frst/Bin/Install,(null)
08:02:35: S ->
verify_perm(C:/CVSNT/Solutions/Frst/Bin/Install,(null),read,(null),(null
))
08:02:35: S -> verify_owner(C:/CVSNT/Solutions/Frst/Bin/Install)
08:02:35: S ->
cache_directory_permissions(C:/CVSNT/Solutions/Frst/Bin/Install)
08:02:35: S -> fileattr_read(C:/CVSNT/Solutions/Frst/Bin/Install)
08:02:35: S -> ACL lookup on directory
C:/CVSNT/Solutions/Frst/Bin/Install
08:02:35: S -> verify_acl(read,HEAD,(null))
08:02:35: S -> user_state = 0, group_state = 0
08:02:35: S -> no match at this level
08:02:35: S -> ACL lookup on directory C:/CVSNT/Solutions/Frst/Bin
08:02:35: S -> verify_acl(read,HEAD,(null))
08:02:35: S -> user_state = 0, group_state = 0
08:02:35: S -> no match at this level
08:02:35: S -> ACL lookup on directory C:/CVSNT/Solutions/Frst
08:02:35: S -> verify_acl(read,HEAD,(null))
08:02:35: S -> user_state = 0, group_state = 0
08:02:35: S -> no match at this level
08:02:35: S -> ACL lookup on directory C:/CVSNT/Solutions
08:02:35: S -> verify_acl(read,HEAD,(null))
08:02:35: S -> user_state = 0, group_state = 0
08:02:35: S -> no match at this level
08:02:35: S -> Create_Admin (Install, Frst/Bin/Install,
C:/CVSNT/Solutions/Frst/Bin/Install, test, , 0, 0)
08:02:35: S -> run template proc
08:02:35: S -> run_trigger()
08:02:35: S -> Call pre-loaded 'info.dll'
08:02:35: S -> template_proc(Frst/Bin/Install)
08:02:35: S -> default_trigger:
parse_rcsinfo(CVSROOT/rcsinfo,Frst/Bin/Install)
08:02:35: S -> Regexp match: ALL - Frst/Bin/Install
08:02:35: S -> Match found!
08:02:58:   -> call_in_directory
/Solutions/Frst/Bin/Install/,Frst/Bin/Install/
cvs [export aborted]: cannot open <CVS/Template file> for writing: No
such file or directory


My rcsinfo file:
# The "rcsinfo" file is used to control templates with which the editor
# is invoked on commit and import.
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being made to, relative to
the
# $CVSROOT.  For the first match that is found, then the remainder of
the
# line is the name of the file that contains the template.
#
# If the repository name does not match any of the regular expressions
in this
# file, the "DEFAULT" line is used, if it is specified.


# Scmbug_STANZA_START
#
#
# Load the Scmbug integration glue template
ALL	/CVSNT/Solutions/CVSROOT/etc/scmbug/log_template
#
#
# Scmbug_STANZA_STOP

You will note that it does not refer to the log_template script relative
to $CVSROOT because that variable wasn't being set correctly, so I have
used a fully qualified path name.

Cheers,
Dave

-----Original Message-----
From: Arthur Barrett [mailto:arthur.barrett at march-hare.com] 
Sent: Wednesday, 7 May 2008 7:34 p.m.
To: David Oram; cvsnt at cvsnt.org
Subject: RE: [cvsnt] Export fails


David,

> I've recently integrated ScmBug with CVSNT (CVSNT 2.5.03 Build 2382 on

> XP Sp2) which installs a bunch of scripts that run at CVS Trigger 
> points.

I recommend: http://www.march-hare.com/cvsnt/features/bugzilla/en.asp

The next version (due for GM in the next few days) supports Mantis 1.1.1
and maybe another tracker as well.

> However cvs export now fails as follows:
> 
> cvs export -r test Frst
> cvs export: Updating Frst
> cvs export: Updating Frst/Bin
> cvs export: Updating Frst/Bin/Build
> cvs export: Updating Frst/Bin/CruiseControl
> cvs [export aborted]: cannot open <CVS/Template file> for writing: No 
> such file or directory
> 
> I found that this bug was fixed in cvs 1.11.2 (see 
> http://www.mail-archive.com/bug-cvs@gnu.org/msg02963.html ), and 
> wondered if this fix has been propagated to CVSNT.
> 

CVSNT 2.5.03 is MUCH newer than 1.11.2 and I haven't seen anyone else
report an export bug, so I suspect they are different (but similar
result).

You'll need to enable server side tracing in the advanced options on the
server control panel and then do your export with -ttt then look at the
trace for the relavent bits and post JUST THOSE BITS to the newsgroup
(anything too big and the newsgroup server will bounce your post).

cvs -ttt export -r test Frst

Regards,


Arthur