UMD:Repository
Revision as of 16:46, 14 October 2011 by imported>Kkoum
Introduction | Prerequisites | Repository | Products | Capabilities |
There are two ways to configure the necessary repositories for UMD-1
RPM based configuration
On each production machine that is to be configured for using the UMD repositories, site administrators must follow the installation instructions given below:
- Remove all UMD and EPEL related configuration files that may exist from /etc/yum.repos.d so that there is no misconfigured epel or UMD repositories.
Note be careful not to remove the OS or other necessary repo configuration files
execute rm /etc/yum.repos.d/UMD* /etc/yum.repos.d/epel* - Install epel-release-5-4.noarch.rpm
execute wget http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm
yum install epel-release-5-4.noarch.rpm - Install yum-priorities RPM
execute yum install yum-priorities - Install the umd-release RPM that adds all missing repositories that are needed for the installation of UMD products and configures yum priorities
execute wget http://repository.egi.eu/sw/production/umd/1/sl5/x86_64/updates/umd-release-1.0.2-1.el5.noarch.rpm
yum install umd-release-1.0.2-1.el5.noarch.rpm
Manual Configuration
The Production sites will need to configure the following repositories
- The Main OS Repository
- EPEL repository: follow the installation notes available at EPEL
- EGI Trust Anchor Repository: use the .repo files at EGI CAs repository
- UMD Production Repository: use the .repo files at UMD repository
It is required to set the UMD repository with the highest priority in order to avoid possible discrepancies with EPEL.
In order to do this, you will need to install yum-priorities package and verify that the .repo file for UMD has
protect=1 priority=1
Also make sure that your /etc/yum/pluginconf.d/priorities.conf file has
[main] enabled = 1
check_obsoletes = 1