Difference between revisions of "Transfer to SourceForge"

From NST Wiki
Jump to navigationJump to search
(Image:Warning.png‎ Dual Transfers)
(FTP to SourceForge)
Line 10: Line 10:
 
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).
  
  [root@dev18-32 repo]# (unset DISPLAY; make -C yum sftp-sf SFUSER=your-user-id)
+
  [nst@nst24-repo repo]$ (unset DISPLAY; make -C yum sftp-sf SFUSER=USERNAME)  
  make: Entering directory `/root/repo/yum'
+
  make: Entering directory '/home/nst/repo/yum'
 
  if [ -z "" ]; then \
 
  if [ -z "" ]; then \
  sftp your-user-id,nst@frs.sourceforge.net:/home/frs/project/n/ns/nst/; \
+
  sftp USERNAME,nst@frs.sourceforge.net:/home/frs/project/n/ns/nst/; \
else \
+
else \
  nautilus ssh://your-user-id,nst@frs.sourceforge.net/home/frs/project/n/ns/nst/; \
+
  nautilus ssh://USERNAME,nst@frs.sourceforge.net/home/frs/project/n/ns/nst/; \
fi
+
fi
  Connecting to frs.sourceforge.net...
+
  Connected to frs.sourceforge.net.
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 18-4509"
+
  sftp> mkdir "NST/NST 24-7977"
 
  sftp> ls NST
 
  sftp> ls NST
  NST/NST 18-4509          NST/NST v2.13.0-2066      NST/NST v2.15.0-2515     
+
  NST/NST 20-6535    NST/NST 22-7248    NST/NST 22-7334    NST/NST 24-7977   
NST/NST v2.16.0-3170      NST/NST v2.16.0-4104   
+
  sftp> cd "NST/NST 24-7977"
  sftp> cd "NST/NST 18-4509"
+
  sftp> lcd ../nst-24-7977
  sftp> lcd ../nst-18-4509
 
 
  sftp> lls
 
  sftp> lls
README.txt
+
  nst-24-7977.tar.gz README.txt
  nst-2.13.0-1713.i686.iso
+
  nst-24-7977.x86_64.iso release-notes-24-7977.txt
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
 
  sftp> put README.txt
  ... Output as source is uploaded ...
+
  Uploading README.txt to /home/pfs/project/n/ns/nst/NST/NST 24-7977/README.txt
  sftp> put nst-18-4509.tar.gz
+
README.txt                                    100% 1150    1.1KB/s  00:01   
  ... Output as source is uploaded ...
+
  sftp> put nst-24-7977.tar.gz
  sftp> put nst-18-4509.i686.iso
+
  Uploading nst-24-7977.tar.gz to /home/pfs/project/n/ns/nst/NST/NST 24-7977/nst-24-7977.tar
  ... Output as ISO is uploaded ...
+
  sftp> put nst-24-7977.x86_64.iso
sftp>
+
  Uploading nst-24-7977.x86_64.iso to /home/pfs/project/n/ns/nst/NST/NST 24-7977/nst-24-7977.x86_64.iso
  
 +
<!--
 
== [[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 from a different location.
 
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 from a different location.
 +
-->
  
 
= Save Copy On cirrus =
 
= Save Copy On cirrus =

Revision as of 19:15, 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:

[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).

[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


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]#