Build and Update the Yum Repository: Difference between revisions

From MediaWiki
Jump to navigationJump to search
No edit summary
No edit summary
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Before building the ISO release image, you should make sure the NST yum repository is up to date.
Before building the ISO release image, you should make sure the NST yum repository is up to date and built for a ISO release.


If the release you are working on is based on a new version of Fedora, you will probably want to prune any old package builds and delta RPMs out of your repository before uploading the initial versions of the RPMs associated with the release. This can be done using the following commands:
You can also prime the pump by copying your development cache area to your new repository build area. This is optional, but saves download time and avoids the case of a server being down or an author upgrading a package since your last testing cycle.


[root@nst-dev-32 repo]# cd yum
The following will prune any old package builds and delta RPMs out of your repository and make sure the configuration files in the ''nst-release'' package are updated (these are the files that end up under the ''/etc/nst/iso/'' directory). This can be done using the following command:
  [root@nst-dev-32 yum]# make clear
[root@nst-dev-32 yum]# rm -fr repo/drpm
[root@nst-dev-32 yum]# ./configure
[root@nst-dev-32 yum]# make all repo-sign


Run the following command to make sure the NST yum repository is up to date.
[nst@nst-repo repo]$ svn update # To make sure you are in sync with your manifest commit
 
  [nst@nst-repo repo]$ cp -r ../dev/yum/cache yum/
  [root@nst-dev-32 repo]# make repo-build-upload
[nst@nst-repo repo]$ make release-repo-build

Latest revision as of 07:17, 7 June 2020

Before building the ISO release image, you should make sure the NST yum repository is up to date and built for a ISO release.

You can also prime the pump by copying your development cache area to your new repository build area. This is optional, but saves download time and avoids the case of a server being down or an author upgrading a package since your last testing cycle.

The following will prune any old package builds and delta RPMs out of your repository and make sure the configuration files in the nst-release package are updated (these are the files that end up under the /etc/nst/iso/ directory). This can be done using the following command:

[nst@nst-repo repo]$ svn update # To make sure you are in sync with your manifest commit
[nst@nst-repo repo]$ cp -r ../dev/yum/cache yum/
[nst@nst-repo repo]$ make release-repo-build