On 07/26/2011 03:16 PM, Dr Andrew C Aitchison wrote:
> Not sure whether the problem is my end or upstream, but my SL6 "mirror" has
>
> /local/dpmms-builds/NOBACKUP/upstream/61/i386/os/Packages/compat-openldap-2.3.43-2.el6.i686.rpm
> /local/dpmms-builds/NOBACKUP/upstream/61/i386/os/Packages/compat-openldap-2.4.19_2.3.43-15.el6.i686.rpm
> /local/dpmms-builds/NOBACKUP/upstream/61/i386/updates/security/compat-openldap-2.4.19_2.3.43-15.el6_0.2.i686.rpm
>
> rpmquery --qf '%{epoch}:%{name}-%{version}-%{release}.%{arch}.rpm\n' -p /local/dpmms-builds/NOBACKUP/upstream/61/i386/*/*/compat-openldap-2.*rpm
> 1:compat-openldap-2.3.43-2.el6.i686.rpm
> (none):compat-openldap-2.4.19_2.3.43-15.el6.i686.rpm
> (none):compat-openldap-2.4.19_2.3.43-15.el6_0.2.i686.rpm
>
> Which version should I be using, compat-openldap-2.3.43-2.el6 because
> it has an (implicitly higher) epoch, or
> compat-openldap-2.4.19_2.3.43-15.el6_0.2 because the version number is
> higher and it is in a security update ?
>
> Thanks,
>

Hi,
It looks like you mirror is a bit off.  It is labeled "61" but it has 
everything from 60 and 61.

The "2.4.19_2.3.43" packages where from SL 6.0.  They were built from 
openldap 2.4.19_2.3.43 source rpm.
But then I think someone figured out that you had no idea which version 
of openldap the compat-openldap was compatible with.  So they pulled the 
compat libraries into it's own source rpm and lowered the number to be 
the number that it is compatible with.
They then added the epoch because the new compat-openldap had a lower 
release version that the old one.

So you need to do two things.
1 - clean up your 61 mirror
2 - trust yum :)

Troy
-- 
__________________________________________________
Troy Dawson  [log in to unmask]  (630)840-6468
Fermilab  ComputingDivision/SCF/FEF/SLSMS Group
__________________________________________________