Bug 104640
Summary: | up2date does not update kernel-headers-2.4.9-e.24 to 2.4.9-e.27 as in RHSA-2003:239 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Lars Herrmann <herrmann> |
Component: | up2date | Assignee: | Bret McMillan <bretm> |
Status: | CLOSED WONTFIX | QA Contact: | Fanny Augustin <fmoquete> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | shillman |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-19 19:24:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lars Herrmann
2003-09-18 11:57:28 UTC
Did you make sure to remove 'kernrel-*' from the exceptions list? If you did not do this during your initial run of up2date, you can run up2date-config, and click on the package-exceptions tab to change that. If it is removed, please let me know so I can investigate further. Also, please let me know if you have had any of the QU errata applied to 2.1ES. yes, we did clear the pkgSkipList. up2date did download and update kernel-2.*rpm and if I remember well, also kernel-source, but NOT kernel-headers. That's why i filed the bug, because after updating >10 packages via RHN, kernel-headers remained in the "to-update" list. This bug is filed against RHEL2.1, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |