Hi Dennis,
the xrootd rpm was added to UMD to solve some dependency conflicts
for one UMD update. I will check the details of the problem to have
more information.
In principle xrootd is not part of UMD, but these dependencies, but as
you are pointing out the priority of UMD is preventing you to install
the new client library.
There's an UMD update at the end of this month, and we will most
probably release the version 3.3.6-1 to make it available to sites
using UMD repositories.
Thanks a lot for pointing out this issue.
Peter
On 22 May 2014 14:50, Dennis van Dok <[log in to unmask]> wrote:
> I'm seeing something odd when installing xrootd from UMD-3.
>
> =================================================================================================================
> Package Arch Version Repository Size
> =================================================================================================================
> Installing:
> dpm-xrootd x86_64 3.1.3-4.el5 umd-3-el5-x86_64-updates 160 k
> Installing for dependencies:
> xrootd x86_64 1:3.3.3-1.el5 epel-5-x86_64 518 k
> xrootd-client-libs x86_64 1:3.3.3-1.el5 umd-3-el5-x86_64-updates 504 k
> xrootd-server-libs x86_64 1:3.3.3-1.el5 epel-5-x86_64 351 k
>
> Transaction Summary
> =================================================================================================================
>
> Does anybody know why only xrootd-client-libs is included in umd-3-updates? I've given that repo
> a higher priority, so it will only install from epel if no package is available.
>
> Cheers,
>
> Dennis
> --
> D.H. van Dok :: System administrator :: www.nikhef.nl/grid ::
> Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/
--
Peter Solagna
EGI.eu - Senior Operations Manager
email: [log in to unmask]
skype: peter.solagna.egi
Mobile: +31(0)630373070
|