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

2005-07-16 Thread 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 -aaliases...
 # 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






___
Savannah-help-public mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/savannah-hackers


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

2005-07-15 Thread Sylvain Beucler
I did post a reply but it was apparently lost.

I think you are trying to modify an anonymous working directory.

Try checking it out with your Savannah user.

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

-- 
Sylvain


On Fri, Jul 15, 2005 at 08:08:57PM +0200, Eric NOULARD wrote:
 Hi Savannah Admin,
 
 I did post an help message on savannah-help-public
 but did not had any answer.
 
 http://lists.gnu.org/archive/html/savannah-hackers/2005-07/msg00044.html
 
 Are you unavailable or did I miss something about the use
 of savannah-hackers ML?
 Last time I did use it I did have quick answer?
 
 I do still have my small problem:
 
 
 [EMAIL PROTECTED] tsp]$ cvs ci src/util/libbb/bb_core.h
 cvs [server aborted]: commit requires write access to the repository
 cvs commit: saving log message in /home/eric/tmp/cvsIUaFfP
 [EMAIL PROTECTED] tsp]$ date
 Fri Jul 15 20:02:01 CEST 2005
 [EMAIL PROTECTED] tsp]$
 
 
 Eric



___
Savannah-help-public mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/savannah-hackers