[Savannah-help-public] Re: [Savannah-help-private] not able to commit in branch: "commit" requires write access to the repository

[Sylvain Beucler]

Ok, done :)

-- 
Sylvain

On Sat, Jul 16, 2005 at 01:26:23AM +0200, Eric NOULARD wrote:
> On Sat, 2005-07-16 at 00:07 +0200, Sylvain Beucler wrote:
> > I did post a reply but it was apparently lost.
> > 
> > I think you are trying to modify an anonymous working directory.
> 
> You are right as usual :))
> 
> I really don't know how I end up with 2 checkout
> out of 5 done as anonymous :((
> 
> > 
> > Try checking it out with your Savannah user.
> 
> I just did this and it's ok now, commit in the branch work perfectly.
> > 
> > If not, give me the content of CVS/Root and CVS/Repository, as well as the 
> > output of the cvs command with the -t flag:
> > cvs -t commit....
> 
> 
> Sorry for this, I am preparing some concurrent work using
> different checkout and ... 
> 
> As I get you in person could
> you update our CVS/modules with the one attached to the mail.
> I know I can't do it myself since you did it for me last time.
> 
> I've just finished adding some top-level CVS module and
> wanting to update alias 'tsp_all' for getting all of them
> at once.
> 
> The diff is the following:
> Index: CVSROOT/modules
> ===================================================================
> RCS file: /cvsroot/tsp/CVSROOT/modules,v
> retrieving revision 1.3
> diff -r1.3 modules
> 29c29
> < tsp_all &tsp &jtsp &tsp_docs
> ---
> > tsp_all &tsp &tsp_docs &jtsp &perltsp &pytsp &tcltsp
> 
> Eric

> # Three different line formats are valid:
> #     key     -a    aliases...
> #     key [options] directory
> #     key [options] directory files...
> #
> # Where "options" are composed of:
> #     -i prog         Run "prog" on "cvs commit" from top-level of module.
> #     -o prog         Run "prog" on "cvs checkout" of module.
> #     -e prog         Run "prog" on "cvs export" of module.
> #     -t prog         Run "prog" on "cvs rtag" of module.
> #     -u prog         Run "prog" on "cvs update" of module.
> #     -d dir          Place module in directory "dir" instead of module name.
> #     -l              Top-level directory only -- do not recurse.
> #
> # NOTE:  If you change any of the "Run" options above, you'll have to
> # release and re-checkout any working directories of these modules.
> #
> # And "directory" is a path to a directory relative to $CVSROOT.
> #
> # The "-a" option specifies an alias.  An alias is interpreted as if
> # everything on the right of the "-a" had been typed on the command line.
> #
> # You can encode a module within a module by using the special '&'
> # character to interpose another module into the current module.  This
> # can be useful for creating a module that consists of many directories
> # spread out over the entire source repository.
> 
> ################## TSP all-in-one module ########################
> tsp_all &tsp &tsp_docs &jtsp &perltsp &pytsp &tcltsp