On Tue, Dec 11, 2007 at 07:45:36PM -0800, MHR enlightened us: > > On Tue, Dec 11, 2007 at 02:13:10PM -0800, MHR enlightened us: > > > Please note: the version number listed in the rpm -qa is 2.3.0, but the > > > version number listed in the yum update confirmation is 2.0.4. > > > > > > > rpm -qa --queryformat "%{epoch}:%{name}-%{release}-%{version}.%{arch}" > openoffice* > > > > I bet they have an epoch of 0, but the 2.0.4 packages have an epoch of 1, > > which means they are newer, even though the version number is smaller. > > > They work like the 2.0 version from before, meaning the same bug I moved to > 2.3 to avoid. > > So, I guess I'll put in an exclude until something else changes. > I wasn't terribly clear. By "newer", I only mean in the eyes of RPM. You could take foo-0.0.0.0.1beta, give it an epoch of 1 and foo-99.9pro with the default epoch of 0, and RPM would think the 0.0.0.0.1beta was newer. I'm not sure why the openoffice 2.x RPMs have an epoch of 1. Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263 _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos