Thread: Postgresql 8.0.2 SLES 9 rpm - libpq.so.3 broken

R WARRINER wrote:

> Anyone ran across a broken libpq.so.3 link from the SLES rpm, and if
> so found a solution to fix it?
>
>
>
> Regards,
>
> Paul
>
>
>
> PS,
>
> #### YaST2 conflicts list - generated 2005-04-19 04:22:00 ####
>
>
>
> freeradius 0.9.3-106.6 conflict
>
>     Unresolved Requirements:
>
>         freeradius requires libpq.so.3()(64bit)
>
>     Conflict Resolution:
>
>         ( ) Ignore Conflict and Risk System Inconsistencies
>
> libpq.so.3()(64bit) not available
>
>     Required by:
>
>         PyGreSQL requires libpq.so.3()(64bit)
>
>         freeradius requires libpq.so.3()(64bit)
>
>         pure-ftpd requires libpq.so.3()(64bit)
>
>         samba-pdb requires libpq.so.3()(64bit)
>
>         snort requires libpq.so.3()(64bit)
>
>     Conflict Resolution:
>
>         ( ) Remove All 5 Referring Packages
>
>             Delete PyGreSQL
>
>             Delete snort
>
>             Delete samba-pdb
>
>             Delete pure-ftpd
>
>             Delete freeradius
>
>         ( ) Ignore Conflict and Risk System Inconsistencies
>
> pure-ftpd 1.0.18-39.4 conflict
>
>     Unresolved Requirements:
>
>         pure-ftpd requires libpq.so.3()(64bit)
>
>     Conflict Resolution:
>
>         ( ) Ignore Conflict and Risk System Inconsistencies
>
> PyGreSQL 3.4-34.1 conflict
>
>     Unresolved Requirements:
>
>         PyGreSQL requires libpq.so.3()(64bit)
>
>     Conflict Resolution:
>
>         ( ) Ignore Conflict and Risk System Inconsistencies
>
> samba-pdb 3.0.9-2.6 conflict
>
>     Unresolved Requirements:
>
>         samba-pdb requires libpq.so.3()(64bit)
>
>     Conflict Resolution:
>
>         ( ) Ignore Conflict and Risk System Inconsistencies
>
> snort 2.1.1-37.6 conflict
>
>     Unresolved Requirements:
>
>         snort requires libpq.so.3()(64bit)
>
>     Conflict Resolution:
>
>         ( ) Ignore Conflict and Risk System Inconsistencies
>
>
>
> #### YaST2 conflicts list END ###
>


There's been a change on  libpq  from libpq.so.3  to libpq.so.4
you need to recompile all the pagackes that depend on  libpq.so.3  so
they can use  the new libpq.so.4




Leonel Nunez

Hi,

On Tue, 19 Apr 2005, Leonel Nunez wrote:

> There's been a change on  libpq  from libpq.so.3  to libpq.so.4
> you need to recompile all the pagackes that depend on  libpq.so.3  so they
> can use  the new libpq.so.4

Actually, no.

Reinhard Max, the SuSE PostgreSQL RPM maintainer has just wrote that:

"Whoops, it seems I accidentally used a version of the spec file that
didn't the libpq.so.3 workaround. I'll build and upload a fixed
postgresql-libs package shortly..."

FYI
--
Devrim GUNDUZ
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.tdmsoft.com                         http://www.gunduz.org

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


Hi,

On Tue, 19 Apr 2005, R WARRINER wrote:

> Anyone ran across a broken libpq.so.3 link from the SLES rpm, and if so
> found a solution to fix it?
<snip>

Update:

Reinhard has fixed the problem and uploaded the new binaries. They are
now available from:

ftp://ftp.suse.com/pub/projects/postgresql

They will also be available in PostgreSQL FTP site and its mirrors later
in the day.

Regards,
- --
Devrim GUNDUZ
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.tdmsoft.com                         http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFCZi98tl86P3SPfQ4RAlcfAKDP7DjyEqDccSKO42HFAzBjk3xuwACeLVJO
TicD+1C+/vYyv0pxMgZtVGY=
=j5ag
-----END PGP SIGNATURE-----