Transfer to SourceForge: Difference between revisions
| Line 41: | Line 41: | ||
== [[Image:Warning.png]] Dual Transfers == | == [[Image:Warning.png]] Dual Transfers == | ||
If the 32bit ISO has already been transferred to the NST Pro site, then one can download it, check the md5sum and start the transfer to sourceforge | If the 32bit ISO has already been transferred to the NST Pro site, then one can download it, check the md5sum and start the transfer to sourceforge. | ||
= Save Copy On cirrus = | = Save Copy On cirrus = | ||
Revision as of 08:26, 13 April 2013
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:
[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 [root@nst-dev-32 repo]# emacs nst-2.15.0-2515/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).
[root@dev18-32 repo]# (unset DISPLAY; make -C yum sftp-sf SFUSER=your-user-id) make: Entering directory `/root/repo/yum' if [ -z "" ]; then \ sftp your-user-id,nst@frs.sourceforge.net:/home/frs/project/n/ns/nst/; \ else \ nautilus ssh://your-user-id,nst@frs.sourceforge.net/home/frs/project/n/ns/nst/; \ fi Connecting to frs.sourceforge.net... Enter passphrase for key '/root/.ssh/id_dsa': Changing to: /home/frs/project/n/ns/nst/ sftp> mkdir "NST/NST 18-4509" sftp> ls NST NST/NST 18-4509 NST/NST v2.13.0-2066 NST/NST v2.15.0-2515 NST/NST v2.16.0-3170 NST/NST v2.16.0-4104 sftp> cd "NST/NST 18-4509" sftp> lcd ../nst-18-4509 sftp> lls README.txt nst-2.13.0-1713.i686.iso nst-2.13.0-1713.tar.gz nst-minimal-2.13.0-1713.i686.iso release-notes-2.13.0-1713.txt sftp> put README.txt ... Output as source is uploaded ... sftp> put nst-18-4509.tar.gz ... Output as source is uploaded ... sftp> put nst-18-4509.i686.iso ... Output as ISO is uploaded ... sftp>
Dual Transfers
If the 32bit ISO has already been transferred to the NST Pro site, then one can download it, check the md5sum and start the transfer to sourceforge.
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:
[root@dev18-32 repo]# scp -rp nst-18-4509/ cirrus:/NSTDEV32/releases/nst-18-4509/ ... Many files are transferred ... [root@dev18-32 repo]#
