ART Team,

QUESTION: Will any of these DAG/RPMFORGE/EPEL repos (below) conflict with ATOMIC repos, or the ASL ???

1) I have CENTOS BASE as priority=1, ATOMIC as priority=5, and DAG/RPMFORGE/EPEL repos as priority=10
2) I am following instructions for a CentOS+NGINX+DoveCot+ISPConfig install:

http://www.howtoforge.com/perfect-serve ... onfig-3-p3

It says to do the following:

rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY*
rpm --import http_//dag.wieers.com/rpm/packages/RPM-GPG-KEY.dag.txt
wget http_//pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.2-2.el6.rf.i686.rpm
rpm -ivh rpmforge-release-0.5.2-2.el6.rf.i686.rpm

rpm --import https://fedoraproject.org/static/0608B895.txt
wget http_//dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-7.noarch.rpm
rpm -ivh epel-release-6-7.noarch.rpm

rpm --import http_//rpms.famillecollet.com/RPM-GPG-KEY-remi
rpm -ivh http_//rpms.famillecollet.com/enterprise/remi-release-6.rpm

They say:

"enable RPMforge/EPEL repos as lots of packages we need are not available in the official CentOS 6.3 repositories"
"also need to enable the Remi RPM repository which contains the php-fpm package which we will install later on"

QUESTION: Will any of these DAG/RPMFORGE/EPEL repos (below) conflict with ATOMIC repos, or the ASL ???

Thx!
Jim

I dont know on that one, there are some areas where there are conflicting implementations. For example we standardized on the same design for clamav as Dag, the EPEL version on the other hand is totally different (naming, paths, etc). Its probably not going to conflict since we usually get the new releases out faster than EPEL does. Remi is a different story, since remi is usually out in front of everyone on php (hes on 5.4, we're on 5.3), you could run into problems there. Your priorities will probably keep the conflicts to a minimum, but I'd love to hear about any you run in to.

So far I've had to change the priorities for ATOMIC:

-- CENTOS BASE as priority=1
-- ATOMIC as priority=1
-- DAG/RPMFORGE/EPEL repos as priority=10

This allowed PHP to install without the php-common conflict... and will hopefully protect me in the future.