RE: [gui-dev] CVS lockup in the gui module for its themes folder -badaccess rights

Hi Michael,

Thanks very much for the information on fixing up CVS.  Our situation is
somewhat more unique in that we want to provide different access rights for
different modules.  Philippe Verdy, for instance, has privileges to write to
the 'lib' module, as he provides excellent contributions and maintenance for
internationalizing LimeWire.  Roger Kapsi also has privileges to the 'daap'
module, which is more or less his code that we're providing a public CVS
repository for (and is incorporated in to LimeWire).  These and all the
other modules (core, gui, tests, etc...) are writable by us LimeWire folk.
To do this, we have special groups ('cvs-lib' and 'cvs-daap' that those
modules are owned by (and those users belong to), whereas all the others
ones belong to 'cvs'.  Will your scheme still work, providing we set the
sticky bits appropriately in each respective module?  It seems now that the
directories are created with the uid of the cvs user that creates them.

Thanks,
 Sam

> -----Original Message-----
> From: [email protected] [mailto:gui-dev-
> [email protected]] On Behalf Of Michael D. Hirsch
> Sent: Friday, November 26, 2004 10:19 PM
> To: [email protected]
> Subject: Re: [gui-dev] CVS lockup in the gui module for its themes folder
> -badaccess rights
> 
> On Friday 26 November 2004 02:31 pm, Sam Berlin wrote:
> > Fixed now -- I believe it's a problem with the way CVS creates new
> > directories.
> 
> Sounds like you may have the CVS directories misconfigured.  Everyone
> with write permission should be in a group and that group should own all
> the files.  The way to do this is to create the top dir with the right
> group ownership and 2775 permissions.
> 
> If you don't have this, first change the ownership:
> 	chgroup -R groupname topdirname
> Now, change the guid bit set on the directories.  Assuming that you are
> using a unix server for CVS, the guid bit of the CVS directories should
> be set.  Use "chmod g+s directory" for a single directory.  A quick
> script or find invocation will be needed to set it in every directory.
> 
> The point of the guid bit is that it means any file or dir created in the
> guid directory will be owned by the same group, so this problem won't
> reoccur.
> 
> Of course, I could be reading a lot or hooey into your one line account
> and be totally off base, here.  If so, then please ignore me.  :-)
> 
> Michael
> 
> > Thanks,
> >  Sam
> >
> > > -----Original Message-----
> > > From: [email protected] [mailto:gui-dev-
> > > [email protected]] On Behalf Of Philippe Verdy
> > > Sent: Friday, November 26, 2004 2:23 PM
> > > To: [email protected]
> > > Subject: [gui-dev] CVS lockup in the gui module for its themes
> > > folder - badaccess rights
> > >
> > > I can't update the GUI module completely, because of strange bad
> > > access rights for a lock folder used in CVS:
> > >
> > > cvs server: Updating com/limegroup/gnutella/gui/themes
> > > cvs server: failed to create lock directory for
> > > `/cvs/gui/com/limegroup/gnutella/gui/themes'
> > > (/usr/local/tigris/data/helm/cvs/lock/gui/com/limegroup/gnutella/gui
> > >/theme s/#cvs.lock):
> > > Permission denied
> > > cvs server: failed to obtain dir lock in repository
> > > `/cvs/gui/com/limegroup/gnutella/gui/themes'
> > > cvs [server aborted]: read lock failed - giving up
> > >
> > > Apparently, the .../cvs/lock/... directory was created by the wrong
> > > user, and denies access to users in the group normally granted
> > > update accesses to
> > > the GUI module.
> > >
> > > (note that the user "guest" is part of that group which should be
> > > able to get locks to perform updates, even if it is not granted
> > > additions/deletions/commit)
> > >
> > > Because of this lock, that occurs only for that subfolder, the
> > > following folders after "/gui/themes" are not updated, and must be
> > > updated separately... This is new, because in the past even "guest"
> > > could update its
> > > sources...
> > >
> > > Only LimeWire admins can correct this by checking the Unix folder
> > > ownerships
> > > and access rights in the cvs/lock folder indicated above.
> > >
> > > _______________________________________________
> > > gui-dev mailing list
> > > [email protected]
> > > http://www.limewire.org/mailman/listinfo/gui-dev
> >
> > _______________________________________________
> > gui-dev mailing list
> > [email protected]
> > http://www.limewire.org/mailman/listinfo/gui-dev
> _______________________________________________
> gui-dev mailing list
> [email protected]
> http://www.limewire.org/mailman/listinfo/gui-dev

_______________________________________________
gui-dev mailing list
[email protected]
http://www.limewire.org/mailman/listinfo/gui-dev