[Savannah-hackers] [support #103302] Can't commit due to permissions problem

[Sylvain Beucler]

This mail is an automated notification from the support tracker
 of the project: Savannah Administration.

/**************************************************************************/
[support #103302] Latest Modifications:

Changes by: 
                Sylvain Beucler <address@hidden>
'Date: 
                Thu 08/26/2004 at 13:54 (Europe/Paris)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | Postponed                 | Done


------------------ Additional Follow-up Comments ----------------------------
Done. Let me know if everything is ok.
You also have to make a new checkout of the station-info module.






/**************************************************************************/
[support #103302] Full Item Snapshot:

URL: <http://savannah.gnu.org/support/?func=detailitem&item_id=103302>
Project: Savannah Administration
Submitted by: John Kodis
On: Wed 08/25/2004 at 12:59

Category:  None
Priority:  5 - Normal
Severity:  1 - None
Resolution:  Done
Privacy:  Public
Assigned to:  Beuc
Originator Email:  address@hidden
Status:  Open


Summary:  Can't commit due to permissions problem

Original Submission:  I tried to check a few small changes in today, but thec 
ommits are aborting due to a permission problem.  Here's a typical failure:
                                                                                
    address@hidden:station-info> cvs-station ci NEWS configure.ac
    Checking in NEWS;
    /cvsroot/station-info/NEWS,v  <--  NEWS
    new revision: 1.19; previous revision: 1.18
    cvs [commit aborted]: cannot rename file
    /cvsroot/station-info/,NEWS,
    to /cvsroot/station-info/NEWS,v: Operation not permitted
                                                                                
The cvs-station command is just an alias that points to the project repository:
                                                                                
    alias cvs-station='CVS_RSH=ssh cvs -z3 -d
    :ext:address@hidden:/cvsroot/station-info'
                                                                                
Oddly, this problem only seems to effect existing files at the top level of the 
project.  I have been able to add new files to the top level directory, and 
commit changes to the new file and to files in any of the project 
subdirectories.  This indicates that the problem is not with my ssh or 
networking setup, but something about the permission or ownership of the 
top-level project files.
                                                                                
Thanks for any assistance that you can offer.
                                                                                
-- John Kodis.
                                                                                

Follow-up Comments
------------------


-------------------------------------------------------
Date: Thu 08/26/2004 at 13:54       By: Sylvain Beucler <Beuc>
Done. Let me know if everything is ok.
You also have to make a new checkout of the station-info module.

-------------------------------------------------------
Date: Thu 08/26/2004 at 13:06       By: John Kodis <kodis>
Yes, moving all of the top-level files into a single station-info module is 
probably the right thing to do, especially if that's the most common setup.

Thanks for your assistance.


-------------------------------------------------------
Date: Thu 08/26/2004 at 12:36       By: Sylvain Beucler <Beuc>
Currently for security reason we do not provide full write access on the 
top-level directory of the repository. The best would be to move all your files 
in a 'station-info' module.

Do you want me to do this?


-------------------------------------------------------
Date: Wed 08/25/2004 at 14:17       By: Sylvain Beucler <Beuc>
People usually do not use the same directory layout as you do: they create a 
top-level module and put all their files in it.

However, I do not know exactly why the top-level directory permissions are set 
this way (1777) - it is the same sitewide. I need to have a discussion with 
some other Savannah hackers tonight before to make a decision.












For detailed info, follow this link:
<http://savannah.gnu.org/support/?func=detailitem&item_id=103302>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/