> -----Original Message-----
> From: GRIDPP2: Deployment and support of SRM and local storage management
> [mailto:[log in to unmask]] On Behalf Of Graeme Stewart
>
> (I'm not sure what happens if you try to upgrade your worker nodes, but it
> seems a fresh install will definitely suffer from this issue.)
>
It breaks. We currently have a yum versionlock list[1] that pins
all the affected packages to the 1.7.4 versions that are available
in both 64 and 32 bit flavours, but someone with VO sized clout
really does need to poke people into fixing the 1.8.0 packages.
Ewan
[1]:
dpm-1.7.4-7sec.sl5.i386
dpm-1.7.4-7sec.sl5.x86_64
dpm-devel-1.7.4-7sec.sl5.i386
dpm-devel-1.7.4-7sec.sl5.x86_64
lcgdm-devel-1.7.4-7sec.sl5.i386
lcgdm-devel-1.7.4-7sec.sl5.x86_64
lfc-1.7.4-7sec.sl5.i386
lfc-1.7.4-7sec.sl5.x86_64
lfc-devel-1.7.4-7sec.sl5.i386
lfc-devel-1.7.4-7sec.sl5.x86_64
lfc-libs-1.7.4-7sec.sl5.i386
lfc-libs-1.7.4-7sec.sl5.x86_64
perl-dpm-1.7.4-7sec.sl5.i386
perl-dpm-1.7.4-7sec.sl5.x86_64
perl-lfc-1.7.4-7sec.sl5.i386
perl-lfc-1.7.4-7sec.sl5.x86_64
python-lfc-1.7.4-7sec.sl5.i386
python-lfc-1.7.4-7sec.sl5.x86_64
python25-dpm-1.7.4-7sec.sl5.i386
python25-dpm-1.7.4-7sec.sl5.x86_64
python25-lfc-1.7.4-7sec.sl5.i386
python25-lfc-1.7.4-7sec.sl5.x86_64
python26-dpm-1.7.4-7sec.sl5.i386
python26-dpm-1.7.4-7sec.sl5.x86_64
python26-lfc-1.7.4-7sec.sl5.i386
python26-lfc-1.7.4-7sec.sl5.x86_64
lcgdm-libs-1.7.4-7sec.sl5.i386
lcgdm-libs-1.7.4-7sec.sl5.x86_64
dpm-libs-1.7.4-7sec.sl5.i386
dpm-libs-1.7.4-7sec.sl5.x86_64
python-dpm-1.7.4-7sec.sl5.i386
python-dpm-1.7.4-7sec.sl5.x86_64
|