From: Jérôme <rom...@ya...> - 2013-03-24 10:28:27
|
I thought it was an other level according to table of content! Release Files for Download (FRS) File Manager (Web Interface) SCP Rsync SFTP SSH Release notes Known limitations Migration from package/release system And not specific (child level) to SSH. OK, I will try SSH. Thanks! Jérôme Le 23/03/2013 20:34, John Ralls a écrit : > > On Mar 23, 2013, at 12:16 PM, Jérôme <rom...@ya...> wrote: > >>> Yeah, use a naked shell instead of ftp: >>> http://sourceforge.net/p/forge/documentation/Shell%20Service/ >> >> Well, then something is missing or wrong on sourceforge's documentation... >> >> "Known limitations >> >> Moving files may be accomplished via the shell, but cannot be done with the web file manager. >> Note: download statistics are based on path and filename, so stats for moved files will be reset. Your total project download count will include the previous name's stats. >> Migration from package/release system >> >> For projects that had releases available for download at the time of the change to the File Manager facility (July 2009), those files were migrated to logical folders. This is based upon the package & release names. >> >> In addition to the folders created for migrated package and releases, an "OldFiles" folder was also created which contains files that were previously hidden. The "OldFiles" folder is not visible to users downloading files from your project. If you wish to make a file visible, simply move it to a different folder." >> >> http://sourceforge.net/p/forge/documentation/Release%20Files%20for%20Download/ > > But you didn't do that. You were using sftp, which doesn't have a 'mv' command. Just ssh in to SF following the directions on the link I gave you, cd to the frs folder, and then use mv. > > Regards, > John Ralls > > |