Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 Jan 2006 01:36:16 +0800
From:      "Jose Liang" <jliang@so-net.net.tw>
To:        "Giorgos Keramidas" <keramida@ceid.upatras.gr>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Problem with cvs commit failed in  cvs-freebsd setup
Message-ID:  <000a01c6160c$5c2b5480$2e02a8c0@josematrix>
References:  <000601c61351$930ab8f0$2e02a8c0@josematrix> <003401c6133e$427b8850$2e02a8c0@josematrix> <20060107045755.GA4344@flame.pc> <000f01c61350$e706c5d0$2e02a8c0@josematrix> <20060107173741.GB1053@flame.pc> <005601c613b7$993d1d60$2e02a8c0@josematrix> <20060107212659.GA2175@flame.pc>

next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for your patience and explaining first!

I've created a group file inside the chroot directory, it looks just like:

wheel:*:0:root,cvs
nobody:*:65534:
cvs:*:1002:jose

but it is still unable to work.
And I exec ./commitcheck in local directory,
it complains:

Can't locate CVSROOT/cfg.pm in @INC (@INC contains:
:pserver:jose@localhost:/cvsroot /usr/local/lib/perl5/5.8.7/BSDPAN
/usr/local/lib/perl5/site_perl/5.8.7/mach
/usr/local/lib/perl5/site_perl/5.8.7 /usr/local/lib/perl5/site_perl
/usr/local/lib/perl5/5.8.7/mach /usr/local/lib/perl5/5.8.7 .) at
./commitcheck line 13.
BEGIN failed--compilation aborted at ./commitcheck line 13.

So should I creat above files to the chroot environment manually?
Because I'm afraid of I don't know exactly how to dig a bit deeper into Perl
stuff. :(

Maybe I should quit, but I just wanna use the feature of expanding a tag(cvs
keyword) like 'FreeBSD'.
When I modify CVSROOT/config to add my setting of KeywordExpand, cvs always
failed.
How could I get a solution to solve this?

Thanks a lot!

----- Original Message ----- 
From: "Giorgos Keramidas" <keramida@ceid.upatras.gr>
To: "Jose Liang" <jliang@so-net.net.tw>
Cc: <freebsd-questions@freebsd.org>
Sent: Sunday, January 08, 2006 5:26 AM
Subject: Re: Problem with cvs commit failed in cvs-freebsd setup


>
> Try creating a minimal /etc/group file inside the chroot environment,
> and see if this fixes the problem.  If not, you may have to dig a bit
> deeper into Perl stuff and add debugging code around the execution of
> CVSROOT/commitcheck, i.e. by modifying CVSROOT/commitinfo to call a
> script of your own, which prints more information about the process that
> tries to invoke CVSROOT/commitcheck.
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000a01c6160c$5c2b5480$2e02a8c0>