Re: postgresql-server-7.0.3-2.i386.rpm error

From: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
To: Vilson farias <vilson(dot)farias(at)digitro(dot)com(dot)br>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: postgresql-server-7.0.3-2.i386.rpm error
Date: 2000-12-12 15:35:23
Message-ID: 3A3645BB.D8124ACD@wgcr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Vilson farias wrote:
> I've been trying to install 7.0.3, but I'm always getting the same error,
> even if I try to install in another computer. What can I do?

> [root(at)localhost /tmp]# rpm -i postgresql-7.0.3-2.i386.rpm
> [root(at)localhost /tmp]# rpm -i postgresql-devel-7.0.3-2.i386.rpm
> [root(at)localhost /tmp]# rpm -i postgresql-server-7.0.3-2.i386.rpm
> /sbin/ldconfig: warning: can't open var/tmp/rpm-tmp.10903 (Not a directory),
> skipping
> /sbin/ldconfig: warning: can't open 1 (No such file or directory), skipping

The ldconfig warnings are a bunch of bogosities. They are not a
problem. Now, an ldconfig _error_ is a bird of a different feather.....

I will investigate _why_ these warnings are even being generated -- but,
the gist is that they do not in any way cause problems with the actual
installation.

The technical side of it is that the ldconfig warnings are being issued
by a %post scriptlet, after the files themselves are already installed.
Ldconfig needs to be run to update ld.so on the new shared objects that
are being installed -- and ldconfig is choking on some files. Again,
I'll double check the scriptlet to see _why_ it's choking on these
particular filenames, but, in the meantime, it's not a big deal and
won't cause problems with the installation, AFAIK.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Nathan Barnett 2000-12-12 15:39:36 RE: Reliability Stability of PgSQL & it's JDBC driver
Previous Message Gordan Bobic 2000-12-12 15:26:29 v7.1 RPMs