[Scottish] Failed RPM dependencies - what to do about 'em?

[Phil Deane]

On Friday 11 Jun 2004 10:14, TC wrote:
> > Most RPM-based distributions now have some sort of automatic
> > dependency-resolving system. IIRC Fedora uses up2date, Mandrake uses
> > urpmi, and some use apt-rpm
>
> Ah, OK. Cool. So I'm using Redhat, in which case it mut be up2date.
>
> First problem with that is that I hit what appears to be a well-known
> SSL problem.  Quick google around and I find there's a new version of
> up2date that must be installed for use after 28th/08/03.  So, I download
> that and attempt to install. Guess what - it fails with a dependency
> error :-)
>
> The redhat page concerned does give the catch-all:
>
> "Before applying this update, make sure all previously released
> errata relevant to your system have been applied."
>
> So I can't say I wasn't warned.  But *how* do I make sure?
> So begins that maze of little passages.  Here's what happens:
>
> First, the error I get is:
>
> root at localhost downloads]# rpm -Fvh up2date-3.1.23.2-1.i386.rpm
> error: Failed dependencies:
>         up2date = 3.1.23 is needed by (installed) up2date-gnome-3.1.23-1
>
> Hmm.  What on earth is that on about.  It seems to imply that an already
> installed package (up2date-gnome-3.1.23-1).  But why did it tell me
> that.  I asked it to install a non-gnome up2date.
> Shrug, let's move on blindly. I'm thinking "something is needed by
> up2date-gnome??"  Maybe I need to update that rpm first. So, I download
> that (from the same place) and try:
>
> [root at localhost downloads]#  rpm -Fvh up2date-gnome-3.1.23.2-1.i386.rpm
> error: Failed dependencies:
>         up2date = 3.1.23.2 is needed by up2date-gnome-3.1.23.2-1
>
> Yeah, right.  That worked.  Whatever it is that I'm doing, it looks like
> I'll need to find up2date-3.1.23.2 and/or up2date-3.1.23.2 first.
>
> Now I move back to the redhat page, on to their download area, and find
> an Aladdin's cave - the Fedora area.  Clueless wanderer that I am, I
> didn't know that was there.  Looking into the RPMs there I see that
> they're now at major rev 4 for up2date and up2date-gnome.  I'll just get
> those, says me.  Bypass all the older dependency issues I will. Yes
> precious.
>
> [root at localhost downloads]# rpm -Uvh up2date-4.1.21-3.i386.rpm
> warning: up2date-4.1.21-3.i386.rpm: V3 DSA signature: NOKEY, key ID
> 4f2a6fd2
> error: Failed dependencies:
>         rhnlib >= 1.3-12 is needed by up2date-4.1.21-3
>         up2date = 3.1.23 is needed by (installed) up2date-gnome-3.1.23-1
>
> Doh!  Not only do I still need the 3.1.23, but now I need an update of
> rhnlib.  And is there an rhnlib anywhere to be found in the download
> area?  Nope.
>
> Last grasp at a straw with the gnome version:
>
> [root at localhost downloads]# rpm -Uvh up2date-gnome-4.1.21-3.i386.rpm
> warning: up2date-gnome-4.1.21-3.i386.rpm: V3 DSA signature: NOKEY, key
> ID 4f2a6fd2
> error: Failed dependencies:
>         up2date = 4.1.21 is needed by up2date-gnome-4.1.21-3
>

I am not a Redhat user. I use mandrake, but when I install somthing I dont 
type rpm i package i type urpmi package.

In urpmi you set up web addresses where packages are kept, and it gets the 
dependencies from there. 

I would imagine you would type somthing like up2date package instead.

Hope that helps


-- 

Phil Deane
http://www.MiracleExpress.force9.co.uk