Using the RPM Epoch term

Add Epoch Term | Problems with Dependencies

The Epoch term allows new RedHat Package Manager (RPM) packages to replace old packages with slightly different names, and also where rpm considers the new package version number to be lower than the installed package. Simply increment the Epoch in the new package specification file, and rebuild the new package.

As an alternative to icrementing the Epoch, use the Obsoletes term to make the new package replace the named package. This is usually a better option for RPM name changes, not version number problems.

Add Epoch Term

Example package names that exhibit the problem:

# installed
openafs-1.4.1rc9-rhel4.4

# new version
openafs-1.4.1-rhel4.5

In this case, update the Epoch in the openafs.spec file for openafs-1.4.1-rhel4.5, then rebuild the package:

Epoch: 1

Problems with Dependencies

Adding an Epoch term may break Requires in child packages, resulting in Unable to satisfy dependencies errors at install time. Run rpm -q --provides -p subpackage.rpm to see what the child package requires, then update the parent package to match this format. Another option: set a Provides: packagename = VERSION in the parent package to satisfy the child package.

If using Yellowdog Updater, Modified (YUM), install the most recent stable version. Outdated versions of yum may not process dependencies properly.