Red Hat Bugzilla – Bug 470227
Unresolvable chain of dependencies with HelixPlayer, RealPlayer, and RealPlayer-uninstall
Last modified: 2011-02-15 08:58:43 EST
Created attachment 322700 [details]
up2date -u output
Description of problem:
A RHEL 4.7 box with all packages installed hit this error when I tried to update it from RHN. The full up2date output is attached, here's a summary:
- RHEL 4.7 'everything' installation is performed. It contains HelixPlayer.
- The box is then subscribed with the Extras channel, which contains RealPlayer
- RealPlayer obsoletes HelixPlayer.
- RealPlayer-uninstall obsoletes RealPlayer and HelixPlayer, and conflicts
- up2date -u is performed
- transaction fails.
Version-Release number of selected component (if applicable):
This is a showstopper for the update. Looks like one has to uninstall HelixPlayer manually and try up2date -u again. Then it's all right. Another ugly workaround is to do up2date -u RealPlayer, which brings Realplayer and obsoletes HelixPlayer. Then up2date -u is able to update to box, ignoring RealPlayer-uninstall (which is very interesting...).
So, I think up2date is misbehaving. However, feel free to change this to component RealPlayer if its Obsoletes:/Conflicts: are wrong.
I'm seeing something in a similar vein here though in my case the chain of dependencies is clear.
A workstation subscribed to the Extras channel with only HelixPlayer installed will see the RealPlayer-uninstall package remove HelixPlayer.
Since there does not seem to be advisory against HelixPlayer this behaviour is unwanted.
*** Bug 441778 has been marked as a duplicate of this bug. ***
I'm seeing the same as in comment #7. System is subscribed to the Extras channel and to all BETA channels.
*** Bug 485188 has been marked as a duplicate of this bug. ***
I can verify that with RealPlayer-uninstall-10.0.9-4 the update process proceeds without any unsatisfied dependencies.
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 therefore 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.