Bug 88794 - RFE: Ability to mark certain packages as "never update"
Summary: RFE: Ability to mark certain packages as "never update"
Keywords:
Status: CLOSED DUPLICATE of bug 25257
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Other
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chip Turner
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-04-14 09:08 UTC by Joachim Breitsprecher
Modified: 2007-10-24 02:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:52:40 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Joachim Breitsprecher 2003-04-14 09:08:22 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020903

Description of problem:
In RHN, there is no possibility to mark packages that should never be updated.
For example, I am running a system with a custom-built kernel that should not be
updated via RHN.
Now, of course, the RHN pages show this system as having "critical updates"
available. I could not find a way to turn that off.

It would be nice to have some kind of "skip list" in the system preferences
where one could mark certain packages as irrelevant for updates, although they
are installed.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Log in to RHN
2. Look at the "My RedHat Network" page

    

Actual Results:  Some systems are shown as having "critical updates available",
although not all updates apply to these systems

Additional info:
Comment 1 Greg DeKoenigsberg 2003-04-14 13:30:40 UTC 
Yes, this is one of the oldest requests in our collection.  We'll get to it one
day, we promise.

*** This bug has been marked as a duplicate of 25257 ***
Comment 2 Red Hat Bugzilla 2006-02-21 18:52:40 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.