This is a workaround for a bug in up2date-4.2.16 (version
included in Update 3 for RHEL 3). That version fails to
update the up2date package when scheduled from the website
(commandline or gui useage is fine). In order to enable
customers to update "up2date" via the RHN web interface,
this package requires a up2date >= 4.2.33. User can
choose to install this package, and the newer up2date
will be installed as a dependency. The new up2date
will be correct, and the "up2date-update" package can
then be removed.
Put the new up2date (4.2.36 or higher) into a channel
(child channel is fine)
Install up2date-4.2.16 on a rhel3 box.
attempt to update to newest update via an action
that schedules up2date only. This will fail.
Then try to install the "up2date-update" package.
This will schedule an action for "up2date-update" that
should pull in the newer up2date as a dep.
Then do basic sanity checks on up2date.
Then we need to push an even newer up2date package
into the channel. Then we need to verify that
up2date-4.2.36 can be updated to 188.8.131.52 (for example)
via a "update" action on just the up2date package.
Then downgrade to up2date-4.2.36, then update
up2date manually "aka, up2date up2date".
Repeat, but this time with "up2date -u".
Repeat but this time with the gui.
for version to verify that 4.2.36 can update itself.
Looks beautiful ;-)
See also bug 130867
An errata 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.
*** Bug 156852 has been marked as a duplicate of this bug. ***