Thread: libpq version in rpm packages

I just set up a new server and would like to use rpms to manage the software on this one.  I've done the compile from source thing most of the time, but over time it seems to get messy.

I'm using CentOS 4.2, which only has packages for postgres 7.4, but I very much want to use 8.1.  I installed the 8.1 RPMs, but when I try to install packages like perl-DBD-Pg, or php-pgsql, rpm complains because they want libpq.so.3, and postgres 8.1 comes with libpq.so.4.

Does anyone have a workaround for this?  I've thought about forcing the rpms to install, or even installing the postgres libs from 7.4.

Suggestions?

Thanks.

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


Hi,

On Wed, 9 Nov 2005, Brian Mathis wrote:

> I'm using CentOS 4.2, which only has packages for postgres 7.4, but I very
> much want to use 8.1. I installed the 8.1 RPMs, but when I try to install
> packages like perl-DBD-Pg, or php-pgsql, rpm complains because they want
> libpq.so.3, and postgres 8.1 comes with libpq.so.4.
>
> Does anyone have a workaround for this? I've thought about forcing the rpms
> to install, or even installing the postgres libs from 7.4.

We have a compat RPM to solve that issue:

http://developer.postgresql.org/~devrim/rpms/compat/

There are RPMs for x86 and x86_64; as well as a srpm. This RPM includes
libs from older PostgreSQL versions and these libs satisfy the
dependencies.

Regards,
- --
Devrim GUNDUZ
Kivi Bilişim Teknolojileri - http://www.kivi.com.tr
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
                       http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDckwF4zE8DGqpiZARAvUvAKCfhBwx1OJ3KrpCBU1ODTnBaFwb3ACgqPdO
OJ9hxlkksO7dHtAy1rd/tDo=
=mcse
-----END PGP SIGNATURE-----

Thanks for that rpm.

I noticed that the x86_64 version of the compat libs installs the files in /usr/lib, while the x86_64 postgresql-libs rpm uses /usr/lib64.  Is there are reason for that?  Otherwise, I'd prefer to keep all the 64bit libs in lib64.

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


Hi,

On Wed, 9 Nov 2005, Brian Mathis wrote:

> I noticed that the x86_64 version of the compat libs installs the files in
> /usr/lib, while the x86_64 postgresql-libs rpm uses /usr/lib64. Is there are
> reason for that? Otherwise, I'd prefer to keep all the 64bit libs in lib64.

Good catch! It seems that I used an errorneus .rpmmacros file in the
x86_64 server :(

The RPM is fixed now and will be uploaded in an hour. Until then, you can
do a

rpmbuild --rebuild

with the srpm and build the correct RPM for yourself.

Regards,
- --
Devrim GUNDUZ
Kivi Bilişim Teknolojileri - http://www.kivi.com.tr
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
                        http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDcl5S4zE8DGqpiZARAn/PAJ9zsfpK7Z85fMgGzqB8nedmiYFCswCgkyWU
H9nHr7MruNoResv+S8YBWdU=
=MfHS
-----END PGP SIGNATURE-----

Brian Mathis wrote:
> I just set up a new server and would like to use rpms to manage the
> software on this one.  I've done the compile from source thing most of
> the time, but over time it seems to get messy.
>
> I'm using CentOS 4.2, which only has packages for postgres 7.4, but I
> very much want to use 8.1.  I installed the 8.1 RPMs, but when I try
> to install packages like perl-DBD-Pg, or php-pgsql, rpm complains
> because they want libpq.so.3, and postgres 8.1 comes with libpq.so.4.
>
> Does anyone have a workaround for this?  I've thought about forcing
> the rpms to install, or even installing the postgres libs from 7.4.

I did a rpmbuild --rebuld of those two packages (perl and php) after I
installed 8.1.  This worked OK, but I can't run a nightly yum update
because it complains that it can't install the update for the php package.

Is there some type of compat rpm that we can install so that these
packages will find the required version of libpq?

Matt