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,
--
Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge
[email protected] http://www.dpmms.cam.ac.uk/~werdna
