[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Fedora 9 dependency issues





Michael Schwendt wrote:
On Sat, 29 Nov 2008 15:31:01 -0500, Jeffrey Ross wrote:

Michael Schwendt wrote:
On Sat, 29 Nov 2008 14:29:43 -0500, Jeffrey Ross wrote:

I've got a dependency issue that I'm not sure how to deal with. This is a Fedora 9 x86_64 system. I'm trying to install tkinter and I'm running the command "sudo yum install tkinter" yum proceeds to run, listing the packages that need to be included to satisfy the dependencies. However it gets to:

--> Missing Dependency: python = 2.5.1-25.fc9 is needed by package tkinter-2.5.1-25.fc9.x86_64 (fedora)
DEBUG:
[]
Error: Missing Dependency: python = 2.5.1-25.fc9 is needed by package tkinter-2.5.1-25.fc9.x86_64 (fedora)



I then try to install python by itself with "sudo yum install python" and I get the following:

Package matching python-2.5.1-25.fc9.x86_64 already installed. Checking for update.
Nothing to do


So for whatever reason it appears as if tkinter is looking for the non x86_64 version.

How do I get around this?
Could you please show the result of some queries?

  yum repolist
  yum list tkinter python
  rpm -q tkinter python

And just to mention it, 2.5.1-26.fc9 (python+tkinter) is latest.
 * updates: mirror.umoss.org
 * rpmfusion-nonfree: lordmorgul.net
4999 packages excluded due to repository priority protections
  ^^^^^^^^^^^^^^^^^^^^^^
  ^^^
Highly suspicious. See whether you can get rid of those excludes
somehow (by disabling/reconfiguring Yum plugins).

Available Packages
tkinter.x86_64 2.5.1-25.fc9 fedora

-26.fc9 is in updates-newkey

[jeff wisdom tmp]$ rpm -q tkinter python
package tkinter is not installed
python-2.5.1-26.fc9.x86_64

The old tkinter you're seeing requires the old python (-25.fc9) from
the original "fedora" Everything repo. You've got the update for Python
already, -26.fc9, but not the corresponding tkinter. They are built
from the same src.rpm and are found in the updates repo.

well you pointed me in the right direction. The problem was not completely due to the excludes but how the priorities were configured. Basically when the "new-key" repros were put into place I never upped the priority for it and as such was only checked if no other repo's had the file I was looking for.

Thanks, Jeff


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]