Make Sure Public Repos Are Setup - Revision history

Rwh at 21:00, 23 June 2021

2021-06-23T21:00:58Z

← Older revision		Revision as of 17:00, 23 June 2021
Line 17:		Line 17:
	'''NOTE''': To create an ''empty'' repository at networksecuritytoolkit.org, log into the web server and run the following commands:		'''NOTE''': To create an ''empty'' repository at networksecuritytoolkit.org, log into the web server and run the following commands:
	cd ~/public_html/repo/nst		cd ~/public_html/repo/nst
	install -d f34 && ln -s ../empty f34/x86_64		install -d f34 && cp -a ../empty f34/x86_64

Paul Blankenbaker: Updated for NST 34 links

2021-06-13T15:20:14Z

Updated for NST 34 links

← Older revision		Revision as of 11:20, 13 June 2021
Line 1:		Line 1:
	You should verify that the public mirror list and ''yum'' repositories have be set up.		You should verify that the public mirror list and ''yum'' repositories have be set up.

	* Check the public repository mirror listing(s) for the release: http://www.networksecuritytoolkit.org/nst/mirrors/repo-~~f28~~-x86_64.mirrors.txt		* Check the public repository mirror listing(s) for the release: http://www.networksecuritytoolkit.org/nst/mirrors/repo-f34-x86_64.mirrors.txt
	* If you don't see a text mirror list file for the 64 bit release you need to do the following:		* If you don't see a text mirror list file for the 64 bit release you need to do the following:
	** Create and add the missing files to ''html/mirrors'' on the development machine.		** Create and add the missing files to ''html/mirrors'' on the development machine.
	** Edit the ''yum/pkgs/nstweb/pkginfo.xml'' file and bump the release number and update the dependency list for the new mirror files added.		** Edit the ''yum/pkgs/nstweb/pkginfo.xml'' file and bump the release number and update the dependency list for the new mirror files added.
	** Push out the mirrors and initial empty ''yum'' repositories by running the following commands on the development machine:		** Push out the mirrors and initial empty ''yum'' repositories by running the following commands on the development machine:
	[root@~~dev32~~ repo]# cd ~/nstpro		[root@dev repo]# cd ~/nstpro
	[root@~~dev32~~ nstpro]# make upload-repo		[root@dev nstpro]# make upload-repo
	* Verify that you can load the empty repomd.xml file from each of the listed mirrors for the release. For ~~the NST 28 release this was~~:		* Verify that you can load the empty repomd.xml file from each of the listed mirrors for the release. For example:
	** http://networksecuritytoolkit.org/repo/nst/~~f28~~/x86_64/repodata/repomd.xml		** http://networksecuritytoolkit.org/repo/nst/f34/x86_64/repodata/repomd.xml

	'''NOTE''': If there are any errors, you may need to log into the mirrors to create the top level directories.		'''NOTE''': If there are any errors, you may need to log into the mirrors to create the top level directories.
Line 17:		Line 17:
	'''NOTE''': To create an ''empty'' repository at networksecuritytoolkit.org, log into the web server and run the following commands:		'''NOTE''': To create an ''empty'' repository at networksecuritytoolkit.org, log into the web server and run the following commands:
	cd ~/public_html/repo/nst		cd ~/public_html/repo/nst
	install -d ~~f28~~ && ln -s ../empty ~~f28~~/x86_64		install -d f34 && ln -s ../empty f34/x86_64

Paul Blankenbaker at 12:31, 30 June 2018

2018-06-30T12:31:50Z

Paul Blankenbaker at 09:13, 8 October 2017

2017-10-08T09:13:05Z

← Older revision		Revision as of 05:13, 8 October 2017
Line 10:		Line 10:
	* Verify that you can load the empty repomd.xml file from each of the listed mirrors for the release. For the NST 26 release this was:		* Verify that you can load the empty repomd.xml file from each of the listed mirrors for the release. For the NST 26 release this was:
	** http://networksecuritytoolkit.org/repo/nst/f26/x86_64/repodata/repomd.xml		** http://networksecuritytoolkit.org/repo/nst/f26/x86_64/repodata/repomd.xml
	** http://repo.networksecuritytoolkit.org/repo/f26/x86_64/repodata/repomd.xml

	'''NOTE''': If there are any errors, you may need to log into the mirrors to create the top level directories.		'''NOTE''': If there are any errors, you may need to log into the mirrors to create the top level directories.

Paul Blankenbaker at 08:36, 6 October 2017

2017-10-06T08:36:21Z

← Older revision		Revision as of 04:36, 6 October 2017
Line 1:		Line 1:
	You should verify that the public mirror list and ''yum'' repositories have be set up.		You should verify that the public mirror list and ''yum'' repositories have be set up.

	* ~~Go to URL~~: http://www.networksecuritytoolkit.org/nst/mirrors/		* Check the public repository mirror listing(s) for the release: http://www.networksecuritytoolkit.org/nst/mirrors/repo-f26-x86_64.mirrors.txt
	* If you don't see a text mirror list file for the 64 bit release you need to do the following:		* If you don't see a text mirror list file for the 64 bit release you need to do the following:
	** Create and add the missing files to ''html/mirrors'' on the development machine.		** Create and add the missing files to ''html/mirrors'' on the development machine.
Line 8:		Line 8:
	[root@dev32 repo]# cd ~/nstpro		[root@dev32 repo]# cd ~/nstpro
	[root@dev32 nstpro]# make upload-repo		[root@dev32 nstpro]# make upload-repo
			* Verify that you can load the empty repomd.xml file from each of the listed mirrors for the release. For the NST 26 release this was:
			** http://networksecuritytoolkit.org/repo/nst/f26/x86_64/repodata/repomd.xml
			** http://repo.networksecuritytoolkit.org/repo/f26/x86_64/repodata/repomd.xml

	'''NOTE''': If there are any errors, you may need to log into the mirrors to create the top level directories.		'''NOTE''': If there are any errors, you may need to log into the mirrors to create the top level directories.

	'''NOTE''': You skip this step for interim releases.		'''NOTE''': You skip this step for interim releases.

			'''NOTE''': To create an ''empty'' repository at networksecuritytoolkit.org, log into the web server and run the following commands:
			cd ~/public_html/repo/nst
			install -d f26 && ln -s ../empty f26/x86_64

Paul Blankenbaker at 18:30, 2 July 2016

2016-07-02T18:30:39Z

← Older revision		Revision as of 14:30, 2 July 2016
Line 2:		Line 2:

	* Go to URL: http://www.networksecuritytoolkit.org/nst/mirrors/		* Go to URL: http://www.networksecuritytoolkit.org/nst/mirrors/
	* If you don't see a text mirror list file for ~~both 32 bit and~~ 64 bit you need to do the following:		* If you don't see a text mirror list file for the 64 bit release you need to do the following:
	** Create and add the missing files to ''html/mirrors'' on the development machine.		** Create and add the missing files to ''html/mirrors'' on the development machine.
	** Edit the ''yum/pkgs/nstweb/pkginfo.xml'' file and bump the release number and update the dependency list for the new mirror files added.		** Edit the ''yum/pkgs/nstweb/pkginfo.xml'' file and bump the release number and update the dependency list for the new mirror files added.
	** Push out the mirrors and initial empty ''yum'' repositories by running the following commands on ~~both~~ the ~~32 bit and 64 bit~~ development machine:		** Push out the mirrors and initial empty ''yum'' repositories by running the following commands on the development machine:
	[root@dev32 repo]# cd ~/nstpro		[root@dev32 repo]# cd ~/nstpro
	[root@dev32 nstpro]# make upload-repo		[root@dev32 nstpro]# make upload-repo

Paul Blankenbaker at 17:57, 8 February 2015

2015-02-08T17:57:09Z

← Older revision		Revision as of 13:57, 8 February 2015
Line 10:		Line 10:

	'''NOTE''': If there are any errors, you may need to log into the mirrors to create the top level directories.		'''NOTE''': If there are any errors, you may need to log into the mirrors to create the top level directories.

			'''NOTE''': You skip this step for interim releases.

Paul Blankenbaker at 13:46, 12 April 2013

2013-04-12T13:46:44Z

← Older revision		Revision as of 09:46, 12 April 2013
Line 6:		Line 6:
	** Edit the ''yum/pkgs/nstweb/pkginfo.xml'' file and bump the release number and update the dependency list for the new mirror files added.		** Edit the ''yum/pkgs/nstweb/pkginfo.xml'' file and bump the release number and update the dependency list for the new mirror files added.
	** Push out the mirrors and initial empty ''yum'' repositories by running the following commands on both the 32 bit and 64 bit development machine:		** Push out the mirrors and initial empty ''yum'' repositories by running the following commands on both the 32 bit and 64 bit development machine:
	[root@dev32 repo]# cd ~~yum~~		[root@dev32 repo]# cd ~/nstpro
	[root@dev32 ~~repo~~]# make repo~~-upload~~		[root@dev32 nstpro]# make upload-repo

	'''NOTE''': If there are any errors, you may need to log into the mirrors to create the top level directories.		'''NOTE''': If there are any errors, you may need to log into the mirrors to create the top level directories.

Paul Blankenbaker at 22:35, 27 February 2012

2012-02-27T22:35:29Z

← Older revision		Revision as of 18:35, 27 February 2012
Line 4:		Line 4:
	* If you don't see a text mirror list file for both 32 bit and 64 bit you need to do the following:		* If you don't see a text mirror list file for both 32 bit and 64 bit you need to do the following:
	** Create and add the missing files to ''html/mirrors'' on the development machine.		** Create and add the missing files to ''html/mirrors'' on the development machine.
			** Edit the ''yum/pkgs/nstweb/pkginfo.xml'' file and bump the release number and update the dependency list for the new mirror files added.
	** Push out the mirrors and initial empty ''yum'' repositories by running the following commands on both the 32 bit and 64 bit development machine:		** Push out the mirrors and initial empty ''yum'' repositories by running the following commands on both the 32 bit and 64 bit development machine:
	[root@dev32 repo]# cd yum		[root@dev32 repo]# cd yum

Paul Blankenbaker: Created page with "You should verify that the public mirror list and ''yum'' repositories have be set up. * Go to URL: http://www.networksecuritytoolkit.org/nst/mirrors/ * If you don't see a text ..."

2012-02-27T22:15:08Z

Created page with "You should verify that the public mirror list and ''yum'' repositories have be set up. * Go to URL: http://www.networksecuritytoolkit.org/nst/mirrors/ * If you don't see a text ..."

New page

You should verify that the public mirror list and ''yum'' repositories have be set up.

* Go to URL: http://www.networksecuritytoolkit.org/nst/mirrors/
* If you don't see a text mirror list file for both 32 bit and 64 bit you need to do the following:
** Create and add the missing files to ''html/mirrors'' on the development machine.
** Push out the mirrors and initial empty ''yum'' repositories by running the following commands on both the 32 bit and 64 bit development machine:
[root@dev32 repo]# cd yum
[root@dev32 repo]# make repo-upload

'''NOTE''': If there are any errors, you may need to log into the mirrors to create the top level directories.

← Older revision		Revision as of 08:31, 30 June 2018
Line 1:		Line 1:
	You should verify that the public mirror list and ''yum'' repositories have be set up.		You should verify that the public mirror list and ''yum'' repositories have be set up.

	* Check the public repository mirror listing(s) for the release: http://www.networksecuritytoolkit.org/nst/mirrors/repo-~~f26~~-x86_64.mirrors.txt		* Check the public repository mirror listing(s) for the release: http://www.networksecuritytoolkit.org/nst/mirrors/repo-f28-x86_64.mirrors.txt
	* If you don't see a text mirror list file for the 64 bit release you need to do the following:		* If you don't see a text mirror list file for the 64 bit release you need to do the following:
	** Create and add the missing files to ''html/mirrors'' on the development machine.		** Create and add the missing files to ''html/mirrors'' on the development machine.
Line 8:		Line 8:
	[root@dev32 repo]# cd ~/nstpro		[root@dev32 repo]# cd ~/nstpro
	[root@dev32 nstpro]# make upload-repo		[root@dev32 nstpro]# make upload-repo
	* Verify that you can load the empty repomd.xml file from each of the listed mirrors for the release. For the NST 26 release this was:		* Verify that you can load the empty repomd.xml file from each of the listed mirrors for the release. For the NST 28 release this was:
	** http://networksecuritytoolkit.org/repo/nst/~~f26~~/x86_64/repodata/repomd.xml		** http://networksecuritytoolkit.org/repo/nst/f28/x86_64/repodata/repomd.xml

	'''NOTE''': If there are any errors, you may need to log into the mirrors to create the top level directories.		'''NOTE''': If there are any errors, you may need to log into the mirrors to create the top level directories.
Line 17:		Line 17:
	'''NOTE''': To create an ''empty'' repository at networksecuritytoolkit.org, log into the web server and run the following commands:		'''NOTE''': To create an ''empty'' repository at networksecuritytoolkit.org, log into the web server and run the following commands:
	cd ~/public_html/repo/nst		cd ~/public_html/repo/nst
	install -d ~~f26~~ && ln -s ../empty ~~f26~~/x86_64		install -d f28 && ln -s ../empty f28/x86_64