Transfer to SourceForge - Revision history

Paul Blankenbaker at 16:04, 16 July 2019

2019-07-16T16:04:49Z

← Older revision		Revision as of 12:04, 16 July 2019
Line 41:		Line 41:
	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 =~~

	~~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]$~~

Paul Blankenbaker at 23:19, 3 July 2016

2016-07-03T23:19:15Z

← Older revision		Revision as of 19:19, 3 July 2016
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]$

Paul Blankenbaker: /* FTP to SourceForge */

2016-07-03T23:15:05Z

FTP to SourceForge

← Older revision		Revision as of 19:15, 3 July 2016
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 =

Rwh: /* Image:Warning.png‎ Dual Transfers */

2013-04-13T13:31:25Z

Image:Warning.png‎ Dual Transfers

← Older revision		Revision as of 09:31, 13 April 2013
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 from ~~two~~ different ~~locations~~.		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 =

Rwh: /* Image:Warning.png‎ Dual Transfers */

2013-04-13T13:30:35Z

Image:Warning.png‎ Dual Transfers

← Older revision		Revision as of 09:30, 13 April 2013
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 from two different locations.

	= Save Copy On cirrus =		= Save Copy On cirrus =

Rwh: /* Image:Warning.png‎ Dual Transfers */

2013-04-13T13:26:33Z

Image:Warning.png‎ Dual Transfers

← Older revision		Revision as of 09:26, 13 April 2013
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.

	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 =		= Save Copy On cirrus =

Rwh: /* FTP to SourceForge */

2013-04-13T13:26:01Z

FTP to SourceForge

← Older revision		Revision as of 09:26, 13 April 2013
Line 39:		Line 39:
	... Output as ISO is uploaded ...		... Output as ISO is uploaded ...
	sftp>		sftp>

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

	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.

Paul Blankenbaker: /* Save Copy On cirrus */

2013-04-13T13:08:21Z

Save Copy On cirrus

← Older revision		Revision as of 09:08, 13 April 2013
Line 46:		Line 46:
	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 ''/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~~/		[root@dev18-32 repo]# scp -rp nst-18-4509/ cirrus:/NSTDEV32/releases/nst-18-4509/

	... Many files are transferred ...		... Many files are transferred ...

	[root@~~nst-dev~~-32 repo]#		[root@dev18-32 repo]#

Paul Blankenbaker: Updated for NST 18

2013-04-13T13:07:22Z

Updated for NST 18

← Older revision		Revision as of 09:07, 13 April 2013
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@~~nst-dev~~-32 repo]# (unset DISPLAY; make -C yum sftp-sf SFUSER=your-user-id)		[root@dev18-32 repo]# (unset DISPLAY; make -C yum sftp-sf SFUSER=your-user-id)
	make: Entering directory `/root/repo/yum'		make: Entering directory `/root/repo/yum'
	if [ -z "" ]; then \		if [ -z "" ]; then \
Line 20:		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~~-~~1713~~"		sftp> mkdir "NST/NST 18-4509"
	sftp> ls NST		sftp> ls NST
	NST/NST v1.8.0 NST/NST v1.8.1 NST/NST v2.13.0-~~1713~~		NST/NST 18-4509 NST/NST v2.13.0-2066 NST/NST v2.15.0-2515
	sftp> cd "NST/NST ~~v2.13.0~~-~~1713~~"		NST/NST v2.16.0-3170 NST/NST v2.16.0-4104
	sftp> lcd ../nst-~~2.13.0~~-~~1713~~		sftp> cd "NST/NST 18-4509"
			sftp> lcd ../nst-18-4509
	sftp> lls		sftp> lls
	README.txt		README.txt
Line 33:		Line 34:
	sftp> put README.txt		sftp> put README.txt
	... Output as source is uploaded ...		... Output as source is uploaded ...
	sftp> put nst-~~2.13.0~~-~~1713~~.tar.gz		sftp> put nst-18-4509.tar.gz
	... Output as source is uploaded ...		... Output as source is uploaded ...
	sftp> put nst-~~2.13.0~~-~~1713~~.i686.iso		sftp> put nst-18-4509.i686.iso
	... Output as ISO is uploaded ...		... Output as ISO is uploaded ...
	sftp>		sftp>

Paul Blankenbaker at 00:58, 28 February 2012

2012-02-28T00:58:13Z

← Older revision		Revision as of 20:58, 27 February 2012
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@nst-dev-32 repo]# (unset DISPLAY; make -C yum sftp-sf)		[root@nst-dev-32 repo]# (unset DISPLAY; make -C yum sftp-sf SFUSER=your-user-id)
	make: Entering directory `/root/repo/yum'		make: Entering directory `/root/repo/yum'
	if [ -z "" ]; then \		if [ -z "" ]; then \
	sftp ~~pblankenbaker~~,nst@frs.sourceforge.net:/home/frs/project/n/ns/nst/; \		sftp your-user-id,nst@frs.sourceforge.net:/home/frs/project/n/ns/nst/; \
	else \		else \
	nautilus ssh://~~pblankenbaker~~,nst@frs.sourceforge.net/home/frs/project/n/ns/nst/; \		nautilus ssh://your-user-id,nst@frs.sourceforge.net/home/frs/project/n/ns/nst/; \
	fi		fi
	Connecting to frs.sourceforge.net...		Connecting to frs.sourceforge.net...