Transfer to SourceForge: Difference between revisions

From MediaWiki
Jump to navigationJump to search
No edit summary
Line 3: Line 3:
You should copy the release notes to a file named ''README.txt'', review and ''tweak'' them prior to uploading the files. For example:
You should copy the release notes to a file named ''README.txt'', review and ''tweak'' them prior to uploading the files. For example:


  [root@nst-dev-32 repo]# cp nst-2.15.0-2515/release-notes-2.15.0-2515.txt nst-2.15.0-2515/README.txt
  [nst@nst24-repo repo]$ cp nst-24-7977/release-notes-24-7977.txt nst-24-7977/README.txt
  [root@nst-dev-32 repo]# emacs nst-2.15.0-2515/README.txt
  [nst@nst24-repo repo]$ emacs -nw nst-24-7977/README.txt


= FTP to SourceForge =
= FTP to SourceForge =
Line 34: Line 34:
  sftp> put nst-24-7977.x86_64.iso
  sftp> put nst-24-7977.x86_64.iso
  Uploading nst-24-7977.x86_64.iso to /home/pfs/project/n/ns/nst/NST/NST 24-7977/nst-24-7977.x86_64.iso
  Uploading nst-24-7977.x86_64.iso to /home/pfs/project/n/ns/nst/NST/NST 24-7977/nst-24-7977.x86_64.iso
sftp> exit
[nst@nst24-repo repo]$


<!--
<!--
Line 42: Line 44:
= Save Copy On cirrus =
= Save Copy On cirrus =


You should also save a copy of the released files under the ''/NSTDEV32/releases'' (32 bit) and ''/NSTDEV64/releases'' (64 bit) directory corresponding to the build. For example, if you just produced the 32 bit ''nst-2.13.0-1713'' release, you would run the following command:
You should also save a copy of the released files under the ''/NSTDEV64/releases'' directory. For example:


  [root@dev18-32 repo]# scp -rp nst-18-4509/ cirrus:/NSTDEV32/releases/nst-18-4509/
  [nst@nst24-repo repo]$ rsync -avh -rp nst-24-7977 cirrus:/NSTDEV64/releases
   
   
  ... Many files are transferred ...
  ... Files are transferred ...
   
   
  [root@dev18-32 repo]#
  [nst@nst24-repo repo]$

Revision as of 18:19, 3 July 2016

Tweak Release Notes

You should copy the release notes to a file named README.txt, review and tweak them prior to uploading the files. For example: 

[nst@nst24-repo repo]$ cp nst-24-7977/release-notes-24-7977.txt nst-24-7977/README.txt
[nst@nst24-repo repo]$ emacs -nw nst-24-7977/README.txt

FTP to SourceForge

At this point you can start transferring files to SourceForge. The make -C yum sftp-sf can be used to simplify this task (NOTE: It defaults to Nautilus if the DISPLAY variable is set, unset DISPLAY to remain on the command line). 

[nst@nst24-repo repo]$ (unset DISPLAY; make -C yum sftp-sf SFUSER=USERNAME) 
make: Entering directory '/home/nst/repo/yum'
if [ -z "" ]; then \
  sftp USERNAME,nst@frs.sourceforge.net:/home/frs/project/n/ns/nst/; \
else \
  nautilus ssh://USERNAME,nst@frs.sourceforge.net/home/frs/project/n/ns/nst/; \
fi
Connected to frs.sourceforge.net.
Changing to: /home/frs/project/n/ns/nst/
sftp> mkdir "NST/NST 24-7977"
sftp> ls NST
NST/NST 20-6535     NST/NST 22-7248     NST/NST 22-7334     NST/NST 24-7977     
sftp> cd "NST/NST 24-7977"
sftp> lcd ../nst-24-7977
sftp> lls
nst-24-7977.tar.gz	README.txt
nst-24-7977.x86_64.iso	release-notes-24-7977.txt
sftp> put README.txt
Uploading README.txt to /home/pfs/project/n/ns/nst/NST/NST 24-7977/README.txt
README.txt                                    100% 1150     1.1KB/s   00:01    
sftp> put nst-24-7977.tar.gz
Uploading nst-24-7977.tar.gz to /home/pfs/project/n/ns/nst/NST/NST 24-7977/nst-24-7977.tar
sftp> put nst-24-7977.x86_64.iso
Uploading nst-24-7977.x86_64.iso to /home/pfs/project/n/ns/nst/NST/NST 24-7977/nst-24-7977.x86_64.iso
sftp> exit
[nst@nst24-repo repo]$


Save Copy On cirrus

You should also save a copy of the released files under the /NSTDEV64/releases directory. For example: 

[nst@nst24-repo repo]$ rsync -avh -rp nst-24-7977 cirrus:/NSTDEV64/releases

... Files are transferred ...

[nst@nst24-repo repo]$
Retrieved from "https://wiki.networksecuritytoolkit.org/nstwiki/index.php?title=Transfer_to_SourceForge&oldid=8396"