Hello,
I have the same issue as this poster with libpq.so.4:
http://www.nabble.com/8.3.0-upgrade-td16093803.html
In short, I've upgraded to 8.3.1 from 8.1 on RHEL 4 (with some CentOS
packages). I have apps with dependencies of libpq.so.4 but this is no
longer available. 8.3.1 provides
Oliver Kohll [EMAIL PROTECTED] writes:
What I've thought of trying so far is
1) creating a symlink called libpq.so.4 towards libpq.so.5 - slightly
dangerous due to possible API changes?
Worth trying. According to the CVS logs
Oliver Kohll wrote:
I have the same issue as this poster with libpq.so.4:
http://www.nabble.com/8.3.0-upgrade-td16093803.html
In short, I've upgraded to 8.3.1 from 8.1 on RHEL 4 (with
some CentOS packages). I have apps with dependencies of
libpq.so.4 but this is no longer available. 8.3.1
Am Sunday, 8. June 2008 schrieb Albe Laurenz:
In short, I've upgraded to 8.3.1 from 8.1 on RHEL 4 (with
some CentOS packages). I have apps with dependencies of
libpq.so.4 but this is no longer available. 8.3.1 provides
libpq.so.5 and the compat-libs provide libpq.so.3.
Strange; does
Hi,
On Sun, 2008-06-08 at 11:55 +0100, Oliver Kohll wrote:
snip
3) building a custom compat package - I don't know how to do this
though.
These are probably my packages from http://yum.pgsqlrpms.org , and I
thought I already fixed this issue -- I'll check.
Anyway,
Peter Eisentraut [EMAIL PROTECTED] writes:
A workable fix, at least from the point of view of a Debian developer, is to
put the soname number into the package name (libpq3, libpq4, libpq5, etc.),
thus making them unique and coinstallable for all times.
FWIW, the package names Red Hat has
Thanks all, option 2 seems to work for me, just wanted to be sure I
wasn't asking for crashes.
Oliver Kohll
On 8 Jun 2008, at 18:01, Tom Lane wrote:
Oliver Kohll [EMAIL PROTECTED] writes:
What I've thought of trying so far is
1) creating a symlink called libpq.so.4 towards libpq.so.5 -
