mainSavannah Administration - Support: sr #104708, Binary download directory.

 
 

sr #104708: Binary download directory.

Submitter:  Derek Robert Price <dprice>
Submitted:  Wed 05 Oct 2005 05:31:22 PM UTC
   
 
Category:  Download area - developer access Priority:  5 - Normal
Severity:  4 - Important Status:  Done
Privacy:  Public Assigned to:  Beuc
Operating System:  None Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Sat 03 Dec 2005 09:02:11 PM UTC, comment #17: 

Sorry for not bean clear :)
I mean: since this is a shared directory, with each member having an account instead of using a shared account, other project members can be stuck with bad permissions. sftp tries to respect the permissions of the original file you upload (which can lack the group permissions, for example), and vicious people can chgrp directories and lock other members out.

I don't think this should be a real issue, but if this kind of issues happen too often, we may work on patching sftp accordingly or try to provide one account for all project members (though we lose track of who does what then).

Sylvain Beucler <Beuc>
Sat 03 Dec 2005 08:30:26 PM UTC, comment #16: 

It appears to be working for me.  What were we doing wrong with the permissions?  o+w or something?  I really didn't do anything to the permissions...  I just let the system use its defaults...

Thanks,

Derek Robert Price <dprice>
Fri 02 Dec 2005 11:59:38 PM UTC, comment #15: 

I'm working on the download setup.
Please use
sftp -o port=10022 YOUR_SAVANNAH_USERNAME@savannah.gnu.org:/var/lib/download/cvs

You need to be more careful with permissions, btw.
Feedback would be appreciated :)

Sylvain Beucler <Beuc>
Mon 07 Nov 2005 10:33:14 PM UTC, comment #14: 

Okay, great!  We'll try not to lock it.  :)

Thanks again,

Anonymous
Mon 07 Nov 2005 10:24:19 PM UTC, comment #13: 

It will be easier to let things as is - that is, until sftp accounts are available sidewide.

It you lock the account, just open a support request :)

Sylvain Beucler <Beuc>
Mon 07 Nov 2005 05:27:28 PM UTC, comment #12: 

One final thought, if you want to take away our direct access to our own authorized_keys file, and it isn't too hard, maintaining it with the same ssh keys that are authorized for CVS access to the cvs project via savannah would work.  This way we can't accidentally lock ourselves out without an established way to restore our access via the savannah interface.  Otherwise, we are very happy anyhow and will be careful with the authorized_keys file.

Thanks again,

Derek Robert Price <dprice>
Mon 07 Nov 2005 02:55:20 PM UTC, comment #11: 

Thanks Sylvain!  It looks like it is working, so you can close this.

Thanks again!

Derek Robert Price <dprice>
Sun 06 Nov 2005 05:57:07 PM UTC, comment #10: 

Derek, try:

 sftp -o port=10022 -email is unavailable-

Then update ~/.ssh/authorized_keys to suit your needs, and manager ~/cvs/ which points to the download area.

Tell me if there's something, or if you think there is a security risk in my setup somewhere (shouldn't be) :)

Sylvain Beucler <Beuc>
Thu 20 Oct 2005 05:10:03 PM UTC, comment #9: 

Okay, that sounds simple enough.  I assume the sftp account could be equipped to handle multiple uploaders?  We currently have 4 people who would like access re CVS task #4844.

Derek Robert Price <dprice>
Thu 20 Oct 2005 04:56:50 PM UTC, comment #8: 

I would like to get Justin's reply first.

The solution I would setup - until Savannah gets the needed upload management and if ftp.gnu.org/non-gnu cannot get directives activated - would be a sftp account, I think.

Sylvain Beucler <Beuc>
Thu 20 Oct 2005 04:47:38 PM UTC, comment #7: 

So, something like the procedure outlined in http://www.gnu.org/prep/maintain/html_node/Automated-Upload-Procedure.html, but upload to ftp://savannah.gnu.org/incoming/savannah/cvs/with-directives or the like?  This would work for us.

Derek Robert Price <dprice>
Thu 20 Oct 2005 04:18:24 PM UTC, comment #6: 

I didn't know the system didn't work for non-gnu/ :/

I really can't set an ETA for supporting sftp and the like. This is the same restructuration issue than with supporting Arch - plus I'm in the process of moving 1000km North which doesn't ease the thing :)

Supporting an upload directory that I would manually manage may be possible. The way it would be done would however be subject to change in the long run.

Sylvain Beucler <Beuc>
Thu 20 Oct 2005 04:03:18 PM UTC, comment #5: 

This issue may need to be reopened.

Re CVS task #4844, Justin Baugh wrote me back for -email is unavailable- saying that the instructions you referred me to were for admininstrating subdirectories of the "gnu" directory of ftp.gnu.org only and did not apply to ftp.gnu.org/non-gnu/. I asked whether it was possible to change this about 24 hours ago and have yet to get a response.

Anyhow, I'm trying to explore all our options.  How likely is it that Savannah will grant control over subdirectories in the project download areas in the near future?  If likely, how long would this take?  If not likely, would it be possible to make special arrangements for the CVS project?

Thanks,

Derek Robert Price <dprice>
Tue 18 Oct 2005 02:58:28 PM UTC, comment #4: 

Ok, thanks.

Sylvain Beucler <Beuc>
Tue 18 Oct 2005 02:47:02 PM UTC, comment #3: 

Hi,

You can close this if you like.  I am going to request direct access to ftp.gnu.org for several project members, using the -email is unavailable- email.

Thanks,

Derek Robert Price <dprice>
Tue 11 Oct 2005 03:04:02 PM UTC, comment #2: 

Hrm.  ftp.gnu.org/non-gnu/cvs is already a mirror of Savannah in this case.  I'm not sure how the current mirroring setup would interoperate with also using the ftp.gnu.org interface.

The easiest thing from my end would be if you let me create and admin download directories on Savannah, let other project members do the same, and the current mirroring script continued to mirror this to ftp.gnu.org, but perhaps the best thing all around would be if I and any project members who wish to registered to admin the ftp.gnu.org/non-gnu/cvs directory directly and we broke the mirror?  This would avoid the ~4 hour delay between uploads to Savannah and the mirroring, and I could then avoid advertising the Savannah download page in release announcements, which should save on Savannah bandwidth.  We could also leave the binaries off Savannah which should also save Savannah bandwidth and you wouldn't have to hurry with any Savannah download subdir admin programs.  In the end, this wouldn't be much harder for me anyhow, since my release uploads are scripted anyhow - I'll only have to make the change once.

Are we agreed?  If so, I can send the appropriate requests to ftp-upload@gnu.org.

Derek Robert Price <dprice>
Fri 07 Oct 2005 05:17:33 PM UTC, comment #1: 

Hi,

I remember that CVS has a download area at ftp.gnu.org; ftp.gnu.org accepts a directive file that can create sub-directories:
http://www.gnu.org/prep/maintain/html_node/Automated-Upload-Procedure.html

If this concerns Savannah itself, we can manually create such directories.

What do you think?

Sylvain Beucler <Beuc>
Wed 05 Oct 2005 05:31:22 PM UTC, original submission:  

Hello,

I know the documentation says no, but is there any way to create & manage subdirectories in our project FTP area?  We have been getting user complaints that we haven't distributed binaries since the move to Savannah and Conrad & I were discussing how to distribute them from Savannah, but with often 7 or more binaries distributed with each CVS release, I was worried that the flat download area provided by Savannah would become difficult to navigate after a few releases.  With just sources and a few suport files from the releases, our download area is already starting to look pretty messy.

Thanks,

Derek Robert Price <dprice>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Digest:
   task dependencies.

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

Follow 11 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2005-11-07 Beuc StatusNeed Info Done
    Open/ClosedOpen Closed
2005-10-20 dprice Dependencies- task #4844 is dependent
2005-10-20 Beuc StatusWont Do Need Info
    Open/ClosedClosed Open
    Carbon-Copy- Added baughj
2005-10-18 Beuc StatusNone Wont Do
    Open/ClosedOpen Closed
2005-10-07 Beuc Assigned toNone Beuc
2005-10-05 dprice Carbon-Copy- Added -email is unavailable-
    Carbon-Copy- Added -email is unavailable-

Back to the top

Powered by Savane 3.13-3230.
Corresponding source code