Re: yup update problem


Subject: Re: yup update problem
From: Bryan Stillwell (bstill@terraplex.com)
Date: Thu Jan 25 2001 - 08:56:15 MST


On Wed, Jan 24, 2001 at 09:46:55PM -0500, Patrick Callahan wrote:
>Shouldn't we be able to install additional packages and upgrades without
>having to abandon the upgrades you provide?

Absolutely, but not if the rpm database gets broken by calling rpm with
the --force command.

>Otherwise the solution is a clean install,
> followed by a yup update
> followed by upgrades and installs of all the packages we want over and
>above the ones ydl provides in the base distribution and yup.

Your best bet would be to recompile the new software which you wish to
install from SRPMs, so that they use the libraries on your system and not
from someone else's system. You can try running yup with the
--ignore-deps option, but if you want to avoid probable problems in the
future you should make sure your libraries match what your programs use.
The easiest way to do that is by having an unbroken rpm database.

If you're curious which shared libraries a given executable on your
system uses, you can run ldd on it:

(~)> ldd /usr/sbin/mtr
        libresolv.so.2 => /lib/libresolv.so.2 (0x0ffcd000)
        libm.so.6 => /lib/libm.so.6 (0x0ff7f000)
        libncurses.so.5 => /usr/lib/libncurses.so.5 (0x0ff07000)
        libtermcap.so.2 => /lib/libtermcap.so.2 (0x0fee3000)
        libc.so.6 => /lib/libc.so.6 (0x0fd9f000)
        /lib/ld.so.1 => /lib/ld.so.1 (0x30000000)

Bryan

-- 
  Terra Soft Solutions, Inc.           | Software Engineer
  http://www.terrasoftsolutions.com/   | bstill@terraplex.com
  GPG fingerprint: 3608 4610 8C08 B8EB 0970  9686 8A93 386C 6116 EFE2



This archive was generated by hypermail 2a24 : Thu Jan 25 2001 - 08:56:18 MST