Red Hat Bugzilla – Bug 67519
up2date gets confused when calculating dependancies.
Last modified: 2015-01-07 18:57:24 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020606
Description of problem:
up2date works perfectly apart from the fact that I cannot update kernels. My
first notion was that the Nvidia kernel drivers were causing the fault, so I
uninstalled the RPMS - the fault persisted.
When trying to update the kernel, I get this error message on the console used
to start up2date:
Traceback (innermost last):
File "/usr/share/rhn/up2date_client/gui.py", line 858, in doInstallation
kernelsToInstall = up2date.installPackages(self.selectedPkgList,
File "/usr/share/rhn/up2date_client/up2date.py", line 2237, in installPackages
raise DependencyError(_("Dependencies should have already been resolved, but
they are not."), deps)
up2date_client.up2date.DependencyError: RPM dependency error. The message was:
Dependencies should have already been resolved, but they are not.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
I have only observed this error on a single system, however if you can provide
some form of ID, I can let you into the affected box to see the bug first hand.
Actual Results: Up2date appears to hang - it needs to be X'd or Cancelled (with
the cancel button).
Just so long as I did not attempt to upgrade the kernel, things are fine.
I am using the Nvidia Kernel drivers - these are the only 3rd party kernel level
add-ons to the Redhat box.
The traceback shouldn't happen with current versions.
However, in this scenario, an update can not be performed
correctly without leaving unresolved deps. So the error
message is correct.