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

[Paul Millar]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 11 June 2004 10:14, TC wrote:
> 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

up2date-gnome is the graphical front-end to up2date.  You'll need to 
upgrade both at the same time.  Just put them both on the same command 
line. (No, it isn't clear from the docs that that'll work).

(but I've no idea where you might get rhnlib from, either fedora distro 
or perhaps fedora-legacy)

Just a word of warning.  up2date used to be RedHat's clone of autorpm 
(if I've got the chronology the right way around).  autorpm keeps your 
machine in sync, but originally didn't do any dependency fixing.  
Fairly recent versions had ways of guessing the RPM filename from 
dependency-name and so could fix certain problems, but it was by no 
means fool-proof (and RedHat did have a habit of breaking it).

meta-package managers (apt, yum, ...) build and maintain a database of 
these mappings, so they can (in principle) always fix dependencies.  
That is provided you don't ask the system to do something that's 
impossible ;^)

AFAIK, there's a RPM-port of Debian's apt, and a generic port of 
(Mandrake's ?) yum for RedHat platforms (fedora and legacy systems).  
I've heard good things about yum, and I image apt will work fine too, 
but I can say for sure as I'm now going with Debian (which is very 
nice).

HTH,

Paul.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAydtZ/9JwS78PA+kRApKkAJ92efjPmNOq/DVCLLedZ3imUkFk1gCfXoki
fRvu3Be4hqOxd9BH6OK3n1A=
=KTe9
-----END PGP SIGNATURE-----