Bug 97946 - need a mechanism to install a specific version of a package, and have packages co-exist
Summary: need a mechanism to install a specific version of a package, and have package...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Adrian Likins
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-06-24 13:42 UTC by Need Real Name
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-02 16:53:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2003-06-24 13:42:37 UTC
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:

Comment 1 Mihai Ibanescu 2003-06-24 13:48:28 UTC
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).

Comment 2 Adrian Likins 2003-07-09 21:54:29 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.