Yes it is worth everyone knowing that the EPEL repo seems to have an EMI style version of DPM and that it has a more recent version number than the glite one.
So if it gets triggered in a yum update for example it will install it's stuff in locations that are likely to be completely incompatible with what you are upgrading from.
So EPEL must be disabled or lower priority than the glite repo (if you want a glite DPM)
Wahid
On 17 Aug 2011, at 19:55, Ewan MacMahon wrote:
>> -----Original Message-----
>> From: GRIDPP2: Deployment and support of SRM and local storage management
>> [mailto:[log in to unmask]] On Behalf Of Santanu Das
>>
>> Thanks everyone; everything is [hopefully] sorted out now.
>> Figured out (hard-way though) that RPMforge repo must be installed and
>> epel must be disabled.
>>
> I'm glad it's working, but I would just note that that's the precise
> opposite of how we have things. The only real problem we've found
> with EPEL is that it contains a version of DPM; we use the
> yum-priorities plugin to ensure that we get DPM from the glite repo,
> and just use EPEL for things that aren't in the glite (or indeed,
> other) repos.
>
> Ewan
>
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
|