This bug has been copied from bug #378911 and has been proposed to be backported to 5.1 z-stream (EUS).
Created attachment 291589 [details] logfile of rhn_check
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0057.html
*** Bug 435635 has been marked as a duplicate of this bug. ***
*** Bug 436808 has been marked as a duplicate of this bug. ***
added to RHEl5.2 release notes updates as follows: <quote> If your system has yum-rhn-plugin-0.5.2-5.el5_1.2 (or an earlier version) installed, you will be unable to upgrade to Red Hat Enterprise Linux 5.2 through yum update. To work around this, upgrade your yum-rhn-plugin to the latest version (using yum update yum-rhn-plugin) before running yum update. </quote> please advise if any further revisions are required. thanks!
*** Bug 454322 has been marked as a duplicate of this bug. ***
Tracking this bug for the Red Hat Enterprise Linux 5.3 Release Notes.
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team.
*** Bug 462413 has been marked as a duplicate of this bug. ***
*** Bug 461251 has been marked as a duplicate of this bug. ***
*** Bug 455710 has been marked as a duplicate of this bug. ***
*** Bug 452452 has been marked as a duplicate of this bug. ***
*** Bug 448728 has been marked as a duplicate of this bug. ***
*** Bug 444035 has been marked as a duplicate of this bug. ***
*** Bug 394471 has been marked as a duplicate of this bug. ***
*** Bug 466059 has been marked as a duplicate of this bug. ***
*** Bug 464433 has been marked as a duplicate of this bug. ***
*** Bug 474307 has been marked as a duplicate of this bug. ***