Make Sure Public Repos Are Setup: Difference between revisions

From MediaWiki
Jump to navigationJump to search
No edit summary
No edit summary
 
(7 intermediate revisions by one other user not shown)
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-f34-x86_64.mirrors.txt
* 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 yum
  [root@dev repo]# cd ~/nstpro
  [root@dev32 repo]# make repo-upload
  [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 example:
** 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.
'''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 f34 && cp -a ../empty f34/x86_64

Latest revision as of 16:00, 23 June 2021

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-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:
    • 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 the development machine:
[root@dev repo]# cd ~/nstpro
[root@dev 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: 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 f34 && cp -a ../empty f34/x86_64
Retrieved from "https://wiki.networksecuritytoolkit.org/nstwiki/index.php?title=Make_Sure_Public_Repos_Are_Setup&oldid=9622"