[kdewebdev-site] Permissions continued

Andras Mantia amantia at kdewebdev.org
Sat Mar 5 10:35:01 EST 2005


On Saturday 05 March 2005 00:39, Eric Laffoon wrote:
> > It is:
> > -rw-rw-r--    1 amantia  kdewebde     6801 Mar  3 03:03 xml.dcl
>
> Strange. I have a couple files in kallery that are in the project and
> block me when I try to upload too, as well as the scripts and another
> directory in public_html that Quanta can't seem to identify correctly
> as directories, but as files which expand like directories. Maybe I
> should send you the project file, but it's also on site.

I will check the Kallery site, altough I think it's OK.

>
> > so it's group writable...
> > But remember, that this mail referred to the /var/lib/cvs, the list
> > with problem directories under /home/kdewebdev is in the other mail
> > I sent today to the list.
>
> Now I'm really confused. I've looked at the CVS and it seems like all
> directories are group writable. 

Yes, all are group writable (except Paulo's releases directory), but 
some of them miss the setgid flag. This means the if I add a new file 
under such directory it will belong only to me, not to the group, so 
nobody else could write to it anymore. This is bad, so every directory 
must have the setgid flag set. This wouldn't be a problem if we knew it 
from the start and before even importing anything to CVS, the top 
directories would have the setgid flag set.
 The same thing applies for the /home directories, but now for the 
upload, not for committing. So I sent to lists yesterday, the first 
(detailed) with the problem directories under /home/kdewebdev (and 
subdomains), the second (not detailed, just with the directory names) 
under /var/lib/cvs. 
 I suggest to stop uploading and committing until the permission issues 
are solved, otherwise we will never get to the end of this.

> All files are read only and this 
> seems to work fine. 

Yes, this is OK.

> You are still having trouble pulling CVS? 
I'm trying now:
cvs server: failed to create lock directory for 
`/var/lib/cvs/kdewebdev/klinkstatus/public_html/releases' (/var/lib/cvs/kdewebdev/klinkstatus/public_html/releases/#cvs.lock): 
Permission denied
cvs server: failed to obtain dir lock in repository 
`/var/lib/cvs/kdewebdev/klinkstatus/public_html/releases'
cvs [server aborted]: read lock failed - giving up
cvs [update aborted]: received broken pipe signal

This is because of:
drwxrwxr-x    2 moura    moura        4096 Mar  4 13:01 releases

But see now my Test commit (a new test.html and a modified quanta.php) 
to developer area in CVS:
-r--r--r--    1 amantia  amantia      3129 Mar  5 03:33 quanta.php,v
-r--r--r--    1 amantia  amantia       263 Mar  5 03:33 test.html,v

(I changed back, so you won't have a problem, but this is what I got 
after commit).

Now I don't think we want this. This is because:
drwxrwxr-x    3 kdewebde kdewebde     4096 Mar  4 13:11 developer
instead of
drwxrwsr-x    3 kdewebde kdewebde     4096 Mar  4 13:11 developer

Same for the other directories I listed there.

> I had  
> weird problems before and did a fresh checkout and everything seemed
> okay so I could not complain. Have you tried that?
This is not about checking out, it's about checking in. ;-)

> > I don't mind if some areas are not group writable, just we need to
> > know what and where can we commit and where can we upload. And
> > where we (any of us) can commit and upload should have the correct
> > permissions, so we don't stay in someone other's way.
>
> This brings up a question about project files. For instance you have
> release files in the project that I don't need to upload. I guess I
> mark them as uploaded.

Mar them as Never Upload.

> Then if you update and commit won't Quanta 
> want to upload again? What if I mark the file as don't upload? Will
> that cause problems for you?

No. I can still upload if I want.

> Maybe we need even more thought for Team functionality for 3.5? ;-)

There are some thing that should be enhanced there. One was the 
separation of user specific settings from the project files. I have 
such webprj files for almost all subdomains, but I don't know if you 
want to commit or not. If you don't use CVS HEAD, the user specific 
settings will be written to the webprj file...
 I also created a global webprj file, but in order make this really 
usable, we should define different upload profiles per subdomains.
So there is room to improve. ;-)

Andras
-- 
Quanta Plus developer - http://quanta.sourceforge.net
K Desktop Environment - http://www.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://momo.creolmail.org/pipermail/kdewebdev-site/attachments/20050305/9df0dd2c/attachment-0001.pgp


More information about the kdewebdev-site mailing list