solved - Re: [K12OSN] [REPOST] yum dependency resolution

[Gavin Chester]

On Fri, 2005-08-12 at 11:49 -0300, Ramon wrote:
> run the resolve dependencies command.
> not sure what it is right now, but do "man yum" and you will see the command to
> resolve dependencies.

Thanks anyway, but not sure I understood your post - primarily because
yum is all about resolving dependencies automagically.  Nevertheless, I
did re-read the man page, but there was nothing to explain what you were
referring to.

Anyway, I did some yahoo-ing* and reading for an hour or so and came
across something useful in this FAQ http://wiki.linux.duke.edu/YumFaq

Seems I needed to remove the problem package (named in the error report)
as the best way to overcome the update blockage to yum.  The FAQ then
suggests reinstalling said package after the update is complete.  That's
what is happening as I type - so, success!

I just find too many error messages need explanation from someone who
knows how write more than just lines of code.  I was off on a completely
wrong tangent to what the error message really meant until I read the
FAQ. 

*I'm favouring yahoo again nowadays because they claim to have indexed
more pages than google since recent upgrades, and I reckon google are
almost becoming a microsoft-like monopoly in their own omnipotent way.

Gavin 


> > Try and make a long story short by citing one small example ;-) -
> >
> > I'm having trouble understanding why a yum update is failing with an
> > unmet dependency when a search of my system shows that the dependency in
> > question is already installed on my system in the exact version
> > required.  I did an "rpm--rebuilddb" just in case my system didn't know
> > about the package for some reason, but otherwise I can't seem to get
> > past this.  Is there need to, or some means to, tell yum about
> > everything that's on your system - I've always assumed it "just
> > know" (tm).
> >
> > --
> > Regards,
> >         Gavin Chester
> >