Red Hat Bugzilla – Bug 97946
need a mechanism to install a specific version of a package, and have packages co-exist
Last modified: 2007-11-30 17:07:11 EST
Description of problem: I want to install documentation RPMs for multiple releases, but up2date always selects the most recent version of a given RPM, with no mechanism for installing multiple RPMs that can co-exist, or for installing a specific version of an RPM. Version-Release number of selected component (if applicable): up2date 2.8.39-1.7.2 How reproducible: 100% Steps to Reproduce: 1. Create a custom channel. 2. Load the noarch documentation RPMs from multiple releases into that channel. 3. Try to install all of the documentation RPMs for all of the releases you loaded. Actual results: You only get the most recent version of a package, even if it can reasonably co-exist with other RPMs. Expected results: There should be a mechanism (like what is used for the kernel rpms) to use for RPMs that can have multiple versions installed and can legally co-exist with each other. Additional info:
To make multiple versions of the same package coexist, just add them to removeSkipList (this is how the kernel packages are installed, without removing prior versions).
support for this as an action will probabaly land soon, cvs client code can do it as an action, just need web/app code to let you choose to install old packages.