Bug 79284 - up2date does not resolve packets that are marked in the skiplist
up2date does not resolve packets that are marked in the skiplist
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: up2date (Show other bugs)
2.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Red Hat Satellite QA List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-12-09 11:05 EST by Steffen Mann
Modified: 2007-11-30 17:06 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-01-15 00:41:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Steffen Mann 2002-12-09 11:05:06 EST
Description of Problem:
up2date glibc-devel ENTER w/o kernel-headers installed

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

up2date2.7.61-7.x.2
kernel-headers 2.4.9e.i3
gcc2.96


How Reproducible:


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:

to come across this we did up2date -f kernel-headers and then 
up2date gcc 

prior to this glibc-devel came back with the error message that and
kernel-headers are required and it can not resolve packet interdependencies,
which it shouln't have, or it should have said that the *kernel is marked in the
skiplist and it can not resolve interdependencies because of this.

Expected Results:

resolve dependencies even kernel-headers are in skiplist, they need to be installed!

Additional Information:
Comment 1 Adrian Likins 2003-01-15 00:41:40 EST
Things on the skiplist are not installed. Even when they are deps (especially
when they are deps...)

That said, the error messages should indicate why the package wasn't
available. I belive this error reporting is more verbose in current versions.


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