Difference between revisions of "Transfer to SourceForge"
From NST Wiki
Jump to navigationJump to search| Line 1: | Line 1: | ||
| + | = Tweak Release Notes = | ||
| + | |||
| + | You should review and possibly ''tweak'' the release notes that will accompany the upload to SourceForge prior to uploading the files. For example: | ||
| + | |||
| + | [root@nst-dev-32 repo]# emacs nst-2.13.0-1713/release-notes-2.13.0-1713.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). | 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). | ||
| Line 11: | Line 20: | ||
Enter passphrase for key '/root/.ssh/id_dsa': | Enter passphrase for key '/root/.ssh/id_dsa': | ||
Changing to: /home/frs/project/n/ns/nst/ | Changing to: /home/frs/project/n/ns/nst/ | ||
| − | sftp> mkdir "NST/NST v2.13.0" | + | sftp> mkdir "NST/NST v2.13.0-1713" |
sftp> ls NST | sftp> ls NST | ||
| − | NST/NST v1.8.0 NST/NST v1.8.1 NST/NST v2.13.0 | + | NST/NST v1.8.0 NST/NST v1.8.1 NST/NST v2.13.0-1713 |
| − | sftp> cd "NST/NST v2.13.0" | + | sftp> cd "NST/NST v2.13.0-1713" |
| − | sftp> lcd ../nst-2.13.0 | + | sftp> lcd ../nst-2.13.0-1713 |
sftp> lls | sftp> lls | ||
| − | nst-2.13.0. | + | nst-2.13.0-1713.i686.iso |
| − | nst-2.13.0.tar.gz | + | nst-2.13.0-1713.tar.gz |
| − | nst-minimal-2.13.0. | + | nst-minimal-2.13.0-1713.i686.iso |
| − | sftp> put release-notes-2.13.0.txt | + | release-notes-2.13.0-1713.txt |
| + | sftp> put release-notes-2.13.0-1713.txt | ||
... Output as source is uploaded ... | ... Output as source is uploaded ... | ||
| − | sftp> put nst-2.13.0.tar.gz | + | sftp> put nst-2.13.0-1713.tar.gz |
... Output as source is uploaded ... | ... Output as source is uploaded ... | ||
| − | sftp> put nst | + | sftp> put nst-2.13.0-1713.i686.iso |
... Output as ISO is uploaded ... | ... Output as ISO is uploaded ... | ||
| − | |||
| − | |||
| − | |||
| − | |||
sftp> | sftp> | ||
NOTE: In the past, we've had user's start to download files before they were fully transferred. To avoid this, you can transfer the files to the ''OldFiles'' directory first and then use the '''rename''' command to make the files "instantly" appear in the download area. | NOTE: In the past, we've had user's start to download files before they were fully transferred. To avoid this, you can transfer the files to the ''OldFiles'' directory first and then use the '''rename''' command to make the files "instantly" appear in the download area. | ||
| + | |||
| + | = 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@nst-dev-32 repo]# scp -rp nst-2.13.0-1713/ cirrus:/NSTDEV32/releases/nst-2.13.0-1713/ | ||
| + | |||
| + | ... Many files are transferred ... | ||
| + | |||
| + | [root@nst-dev-32 repo]# | ||
Revision as of 11:55, 21 January 2011
Tweak Release Notes
You should review and possibly tweak the release notes that will accompany the upload to SourceForge prior to uploading the files. For example:
[root@nst-dev-32 repo]# emacs nst-2.13.0-1713/release-notes-2.13.0-1713.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@nst-dev-32 repo]# (unset DISPLAY; make -C yum sftp-sf) make: Entering directory `/root/repo/yum' if [ -z "" ]; then \ sftp pblankenbaker,nst@frs.sourceforge.net:/home/frs/project/n/ns/nst/; \ else \ nautilus ssh://pblankenbaker,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 v2.13.0-1713" sftp> ls NST NST/NST v1.8.0 NST/NST v1.8.1 NST/NST v2.13.0-1713 sftp> cd "NST/NST v2.13.0-1713" sftp> lcd ../nst-2.13.0-1713 sftp> lls 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 release-notes-2.13.0-1713.txt ... Output as source is uploaded ... sftp> put nst-2.13.0-1713.tar.gz ... Output as source is uploaded ... sftp> put nst-2.13.0-1713.i686.iso ... Output as ISO is uploaded ... sftp>
NOTE: In the past, we've had user's start to download files before they were fully transferred. To avoid this, you can transfer the files to the OldFiles directory first and then use the rename command to make the files "instantly" appear in the download area.
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@nst-dev-32 repo]# scp -rp nst-2.13.0-1713/ cirrus:/NSTDEV32/releases/nst-2.13.0-1713/ ... Many files are transferred ... [root@nst-dev-32 repo]#
