CVS Feature Request -- WAS Re: [A-a-p-user] problems with cvs in a-a-p

[Matthew W. O. <mat...@we...>]

-- Bram Moolenaar <Br...@mo...> wrote
(on Wednesday, 20 November 2002, 10:48 AM +0100):
> 
> Matthew Weier OPhinney wrote:
> 
> > I'm trying to add cvs functionality to my a-a-p recipe, and I've
> > followed the directions in both the tutorial and the manual. 
<snip>
> > >From the directory in which the recipe exists, I can run a cvs update
> > and cvs commit without error. However, when I run "aap revise", I get
> > notices like the following:
> >     cvs server: failed to create lock directory for `/repository/pws'
> >     (/repository/pws/#cvs.lock): No such file or directory
> >     cvs server: failed to obtain dir lock in repository `/repository/pws'
> >     cvs [server aborted]: read lock failed - giving up
> > 
> > (where pws is the name of the project). 
> > 
> > What's happening here? How do I get this to work correctly?
> 
> I have no idea.  It actually looks like there is something wrong with
> the repository.  But it could be caused by the CVS commands that A-A-P
> invokes.
> 
> Please look at the CVS commands that aap invokes.  If they look OK,
> there must be something wrong with the repository.  You might also want
> to try doing it by hand to make sure there is nothing funny going on.
So, I found when after logging in to my cvs server, I had no problems.
However, when using the -d:pserver:user@server:/respository notation, I
did. 

It took me a while to run it down, but eventually I did -- I'm on debian
and use the chroot jail pserver installed with the cvsd package. I just
installed it, specifically for using with A-A-P (prior to this, I'd
simply checked in to a local repository -- no pserver needed). In the
process of configuring and reconfiguring it, I didn't realize that the
chroot jail was making mapping my user to the cvsd user -- and the cvsd
user had no permissions to make changes in the repository! Once I got
that fixed, it all worked like a charm.

So, now I need to make this a feature request. While I like the ability
to update, add, and remove from CVS with one easy command from aap, I'd
still like to be able to use custom commit messages -- any chance that
this could become an option?

-- 
Matthew Weier O'Phinney
ma...@we...