Re: [Savannah-hackers] savannah insanity

[loic]

Joel N. Weber II writes:
 > I tried actually running sf_cvs manually, and for whatever reason it
 > seemed to want to delete a bunch of users (3diff, tower, etc) who
 > shouldn't be deleted, and there was some other impressive brokenness.

        I'd be interested to have the output of sf_cvs. I never had
this kind of behaviour but the mere idea of this happening is
frightening.

 > It also seems very poor that it's apparently designed so that if you
 > don't pipe its output to sh, then those batch updates will just be
 > ignored and forever forgotten.  Or maybe it's just documented
 > confusingly.
        
        The documentation could be improved, that's true. Generating a
shell script is a great way to debug and fix mistakes. I could
advocate for this method during hours :-) For instance it's a true
guarantee that you can ask for "what are you going to do" without
doing it.

        Cheers,

P.S. Is this the documentation you read ?

Must be root to run this script. Must export CVS_RSH=ssh. You are advised to 
run it in /subversions/sourceforge/tmp, although it is not mandatory.

It is run from the crontab and the output is logged in /var/log/sf_cvs.log.

The sf_cvs script generates a shell script that will synchronize the system 
files with the state of the Savannah database (sourceforge).

This script only generates lines if something needs to be done. When the 
resulting script is executed, another run must not display any action, unless 
the database was modified in the meantime.

It performs the following tasks, in this order.


Add new projects
    /subversions/cvs/software/project and 
/subversions/cvs/gnuweb/software/project directories are created.
Update existing projects
    Fixes projects that do not have a /subversions/cvs/gnuweb/software/project 
directory or a directory with wrong permissions.
Add missing users
    Create users (in /etc/passwd) that are bound to at least a project in 
Savannah.
Remove users
    Remove users not bound to any project in Savannah If user belongs to groups 
not managed by Savannah, just redefine its group list.
Update existing users
    Modify the system files if they are not in sync with the Savannah database.
Update the groups of anoncvs
    The list of groups (projects) to which anoncvs belongs is restricted by the 
public/non public status of a project. The only exception is emacs that is a 
public project without anonymous cvs access. When the policy changes the sf_cvs 
script will have to be updated.
Update the CVS password file
    Update the /subversions/cvs/CVSROOT/passwd file to reflect the passwd and 
users bound to projects in Savannah.
Update xinetd.conf
Update the cvspserver/cvskserver with all possible pserver roots



-- 
Loic   Dachary         http://www.dachary.org/  address@hidden
24 av Secretan         http://www.senga.org/      address@hidden
75019    Paris         Tel: 33 1 42 45 09 16        address@hidden
        GPG Public Key: http://www.dachary.org/loic/gpg.txt